MIA89FA109 · Cessna 172M
Cessna 172M · Accident: in flight encounter with weather
From Lakefront Airport (NEW) to Mobile Regional Airport (MOB)
Event
- NTSB case
- MIA89FA109
- 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
- 2 · 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
- Instrument Meteorological Cond
Cessna 172M
- 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
- N80542
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Lakefront Airport (NEW), New Orleans, LATo Mobile Regional Airport (MOB), Mobile, 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
- Unknown
- 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
- In flight encounter with weather
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Visual flight rules (VFR) flight into instrument meteorological conditions (IMC); Tree(s)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › VFR flight into imc, continued
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE ACFT WAS REPORTED MISSING WHEN IT DID NOT RETURN TO MOBILE AFTER A TRIP TO NEW ORLEANS ON 3/16/89. A SEARCH WAS INITIATED BY THE CIVIL AIR PATROL & THE ACFT WAS FOUND ON 3/19/89 WHERE IT CRASHED NEAR THE ARPT AT PASCAGOULA, MS. INITIAL IMPACT OCCURRED WITH TREES APRX 300 YARDS SHORT OF RWY 31. A WITNESS SAID HE HEARD AN ACFT FLY OVER THE ARPT AT APRX 2330 CST. AT THAT TIME, HE NOTED THE WX WAS EXTREMELY FOGGY. NO PREIMPACT PART FAILURE OR MALFUNCTION WAS FOUND DURING THE INVESTIGATION. THE NON-INSTRUMENT RATED PLT HAD LOGGED ONLY ABOUT 65 HRS FLT TIME.
Probable cause
CONTINUED FLIGHT BY THE PILOT INTO INSTRUMENT METEOROLOGICAL CONDITIONS (IMC). CONTRIBUTING FACTORS WERE: INADEQUATE PREFLIGHT PLANNING, WEATHER CONDITIONS, PILOT'S LACK OF INSTRUMENT FLIGHT TIME, LACK OF VISUAL CUES AT NIGHT, AND TREES AT THE CRASH SITE.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA89FA109
- Event ID
- 20001213X27937
- Case number
- MIA89FA109
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1989-03-17.
- API snapshot SHA-256: e53598a47b59f29d767effe8c153068f27069c3a016f4da5a2ebf4e513a78ded; retrieved 2026-09-21T03:22:38.736Z.