ERA21LA003 · SOCATA TBM700
SOCATA TBM700 · Accident: loss of control in flight en route
From Manchester-Boston Regional Airport (MHT) to Buffalo Niagara International Airport (BUF)
Event
- NTSB case
- ERA21LA003
- 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 TBM700
- Aircraft type
- Socata TBM700
- 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
- N965DM
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Manchester-Boston Regional Airport (MHT), Manchester, NHTo Buffalo Niagara International Airport (BUF), Buffalo, NY
- Aircraft age
- About 11 years (built 2009)
- 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 · descent
- 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
No findings designated as a cause are recorded in the NTSB data yet.
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The airplane was in cruise flight at FL280 when the instrument-rated pilot failed to contact air traffic control (ATC) following a frequency change assignment. After about 25 minutes, and when 30 miles east of the destination airport, the pilot contacted ATC on a frequency other than the one that was assigned. He requested the instrument landing system (ILS) approach at his intended destination, and the controller instructed the pilot to descend to 8,000 ft and to expect vectors for the ILS approach at the destination airport. The controller asked the pilot if everything was “okay,” to which the pilot replied, “yes sir, everything is fine.” The controller then observed the airplane initiate a descent. About 2 minutes later, the controller asked the pilot where he was headed, and the pilot provided a garbled response. The controller instructed the pilot to stop his descent at 10,000 ft, followed by an instruction to stop the descent at any altitude. The pilot did not respond, and additional attempts to contact the pilot were unsuccessful. The airplane impacted terrain in a heavily wooded area 17 miles from the destination airport. All major components of the airplane were located in the vicinity of the main wreckage. Examination of the airframe and engine revealed no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation. The investigation was unable to determine why the pilot was not in contact with ATC for 25 minutes. The pilot’s eventual contact with ATC about 30 miles from his intended destination, while still operating at his cruise altitude, suggests a clear breakdown in awareness of his position through distraction or impairment. However, upon re-establishing contact with ATC, the pilot’s communications were clear, nominal, and timely, which did not suggest impairment or use of an oxygen mask. Additionally, in response to a direct query from ATC the pilot did not indicate any difficulty. Further, there was no sign of airframe depressurization and examination of the wreckage did not reveal deployment of the passenger oxygen masks. Toxicology results were positive for ethanol at a low level, which was likely due to post-mortem production. Meteorological data and a performance study indicated that the pilot initiated a descent through multiple cloud layers about 15 seconds after acknowledging the descent clearance. During the initial portion of the airplane’s descent, its airspeed and rate of descent appeared to be nominal. About 2 minutes later, excessive airspeeds, descent rates, bank angles, and pitch attitudes were achieved. The performance study depicted the airplane entering a spiral dive during which the airplane exceeded airspeed, maneuvering, structural, and autopilot limitations. At 6,000 ft above ground level, and about 10 seconds before ground contact, the airplane descended through a final cloud layer, the descent profile shallowed, and the rate of descent decreased to 6,800 ft/min before radar data ended. In addition, there were no clearances issued by ATC that would have required the pilot to change either the airplane’s rate of descent or track about this time; however, the airplane’s proximity to the destination airport may have created a heightened sense of urgency for the pilot to descend and or configure his avionics for the approach, which may have served as an operational distraction. Although it was possible that restrictions to visibility during the descent may have affected the pilot’s ability to maintain positive airplane control, there is insufficient information to determine how or why the pilot lost control.
Probable cause
The pilot’s failure to maintain control of the airplane for undetermined reasons during the descent to the destination airport.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA21LA003
- Event ID
- 20201002102077
- Case number
- ERA21LA003
- 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: 33635abed68d1d96925668111cbd9730fda972719b78106ce809f1e98a0af347; retrieved 2026-09-15T07:20:45.722Z.