MIA03LA028 · Beech A36
Beech A36 · Accident: total loss of engine power (mechanical failure) en route
From Greenville-Spartanburg International Airport (GSP) to Charleston International Airport (CHS)
Event
- NTSB case
- MIA03LA028
- 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
- 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 A36
- 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
- N12MB
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Greenville-Spartanburg International Airport (GSP), Greer, SCTo Charleston International Airport (CHS), Laurens, SC
- 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
- Total loss of engine power (mechanical failure)
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Fuel starvation; Tree(s)
- 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
- Other maintenance personnel › Maintenance, installation, improper
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot stated that he reached an altitude of 7,000 feet and leveled the airplane, when all of a sudden he felt a slight bump, and the engine immediately lost all power. He performed emergency procedures, but the engine did not regain power. While performing emergency procedures, he said he noticed fuel streaming from the area of the cowling, aft toward the windshield, so he committed himself to making a forced landing. The pilot executed a forced landing in an area of low pine trees and the airplane incurred substantial damage. The FAA inspector stated that postaccident examination of the airplane revealed that the stainless steel fuel line at the front top side of the engine had separated from the fuel flow transmitter, consistent with the pilot's report of the loss of engine power, and fuel streaming out the top of the cowling. The inspector said that the fitting on the fuel flow transmitter showed signs of fretting, and had been cracked, allowing fuel pressure to cause the hose to back off the o-ringed nipple. In addition, the support standoff that attaches the fuel line to the top alternator mount so as to provide support for the fuel line, was not attached, and had been subject to vibration loads, causing the fitting to separate from the fuel flow transmitter. Maintenance records indicate that the alternator had been replaced by a maintenance facility 26.6 hours prior to the accident.
Probable cause
Improper maintenance and inspection of the airplane by other maintenance personnel, and their failure to install the fuel line support after maintenance had been completed, which resulted in the introduction of vibrational loads and the in-flight separation of the fuel line from the fuel flow transmitter, fuel starvation, the subsequent loss of engine power, an emergency descent/ landing, and damage to the airplane during the off airport landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA03LA028
- Event ID
- 20021217X05612
- Case number
- MIA03LA028
- 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, coordinates. 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: 62b752b174aa62cc10a412b499c21f68ef170f96508925306c8c4c7d19ef8748; retrieved 2026-09-22T09:48:34.147Z.