FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA12FA412 · SOCATA TB21

25 Jun 2012 · Gold Hill, NC, United States

SOCATA TB21 · Accident: fire/smoke (non-impact) during initial climb

From Gold Hill Airport (NC25) to Lancaster, PA

Report a problem

Event

NTSB case
ERA12FA412
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
1 · 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
Instrument Meteorological Cond

SOCATA TB21

Aircraft type
Socata TB21
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
N2528N
Operator
Unknown
Onboard fatalities
Unknown
Route
From Gold Hill Airport (NC25), Gold Hill, NCTo Lancaster, PA
Aircraft age
About 23 years (built 1989)
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
Initial climb
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
Fire/smoke (non-impact)
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

  • Not determined › Not determined

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

NTSB narrative

The pilot departed his home airport in North Carolina with the intention of flying the airplane to Germany where he had another residence. During the weeks before the accident, the pilot made several modifications to the airplane in preparation for the trip. Friends and witnesses described the installation of a white plastic fuel tank in the backseat, "similar to a tank you would see on a riding lawnmower." Such a tank is not aviation-approved. The installation included fuel lines that were smaller than recommended by the airplane manufacturer, and the system was vented into the cabin. Local mechanics also reported that the pilot performed his own maintenance to the turbocharger and the exhaust system. In the 2 weeks before the accident, mechanics "topped off" the oxygen system twice, the most recent service occurring 3 days before the accident. During that servicing, mechanics noted water leaking from the oxygen line, and the pilot reported trouble breathing at an altitude of 25,000 feet.

On the day of the accident, the pilot departed before dawn into instrument meteorological conditions. A witness observed the airplane trailing white and gray smoke, which turned to an orange color, consistent with an in-flight fire. Shortly after, the airplane impacted trees about ½ mile north of the departure airport.

The airplane was consumed by fire and the investigation was unable to determine the fire's origin; however, evidence of several non-approved modifications to the airplane were observed in the wreckage path, including the non-approved fuel line and valve as well as an aluminum can that was safety-wired to the outlet of the air-oil separator. Such modifications could have likely contributed to the fire's origin or spread. Fueling records from a nearby airport revealed that the pilot purchased fuel twice during the week before the accident. Airport security video showed the pilot placing the fuel hose inside the cabin of the airplane on the dates he purchased fuel, likely to fill the tank that was in the back seat.

While the pilot's most recent documented flight time was logged 2 years before the accident, his recent and total flight time could not be confirmed after the accident. Accordingly, the investigation was unable to determine if a lack of recent piloting experience may have contributed to the accident. Although the autopsy also identified coronary artery disease and a mass in the pilot's abdomen, the manner in which the airplane was flown before the accident and the witness report of an inflight fire indicates that the pilot was most likely in control of the airplane and was not incapacitated.

Probable cause

An inflight fire, the origin of which could not be determined because of postaccident fire damage. Contributing to the accident was the pilot's improper modifications to the airplane.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA12FA412
Event ID
20120625X80103
Case number
ERA12FA412
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: abfc174489ef5f92ddba7ddb196801e10f4900d85b9f5ace459864d4ae8bfa2f; retrieved 2026-09-13T22:27:20.251Z.