MIA01LA089 · Piper PA-32RT-300T
Piper PA-32RT-300T · Accident: in flight encounter with weather while maneuvering
From Tampa International Airport (TPA) to Beaumont Municipal Airport (BMT)
Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- MIA01LA089
- 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
- Unknown
- 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-32RT-300T
- Aircraft type
- Piper PA-32
- 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
- N911PL
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Tampa International Airport (TPA), Tampa, FLTo Beaumont Municipal Airport (BMT), Beaumont, TX
- 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
- Maneuvering · turn to reverse direction
- 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 › Design stress limits of aircraft, exceeded
- Pilot in command › Flight into known adverse weather, attempted
- Wing › Separation
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
According to transcripts of the Saint Petersburg AFSS telephone brief of flight conditions given to a person represented as the pilot of N911PL for a VFR flight plan between Tampa, Florida and Beaumont, Texas, on March 3, 2001. Due to a stationary frontal system lying between northern Georgia and a point in the Gulf of Mexico west of New Orleans, severe thunderstorm watches were in effect, moderate turbulence, strong headwinds, surface and aloft hail to 1 inch possible, wind gusts to 60 knots possible with maximum tops of thunderstorms about 45,000 feet existed along his intended flight path. Numerous SIGMETS, AIRMETS, and weather watches were in effect prior to and during the actual flight. The destination forecast called for IFR ceilings until 2000 local time although the flight plan called for a destination arrival time of 1438. The flight departed Tampa at 1208 and was advised by FAA Gulfport Approach Control that FAA New Orleans Approach Control recommended the flight not continue VFR. Once the pilot accepted the recommendation, Gulfport suggested a heading, but the radar return was observed to take a different heading, start a high rate of descent, and communications ceased at 1422 local time. A Coast Guard helicopter sighted wreckage pieces at about the 216 degree radial/ 17 miles from the Gulfport VOR at about 1509. A Coast Guard vessel was dispatched to the scene and recovered aircraft seats, interior parts, personal luggage, and an undeployed life raft. Subsequently, the left wing was recovered and the wing/fuselage attachments underwent NTSB Materials Laboratory analysis. The fractures were indicative of overstress in the upward, (assuming upright aircraft orientation) direction. No other pieces of the wreckage nor the pilot was recovered to date.
Probable cause
the pilot's attempted flight into known adverse weather, resulting in an in flight loss of control, exceedance of design limits of the aircraft, and wing separation prior to collision with water.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA01LA089
- Event ID
- 20010307X00554
- Case number
- MIA01LA089
- 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, coordinates. 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: 87d7e487343b825686a7e47fe50883f012d5a264813791f16c6e51131534e8b5; retrieved 2026-09-20T20:38:32.535Z.