The U.S. aircraft register, updated daily
Accidents · NTSB SEA02LA102 · Final report

Piper PA-16 accident near Umpqua, Oregon, June 15, 2002

On June 15, 2002 at about 11:00 pm local time, a Piper PA-16, registered N5942H, was substantially damaged in an accident near Umpqua, Oregon (Umpqua Sky Park 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 failure to adequately compensate for unfavorable wind conditions and maintain clearance from the terrain during an attempted VFR go-around. Factors include an encounter with unfavorable wind conditions during the landing flare and the attempted go-around.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
June 15, 2002 · about 11:00 pm local time
Place
Umpqua, Oregon · Umpqua Sky Park · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Piper PA-16 · all PA-16s on the register
Registration
N5942H · registry record · serial 16-564
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

Just as the pilot was about to initiate the landing flare at the 1,800 foot grass airstrip, he encountered unfavorable winds that caused the aircraft to yaw to the left. The pilot therefore executed a go-around, but the aircraft impacted the terrain along the left side of the runway, and then collided with a nearby fence. It was determined that there were no problems with the aircraft’s flight controls or its engine, but that the pilots attempted compensation for the unfavorable winds was inadequate to avoid impacting the terrain.

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: 500 hours in all; 3 in this make and model; 20 in the last 90 days; 15 in the last 30 days; 450 as pilot in command
  • Last flight review: September 14, 2001
  • Medical certificate: Class 3 (valid medical--no waivers/lim.)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 2,500 hours
  • Last inspection: annual inspection, June 26, 2001; 30 hours since
  • Maximum gross weight: 1,500 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming O-235-C1 (piston); 0 hours total

The flight

  • Departed from: RBG Roseburg OR at 10:30 pm
  • Destination: Umpqua OR
  • Flight plan: none
  • Runway 090, 1,800 ft by 100 ft

Weather at the time

  • Light: daylight
  • Visibility: 20 statute miles
  • Sky: clear
  • Temperature: 70°F (21°C), dew point 0°F (-18°C)

Injuries

FatalSeriousMinorNone
Crew1

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 N5942H the same tail number, which may have belonged to a different aircraft at the time

2013-03-17ANC13CA034 · accident near Big Lake, AK · substantial damage · no injuries
2005-07-20SEA05CA148 · accident near Park City, MT · substantial damage · no injuries

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.