- 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
I used to run the "Aviation Accidents/This Day in History" Facebook page (also known as the Junior GA Reporter) from 2017 until late 2024. Early coverage for all incidents and accidents on US soil, more detailed coverage for fatal and more serious events. On-time NTSB preliminary report posting and run downs of daily FAA reports. Occasional NTSB final report posting. Not monetized and I don't plan to do that anytime soon, if ever.
Monday, August 25, 2025
Pitts S-1T Special, N51HC, fatal accident occurred on August 12, 2025, near Goodyear, Arizona
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
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:
- Airport Information:
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)
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.
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.
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.

















