GAA16CA011 · Cessna 172M
Cessna 172M · Accident: collision during takeoff/landing
From Aurora State Airport (UAO) to McMinnville Municipal Airport (MMV)
Event
- NTSB case
- GAA16CA011
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Cessna 172M
- Aircraft type
- Cessna 172
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N20488
- Operator
- David F Waggoner · private individual
- Onboard fatalities
- Unknown
- Route
- From Aurora State Airport (UAO), Aurora, ORTo McMinnville Municipal Airport (MMV), McMinnville, OR
- Aircraft age
- About 42 years (built 1973)
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Landing · flare/touchdown
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Collision during takeoff/landing
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Action/decision
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB 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.
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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA16CA011
- Event ID
- 20151009X44408
- Case number
- GAA16CA011
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2015-10-02.
- API snapshot SHA-256: 75bd567241791012c16c4c47e9f0a2df08468b34060ffe37de85b0f490e5f035; retrieved 2026-09-16T02:52:39.707Z.