Tuesday, August 26, 2025

Cessna 172S Skyhawk SP, N121CW, accident occurred on July 30, 2025, near Kissimmee Gateway Airport (ISM/KISM), Kissemmee, Florida

  • Location: Kissimmee, FL 
  • Accident Number: ERA25LA281 
  • Date & Time: July 30, 2025, 11:28 Local 
  • Registration: N121CW 
  • Aircraft: Cessna 172S 
  • Injuries: 2 None 
  • Flight Conducted Under: Part 91: General aviation - Instructional

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

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

Aerostar Training Services LLC

On July 30, 2025, at 11:28 eastern daylight time, a Cessna 172S, N121CW, was substantially damaged when it was involved in an accident near Kissimmee, Florida. The private pilot and flight instructor were uninjured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 instructional flight.

According to the flight instructor, the purpose of the flight was to provide commercial instruction for the private pilot. The instructor reported that during the preflight, the airplane had sufficient fuel, and the engine had sufficient oil for the cross-country flight. The pilot stated that the taxi, runup, and takeoff were all normal. After departing the Kissimmee Gateway Airport (ISM), Orlando, Florida, while climbing through 1,900 ft mean sea level (msl), both pilots reported feeling engine vibrations, and shortly after, heard a loud bang, and the windshield became covered with engine oil. The instructor took control of the airplane and began to head back to ISM; however, after determining that they had insufficient altitude to return to the airport, they elected to perform a forced landing on a road. The pilots reported their visibility was significantly reduced due to the oil covering the windshield. The pilot receiving instruction looked out the side window, and the instructor utilized her peripheral vision to guide the airplane onto the road. During the forced landing, the airplane impacted a car, and the airplane came to rest on the side of the road. A postaccident examination by the Federal Aviation Administration revealed that the fuselage sustained substantial damage and the engine had experienced a catastrophic internal engine failure. A large portion of the top crankcase had broken free from the rest of the crankcase, and the no. 2 connecting rod had released from its crankshaft journal.

The wreckage was retained for further examination. 

Sonex Aircraft Sonex, N67BG, accident occurred on August 5, 2025, near Tellico Plains Municipal Airport (85TN), Tellico Plains, Tennessee

  • Location: Tellico Plains, TN 
  • Accident Number: ERA25LA290 
  • Date & Time: August 5, 2025, 11:31 Local 
  • Registration: N67BG 
  • Aircraft: GARY W LEWINSKI SONEX 
  • Injuries: 1 Serious 
  • Flight Conducted Under: Part 91: General aviation - Personal
https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/200719/pdf

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

On August 5, 2025, about 1131 eastern daylight time, a Lewinski Sonex, N67BG, was substantially damaged when it was involved in an accident near Tellico Plains, Tennessee. The private pilot was seriously injured. The airplane was operated as a Title 14?Code of Federal Regulations Part 91 personal flight.

The pilot stated that in anticipation of an intended buyer coming to take possession of the airplane in several days, he washed it then performed several taxi tests. During one taxi run he noted a violent shake that stopped when he applied aft control input. He attributed the issue to be related to the nose wheel bearing. He then elected to fly once around the traffic pattern and after takeoff, with one notch of flaps extended, reported the airplane pulled suddenly to the left which he could not correct. Approaching trees ahead, he pulled aft on the control yoke and believed the airplane stalled. The airplane descended uncontrolled and came to rest in trees about 10 to 12 ft above ground level. A fire began in the engine compartment and with some difficulty he exited the cockpit and jumped to the ground. He reported no issues with the engine at any time during the flight. The pilot further stated that there was no failure or malfunction of the flight controls during his preflight check, or as part of a check before departure.

Because he was wearing knee length cotton shorts, he sustained second-degree burns on the lower portion of one of his legs and first-degree burns on the lower portion of his other leg. The postcrash fire extensively damaged the cockpit area of the wreckage, which was recovered for further examination.

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.