FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA83FA143 · Piper PA-28-140

17 May 1983 · NEAR SOUTH BAY, FL, United States

Piper PA-28-140 · Accident: in flight encounter with weather en route

From Miami-Opa Locka Executive Airport (OPF) to X41 · LA BELLE, FL

Report a problem

Event

NTSB case
MIA83FA143
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
1 · 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

Piper PA-28-140

Aircraft type
Piper PA-28
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
N8235N
Operator
Unknown
Onboard fatalities
Unknown
Route
From Miami-Opa Locka Executive Airport (OPF), Miami, FLTo X41 · LA BELLE, 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
Visual flight rules (VFR) flight into instrument meteorological conditions (IMC); Wire, transmission
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 PLT HAD RECENTLY PURCHASED THE ACFT & WAS USING IT TO COMMUTE ON A WEEKLY BASIS BETWEEN HIS RESIDENCE IN HIALEAH & LA BELLE WHERE HE WORKED AS AN ACFT MECHANIC. THE WRECKAGE WAS FOUND COMPLETELY SUBMERGED IN A CANAL AFTER A FLORIDA FISH & GAME OFFICIAL BECAME SUSPICIOUS WHEN HE OBSERVED SOME SMALL DEBRIS HANGING FROM A POWERLINE. VFR WX PREVAILED IN MIAMI DURING THE 0830 DEPARTURE. HOWEVER, A WITNESS AT THE LA BELLE ARPT STATED THAT AFTER 0700 FOG COMPLETELY COVERED THE ARPT & VISIBILITY WAS DOWN TO 30 FT. THE WIND THEN PICKED UP AROUND 1000 & BETWEEN 1030 & 1100 THE WIND BLEWTHE FOG AWAY.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record MIA83FA143
Event ID
20001214X43072
Case number
MIA83FA143
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: 0006a66579357b58fa5150470c4ddc885fe7afec8d8ce942f12f7e91da4d5b9b; retrieved 2026-09-21T06:48:26.946Z.