FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA84LA052 · Boeing 737-201

29 Dec 1983 · NEAR TAMPA, FL, United States

Boeing 737-201 · Accident: in flight encounter with weather en route

From Tampa International Airport (TPA) to Jacksonville International Airport (JAX)

Show on map Search Wikipedia NTSB source dataset
Report a problem

Event

NTSB case
MIA84LA052
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
Airline
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

Boeing 737-201

Aircraft type
Boeing 737
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
N811N
Operator
Unknown
Onboard fatalities
Unknown
Route
From Tampa International Airport (TPA), Tampa, FLTo Jacksonville International Airport (JAX), Jacksonville, 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 121: Air Carrier
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
None

Cause areas

  • Dispatcher › Dispatch, improper
  • Flight attendant › Seat belt, not used
  • Passenger › Seat belt, not used
  • Pilot in command › Flight into known adverse weather, initiated
  • Pilot in command › In-flight planning/decision, improper

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

NTSB narrative

PRIOR TO DEPARTURE, THE CAPTAIN REVIEWED AVAILABLE WX REPORTS & WAS AWARE OF THE WX CONDITIONS, INCLUDING CURRENT SIGMETS. HE DECIDED TO FLY A COURSE THAT WAS PARALLEL TO A FRONTAL SYS UNTIL HE COULD GET TO AN AREA WHERE HE COULD CONTINUE TO HIS DESTINATION. AFTER DEPARTING, HE LEFT THE SEAT BELT SIGN ON, BUT DID NOT BRIEF THE PASSENGERS TO EXPECT TURBULENCE NOR RESTRICT THE FLT ATTENDANTS TO THEIR SEATS, SINCE HE DID NOT EXPECT TO ENCOUNTER TURBULENCE. WHILE CRUISING AT 17,000 FT MSL, HE USED HIS RADAR AS WELL AS ATC ADVISORIES TO IDENTIFY ADVERSE WX. AFTER TURNING TO AVOID AN AREA OF HEAVY PRECIPITATION, THE ACFT ENCOUNTERED TURBULENCE. AT THAT TIME, 3 FLT ATTENDANTS & 1 PASSENGER WERE WALKING IN THE AISLE OF THE ACFT. ONE PASSENGER WAS SERIOUSLY INJURED. ONE FLT ATTENDANT & 6 PASSENGERS RECEIVED MINOR INJURIES. THE ACFT WAS THEN FLOWN BACK TO TAMPA, FL WHERE IT WAS LANDED WITHOUT FURTHER INCIDENT.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record MIA84LA052
Event ID
20001214X45366
Case number
MIA84LA052
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, damage. 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: 0aab32640211ff8481bfd90ea1ed99e0e375c81f2412f062459a479535485436; retrieved 2026-09-18T20:46:14.320Z.