Skip to content

SEA07CA216

2007-07-24 · Baker City, Oregon, United States · None · 1 aircraft · Status: Completed

Airport BKE

Aircraft involved

Probable cause & findings

The pilot's failure to maintain airspeed and misjudged flare during landing.

Factual narrative

As the pilot turned the aircraft onto the final approach leg of the traffic pattern, he referenced the Precision Approach Path Indicator (PAPI) of the landing runway. The PAPI indicated that the aircraft was above the standard glidepath, so the pilot reduced engine power to help the aircraft descend to glidepath altitude. According to the pilot, the aircraft "dropped too fast" and he applied power in an attempt to correct the descent rate. The aircraft then stalled above the runway and bounced on touchdown. The pilot recovered from the bounced landing and was able to taxi the aircraft back to the ramp. A post accident inspection revealed that the aircraft's firewall was bent. As the pilot turned the aircraft onto the final approach leg of the traffic pattern, he referenced the Precision Approach Path Indicator (PAPI) of the landing runway. The PAPI indicated that the aircraft was above the standard glidepath, so the pilot reduced engine power to help the aircraft descend to glidepath altitude. According to the pilot, the aircraft "dropped too fast" and he applied power in an attempt to correct the descent rate. The aircraft then stalled above the runway and bounced on touchdown. The pilot recovered from the bounced landing and was able to taxi the aircraft back to the ramp. A post accident inspection revealed that the aircraft's firewall was bent. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12

Verbatim from NTSB's published report. Source file NTSB_2007_SEA07CA216.txt. Findings + structured fields enriched from FAA avall.mdb. Full investigation docket on data.ntsb.gov ↗.

Related research

Matched on aircraft type or causal vocabulary (stall). All research papers