Friday, January 30, 2026

Cessna 550 Citation II, N257BW, fatal accident occurred on December 18, 2025, at Statesville Regional Airport (SVH/KSVH), Statesville, North Carolina

  • Location: Statesville, NC
  • Accident Number: WPR26MA063
  • Date & Time: December 18, 2025, 10:22 Local
  • Registration: N257BW
  • Aircraft: Cessna 550
  • Injuries: 7 Fatal
  • Flight Conducted Under: Part 91: General aviation - Personal

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

http://registry.faa.gov/AircraftInquiry/Search/NNumberResult?nNumberTxt=N257BW

On December 18, 2025, at 1015 eastern standard time, a Cessna Citation 550, N257BW, was destroyed when it was involved in an accident near Statesville, North Carolina. The pilot and 6 passengers were fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations (CFR) Part 91 personal flight.

The airplane was positioned on the south parking ramp at Statesville Regional Airport (SVH), Statesville, North Carolina, for passenger loading and preflight. Ground personnel reported the airplane was fully fueled prior to the flight. Cockpit Voice Recorder (CVR) audio began recording the accident flight at 0944:21. The CVR recording confirmed the airline transport rated pilot was seated in the left seat, the pilot’s adult son, who held a private pilot certificate with a single engine land and an instrument rating, was a passenger in the right seat. A rear seat passenger with a private pilot certificate and ratings for multi-engine land, instrument airplane, and rotorcraft-helicopter was positioned near the cockpit in the cabin area.

Engine start was initiated using onboard battery power and, following an initial unsuccessful start of the left (no. 1) engine, both engines were started about 0953. The airplane taxied from the south parking area at 0959, crossed runway 10/28 at midfield, and taxied to the approach end of runway 10. During taxi, the pilot and the two pilot-rated passengers discussed that a thrust reverser indicator light(s) for an unspecified engine was inoperative, but that the thrust reverser for the affected engine was working properly.

The airplane departed from runway 10 at SVH, under visual flight rules (VFR) about 1006. The pilot intended to activate an instrument flight rules (IFR) flight plan, with a planned destination of Sarasota/Bradenton International Airport (SRQ), Sarasota, Florida, once airborne. The pilot performed the takeoff and departure while the right seat passenger performed various checklists and communicated on the radio. During takeoff roll, the rear passenger commented that the left engine was producing more power than the right and indicated there may have been a faulty gauge. The pilot continued the takeoff.

Preliminary GPS data showed the airplane made a climbing left turn following takeoff. At 1007:19 the pilot commented that he would remain VFR until they received their IFR clearance. At 1008, the airplane had turned about 180° and attained an altitude of about 2,200 ft mean sea level (msl). The airplane continued to turn left and began to descend. The right-seat passenger attempted to contact ZTL ATC and activate the flight’s IFR flight plan three times between 1008 and 1010 but was unsuccessful due to the controller’s workload and associated radio communications.

About 1009 there was discussion between the pilot and rear passenger about climbing to a higher altitude, even though they were technically required to remain VFR. The airplane had descended to about 1,580 ft msl and was established on a heading of about 250° and 164 knots (kts) indicated airspeed (IAS) at that time. The pilot initiated a climb, and shortly after, the rear passenger noted a difference between the left and right engine interstage turbine temperature (ITT) indications. There were no further discussions regarding the engine instruments throughout the remainder of the CVR recording. The autopilot was either disengaged intentionally, or it disengaged independently at 1010:02.

Beginning at 1010:14 no intelligible CVR audio was captured from the left seat hot microphone and audio panel for the next 3 minutes and 55 seconds.

Starting at 1010:18, the cockpit area microphone captured the pilot making remarks indicating his altitude indicator was not working properly and that additional left side flight instruments may not have been working properly. The Garmin GTN-750 stopped recording airspeed data at 1009:37 and heading data at 1010:58.

About 1011, airplane control was transferred to the right seat passenger, at an altitude of about 4,500 ft msl. No comments were recorded during the remainder of the CVR recording to indicate there were any malfunctions with the right side cockpit flight instruments.

At 1011:04 severe degradation in CVR audio quality began in all channels, which continued for 3 minutes and 5 seconds.

About 1013, at an altitude of about 1,870 ft msl, the pilot and both pilot-rated passengers stated they could see the ground. Although a positive transfer of airplane control was not recorded, subsequent communication between the pilot and right seat passenger was consistent with the pilot having resumed control of the airplane at that time. The pilot requested the flaps be extended at 1013:03, made a right turn to a westerly heading, and requested the landing gear be extended at 1013:22. Subsequent discussions were consistent with the landing gear being configured; however, the gear indicator lights were not illuminated. At 1013:48, the right seat passenger transmitted on the SVH common traffic advisory frequency (CTAF) in part “…we’re having some issues here.”

At 1014:05 the rear passenger made a query to the pilot regarding power to the “alternator” (NOTE: the CE-550 airplane is not equipped with an alternator). About 4 seconds later audio quality returned to previous levels on all recorded CVR audio channels. After the audio quality returned, the pilot made a comment indicating that was the “problem”, however, did not specify what the “problem” was or what actions were taken to correct it. There were no additional discussions regarding the pilot’s flight instrumentation for the remainder of the CVR recording. The airplane started a left turn (consistent with the base leg) towards runway 28 about 1014:10, at an altitude of about 1,325 ft and 142 kts groundspeed. The Garmin GTN-750 recordings of airspeed data returned at 1014:12. The GPS data showed the airplane rolled out of the turn onto runway heading about 1014:50, at an altitude of about 1,240 ft msl and 114 kts IAS. Recorded CVR audio indicated the right seat passenger visually acquired the runway and provided directions to the pilot as to where the runway was. About 1015:00, the pilot made comments which indicated he had acquired the runway visually.

Recorded data from the GTN-750 showed that the airplane’s airspeed and altitude continued to decrease from the time the airplane was aligned on final approach to the runway until 1015:18, when the airplane was at 984 ft msl and 99 kts IAS. The airplane continued to descend to 942 ft msl until the CVR audio and GPS data ended at 1015:23. The IAS increased to 107 kts and then decreased to about 93 kts during the final five seconds of data. (See figure 1.)

Accident Site and Wreckage

Examination of the accident site revealed that the first identified point of impact (FIPI) was the first (easternmost) light station of the runway 28 Medium Intensity Approach Light System with Runway Alignment Indicator Lights (MALSR), located about 1,380 ft from the runway threshold. Two lightbulbs, the left and fourth from the left position (when viewed looking towards the runway), approximately 6 ft apart, were separated from the otherwise intact 29 ft tall light station (figure 2) and located on the ground near the station. The upper portion of the second MALSR light station located about 180 ft from the FIPI was separated, of which about 15 ft of the frangible pole was still standing. A group of damaged trees located about 235 ft from the FIPI, were sheared about 12 ft above ground level (agl). The first indication of fire was blackened branches and grass near the west side of the trees.

A ground impression was observed about 350 ft from the FIPI, near the airport perimeter fence, and extended through the MALSR decision light station. The debris path continued along a westerly heading through the runway overrun to where the main wreckage came to rest on the runway blast area about 400 ft short of the runway 28 threshold, oriented on an easterly heading. Heavy charring of the ground began near the decision light station and continued along the remaining length of the debris field to the wreckage.

A post impact fire consumed a majority of the fuselage and heat damaged both wings, empennage, and both engines (figure 3). All flight control surfaces were identified in the debris path and main wreckage. No evidence of pre-impact separation of any airplane component or structure was observed.

Both engines remained attached to the pylon structures and both thrust reversers were found in the stowed position. There was no evidence of uncontained engine failure with either engine. Examination of the cockpit throttle quadrant found both thrust levers to be in the full forward position and both reverse throttle levers in the down position, consistent with being stowed.

The No. 1 engine stage 2 low pressure turbine (LPT) blades, viewed through the exhaust duct, were all full length and appeared undamaged. The No. 1 engine fan blades, viewed through the engine inlet, exhibited various degrees of damage and had missing material at the blade tips. The engine inlet surfaces exhibited circumferential scoring between the fan blades forward to the inlet.

The No. 2 engine stage 2 LPT blades, viewed through the exhaust duct, were all full length and appeared undamaged. Most of the engine inlet was not attached to the engine. The No. 2 engine fan blades exhibited various degrees of damage and had missing material at the blade tips.

Pilot Experience

The pilot had type ratings for the A-320, A-330, A-350, B-737, B-757, B-767, CE-500, and DC-10. As part of the pilot’s CE-500 type rating, he had the limitation “CE-500 Second in Command Required.” The pilot reported civil flight experience that included 17,000 total and 400 hours in the last six months as of his last first-class medical application dated April 29, 2025. Review of the right-seat passenger’s logbook indicated that he had 175.3 total flight hours in single engine land airplanes as of November 29, 2025. The right seat passenger’s most recent first-class medical certificate was issued on August 12, 2024. The right seat passenger was not qualified to perform second in command duties per Title 14 CFR part 61.55. The rear passenger reported civil flight experience that included 3,500 total and 65 hours in last six months as of his last medical application dated February 21, 2025. He was issued a second-class medical certificate without limitation.

Weather

The SVH Automated Weather Observing System (AWOS), recorded on the CVR audio, reported the weather at 0945 as wind calm, visibility 10, ceiling 3,900 ft broken, 4,800 ft overcast, temperature 7° C, dewpoint -0° C, altimeter 30.19.

The SVH AWOS, recorded on the CVR audio, reported the weather at 0954 as wind from 050° at 3 knots, visibility 10, 3,900 ft scattered, ceiling 5,000 ft overcast, temperature 7° Celsius, dewpoint 0° C, altimeter 30.19.

The Meteorological Aerodrome Report (METAR), at 1015, reported weather at SVH as: wind calm, visibility of 5 statute miles, heavy drizzle, ceiling broken at 1,200 ft agl, ceiling broken at 2,200 ft agl, overcast clouds at 5,000 ft agl, temperature of 7°C, dew point temperature of 1°C, altimeter setting of 30.19 inHg; Remarks: station with a precipitation discriminator, temperature of 7.2°C and dew point temperature of 1.0°C.

Recorders

The airplane was equipped with a Fairchild GA-100 tape-based cockpit voice recorder (CVR). The CVR was recovered at the accident site by NTSB personnel. Audio recording of the accident flight was successfully downloaded from the CVR. The recorder contained about 31 minutes of analog audio on a continuous loop tape in a four-channel format: one channel for each flight crew and one channel for the cockpit area microphone (CAM) with one spare channel. Audio quality of the recording was poor with low signal-to-noise ratio and extraordinary means were required to make portions of the recording intelligible. The airplane was not equipped with a flight data recorder, nor was it required to be. 

A Garmin GTN-750 was recovered at the accident site by NTSB personnel. The GTN-750 is a combination GPS/Navigation receiver/Radio/Multi-Function display that has the capability of recording some data in non-volatile memory. In its configuration on the accident aircraft the unit recorded about 20 parameters for the full accident flight.

Beechcraft B300 King Air 350i, ANX-1209, fatal accident occurred on December 22, 2025, near Galveston-Scholes International Airport (GLS/KGLS), Galveston, Texas

  • Location: Galveston, TX 
  • Accident Number: WPR26FA067 
  • Date & Time: December 22, 2025, 15:05 Local 
  • Registration: ANX1209 
  • Aircraft: Beechcraft B300 
  • Injuries: 6 Fatal, 2 Serious 
  • Flight Conducted Under: Armed Forces 

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

On December 22, 2025, about 1505 central standard time, a Beechcraft B300, ANX1209, was substantially damaged when it was involved in an accident near Galveston, Texas. The pilot, co-pilot, two flight crew, two passengers were fatally injured and two passengers sustained serious injuries. The airplane was operated by the Mexican Navy.

Review of recorded communications between Houston Approach Control and flight crew revealed that at 2048:24, the flight crew established radio communications with the controller while enroute to the Scholes International Airport (GLS), Galveston, Texas. At 2048:38, the controller advised the flight crew that the approach into GLS would be vectors to final and queried if the flight was a medivac flight, to which the flight crew confirmed. At 2048:40, the controller advised the flight crew to turn 10° right, maintain 3,000 ft, vectors for the ILS. At 2048:49, the approach controller changed the approach clearance to the RNAV approach 14. At 2048:52, the flight crew responded with, “right and 10° right.” At 2049:18, the controller advised the flight crew to descend and maintain 3,000 ft and expect vectors for the RNAV. At 2049:26, the flight crew responded with, maintain 3,000, expect vectors to the runway.

At 2052:43, the flight crew queried the approach controller to determine which runway was in use. At 2052:54, the controller advised the flight crew, that RNAV 14 was in use, and that the GLS tower had advised the ceilings were 300 ft and queried the flight crew if they would like to continue with the approach, to which the flight crew responded with yes. At 2054:28, the controller instructed the flight crew to fly heading 310 descend and maintain 2,000, to which the flight crew responded with, “descend and maintain two three thousand, heading three one zero.” At 2054:42, the controller advised the flight crew, their assigned altitude is 2,000 and the heading was correct, which the flight crew acknowledged. At 2055:08, the controller advised the flight crew that in the event of a missed approach, fly 250 and maintain 2,000 followed by an acknowledgement from the flight crew. At 2055:42, the controller advised the flight crew to reduce speed to 170, which was acknowledged by the flight crew. At 2056:22, the controller advised the flight crew to turn left to a heading of 220 and the flight crew responded with, heading 220. At 2057:34, the controller advised the flight crew to fly heading 150, “to join,” which was acknowledged by the flight crew. At 2057:46, the controller advised the flight crew that because they didn’t make the turn, fly heading 100 “to join,” which the flight crew responded with 100.

At 2058:08 the controller advised the flight crew, once established they were cleared for the RNAV 14, and advised the flight crew a second time at 2058:40, they were cleared for RNAV 14. At 2058:49, the flight crew responded with, cleared to land runway one four. At 2058:53, the controller advised the flight crew that they were not cleared to land, that they were cleared for the RNAV. At 2059:02, the controller advised the flight crew that they were cleared for the RNAV, they were not cleared to land. At 2059:09, the controller advised the flight crew to contact the tower, which was acknowledged by the flight crew. The controller subsequently issued multiple low altitude alerts; however, there received no further radio communication from the flight crew.

Recorded ADS-B data provided by the Federal Aviation Administration (FAA) showed that flight track started about 13 miles northeast of the Merida International Airport (MMMD), Merida, Mexico at 1854:42, the airplane was on a northwest heading, at an altitude of about 12,025 ft mean sea level (msl). The airplane continued to climb to an altitude of about 27,500 ft. At 2034:49 the airplane continued on a northwest heading and initiated a decent to about 3,000 ft msl. At 2049:03 the airplane made a turn to a north – northwest heading and continued to descend. At 2056:39, at an altitude of about 1,950 ft msl, the airplane made a left turn to a southwest heading, consistent with radar vectors for the GPS 14 approach to GLS. At 2057:59, at an altitude of about 1,950 ft msl, the airplane made a left turn to a southern heading, consistent with radar vectors to the final approach course for the GPS 14 approach. At 2059:31, the data showed that the airplane initiated a descent, until ADS-B contact was lost. The last ADS-B target was at an altitude of 275 ft msl, about 3 miles northwest of GLS.

Witnesses near the accident reported hearing an airplane over flying their location. One witness reported that, he heard the sound of the airplane’s engine “pull back” and then go to full power as if they were going to attempt a go-around before the sound stopped. Other witnesses who were on a boat, briefly heard, and then saw the airplane overfly their location, followed by a sound consistent with the airplane impacting the water. Numerous witnesses reported that the weather conditions at the time of the accident was fog with limited visibility.

Recorded weather for GLS at 2215, included wind from 100° at 5 knots, visibility of ¼ statute mile, vertical visibility at 200 ft above ground level (agl), temperature of 69°F and dew point temperature of 69°F, altimeter setting of 30.21 inches of mercury.

Local law enforcement searched for and located the airplane wreckage about ½ mile from the Galveston shoreline in the waters of West Bay at a depth of about 5 to 10 ft. The debris path was oriented on a southern heading and was about 200 ft in length. The fuselage, both wings, engines and empennage were located within the debris path. The airplane was recovered from the water and transported to a secure location for further examination.

Beechcraft A36 Bonanza, N5677X, fatal accident occurred on January 8, 2026, near Sabine Pass, Texas

  • Location: Sabine Pass, TX 
  • Accident Number: CEN26FA086 
  • Date & Time: January 8, 2026, 14:31 Local 
  • Registration: N5677X 
  • Aircraft: Beech A36 
  • Injuries: 1 Fatal 
  • Flight Conducted Under: Part 91: General aviation - Personal

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

https://registry.faa.gov/AircraftInquiry/Search/NNumberResult?NNumberTxt=5677X

On January 8, 2026, about 1431 central standard time, a Beech A36 airplane, N5677X, was substantially damaged when it was involved in an accident near Sabine Pass, Texas. The pilot was fatally injured. The airplane was operated under the provisions of Title 14 Code of Federal Regulations Part 91 as a personal flight.

The airplane departed the Jennings Airport (3R7), Jennings, Louisiana, at 1351, and was en route to the Scholes International Airport (GLS), Galveston, Texas, at an altitude of 6,000 ft mean sea level (msl). The pilot had filed an instrument flight rules flight plan and was in radio communications with Houston Terminal Radar Approach Control (TRACON). At 1430, the pilot was given a clearance to descend to 4,000 ft msl, which was acknowledged by the pilot. ADS-B data showed that about that time, the airplane entered a rain shower followed by a descending right turn before radar contact was lost. A U.S. Coast Guard crew subsequently found the wreckage in a marsh between Salt Lake and Knight Lake following a brief search (see Figure 1).

The debris field consisted of four main sections which were distributed over an area about 360 ft long and 160 ft wide. The first section included the left wing and aileron that had fractured at the wing root. The second section included the outboard right wing separated near the mid spar and the right pilot’s seat. The third section included the propeller, engine, cowling, and cockpit instrumentation which were submerged in the marshy terrain. The final section included the aft cabin and empennage (see Figure 2). Smaller portions of doors, insulation, and aileron were located between the major wreckage areas. There was no evidence of fire. The flaps appeared to be in the retracted position.
The airplane was retained for further examination.

A preliminary review of weather information revealed rain showers were present in the airplane’s route of flight when the right descending turn began (see Figure 3).

Beechcraft K35 Bonanza, N6010E, incident occurred on January 7, 2026, at Prescott Regional/Ernest A Love Field Airport (PRC/KPRC), Prescott, Arizona

  • Location: Prescott, AZ 
  • Accident Number: WPR26LA078 
  • Date & Time: January 7, 2026, 08:09 Local 
  • Registration: N6010E 
  • Aircraft: Beech K35 
  • Injuries: 2 None 
  • Flight Conducted Under: Part 91: General aviation - Instructional 

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

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

On January 7, 2026, at about 0809 mountain standard time, a Beech K35, N6010E, was substantially damaged when it was involved in an accident near Prescott, Arizona. The pilot and flight instructor were not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 instructional flight.

The pilot receiving instruction reported that upon arriving at the Prescott Regional/Ernest A Love Field Airport (PRC), Prescott, Arizona, they conducted an ILS approach to runway 21L. After they completed a touch and go landing and takeoff, they noted a positive rate of climb and retracted the landing gear. At about 50 ft agl, they heard a loud “bang” and observed the airplane’s propellor completely stop. The flight instructor then pushed the control yoke forward to maintain airspeed. Unable to maintain altitude the pilot initiated a gear up forced landing to the remaining runway. During the landing flare the airplane landed hard, which resulted in substantial damage to the fuselage and empennage.

The airplane was recovered for further examination. 

North American AT-6F Texan, N6601C, incident occurred on January 29, 2026, at Arcadia Municipal Airport (X06), Arcadia, 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=N6601C

- History of Flight:
On January 29, 2026, at about 1725 local time, a North American AT-6F Texan, N6601C, registered to Nicholls Aviation LLC out of Dover, Delaware, sustained unknown damage when it was involved in an incident at Arcadia Municipal Airport (X06), Arcadia, Florida. The sole pilot onboard was not injured.

The FAA reported: "Aircraftt landed and the gear collapsed."

- Weather:

METAR KPGD 292153Z 00000KT 10SM CLR 21/M11 A3013 RMK AO2 SLP203 T02061106

METAR KPGD 292253Z 06004KT 10SM CLR 18/M08 A3013 RMK AO2 SLP201 T01781078

Bell 47G-3B, N347BH, accident occurred on January 19, 2026, near Floral City, 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=N347BH

- History of Flight:
On January 29, 2026, at about 1215 local time, a privately-registered Bell 47G-3B, N347BH, was destroyed when it was involved in an accident near Floral City, Florida. The pilot was not injured.

The FAA reported: "The helicopter landed hard in a field under unknown circumstances."

On August 2, 2018, the helicopter was involved in an accident near Custer, South Dakota. At the time, the NTSB determined the cause to be "The pilot's mismanagement of rotor RPM and subsequent forced landing on uneven terrain which led to a dynamic rollover."

Zenith CH601XL Zodiac, N601LL, incident occurred on January 29, 2026, near Daphne, 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=N601LL

- History of Flight:
On January 29, 2026, at about 1204 local time, a privately-registered Zenith CH601XL Zodiac, N601LL, sustained unknown damage in a forced landing near Daphne, Alabama. The pilot was not injured. The flight originated from the Collier Airpark (2AL1), Foley, Alabama, at 1145 LT.

The FAA reported: "Aircraft attempted to land in a field for unknown reasons and came to rest in a ditch." The pilot reported to local news that he believes he had an engine failure. ADS-B data show the airplane cruising through 2,700 ft when it entered a descending 180 turn and ended up in a residential area shortly aftewards.

On January 10, 2026, the following was posted by the registered owner on Facebook regarding N601LL:

"With MOSAIC here — and getting in and out of N601LL becoming more of a challenge - I’m starting to look seriously at a high‑wing Zenith.

For anyone curious, N601LL is a Zenith 601XL with all service bulletins completed, a 650 canopy, Dynon HDX panel, backup D6 EFIS, two‑axis autopilot, and a 2025 Viking 140T. Nice, fast VFR plane that can be IFR with installation of a navigator.

If you want to see how this setup performs, the Viking Aircraft Engines YouTube channel has several flight videos featuring this plane.

Anyone with a comparably equipped Zenith high wing interested in a trade?"

Figure 1: ADS-B exchange track

Robinson R44 Raven II accident occurred on January 29, 2026, near Sullivan, Missouri

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=

- History of Flight:
On January 29, 2026, at about 1300 local time, a Robinson R44 Raven II, registration unknown, sustained substantial damage when it was involved in an accident near Sullivan, Missouri. The pilot and three passengers sustained minor injuries. The local aerial survey flight originated from an unspecified location.

The FAA reported: "Aircraft struck power lines while performing deer survey and crashed in a river." The registration was reported as "pending."

American Champion 8KCAB Super Decathlon, N59SE, accident occurred on January 29, 2026, near Irwin, Idaho

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


- History of Flight:
On January 29, 2026, at about 1430 local time, a American Champion 8KCAB Super Decathlon, N59SE, sustained substantial damage when it was involved in an accident near Irwin, Idaho. The pilot suffered minor injuries.

The FAA reported: "Aircraft made a right turn over dry lakebed, cartwheeled and came to rest inverted in a snowbank."

The pilot reported to local law enforcement: "I was flying low just past the end of the runway when my wing caught the ground during a turn causing the plane to flip over and land upside down in the snow."

Cessna 172S Skyhawk SP, N969FG, incident occurred on January 28, 2026, at Wilmington Airport (ILG/KILG), Wilmington, Delaware

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

- History of Flight:
On January 28, 2026, at about 2044 local time, a Cessna 172S Skyhawk SP, N969FG, registered to Mustang Sally Aviation LLC out of Camden, SC, and being operated by the Infinity Flight Group, sustained minor damage (per FAA) when it was involved in an incident at Wilmington Airport (ILG/KILG), Wilmington, Delaware. The pilot and passenger were not injured. The local flight originated from KILG at 1900 LT.

The FAA reported: "Aircraft landed on a closed runway, lost control damaging the prop and wings." According to ADS-B data, the airplane landed on runway 32. Runway 14/32 was closed per a NOTAM at the time of the event.

Figure 1: ADS-B exchange end of track

- Weather:

METAR KILG 290051Z 00000KT 10SM CLR M09/M17 A3011 RMK AO2 SLP197 T10891172 $

METAR KILG 290151Z AUTO 32004KT 10SM CLR M11/M17 A3011 RMK AO2 SLP196 T11061167 $

Mooney M20C Mark 21, N1392W, incident occurred on January 28, 2026, 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=N1392W

- History of Flight:
On January 28, 2026, at about 1707 local time, a Mooney M20C Mark 21, N1392W, registered to Ocala Aviation Services Inc, sustained unknown damage when it was involved in an incident at Inverness Airport (INF/KINF), Inverness, Florida. The flight originated from Ocala International Airport-Taylor Field (OCF/KOCF), Ocala, Florida, at 1618 LT.

The FAA reported: "Aircraft landed gearup." ADS-B data show that the airplane initiated a go-around during an attempted landing on runway 1 and came for a second landing on the same runway.

- Weather:

METAR KINF 282155Z AUTO 26004KT 7SM CLR 12/00 A3026 RMK AO2

METAR KINF 282215Z AUTO 26005KT 7SM CLR 11/00 A3026 RMK AO2

Rutan Cozy Mk IV, N716CZ, incident occurred on January 28, 2026, at Boca Raton Airport (BCT/KBCT), Boca Raton, 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=N716CZ

- History of Flight:
On January 28, 2026, at about 1612 local time, a privately-registered Rutan Cozy Mk IV, N716CZ, sustained unknown damage when it was involved in a gearup landing at Boca Raton Airport (BCT/KBCT), Boca Raton, Florida. The sole pilot onboard was not injured. The cross-country personal flight originated from Huntsville Executive Airport (MDQ/KMDQ), 
Huntsville, Alabama, at 1136 LT, and was destined to KBCT.

The FAA reported: "Aircraft landed gearup." ADS-B data show that the airplane was on approach to runway 5, went around, and come back for another landing.

- Weather:

METAR KBCT 282053Z 36007G13KT 10SM SCT050 OVC065 19/10 A3015

METAR KBCT 282153Z 34007KT 10SM BKN051 18/06 A3016

Cessna 150L, N67WJ, incident occurred on January 28, 2026, at Donaldson Field Airport (GYH/KGYH), Greenville, South Carolina

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

- History of Flight:
On January 28, 2026, at about 1404 local time, a Cessna 150L, N67WJ, registered to Business As Usual LLC, sustained unknown damage when it was involved in an incident at Donaldson Field Airport (GYH/KGYH), Greenville, South Carolina. The sole pilot onboard was not injured. The flight originated from Spartanburg Downtown Airport (SPA/KSPA), 
Spartanburg, South Carolina, at 1336, and was destined to KGYH.

The FAA reported: "Aircraft nose gear collapsed while doing touch and goes." At the time, winds were from 250° at 11 knots.

Bell 206L-3 LongRanger III, N360DT, accident occurred on August 22, 2025, at Picayune Municipal Airport (MJD/KMJD), Picayune, Mississippi

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

- History of Flight:
On August 22, 2025, at about 1110 local time, a Bell 206L-3 LongRanger III, N360DT, sustained substantial damage when it was involved in an accident at Picayune Municipal Airport (MJD/KMJD), Picayune, Mississippi. The pilot and passenger were not injured. The local flight originated from KMJD.

On January 29, 2026, the FAA reported: "Aircraft lost power while practicing hovering and went into a nose down attitude contacting the ground." It is unknown if the accident was not reported to the FAA originally or not. The accident is not mentioned in the NTSB database.

On December 2025, the helicopter appeared on an online salvage bid with the following stated: "Reported loss of engine N1 at low altitude, (30-40 feet AGL) and unable to auto rotate prior to ground impact.

General Description of Damage: Landing gears are splayed out slightly, left gear mounting bracket penetrated structure, tail boom wrinkled/buckled and cracked; no visual evidence of MRB's, tail rotor, drive shaft or engine damage.

Additional Notes Regarding Logs, Items Missing, Etc.: Total Cycles: 6300 / Total Landings: 13,489; Everything before 2024 is in Spanish as aircraft was in Mexico prior to 2024."

Link: https://mclarens-mediacloud.s3-accelerate.amazonaws.com/2025/11/Salvage-Tender-N360DT.pdf