# Accident 20031027027519A: Cessna 172M, Brandon, OR, October 27, 2003

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: October 27, 2003, 18:50 local time
- Place: Brandon, OR
- Airport: Brandon State Airport
- Damage: Substantial damage
- Phase of flight: Final Approach
- Operating rules: General operating rules (Part 91)
- Location: 43.0667° N, 124.4000° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=43.0667&lon=-124.4000&mi=10
- Aircraft: N80628, a cancelled registration (https://openairdocs.org/deregistered/N80628-2004-01-08) (OpenAirDocs)
- Registry model: Cessna 172M (registry code 2072418, https://openairdocs.org/model/cessna-172m) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: CESSNA 172M
- People aboard: 1
- Fatal injuries: 0
- Pilot flight hours: 1,217 total, 1,111 in this make and model, 30 in the last 90 days
- NTSB investigation: [NTSB SEA04LA013](https://openairdocs.org/ntsb/SEA04LA013) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20031027027519A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

(-23) AT APPROXIMATELY 1850 LOCAL TIME, THE PILOT WAS PRACTICING NIGHT APPROACHES. THE AIRCRAFT HIT NUMEROUS TREES APPROXIMATELY 2,500 FT. SHORT OF RUNWAY 34 THRESHOLD. AIRCRAFT CAME TO REST UPSIDE DOWN.

## The NTSB's investigation of this event (1)

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 SEA04LA013](https://openairdocs.org/ntsb/SEA04LA013), Oct 28, 2003: Cessna 172M (N80628), Bandon, OR, substantial damage. Probable cause: The pilot's failure to maintain clearance from objects while on final approach. Dark night conditions, trees and a low glidepath were factors.

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
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.