FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

FTW85FA006 · Cessna 152

6 Oct 1984 · Monroe, LA, United States

Cessna 152 · Accident: in flight encounter with weather en route

From Winnsboro, LA to Shreveport Regional Airport (SHV)

Report a problem

Event

NTSB case
FTW85FA006
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 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
N4877H
Operator
Unknown
Onboard fatalities
Unknown
Route
From Winnsboro, LATo Shreveport Regional Airport (SHV)
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
In flight encounter with weather
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 › Flight into known adverse weather, performed
  • Pilot in command › Preflight planning/preparation, improper
  • Pilot in command › Spatial disorientation
  • Pilot in command › Weather forecast, disregarded

Approximate · Estimated position: the centre of Monroe, LA, the place the record names. Not the accident site.

NTSB narrative

PRIOR TO DEP THE PLT CONTACTED THE MONROE FSS TWICE REQUESTING A WX BRIEFING. BOTH TIMES VFR FLT WAS NOT RECOMMENDED DUE TO IFR CONDITIONS WITH LOW CEILINGS EN ROUTE AND FORECAST FOG AT THE DEST. DURING THE SECOND CALL THE PLT STATED THAT IT WAS CLEAR AT THE DEPARTURE ARPT AND HE BELIEVED HE COULD FLY TO HIS DEST BEFORE THE FORECAST FOG DEVELOPED. DESPITE THE BRIEFERS REPEATED WARNING THE PLT DEPARTED SHORTLY THEREAFTER. GROUND SCARS INDICATED IMPACT OCCURRED SLIGHTLY NOSE LOW IN A SHALLOW LEFT TURN. LOCAL LAW ENFORCEMMENT OFFICERS ESTIMATED VISIBILITY OF NO MORE THAN 1/2 MILE IN FOG AT THE TIME OF THE ACCIDENT.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record FTW85FA006
Event ID
20001214X41354
Case number
FTW85FA006
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: 0a54c663b982af28bcdc1bda1c8aa28de82bd55f7eff0a16dbdd23aaeeecfddd; retrieved 2026-09-21T05:18:33.211Z.