ATL01LA006 · Cessna 172K
Cessna 172K · Accident: overrun during landing
From Fort Lauderdale Executive Airport (FXE) to X58
Event
- NTSB case
- ATL01LA006
- 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 172K
- 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
- N7396G
- Operator
- Dino M. Ninku · private individual
- Onboard fatalities
- Unknown
- Route
- From Fort Lauderdale Executive Airport (FXE), Fort Lauderdale, FLTo X58
- 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 · landing roll
- First occurrenceThe 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
- Overrun
- 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
- Pilot in command(cfi) › Airspeed, excessive
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to the pilot, upon landing on the dry grass/turf runway 13, despite attempts to stop, the airplane continued to roll past the runway threshold, approaching the ditch abeam the runway. Right rudder was applied unsuccessfully to avoid the ditch, and the airplane ran off of the runway into the ditch and nosed over. Examination of the wreckage revealed no faults or failures associated with the airplane's braking system. Tire marks were found near the end of the runway where the airplane had touched down. The tire marks continued off the end of the grass runway into the ditch where the airplane nosed over. No mechanical problems were discovered during the examination of the airplane.
Probable cause
The pilot had excessive airspeed, misjudged the landing distance, and did not perform a go-around, which resulted in a nose over. The ditch was a contributing factor.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL01LA006
- Event ID
- 20001212X22108
- Case number
- ATL01LA006
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: b7eefe084212d37e6f4a693de5ac396e75ac0319d9a6fe1286c3ec89367c729d; retrieved 2026-09-22T12:23:18.901Z.