WPR12LA090 · Cessna 172E
Cessna 172E · Accident: hard landing
From Garberville Airport (O16) to Dinsmore Airport (D63)
Narrative check · The NTSB narrative appears to contradict this record's damage. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- WPR12LA090
- 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 172E
- 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
- N3879S
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Garberville Airport (O16), Garberville, CATo Dinsmore Airport (D63), Dinsmore, CA
- Aircraft age
- Not recorded
- 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
- 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 Possible conflict
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
According to postaccident statements from both pilots, the flight instructor took control of the airplane from the student pilot either at touchdown or just before. The airplane bounced several times after touchdown while veering to the right, and the right main wheel rolled off the 48-foot wide runway into the grass. The flight instructor added full engine power to go around. The flight instructor stated that he pulled back on the yoke to try to clear the trees beyond the end of the runway, and the airplane stalled and hit the ground. After the airplane’s right wing tip contacted the ground, the airplane reversed direction and came to a stop. Shortly after the airplane came to rest, a postimpact fire began, which consumed the airplane. The student pilot, who was the airplane owner, reported no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation.
Probable cause
The flight instructor's delayed remedial action, inadequate recovery from a bounced landing, and failure to attain/maintain adequate airspeed during an attempted go-around.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR12LA090
- Event ID
- 20120203X74411
- Case number
- WPR12LA090
- 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: d8db777e0dfa2f163f59f0ef2aeca79ad42d6450baa00a5fc190deae74a64027; retrieved 2026-09-15T17:10:18.773Z.