Monday, August 25, 2025

Pitts S-1T Special, N51HC, fatal accident occurred on August 12, 2025, near Goodyear, Arizona

  • Location: Goodyear, AZ 
  • Accident Number: WPR25FA253 
  • Date & Time: August 12, 2025, 10:19 Local 
  • Registration: N51HC 
  • Aircraft: Pitts S-1T 
  • Injuries: 1 Fatal 
  • Flight Conducted Under: Part 91: General aviation - Personal
https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/200772/pdf

https://registry.faa.gov/AircraftInquiry/Search/NNumberResult?nNumberTxt=N51HC

On August 12, 2025, about 1019 mountain standard time, a Pitts S-1T, N51HC, was substantially damaged when it was involved in an accident near Goodyear, Arizona. The pilot was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations (CFR) Part 91 personal flight.

The pilot did not make radio contact with the air traffic control tower, nor was there any evidence he was in radio contact with anyone prior to or during the accident flight. There was no automatic dependent surveillance-broadcast (ADS-B) data for the accident flight. Recorded radar data from the Federal Aviation Administration (FAA) revealed a primary target that started near the airplane’s known departure point at 1014:47 and ended near the accident site at 1019:37. The flight track was consistent with the airplane departing from Goodyear and flying south. At 1019:23, the last 14 seconds of data was consistent with the airplane progressively increasing its bank angle in a left turn, that was also consistent with a spiral (see figure 1 below). There was no altitude data.


Investigators compiled a comparison of the airplane’s past ADS-B data and the radar primaries from the accident flight. When the pilot flew aerobatics, he appeared to regularly fly south to the aerobatic box whose track was similar in appearance to that of the accident flight track. Additionally, there were several occasions where the first maneuver was a sharp left turn, also similar to the last radar returns. (see figures 2 and 3 below).


A witness stated that on the morning of the accident he was driving down to his hangar when he observed the pilot taxiing the airplane at an unusually fast speed directly in front of his truck. He noted that the pilot was not wearing a headset and the long red “remove before flight” cover was installed on the pitot tube. The pilot’s spouse was running after the airplane and appeared very distressed. She asked the witness to help stop the pilot’s flight, explaining that he was on medication and should not be flying an airplane. He then witnessed the airplane exit the hangar area and make a sharp left 180° turn onto Taxiway Alpha. Immediately thereafter, the airplane sounded as though the pilot applied full power and he witnessed the airplane depart from the taxiway within a few hundred feet, briefly contacting the dirt between the taxiway and runway. A review of the airport security cameras located near the air traffic control tower confirmed the witness's observation of the departure sequence from the taxiway (see figure 3 below).


The pilot’s spouse stated that she and the pilot had taken an approximate month-long European vacation and returned on June 14. After the return, he could not sleep which they first attributed to jet lag. After a week without improvement, he sought medical care, but was limited to the medication he could be prescribed due to the Federal Aviation regulations. Despite his attempts, he continued to suffer from severe insomnia and visited the emergency room on two separate occasions. He had to take medical leave from his airline employment and the lack of sleep produced visible effects. She estimated he only received a few hours of sleep per night since they came back from their trip. He had appointments to see specialists and undergo a sleep study a few days after the accident. He had obtained a new medication the day before that accident and was finally able to sleep for 5 hours on the evening before the accident. 

The spouse further stated that on the day of the accident, they planned to pick up documentation for the airline disability request from his primary care physician, who was located near the Goodyear airport. After getting the paperwork, they went to the airport because the pilot wanted to charge the airplane’s battery since it had been inactive for a long duration of time. He first suggested they get coffee while they waited but after a short time, he said he needed to run the engine for five minutes, which they could not do while it was inside the hangar. They moved the airplane outside and after getting inside, he started the engine. The spouse stated that she brought the pilot a bottle of water and became worried because she noticed that he had his lap belt fastened. The pilot handed her back the water and said goodbye. Thereafter, he began to taxi toward the runway, and she ran after him, yelling that he should not be flying.

The accident site was located in level desert terrain composed of soft sand with sporadic desert shrubs. The site was about 10 nautical miles south of the Goodyear Airport and about 4 nautical miles west of the Sierra Estrella Mountains. The elevation was approximately 1,150 feet mean sea level (msl).

The wreckage distribution measured approximately 100 feet and was oriented on a measured magnetic bearing of about 210°. The first identified point of contact was a circular ground crater about 3 ft deep. The engine was located inside the crater in an inverted attitude and exhibited a large hole in the lower crankcase. The propeller hub remained attached to the crankshaft; fractured propeller blades and blade-tip pieces were distributed around the immediate crater area. The main wreckage was near the crater, and the tail section was folded forward over the fuselage in a scorpion-like configuration. The airplane sustained major crush damage and fragmentation, precluding investigators from confirming control continuity.

Cessna 172P Skyhawk, N62296, accident occurred on August 1, 2025, near Gainesville Municipal Airport (GLE/KGLE), Gainesville, Texas

  • Location: Gainesville, TX 
  • Accident Number: CEN25LA300 
  • Date & Time: August 1, 2025, 08:02 Local 
  • Registration: N62296 
  • Aircraft: Cessna 172P 
  • Injuries: 2 None 
  • Flight Conducted Under: Part 91: General aviation - Instructional
https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/200691/pdf

https://registry.faa.gov/AircraftInquiry/Search/NNumberResult?nNumberTxt=N62296

On August 1, 2025, about 0802 central daylight time, a Cessna 172P airplane, N62296, was substantially damaged during an accident near Gainesville, Texas. The flight instructor and pilot-receiving-instruction were not injured. The airplane was operated as a Title 14 Code of Federal Regulations (CFR) Part 91 instructional flight.

The flight instructor reported that the airplane had a sudden loss of engine power during initial climb from runway 36 at Gainesville Municipal Airport (GLE), Gainesville, Texas. The flight instructor estimated that the loss of engine power occurred 250-300 feet above ground level (agl). The engine tachometer indicated about 2,000 rpm after the loss of engine power. The flight instructor took control of the airplane from the pilot-receiving-instruction and determined that landing at the airport was not feasible due to the airplane’s low altitude at the time. The pilot-receiving-instruction was unable to restart the engine by cranking the engine starter after verifying that the fuel selector was on and the mixture control was full-rich. Before the offairport forced landing, the pilot-receiving-instruction moved the fuel selector handle to OFF, and the flight instructor pulled the mixture control to idle cutoff. The forced landing was in a wheat field north of the airport. The airplane subsequently nosed over when the nosewheel dug into the muddy terrain. After the accident, the flight instructor and pilot-receiving-instruction were able to release their restraints and exit the inverted airplane without injury.

According to fueling documentation, the airplane was serviced with 9.95 gallons of fuel at GLE before the flight. The flight instructor indicated that the airplane had about 40 gallons of fuel onboard at engine startup.

A Federal Aviation Administration (FAA) Airworthiness Inspector examined the airplane at the accident site. The airplane had been sitting inverted several days before it was recovered to an upright position. As such, the airplane fuel tanks were void of usable fuel when examined. Engine control continuity was confirmed from the cockpit to the carburetor and the carburetor heat control. Engine crankshaft continuity was confirmed by rotating the propeller. There was no evidence of damage to the crankcase or cylinders, and there was no evidence of an oil leak. The airplane wreckage was transported to a secure storage facility where additional examinations will be conducted.

At 0805, the Automated Weather Observing Station (AWOS) at GLE reported a clear sky, 10 sm visibility, temperature 23° C, dewpoint 23° C, calm wind, and an altimeter setting of 30.18 inches-of-mercury.

According to a carburetor icing probability chart contained in FAA Special Airworthiness Information Bulletin CE-09-35, entitled "Carburetor Icing Prevention", the recorded temperature and dew point about the time of the accident were conducive to the formation of carburetor icing at a descent engine power setting. The bulletin states that if ice forms in the carburetor of a fixed-pitch propeller aircraft, the restriction to the induction airflow will result in decreased power output and a drop in engine rpm, which might be accompanied or followed by a rough running engine. The bulletin also states that pilots should respond to carburetor icing by applying full carburetor heat immediately and that the engine may run rough initially for a short time while the ice melts. The bulletin further states that that pilots should use carburetor heat when operating the engine at low power settings or while in weather conditions in which carburetor icing is probable.

Air Tractor AT-301, N23069, accident occurred on August 6, 2025, near Davenport, North Dakota

  • Location: Davenport, ND 
  • Accident Number: CEN25LA306 
  • Date & Time: August 6, 2025, 20:35 Local 
  • Registration: N23069 
  • Aircraft: AIR TRACTOR INC AT-301 
  • Injuries: 1 Serious 
  • Flight Conducted Under: Part 137: Agricultural

https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/200731/pdf

https://registry.faa.gov/AircraftInquiry/Search/NNumberResult?nNumberTxt=N23069

On August 6, 2025, at 2035 central daylight time, an Air Tractor Inc AT-301 airplane, N23069, was substantially damaged when it was involved in an accident near Davenport, North Dakota. The commercial pilot sustained serious injuries. The airplane was operated under Title 14 Code of Federal Regulations Part 137 as an aerial application flight.

The pilot stated that the flight proceeded as expected, and he completed the aerial application successfully. During the return climb to approximately 500 ft above ground level, he noticed the left fuel tank was low and switched fuel gauge indications to the left fuel tank. Shortly afterwards, the low fuel light illuminated, and the airplane experienced a loss of engine power. He immediately actuated the wobble pump and attempted to restore fuel flow manually, but the engine did not respond. As the airplane began to lose altitude, he prepared for and performed a forced landing in a nearby cornfield. The airplane sustained substantial damage to the wings and fuselage during the forced landing.

The airplane was retained for further examination.

Friday, August 22, 2025

Cessna A185F Skywagon, N714HE, fatal accident occurred on August 22, 2025, at Bangor International Airport (BGR/KBGR), Bangor, Maine

This is preliminary information, subject to change, and may contain errors. Any errors in this report will be corrected when the final report has been completed.

https://registry.faa.gov/AircraftInquiry/Search/NNumberResult?nNumberTxt=N714HE

Southern Aircraft Consultancy Inc Trustee

- History of Flight:

On August 22, 2025, at about 1322 local time, a Cessna A185F Skywagon, N714HE, registered to Southern Aircraft Consultancy Inc Trustee out of Bergh Apton Norfolk, England, was substantially damaged when it was involved in an accident at Bangor International Airport (BGR/KBGR), Bangor, Maine. The pilot was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 ferry flight.

According to flight track history, the airplane was ferried through several countries in Europe since the start of August, 2025. On August 21, 2025, the airplane arrived at Goose Bay, Canada, following a flight from Narsarsuaq, Greenland.

According to preliminary automatic dependent surveillance-broadcast (ADS-B) data, at about 0921 LT, the airplane departed Goose Bay Airport (YYR/CYYR), Newfoundland and Labrador, Canada, and climbed to an inflight cruising altitude of 8,000 ft, heading southwest. It is currently unknown if Bangor was the intended destination.

At 1249:53, the airplane started a descent towards Bangor, Maine. At 1217:17, the airplane was at 1,700 ft and 108 knots groundspeed when it entered a left hand turn towards the airport. At 1218:43, the airplane was at 1,000 ft, 74 knots groundspeed, when it conducted another left hand turn as it was on final approach to runway 33. At 1220:02, the airplane reached runway 33. At roughly 1220:28, the airplane touched down about 3000 ft down the runway. At 1220:49, the last ADS-B return was recorded about 4,800 ft down the runway and on the centerline. The last reported groundspeed value was 62 knots.

According to several news outlets, the aircraft crashed on takeoff at 1330. However, I was able to find a 47-second video showing the entire accident sequence.

The video was captured by an amateur witness from the ramp. The airplane was flying over the runway and preparing to touch down. About 25 seconds into the video, the airplane touched down, but appeared unstable and not on the centerline as is approached the left side of the runway. About 34 seconds into the video, the left wing began scrapping the left side of the runway. The airplane exited the runway, and the left wing was still dragging the ground. About 40 seconds into the video, the airplane pulled up to the left, and appeared slow and struggling to maintain airspeed/altitude. A few seconds later, the left wing dropped and contacted the ground, followed by the cockpit and right wing.

The total flight time was five hours.

Accident Video

- Pilot Information:
unknown

- Aircraft Information:
The accident aircraft, serial number 18504396, was manufactured in 1982. It was powered by a Continental IO-520D engine.

According to the Pilot Operating Handbook (POH):

Stall Speeds
FlapsUp,PowerOff - 65 mph
Flaps Down, Power Off -56 mph

Section 1-7, Balked Landing procedure:
(1) Power -- FULL THROTTLE and 2850 RPM
(2) Wing Flaps -- RETRACT TO 20°.
(3) Airspeed -- 80 MPH
(4) Wing Flaps -- RETRACT slowly.
(5) Cowl Flaps -- OPEN.

In a balked landing (go-around) climb, the wing flap setting should be reduced to 20° immediately after full power is applied. After all obstacles are cleared and a safe altitude and airspeed are obtained, the wing flaps should be retracted and the cowl flaps opened.

- Wreckage and Impact Information:
The airplane came to rest upright and there was no post crash fire. All four corners of the aircraft were present at the accident, and there was little to no debris path leading to the main wreckage. The airplane impacted terrain in a left wing low first, followed by the nose/cockpit and right wing. The left wing was impact damaged and separated. The nose section sustained extensive impact damage. The right wing sustained leading edge impact damage and remained attached to the airframe. The tail remained attached to the airframe and sustained little to no damage. The impact appears consistent with a low altitude aerodynamic stall/spin entry with little to no forward airspeed.


- Airport Information:
Bangor International Airport is a public airport located about 3 miles west of Bangor, Maine. The airport field elevation was 192.1 ft. The airport features a single asphalt/grooved runway 15/33 that is 11440 x 200 ft.

- Weather:
The reported weather at KBGR, at 1253 (about 30 minutes before the accident) included: wind 350° at 10 knots, gusting 18 knots, 10 statute miles visibility, a scattered ceiling at 7000 ft above ground level (agl), a temperature of 25° C, a dew point of 9° C, and a barometric altimeter setting of 29.95 inches of mercury.

The reported weather at KBGR, at 1339 (about 17 minutes after the accident) included: wind 010° at 9 knots, gusting 19 knots, 10 statute miles visibility, a scattered ceiling at 7000 ft above ground level (agl), a temperature of 26° C, a dew point of 8° C, and a barometric altimeter setting of 29.95 inches of mercury.

The calculated density altitude was 1395 ft and 1514 ft respectively.

- Additional Information:
no

Embraer ERJ-170-100LR, N879RW, incident occurred on May 1, 2025, near Ronald Reagan National Airport (DCA/KDCA), Washington, DCA

  • Location: Washington, DC 
  • Incident Number: OPS25LA034 
  • Date & Time: May 1, 2025, 14:33 Local 
  • Registration: N879RW (A2); UNREG (A3) 
  • Aircraft: Embraer ERJ 170-100 LR (A2); Sikorsky UH60 (A3) 
  • Injuries: N/A (A2); N/A (A3) 
  • Flight Conducted Under: Part 121: Air carrier - Scheduled (A2); Armed Forces (A3)
https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/200095/pdf

On May 1, 2025, about 1433 eastern daylight time (EDT), Priority Air Transport flight 23 (PAT23), (tail number forthcoming), a UH-60 Blackhawk helicopter landing at the Pentagon Heliport (JPN), and Republic Airways flight 5825 (RPA5825), an Embraer 170, N879RW, on approach for landing Ronald Reagan Washington National Airport (DCA), Arlington, Virginia, were involved in a loss of separation approximately 1.7 miles north-northwest of DCA. PAT23 was operating as a title 14 Code of Federal Regulations (CFR) Part 91 military flight, and RPA5825 was operating as a title 14 CFR Part 121 scheduled passenger flight. According to the FAA, the closest proximity between PAT23 and RPA5825 was 0.4 miles laterally and 200 feet vertically.

The DCA Airport Traffic Control Tower (ATCT) local control (LC) controller was providing services to both involved aircraft when the loss of separation occurred. At the time of the incident there were five positions open in the tower: LC, assistant LC (ALC), ground control (GC), clearance delivery (CD) / flight data (FD), and operations supervisor (OS). Four CPCs (Certified Professional Controllers), one trainee and one OS were on position. The LC position, which was the position involved with training in progress, was combined with the helicopter control (HC) position. The operations manager (OM) had authorized the HC and LC positions to be combined for training. An OS was providing direct supervision. There was one CPC, one OS, and one OS in training (IT) available, with three CPCs and one trainee performing other duties.

Surveillance data provided by the Federal Aviation Administration (FAA) indicated that PAT23 was inbound to JPN from the southwest via helicopter route 5, Pentagon transition. There were three fixed wing aircraft inbound to runway 19 at DCA. These were (in order): PSA Airlines flight 5073 (JIA5073); Delta Air Lines flight 1671 (DAL1671); and RPA5825.

At about 1421 EDT, PAT23 contacted the DCA ATCT LC controller over Springfield and requested to fly helicopter route 5 to the Pentagon. The controller provided the current DCA altimeter setting, radar identified them and advised them of helicopter traffic transiting westbound at 1,200 feet through helicopter zones 5 and 6. The crew acknowledged and advised they were looking for traffic.

At about 1423 EDT, the DCA ATCT LC controller instructed PAT23 to hold three miles west of DCA. The crew acknowledged and read back the holding instructions.

At about 1424 EDT, the DCA ATCT LC controller instructed PAT23 to proceed to the Glebe Road intersection and hold. The crew acknowledged and read back the instructions.

At about 1425 EDT, JIA5073 checked in with the DCA ATCT LC controller on the River Visual Approach to runway 19. The LC controller issued the winds and cleared JIA5073 to land runway 19.

Also, about this time, the DCA ATCT ALC controller coordinated with Potomac Terminal Radar Approach Control (PCT TRACON) to ask for extended spacing between JIA5073 and RPA5825 that was next in sequence for runway 19. The PCT TRACON radar controller confirmed they would give them some space.

[Between 1425 and 1428 EDT, PCT TRACON had sequenced DAL1671 into the extended spacing that they had advised DCA ATCT they would provide so that DCA ATCT could get PAT23 into JPN.]

At about 1428 EDT, the DCA ATCT LC controller instructed PAT23 to proceed to the Pentagon via helicopter route 5. The crew acknowledged and read back the instructions.

At about 1429 EDT, DAL1671 checked in with the DCA ATCT LC controller on the Area Navigation (RNAV) Zulu approach to runway 19. The LC controller issued the winds, advised of traffic holding in position and cleared them to land runway 19.

Also, about this time, PAT23 reported Glebe Road. The DCA ATCT LC controller acknowledged.

At about 1431 EDT, the DCA ATCT LC controller instructed PAT23 to report landing assured. The crew acknowledged and said “will do.”

Immediately after the response from PAT23, the DCA ATCT LC controller instructed DAL1671 to go around, to climb and maintain 3,000 feet, and to turn right heading 280°. The crew acknowledged and read back the instructions. At the same time, the DCA ATCT ALC controller immediately began coordinating the go around with PCT TRACON.

Exact times have not yet been determined from the Department of Defense audio, but around this time, PAT23 had checked in with the JPN Heliport Tower (HT) LC controller and was attempting to land on the helipad without a landing clearance. When the JPN HT LC controller queried the crew to ask who had cleared them to land, the crew advised they were executing a go around and that DCA ATCT had cleared them to the helipad.

At about 1432 EDT, RPA5825 checked in with the DCA ATCT LC controller inbound on the River Visual Approach to runway 19. The LC controller issued the winds, advised of traffic that would be holding in position and cleared them to land runway 19.

At about 1433 EDT, the DCA ATCT LC controller asked PAT23 if they were landing assured, and the crew advised they were landing assured. Simultaneously, according to information provided in post-incident interviews, the DCA ATCT LC saw PAT23 climb back up above the Pentagon building and immediately issued a go around to RPA5825 and instructed them to climb and maintain 3,000 feet and turn right heading 250°. The crew of RPA5825 acknowledged the go around, and read back the instructions, however separation had already been lost.

Figure 1 is an overhead view of the flight tracks of both RPA5825 and PAT23 and indicates their approximate location at the point of closest proximity.


Upon initial notification, the NTSB requested additional data from both the FAA and the Department of Defense (DOD). After receiving and conducting a review of this preliminary data, the NTSB formed an ATC investigative group and parties to the investigation include the FAA, the National Air Traffic Controllers Association (NATCA), and the United States Army.

Automatic Dependent Surveillance – Broadcast (ADS-B) data, audio recordings, and other pertinent data and documentation were obtained from the FAA. These data are currently being analyzed by the NTSB.

During the week of June 15th, 2025, the ATC investigative group conducted an on-site investigation and interviewed personnel at both DCA ATCT and JPN HT, the ATC facilities that had provided services to RPA5825 and PAT23 at the time of the incident. The group conducted interviews with controllers and also met with technical operations personnel responsible for communications installation and maintenance at both facilities. All information gathered confirmed that there had been no known or documented loss of communication at any time between JPN HT and PAT23, and that there had been no replacement or movement of any communication equipment since the event, and that information previously released regarding the potential loss of communications had been erroneous.

Aero Vodochody L-39C Albatros, N339L, fatal accident occurred on July 21, 2025, near Granite Falls Municipal Airport (KGDB), Granite Falls, Minnesota

Aviation Accident Preliminary Report - National Transportation Safety Board

The National Transportation Safety Board travelled to the scene of this accident.

Investigator In Charge (IIC): Fox, Andrew

Additional Participating Entities:

William G. Muller; Federal Aviation Administration - Minneapolis FSDO; Minneapolis, MN

Daniel L. Sindt; Federal Aviation Administration - Minneapolis FSDO; Minneapolis, MN

https://registry.faa.gov/AircraftInquiry/Search/NNumberResult?nNumberTxt=N339L

L39 Aircraft LLC

  • Location: Granite Falls, MN
  • Accident Number: CEN25FA269 
  • Date & Time: July 21, 2025, 17:28 Local 
  • Registration: N339L 
  • Aircraft: Aero Vodochody L-39C 
  • Injuries: 1 Fatal, 1 Serious 
  • Flight Conducted Under: Part 91: General aviation - Instructional 

https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/200598/pdf

On July 21, 2025, about 1728 central daylight time, an Aero Vodochody L-39C airplane, N339L, was substantially damaged during an accident near Granite Falls, Minnesota. The flight instructor, seated in the front seat, sustained serious injuries after ejecting from the airplane. The pilot-receiving-instruction, seated in the rear seat, did not eject from the airplane and was fatally injured when the airplane impacted terrain. The airplane was operated as a Title 14 Code of Federal Regulations (CFR) Part 91 instructional flight.

The flight instructor stated that the pilot-receiving-instruction was interested in purchasing an Aero Vodochody L-39 airplane and was receiving initial “familiarization” flight training. The airplane operator, L39 Aircraft LLC, held a Federal Aviation Administration (FAA) Letter of Deviation Authority (LODA) that authorized initial flight training, unusual attitude and upset training, formation flight training, instrument competency, and biennial flight reviews in the experimental category Aero Vodochody L-39C high-performance jet trainer airplane.

The flight instructor held an airline transport pilot certificate with type ratings for Boeing 777, Airbus 320, McDonnell Douglas DC-9, Bombardier Canadair Regional Jet CL-65, Saab 340, Embraer 500, Embraer 505, SIAI-Marchetti S.211, and Aero Vodochody L-39 airplanes. The flight instructor reported having flown about 50 hours in an Aero Vodochody L-39 airplane.

The pilot-receiving-instruction held a private pilot certificate with airplane single-engine land and instrument airplane ratings. Additionally, the pilot-receiving-instruction held a type rating for a Cirrus SF-50 airplane. The pilot-receiving-instruction had no previous flight experience in an Aero Vodochody L-39C airplane before the day of the accident.

On July 20, 2025, the flight instructor provided about 1 hour of ground instruction to the pilot-receiving-instruction during which they discussed the operation limitations of the Aero Vodochody L-39C airplane and the use of the VS-1 BRI ejection seat system. The ground instruction was conducted at the pilot-receiving-instruction’s residence (not in the airplane).

On July 21, 2025, the flight instructor provided 2-3 hours of additional ground instruction to the pilot-receiving-instruction during which they discussed the positive and negative aspects of owning/operating an experimental category warbird jet. Additionally, they discussed flight planning, normal flight operations, use of helmet oxygen, weather considerations, and the fuel planning for the Aero Vodochody L-39C airplane. The flight instructor then demonstrated a preflight of the airplane before he assisted the pilot-receiving-instruction into the airplane’s rear seat and its associated parachute harness.

The flight instructor stated that he intended to provide flight instruction during three flight legs to reposition the airplane from its normal base-of-operations at Alpine Airport (46U), Alpine, Wyoming, to Wittman Regional Airport (OSH), Oshkosh, Wisconsin, where they would attend the 2025 Experimental Aircraft Association (EAA) AirVenture event.

The flight instructor was the pilot-in-command and was seated in the front seat of the airplane. The flight instructor noted that the pilot-receiving-instruction was seated in the rear seat because he was unfamiliar with the airplane. All takeoff and landings were flown by the flight instructor.

The flight instructor stated that the first two flight legs, 46U to Northeast Wyoming Regional Airport (GCC), Gillette, Wyoming, and GCC to Watertown Regional Airport (ATY), Watertown, South Dakota, were uneventful. The accident occurred during the third flight leg from ATY to OSH. The flight instructor noted that he filed an instrument flight rules (IFR) flight plan from ATY to Fond Du Lac County Airport (FLD), Fond Du Lac, Wisconsin, but intended to cancel the instrument flight plan while enroute and proceed under visual flight rules (VFR) to OSH via the published warbird arrival procedure associated with the EAA AirVenture event.

According to ADS-B flight data, at 1707:16, the airplane was on initial climb from runway 12 at ATY. The airplane then continued eastbound as it climbed toward flight level 270 (FL270). The flight instructor reported that the airplane’s engine power was set at 103% during the continuous climb yielding 280 knots true airspeed. As the airplane climbed through flight level 200 (FL200) the flight instructor and the pilot-receiving-instruction simultaneously smelled an odor emitted from inside their helmet oxygen masks followed by smoke intrusion into the cockpit. About 4-5 seconds later the aircraft shook briefly in conjunction with an audible metal-to-metal grinding noise. The flight instructor depressurized the airplane which resolved the odor issue and the smoke dissipated from the cockpit. He then began decelerating the airplane toward best glide airspeed (140 knots) and located the nearest airport using the airplane’s Garmin navigational/communication device. The flight instructor attempted to restart the engine using the auxiliary power unit (SAFIR air-turbine system) which is normally used to start the engine. After three unsuccessful attempts to restart the engine using the SAFIR system the flight instructor shifted his focus to flying the airplane towards an airport where a forced landing could be completed.

According to ADS-B flight data, at 1718:05, the airplane entered a descent from about 21,800 ft mean sea level (msl), as depicted in figures 1 and 2. At 1718:09, the flight instructor told the air traffic controller that the airplane had an “engine failure.” The controller acknowledged the loss of engine power and cleared the flight to descend to maintain 10,000 ft msl. At 1718:36, the controller told the flight instructor that Granite Falls Municipal Airport (GDB), Granite Falls, Minnesota, was at the 1 o’clock position and 20 nautical miles (nm) and that Montevideo-Chippewa County Airport (MVE) was at the 10 o’clock position and 15 nm. The flight instructor was subsequently told to change ATC frequencies.

At 1719:53, the flight instructor established contact with a different controller, reiterated that the airplane had an engine failure, and that they were heading direct to GDB for an “emergency landing.” After a brief discussion, the flight instructor told the controller that he intended to fly a visual approach to GDB. At 1720:34, the controller told the flight instructor that GDB was at the 12 o’clock position and 10 nm and asked the flight instructor to report when the airport was in sight. At 1721:00, the controller cleared the flight direct to GDB and descend to maintain 3,000 ft msl.

According to ADS-B flight data, at 1722:35, the airplane descended below 12,500 ft msl as it continued east-southeast toward GDB, as depicted in figure 3. At 1724:09, the flight instructor told the controller that they were attempting to land at Southwest Minnesota Regional Airport (MML), Marshall, Minnesota. The flight instructor cleared the flight direct to MML and descend to maintain 3,000 ft msl. However, at 1725:24, the flight instructor told the controller that they could not reach MML and that they would land at GDB. The controller then cleared the flight direct to GDB. When interviewed after the accident, the flight instructor stated that the airplane’s ground speed decreased significantly while flying toward MML and that was why he decided to resume a flight path toward GDB instead of MML.

Based on ADS-B flight track data, the airplane continued a right descending turn over GDB, as depicted in figure 3. At 1727:48, the airplane crossed over GDB as it descended through 3,000 ft msl. According to available weather data for GDB, there was a 1,200 ft above ground level (agl) broken ceiling at the time of the accident. At 1728:14, the airplane descended below 1,200 ft agl and the airplane’s right roll angle increased in a turn toward runway 15 at GDB. When interviewed after the accident, the flight instructor stated that he saw the yellow chevrons depicting the overrun for runway 15 at GDB and turned the airplane to head directly to the end-of-pavement.

The flight instructor extended the landing gear during the right descending turn toward runway 15. However, during the turn, the flight instructor determined that the airplane would not reach the runway and told the pilot-receiving-instruction to “prepare to eject.” The pilot-receiving-instruction reportedly replied “okay.” The flight instructor stated he brought the airplane into a wings level attitude and reduced the descent rate before he told the pilot-receiving-instruction to “eject.” When he did not hear the rear seat eject from the airplane, the flight instructor again told the pilot-receiving-instruction, using his first name this time, to “eject.” The flight instructor again did not hear the rear seat eject from the airplane. According to the flight instructor, the airplane was nearing the bottom of the ejection envelope and heading toward a power line when he said “eject” for a third time before he activated his own ejection seat. The front seat was ejected from the airplane and the flight instructor subsequently descended under an open parachute canopy to the surface. The flight instructor sustained non-life-threatening serious injuries during the seat ejection and parachute landing.

Figure 1. Plots of airplane altitude, ground speed, true airspeed, calibrated airspeed, and vertical speed.
Figure 2. Plots of airplane heading, roll angle, and flight path angle

Based on the wreckage debris path, the upper portion of the airplane’s vertical stabilizer clipped a power line about 821 ft short of the runway 15 overrun (end-of-pavement). Based on the wreckage distribution, the airplane descended beneath the power line before it impacted a berm adjacent to railroad tracks that run parallel to Minnesota State Highway 23. The impact with the berm was about 590 ft short of the end-of-pavement and about 105 ft right of the runway 15 extended centerline. The airplane’s ground track was about 150° true between the power line and berm. The entire fuselage separated from the wing when the airplane impacted the berm. The fuselage came to rest upright about 45 ft past the berm and was rotated about 70° counterclockwise relative to the airplane’s flight path before it impacted the berm.

There was a strong smell of Jet-A fuel around the accident site and fuel was observed pouring from impact penetrations on the wing tip fuel tanks, and fractured fuselage fuel lines during recovery. The drop pod fuel tanks were separated during the impact with the berm. Both drop pod fuel tanks had impact penetrations. A small amount of residual fuel remained in one of the pods.

The airplane nose and cockpit sustained heavy impact crushing deformation. The front canopy was found intact along the railroad tracks and between the power lines and the berm that the airplane impacted. Portions of the fragmented rear canopy were found throughout the debris field past the berm that the airplane impacted. The pilot-receiving-instruction was found restrained in the rear ejection seat that separated from the airframe during the ground impact sequence. Based on the damage to the ejection seat and its unused firing mechanism components (first stage telescopic ejection mechanism and second stage accelerating rocket motor) the Yellow Medicine County Sheriff requested bomb-squad assistance from the Bloomington Police Department, Bloomington, Minnesota, and the 148th Fighter Wing of the Minnesota Air National Guard, based in Duluth, Minnesota, to safely separate the pilot-receiving-instruction from the damaged rear ejection seat. After the pilot-receiving-instruction was separated from the seat, the bomb-squad personnel rendered the seat safe by a controlled detonation of Composition 4 (C4) plastic explosive.

The engine bay, located in the aft section of the fuselage, remained mostly intact. The Ivchenko model AI-25TL turbofan engine, serial number 9052524100057, remained mounted in the engine bay. The engine cases/bypass ducts were intact and there were no indications of radial uncontainment or undercowl fire, as shown in figures 4 and 5. The inlet guide vanes (IGV) and visible compressor blades were all complete and in good condition. There was organic debris, including small pieces of leaves and dirt collected at the 6 o’clock position of the inlet. There was a stick wedged between the IGVs and the 1st stage compressor blades at the 11 o’clock position, as shown in figures 6 and 7. The compressor/low pressure spool was seized and could not be rotated by hand, or when pressure was applied with a pry bar. During the attempt to rotate the compressor rotor blades, there was a small amount of low pressure turbine (LPT) rotor movement observed through the engine exhaust. The engine oil tank mounted on the compressor case at the 3 o’clock position had impact damage on the forward face. Oil was visible in the tank sight glass and no case penetrations or oil leakage was noted. An external engine air duct on the compressor case had crushing damage at the 12 o’clock position near the inlet. The turbine case bypass duct had impact deformations between the 9 and 10 o’clock positions at the aft flange.

The LPT 1st and 2nd stage rotor blades and nozzle vanes exhibited thermal damage and were partially consumed. The LPT 2nd stage blades visible were consumed to 1/3 span and the LPT 2nd stage nozzle vanes were consumed from the inner diameter platform to 1/2 span, as shown in figure 8. Metal debris was collected at the 6 o’clock position in the exhaust case aft of the LPT, axially in line with the case struts. The exhaust gas temperature (EGT) thermocouples were intact and appeared undamaged.

The airplane wreckage was recovered from the accident site to a secure location where additional examinations will be completed.

Figure 7. Inlet Guide Vanes, Axial Compressor

Beechcraft 95-B55 Baron, N8796R, fatal accident occurred on July 26, 2025, near Pacific Grove, California

  • Location: Pacific Grove, CA
  • Accident Number: WPR25FA224 
  • Date & Time: July 26, 2025, 22:37 Local 
  • Registration: N8796R 
  • Aircraft: Beech 95-B55 (T42A) 
  • Injuries: 3 Fatal 
  • Flight Conducted Under: Part 91: General aviation - Personal

https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/200637/pdf

https://registry.faa.gov/AircraftInquiry/Search/NNumberResult?nNumberTxt=N8796R

On July 26, 2025, about 2237 Pacific daylight time, a Beech 95-B55, N8976R, was substantially damaged when it was involved in an accident near Pacific Grove, California. The pilot and two passengers were fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.

Review of recorded radio communications from the Northern California Terminal Radar Approach Control (NorCal Approach) revealed that the pilot requested flight following to Monterey Regional Airport (MRY), Monterey, California, after departure from San Carlos Airport (SQL), San Carlos, California. The controller provided a transponder code and advised the pilot to remain outside of the San Francisco Class Bravo airspace, to which the pilot acknowledged. The recordings depicted that the pilot had 3 frequency changes spanning the following 32 minutes. About 17 minutes after the pilot had obtained flight following, the controller obtained a Pilot Report (PIREP) from an airplane landing at MRY and quired the pilot if copied the PIREP, which the pilot acknowledged. The pilot then informed the controller he had obtained the current weather for MRY and requested the instrument landing system (ILS) 10R approach. Subsequently, the pilot was cleared to MRY via the ILS 10R approach.

During the approach, the controller saw that the airplane had descended below the minimum vectoring altitude, and quired the pilot as to whether he was going around. The pilot replied “yes,” he was going around and requested vectors back to ZEBED; the ILS initial approach fix. The controller issued instructions for the pilot to turn to a westerly heading and climb to 3,000 ft, which the pilot acknowledged. Shortly after, the controller issued low altitude alerts for the accident airplane and despite multiple attempts, no further radio communication was heard from the pilot.

Recorded ADS-B data provided by the Federal Aviation Administration showed that the airplane departed from SQL, runway 30 at 2211:03, and made a climbing left turn toward the south, before it leveled off at 5,500 ft mean sea level (msl). The data showed that at 2230:01, the airplane began a descent to an altitude of 2,400 ft msl. At 2233:42, the airplane made a left turn to an easterly heading and descended to an altitude of about 1,600 ft msl. At 2236:00 the airplane initiated a left descending turn. The data showed that the airplane continued in the descending left turn until ADS-B contact was lost over the Pacific Ocean at 2237:11, at an altitude of 200 ft msl, about 50 ft south of the accident site as seen in figure 1.

Witnesses near the accident reported hearing an airplane overflying their residence several times. One witness also reported hearing erratic engine noises and a low-flying airplane in a level left turn over their residence. The witness stated that the airplane turned to the north and entered a nose-down attitude until it descended out of their visual range followed by a loud impact sound.

At 2254, recorded weather at MRY was wind from 280° at 6 knots, visibility of 10 statute miles, ceiling overcast at 900 ft, temperature of 59°F, dew point 55°F, altimeter 29.99 inches of mercury, remarks included: an automated station with a precipitation sensor (AO2), and a ceiling height that varied between 600 and 1000 ft.

The wreckage was located about 300 ft from the shoreline, submerged in water, at a depth of about 10 to 15 ft. The airplane was recovered to a secure location for further examination.