FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA12FA023 · SOCATA TBM 700

12 Oct 2011 · Hollywood, FL, United States

SOCATA North America SOCATA TBM 700 · Accident: loss of engine power (total) on approach

From North Perry Airport (HWO) to North Perry Airport (HWO)

Report a problem

Event

NTSB case
ERA12FA023
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

SOCATA TBM 700

Aircraft type
Socata TBM-700
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
N37SV
Onboard fatalities
Unknown
Route
From North Perry Airport (HWO), Hollywood, FLTo North Perry Airport (HWO), Hollywood, FL
Aircraft age
About 3 years (built 2008)
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
Approach · VFR pattern final
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
Loss of engine power (total)
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

  • Aircraft › Aircraft systems
  • Personnel issues › Action/decision
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

In anticipation of the maintenance test flight, a about 72 gallons of fuel was added to the left fuel tank to balance the fuel load. During the preflight, the pilot noted that the left tank had 105 gallons and that the right tank had 108 gallons. Because of the fuel level indications, the pilot did not visually inspect the tanks; even if he had done so the wing dihedral would have prevented him from seeing the fuel level.

About 20 minutes after takeoff, the pilot received the first annunciation of "Fuel Low R," which lasted for about 10 seconds then went out. This indicates the fuel quantity is less than or equal to 9 gallons of usable fuel in the right tank. The pilot attributed this to a malfunction of the low fuel level sensor, since the fuel gauge showed about 98 gallons of fuel. He instructed the right front seat occupant (the mechanic) to make a note so the sensor would be replaced after the flight. Shortly thereafter, the amber "Fuel Unbalance" illuminated, and indicated that the right fuel quantity was greater than the left; as a result the pilot switched the fuel selector to the right tank.

He then initiated a descent to 10,000 feet to perform system checks, and after levelling off at that altitude for about 15 minutes, received a second "Fuel Low R" annunciation; he verified that the fuel selector automatically switched to the left tank and noted that the message went out after about 10 seconds. Either before or during a descent to 4,000 feet, the second "Fuel Unbalance" annunciation occurred. The right tank again depicted a greater quantity of fuel, so the pilot again switched the fuel selector to the right tank. The flight continued to a nearby airport, where the pilot terminated an instrument approach with a low approach. The flight then proceeded to the destination airport and entered the traffic pattern on a left downwind leg..

While on the downwind leg, the pilot received the third "Fuel Unbalance" annunciation and at this time the left fuel gauge indicated 55 gallons while the right fuel gauge indicated 74 gallons. Because he intended to land within a few minutes, the pilot manually selected the fullest (right) tank, then turned to base then final. While at 800 feet on final approach, the red warning message "Fuel Press" illuminated and the engine lost all power. Attempts to restore engine power were unsuccessful. Unable to reach the airport, the pilot landed on a nearby turnpike. Both fuel tanks were breached, and fuel leakage, likely from the left fuel tank, was noted at the site. Inspection of the fuel outlet filter on the engine and the fuel sequencer reservoir considered an airframe item revealed both contained minimal fuel consistent with fuel starvation from the right fuel tank that actually did not contain an adequate supply of fuel.

Postaccident operational testing of the engine revealed no evidence of preimpact failure or malfunction that would have resulted in the loss of power. Examination and testing of the right fuel gauge harness revealed that a high impedance shielded cable was not correctly soldered to the shielding braid when the airplane was manufactured, which resulted in erroneous high readings of the fuel quantity in the right tank.

Several opportunities existed to detect the fuel quantity errors in the right tank during the airplane's 600-hour and annual inspection, which was signed off the day before. Several times during the inspection, electrical power was applied and different fuel quantities for the right tank were displayed, yet nothing was done to determine the reason for the different fuel indications. For example, 41 gallons was displayed, yet 70 gallons was drained; the fuel was returned to the tank after maintenance, yet the gauge showed 51 gallons, and after a post-maintenance run was performed, the gauge showed over 140 gallons even though it hadn't been fueled. Maintenance personnel incorrectly attributed the difference to fuel migration. Further, the pilot had the opportunity to terminate the test flight after multiple conflicting indications from the right tank, yet he continued the test flight, which resulted in fuel starvation.

Probable cause

The pilot’s failure to terminate the flight after observing multiple conflicting errors associated with the inaccurate right fuel quantity indication. Contributing to the accident were the total loss of engine power due to fuel starvation from the right tank, the inadequate manufacturing of the right fuel gauge electrical harness, and failure of maintenance personnel to recognize and evaluate the reason for the changing fuel level in the right fuel tank.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA12FA023
Event ID
20111012X60235
Case number
ERA12FA023
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: 1beecfcee71ca73969886d004d3a01ef7c552edda75a2b76e0bb322f1998952d; retrieved 2026-09-15T16:49:59.909Z.