ERA26FA011 · SOCATA TBM 700
SOCATA TBM 700 · Accident: loss of control in flight during takeoff
From New Bedford Regional Airport (EWB) to Kenosha, WI
Narrative check · The NTSB narrative appears to contradict this record's injuries. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- ERA26FA011
- 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
- Ongoing
- API-reported fatalities
- 2 · all aircraft and ground
- Ground fatalities
- 0
- 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 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
- N111RF
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From New Bedford Regional Airport (EWB), New Bedford, MATo Kenosha, WI
- Aircraft age
- About 22 years (built 2003)
- 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 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
- Substantial
Cause areas
No findings designated as a cause are recorded in the NTSB data yet.
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
On October 13, 2025, at about 0815 eastern daylight time, a Socata TBM 700C2, N111RF, was substantially damaged when it was involved in an accident near Dartmouth, Massachusetts. The private pilot and the passenger were fatally injured and an automobile driver received minor injuries. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. According to preliminary air traffic control ADS-B and voice communication data provided by the Federal Aviation Administration, the pilot had filed an instrument flight rules flight plan from New Bedford Regional Airport (EWB), New Bedford, Massachusetts, to the Kenosha Regional Airport (ENW), Kenosha, Wisconsin. The airplane departed EWB at 0805, and shortly after departure, the pilot stated that he would be returning to the airport. The air traffic controller then instructed the pilot to enter a left downwind for runway 05, an instruction which the pilot confirmed. The controller then queried the pilot if he would need assistance upon landing, to which the pilot reported that he did not need assistance. The controller then cleared the pilot to land on runway 05. The controller next asked the pilot whether he could perform an approach to the airport and reported that the ceilings were around 1,000 ft, or if he would need radar vectors. The pilot responded that he would descend and that he “should be OK.” The controller acknowledged the pilot and cleared him again to land on runway 05. About one minute later, the controller provided the pilot with a low altitude alert and the altimeter setting that was current at the time. The pilot confirmed the altimeter setting. Shortly after, the pilot made an unintelligible exclamation. There were no further communications from the pilot. The accident site was located about 3.6 nautical miles southwest of EWB. Several trees that were impact-damaged were identified as the initial impact points. The trees had the tops cut off approximately 50 feet above the ground. The wreckage path continued through a wooded area, across a highway off ramp, across a portion of Interstate 195 West, and the fuselage came to rest in the median between Interstate 195 West and Interstate 195 East. During the impact sequence, the airplane impacted an automobile that was traveling on Interstate 195 West and the driver received minor injuries. The distance from the initial impact point to where the fuselage came to rest was about 280 ft. The debris path was oriented along a heading of 223° true, and the fuselage came to rest oriented on a heading of 289° true. A post-impact fire consumed portions of both wings and the empennage. All of the major components of the airplane were located at the accident site. Both wings were impact damaged, and portions of both wings had been partially consumed by a post-impact fire. The left aileron was located along the wreckage path and the aileron trim tab remained attached. The rudder sustained significant impact damage to the leading edge, and a portion of the rudder had broken free from the rest of the rudder. The rudder trim tab remained attached to the rudder through its hinge; however, the rudder trim actuator had separated from the rudder trim tab; the damage was consistent with impact. The elevator trim tab remained partially attached to the elevator through the trim tab actuator and the trim tab and both elevators were impact and thermally-damaged. The wing fuel tanks were breached, and no fuel was recovered from the remnants of the fuel tanks; however, there was a strong odor consistent with Jet A fuel noted around the accident site. The fuel strainer bowl and screen remained secured, and there were no signs of fuel leaks. The bowl was removed, and the screen was clear of obstructions. The fuel contamination indicator was in its normal position. The fuel line connecting the fuel outlet at the firewall to the fuel pump inlet was secure and there were no signs of fuel leaks. The fuselage was the furthest piece of wreckage observed along the wreckage path and remained mostly intact; however, the fuselage structure was buckled in multiple locations, and there was a small portion of thermal damage to the forward left side of the fuselage. A portion of the left wing root remained attached to the fuselage, the right wing had completely impact-separated from the fuselage. The main cabin door was found open when the investigators arrived; however, a witness video that was taken after the accident showed that the cabin door was closed immediately after the accident. Both forward seats had impact-separated from their installation points and remained within the cabin area. The airplane was equipped with a digital avionics suite. Both the pilot and copilot primary flight displays (PFD) remained installed, and the electrical connectors remained secured. Both flight displays were recovered and retained for data download. The engine remained partially attached to the airframe through the engine mounts, cables, wires, and hoses. The engine displayed some impact damage signatures and there were no signs of fire. The five blade, constant speed, composite propeller sustained impact damage to all five blades. The propeller blade hub remained attached to the propeller flange. All five of the propeller blades had separated from the propeller hub near their roots, and all of the propeller blades were located along the wreckage path. The blades displayed varying amounts of leading-edge damage. The wreckage was retained for further examination.
Verbatim NTSB factual narrative from the NTSB dataset
Sources
NTSB record ERA26FA011
- Event ID
- 20251013201836
- Case number
- ERA26FA011
- 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: ad872a53a4a65c8e71cb90223643c47fade928fe5f0a93328e328735af041c98; retrieved 2026-09-15T09:09:57.213Z.