# NTSB GAA16CA011: Cessna 172M, N20488, McMinnville, OR, October 2, 2015 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: October 1, 2015, 20:10 local (Oct 2, 2015, 03:10 UTC) - Place: McMinnville, OR - Coordinates: 45.2, -123.129997 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=45.2000&lon=-123.1300&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing-flare/touchdown: Collision during takeoff/land](https://openairdocs.org/ntsb-events/490) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed, report November 5, 2015 - Report: Approved by Office Director - NTSB office: General Aviation Accidents - Parties: FEDERAL AVIATION ADMINISTRATION - NTSB case key (mKey): 92147 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=GAA16CA011 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/92147/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=92147 - Page: https://openairdocs.org/ntsb/GAA16CA011 ## Probable cause The flight instructor's failure to correct the student pilot's approach path during the final approach, which resulted in a collision with runway threshold lights. Contributing to the accident was the student pilot's failure to attain and maintain the recommended approach path. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Action: lack of action](https://openairdocs.org/ntsb-findings/02041030): Personnel issues › Action/decision · Instructor/check pilot (probable cause); cases with it: [Cessna 172M, 15 cases](https://openairdocs.org/ntsb-findings/02041030/cases.md?model=2072418), [All aircraft, 792 cases](https://openairdocs.org/ntsb-findings/02041030/cases.md) - [Performance/control parameters: descent/approach/glide path](https://openairdocs.org/ntsb-findings/01062040): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Cessna 172M, 15 cases](https://openairdocs.org/ntsb-findings/01062040/cases.md?model=2072418), [All aircraft, 810 cases](https://openairdocs.org/ntsb-findings/01062040/cases.md) - [Performance/control parameters: descent/approach/glide path](https://openairdocs.org/ntsb-findings/01062040): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Cessna 172M, 15 cases](https://openairdocs.org/ntsb-findings/01062040/cases.md?model=2072418), [All aircraft, 810 cases](https://openairdocs.org/ntsb-findings/01062040/cases.md) - [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Student/instructed pilot (probable cause); cases with it: [Cessna 172M, 123 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=2072418), [All aircraft, 9,308 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) - [Info processing/decision: decision making/judgment](https://openairdocs.org/ntsb-findings/02041520): Personnel issues › Action/decision · Instructor/check pilot; cases with it: [Cessna 172M, 36 cases](https://openairdocs.org/ntsb-findings/02041520/cases.md?model=2072418), [All aircraft, 3,100 cases](https://openairdocs.org/ntsb-findings/02041520/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Approach-VFR pattern final: Altitude deviation](https://openairdocs.org/ntsb-events/282); cases with it: [Cessna 172M, 2 cases](https://openairdocs.org/ntsb-events/282/sequence.md?model=2072418), [All aircraft, 104 cases](https://openairdocs.org/ntsb-events/282/sequence.md) - [Landing-flare/touchdown: Collision during takeoff/land](https://openairdocs.org/ntsb-events/490) (defining event); cases with it: [Cessna 172M, 15 cases](https://openairdocs.org/ntsb-events/490/sequence.md?model=2072418), [All aircraft, 1,330 cases](https://openairdocs.org/ntsb-events/490/sequence.md) ## Analysis The student pilot reported that on his first night training flight he was practicing takeoffs and landings. He stated that during his third approach, as he was turning from base to final, the precision approach path indicator (PAPI) displayed four red lights, indicating that he was below the recommended approach path. The flight instructor told him that he was too low and to add power. The student pilot added power and the far left PAPI light started to turn from red to white. He reported that on short final, he reduced engine power to idle and that during touchdown, the airplane collided with a runway threshold light. The airplane sustained substantial damage to horizontal stabilizer spar. The flight instructor reported no preimpact mechanical failures or malfunctions with the airframe or engine that would have precluded normal operation. ## Factual narrative The student pilot reported that on his first night training flight he was practicing takeoffs and landings. He stated that during his third approach, as he was turning from base to final, the precision approach path indicator (PAPI) displayed four red lights, indicating that he was below the recommended approach path. The flight instructor told him that he was too low and to add power. The student pilot added power and the far left PAPI light started to turn from red to white. He reported that on short final, he reduced engine power to idle and that during touchdown, the airplane collided with a runway threshold light. The airplane sustained substantial damage to horizontal stabilizer spar. The flight instructor reported no preimpact mechanical failures or malfunctions with the airframe or engine that would have precluded normal operation. ## Aircraft - Registration: [N20488](https://openairdocs.org/aircraft/N20488), registered now, S/N 17261331, built 1973 (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: 17261331 - Year built: 1973 - Airframe hours: 4857 - Engines: LYCOMING O-320-E2D 150 horsepower reciprocating - Damage: Substantial damage - Flight: Instructional, Part 91 - Operator: David F Waggoner, doing business as Willamette Aviation - Registered owner: David F Waggoner - Airworthiness certificate: Standard, Utility - Last inspection: 100 hour, March 27, 2015 - Departed: UAO, AURORA, OR - Destination: MMV, McMinnville, OR - Airport: MMV, Mc Minnville Muni, runway 22, 5,420 × 150 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Student pilot; age 42; injuries: none; student; medical: class 3, without waivers/limitations; seat: left; restraint: 3-point; flight hours: 43 total, 3.7 in this make and model, 3.7 as pilot in command - Flight instructor; age 63; injuries: none; flight instructor, commercial; airplane ratings: single-engine land, multi-engine land; instrument ratings: airplane; medical: class 2, with waivers/limitations; last flight review April 28, 2015; seat: right; restraint: 3-point; flight hours: 1,520 total, 522 in this make and model, 1,445 as pilot in command ## Weather - Conditions: Visual (VMC), Night - Wind: 220° at 5 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 63 °F, dew point 54 °F - Altimeter: 30.05 inHg - Observed at: KMMV ## 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 20151001016679A](https://openairdocs.org/incident/20151001016679A), Oct 1, 2015: Cessna 172M, Mcminnville, OR, Substantial damage. CFII was providing night flight instruction at the mmv airport to a student pilot who did not have night flight endorsements or solo endorsement in CE-172 .… ## Other investigations on N20488 (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 SEA06CA082](https://openairdocs.org/ntsb/SEA06CA082), Mar 28, 2006: Cessna 172 (N20488), Aurora, OR, substantial damage. Probable cause: The student pilot's misjudgment of the landing flare resulting in a hard landing. A related factor was the crosswind. ## Docket (3 files) The files NTSB released with the investigation on October 29, 2015, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=92147. 2.5 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 2.2 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40433310&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF - Memorandum for Record - Telephone Interview, Student Pilot (item 2, .PDF, 27 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40433311&FileExtension=.PDF&FileName=Memorandum%20for%20Record%20-%20Telephone%20Interview,%20Student%20Pilot-Master.PDF - Photo (Courtesy of FAA) (item 3, .PDF, 327 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40433312&FileExtension=.PDF&FileName=Photo%20(Courtesy%20of%20FAA)-Master.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.