Near midair/TCAS alert/loss of separation: Diamond DA20-C1 Eclipse, N857PA, and Robinson R44 Raven, N744AF, incident occurred on December 9, 2023, near North Las Vegas Airport (VGT/KVGT), Las Vegas, Nevada

• Location: North Las Vegas, Nevada 
• Incident Number: OPS24LA011 
• Date & Time: December 9, 2023, 11:06 Local 
• Registration: N857PA (A1); N744AF (A2) 
• Aircraft: DIAMOND AIRCRAFT IND INC DA20-C1 (A1); ROBINSON HELICOPTER R44 (A2) Aircraft 
• Damage: None (A1); None (A2) 
• Defining Event: Near midair/TCAS alert/loss of separation 
• Injuries: 2 None (A1); 1 None (A2) 
• Flight Conducted Under: Unknown (A1); Unknown (A2)

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

A Robinson R-44 helicopter N744AF, VW02 (View 02), and a Diamond DA20-C1 Eclipse, N857PA were involved in a near midair collision (NMAC) approximately 1.7 miles west of the North Las Vegas Airport (VGT).

At the time of the incident the VGT airport traffic control tower (ATCT) was staffed by two controllers with three personnel available. The local control 1 (LC1), local control 2 (LC2), local assist (LA1), and controller in charge (CIC) positions were all combined to the LC1 position. The ground control (GC), flight data (FD), and clearance delivery (CD) positions were combined at the GC position. According to ATC audio recordings and post event interviews, the LC1 controller had instructed N857PA to enter left traffic for runway 30L. About 25 seconds later, VW02 requested a west departure from the transient ramp and the LC1 controller advised departure would be at their own risk. About three minutes later, VW02 and N857PA experienced a NMAC after VW02 had departed to the west and N857PA was on a southeast heading, approaching the mid-field left downwind position for runway 30L.The LC1 controller’s expectation that VW02 would have departed sooner led to an inadequate scan and loss of situational awareness. Additionally, the LC1 controller did not provide adequate or timely traffic advisory or safety alert information to either aircraft as required in FAA Order JO 7110.65AA, Air Traffic Control.

- Probable Cause: The local controller’s loss of situational awareness, inadequate provision of traffic advisory or safety alert information, and lack of positive control, that resulted in a near-midair collision.

Cessna 172N Skyhawk, N6124D, accident occurred on November 17, 2025, near Palm Bay, Florida

• Location: Palm Bay, FL 
• Accident Number: ERA26LA046 
• Date & Time: November 17, 2025, 19:00 Local 
• Registration: N6124D 
• Aircraft: Cessna 172 
• Injuries: 1 Minor 
• Flight Conducted Under: Part 91: General aviation - Personal

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

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

On November 17, 2025, about 1900 eastern standard time, a Cessna 172N, N6124D, was substantially damaged when it was involved in an accident near Palm Bay, Florida. The private pilot sustained minor injuries. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.

The pilot stated that the flight departed with full fuel tanks and after takeoff flew to Okeechobee County Airport (OBE), Okeechobee, Florida, where he performed one touch-and-go landing. He then departed to the north, switched the fuel selector to the right tank for between 5 and 15 minutes to balance the fuel consumed. He then switched the fuel selector to both, performed maneuvers, and then while flying about 2,800 ft mean sea level (msl) initiated a practice emergency descent. Prior to initiating the maneuver, he applied carburetor heat, then reduced the throttle to idle, and banked 45° to the left while descending at 120 knots. Upon reaching 1,500 ft msl, he added full power, but the engine rpm only increased from 800 to 1,100 and he heard the engine sputtering. The pilot pitched the airplane for an airspeed of 65 knots, verified that the mixture was full rich and the carburetor heat was on. He also checked the magnetos and tried to restart the engine but was unsuccessful. The pilot performed a forced landing to a road and after touchdown maneuvered the airplane to the right to avoid a car. During the landing roll the right wing collided with a traffic sign. The airplane veered to the right and came to rest in a ditch with the fuselage elevated in a nearly vertical position. The airplane sustained substantial damage to both wings and the fuselage.

The wreckage was retained for examination to be performed following recovery.

Beechcraft B300 King Air 350, N545KA, and Cessna U206F Stationair, N37EW, accident occurred on November 12, 2025, at Muscatine Municipal Airport (MUT/KMUT), Muscatine, Iowa

• Location: Muscatine, IA 
• Accident Number: CEN26LA045 
• Date & Time: November 12, 2025, 14:10 Local 
• Registration: N37EW (A1); N545KA (A2) 
• Aircraft: Cessna TU206F (A1); HAWKER BEECHCRAFT CORP B300 (A2) 
• Injuries: 2 None (A1); 3 None (A2) 
• Flight Conducted Under: Part 91: General aviation - Personal (A1); Part 91: General aviation - Executive/Corporate (A2)

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

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

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

On November 12, 2025, about 14:10 central standard time, a Cessna TU206F, N37EW, and a Hawker Beechcraft Corp B300, N545KA, were substantially damaged when they were involved in an accident at Muscatine Regional Airport (MUT), Muscatine, Iowa. The pilot and passenger of the TU206F were not injured, and the pilot, check airman, and FAA observer of the B300 were also not injured. The TU206F and B300 were operated as a Title 14 Code Of Federal Regulations Part 91 personal flights.

According to the pilot of TU206F, before crossing runway 06/24, he visually cleared the runway of any traffic. He then made a radio call on the common traffic advisory frequency stating that he was crossing runway 06/24 at taxiway Bravo. He stated that he did not hear any radio transmissions from the B300 before the accident.

According to the pilot of the B300, he was conducting a simulated single-engine approach for the ILS runway 24. He reported that he made a radio call on the common traffic advisory frequency after passing the final approach fix, and on short final to runway 24. During the landing roll, he saw an airplane taxiing across the runway from left to right. He attempted to avoid colliding with the TU206F by veering left. The pilot stated that he did not hear the TU206F make a radio call before crossing the runway.

The B300 impacted the empennage of the TU206F with its right wing at the intersection of runway 24 and taxiway B. The TU206F sustained substantial damage to its empennage, and the B300 sustained substantial damage to its right wing.

A video recording of the accident was gathered for further examination.

Mooney M20K 231, N57229, incident occurred on December 3, 2025, near Bay Minette, Alabama

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=N57229

- History of Flight:
On December 3, 2025, at about 1534 local time, a Mooney M20K 231, N57229, sustained unknown damage when it was involved in a forced landing near Bay Minette, Alabama. The sole pilot onboard sustained unknown injuries. The flight originated from the Foley Municipal Airport (5R4), Foley, Alabama, and was destined to an unknown location.

ADS-B data indicates the airplane was cruising at about 3,800 ft when it entered a descending right hand turn, most likely in an attempt to reach Bay Minette Municipal Airport (1R8).

The FAA reported that: "Aircraft experienced engine issues and made a forced landing in a field." The FAA also listed the wrong N number "N7229."

Figure 1: Flightaware track

Curtiss-Wright Travel Air 4000, N9031, incident occurred on December 2, 2025, at Chico Regional Airport (CIC/KCIC), Chico, California

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=N9031

- History of Flight:
On December 2, 2025, at about 1620 local time, a privately-registered Curtiss-Wright Travel Air 4000, N9031, sustained unknown damage when it was involved in an incident at Chico Regional Airport (CIC/KCIC), Chico, California. The sole pilot onboard was not injured.

The FAA reported that: "Aircraft experienced a brake failure and ground looped off the runway into the grass."

Huebbe Tom Max TH, N48TH, accident occurred on November 26, 2025, at Inverness Airport (INF/KINF), Inverness, Florida

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=N48TH

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

- History of Flight:
On November 26, 2025, at about 1645 local time, a privately-registered Huebbe Tom Max TH, N48TH, sustained substantial damage when it veered off the runway and struck a sign during takeoff at Inverness Airport (INF/KINF), Inverness, Florida. The sole pilot onboard was not injured. The local flight originated from INF.

Cessna 172L Skyhawk, N1141M, incident occurred on December 2, 2025, at Auburn Municipal Airport (AUN/KAUN), Auburn, California

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=N1141M

- History of Flight:
On December 2, 2025, at about 1500 local time, a Cessna 172L Skyhawk, N1141M, registered to Sunshine Flyers out of Auburn, CA, sustained unknown damage when it was involved in an incident at Auburn Municipal Airport (AUN/KAUN), Auburn, California. The pilot and passenger were not injured. The local flight originated from KAUN.

The FAA reported that: "Aircraft on takeoff, veered off runway became airborne and tail struck a power control box on side of the runway."