Piper PA-22-150 accident near Sunriver, Oregon, May 23, 2001
On May 23, 2001, a Piper PA-22-150, registered N7815D, was substantially damaged in an accident near Sunriver, Oregon. It was a personal flight under general aviation rules (Part 91). 2 people had minor injuries. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot's failure to maintain clearance from trees during initial climb. Trees were a factor.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- May 23, 2001 · cases in 2001
- Place
- Sunriver, Oregon · map
- Type
- Accident · collision on the ground
- Injuries
- 2 people had minor injuries.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper PA-22-150 · all PA-22-150s on the register
- Registration
- N7815D · registry record · serial 22-5461
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot reported that as the airplane lifted off from the dirt airstrip, he extended full flaps. The airplane achieved an ascent rate of about 500 feet per minute and attained an altitude to just clear the surrounding trees when the altitude decreased by about 20 to 30 feet and the airspeed dropped about 15 to 20 MPH. There was not sufficient runway left to land the airplane so the pilot continued the takeoff. The airplane did not attain sufficient altitude and collided with trees. The pilot reported that there were no mechanical failures or malfunctions with the aircraft at the time of the accident.
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
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 300 hours in all; 60 in this make and model; 60 in the last 90 days; 40 in the last 30 days; 300 as pilot in command
- Medical certificate: Class 3 (valid medical--w/ waivers/lim.)
- Seat: left
- Injury: minor injuries
The aircraft
- Last inspection: annual inspection
- Seats: 4
- Landing gear: fixed
- Engine: Lycoming O-320 (piston); 0 hours total
The flight
- Departed from: Sunriver OR
- Flight plan: none
- Runway 40, 3,600 ft by 100 ft
Weather at the time
- Light: daylight
- Sky: clear
- Temperature: 0°F (-18°C), dew point 0°F (-18°C)
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| 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.
Connections how this case links to the rest of the register
- N7815D on the register today · the tail number may have moved to another aircraft since
- Piper PA-22 Tri-Pacer and Colt 2,943 registered today · the model family and its accident history
- Piper 44,840 aircraft on the register
- Engine: Lycoming O-320 27,303 aircraft carry this series today · as the NTSB recorded it
- Accidents and incidents in Oregon 1,864 since 1982 · 279 in the last ten years
- Oregon 7,004 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/SEA01LA101.json.
The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.
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 does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
