MIA82IA110 · Piper PA-31-350
Moore Data Systems Piper PA-31-350 · Incident: airframe, component or system failure en route
From Sarasota Bradenton International Airport (SRQ) to Baton Rouge Metropolitan Airport (BTR)
Event
- NTSB case
- MIA82IA110
- 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
- Incident
- 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-31-350
- Aircraft type
- Piper PA-31
- 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
- N41045
- Operator
- Moore Data Systems
- Onboard fatalities
- Unknown
- Route
- From Sarasota Bradenton International Airport (SRQ), Sarasota, FLTo Baton Rouge Metropolitan Airport (BTR), Baton Rouge, LA
- 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
- Airframe, component or system failure
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Minor
Cause areas
- Exhaust system, clamp › Brittle fracture
- Manufacturer › Material defect(inadequate quality of material)
- Manufacturer › Miscellaneous, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
WHILE CRUISING AT 8000 FEET, THE RIGHT ALTERNATOR LIGHT CAME ON AND THE PILOT ACCOMPLISHED THE REQUIRED PROCEDURES FOR AN ALTERNATOR FAILURE. SHORTLY THEREAFTER, HE NOTICED AN AREA OF DISCOLORATION ON THE INBOARD NACELLE OF THE RIGHT ENGINE AND SAW FLAMES INSIDE THE NACELLE. THE PILOT SECURED THE ENGINE, DECLARED AN EMERGENCY AND MADE A SINGLE ENGINE LANDING AT TALLAHASSEE, FL. EXAMINATION OF THE ENGINE REVEALED A BROKEN TURBOCHARGER EXHAUST CLAMP WHICH ALLOWED THE EXHAUST TUBE TO SEPARATE FROM THE TURBO. HIGH TEMPERATURE EXHAUST GASES THEN STARTED THE FIRE WHICH DISABLED THE ALTERNATOR WIRING. METALLURGICAL EXAMINATION OF THIS CLAMP AND SEVERAL OTHERS THAT HAD FAILED INDICATED THAT THE FAILURES WERE DUE TO HIGH TEMPERATURE EMBRITTLEMENT. THE LACK OF HIGH TEMPERATURE DUCTILITY WAS ATTRIBUTED TO IMPROPER HEAT TREATMENT WHEN THE CLAMPS WERE MANUFACTURED.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record MIA82IA110
- Event ID
- 20020917X02422
- Case number
- MIA82IA110
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1982-04-03.
- API snapshot SHA-256: 68b239dc6c7ac04cbf4f41f124894cab07ab187095c62faf99ff89db2896fb99; retrieved 2026-09-24T03:28:04.107Z.