ATL93LA057 · Cessna 152
Ron'S Aircraft Service Cessna 152 · Accident: undershoot during landing
From 5W5 to 5W5
Event
- NTSB case
- ATL93LA057
- 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 152
- Aircraft type
- Cessna 152
- 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
- N49945
- Operator
- Ron'S Aircraft Service
- Onboard fatalities
- Unknown
- Route
- From 5W5To 5W5
- 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
- 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
- Undershoot
- 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 › Directional control, not maintained
- Pilot in command › Proper touchdown point, misjudged
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE STUDENT PILOT WAS ATTEMPTING HIS FOURTH SOLO LANDING OF THE DAY. THE AIRCRAFT LANDED ABOUT 83 FEET SHORT OF THE RUNWAY, LEFT OF CENTERLINE, AND 5 DEGREES LEFT OF RUNWAY HEADING. THE STUDENT WAS UNABLE TO CORRECT BACK TO THE RUNWAY, AND THE AIRCRAFT COLLIDED WITH A RUNWAY LIGHT AND A DIRT BANK BEFORE NOSING DOWN. THE PILOT'S INSTRUCTOR WAS MONITORING THE FLIGHT AND CONFIRMED THAT THE AIRCRAFT VEERED TO THE LEFT OF THE RUNWAY AFTER TOUCHDOWN. THE PILOT REPORTED NO MECHANICAL PROBLEMS WITH THE AIRCRAFT PRIOR TO THE ACCIDENT. THE STUDENT HAD LOGGED ABOUT 21 HOURS TOTAL TIME, INCLUDING ABOUT 1 HOUR SOLO TIME.
Probable cause
THE STUDENT PILOT'S FAILURE TO JUDGE A PROPER TOUCHDOWN POINT, AND HIS FAILURE TO MAINTAIN DIRECTIONAL CONTROL AFTER LANDING. A FACTOR WAS THE PILOT'S LACK OF TOTAL EXPERIENCE.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL93LA057
- Event ID
- 20001211X11780
- Case number
- ATL93LA057
- 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: 6e055b2ec521c07bc3565b48c0025987dd394be956045409ebc832a5aad770a6; retrieved 2026-09-23T02:20:33.877Z.