ATL85LA024 · Piper PA-25-235
Piper PA-25-235 · Accident: total loss of engine power (mechanical failure) while maneuvering
From Hazel Green, AL to an unrecorded destination
Event
- NTSB case
- ATL85LA024
- 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
- 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-235
- 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
- N9855P
- Operator
- Miller L. Jones · private individual
- Onboard fatalities
- Unknown
- Route
- From Hazel Green, ALTo not recorded
- 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
- Total loss of engine power (mechanical failure)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Ignition system, magneto › Jammed
- Ignition system, magneto › Worn
- Other maintenance personnel › Maintenance, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE ACFT WAS MAKING A SWATH RUN SPRAYING CROPS WHEN THE ENGINE SUDDENLY LOST POWER WITH 200 YARDS OF LEVEL FIELD REMAINING FOR AN EMERGENCY LANDING. AFTER TOUCHDOWN THE PLT TURNED THE ACFT TO AVOID A COLLISION WITH TREES. DURING THE TURN THE NOSE OF THE ACFT DUG INTO THE GROUND CAUSING THE ACFT TO NOSE OVER. INSPECTION OF THE ENGINE REVEALED THAT THE MAGNETO COUPLING WAS LOCKED AND WOULD NOT ROTATE. FURTHER INSPECTION DISCLOSED EXCESSIVE PLAY IN THE PAWLS AND WORN STRIKER PINS AND SHAFT SPLINES. ACCORDING TO THE ACFT LOGBOOKS, AD 78-09-07 & AD 82-20-01 HAD BEEN COMPLIED WITH, 19 FLT HOURS PRIOR TO THE ACIDENT. HOWEVER, THE MAKE, MODEL, & SERIAL NUMBER OF THE MAGNETOS WERE NOT ENTERD AS REQUIRED.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record ATL85LA024
- Event ID
- 20001214X41285
- Case number
- ATL85LA024
- 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: d3daab6a18fdd033ed5568b652d1bc073aaf70dd111074c7eb5d393dc1e805ad; retrieved 2026-09-23T18:53:35.525Z.