ATL83LA080 · Swearingen SA-226TC
Swearingen SA-226TC · Accident: airframe, component or system failure en route
From Baton Rouge Metropolitan Airport (BTR) to DeKalb Peachtree Airport (PDK)
Event
- NTSB case
- ATL83LA080
- 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
- Instrument Meteorological Cond
Swearingen SA-226TC
- Aircraft type
- Swearingen SA-226
- 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
- N5291M
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Baton Rouge Metropolitan Airport (BTR), Baton Rouge, LATo DeKalb Peachtree Airport (PDK), Chamblee, GA
- 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
- Substantial
Cause areas
- Landing gear, normal retraction/extension assembly › Inoperative
- Other maintenance personnel › Maintenance, overhaul, inadequate
- Pilot in command › Directional control, not possible
- Pilot in command › Gear extension, not possible
- Propeller system/accessories, blade › Corroded
- Propeller system/accessories, blade › Failure, total
- Propeller system/accessories, blade › Fatigue
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
AT 11,000 FT MSL DURING CRUISE A PROP SEPARATED FROM THE LEFT ENG. THE ENG WAS FEATHERED & THE PLT OBSERVED THE ENG DISPLACED INBOARD & DOWNWARD. AN EMERGENCY LANDING WAS MADE & UPON LANDING THE LEFT MAIN GEAR WAS FOUND TO BE RETRACTED.THE ACFT SLID TO A STOP COMING TO REST ON THE ADJACENT TAXIWAY. METALLURGICAL EXAMINATION REVEALED THAT THE BLADE FAILED FROM FATIGUE INITIATING AT CORROSION PITS ON THE INTERIOR OF THE FAILED BLADE BALANCE HOLE. THE PAINT IN THE BALANCE HOLE WAS DISCONTINUOUS & NON-UNIFORM. THERE WAS NO EVIDENCE OF THE HOLE HAVING BEEN SHOTPEENED. OVERHAUL INSTRUCTIONS REQUIRE SHOTPEENING OF THE BALANCE HOLE. TSO WAS CALCULATED AS 1565.8 HRS.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record ATL83LA080
- Event ID
- 20001214X41927
- Case number
- ATL83LA080
- 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: 35eca2b3f3d3c383581960a4a0a531f7056ef0286d403e47c8e4a327268e3989; retrieved 2026-09-23T23:34:51.229Z.