# NTSB SEA02LA102: Piper PA-16, N5942H, Umpqua, OR, June 15, 2002

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Limited investigation · Final report
- Date: June 15, 2002, 16:00 local (23:00 UTC)
- Place: Umpqua, OR
- Coordinates: 43.350456, -123.539291 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=43.3505&lon=-123.5393&mi=10
- Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping)
- Highest injury: No injuries
- Injuries: 1 uninjured
- Status: Completed, report October 24, 2002
- Report: Approved by Office Director
- Parties: Portland FSDO
- NTSB case key (mKey): 54954
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=SEA02LA102
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/54954/pdf
- NTSB docket: https://data.ntsb.gov/Docket?ProjectID=54954
- Page: https://openairdocs.org/ntsb/SEA02LA102

## Probable cause

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.

## Analysis

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.

## Factual narrative

On June 15, 2002, approximately 1600 Pacific daylight time, a Piper PA-16, N5942H, impacted the terrain during an attempted VFR go-around at Umpqua Sky Park, Umpqua, Oregon. The private pilot, who was the sole occupant, was not injured, but the aircraft, which belonged to a friend of the pilot, sustained substantial damage. The 14 CFR Part 91 personal pleasure flight, which departed Roseburg Airport, Roseburg, Oregon, about 30 minutes prior to the accident, was being operated in visual meteorological conditions. No flight plan had been filed. There was no report of an ELT activation.

According to the pilot, just as he was initiating the flare for landing at the 1,800 foot grass landing strip, he encountered unusual winds that caused the aircraft to suddenly yaw to the left. He therefore initiated a go-around, but the aircraft impacted a ditch along the side of he runway, crossed a dirt road, and collided with a fence. Although he had added full power and attempted to execute a go-around, the pilot's attempt to compensate for the unfavorable wind was not adequate to keep the aircraft from colliding with the terrain near the left side of the runway.

According to both the pilot and the FAA inspector who looked at the aircraft after the accident, there was no indication that there had been any malfunction or anomaly in the aircraft’s flight control system or engine.

## Sequence of events

In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf).

- In flight collision with terrain/water, go-around (vfr)
  - compensation for wind conditions - inadequate, pilot in command (cause)
  - clearance - not maintained, pilot in command (cause)
  - weather condition - unfavorable wind (contributing factor)

## Aircraft

- Registration: [N5942H](https://openairdocs.org/aircraft/N5942H), registered now, S/N 16-564, built 1949 (OpenAirDocs)
- Reported make and model: Piper PA-16
- Registry model: [Piper PA-16](https://openairdocs.org/model/piper-pa-16) (registry code 7101602) (OpenAirDocs)
- Registry engine: [Lycoming 0-235 series](https://openairdocs.org/engine/lycoming-0-235-series) (registry code 41505, 4 cycle) (OpenAirDocs)
- Category: Airplane
- Serial number: 16-564
- Airframe hours: 2500
- Engines: Lycoming O-235-C1 108 horsepower reciprocating
- Damage: Substantial damage
- Flight: Personal, Part 91
- Registered owner: Patricia H. Bruck
- Airworthiness certificate: Standard, Normal
- Last inspection: Annual, June 26, 2001, 30 hours before
- Departed: RBG, Roseburg, OR
- Destination: Umpqua, OR
- Airport: Umpqua Sky Park, runway 090, 1,800 × 100 ft, grass/turf

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 43; injuries: none; private; airplane ratings: single-engine land; medical: class 3, valid medical--no waivers/lim.; last flight review September 14, 2001; seat: left; flight hours: 500 total, 3 in this make and model, 450 as pilot in command, 20 in the last 90 days, 15 in the last 30 days, 1 in the last 24 hours

## Weather

- Conditions: Visual (VMC), Day
- Visibility: 20 statute miles
- Lowest ceiling: none
- Temperature: 70 °F

## FAA reports on this event (1)

The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs).

- [Accident 20020615013339A](https://openairdocs.org/incident/20020615013339A), Jun 15, 2002: Piper PA16, Roseburg, OR, No damage. (.19) On June 15, 2002, approximately 1600 pacific daylight time, a Piper PA-16, N5942H, impacted the terrain while attempting to land at Umpqua sky park,…

## Other investigations on N5942H (2)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB ANC13CA034](https://openairdocs.org/ntsb/ANC13CA034), Mar 17, 2013: Piper PA-16 (N5942H), Big Lake, AK, substantial damage. Probable cause: The pilot's decision to land on unsuitable terrain.
- [NTSB SEA05CA148](https://openairdocs.org/ntsb/SEA05CA148), Jul 20, 2005: Piper PA-16 (N5942H), Park City, MT, substantial damage. Probable cause: The failure of the pilot to maintain directional control of the airplane on the takeoff roll. Factors contributing to the accident included the loose gravel, ditch, and the fence.

## Docket (1 files)

The files NTSB released with the investigation on September 15, 2002, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=54954. 285 KB in all.

- Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 285 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40445557&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.
