ERA12FA514 · SOCATA TB 10
SOCATA TB 10 · Accident: loss of engine power (partial) during takeoff
From Brookhaven Calabro Airport (HWV) to Brookhaven Calabro Airport (HWV)
Event
- NTSB case
- ERA12FA514
- 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
- 2 · 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 TB 10
- Aircraft type
- Socata TB-10
- 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
- N5542Z
- Operator
- Mcelroy David J
- Onboard fatalities
- Unknown
- Route
- From Brookhaven Calabro Airport (HWV), Shirley, NYTo Brookhaven Calabro Airport (HWV), Shirley, NY
- 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
- 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
- Loss of engine power (partial)
- 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 power plant
- Personnel issues › Action/decision
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The accident flight was a pre-purchase demonstration of the accident airplane. The buyer intended to examine and photograph the maintenance records then fly the airplane around the airport traffic pattern with the owner. However, the owner insisted that they fly the airplane before reviewing the maintenance records. Upon starting the airplane, the owner announced that he had just been informed by the mechanic of the airplane’s inoperative tachometer but continued to taxi to the runway.
Witnesses who observed the airplane’s departure described the takeoff roll as “slow” and “anemic” and stated that the airplane used almost the entire length of the runway to become airborne. The airplane climbed slowly to treetop height in a nose-high attitude and disappeared from view. Moments later, a large smoke plume appeared out of the trees a short distance beyond the airport boundary.
A witness who was standing on his back porch facing northeast, about 1.5 miles from the airport, said the airplane appeared above the trees at the back border of his property, flying directly toward him, and that the sound of the engine was "really loud." The airplane descended over his backyard and below the height of his one-story house in a 30-degree left bank. The airplane then pitched up, climbed over the house, and struck a tree and a construction dumpster in front of the house, where it burst into flames.
The mechanic stated that the whereabouts of the maintenance records were unknown, but he provided a handwritten list of discrepancies he found and work he performed on the accident airplane, including 3 hours of disassembling and cleaning of the carburetor.
Examination of the wreckage revealed that the mixture control cable was disconnected from the carburetor mixture control arm. The cable displayed a light coating of soot, with no damage or fraying of the cable. The cable grip hardware on the mixture control arm was also undamaged, and the cable grip hole was completely open and unobstructed by the cable grip hardware, indicating that the cable had been removed from the arm and had not been reattached before the flight.
Although the owner and mechanic had represented the airplane to the buyer as airworthy with a completed annual inspection, they knew this was not the case, as the tachometer was inoperative; further, during a test flight 3 days before the accident, the engine would not produce full power. The pilot complained of the lack of engine power to the mechanic, but the mechanic stated he did nothing to troubleshoot the discrepancy because of the inoperative tachometer and further stated that he had not “signed off” the annual inspection in the maintenance records.
Probable cause
The pilot/owner's operation of the airplane with known deficiencies, and the mechanic's failure to reattach the mixture control cable to the mixture control arm following maintenance of the carburetor.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA12FA514
- Event ID
- 20120820X11154
- Case number
- ERA12FA514
- 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, 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: 7677f536be7e42a25028f994b6481203f025205da9a0aa45d72425e2e0097175; retrieved 2026-09-13T22:34:16.573Z.