ATL98LA104 · Cessna 172
Cessna 172 · Accident: overrun during landing
From 6J0 to an unrecorded destination
Event
- NTSB case
- ATL98LA104
- 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 172
- 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
- N4103F
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From 6J0To not recorded
- 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
- 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 › Airspeed, excessive
- Pilot in command › Altitude, excessive
- Pilot in command › In-flight planning/decision, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot returned to the departure airport for a full stop landing. As she turned final for the landing, she realized that another airplane was behind her in the traffic pattern. At this point she elected to maintain a higher than normal airspeed and altitude on final. The pilot reported that the airplane touched down about 2000 feet down the 4000 foot long runway. The airplane rolled off the departure end of the runway, crossed a two lane road, and collided with a ditch. The pilot also recalled that there was a slight cross wind during the landing, and as she applied brakes to stop the airplane, the brakes appeared to have been ineffective in slowing the airplane. No mechanical problems with the airplane were reported by the pilot.
Probable cause
The pilot's inadequate inflight planning that resulted in excessive airspeed and altitude for a full stop landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL98LA104
- Event ID
- 20001211X10761
- Case number
- ATL98LA104
- 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: ec224c41efbc38c63ea9e0cb29e6a5e880799be1412fc8a95d933cf04e6edce1; retrieved 2026-09-21T20:43:40.095Z.