Piper PA-22 accident near St. Paul, Oregon, July 31, 2008
On July 31, 2008 at about 9:10 pm local time, a Piper PA-22, registered N2441P, was substantially damaged in an accident during landing (flare/touchdown) near St. Paul, Oregon. 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 misjudged altitude, speed, and subsequent failure to attain the proper touchdown point while landing.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- July 31, 2008 · about 9:10 pm local time
- Place
- St. Paul, Oregon · map
- Type
- Accident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper PA-22 · all PA-22s on the register
- Registration
- N2441P · no longer on the register · serial 22-2812
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot was landing on a gravel bar of a river. He made one full-stop landing, and took off for a second landing. The winds were light and he attempted a shorter landing. The wheels contacted the 1-foot-deep water about 30 feet before reaching the landing zone. The airplane pitched forward and in response he applied full back stick pressure and added power. The airplane continued pitching and nosed over, resulting in substantial damage to the wing and fuselage.
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
- Landing area undershoot during landing (flare/touchdown) defining event
- Nose over/nose down during landing (flare/touchdown)
The NTSB's findings
- cause Personnel issues › Action/decision › Info processing/decision › Identification/recognition › Pilot
- cause Personnel issues › Psychological › Perception/orientation/illusio › Perception › Pilot
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Descent/approach/glide path › Not attained/maintained
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 501 hours in all; 42 in this make and model; 14 in the last 90 days; 8 in the last 30 days; 501 as pilot in command
- Last flight review: February 9, 2008
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 3,064 hours
- Last inspection: annual inspection, July 1, 2008; 17 hours since
- Maximum gross weight: 2,000 lb
- Seats: 2
- Landing gear: fixed
- Engine: Lycoming O-320-B2A (piston); 0 hours total
The flight
- Departed from: 7S3 Hillsboro OR at 7:30 pm
- Destination: 7S3 Hillsboro OR
- Flight plan: none
Weather at the time
- Light: daylight
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 70°F (21°C), dew point 0°F (-18°C)
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.