ATL90LA155 · Cessna 172L
Southernaire Carrier Cessna 172L · Accident: partial loss of engine power (mechanical failure) en route
From Tupelo Regional Airport (TUP) to Florala Municipal Airport (0J4)
Event
- NTSB case
- ATL90LA155
- 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 172L
- 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
- N4386Q
- Operator
- Southernaire Carrier
- Onboard fatalities
- Unknown
- Route
- From Tupelo Regional Airport (TUP), Tupelo, MSTo Florala Municipal Airport (0J4), Florala, AL
- 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
- En route · cruise
- 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
- Partial loss of engine power (mechanical failure)
- 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(vref), not maintained
- Pilot in command › Proper touchdown point, not attained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT WAS IN CRUISE FLIGHT WHEN HIS ENGINE BEGAN RUNNING ROUGHLY AND VIBRATING. HE ELECTED TO MAKE AN EMERGENCY LANDING AT A NEARBY AIRPORT WHEN HE COULD NOT CORRECT THE PROBLEM. HE MADE TWO VISUAL APPROACHES TO THE LANDING RUNWAY, BUT WAS UNABLE TO LAND THE AIRPLANE. HE STATED THAT HE WAS 'TOO HIGH AND TOO FAST' ON BOTH APPROACH ATTEMPTS. ON THE THIRD ATTEMPT, HE LANDED 300 METERS PAST THE DEPARTURE END OF THE LANDING RUNWAY, WHICH IS 3,500 FEET LONG. THE AIRPLANE COLLIDED WITH A FENCE AND FLIPPED OVER. HE STATED THAT HE WAS 'SHANKEN UP' BY THE PROBLEM HE WAS HAVING WITH HIS ENGINE. INSPECTION OF THE ENGINE AFTER THE ACCIDENT REVEALED A FAILED NUMBER THREE CYLINDER EXHAUST VALVE.
Probable cause
THE PILOT'S FAILURE TO MAINTAIN PROPER AIRSPEED AND ATTAIN THE PROPER TOUCHDOWN POINT DURING THE EMERGENCY LANDING.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL90LA155
- Event ID
- 20001212X23888
- Case number
- ATL90LA155
- 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: 90d70958d1099f752e930f26e3769ac0f41607bf61c31d9281bfb1517f864c50; retrieved 2026-09-23T05:27:52.535Z.