Saturday, February 28, 2026

Cessna 210M Centurion, N707ER, incident occurred on February 24, 2026, at Lake County Executive Airport (LNN/KLNN), Willoughby, Ohio

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

- History of Flight:
On February 24, 2026, at about 2011 local time, a Cessna 210M Centurion, N707ER, registered to Crossbrook LLC, sustained unknown damage when it was involved in an incident at Lake County Executive Airport (LNN/KLNN), Willoughby, Ohio. The pilot was not injured. The flight originated from Delaware Municipal Airport (KDLZ), 
Delaware, Ohio, at 1921 LT.

The FAA reported: "Aircraft executed a go-around and encountered a right wingtip and prop strike."

Remos GX, N88GX, incident occurred on February 26, 2026, at Glendale Municipal Airport (GEU/KGEU), Glendale, Arizona

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

- History of Flight:
On February 26, 2026, at about 1053 local time, a Remos GX, N88GX, registered to N88GX LLC, sustained minor damage when it was involved in an incident at Glendale Municipal Airport (GEU/KGEU), Glendale, Arizona. The pilot was not injured. The local flight originated from KGEU at 1024 LT.

The FAA reported: "Aircraft made a hard landing incurring a prop strike."

- Weather:

METAR KGEU 261651Z 00000KT 10SM CLR 22/06 A3001

METAR KGEU 261651Z 00000KT 10SM CLR 22/06 A3001

Cessna 172R Skyhawk, N57FA, incident occurred on February 26, 2026, at Miami Executive Airport (TMB/KTMB), Miami, 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=N57FA

- History of Flight:
On February 26, 2026, at about 1311 local time, a Cessna 172R Skyhawk, N57FA, registered to Silver Express Co and doing business as Flying Academy.com, was not damaged when it was involved in an incident at Miami Executive Airport (TMB/KTMB), Miami, Florida. The pilot was not injured. The local flight originated from 1059 LT.

The FAA reported: "Aircraft landed and veered off the end of the runway." At 1253, the winds were from 150° at 10 knots. At 1353 LT, the winds were from 130° at 9 knots, gusting 16 knots.

- Weather:

METAR KTMB 261753Z 15010KT 10SM BKN033 OVC042 26/18 A3008 RMK AO2 SLP186 T02560178 10261 20144 58014

METAR KTMB 261853Z 13009G16KT 10SM BKN029 OVC034 25/18 A3005 RMK AO2 SLP176 T02500178

Beechcraft B36TC Bonanza, N2251Q, incident occurred on February 26, 2026, at Durango–La Plata County Airport (DRO/KDRO), Durango, 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=N2251Q

- History of Flight:
On February 28, 2026, 
a privately-registered Beechcraft B36TC Bonanza, N2251Q, sustained unknown damage when it was involved in an incident at Durango–La Plata County Airport (DRO/KDRO), Durango, Colorado. The pilot and passenger were not injured. The cross-country flight originated from River Falls Airport (H81), Amarillo, Texas, at 1454 LT.

The FAA reported: "Aircraft was landing on runway 21 and experienced a crosswind resulting in a runway excursion." The winds were from 290° at 23 knots, gusting 32 knots.

Weather:

METAR KDRO 262253Z AUTO 29023G32KT 10SM CLR 16/M10 A3010 RMK AO2 PK WND 30042/2234 SLP155 T01611100

METAR KDRO 262353Z AUTO 30024G38KT 10SM CLR 14/M13 A3011 RMK AO2 PK WND 30039/2255 SLP167 T01441128 10172 20144 53005

Van's RV-8, N80AR, fatal accident occurred on February 28, 2026, near St. George, 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=N80AR

- History of Flight:
On February 28, 2026, at about 0944 local time, a privately-registered Van's RV-8, N80AR, was destroyed when it was involved in an accident near St. George, Utah. The sole pilot onboard sustained fatal injuries. The local formation flight originated from the Saint George Regional Airport (SGU/KSGU), Saint George, Utah, at 09
41 LT.

The formation included four other aircraft. It is unknown if this formation was headed for a specific location at this point.

ADS-B data show that the airplane departed runway 19 at KSGU and entered a climbing left turn to an altitude of 4,000 ft. The last ADS-B data point was recorded at 0944:04, the airplane was at 4,100 ft, 130 knots groundspeed, with a reported vertical rate of 128 feet per minute. The time of the last ADS-B point matches the time given in the FAA report.

On March 2, the FAA reported: "Aircraft rolled inverted during detachment from a formation flight of 5 and impacted the ground."

The airplane came to rest inverted in open desert ground and was not consumed by a post crash fire. The nose/engine was impact damaged and separated from the airframe. Both wings and tail remained attached to the fuselage.

The pilot's name was not released and is still unknown.

Weather conditions at the time were unremarkable.

- Weather:

METAR KSGU 281556Z AUTO 00000KT 10SM CLR 12/03 A3011 RMK AO2 SLP182 T01170028

METAR KSGU 281656Z AUTO 03004KT 10SM CLR 13/03 A3010 RMK AO2 SLP182 T01280028

Piper PA-22-150 Tri-Pacer, N3170Z, fatal accident occurred on February 28, 2026, near Oroville, 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=N3170Z

- History of Flight:
On February 28, 2026, at about 0950 local time, a privately-registered Piper PA-22-150 Tri-Pacer, N3170Z, was destroyed when it was involved in an accident near Oroville, California. The sole pilot onboard sustained fatal injuries.

There is no ADS-B data for the accident flight. On March 2, 2026, the FAA stated: "Aircraft crashed under unknown circumstances on a road."

While pilot information remains unknown, the registered owner holds a commercial pilot certificate with a rating for airplane single engine land. His second class FAA medical was issued on October 2025, with two notes stating: "Must use corrective lens(es) to meet vision standards at all required distances. Not valid for any class after 04/30/2026."

Friday, February 27, 2026

Epic E1000, N98FK, fatal accident occurred on February 13, 2026, near Steamboat Springs Airport (SBS/KSBS), Steamboat Springs, Colorado

  • Location: Steamboat Springs, CO 
  • Accident Number: CEN26FA115 
  • Date & Time: February 13, 2026, 00:19 Local 
  • Registration: N98FK 
  • Aircraft: Epic E1000 
  • Injuries: 4 Fatal 
  • Flight Conducted Under: Part 91: General aviation - Personal

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

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

On February 13, 2026, about 0019 mountain standard time, an Epic E1000 airplane, N98FK, was substantially damaged when it was involved in an accident near Steamboat Springs, Colorado. The pilot and three passengers were fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.

According to on-board data collected at the accident site, the airplane departed from John C. Tune Airport (JWN), Nashville, Tennessee, about 1910 central standard time to Steamboat Springs Airport/Bob Adams Field (SBS), Steamboat Springs, Colorado, with a fuel stop in Kansas City Downtown Airport-Wheeler Field (MKC), Kansas City, Missouri. The airplane landed at MKC about 2053, was refueled, and departed to SBS about 2303.

According to preliminary air traffic control data, the pilot was given vectors to TILLI, which is the initial approach fix for both the RNAV Z RWY 32 approach and the RNAV – E approach to SBS. The controller cleared the pilot for the RNAV approach to SBS. The pilot acknowledged the clearance but replied, “RNAV 32 to Steamboat Springs.” The controller approved a frequency change to the SBS common traffic advisory frequency to which the pilot acknowledged. No further communications were received from the pilot. An Alert Notice was issued, and a subsequent search for the wreckage was initiated.

The wreckage was located in mountainous terrain about 3 miles south of SBS at an elevation of about 8,200 ft mean sea level (msl). A ground scar was found about 80 ft south of the main wreckage at an elevation of about 8,175 ft msl. The mountain peak is about 8,250 ft msl. The initial impact ground scars were aligned on an estimated 340° true heading. An odor consistent with jet fuel was present at the scene. Postaccident examination of the engine and airframe found no preimpact anomalies that would have precluded normal operation. 

According to the Garmin G1000 data, the engine was producing about 1,700 propeller rpm (Np) and 92% gas generator speed (Ng). All recorded engine parameters were consistent with normal engine operation at the time of the accident. About 100 gallons of fuel remained at the time of the accident. The waypoints in the data were consistent with the RNAV Z RWY 32 approach. The minimum descent altitude for the approach is 9,100 ft msl. The last recorded altitude for the airplane was 8,221 ft msl, and the airplane’s autopilot was engaged.

The RNAV Z 32 approach plate lists that the approach, both the circling and straight-in to runway 32, is not authorized at night. Additionally, the approach plate lists “Visual Segment – Obstacles.”

A review of SBS meteorological aerodrome reports revealed a report issued four minutes before the accident. At 0015, the wind was calm, visibility was 10 statute miles, and scattered clouds were reported 500 ft above ground level (agl), broken clouds 1,600 ft agl, and overcast clouds 2,400 ft agl. Data from FAA weather cameras installed at SBS was collected for further review.

According to FAA airman and operator records, the pilot held a commercial pilot certificate for airplane single-engine land with an instrument rating. He was issued a first-class medical certificate on October 22, 2025, and on the medical application, the airman reported 1,150 total flight hours.

At the time of the accident, there were two Notice to Airmen (NOTAMs) issued for SBS. One listed the runway end identifier lights (REIL) for runway 32 unusable. The other listed the Precision Approach Path Indicator (PAPI) lights for runway 32 unusable. 

The wreckage was retained for further examination.

Cessna 182G Skylane, N515CL, accident occurred on February 16, 2026, at Richards Field Airport (04FA), Homestead, Florida

  • Location: Quail Heights, FL 
  • Accident Number: ERA26LA116 
  • Date & Time: February 16, 2026, 10:20 Local 
  • Registration: N515CL 
  • Aircraft: Cessna 182G 
  • Injuries: 3 None 
  • Flight Conducted Under: Part 91: General aviation - Personal

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

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

On February 16, 2026, at 1020 eastern standard time a Cessna 182G, N515CL, was substantially damaged when it was involved in an accident near Quail Heights, Florida. The pilot and two passengers were not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.

The pilot reported that during the preflight inspection he added a small quantity of fuel to both wing tanks to ensure both were full, then sumped the wing tank drains and the fuel strainer, finding no contamination. Taxi out and runup were normal with no anomalies noted. Shortly after takeoff, the engine lost all power. The pilot decided to return to the airport and conducted a downwind landing opposite the direction of departure. After touchdown, he was unable to stop the airplane, and it overran the runway and subsequently impacted trees. The left wing and fuselage sustained substantial damage.

Post accident examination by the NTSB and FAA found no visible damage to the engine. Engine control continuity was established. Fuel was observed in both wing tanks, the carburetor bowl, and the fuel strainer, which also contained a small amount of particulate contamination. The upper spark plugs were removed and several exhibited sooting on the electrodes.

The wreckage was retained for further examination.

Cessna 182S Skylane, N7276V, accident occurred on February 21, 2026, at Table Rock Airport (MO32), Golden, 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=N7276V

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

- History of Flight:
On February 21, 2026, at about 1131 local time, a Cessna 182S Skylane, N7276V, registered to Legends Air Center LLC, sustained substantial damage when it was accident at Table Rock Airport (MO32), Golden, Missouri. The pilot and three passengers were not injured. The cross-country personal flight originated from Bentonville Municipal Airport/Louise M Thaden Field (VBT/KVBT), Bentonville, Arkansas, and was destined to MO32.

The FAA reported: "Aircraft went off the end of the runway during landing and through a fence." The winds at the time were from 20° at 12 knots. The NTSB is investigating.

Windshear or thunderstorm: Boeing 737-7H4, N247WN, accident occurred on May 2, 2025, near Centerville, Tennessee

  • Location: Centerville, Tennessee 
  • Accident Number: DCA25LA197 
  • Date & Time: May 2, 2025, 12:00 Local 
  • Registration: N247WN Aircraft: Boeing 737 
  • Aircraft Damage: Substantial 
  • Defining Event: Windshear or thunderstorm 
  • Injuries: 149 None 
  • Flight Conducted Under: Part 121: Air carrier - Scheduled

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

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

On May 2, 2025, at 1200 pm central daylight time, Southwest Airlines flight 2231 (SWA2231) encountered turbulence and hail during initial descent into Nashville International airport (BNA), Nashville, Tennessee. The flight was a regularly scheduled passenger flight from AustinBergstrom International airport (AUS) to BNA. As a result of the hail, the airplane sustained substantial damage to the leading edges of the wings and horizontal stabilizer. The flight continued to its destination without further incident.

The flight crew reported that thunderstorm activity was forecast for their arrival at BNA, and they observed weather approaching the airport using a weather application (WSI app) on their electronic flight bag (EFB). They planned and conducted a deviation to the north to avoid the weather. As the airplane passed the Memphis area, the captain asked the flight attendants to be seated early in the event of unforeseen turbulence.

Prior to the encounter, while descending from flight level (FL) 360 toward FL240, the flight had been in clear air and the flight crew could see a cloud build-up at their 1:00 o’clock position. Air Traffic Control (ATC) also advised of “a cell” at their 12:30 to 1:00 o’clock position. However, after reviewing the on-board weather radar and the WSI app on the EFB, those sources did not depict any indications of weather directly ahead of the airplane. As the descent continued, the flight crew noticed below and ahead of the airplane was a flat stratus cloud layer, with no buildups. ATC advised of moderate to extreme precipitation at their 12:30 to 1:00 position, which the crew associated with the buildup they had visually seen at their 1:00 o’clock position.

SWA2231 entered the clouds at about FL320 and initially the ride was smooth, with occasional light chop. While at a speed of 290 knots, at FL280, SWA2231 suddenly encountered precipitation and turbulence. The captain recalled that the rain was very heavy and the excessive noise caused him to suspect hail, but he was unable to verify visually. He retarded the throttles and deployed the speed brake to slow to turbulent air penetration speed. After about 1 minute the heavy precipitation ceased, and the airplane levelled off at FL240, still in instrument meteorological conditions. The flight crew reported the moderate turbulence to ATC and continued to BNA.

A review of weather records revealed that the National Weather Service’s (NWS) Aviation Weather Center had issued Convective SIGMET 99C at 1155 which was extended over the area for an area of severe embedded thunderstorms, moving from 250° at 40 knots, with maximum tops above FL450. Hail to one inch in diameter and wind gusts to 50 knots were possible with the storms. The NWS Storm Prediction Center had issued a severe thunderstorm weather watch at 0956 for a line of severe thunderstorms moving across Tennessee.

Figure 3 shows the nearest WSR-88D weather radar base reflectivity image for the for 3.12° elevation scan at 1202, with SWA2231’s flight track position overlaid at 30 second intervals. The flight passed through an area of extreme intensity echoes up to 65 dBZ at lower elevation scans and 58.5 dBZ at the airplane’s flight level. The severe hail algorithm indicated hail to 1.58 inches in the vicinity of the flight track during the period with the maximum height of the 18.5 dBZ echoes or echo tops to FL446.

Figure 4 is a software analysis cross section of the WSR-88D imagery at 1202, with the approximate flight track of SWA2231 overlaid in white and depicting the flight overflying a maximum reflectivity core of 60 dBZ and in echoes of 56.0 dBZ along the track.

The reason that the severe weather depicted in figures 3 and 4 was not depicted by the onboard weather radar system or the WSI app was not determined. The first officer did not recall the onboard radar system tilt setting(s) used at the time, and the onboard radar imagery was not recorded. The operator had no means to replicate which imagery was available to or used by the crew from the WSI app. The Federal Aviation Administration’s Aviation Weather Handbook notes the following about airborne weather radar:

The radar display also does not provide assurance of avoiding instrument weather conditions from clouds and fog. A phenomenon called attenuation (see Section 15.2.5) may exist when a cell absorbs or reflects all of the radio signals sent by the radar system (see Figure 15-5). Attenuation may prevent the radar from detecting additional cells that might lie behind the first cell. This is sometimes referred to as a radar “shadow.” For aircraft equipped with airborne weather radar, pilots are expected to be familiar with the operating techniques and limitations of the specific system.

It is important to note that while hail always gives a radar echo, it may fall several miles from the nearest visible cloud, and hazardous turbulence may extend to as much as 20 mi from the echo edge.

The severe weather may not have been depicted to the crew on their resources due to radar limitations or the specific settings of the onboard radar (such as tilt and range), rapid development and/or movement of the severe weather, latency in the data provided by the weather application, or other factor(s). There was insufficient evidence available to determine if any of these characteristics were a factor or not.

- Probable Cause: An encounter with hail during descent.

Grumman American AA-5A Cheetah, N9939U, accident occurred on February 23, 2026, near Admire, Kansas

  • Location: Admire, KS 
  • Accident Number: CEN26LA123 
  • Date & Time: February 23, 2026, 09:58 Local 
  • Registration: N9939U 
  • Aircraft: Grumman AA5 
  • Injuries: 2 None 
  • Flight Conducted Under: Part 91: General aviation - Personal

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

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

On February 23, 2026, about 0958 central standard time, a Grumman AA-5A airplane, N9939U, was substantially damaged when it was involved in an accident near Admire, Kansas. The pilot and passenger were not injured. The airplane operated under the provisions of Title 14 Code of Federal Regulations Part 91 as a personal flight.

The airplane was equipped with long-range fuel tanks and the pilot stated that on the day of the accident, he fully fueled the airplane and departed from the Ellington Airport (LUG), Lewisburg, Tennessee. Based on ADS-B data and pilot recollection, the airplane departed LUG about 0440 and flew to Kansas City Downtown Airport – Wheeler Field (MKC), Kansas City, Missouri, landing about 0825. After a brief stop, the airplane departed MKC about 0910 and headed towards Council Grove Airport (K63), Council Grove, Kansas. While the airplane was in cruise flight at 2,500 ft mean sea level, the pilot reported the engine RPM began to increase and then decrease. When the engine power began to decrease, and he switched fuel tanks, but was unable to restore engine power. He performed a forced landing to a field. During the forced landing, the landing gear collapsed, and both wings were substantially damaged.

The airplane was retained for further examination.

Thursday, February 26, 2026

Tecnam P2006T, N964GV, incident occurred on February 9, 2026, at Miami Executive Airport (TMB/KTMB), Miami, 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=N964GV

- History of Flight:
On February 19, 2026, at about 0901 local time, a Tecnam P2006T, N964GV, registered to Coneburripul Corp and being operated ADF Airways, sustained unknown damage when it was involved in an incident in Miami, Florida. The pilot was not injured. The local training flight originated from KTMB at 0855 LT.

The FAA reported: "Aircraft declared an emergency due to a broken aileron and landed safely at TMB." 

Magni Gyro M24 Orion, N678HJ, incident occurred on February 24, 2026, at Denton Enterprise Airport (DTO/KDTO), Denton, 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=N678HJ

- History of Flight:
On February 24, 2026, at about 1430 local time, a Magni Gyro M24 Orion, N678HJ, sustained unknown, but apparent minor damage when it was involved in an incident at Denton Enterprise Airport (DTO/KDTO), Denton, Texas. The pilot was not injured.

The FAA reported: "Aircraft holding short of the runway for departure, encountered a gust of wind that separated the door from the aircraft." According to ADS-B data, the gyro starting taxiing to runway 18L at 1420 LT, and was holding short at 1430 LT, but it taxied back to the ramp at around 1446 LT (see figure).

According to weather information, at 1353 LT, the winds were from 200° at 20 knots, gusting 31 knots. At 1453 LT, the winds from 200° at 25 knots, gusting 34 knots.

According to the Magni M24 Orion Pilot Operating Handbook (POH):

4.8 TAXIING TO THE HOLDING POINT: 

WARNING: Taxiing with the doors closed is recommended if there is a strong wind or wind gusts. This to avoid damage to the doors and/or stress to the locking/hinge system.

4.8.3 CLOSING THE DOORS (Fig. 2) - Grab the frame of the door (1) and lower it; - close the door (1) pulling the knob (2); - engage the pins of the locking system lowering the lock lever (3). Visually check that both pins (front and rear) have engaged securely.

Figure: ADS-B data

Figure 2: POH Info

- Weather:

METAR KDTO 241953Z 20020G31KT 10SM CLR 21/M04 A2988 RMK AO2 PK WND 19032/1930 SLP115 T02111044 $

METAR KDTO 242053Z 20025G34KT 10SM CLR 22/M03 A2983 RMK AO2 PK WND 19034/2048 SLP099 T02171033 56048 $

Piper PA-28-151 Cherokee Warrior, N85RW, accident occurred on February 24, 2026, near College Grove, Tennessee

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

- History of Flight:
On February 24, 2026, at about 1107 local time, a Piper PA-28-151 Cherokee Warrior, N85RW, registered to JKG LLC, sustained substantial damage in a forced landing near College Grove, Tennessee. The pilot sustained unknown, but apparent minor injuries. The training flight originated from Murfreesboro Municipal Airport (MBT/KMBT), 
Murfreesboro, TN, at 0824 LT.

According to ADS-B data, after departure from KMBT, the airplane proceeded west and continued up until 1 hour and 40 minutes later when it conducted one touch-and-go at Jackson Regional Airport (MKL/KMKL), Jackson, TN. The airplane then proceeded east back towards KMBT and was cruising at 7,200 ft when it initiated a rapid descent. Towards the end of the track, the airplane entered a descending right hand turn into a wooded area before coming to rest. The total flight time was roughly 2h45m.

The FAA reported: "Aircraft made a forced landing on a road impacting trees." Photos show that the airplane impacted trees and came to rest upright. Both wings were impact damaged and separated from the airframe. There was no post crash fire. Both propellers remained attached to the propeller hub, which remained attached to the engine. Both propeller blades were straight and shown signs of providing to little to no power on impact.

Figure 1: Airplane Final Rest, note propellers

- Weather:

METAR KMBT 241635Z AUTO 17009KT 10SM CLR 01/M09 A3018 RMK A01

METAR KMBT 241655Z AUTO 20009G15KT 10SM CLR 02/M08 A3016 RMK A01

METAR KMBT 241715Z AUTO 19007KT 160V220 10SM CLR 03/M08 A3015 RMK A01

METAR KMBT 241735Z AUTO 16008KT 10SM CLR 03/M08 A3013 RMK A01

Vans RV-12IS, N46TB, accident occurred on February 24, 2026, at Appleton International Airport (ATW/KATW), Appleton, Wisconsin

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

- History of Flight:
On February 24, 2026, at about 0948 local time, a Vans 12IS, N46TB, registered to Fly Barely LLC out of Manitowoc, WI, sustained substantial damage when it was involved in an accident at Appleton International Airport (ATW/KATW), Appleton, Wisconsin. The pilot and passenger were not injured. The local flight originated from KATW at 0836 LT.

The FAA reported: "Aircraft on a left circling maneuver after an instrument approach and left wing struck the runway." Based on ADS-B data, the airplane was originally on approach to runway 3 when it entered a left circling maneuver for runway 12 as seen in the figure. Winds at the time were from 190° at 14 knots, gusting 18 knots.

Figure: Approach to KATW as seen on Google Earth (ADS-B exchange data)

- Weather:

METAR KATW 241445Z 19014G21KT 10SM SCT120 M04/M09 A2973

METAR KATW 241545Z 18015G22KT 10SM BKN120 M03/M09 A2964 <<<<

METAR KATW 241645Z 19017G24KT 10SM SCT070 BKN110 M02/M09 A2959

Wednesday, February 25, 2026

Cessna 140, N2221V, accident occurred on February 16, 2026, at or around Langlade County Airport (AIG/KAIG), Antigo, Wisconsin

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

- History of Flight:
On February 16, 2026, at an unknown time, a privately-registered Cessna 140, N2221V, sustained substantial damage when it was involved in an accident at or around Langlade County Airport (AIG/KAIG), Antigo, Wisconsin. There were no injuries.

The FAA did report the event in their daily database. However, the NTSB added the event as an accident, case number CEN26LA121, and assigned it as a loss of control on ground.

Bellanca 8GCBC Scout, N5071K, accident occurred on February 13, 2026, at Wilder Airport (6E5), De Smet, South Dakota

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

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

- History of Flight:
On February 13, 2026, at about 1600 local time, a Bellanca 8GCBC Scout, N5071K, sustained substantial damage when it was involved in an accident at Wilder Airport (6E5), De Smet, South Dakota. The sole pilot onboard was not injured. The flight originated from Lee Airport (SD83), De Smet, SD, and was destined to 6E5.

The FAA reported: "Aircraft veered off runway after landing and came to rest in a ditch." The NTSB is investigating.

Beechcraft A36TC Bonanza, N1807F, accident occurred on February 21, 2026, at Manassas Regional Airport/Harry P. Davis Field (HEF/KHEF), Manassas, 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=N1807F

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

- History of Flight:
On February 21, 2026, at about 1716 local time, a Beechcraft A36TC Bonanza, N1807F, registered to Turboflyers Inc, sustained substantial damage when it was involved in an accident at Manassas Regional Airport/Harry P. Davis Field (HEF/KHEF), Manassas, Virginia. The sole pilot onboard was not injured. The flight originated from Waynesboro-Eagle's Nest Airport (W13), 
Waynesboro, Virginia, at 1646 LT.

The FAA reported: "Aircraft nose gear collapsed on landing." But listed the wrong N number as N180F. The NTSB is investigating.

Wrong surface or wrong airport: Embraer 170-100 LR, N772MR, incident occurred on September 25, 2024, at O'Hare International Airport (ORD/KORD), Chicago, Illinois

  • Location: Chicago, Illinois 
  • Incident Number: DCA24LA318 
  • Date & Time: September 25, 2024, 15:26 Local 
  • Registration: N772MR 
  • Aircraft: Embraer ERJ 170-100 LR 
  • Aircraft Damage: None 
  • Defining Event: Wrong surface or wrong airport 
  • Injuries: 68 None 
  • Flight Conducted Under: Part 121: Air carrier - Scheduled

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

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

On September 25, 2024, about 1526 central daylight time (CDT), Envoy Airlines flight 3936 (ENY3936), an Embraer 170-100 LR, N772MR, was cleared for the instrument landing system (ILS) approach to land on runway 10C at Chicago O’Hare International Airport (ORD), Chicago, Illinois, but the flight crew landed on runway 10L instead. None of the 68 occupants aboard the airplane were injured, and the airplane was not damaged. The regularly scheduled passenger flight was operating under the provisions of Title 14 Code of Federal Regulation Part 121 from Norfolk International Airport (ORF), Norfolk, Virginia, to ORD.

This incident occurred when the flight crew of Envoy Airlines flight 3936 (ENY3936), an Embraer 170-100 LR, was cleared for a visual approach to land on runway 10C at Chicago O’Hare International Airport (ORD), Chicago, Illinois, however, the flight crew inadvertently landed on runway 10L.

While on descent and upon initial check-in with the ORD approach controller, the flight crew was instructed to expect runway 10C. They were subsequently cleared for the instrument landing system (ILS) to runway 10C. The flight crew acknowledged and correctly read back the approach clearance.

The flight crew stated that the captain, who was the pilot monitoring, briefed the approach, programmed the flight management computer (FMC) with the ILS approach to runway 10C to back up the planned visual approach. However, they were not receiving the ILS identifier. The captain attempted to troubleshoot why the localizer frequency would not autotune by reloading the approach in the FMC and manually tuning the frequency. Unable to resolve the issue they elected to proceed visually.

The captain contacted the air traffic control tower (ATCT) controller stating they were on the visual approach to runway 10C, and the airplane was cleared to land on runway 10C. However, the airplane was aligned with and landed on runway 10L. The flight crew’s decision to continue the approach without the correct ILS frequency was likely affected by their task saturation and planned continuation bias, and their inability to perceive and efficiently integrate available information.

Planned continuation bias is an unconscious cognitive phenomenon to continue with the original plan in spite of changing conditions. Once a plan is made and committed to, it becomes increasingly difficult for stimuli or changing conditions to be recognized as necessitating a change to the plan. In addition, as workload increases conditions that may appear obvious to individuals external to the situation are difficult for people caught up in the plan to recognize.

Recorded data from the flight data recorder revealed that while flying a heading to intercept the ILS 10C, the localizer frequency in the Nav 1 radio was correctly tuned to 108.95 MHz, the frequency for the ILS 10C localizer, for four seconds. Subsequently, the Nav 1 radio was changed to 108.4 MHz and Nav 2 radio was changed to 113.0 MHz for the remainder of the flight. Although the correct ILS frequency (108.95 MHz) was briefly tuned in the Nav 1 radio, it was subsequently changed to an incorrect frequency (108.4 MHz), and Nav 2 was tuned to a non-ILS frequency (113.0 MHz), preventing the crew from confirming alignment with runway 10C.

The FAA mandatory occurrence report (MOR) revealed that the ATCT controller noticed the runway alignment error and coordinated with the runway 10L controller to allow ENY3936 to land on the incorrect runway as no traffic conflicts were noted. The air traffic control (ATC) services provided by the controller were deficient and contrary to FAA directives. Specifically, the controller failed to notify ENY3936 of their alignment error and did not issue control instructions to prevent the wrong surface landing. Had the controller notified the flight crew of the alignment error or provided control instructions it is likely that the wrong surface landing would have been prevented.

- Probable Cause: The flight crew’s misidentification of the intended landing runway, which resulted in an approach to and landing on the wrong runway due to their planned continuation bias. Contributing to the incident was the flight crew’s decision to continue the approach without the correct ILS frequency in the FMS. Also contributing was air traffic control’s failure to notify the flight crew that the were lined up with the incorrect runway contrary to FAA directives.

Airbus A330-343 (P2F), N5827K, accident occurred on January 28, 2026, at Cincinnati/Northern Kentucky Airport (CVG/KCVG), Hebron, Kentucky

  • Location: Hebron, KY 
  • Accident Number: DCA26LA106 
  • Date & Time: January 28, 2026, 15:05 Local 
  • Registration: N5827K 
  • Aircraft: Airbus A330-343 
  • Injuries: 2 None 
  • Flight Conducted Under: Part 121: Air carrier - Non-scheduled 

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

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

On January 28, 2026, at 1505 eastern standard time, Alaska Airlines flight 2616, an Airbus 330- 343, N5827K, powered by two Rolls Royce RB211 engines, struck birds during initial climb after takeoff from Cincinnati/Northern Kentucky International Airport (CVG), Hebron, Kentucky. There were no injuries to the 2 crew on board. Alaska Airlines operated the airplane as a Title 14 Code of Federal Regulations Part 121 domestic cargo flight for Amazon.com Services LLC and was destined for George Bush Intercontinental Airport (IAH), Houston, Texas.

According to the flight crew, after takeoff from runway 27, while climbing through 900-1,000 ft, the captain observed a flock of geese flying from right to left. The captain, who was the pilot monitoring, called out “birds” and then the flight crew felt multiple birds impact the left and right side of the airplane. At that time, the flight crew observed the electronic centralized aircraft monitor (ECAM) warning and a master caution indication. The flight crew observed the ENG 1 FAULT indication on the ECAM, immediately followed by ENG 1 FAIL. The flight crew initiated the ECAM procedures for the No. 1 (left) engine failure. The captain alerted air traffic control (ATC) of the birdstrike, declared an emergency, and requested a return to CVG.

ATC provided vectors for landing on runway 36R. During the air return, the flight crew observed smoke entering the cockpit and subsequently a MD (main deck) SMOKE ECAM message. The flight crew donned their oxygen masks and began to run the quick reference handbook (QRH) procedure for the MD SMOKE indication. After configuring the airplane for landing, the flight crew determined the smoke had dissipated and removed their oxygen masks for the remainder of the approach and landing.

After landing, the first officer, who was the pilot flying, stopped the airplane on the runway and airport rescue and firefighting (ARFF) personnel inspected the airplane. The flight crew completed the left engine failure ECAM procedures and discharged fire extinguishing agent. After determining that there was no fire on the airplane, ground personnel  owed the airplane to the ramp. Airport operations personnel stated that they recovered the remains of eight Canada geese after the event.

A postaccident examination of the airplane revealed bird remnants on the left main landing gear door and strut, the left-wing inboard flap, the No. 2 (right) engine pylon, the right-wing leading-edge slat and slat track. Additionally, both engines exhibited evidence of bird ingestion. Damage and bird remnants were observed on the left engine nacelle (inside and outside of the inlet) and fan blades. The left engine fan had restricted rotation and was visibly misaligned. The right engine had damage to the inlet cowl acoustic liner and bird remnants were found on the spinner and the exhaust nozzle. The right engine fan rotated freely.

As part of the investigation process, the NTSB invited qualified parties to participate in the investigation, including the Federal Aviation Administration (FAA) and Alaska Airlines. In accordance with the provisions of Annex 13 to the Convention on International Civil Aviation, Accredited Representatives from the Bureau of Enquiry and Analysis for Civil Aviation Safety (BEA) of France, the State of Manufacture for the airplane, the Air Accidents Investigation Branch (AAIB) of the United Kingdom, the State of Manufacture for the engines, and the German Federal Bureau of Aircraft Accident Investigation (BFU), the State of Design for the engines, were appointed to support the investigation, with Airbus , Rolls Royce, , and European Union Aviation Safety Agency (EASA) as technical advisors. The following NTSB specialists were assigned to investigate the accident: Airports, Powerplants, and Flight Data Recorder (FDR).

The investigation is ongoing.

Tuesday, February 24, 2026

Piper PA-30-160 Twin Comanche B, N811LE, incident occurred on February 23, 2026, at Big Bear Airport (L35), Big Bear City, 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=N811LE

- History of Flight:
On February 23, 2026, at about 1800 local time, a privately-registered Piper PA-30-160 Twin Comanche B, N811LE, sustained unknown damage when it was involved in an incident at Big Bear Airport (L35), Big Bear City, California. The pilot and passenger were not injured. The personal flight originated from San Diego-Montgomery-Gibbs Executive Airport (MYF/KMYF), 
San Diego, California, at 1720 LT.

The FAA reported: "Aircraft gear collapsed on landing." ADS-B data show that the airplane was landing on runway 8.

- Weather:

METAR KL35 240135Z AUTO 26004KT 10SM CLR 08/M03 A3032 RMK AO2

METAR KL35 240155Z AUTO 00000KT 10SM CLR 06/M03 A3033 RMK AO2

METAR KL35 240215Z AUTO 00000KT 10SM CLR 03/M03 A3033 RMK AO2

Piper PA-28RT-201 Arrow IV, N279SR, incident occurred on February 23, 2026, at Glencoe Municipal Airport (GYL/KGYL), Glencoe, Minnesota

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

- History of Flight:
On February 23, 2026, at about 1723 local time, a Piper PA-28RT-201 Arrow IV, N279SR, registered to Metro Aircraft CO, landed gearup on an unknown runway at Glencoe Municipal Airport (GYL/KGYL), Glencoe, Minnesota. The two occupants onboard were not injured. The flight originated from Minneapolis-Flying Cloud Airport (FCM/KFCM), 
Minneapolis, Minnesota, at 1609 LT

- Weather:

METAR KGYL 232315Z AUTO 11004KT 10SM CLR M07/M13 A3029 RMK AO2 T10751130

METAR KGYL 232335Z AUTO 10007KT 10SM CLR M08/M13 A3028 RMK AO2 T10811133

Grumman American AA-5A Cheetah, N9939U, incident occurred on February 23, 2026, near Harveyville, Kansas

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

- History of Flight:
On February 23, 2026, at about 0952 local time, a privately-registered Grumman American AA-5A Cheetah, N9939U, sustained unknown damage in a forced landing near Harveyville, Kansas. The pilot and passenger were not injured. The cross-country personal flight originated from Charles B. Wheeler Downtown Airport (KMKC), Kansas City, Missouri, at 0911 LT.

The FAA reported: "Aircraft experienced engine issues and crashed in a field." ADS-B data shows that the airplane entered a descent from its cruise altitude of 2,500 ft at around 0944 LT. The airplane entered a series of maneuvers before it landed in a cornfield in the vicinity of Converse Farm Landing Strip (SN47), Harveyville, Kansas.

- Weather:

METAR KFOE 231453Z 03005KT 10SM CLR M09/M14 A3065 RMK AO2 SLP396 T10941144 51003

METAR KFOE 231553Z 03006KT 10SM CLR M07/M14 A3064 RMK AO2 SLP393 T10721144

METAR KFOE 231653Z 05006KT 10SM CLR M06/M14 A3063 RMK AO2 SLP387 T10611144

Piper PA-28-140 Cherokee, N55428, incident occurred on February 21, 2026, in Heath, Ohio

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

Photo: Christopher Calhoun on FB

- History of Flight:
On February 21, 2026, at about 1342 local time, a Piper PA-28-140 Cherokee, N55428, registered to Flight Gear Aviation LLC, was not damaged in a forced landing in Heath, Ohio. The flight instructor and student pilot were not injured. The local training flight originated from Licking County Regional Airport (VTA/KVTA), Heath, Ohio, at 1310 LT.

The FAA reported: "Aircraft lost engine power on takeoff and made an emergency landing in a field." While ADS-B did not capture the "takeoff", it appears the incident occurred during an attempted go-around from runway 27. The airplane was last seen on final approach to the same runway, and was presumably landed in an open field ~1 mile west of the airport.

Hughes 269A, N1020S, accident occurred on February 21, 2026, in Gettysburg, Pennsylvania

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

- History of Flight:
On February 21, 2026, at about 1230 local time, a Hughes 269A, N1020S, "Registration Pending", sustained substantial damage when it was involved in an accident in Gettysburg, Pennsylvania. The two occupants onboard sustained unknown injuries.

The FAA reported: "Aircraft impacted a hangar while hovering and came to rest on its side."

Beechcraft V35B Bonanza, N9AB, and Piper PA-28-140 Cherokee, N6780W, accident occurred on February 1, 2026, at Odessa-Schlemeyer Field (ODO/KODO), Odessa, Texas

  • Location: Odessa, TX 
  • Accident Number: CEN26LA103 
  • Date & Time: February 1, 2026, 14:30 Local 
  • Registration: N95AB (A1); N6780W (A2) 
  • Aircraft: Beech V35B (A1); Piper PA28 (A2) 
  • Injuries: 2 None (A1); 2 None (A2) 
  • Flight Conducted Under: Part 91: General aviation - Instructional (A1); Part 91: General aviation - Personal (A2) 

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

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

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

On February 1, 2026, about 1430 central standard time, a Beech V35B, N9AB, and a Piper PA28-140, N6780W, were substantially damaged when they were involved in an accident near Odessa, Texas. None of the occupants, 2 in each airplane, were injured. Both airplanes were operated as Title 14 Code of Federal Regulations Part 91 personal flights.

According to a statement from the pilot of N9AB, about 10 nautical miles from Odessa Airport-Schlemeyer Field (KODO), Odessa, Texas, when he had KODO in sight, he cancelled his IFR flight plan, checked the automated weather observing system (AWOS), and made an announcement on the common traffic advisory frequency (CTAF) for KODO. He reported that he flew over the airport at 4,500 feet msl, entered a left downwind for runway 11 and transmitted, “N9AB on downwind for 11.” He reported having made a normal landing on runway 11, and when he started to apply the brakes, he noticed a single-engine airplane on the runway. The pilot immediately applied full power and raised the nose of the airplane to get off the ground and avoid the other airplane. He felt the undercarriage of his airplane impact the other airplane, and subsequently he lost control of the airplane.

According to the statement from the pilot of N6780W, he planned to take off from runway 20 and was monitoring the CTAF. According to the pilot the fixed-base operator had told N95AB runway 20 was the favored runway and that N95AB had acknowledged to use runway 20 to land. He heard no further radio transmissions from N95AB. He proceeded northbound toward runway 20 and had to cross two runways. He stated that before crossing each runway, “we visually cleared both directions and detected no traffic.” He then went on to say, that while crossing runway 11/29, “we again looked right, then left, and at that moment caught a brief glimpse of an approaching aircraft.” At that time, he stated his airplane was about three quarters of the way across the runway. Full braking was applied to avoid the oncoming airplane but despite braking his airplane was struck by N95AB which appeared to be attempting a landing or possible go around on runway 11.

On site examination of the airplanes showed that N95AB went through the windscreen of N6780W and struck the instrument panel and other structure which resulted in substantial damage to the fuselage forward of the cockpit a-pillars. N95AB was substantially damaged and came to rest off the side of the runway with its left wing partially separated.

Cessna 560XL Citation XLS+, N476JC, accident occurred on February 6, 2026, at Stuart Powell Field (DVK/KDVK), Danville, Kentucky

  • Location: Danville, KY 
  • Accident Number: ERA26LA107 
  • Date & Time: February 6, 2026, 09:25 Local 
  • Registration: N476JC 
  • Aircraft: Cessna 560 
  • Injuries: 4 None 
  • Flight Conducted Under: Part 91: General aviation - Personal 

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

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

On February 6, 2026, about 0925 eastern daylight time, a Cessna 560XL, N476JL, was substantially damaged when it was involved in an accident near Danville, Kentucky. The two flight crew and two passengers were not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.

According to the pilot, the planned flight was from Stuart Powell Field Airport (DVK), Danville, Kentucky, to Bowling Green-Warren County Regional Airport (BWG), Bowling Green, Kentucky. After picking up a passenger at BWG they intended to continue to Fort Wayne International Airport (FWA), Fort Wayne, Indiana. The pilot and copilot performed the preflight walk-around inspection using the checklist. The preflight paperwork was completed and the weather was checked for both airports. They added 5,000 lbs. of fuel, resulting in a projected takeoff weight of 18,000 lbs.

During taxi to the 5,000-ft-long runway, the before takeoff checklist was completed, which included verifying and checking flight control position and movement. No anomalies were noted with the airplane, and the takeoff roll was initiated. At 103 kts, the pilot pulled back on the yoke; however, the airplane did not rotate and all three landing gear remained on the runway. He verified the airspeed was above 103 kts; however, the airplane would not rotate, so he decided to abort the takeoff.

The pilot applied maximum braking and deployed the thrust reversers. The airplane began to slow down but he knew insufficient runway remained to stop. The airplane contacted a snow berm at the end of the runway and all three landing gear collapsed. The airplane then traveled about 450 ft before coming to rest in a field. The main landing gear were forced up through the wings, which resulted in substantial damage.

The airplane was retained for further examination. 

Cessna 500 Citation I, C-GJVK, accident occurred on January 19, 2026, at Great Falls International Airport (GTF/KGTF), Great Falls, Montana

  • Location: Great Falls, MT 
  • Accident Number: WPR26LA093 
  • Date & Time: January 19, 2026, 13:03 Local 
  • Registration: C-GJVK 
  • Aircraft: Cessna 500 
  • Injuries: 2 None 
  • Flight Conducted Under: Part 91: General aviation - Personal 

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

https://wwwapps.tc.gc.ca/saf-sec-sur/2/ccarcs-riacc/ADet.aspx?id=512888&rfr=RchSimp.aspx

On January 19, 2026, about 1303 mountain standard time, a Cessna 500 airplane, C-GJVK, was substantially damaged when it was involved in an accident at Great Falls International Airport (GTF), Great Falls, Montana. The pilot and passenger were not injured. The airplane was operated as a Title 14 Code of Federal Regulations personal flight.

The pilot reported that during the approach he extended the landing gear and received an unsafe indication for the left main landing gear while the nose gear and right main landing gear indicated down and locked. He then moved the landing gear lever slightly and received a down and locked indication for the left main landing gear. All three landing gear down and locked lights were illuminated for the remainer of the approach. The landing was smooth and as the airplane slowed to about 30 knots, the pilot felt the left wing begin to lower and the left wing and flap then contacted the runway. The airplane veered slightly to the left and came to rest with the left wing over the grass and with the left main landing gear collapsed.

Postaccident examination revealed that the airplane’s left wing sustained substantial damage. The airplane was recovered and retained for further examination.