Socata TBM 700 accident near Dartmouth, Massachusetts, October 13, 2025
On October 13, 2025 at about 12:15 pm local time, a 2003 Socata TBM 700, registered N111RF, was substantially damaged in an accident during takeoff near Dartmouth, Massachusetts. It was a personal flight under general aviation rules (Part 91). 2 people were killed. The weather was instrument conditions (cloud, fog or low visibility).
The NTSB's probable cause their words, unchanged
The NTSB has not yet published a probable cause for this accident. Investigations usually take one to two years; this page updates when the final report is released.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- October 13, 2025 · about 12:15 pm local time · cases in 2025
- Place
- Dartmouth, Massachusetts · map
- Type
- Accident
- Injuries
- 2 people were killed.
- Weather
- instrument conditions (cloud, fog or low visibility)
- Aircraft
- Socata TBM 700, built 2003 · all TBM 700s on the register
- Registration
- N111RF · registry record · serial 259
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative preliminary · quoted from the NTSB record
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.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Loss of control in flight during takeoff defining event
The aircraft
- Seats: 7
- Landing gear: retractable
- Fire on the ground
The flight
- Departed from: EWB New Bedford MA at 12:05 pm
- Destination: Kenosha WI
- Flight plan: IFR
Weather at the time
- Light: daylight
- Wind: from 040° at 19 knots, gusting 28
- Visibility: 2.5 statute miles
- Sky: broken clouds at 900 ft
- Temperature: 55°F (13°C), dew point 54°F (12°C)
- Altimeter: 30.04 inHg
- Observation at 8:16 am from EWB, 4 miles away
Weather report (METAR): SPECI KEWB 131216Z 04019G28KT 2 1/2SM -RA BR BKN009 OVC015 13/12 A3004 RMK AO2 WND 05031/1202 SPECI KEWB 131207Z 03014G31KT 1 3/4SM R05/6000VP6000FT -RA BR BKN009 OVC015 13/12 A3003 RMK AO2 PK WND 05031/1202
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The NTSB has not released the docket for this case yet. The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), is usually released when the investigation is nearly complete, and the list here is refreshed when it appears. Check at the NTSB.
Connections how this case links to the rest of the register
- N111RF on the register today · the tail number may have moved to another aircraft since
- Daher (Socata) TBM-700 TBM 700 through TBM 960 1,008 registered today · the model family and its accident history
- New Bedford Regional · departed from
- Accidents and incidents in Massachusetts 987 since 1982 · 90 in the last ten years
- Massachusetts 2,645 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/ERA26FA011.json.
The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
