Piper PA32R accident near Colorado Springs, Colorado, July 23, 2009
On July 23, 2009 at about 6:40 pm local time, a Piper PA32R, registered N301RT, was substantially damaged in an accident during takeoff near Colorado Springs, Colorado (Colorado Springs Municipal airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot's low altitude encounter with windshear during takeoff.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- July 23, 2009 · about 6:40 pm local time
- Place
- Colorado Springs, Colorado · Colorado Springs Municipal · map
- Type
- Accident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper PA32R 301T · all PA32Rs on the register
- Registration
- N301RT · registry record · serial 32R-8229068
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
According to the pilot, the tower controller cautioned for wind shear and then cleared the flight to depart. The pilot delayed momentarily to assess the wind conditions and then departed. The airplane climbed to 75 feet, and then began to lose altitude as if the airplane was "being pushed down." The pilot applied corrective measures but was unable to arrest the descent. The airplane impacted the runway resulting in substantial damage to the airplane. The automated special weather observation report, issued shortly after the time of the accident, reported winds variable from 100 degrees to 160 degrees at 7 knots with light rain.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Windshear or thunderstorm during takeoff defining event
The NTSB's findings
- cause Environmental issues › Conditions/weather/phenomena › Wind › Windshear › Ability to respond/compensate
- Aircraft › Aircraft oper/perf/capability › Aircraft capability › Climb capability › Capability exceeded
Pilot
- Certificate: private
- Ratings: single-engine land; instrument: airplane
- Flight time: 930 hours in all; 355 in this make and model; 19 in the last 90 days; 8 in the last 30 days; 848 as pilot in command
- Last flight review: December 31, 2008
- Medical certificate: Class 3 (without waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 2,770 hours
- Last inspection: annual inspection, May 13, 2009
- Seats: 6
- Landing gear: fixed
- Engine: Lycoming TIO540 (piston); 0 hours total
The flight
- Departed from: KCOS Colorado Springs CO at 6:40 pm
- Destination: Amarillo TX
- Flight plan: VFR
- Runway 17R, 11,022 ft by 150 ft
Weather at the time
- Light: daylight
- Visibility: 10 statute miles
- Sky: a few clouds at 5,500 ft
- Temperature: 84°F (29°C), dew point 41°F (5°C)
- Altimeter: 30.19 inHg
- Observation at 7:56 pm from KCOS
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.