Trans South Piper PA-28R-200 accident
Piper PA-28R-200 · Accident: total loss of engine power (mechanical failure) en route
From Huntsville, AL to Birmingham, AL
Event
- NTSB case
- ATL86LA089
- 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
- Charter & commuter
- 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-28R-200
- Aircraft type
- Piper PA-28
- 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
- N74HB
- Operator
- Trans South
- Onboard fatalities
- Unknown
- Route
- From Huntsville, ALTo Birmingham, AL
- 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 135: Air Taxi & Commuter
- 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
- 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
- Company maintenance personnel › Maintenance, inspection, not performed
- Company maintenance personnel › Maintenance, service bulletin/letter, not followed
- Engine assembly, connecting rod › Failure, total
- Engine assembly, connecting rod › Overload
- Engine assembly, cylinder › Separation
Approximate · Estimated position: the centre of Hanceville, AL, the place the record names. Not the accident site.
NTSB narrative
WHILE ENROUTE TO BIRMINGHAM THE PILOT EXPERIENCED A COMPLETE POWER FAILURE WHEN NO. 2 CYLINDER SEPARATED FROM THE ENGINE ASSEMBLY. THE PILOT ATTEMPTED TO MAKE AN EMERGENCY LANDING ON INTERSTATE 65 NEAR HANCEVILLE, AL, AND THE AIRCRAFTCOLLIDED WITH AN EMBANKMENT ADJACENT TO THE SOUTHBOUND LANES. THE INVESTIGATION DETERMINED THAT THE AIRCRAFT HAD EXPERIENCED SEVERE ENGINE VIBRATIONS TWICE WITHIN THE THREE MONTHS PRIOR TO THE ACCIDENT. ON BOTH OCCURRENCES THE CYLINDERS WERE OVERHAULED AND THE AIRCRAFT RETURNED TO SERVICE. THE MAINTENANCE PERSONNEL WHO REPAIRED THE ENGINE STATED THAT HE DID NOT FOLLOW THE PROCEDURES AS OUTLINED IN THE ENGINE SERVICE MANUAL. THE FAILURE TO RETORQUE AND INSPECT THE ENGINE ASSEMBLY CAUSED THE OTHER CYLINDERS STUDS TO LOOSEN AND EVENTUAL NO. 2 CYLINDER FAILURE.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record ATL86LA089
- Event ID
- 20001213X32981
- Case number
- ATL86LA089
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (5)
- 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: fbfa0a6c1835a1251af0afe715caf13b43da9c672fa512668933079383b9357b; retrieved 2026-09-18T20:04:39.084Z.
- The NTSB's operator name is blank for N74HB; the operator shown is the name the NTSB records it doing business as.