Piper PA-18 accident near Aspen, Colorado, August 9, 2009
On August 9, 2009 at about 4:00 pm local time, a Piper PA-18, registered N350CC, was substantially damaged in an accident during takeoff near Aspen, Colorado (Aspen-Pitkin County Airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 2 people were on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot's failure to maintain adequate separation behind a preceding large business jet, which resulted in an encounter with wake turbulence.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- August 9, 2009 · about 4:00 pm local time
- Place
- Aspen, Colorado · Aspen-Pitkin County Airport · map
- Type
- Accident
- Injuries
- No one was hurt; 2 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper PA-18 · all PA-18s on the register
- Registration
- N350CC · registry record · serial 18-1172
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
Prior to takeoff, the pilot was warned by tower controllers to use caution for wake turbulence from a preceding large business jet. During takeoff roll, prior to the tailwheel becoming airborne, the airplane ground-looped to the left and came to rest beside the runway. The pilot stated that the winds were calm and that he did not wait a sufficient amount of time behind the preceding airplane before starting his takeoff. Examination of the airplane revealed a bent right wing spar, bent right horizontal stabilizer and elevator.
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
- Aircraft wake turb encounter during takeoff defining event
- Loss of control on ground during takeoff
- Runway excursion during takeoff
The NTSB's findings
- cause Personnel issues › Action/decision › Info processing/decision › Identification/recognition › Pilot
- Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Directional control › Attain/maintain not possible
Pilot
- Certificate: private
- Ratings: multi-engine land; single-engine land; single-engine sea; instrument: airplane; rotorcraft: glider
- Flight time: 9,800 hours in all; 1,500 in this make and model
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: frt
- Injury: no injuries
The aircraft
- Seats: 2
- Landing gear: fixed
- Engine: Cont Motor AIO-320-A2B (piston); 0 hours total
The flight
- Departed from: ASE Aspen CO
- Destination: Gateway Canyons CO
- Flight plan: none
- Runway 33
Weather at the time
- Light: daylight
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 55°F (13°C), dew point 0°F (-18°C)
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 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.
Other NTSB records under N350CC the same tail number, which may have belonged to a different aircraft at the time
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.