ERA16FA185 · Beech A36TC UNDESIGNAT
Beech A36TC UNDESIGNAT · Accident: system/component malfunction/failure (non-power) during takeoff
From Tupelo Regional Airport (TUP) to Charlottesville Albemarle Airport (CHO)
Event
- NTSB case
- ERA16FA185
- 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
- 4 · all aircraft and ground
- Ground fatalities
- Unknown
- 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
Beech A36TC UNDESIGNAT
- Aircraft type
- Beechcraft 36
- 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
- N60RW
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Tupelo Regional Airport (TUP), Tupelo, MSTo Charlottesville Albemarle Airport (CHO), Charlottesville, VA
- Aircraft age
- About 36 years (built 1980)
- 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
- Takeoff
- Defining eventThe 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
- System/component malfunction/failure (non-power)
- 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
- Aircraft › Aircraft power plant
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The airline transport pilot was taking off in the turbocharged reciprocating engine-equipped airplane for a personal flight. One witness reported seeing something fall from the airplane as it departed. Shortly after departure, the pilot notified air traffic control of smoke in the cockpit. The airplane then made a left, westbound turn back toward the airport, about 500ft above the ground and then it turned back toward the approach end of the departure runway while descending. Two witnesses also reported seeing fire and smoke coming from the bottom, left side of the airplane before it impacted terrain.
After the accident, airport personnel found the exhaust tailpipe and fractured v-band coupling on the runway. A support clamp, which was intended to support the exhaust tailpipe, was not found. Examination of the v-band coupling revealed stress rupture features at the edge of a spot weld that attached the outer band to the retainer, which led to the v-band fracturing, the exhaust tailpipe separating from the airplane, and an in-flight fire. Review of the maintenance records did not reveal when the v-band coupling was installed or last inspected.
There is a longstanding history of accidents and incidents resulting from v-band coupling failures on both fixed-wing aircraft and rotorcraft. Although before the accident the Federal Aviation Administration (FAA) had issued six v-band-specific airworthiness directives (AD) and other guidance materials and recommendations related to v-band failures, none of them were specific to the accident airplane make and model. Subsequent to the accident, the FAA published a notice of proposed rulemaking to obtain public feedback regarding a proposed AD that would require a repetitive annual inspection of, and would impose a 500-hour life limit on, the exhaust tailpipe v-band coupling on the accident aircraft make and model.
Probable cause
A preexisting stress rupture that initiated at a spot weld in the turbocharger v-band exhaust clamp, which resulted in the failure of the clamp and separation of the exhaust tailpipe, an in-flight fire, and subsequent impact with terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA16FA185
- Event ID
- 20160516X05929
- Case number
- ERA16FA185
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 31cd881e2923d93e433c8e6d982b4b3877ac2cf8b761c9ce1447f4e52f9adac0; retrieved 2026-09-14T21:46:09.004Z.