GAA18CA391 · Cessna 172 P
Cessna 172 P · Accident: hard landing
From Oakland Troy Airport (VLL) to Oakland Troy Airport (VLL)
Event
- NTSB case
- GAA18CA391
- 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 172 P
- 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
- N6508K
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Oakland Troy Airport (VLL), Troy, MITo Oakland Troy Airport (VLL), Troy, MI
- Aircraft age
- About 38 years (built 1980)
- 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
- 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
- Hard 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 › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The solo student pilot reported that, during landing, the airplane slowed, and the stall warning sounded as the main landing gear contacted the runway. He added that it appeared that the airplane had landed, but he then observed the nose drop below the horizon. He added power to go around, but the nosewheel impacted the runway, and the airplane pitched "rearward." Subsequently, the airplane porpoised, the nose landing gear strut collapsed, and he aborted the go-around. The student taxied the airplane to park without further incident.
The flight instructor reported that he witnessed that the airplane on approach was a little flat but did not appear to be unstable. The student then pitched the airplane for the numbers, the airplane floated down the runway, and it then touched down in a flat attitude. Subsequently, the airplane bounced 2 to 3 ft, porpoised, and the student was then able to taxi from the runway. The flight instructor added that the student was too late on the flare and that all of the energy came down on the nosewheel.
The airplane sustained substantial damage to the fuselage.
The student reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation.
The automated weather observation system at the airport reported that, about the time of the accident, the wind was from 250° at 7 knots. The student pilot landed the airplane on runway 27.
Probable cause
The student pilot’s failure to maintain a proper landing flare, which resulted in a hard, porpoised landing during an aborted go-around.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA18CA391
- Event ID
- 20180705X92917
- Case number
- GAA18CA391
- 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: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 65bd76ce29c85649874dd9f14d8e6adeb61fdfd665a2186099e47c55906ae3af; retrieved 2026-09-16T07:45:44.831Z.