FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ATL04FA077 · Piper PA-46-310P

23 Feb 2004 · Arlington, AL, United States

Piper PA-46-310P · Accident: in flight encounter with weather en route

From PFN · Panama City, FL to Tulsa Riverside Airport (RVS)

Report a problem

Event

NTSB case
ATL04FA077
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
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-46-310P

Aircraft type
Piper PA-46
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
N9103Z
Operator
Unknown
Onboard fatalities
Unknown
Route
From PFN · Panama City, FLTo Tulsa Riverside Airport (RVS), Tulsa, OK
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 › Aircraft control, not maintained
  • Pilot in command › Design stress limits of aircraft, exceeded
  • Pilot in command › Flight into known adverse weather, continued
  • Pilot in command › In-flight planning/decision, inadequate
  • Weather condition › Thunderstorm

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The pilot received a preflight briefing from the Gainesville Automated Flight Service Station before departing on the instrument flight. The briefer advised the pilot of the potential for occasional moderate turbulence between 24,000 and 37,000 feet and on the current Convective SIGMET for embedded thunderstorms over southern Mississippi. The flight was in cruise flight at 24, 000 feet when the airplane encountered moderate to severe turbulence and heavy rain. The airplane descended from 24,000 feet to 3,100 feet in a descending right turn in 2 minutes and 10 seconds before radar contact was lost. The airplane was located 8 hours 26 minutes after the accident along a crash debris line that extended between 1.31 miles and 1.53 miles northwest of Arlington, Alabama. Airframe components recovered from the accident site were submitted to the NTSB Materials laboratory for examination. The examinations revealed all failures were consistent with overstress fracturing and there was no evidence of pre-existing conditions or fatigue damage. Examination of the airframe revealed that the airframe design limits were exceeded. The Pilot's Operating Handbook states the maximum structural cruising speed is 173 knots indicated airspeed or 170 knots calibrated airspeed. The co-pilot airspeed indicator at the crash site indicated 180 knots calibrated airspeed. The design maneuvering speed is 135 knots indicated airspeed or 133 knots calibrated airspeed.

Probable cause

The pilots inadequate in-flight planning/decision and his failure to maintain aircraft control, resulting in an in-flight encounter with a thunderstorm and exceeding the design limits of the aircraft.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ATL04FA077
Event ID
20040305X00268
Case number
ATL04FA077
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: eead42c7365756d577c31d76d14f1c4a3995d9c4636c1a9db9a40c9ce0c7ebcd; retrieved 2026-09-20T18:32:40.824Z.