ERA12FA115 · SOCATA TBM 700
SOCATA TBM 700 · Accident: loss of control in flight en route
From Teterboro Airport (TEB) to DeKalb Peachtree Airport (PDK)
Event
- NTSB case
- ERA12FA115
- 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
- 5 · 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
- N731CA
- Operator
- Jeffery F. Buckalew · private individual
- Onboard fatalities
- Unknown
- Route
- From Teterboro Airport (TEB), Teterboro, NJTo DeKalb Peachtree Airport (PDK), Atlanta, GA
- 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 · climb to cruise
- 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 control in flight
- 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 oper/perf/capability
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
Although the pilot filed an instrument flight rules flight plan through the Direct User Access Terminal System (DUATS), no evidence of a weather briefing was found. The flight departed in visual meteorological conditions and entered instrument meteorological conditions while climbing through 12,800 feet. The air traffic controller advised the pilot of moderate rime icing from 15,000 feet through 17,000 feet, with light rime ice at 14,000 feet. The controller asked the pilot to advise him if the icing worsened, and the pilot responded that he would let them know and that it was no problem for him. The controller informed the pilot that he was coordinating for a higher altitude. The pilot confirmed that, while at 16,800 feet, "…light icing has been present for a little while and a higher altitude would be great." About 15 seconds later, the pilot stated that he was getting a little rattle and requested a higher altitude as soon as possible. About 25 seconds after that, the flight was cleared to flight level 200, and the pilot acknowledged. About one minute later, the airplane reached a peak altitude of 17,800 feet before turning sharply to the left and entering a descent. While descending through 17,400 feet, the pilot stated, "and N731CA's declaring…" No subsequent transmissions were received from the flight.
The airplane impacted the paved surfaces and a wooded median on an interstate highway. A postaccident fire resulted. The outboard section of the right wing and several sections of the empennage, including the horizontal stabilizer, elevator, and rudder, were found about 1/4 mile southwest of the fuselage, in a residential area. Witnesses reported seeing pieces of the airplane separating during flight and the airplane in a rapid descent. Examination of the wreckage revealed that the outboard section of the right wing separated in flight, at a relatively low altitude, and then struck and severed portions of the empennage. There was no evidence of a preexisting mechanical anomaly that would have precluded normal operation of the airframe or engine.
An examination of weather information revealed that numerous pilots reported icing conditions in the general area before and after the accident. At least three flight crews considered the icing "severe." Although severe icing was not forecasted, an Airmen's Meteorological Information (AIRMET) advisory included moderate icing at altitudes at which the accident pilot was flying. The pilot operating handbook warned that the airplane was not certificated for flight in severe icing conditions and that, if encountered, the pilot must exit severe icing immediately by changing altitude or routing. Although the pilot was coordinating for a higher altitude with the air traffic controller at the time of the icing encounter, it is likely that he either did not know the severity of the icing or he was reluctant to exercise his command authority in order to immediately exit the icing conditions.
Probable cause
The airplane’s encounter with unforecasted severe icing conditions that were characterized by high ice accretion rates and the pilot's failure to use his command authority to depart the icing conditions in an expeditious manner, which resulted in a loss of airplane control.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA12FA115
- Event ID
- 20111220X20005
- Case number
- ERA12FA115
- 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: 596f7e4a5cf9a7812998809db4ce5cb2d1661ef33a4bd682657e08df263a3e25; retrieved 2026-09-13T22:05:33.463Z.