The U.S. aircraft register, updated daily
Accidents · NTSB ERA25FA230 · Final report

Mooney M20F accident near Beverly, Massachusetts, June 19, 2025

On June 19, 2025 at about 12:47 pm local time, a 1966 Mooney M20F, registered N9573M, was substantially damaged in an accident during maneuvering near Beverly, Massachusetts (Beverly Rgnl airport). It was a personal flight under general aviation rules (Part 91). 2 people were killed. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot’s failure to maintain control of the airplane while maneuvering to return to the airport which resulted in an aerodynamic stall. Contributing to the accident was the improperly installed No. 2 cylinder bottom spark plug by maintenance personnel, which came loose and resulted in an engine backfire on takeoff.

Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.

What the record shows

Date
June 19, 2025 · about 12:47 pm local time · cases in 2025
Place
Beverly, Massachusetts · Beverly Rgnl · cases near this airport · map
Type
Accident
Injuries
2 people were killed.
Weather
visual conditions (good weather)
Aircraft
Mooney M20F, built 1966 · all M20Fs on the register
Registration
N9573M · registry record · serial 670150
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

The pilot and the passenger were attempting to take off when surveillance video captured, and a witness heard, the sound of the airplane’s engine backfiring followed by a sudden decrease and increase in engine power. Dark smoke was also seen trailing under the belly of the airplane. Data downloaded from the airplane’s onboard engine monitor recorded an rpm drop from 2,600 to 1,500 rpm then back to 2,500 rpm shortly after the airplane became airborne. Fuel flow, manifold pressure, and horsepower readings uniformly tracked with the decrease/increase of rpm, consistent with the pilot quickly reducing the throttle to idle then back to full power. During the takeoff, the pilot advised the air traffic controller that the airplane was having an engine problem and that he planned to “head up and turn back.” The airplane subsequently made a right turn toward the intersecting runway shortly after the engine backfired and it’s possible the pilot reduced power in an attempt to land but changed his mind and decided to circle back to another runway. The airplane then entered a steep left turn and descended, in what a witness described as a stall-like state. The last radar return indicated the airplane was about 110 ft above the ground at a groundspeed near its published stall speed. According to data downloaded from the airplane’s engine monitor, the engine was operating near full power as the airplane descended to ground contact. Postaccident examination of the engine revealed the No. 2 cylinder bottom spark plug was loose, and stains/residue from combustion exhaust gas leakage was visible around the spark plug port consistent that it had been loose prior to the accident. Review of the airplane’s engine maintenance logbook revealed that the spark plugs were, “cleaned, gapped, tested, and rotated” at the last annual inspection, about 37 hours before the accident. There were no other entries in the engine maintenance logbook regarding removal of the spark plugs after the annual inspection. According to the engine manufacturer’s service instruction on how to install spark plugs, the spark plugs should have been torqued to a specific torque value to prevent them from coming loose. Examination of the fuel system and its components revealed evidence of water/corrosion and debris; however, testing found no indication that would have precluded fuel from reaching the engine. While the data showed that the cylinder head temperature was low on the No. 1 cylinder, there was no evidence of a stuck valve, and the ignition system tested normally. An erratic exhaust gas temperature (EGT) reading for the No. 1 cylinder was also recorded for the entire flight. The EGT data had been erratic since the engine’s last annual inspection. The No.1 cylinder’s EGT connector was found undamaged and the yellow (positive) wire for the EGT probe was not connected (the red wire was connected). As such, the probe had most likely not been working properly since the last annual inspection. Based on the available information, it is most likely that the backfiring heard coming from the engine was due to the loose No. 2 cylinder spark plug, which was not properly torqued at the last annual inspection. Despite the fact that the engine was still producing close to full power following the backfire, the pilot entered a steep turn, likely in an attempt to return to the airport, after which the airplane most likely stalled from an altitude that was too low to recover.

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

  1. Loss of control in flight during maneuvering defining event
  2. Powerplant sys/comp malf/fail during initial climb
  3. Collision with terrain or object (not controlled flight into terrain) during uncontrolled descent

The NTSB's findings

  • Aircraft › Aircraft power plant › Engine (reciprocating) › Recip eng cyl section › Failure other cases naming the engine
  • Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
  • Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Airspeed › Not attained/maintained
  • Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Angle of attack › Not attained/maintained
  • Personnel issues › Task performance › Maintenance › Installation › Maintenance personnel

Pilot

  • Certificate: commercial pilot
  • Ratings: single-engine land; instrument: airplane
  • Flight time: 429 hours in all; 77.2 in this make and model; 13.7 in the last 90 days; 0 in the last 30 days
  • Last flight review: January 8, 2025
  • Medical certificate: Class 2 (without waivers/limitations)
  • Seat: left
  • Injury: fatal

The aircraft

  • Airframe total time: 6,415 hours
  • Last inspection: annual inspection, October 11, 2024; 37 hours since
  • Maximum gross weight: 2,740 lb
  • Seats: 4
  • Landing gear: retractable
  • Engine: Lycoming IO-360-A3B6 (piston); 2,268 hours total

The flight

  • Destination: GFL Great Falls NY
  • Flight plan: IFR
  • Runway 16/3, 5,001 ft by 100 ft

Weather at the time

  • Light: daylight
  • Wind: from 260° at 6 knots
  • Visibility: 10 statute miles
  • Sky: broken clouds at 900 ft
  • Temperature: 73°F (23°C), dew point 70°F (21°C)
  • Altimeter: 29.80 inHg
  • Observation at 8:53 am from KBVY, 1 miles away

Weather report (METAR): KBVY 191253Z 26006KT 10SM BKN009 23/21 A2980

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers1

Photographs from the investigation 5 pictures from the NTSB's docket, as the NTSB released them

The NTSB's photographs with the NTSB's captions, at screen size. Open a picture to see it full size or to report one that should not be shown.

Documents from the investigation the NTSB's docket: the evidence folder behind the report

19 documents, released by the NTSB on October 16, 2026. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

#DocumentWhat it is
1 NTSB Mor - Air Traffic Controller PDF, 1 page · our copy View Download
2 NTSB Summary of Email - Witness Satement PDF, 1 page · our copy View Download
3 Investigation Photos PDF, 6 pages · our copy View Download
4 FAA Atct Report - Excerpt of Communications PDF, 1 page · our copy View Download
5 Bvy Airport Security Video video View Download
6 Ring Camera Video video View Download
7 Flight Track PDF, 1 page · our copy View Download
8 radar Data Raw File data file · our copy Download
9 NTSB Wreckage Exam Report PDF, 6 pages · our copy View Download
10 NTSB Mor - Fuel Servo and Injectors Test Report PDF, 8 pages · our copy View Download
11 Maintenance Records - Last Annual Engine PDF, 1 page · our copy View Download
12 Recorded Flight Data - Specialist's Factual Report PDF, 8 pages · our copy View Download
13 Attachment 1 to Recorded Flight Data - Specialist's Factual Report data file · our copy Download
14 Materials Laboratory Factual Report 25-064 PDF, 12 pages · our copy View Download
15 Statement of Party Representatives to NTSB Investigation PDF, 14 pages · our copy View Download
16 Release of Aircraft Wreckage, NTSB Form 6120.15 PDF, 4 pages · our copy View Download
17 Emergency Checklist PDF, 1 page · our copy View Download
18 M20F Owner's Manual Excerpt PDF, 2 pages · our copy View Download
19 Toxicological Report PDF, 1 page · our copy View Download

The same docket at the NTSB.

Connections how this case links to the rest of the register

Aircraft
Place

The whole map of how records connect · these connections as data: /graph/accident/ERA25FA230.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.