FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA82FKJ05 · Piper PA-25

2 Aug 1982 · JAY, FL, United States

Piper PA-25 · Accident: loss of control in flight while maneuvering

From ODUM STRIP, FL to ODUM STRIP, FL

Report a problem

Event

NTSB case
MIA82FKJ05
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
Visual Meteorological Cond

Piper PA-25

Aircraft type
Piper PA-25
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
N8921L
Operator
E.M. Odum
Onboard fatalities
Unknown
Route
From ODUM STRIP, FLTo ODUM STRIP, 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 137: Agricultural
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 · aerial application
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
Loss of control in flight
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
Stall
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 handling, improper
  • Pilot in command › Airspeed, not maintained
  • Pilot in command › Inadequate initial training
  • Pilot in command › Judgment, poor
  • Pilot in command › Lack of familiarity with aircraft
  • Pilot in command › Lack of total experience in type of aircraft
  • Pilot in command › Lack of total experience in type operation
  • Pilot in command › Overconfidence in personal ability

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

NTSB narrative

THE ACFT STALLED DURING A SPRAYING OPERATION. THE PLT RECEIVED HIS PRIVATE PILOT'S CERTIFICATE APPROXIMATELY FOUR MONTHS PRIOR TO THE ACCIDENT. HE HAD NO FLT TIME LOGGED IN A PA-25 & NO INFORMATION COULD BE FOUND TO INDICATE THE PLT HAD RECEIVED ANY INSTRUCTION, GROUND OR FLT, IN AGRICULTURAL OPERATIONS. THE PLT DID NOT HOLD A PART 137 CERTIFICATE. THE ACFT WAS BORROWED BY THE PLT FROM A PART 137 OPERATOR TO SPRAY HIS OWN CROPS.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record MIA82FKJ05
Event ID
20020917X03786
Case number
MIA82FKJ05
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: 702136992db9cab100c5871432fe435ecdaa7e3e76f4f4f8b689fe899e11f656; retrieved 2026-09-21T07:59:23.712Z.