FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA91LA063 · Cessna 182N

9 Jan 1991 · LA BELLE, FL, United States

Cessna 182N · Accident: in flight encounter with weather en route

From 8X6 · Lake Placid, FL to Arcadia Municipal Airport (X06)

Report a problem

Event

NTSB case
MIA91LA063
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
Instrument Meteorological Cond

Cessna 182N

Aircraft type
Cessna 182
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
N69UU
Operator
Smith, Gregory H. · private individual
Onboard fatalities
Unknown
Route
From 8X6 · Lake Placid, FLTo Arcadia Municipal Airport (X06), Arcadia, FL
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
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
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 › Altitude, not maintained

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

THE PLT DID NOT OBTAIN A WX BRIEFING FOR A NIGHT CROSS COUNTRY FLT. HIS CHARTS & AIRPORT FACILITY DIRECTORY (AFD) WERE IN HIS BRIEFCSE IN THE BACK SEAT. THE FLT DEPARTED & ABOUT 8 MILES WEST OF THE DEPARTURE ARPT, ENCOUNTERED FOG. THE PLT BECAME DISORIENTED & LOST. HE OBTAINED THE AFD, ENTERED THE COORDINATES INTO HIS LORAN RECEIVER; WHICH INDICATED THE ACFT WAS 26 MILES SOUTHEAST. HE INITIATED A TURN TO RETURN & WHILE CALLING HIS INSTRUCTOR VIA A PORTABLE TELEPHONE TO OBTAIN CURRENT WX CONDITIONS, 'LOST TRACK OF ALTITUDE, MISREAD ALTIMITER'. THE ACFT COLLIDED WITH TREES. THE ACFT CAUGHT FIRE WHILE HE WAS ATTEMPTING TO RECOVER HIS BRIEFCASE. THE PLT STATED THERE WAS NO ENGINE MALFUNCTION.

Probable cause

THE PILOT'S FAILURE TO MAINTAIN ALTITUDE. A FACTOR WAS THE PILOT'S FAILURE TO OBTAIN A WEATHER FORECAST.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA91LA063
Event ID
20001212X16351
Case number
MIA91LA063
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: 8931249916d6aeb9b7429e07424bb894a57cecbd6c8c78b5682efda54322ae42; retrieved 2026-09-21T15:32:29.455Z.