Tuesday, January 13, 2026

Cessna 750 Citation X, N772XJ, accident occurred on January 13, 2026, at Telluride Regional Airport (TEX/KTEX), Telluride, Colorado

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

- History of Flight:
On January 13, 2026, at about 1216 local time, a Cessna 750 Citation X, N772XJ, registered to Mach .92 Leasing LLC out of Raleigh, North Carolina, and being operated by Jet Excellence LLC, sustained substantial damage when it was involved in an accident at Telluride Regional Airport (TEX/KTEX), Telluride, Colorado. The two pilots and three passengers were not injured. The flight originated from Teterboro Airport (TEB/KTEB), 
Teterboro, New Jersey, at 0820 LT, and was destined to KTEX.

Preliminary information indicates the airplane veered off the left side of runway 9 due to wind gusts. The left main gear collapsed as a result. The thrust reversers were notably deployed.

At 1155 LT, the winds were from 270° at 4 knots, gusting 17 knots. At 1215 LT, the winds were from 020° at 4 knots.

Weather:

METAR KTEX 131855Z AUTO 27004G17KT 10SM CLR 08/M07 A3043 RMK AO2

METAR KTEX 131915Z AUTO 02004KT 10SM CLR 08/M08 A3041 RMK AO2

METAR KTEX 131935Z AUTO 05003KT 10SM CLR 07/M08 A3041 RMK AO2

Cessna 172N Skyhawk, N9360E, fatal accident occurred on January 4, 2026, at Provincetown Municipal Airport (PVC/KPVC), Provincetown, Massachusetts

  • Location: Provincetown, MA 
  • Accident Number: ERA26FA084 
  • Date & Time: January 4, 2026, 15:04 Local 
  • Registration: N9360E 
  • Aircraft: Cessna 172 
  • Injuries: 1 Fatal 
  • Flight Conducted Under: Part 91: General aviation - Personal

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

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

On January 4, 2026, at 1504 eastern standard time, a Cessna 172N, N9360E, was substantially damaged when it was involved in an accident near Provincetown, Massachusetts. The private pilot was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.

The airplane was owned and operated by a flying club that was based at Taunton Municipal Airport (TAN), Taunton, Massachusetts. ADS-B track data provided by the Federal Aviation Administration showed that the airplane departed from runway 30 at TAN at 1406 before it began flying toward Provincetown Municipal Airport (PVC), Provincetown, Massachusetts. According to the airport manager of PVC, about 1430 the accident pilot advised over the airport’s Common Traffic Advisory Frequency (CTAF) that he was inbound to runway 7 for a full stop landing. The pilot was subsequently advised that the airport was closed for snow removal operations but would be reopening about 15 minutes later. The pilot acknowledged the transmission and about that time, the airplane’s ADS-B track began maneuvering before it started flying toward Marshfield Municipal Airport (GHG), Marshfield, Massachusetts (see figure 1). ADS-B track data was lost at 1447 as the airplane approached runway 24 at CHG and resumed at 1450 as the airplane climbed away from that runway.

The airplane began to head toward PVC, and about 1500, the pilot stated on the PVC CTAF that he was inbound for to land on runway 25. No further communications from the pilot were heard over the CTAF. The ADS-B data track was interrupted about 600 ft before the runway 25 threshold, with the last data point of the approach displaying a barometric altitude of 0 ft and groundspeed of 63 knots. The ADS-B track resumed when the airplane was over the runway after the barometric altitude fluctuated up to 75 ft, about 1,500 ft from the runway threshold. The last ADS-B data point showed barometric altitude of 75 ft and a ground speed of 80 knots and was located about 50 ft prior to where impact marks were found on the runway surface (figure 2).

A surveillance camera located on a maintenance hangar at PVC captured the airplane as it crossed the runway threshold at a low altitude before it began to slightly climb and exit the video frame. A second surveillance camera captured the airplane in a slight climb over the runway before it began a sudden descent. The airplane impacted the runway and bounced before contacting the runway a second time and sliding to a stop. The airport windsock was visible and indicated a crosswind from the northwest (right side of the runway) prevailed.

Postaccident examination of the runway revealed that there were impact marks 2,020 ft from the runway 25 threshold that were 25 ft to the left of the runway centerline. The impact marks included impressions consistent with the geometry of the three landing gear, slashes of the runway pavement oriented perpendicular with the runway direction that were consistent with propeller strikes, and abrasion that was consistent with contact from the underside of the airplane’s fuselage. Another ground scar was located 18 ft to the right of the nose landing gear impact signature consistent with right wingtip contact. A second set of impact signatures and subsequent skid signatures was located 2,450 ft from the runway threshold and 15 ft to left of the runway centerline. The majority of the airplane came to rest 2,720 ft from the runway 25 threshold, just beyond taxiway C, with the empennage overhanging the right side of the runway. A postimpact fire damaged much of the central portion of the airplane.

The right wing was partially attached to the fuselage structure remnants and the wing strut remained attached to the wing and to the lower fuselage. The right wing was displaced upward starting midspan and out towards the wing tip. The right wingtip composite material was fractured and evidence of scrapping consistent with runway contact was present. The right flap was in the retracted position. The right fuel tank was intact and contained several gallons of liquid consistent with aviation fuel. The left wing, including the flap, was consumed by fire. The left fuel tank was breached. Control cable continuity of the ailerons to the control yokes was established.

The empennage was intact but separated from the fuselage as a result of fire. Control cable continuity of the elevator and rudder was established. The elevator trim actuator was measured and correlated to a tab deflection that was 5° toward nose down.

The engine remained attached to the fuselage via the tubular engine mounts. The engine’s crankshaft rotated 720° when force was applied to the crankshaft flange. Thumb compression and valve action movement were observed on all cylinders. Continuity of the crankshaft to the camshaft was confirmed throughout the engine. The cylinders were examined with a lighted borescope and there were no discrepancies with the valves observed. The piston faces had combustion residue and deposits consistent with normal engine operation.

The two-blade, metal propeller remained attached to the engine crankshaft flange. The spinner was secured to the propeller hub and was displaced upward. The bottom of the spinner displayed signatures consistent with abrasion from runway contact. One propeller blade was twisted and displayed leading edge gouging and scoring, chordwise scratching, and tip curling. The other blade had tip curling and chordwise scratching on the blade tip.

Piper PA-46-701TP M700 Fury, N646U, accident occurred on November 24, 2025, at Provo Airport (PVU/KPVU), Provo, Utah

  • Location: Provo, UT 
  • Accident Number: WPR26LA050 
  • Date & Time: November 24, 2025, 15:29 Local 
  • Registration: N646U 
  • Aircraft: PIPER AIRCRAFT INC PA-46-701TP 
  • Injuries: 1 Serious, 3 Minor 
  • Flight Conducted Under: Part 91: General aviation - Personal

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

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

 On November 24, 2025, at 1529 Pacific daylight time, a Piper Aircraft Inc. PA-46-701TP (Fury), N646U, was substantially damaged when it was involved in an accident in Provo, Utah. The pilot was seriously injured and the three passengers sustained minor injuries. The airplane was operated as a Title 14 Code of Federal Regulations (CFR) Part 91 personal flight.

The pilot reported that he and the passengers had flown into Provo earlier in the day, and that the accident flight was destined to return to their home base in Van Nuys, California. The pilot recalled that he performed his normal takeoff procedure by configuring the autopilot to hold the runway heading, setting the climb in the flight management system (FMS) to an airspeed of about 125 kts with an altitude of 9,000 ft selected. He initiated the takeoff using the autothrottle button in takeoff mode. He reported the airplane departed normally and he subsequently retracted the landing gear. At about 500 to 600 feet above ground level (agl), he engaged the autopilot and a few seconds later, the airplane stopped climbing, and then began to descend. He checked the configuration and then disconnected the autothrottle and the autopilot.

The pilot further stated that when the airplane reached about 7,000 ft msl, the control yoke became very difficult to move and he observed that the pitch trim indication showed a full nose-up position. He attempted to move the trim wheel, but was unable to move it from the up stop. He asked the right-seated passenger to roll the trim wheel toward a neutral indication, but the pilot stated there was no effect on the control forces or the airplane’s nose-up tendency. The pilot held both hands on the yoke to hold the pitch attitude down in order to maintain level flight or descend. He stated the control pressure required to keep the nose from rising was extreme and unlike anything he had experienced. He stated he believed the trim was stuck in the full nose-up position even when the indicator later showed it to be near neutral.

The pilot reported that he relayed to air traffic control that he wanted to return to land at the departure airport and while maneuvering back he continued to exert high forward yoke forces to keep the airplane from pitching up. He reported difficulty slowing the airplane and attempted to locate and pull the appropriate circuit breaker, but could not reach it while maintaining forward pressure. He aligned the airplane for the approach to the runway with minimal configuration changes and targeted an airspeed of about 110 to 115 knots prior to touchdown. He stated that even on short final, he maintained two hands on the yoke and used a knee to keep the nose down. On touchdown, the pilot briefly relaxed his grip and the airplane immediately pitched up and became airborne again, then descended back to the runway. The airplane erupted in flames after it came to rest.

The airplane was equipped with a Garmin G3000 avionics suite with a GFC 700 digital autopilot, and a HALO autothrottle. According to the airplane’s Pilot Operating Handbook (POH), when the autothrottle is engaged, the system limits autothrottle operation to within the approved speed envelope of the airplane. Specifically, the autothrottle will automatically limit the airplane’s speed to the current configuration speed limitation regardless of the power or speeds selected by the pilot. When the autothrottle is not engaged, the system continuously monitors for overspeed and underspeed conditions, independent of flight director or autopilot modes, as long as the Electronic Stability and Protection (ESP) is active. If the airplane accelerates beyond the current configuration speed limit, the autothrottle engages and decreases power to prevent an overspeed condition; the pilot would receive an annunciation of “MAX SPD” as well as “Airspeed” and “Engaging Autothrottle” aural alerts. As the speed decreases below the limit, autothrottle disengages, an “Autothrottle” aural alert is played, and power remains where it was last set by the MAX SPD commands.

A preliminary review of the downloaded Garmin data was performed by the airplane manufacturer representatives. The data disclosed that while the airplane was at the hold-short threshold for runway 13, the autopilot was configured laterally in the heading-hold mode and then while taxiing to the runway centerline, the autopilot vertical mode was configured to flight level change (FLC) pitch-for-speed mode. As the airplane was on the centerline, the autothrottle was engaged as the pilot initiated the takeoff. The airplane lifted off at 1518:53, as indicated by the transition of the weight-on-wheels parameter to an airborne state. The landing gear retracted several seconds later and the flaps remained at the takeoff setting of 15°.

At 1519:11, as the airplane climbed to about 275 ft agl, the autopilot was activated and simultaneously the autopilot vertical mode changed from FLC to altitude hold mode. Beginning at 1519:26, the airplane entered a brief descent of approximately 133 ft with both the autopilot and autothrottle engaged, with the vertical mode remaining in FLC. (See Figure 1). During this descent, the airspeed appeared to exceed the Maximum Flap Extended Speed (Vfe) at 15° flaps (147 kt indicated airspeed (KIAS)). A reduction in engine torque occurred at 1519:41 with the autothrottle still engaged.

The autothrottle disconnected at 1519:56, followed by activation of the autothrottle in ESP mode at 1520:02. The autothrottle engaged at 1520:04, consistent with protection that prevented an exceedance of the flap-extended airspeed limitation. Multiple autothrottle state changes occurred during the flap overspeed condition, consistent with manual disconnection attempts followed by automatic re-engagement as the airplane continued to exceed the 147 kts Vfe. (See Figure 2). The vertical mode changed from FLC to pitch mode at 1520:12 and from pitch to vertical speed mode at 1520:44.

At 1521:28, altitude data showed the airplane entering a climb with the autopilot still engaged. Pitch trim values increased in the nose-up direction. There was an overtorque at 1521:08 and then again at 1521:55. The airplane’s pitch attitude increased from -1.1° to +10.7° over a 23.6- second interval, reaching the maximum value at 1521:51. A full extension and retraction of the landing gear occurred at 1521:35. A pitch oscillation of approximately 4° occurred at 1521:55, and the autothrottle was activated simultaneously. Pitch trim reached its maximum nose-up setting at 1522:11 and remained around there until 1524:04, at which point it transitioned to the nose-down position. Autothrottle was activated at 1523:39, and the flaps were retracted from 15° to the UP position at 1523:53. The vertical mode changed from vertical speed to pitch mode at 1524:15, then reverted back to vertical speed 2.6 seconds later. The airplane reached its maximum altitude of about 3,280 ft agl at 1524:18.

At 1525:16, the vertical mode again changed briefly from vertical speed to pitch mode before returning to vertical speed. Another brief pitch mode transition occurred at 1527:35 before the system returned to vertical speed. Pitch trim reached a neutral value at 1527:30. The pilot selected the landing gear down at 1528:01 at an indicated airspeed of 204 kts, well above the landing-gear-extended limit of 170 kts. Autothrottle was activated at 1528:03, accompanied by multiple state changes as the airspeed gradually decayed. The pitch trim moved in the nose-up direction following gear extension. The vertical mode again transitioned from vertical speed to pitch mode at 1528:10 and returned to vertical speed shortly thereafter.

The descent for landing began at 1528:18. The autopilot disconnected at 1528:40 at an altitude of 83 ft agl. A pitch oscillation developed immediately following the disconnect, with a maximum recorded peak-to-peak amplitude of approximately 12.9° during a 1.8-second period. When the airplane’s pitch attitude reached -4.9°, wheel-speed sensors on both main landing gears registered simultaneous spikes, and the left main weight-on-wheels parameter briefly indicated ground contact. The nose-gear weight-on-wheels parameter remained in the airborne state until 1536:41.

The airplane was recovered for a future examination.

Enstrom F-28A, N520H, and Enstrom 280C Shark, N280MG, fatal accident occurred on December 28, 2025, in Hammonton, New Jersey

  • Location: Hammonton, NJ 
  • Accident Number: ERA26FA077 
  • Date & Time: December 28, 2025, 11:24 Local 
  • Registration: N280MG (A1); N520H (A2) 
  • Aircraft: Enstrom 280 (A1); Enstrom F28 (A2) 
  • Injuries: 1 Fatal (A1); 1 Fatal (A2) 
  • Flight Conducted Under: Part 91: General aviation - Personal (A1); Part 91: General aviation - Personal (A2)

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

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

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

 On December 28, 2025, at 1124 eastern standard time, an Enstrom F-28A helicopter, N520H, and an Enstrom 280C helicopter, N280MG, collided in midair near Hammonton, New Jersey. The private pilots onboard each of the helicopters were fatally injured. Both helicopters were being operated as Title 14 Code of Federal Regulations Part 91 personal flights.

According to preliminary ADS-B data provided by the Federal Aviation Administration, both helicopters had departed from Vineland-Downstown Airport (28N), Vineland, New Jersey at about 0948 and flew parallel paths to Hammonton Municipal Airport (N81), Hammonton, New Jersey, arriving about 0958. No ADS-B data captured the helicopters’ subsequent departure from N81 on the accident flight.

Surveillance video captured both helicopters as they flew in close proximity to each other shortly before the accident. The helicopters were slightly staggered from one another and flying on a similar heading, similar to a formation flight. As the flight continued, the helicopters converged until they contacted each other. Subsequently, one helicopter began a tumbling descent toward terrain before exiting the frame of the video. The other helicopter pitched up sharply before leveling out. Shortly after, the helicopter began yawing in a clockwise direction and descended rapidly until it exited the video frame.

The accident site was located about 1.5 miles southwest of N81 and was comprised of a debris path that was about 1,211 ft-long. The first identified debris along the path included several paint chips consistent with the paint color of both helicopters. Further along the debris path were portions of the main rotor blades of both helicopters, as well as portions of the tail cone and tail rotor blades of N280MG.

The primary wreckage of N520H was about 890 feet from the beginning of the debris path. The helicopter sustained substantial damage to the fuselage, tail cone, tail rotor, and main rotor. The aft portion of the tail cone had partially separated from the forward portion of the tail cone and was only attached to the airframe through one tail rotor control cable; the other control cable displayed tensile overload signatures. There were no signs of fire. Portions of the main rotor skin, plexiglass, as well as a portion of the tail rotor drive shaft, were found along the debris path. The ground on the left side of main portion of the wreckage displayed signatures consistent with main rotor strikes.

The primary wreckage of N280MG was about 270 ft from the primary wreckage of N520H. The helicopter was destroyed by a postimpact fire, and most of the fuselage and main rotor system had been consumed by the fire. The tail cone remained relatively intact and displayed terrain impact damage and the aft portion of the tail cone displayed damage consistent with impact while in flight. Portions of one of the main rotor blades, the tail rotor, and the tail cone of this helicopter were also found along the debris path.

Further examination of the main rotor skins of N520H revealed an impact mark with paint transfer of a color consistent with the tail rotor blade of N280MG. 

The wreckage was recovered and retained for further examination.

Cirrus SR22 GTS G3 Turbo, N242AZ, accident occurred on December 20, 2025, near Springfield, Missouri

  • Location: Springfield, MO 
  • Accident Number: CEN26LA066 
  • Date & Time: December 20, 2025, 13:02 Local 
  • Registration: N242AZ 
  • Aircraft: CIRRUS DESIGN CORP SR22 
  • Injuries: 2 None 
  • Flight Conducted Under: Part 91: General aviation - Personal

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

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

On December 20, 2025, about 1302 central standard time, a Cirrus SR22 airplane, N242AZ, was substantially damaged when it was involved in an accident near Springfield, Missouri. The pilot and passenger were not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.

The airplane departed from the General Dewitt Spain Airport (M01), Memphis, Tennessee, about 1130, for the cross-country flight. According to the pilot, about an hour and twenty minutes after departing, while in cruise flight at 8,000 ft mean sea level, he received a Crew Alerting System (CAS) message indicating a high turbine inlet temperature (TIT). The pilot followed the appropriate checklist and reduced fuel flow to the engine which resolved the CAS message; however, the engine started to run rough. The engine roughness increased over time though the engine instruments indicated normal operation. The pilot elected to divert to the Springfield – Branson National Airport (SGF), Springfield, Missouri, and started a descent. Upon reducing power for the descent, the engine ran significantly worse. The pilot descended at the airplane’s best glide speed and prepared to make a forced landing to a road. The pilot stated that during the forced landing, he moved the power lever forward, but the engine did not provide any thrust.

The pilot landed on the southbound lanes on US 65, about 9 miles east-northeast of SGF. During the landing, the airplane’s left wing struck a road sign, crossed the highway median and came to rest upright in the northbound lanes. The pilot and the passenger were able to egress from the airplane without further incident. A post-accident fire ensued and partially consumed the airplane. The airplane sustained substantial damage to both wings and the fuselage.

The airplane was recovered to a secure facility for future examination.

The airplane was equipped with a Continental Motors IO-550-N51 reciprocating engine and a Hartzell PHC-J3YF-1N/N7605C 3-blade controllable pitch composite propeller.

Cessna 172P Skyhawk, N54576, accident occurred on December 20, 2025, near New Kent County Airport (W96), Quinton, Virginia

  • Location: Browns Corner, VA 
  • Accident Number: ERA26LA073 
  • Date & Time: December 20, 2025, 14:15 Local 
  • Registration: N54576 
  • Aircraft: Cessna 172P 
  • Injuries: 1 None 
  • Flight Conducted Under: Part 91: General aviation - Personal 

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

https://registry.faa.gov/aircraftinquiry/Search/NNumberResult?NNumberTxt=N54576

On December 20, 2025, at 1415 eastern standard time, a Cessna 172P airplane, N54576, was substantially damaged when it was involved in an accident near Quinton, Virginia. The private pilot was not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.

The pilot was operating out of New Kent County Airport (W96) Quinton, Virginia and reported that the preflight inspection, engine run-up, and taxi were normal. He performed several touchand-go landings that were uneventful. Shortly after takeoff, as the airplane was climbing through 500 ft above ground level (agl), the engine rpm began to fluctuate. The pilot further described that, the engine did not “sputter,” but the rpm was “abnormal.” The pilot applied carburetor heat and attempted to troubleshoot the irregularity without success. As the airplane reached about 650 ft agl, it stopped climbing and began to lose altitude and airspeed. The pilot decreased the airplane’s pitch, established best glide speed, and identified an open field for a forced landing.

While maneuvering on final approach to the field, the pilot realized that the field was very hilly and bordered with trees. The pilot attempted to make slight turns to increase the chances of a successful landing, but in the process, the airplane lost too much airspeed. Unable to make additional adjustments due to the low airspeed and altitude, the pilot fully extended the flaps and intentionally “planted” the landing gear hard into the mud so that the airplane would stop before impacting the trees. After touchdown, the landing gear created deep gouges in the field for about 100 ft before the airplane rolled into the tree line and came to rest. The hard landing and impact with the trees resulted in substantial damage to the wings and fuselage; the right outboard wing was fractured downward, both wing struts were damaged, and the engine compartment was canted. The propeller and spinner were largely intact and did not exhibit any chordwise scraping or leading edge gouges.

The airplane was recovered and retained for further examination.

Pitts S-1 Special, N401MS, accident occurred on December 31, 2025, at Southern Illinois Airport (MDH/KMDH), Carbondale/Murphysboro, Illinois

  • Location: Carbondale, IL 
  • Accident Number: CEN26LA074 
  • Date & Time: December 31, 2025, 16:03 Local 
  • Registration: N401MS 
  • Aircraft: Pitts S1S 
  • Injuries: 1 Minor 
  • Flight Conducted Under: Part 91: General aviation - Personal

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

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

On December 31, 2025, at 1603 central standard time, a Pitts S1S airplane, N401MS, was substantially damaged when it was involved in an accident near Carbondale, Illinois. The pilot received minor injuries. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.

The pilot reported that he had completed three touch-and-go landings on runway 36R. He then completed a low approach over runway 18L and began a climb near the departure end of the runway. Upon reaching 400 ft above ground level (agl), the engine lost power. The pilot was able to momentarily restore partial power by manually actuating the emergency fuel pump; however, the engine lost power again. Unable to maintain altitude, the pilot completed a forced landing on an airport perimeter road, then exited the road to the right and struck a power pole. The left wing separated from the airplane during the impact.

The tail mounted video camera captured the accident sequence, and the video was provided for the investigation. The airplane’s engine monitoring system data card and the airplane have been retained for further examination.

Cessna TU206F Turbo Stationair, N917WC, accident occurred on December 11, 2025, near Chulavista, Alabama

  • Location: Pell City, AL
  • Accident Number: ERA26LA066
  • Date & Time: December 11, 2025, 19:40 UTC 
  • Registration: N917WC 
  • Aircraft: Cessna TU206 
  • Injuries: 1 Minor, 1 None 
  • Flight Conducted Under: Part 91: General aviation - Aerial observation

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

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

On December 11, 2025, about 1340 central standard time, a Cessna TU206F, N917WC, was substantially damaged when it was involved in an accident near Pell City, Alabama. The commercial pilot was not injured. The single passenger sustained minor injuries. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 aerial observation flight.

The pilot reported that he departed on the aerial observation flight with 107 gallons of fuel onboard for a planned 4-hour flight. About 3 hours and 45 minutes into the flight, the pilot observed fluctuations of the fuel quantity and fuel pressure gauges followed, by a sudden total loss of engine power. After informing air traffic control of the emergency, the pilot made an emergency landing in a field, resulting in substantial damage to the fuselage.

A postaccident examination of the wreckage by a Federal Aviation Administration inspector revealed that the nose landing gear had collapsed and the empennage had partially separated during the forced landing. The wreckage was recovered and retained for further examination.

- Ground Collision: AkroTech Giles G-202, N202RD, and Cessna 172R Skyhawk, N825KS, accident occurred on October 28, 2025, at Boca Raton Airport (BCT/KBCT), Boca Raton, Florida

  • Location: Boca Raton, Florida 
  • Accident Number: ERA26LA025 
  • Date & Time: October 28, 2025, 09:03 Local 
  • Registration: N202RD (A1); N825KS (A2) 
  • Aircraft: AKROTECH AVIATION INC GILES G-202 (A1); Cessna 172R (A2) 
  • Aircraft Damage: Substantial (A1); Substantial (A2) 
  • Defining Event: Ground collision 
  • Injuries: 1 None (A1); 2 None (A2) 
  • Flight Conducted Under: Part 91: General aviation - Personal (A1); Part 91: General aviation - Instructional (A2)

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

https://data.ntsb.gov/Docket?ProjectID=201933

The pilot of the tailwheel-equipped low-wing airplane received a taxi clearance from the tower air traffic controller for a planned departure and began taxing toward the assigned runway. About 3 minutes later, the student pilot of the high-wing airplane requested and received a takeoff clearance while located stationary at the edge of the runup area. The student pilot then advised his flight instructor that the low-wing airplane was approaching from the left, heading toward their airplane. To avoid a collision, the flight instructor took control of the high-wing airplane and advanced the throttle in an attempt to taxi out of the path of the low-wing airplane. The low-wing airplane then impacted the high-wing airplane, resulting in substantial damage to the propeller of the low-wing airplane and to the left wing of the high-wing airplane. The pilot of the low-wing airplane reported that he saw other airplanes in the runup area but did not see the accident high-wing airplane until he was “underneath” its wing. The pilots of both airplanes reported that there were no preaccident mechanical malfunctions or failures with the airplanes that would have precluded normal operation.

- Probable Cause: The low-wing pilot’s inadequate visual lookout, which resulted in a collision with another airplane while taxiing.

Kubicek BB26M, N90MN, accident occurred on January 10, 2026, in La Verkin, Utah

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


- History of Flight:
On January 10, 2026, at about 1000 local time, a Kubicek BB26M hot air balloon, N90MN, registered to A&L Professional Services Inc out of Minden, Nevada, sustained substantial damage when it was involved in an accident in La Verkin, Utah. The pilot and a designated Pilot Examiner (DPE) onboard were not injured.

The FAA reported: "Aircraft maneuvering and experienced a down draft and became stuck in power lines."

During a post accident interview, the DPE onboard reported the following: 

"...said the flight was a pilot’s exam, and the pilot was doing well up until the sudden weather changes. He said the pilot had great control of the balloon, but as they were finding a spot to land, they passed over a cavern, which created a down draft."

“Once it appeared that we were probably going to contact the wires, the applicant did a good job. He pulled the top, which means we weren’t going to try to go up anymore. We’re just going to hit the wires at an envelope lever, which would mean the basket would be safe, and that’s what we did, and we hit it, and we actually slid down to the ground.”

Despite making contact with the ground, the DPE stated that the protocol dictated that the passengers remain in the basket until the power company confirmed that the power had been cut from the wires.

"... said they would attempt another flight for the pilot on Sunday for certification purposes."

Piper PA-28-180 Cherokee D, N6516J, accident occurred on January 10, 2026, near Okeechobee, 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=N6516J

- History of Flight:
On January 10, 2026, at about 1927 local time, a Piper PA-28-180 Cherokee D, N6516J, registered to Telesurv Corp, sustained substantial damage when it was involved in an accident near Okeechobee, Florida. One of the two occupants onboard sustained serious injuries, and another sustained minor injuries. The personal flight originated from the Okeechobee County Airport (OBE/KOBE), 
Okeechobee, Florida, at 1916 LT, and was destined to an unknown location.

According to preliminary Automatic Dependent Surveillance – Broadcast (ADS-B) data, the airplane departed runway 5 at KOBE and entered a climbing right hand turn to an altitude of 2,300 ft. At 1923 LT, the airplane started a descent from that altitude and entered a 180 right turn. The airplane continued to descent until the end of the track (see figure).

The FAA reported: "Aircraft crashed for unknown reasons in a wooded area."

Figure 1: ADS-B Track

Figure 2: End of track.

Piper PA-31-310 Navajo, N669CW, accident occurred on January 11, 2026, at Merrill Field (MRI/PAMR), Anchorage, Alaska

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

- History of Flight:
On January 11, 2026, at about 1602 local time, a Piper PA-31-310 Navajo, N669CW, sustained substantial damage when it was involved in an accident at Merrill Field (MRI/PAMR), Anchorage, Alaska. The sole pilot onboard was not injured. The airplane was registered to Precision Air Inc out of Nelson Lagoon, AK, and being operated on an on-demand Part 135 flight.

According to preliminary Automatic Dependent Surveillance – Broadcast (ADS-B) data, at 1554 LT, the airplane taxied from the east ramp and departed from runway 7L at Merrill Field (MRI/PAMR), Anchorage, Alaska. The airplane climbed to about 1,500 ft before it started a circling 360 turn followed by a 180 turn. At 1600, the airplane entered from 1,500 ft and headed north. At ~1601:50, the airplane entered a tight base-to-final turn for runway 25 at Merrill Field (MRI/PAMR), Anchorage, Alaska. The data shows that the airplane landed and veered off to the left side before coming to rest (see figures).

The NTSB is investigating the event as an accident, case number ANC26LA009.

- Weather:

METAR PAMR 120053Z 36005KT 2SM -SN BR BKN007 OVC024 M11/M13 A2923 RMK AO2 SNB43 SLP901 P0000 T11111128

METAR PAMR 120104Z 01006KT 2SM BR BKN007 OVC024 M11/M13 A2923 RMK AO2 SNE04 P0000 T11111128

METAR PANC 120053Z 01005KT 10SM OVC026 M11/M13 A2923 RMK AO2 SNE2358 SLP900 P0000 T11111128 $

METAR PANC 120153Z 03006KT 10SM OVC026 M12/M14 A2923 RMK AO2 SLP904 T11171139 $

Figure 1: ADS-B data

Figure 2: Landing at MRI

Cessna 172N Skyhawk, N5136E, incident occurred on January 7, 2026, at San Marcos Regional Airport (HYI/KHYI), Austin, Texas

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

- History of Flight:
On January 7, 2026, at about 1400 local time, a Cessna 172N Skyhawk, N5136E, registered to Wings Over Texas Holdings LLC out of Denton, TX, sustained minor damage when it was involved in an incident at San Marcos Regional Airport (HYI/KHYI), Austin, Texas. The student pilot and flight instructor were not injured.

The FAA reported: "Aircraft conducting a simulated engine failure on climb out, landed hard and bent the nose gear."

Piper PA-24-250 Comanche, N7085P, incident occurred on January 8, 2026, in Bay City, Michigan

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

- History of Flight:
On January 8, 2026, at about 1441 local time, a Piper PA-24-250 Comanche, N7085P, registered to Flyum LLC, sustained minor damage when it was involved in an incident in Bay City, Michigan. The pilot was not injured.

The FAA reported: "Aircraft gear collapsed on landing." There is no ADS-B data available for the incident flight.

Quad City Challenger II, N194JR, accident occurred on January 6, 2026, in Greenbrier, Arkansas

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

- History of Flight:
On January 6, 2026, at about 1700 local time, a privately-registered Quad City Challenger II, N194JR, sustained substantial damage when it was involved in an accident in Greenbrier, Arkansas. The pilot sustained minor injuries.

The FAA reported that the airplane crashed immediately after takeoff. However, another online report suggests the airplane crashed during an attempted landing after circling the airport two times.

Raytheon Hawker 800XP, N15RK, and IAI 1125 Astra SPX, N230TG, incident occurred on January 8, 2026, at Chicago-Midway Airport (MDW/KMDW), Chicago, Illinois

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

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

- History of Flight:
On January 8, 2026, at about 0917 local time, a Raytheon Hawker 800XP, N15RK, registered to NLN Hawker Holdings LLC, was taxiing for departure when it struck a parked IAI 1125 Astra SPX, N230TG, at Chicago-Midway Airport (MDW/KMDW), Chicago, Illinois. There were no reported injuries.

ADS-B data indicates that the Astra arrived at Chicago on January 6 and was parked at the west ramp. The Hawker was last seen taxiing towards the same ramp on January 7. The taxiing portion for January 8 was not covered on any ADS-B tracking site.