# NTSB SEA04LA013: Cessna 172M, N80628, Bandon, OR, October 28, 2003 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: October 27, 2003, 18:50 local (Oct 28, 2003, 02:50 UTC) - Place: Bandon, OR - Coordinates: 43.066665, -124.400001 - Nearby events: https://openairdocs.org/map.md?lat=43.0667&lon=-124.4000&mi=10 - Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report March 2, 2004 - Report: Approved by Office Director - Parties: FAA-FSDO - NTSB case key (mKey): 58262 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=SEA04LA013 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/58262/pdf - Page: https://openairdocs.org/ntsb/SEA04LA013 ## 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. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - In flight collision with object, approach - vfr pattern - final approach - clearance - not maintained, pilot in command (cause) - object - tree(s) (contributing factor) - proper glidepath - low, pilot in command (contributing factor) - light condition - dark night (contributing factor) ## Analysis The pilot reported that while on final approach in dark night conditions, he noted that three of the four precision approach path indicator (PAPI) light units were red with the fourth pink, fading to white, when the aircraft suddenly collided with trees about 1/2 mile from the end of the runway. The aircraft subsequently collided with the ground and came to rest inverted. The Airport/Facility Directory for the airport indicate trees as obstructions and identifies a threshold cross height requirement to clear the obstructions. ## Factual narrative On October 27, 2003, at 1850 Pacific standard time, a Cessna 172M, N80628, registered to and operated by the pilot as a 14 CFR Part 91 personal flight, collided with trees and subsequently the terrain while on final approach to Bandon State Airport, Bandon, Oregon. Night visual meteorological conditions prevailed at the time and no flight plan was filed for the local flight. The aircraft was substantially damaged and the private pilot, the sole occupant, was not injured. The pilot reported that he was practicing full stop landings in night conditions for currency requirements. The pilot stated that one landing had been accomplished without incident. During the second approach to runway 34, the pilot reported that the runway lights were lit and on low brightness, and the runway end identifier lights (REIL) were visible while on base and final approach. The pilot stated that while on final approach, he noted on the precision approach path indicator (PAPI) lights, that three of the four were red with the fourth light pink fading to white when the aircraft suddenly collided with trees. The aircraft subsequently collided with the ground, coming to rest inverted about 1/2 mile from the end of the runway. The Airport/Facility Directory for Bandon State indicates that runway 34 PAPI is equipped with four identical light units placed on the left side of the runway. An approach slope angle is not indicated, however, a threshold crossing height of 40 feet is indicated to clear trees. The Aeronautical Information Manual (AIM) indicates that for a four light unit PAPI, three red light units and one red light unit indicates a slightly low glide slope (2.8 degrees). Four red light units indicates low on the glide slope (less than 2.5 degrees). The pilot further reported on the NTSB Pilot/Operator Aircraft Accident Report Form 6120.1/2, "Review PAPI's for correct beam transmission." The U.S. Naval Observatory Sun and Moon Data for October 27, 2003, indicated sunset was at 1717, with end of civil twilight at 1746. The moon was waxing crescent with 8% of the Moon's visible disk illuminated. ## Aircraft - Registration: [N80628](https://openairdocs.org/deregistered/N80628-2004-01-08), registration cancelled 2004-01-08, S/N 17266677, built 1976 (OpenAirDocs) - Reported make and model: Cessna 172M - Registry model: [Cessna 172M](https://openairdocs.org/model/cessna-172m) (registry code 2072418) (OpenAirDocs) - Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 17266677 - Airframe hours: 5209 - Engines: Lycoming O-320-E2D 160 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Registered owner: James F. King - Airworthiness certificate: Standard, Normal - Last inspection: Annual, October 2, 2003, 33 hours before - Departed: S05, Bandon, RI - Airport: S05, Bandon State, runway 34, 3,600 × 60 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 74; injuries: none; private; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 2, valid medical--w/ waivers/lim; last flight review October 4, 2003; seat: left; flight hours: 1,217 total, 1,111 in this make and model ## Weather - Conditions: Visual (VMC), Night/dark - Wind: 340° at 9 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 59 °F, dew point 48 °F - Altimeter: 30.27 inHg - Observed at: OTH, 20 nm away ## 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 20031027027519A](https://openairdocs.org/incident/20031027027519A), Oct 27, 2003: Cessna 172M, Brandon, OR, Substantial damage. (-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… 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.