Casualties unknown

Aircraft Collides with Trees on Night Approach (N80628)

Bandon, OR, US

On October 28, 2003, a Cessna 172M (registration N80628) was involved in an aviation accident near Bandon, OR. Investigators recorded the probable cause as: The pilot's failure to maintain clearance from objects while on final approach. Dark night conditions, trees and a low glidepath were factors. This summary draws on records from the U.S. National Transportation Safety Board (NTSB) historical archive.

Sourcesthe U.S. National Transportation Safety Board (NTSB) historical archivePrimary reportUpdated 2026-07-04Data APIEditorial standards

During a dark night approach, a pilot observed unstable PAPI lights before the aircraft struck trees about half a mile from the runway, then crashed inverted. Airport records note tree obstructions and a threshold height requirement.

Incident Overview

A pilot reported that while on final approach in dark night conditions, the precision approach path indicator (PAPI) displayed unusual readings. Three of the four PAPI units were red, and the fourth appeared pink, fading to white. Shortly thereafter, the aircraft collided with trees approximately half a mile from the runway threshold. Following the tree strike, the aircraft impacted the ground and came to rest inverted.

Airport Information

The Airport/Facility Directory for the airport lists trees as obstructions and specifies a threshold cross height requirement to clear those obstructions. The directory does not provide further details on the required altitude or other specifics.

Observations

The pilot's account indicates that the approach was conducted in dark night conditions, with no other environmental factors mentioned. The PAPI light configuration suggested that the aircraft was below the ideal glide path at the moment of the collision. No information is available regarding the aircraft type, registration, engine count, operator, location, date, time of day beyond darkness, ATC involvement, or injuries. The source does not specify any damage items or occupant status.

Conclusion

The report ends with the pilot's statement and the airport directory notation. No probable cause is assigned in the source material.

Frequently asked questions

What happened in the 28 Oct 2003 Cessna 172M accident near Bandon, OR?

During a dark night approach, a pilot observed unstable PAPI lights before the aircraft struck trees about half a mile from the runway, then crashed inverted. Airport records note tree obstructions and a threshold height requirement.

What aircraft was involved and where did it happen?

The accident on 28 Oct 2003 involved a Cessna 172M, registration N80628, at Bandon, OR.

What was the probable cause of the accident?

The pilot's failure to maintain clearance from objects while on final approach. Dark night conditions, trees and a low glidepath were factors.

Investigation report by the U.S. National Transportation Safety Board (NTSB) historical archive. Original record: https://carol.ntsb.gov/event/20031103X01858. This page is a structured re-presentation; facts and quotes are in the National Transportation Safety Board (NTSB), United States.