Tuesday, February 10, 2026

Pipistrel Taurus 503, N414HG, accident occurred on February 9, 2026, near Willis Gliderport (FA44), Boynton Beach, 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=N414HG

- History of Flight:
On February 9, 2026, at about 1515 local time, a privately-registered Pipistrel Taurus 503 glider, N414HG, sustained substantial damage when it was involved in an accident in Boynton Beach, Florida. The pilot sustained serious injuries.

The FAA reported: "Aircraft crashed under unknown circumstances in a yard." and reported the time of the accident as 1157 LT. However, the local sheriff reported the glider came down 100 yards south of the runway at around 1515 local time. The NTSB is investigating.

- Weather:
METAR KLNA 091955Z AUTO 11008G14KT 10SM SCT045 23/08 A3023 RMK AO2 T02320083

METAR KLNA 092015Z AUTO 12010KT 10SM BKN045 BKN055 22/09 A3022 RMK AO2 T02210087

METAR KLNA 092035Z AUTO 13009KT 10SM SCT047 SCT055 23/09 A3022 RMK AO2 T02250088

Cessna 182Q Skylane, N735ZD, accident occurred on October 27, 2025, near James G. Whiting Memorial Field (MEY/KMEY), Mapleton, Iowa

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

- History of Flight:
On October 27, 2025, at about 1400 local time, a privately-registered Cessna 182Q Skylane, N735ZD, reportedly sustained substantial damage when it was involved in an accident in Mapleton, Iowa. The pilot and two passengers were not injured.

On February 10, 2026, the FAA reported: "Aircraft landed in a field shortly after departure due to propeller issues." and rated the damage as substantial and wrote the date of the event as October 29th. A search of the NTSB list did not yield any results for an active investigation involving this aircraft. It is unknown why the FAA report was delayed this much. The event itself was mentioned on an line Facebook group on October 27th.

Turbulence encounter: Boeing 777-222ER, N788UA, accident occurred on February 10, 2024, near Kelsey, New York

  • Location: Kelsey, New York 
  • Accident Number: DCA24LA097 
  • Date & Time: February 10, 2024, 15:43 Local 
  • Registration: N788UA 
  • Aircraft: Boeing 777-222ER 
  • Aircraft Damage: None 
  • Defining Event: Turbulence encounter 
  • Injuries: 3 Serious, 277 None 
  • Flight Conducted Under: Part 121: Air carrier - Scheduled
https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/193784/pdf

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

United Airlines flight 1890 (UAL1890) encountered turbulence during descent into Newark Liberty International Airport (EWR) which resulted in three flight attendants receiving serious injuries. The encounter occurred within a localized region of moderate-to-severe turbulence near flight level (FL) 215 (21,500 feet). The flight was conducted under the provisions of Title 14 Code of Federal Regulations Part 121 as a scheduled domestic passenger flight from Los Angeles International Airport (LAX), Los Angeles, California to EWR.

The flight was in instrument meteorological conditions (IMC) and descending along an air traffic control (ATC) assigned route, toward the Hancock (HNK) VOR. The turbulence encounter resulted in significant cabin vertical accelerations, with quick access recorder (QAR) data showing fluctuations between -0.55 g and +1.82 g over a period of several seconds. Although the flight crew conducted standard preflight turbulence assessments using Weather Services International (WSI) and SkyPath tools, these products depicted only light to moderate turbulence along the planned route. The dispatcher similarly reported only one moderate turbulence report, from a regional jet on descent into EWR, with no updated concerns during the subsequent hours of the flight.

Throughout cruise and initial descent, the flight crew continued monitoring WSI and SkyPath, and neither indicated significant turbulence activity along their descent path. The captain ensured that the onboard radar was active for descent; however, no returns indicating convective or turbulent weather were noted by the flight crew.

ATC did not provide any real-time weather advisories during the period the airplane was under Boston Center’s control, despite receiving a moderate turbulence report from ACA548 (an uninvolved airplane) about three minutes prior to the encounter. ACA548 was operating ahead of UAL1890, on the same route and reported moderate turbulence to the Boston Air Route Traffic Control Center (ZBW ARTCC), R24C controller. The controller did not acknowledge or disseminate this report to other aircraft, including UAL1890, as required by Federal Aviation Administration (FAA) procedures for Pilot Weather Reports (PIREPs) solicitation and dissemination. The controller stated during their interview they did not hear the PIREP. UAL1890 subsequently encountered turbulence in approximately the same area. A turbulence PIREP was transmitted to the flight at 1541 eastern standard time (EST), although it could not be conclusively determined if the crew saw or read the message.

Meteorological analysis revealed that there was a cold front in the vicinity of the accident site along with a relatively strong jet stream of 150 knots near 30,000 ft. The cold front and associated upper level trough provided the support for the formation of a band of rain showers and embedded thunderstorms in western and central New York that was moving eastward with time. The tops of the convection ranged from 21,000 to 23,000 ft in the vicinity of the accident site based on the Geostationary Operational Environmental Satellite number 16 (GOES-16) imagery and pilot statements. Lightning was noted in the convective line encountered by the accident flight in the GOES-16 lightning flash imagery about 20 to 30 minutes prior to the encounter. Figure 1 presents the GOES-16 visible image at 1546 EST at 3X magnification with the accident site highlighted with a red square. There was cloud cover indicated above the accident site with the cloud cover moving from west to east. Figure 2 presents the GOES-16 infrared image at 1546 EST (closest image to the accident time) at 8X magnification with the accident site highlighted with a red square. Cloud cover was indicated above the accident site with lower brightness temperatures (green colors; higher cloud tops) located above and to the northeast through south of the accident site.

In addition, the High-Resolution Rapid Refresh (HRRR) model soundings showed a large change of wind speed between 17,000 ft (around a 45-knot wind) and 21,000 ft (around 110- knot wind) and this caused wind shear and turbulence at the tops of the rain shower/thunderstorm activity. The sounding analysis also indicated moderate or greater clearair  turbulence (CAT) between 18,000 and 21,000 ft near the time and location of the encounter. The turbulence at the tops of the cloud cover is visible on the GOES-16 imagery as evidence by the transverse banding.

UAL1890 checked in with the R24A controller at 1535:10, while level at FL270, but did not receive an immediate response because the controller was occupied with other coordination tasks. As the airplane continued descending under successive clearances, ATC did not pass along the moderate turbulence PIREP issued by ACA548 at 1540:38. This omission reduced the crew’s situational awareness regarding developing turbulence in the same airspace.

When UAL1890 encountered turbulence descending through FL210, the airplane was already committed to the assigned crossing restriction near the HNK VOR. The crew reported the encounter as “severely moderate turbulence,” and ATC also did not respond to that advisory. Shortly thereafter, when handed to the R05 controller, the facility advised of only “light to moderate turbulence,” further indicating that ATC personnel had not fully integrated or disseminated the earlier PIREP information.

QAR data show that autopilot and autothrottle remained engaged throughout the encounter, and the airplane remained within design structural limits. As shown in figure 3, the turbulence generated rapid vertical accelerations and short-duration negative-g forces sufficient to lift unsecured crewmembers from the cabin floor. At the time of the event, the captain had recently re-illuminated the seatbelt sign and instructed the flight attendants to prepare the cabin for landing, a phase during which some flight attendants were completing final safety tasks and not seated. As a result, three crew members were injured.

A peak EDR value of 0.431 was noted as the accident aircraft was in IMC at 1543 EST while descending through both the convective updrafts in the rain shower and thunderstorms and the wind shear layer in the jet stream. This value corresponds to moderate to severe turbulence for a “heavy” class of aircraft.

The evidence indicates the flight crew performed standard preflight and in-flight turbulence risk mitigation, used available tools, and operated the airplane within procedures. The turbulence encountered was not forecast to be significant at the precise altitude, time, and location of the airplane by the operator’s weather provider. Further, the most relevant real-time warning—the moderate turbulence PIREP issued minutes prior—was not disseminated to the flight crew by ATC in accordance with FAA requirements.

The location of the three seriously injured flight attendants (FAs) were two positioned in the aft galley area and one located in the mid-cabin aisle near door 3. FA 2 was lifted into the ceiling and forcefully thrown to the cabin floor, resulting in a spinal fracture. FA 3 was thrown to the ceiling, lost consciousness, struck a beverage cart, and landed heavily on the left leg, sustaining a shattered femur, crushed spinal vertebrae, and a head injury with bleeding. FA 9 was thrown upward and then into galley structures, lost consciousness, and sustained facial lacerations and a diagnosed intracranial bleed.

- Probable Cause: The airplane’s encounter with an unanticipated localized region of moderate-to-severe turbulence while in instrument meteorological conditions (IMC) associated with strong upper-level wind shear and convective cells. Contributing to the severity of the outcome was the failure of air traffic control to disseminate a recently reported moderate turbulence pilot weather report, which reduced the flight crew’s situational awareness and opportunity to prepare the cabin for the encounter.

Piper PA-22-150 Tri-Pacer, N3263Z, accident occurred on February 1, 2026, at Anchorage-Merrill Field (MRI/PAMR), Anchorage, Alaska

  • Location: Anchorage, AK
  • Accident Number: ANC26LA013
  • Date & Time: January 31, 2026, 19:21 Local
  • Registration: N3263Z
  • Aircraft: Piper PA-22-150
  • Injuries: 1 Serious, 1 None
  • Flight Conducted Under: Part 91: General aviation - Personal

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

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

On January 31, 2026, about 1921 Alaska standard time, a Piper PA-22-150 airplane, N3263Z, was substantially damaged when it was involved in an accident near Anchorage, Alaska. The pilot was uninjured, and the passenger was transported to the hospital with potentially serious injuries. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.

According to the pilot, earlier in the evening, he and the passenger departed Kenai Municipal Airport (ENA), Kenai, for a personal flight to Merrill Field Airport (MRI), Anchorage, with about 36 gallons of 100LL aviation fuel onboard. The flight to Anchorage was uneventful. After parking in the transient area, the pilot and passenger left for dinner and later returned to the airplane. The pilot conducted an engine run-up at transient parking and then taxied to Runway 34, where he was instructed to expect a Campbell Departure to the south.

Shortly after takeoff from Runway 34, the airplane experienced a loss of engine power. The pilot maneuvered the airplane in a right-banking turn back toward the runway environment, and the airplane impacted the airport ramp before coming to rest on Taxiway Alpha, about 950 ft northeast of the departure end of Runway 34.


The outboard right wing, beyond the lift strut, and right aileron exhibited spanwise deformation consistent with impact damage. The right main gear collapsed and folded backwards against the fuselage. The nose gear collapsed and folded laterally towards the left side of the fuselage. One propeller blade was curled backwards and had left witness marks on the left side of the cowling.


A security camera at the airport captured video and audio of the airplane’s taxi and takeoff roll. Shortly after the airplane exited the camera frame, the engine can be heard sputtering, followed by a loss of power. Engine power is then momentarily restored before the airplane impacts the ramp area.

An investigator from the National Transportation Safety Board’s (NTSB) Alaska Regional Office responded to the accident site and documented the airplane wreckage. During the on-scene examination, the investigator recovered a data card containing flightpath and engine monitoring data.

The wreckage will be recovered to a secure facility for further examination.

Cessna 170B, N2334D, incident occurred on February 8, 2026, at Warrenton-Fauquier Airport (HWY/KHWY), Warrenton, Virginia

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

- History of Flight:
On February 8, 2026, at about 0932 local time, a privately-registered Cessna 170B, N2334D, sustained unknown damage when it was involved in an incident at Warrenton-Fauquier Airport (HWY/KHWY), Warrenton, Virginia. The pilot and passenger were not injured. The local flight originated from KHWY at 0850 LT.

The FAA reported: "Aircraft landed and veered off the runway impacting a snowbank."

Figure 1: METARs at KHWY in day of incident, relevant ones marked with red