ERA23LA091 · Cessna R172K
Cessna R172K · Accident: hard landing
From Orlando Executive Airport (ORL) to an unrecorded destination
Event
- NTSB case
- ERA23LA091
- 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
- 0
- 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 R172K
- 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
- N5405V
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Orlando Executive Airport (ORL), Orlando, FLTo not recorded
- Aircraft age
- About 45 years (built 1977)
- 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
Cause areas
- Aircraft › Aircraft systems
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that he made a normal touchdown, but he was unable to maintain directional control of the airplane during the landing roll. He reported that the airplane did not respond to his control inputs, and it veered off the left side of the runway, struck a ditch, nosed over, and came to rest inverted. The airplane sustained substantial damage to the wings and fuselage. A tower controller initially reported to local law enforcement that the airplane bounced on landing, but he later recanted his statement. Examination of the wreckage revealed the nose wheel was separated and the nose gear fork assembly was fractured. A metallurgical examination of the fractured pieces of the nose gear revealed fracture surfaces with features consistent with overstress fracture. Flight control continuity was confirmed, and the remainder of the examination revealed no pre-impact mechanical anomalies that would have precluded normal operation. Based on the physical evidence, the landing gear likely fractured during a hard landing, causing the loss of directional control.
Probable cause
A hard landing that fractured the nose landing gear assembly, resulting in a loss of directional control and a nose-over.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA23LA091
- Event ID
- 20221219106470
- Case number
- ERA23LA091
- 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, cause areas. 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: beebd322169d974d78803fe7c8ace4eed98c5e88b88bb9ad3efabc48703a5460; retrieved 2026-09-16T16:35:31.655Z.