Monday, February 09, 2026

Beechcraft G36 Bonanza, N229TT, accident occurred on February 9, 2026, in Gainesville, Georgia

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

- History of Flight:
On February 9, 2026, at about 1210 local time, a Beechcraft G36 Bonanza, N229TT, registered to AirMart Inc out of Lexington, Kentucky, sustained substantial damage following a forced landing in Gainesville, Georgia. The pilot and passenger and two people on the ground sustained minor injuries. The flight originated from the Lee Gilmer Memorial Airport (GVL/KGVL), 
Gainesville, Georgia.

According to preliminary automatic dependent surveillance-broadcast (ADS-B) data, earlier in the day, at 1043 LT, the airplane departed the Tri-Cities Airport (TRI/KTRI), Bristol/Johnson/Kingsport, Tennessee, and landed at KGVL at 1200 LT. The accident flight originated from the airport 5 minutes later at 1205 LT.

ADS-B data show that the airplane departed runway 5 (asphalt, grooved 8000 x 150 ft) and entered a climbing left turn to an altitude of 3,225 ft. At 1208, the airplane initiated a descending left hand turn about 3.50 miles east of the airport. At 1209:26, the airplane was at 1,700 ft, 90 knots groundspeed, and descending 1150 feet per minute (fpm) roughly 1.85 miles away from the airport when the pilot elected to turn left and land on a busy road. At 1210:02, the last ADS-B return was recorded at 1,000 ft, 74 knots (GS), and -1200 feet per minute rate.

An online video showed the aircraft landing wings level and hard into the road before it rear ended a car, veered left, struck two other cars, spun around before coming to rest upright and 180 degrees opposite to its original travel path.

The road has several wires running across and is located ~0.93 mile from the airport.

The pilot reported to a local news station: "We lost our engine taking off out of Gainesville and realized, tried to glide back, did everything by the book, but realized we weren't gonna make it back with how far out we were, so we came down the road."

Figure 1: Flightaware track ran through Google Earth

Figure 2: Google Earth view of landing location

- Weather:

METAR KGVL 091653Z AUTO 08005KT 10SM CLR 08/M06 A3029 RMK AO2 SLP257 T00781056

METAR KGVL 091753Z AUTO 10SM CLR 09/M05 A3026 RMK AO2 SLP248 T00941050 10094 20000 58016

Wag-Aero J-3 Cub Replica, N437WT, accident occurred on December 26, 2025, near Wimberley, Texas

  • Location: Wimberley, TX 
  • Accident Number: CEN26LA082 
  • Date & Time: December 26, 2025, 16:30 Local 
  • Registration: N437WT 
  • Aircraft: Wag Aero Cuby 
  • Injuries: 1 None 
  • Flight Conducted Under: Part 91: General aviation - Personal

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

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

On December 26, 2025, about 1630 central standard time, a Wag Aero Cuby airplane, N437WT, was substantially damaged when it was involved in an accident near Wimberley, Texas. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.

The pilot stated that while turning from the downwind to the base leg of the traffic pattern, the engine suffered an instantaneous, total loss of power. No indications or abnormalities were observed before the total loss of engine power. The pilot pitched the airplane for the best glide airspeed and set up for a forced landing. He verified that the fuel selectors were both in the “ON” position, the mixture lever was in the full rich position, the carburetor heat was “ON,” and the magneto positions were cycled. The pilot attempted to restart the engine, and engine power was restored for about 3 to 5 seconds before the engine lost total power again.

The pilot stated that the airplane did not have enough altitude to reach the first intended landing point and elected a new landing area. He executed the forced landing in a clearing with small cedar trees. The airplane came to rest upright after impacting several trees, resulting in substantial damage to the left wing.

Both fuel tanks remained intact with no observed fuel leakage, and there was about 1/3 capacity of fuel in each tank.

Flight data logs were recovered from the airplane’s avionics, and the wreckage was retained for further examination.

Tecnam P2012 Traveller, N651CA, accident occurred on November 25, 2024, at Boston-Logan International Airport (BOS/KBOS), Boston, Massachusetts

  • Location: Boston, Massachusetts 
  • Accident Number: ERA25LA060 
  • Date & Time: November 25, 2024, 18:26 Local 
  • Registration: N651CA 
  • Aircraft: COSTRUZIONI AERONAUTICHE TECNA P2012 TRAVELLER 
  • Aircraft Damage: Substantial 
  • Defining Event: Ground collision 
  • Injuries: 2 Minor, 3 None 
  • Flight Conducted Under: Part 135: Air taxi & commuter - Scheduled

https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateFinalReport/195551/pdf

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

At the conclusion of the air taxi flight, the flight crew were taxiing the small twin-engine airplane to their assigned gate at night. The crew were holding short of the gate area and awaiting clearance to enter. After holding for about 10 minutes with the airplane's parking brake set, the flight crew heard a loud noise and the airplane lunged forward when it was stuck from behind by a tug that was towing an unoccupied airliner. The small airplane sustained substantial damage to its elevator and horizontal stabilizer. The tug's windshield was damaged during the collision, and the airliner was not damaged.

Surveillance video showed that the tug's headlights were operating as it drove straight along the taxiway toward the small airplane. The small airplane's wing and tail navigational light were also visible and operating.  As the tug approached the rear of the airplane, its headlights brightened, and its speed abruptly slowed just prior to the impact with the airplane's elevator.

According to the company who operated the tug, following the accident, the driver and safety observer in the tug initially reported that its brakes had “failed' but later described that the brakes were not operating as expected. The tug crew also reported that an “oversteer alarm' had been sounding continuously during their operation of the tug, and that they had reported this to a supervisor prior to initiating the tow of the airliner. They were instructed to complete the tow, after which maintenance personnel would evaluate the reason for the alarm. Following the accident, maintenance personnel performed an operational check of the tug's brakes and noted no anomalies. Further examination revealed that the oversteer alarm was due to a malfunction in the tug's monitoring system.

Given this information it is likely that the tug crew saw the small airplane, but their visual lookout was not sufficient to identify it with sufficient time/distance to stop. While the tug was being operated with an active alarm, this should not have impacted the tug crew's ability to stop the tug while driving straight on a taxiway.

- Probable Cause: The tug crew's inadequate visual lookout while towing an airplane at night and their failure to identify a stationary airplane within sufficient time/distance to stop.

Piper PA-30 Twin Comanche, N7473Y, incident occurred on February 6, 2026, at Palmer Municipal Airport (PAQ/PAAQ), Palmer, Alaska

 This is preliminary information, subject to change, and may contain errors. Any errors in this report will be corrected when the final report has been completed.

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

- History of Flight:
On February 6, 2026, at about 1505 local time, a Piper PA-30 Twin Comanche, N7473Y, registered to Advanced Aero Technologies Group LLC, sustained unknown damage when it suffered a landing gear(s) collapse during landing at Palmer Municipal Airport (PAQ/PAAQ), Palmer, Alaska. The pilot and passenger were not injured. The local flight originated from PAAQ at 1452 LT.

- Weather:

METAR PAAQ 062353Z 21003KT 10SM CLR 01/M03 A2957 RMK AO2 SLP017 T00111028 10022 21022 56022 $=

METAR PAAQ 070053Z 00000KT 10SM CLR 00/M03 A2956 RMK AO2 SLP013 T00001033 $=

Piper PA-32-300 Cherokee Six, N4181W, incident occurred on February 7, 2026, in Lakeside, 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=N4181W

- History of Flight:
On February 7, 2026, at about 1005 local time, a Piper PA-32-300 Cherokee Six, N4181W, registered to Mission Flight out of El Monte, CA, was not damaged in a forced landing in Lakeside, California. The pilot and two passengers were not injured. The flight originated from San Diego-Gillespie Field (SEE/KSEE), 
San Diego, California, at 0959 LT.

The FAA reported: "Aircraft experienced engine issues and made an emergency landing on a highway." ADS-B data show that the airplane climbed to about 1,800 ft before it stopped tracking in the vicinity of the state Route 67.

Piper PA-46-310P Malibu, N9080X, incident occurred on February 8, 2026, at Elkhart Municipal Airport (EKM/KEKM), Elkhart, Indiana

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

- History of Flight:
On February 8, 2026, at about 1636 local time, a Piper PA-46-310P Malibu, N9080X, registered to Non-TS Travel LLC out of Roseville, MN, sustained unknown damage when it was involved in an incident at Elkhart Municipal Airport (EKM/KEKM), Elkhart, Indiana. The pilot was not injured. The flight originated from the Minneapolis-Anoka County-Blaine Airport/Janes Field Airport (ANE/KANE), Minneapolis, Minnesota, at 1435 LT, and was destined to EKM.

The FAA reported: "Aircraft landed in the snow parallel to the runway." ADS-B data show that the airplane was on final approach to runway 18 (asphalt, grooved 3999 x 75 ft) at KEKM (see figure).

Figure 1: ADS-B exchange end of track

- Weather:

METAR KEKM 082115Z AUTO 10007KT 10SM CLR M05/M11 A3034 RMK AO2 T10541111 $

METAR KEKM 082135Z AUTO 10009KT 10SM CLR M05/M11 A3034 RMK AO2 T10541113 $

METAR KEKM 082155Z AUTO 12008KT 10SM CLR M05/M12 A3033 RMK AO2 T10541115 $

Cessna 172RG Cutlass RG, N9706B, incident occurred on February 7, 2026, at Cincinnati Municipal Airport-Lunken Field (LUK/KLUK), Cincinnati, 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=N9706B

- History of Flight:
On February 7, 2026, at about 1645 local time, a Cessna 172RG Cutlass RG, N9706B, sustained unknown damage when it was involved in an incident at the Cincinnati Municipal Airport-Lunken Field (LUK/KLUK), Cincinnati, Ohio. The pilot and passenger were not injured. The flight originated from Clermont County Airport (I69), Batavia, Ohio, at 1535 LT.

The FAA reported: "Aircraft landed gearup." Local media reported that the aircraft experienced a "mechanical failure" causing only one gear to deploy and that the pilot had to make an emergency landing. ADS-B data indicates the airplane conducted one flyby over runway 3R before it came for a second landing.

- Weather:

METAR KLUK 072053Z 34005KT 10SM CLR M05/M16 A3042 RMK AO2 SLP309 T10501156 58001

METAR KLUK 072153Z 01009KT 10SM CLR M06/M16 A3041 RMK AO2 SLP306 T10561156

Figure 1: ADS-B exchange track of entire flight

Piper PA-31-350 T-1020, N41189, Yute Commuter Services, incident occurred on February 7, 2026, at Bethel Airport (BET/PABE), Bethel, Alaska

This is preliminary information, subject to change, and may contain errors. Any errors in this report will be corrected when the final report has been completed.

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

- History of Flight:
On February 7, 2026, at about 1312 local time, Yute Commuter Services flight 189, a Piper PA-31-350 T-1020, N41189, registered to YR-Aircraft Leasing LLC and being operated by Yute Air on a Part 135 on-demand flight, sustained minor damage when it was involved in an incident in Bethel, Alaska. There were no injuries.

The FAA reported: "Aircraft departed, experienced engine issues and requested to return to airport and the engine caught fire during taxi." ADS-B data show that the airplane departed runway 1L and entered a climbing left turn to 1,200 ft before it landed back at the airport. The airplane was observed taxiing to the ramp before data stopped. Winds at the time were from 020° at 21 knots, gusting 31 knots.

- Weather:

METAR PABE 072153Z 02021G31KT 10SM CLR M14/M18 A2956 RMK AO2 PK WND 02032/2107 SLP014 T11391178

METAR PABE 072253Z 02024G31KT 10SM CLR M13/M18 A2956 RMK AO2 PK WND 02031/2200 SLP015 T11331178

Mooney M20R Ovation 2 GX, N567RD, incident occurred on February 8, 2026, at Jackson Regional Airport (MKL/KMKL), Jackson, 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=N567RD

- History of Flight:
On February 8, 2026, at about 0826 local time, a Mooney M20R Ovation 2 GX, N567RD, registered to Franks Properties LLC, sustained unknown damage when it was involved in an incident at Jackson Regional Airport (MKL/KMKL), Jackson, Tennessee. The pilot was not injured. The cross-country personal flight originated from Kosciusko-Attala County Airport (KOXK), 
Kosciusko, Mississippi, at 0729 LT, and was destined to KMKL.

The FAA reported: "Aircraft landed, exited the runway and while taxiing too fast on the ice incurred a prop strike." ADS-B data show that the airplane departed Jackson at 1000 (1h30m after incident) on a flight to Carthage-Leake County Airport (08M), Carthage, Mississippi. It is unknown when the propeller strike was reported to the FAA.

- Weather:

METAR KMKL 081353Z 00000KT 10SM CLR 00/M07 A3029 RMK AO1 SLP260 T00001072 $

METAR KMKL 081453Z 16005KT 10SM CLR 03/M08 A3028 RMK AO1 SLP258 T00331078 50007 $

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

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

- History of Flight:
On February 6, 2026, at about 0815 local time, a Cessna 560XL Citation XLS+, N476JC, registered to Bandyco LLC, sustained substantial damage when it was involved in a runway overrun at Stuart Powell Field (DVK/KDVK), Danville, Kentucky. The pilot and three passengers were not injured. The Part 91 personal flight was destined to Bowling Green-Warren County Airport (BWG/KBWG), Bowling Green, Kentucky.

The FAA reported: "Aircraft slid off the end of the runway during departure." The event was not captured on ADS-B tracking sites, but it happened on runway 31 (5000 x 75 ft). Preliminary information indicates the pilot aborted the takeoff and the aircraft veered to the left, overran the runway, and came to rest in the grass with the landing gear retracted. The flaps were deployed. About 20 minutes before the event, winds were reported from 220 at 8 knots. At the time of the event, winds were from 220 at 8 knots, gusting 14 knots.

On February 10, 2026, the NTSB added the event as an accident on their database (ERA26LA107).

- Weather:

METAR KDVK 061255Z AUTO 22008KT 10SM CLR M02/M05 A2979 RMK AO2

METAR KDVK 061315Z AUTO 22008G14KT 10SM CLR M01/M05 A2977 RMK AO2

METAR KDVK 061335Z AUTO 22007KT 10SM CLR M01/M05 A2978 RMK AO2

Cessna 185D Skywagon, N75LE, incident occurred on February 6, 2026, at Mesa-Falcon Field Airport (FFZ/KFFZ), Mesa, 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=N75LE

- History of Flight:
On February 6, 2026, at about 0857 local time, a Cessna 185D Skywagon, N75LE, was not damaged when it was involved in an incident at Mesa-Falcon Field Airport (FFZ/KFFZ), Mesa, Arizona. The pilot was not injured.

The FAA reported: "Aircraft declared an emergency after takeoff and made an emergency landing in a field." ADS-B data show the airplane taxied from the ramp to runway 4R. During takeoff, the airplane climbed to about 1,350 ft before it entered a descending right hand turn and landed in a vacant field on airport property. The airplane was relocated to the ramp two hours later (see figure).

Figure 1: ADS-B exchange data

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

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://wwwapps.tc.gc.ca/saf-sec-sur/2/ccarcs-riacc/ADet.aspx?id=512888&rfr=RchSimp.aspx

- History of Flight:
On January 19, 2026, at about 1259 local time, a privately, Canadian-registered Cessna 500 Citation I, C-GJVK, sustained substantial damage when it was involved in an accident at Great Falls International Airport (GTF/KGTF), Great Falls, Montana. There there were no injuries. The cross-country flight originated from Idaho Falls Regional Airport (KIDA), 
Idaho Falls, Idaho, at 1152 LT, and was destined to KGTF.

The NTSB added the event on their database recently, case number WPR26LA093, and gave the "defining event" as a landing gear collapse. ADS-B data indicates the airplane landed on runway 21 in bad weather before coming to a halt.

Figure 1: ADS-B exchange data

Glasair GlaStar, N789BM, accident occurred on February 6, 2026, in Beaumont, 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=N789BM

- History of Flight:
On February 6, 2026, at about 1830 local time, a privately-registered Glasair GlaStar, N789BM, sustained substantial damage when it was involved in an accident in Beaumont, Texas. The pilot was not injured.

The FAA reported: "Aircraft experienced loss of oil pressure before landing on taxiway, became airborne briefly before touching down again and striking the airport fence." The NTSB has opened an investigation.

Cirrus SR22, N705CD, fatal accident occurred on February 6, 2026, near Whiteplains Airport (SC99), Lexington, 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=N705CD

Aaron McCarter, NTSB IIC

- History of Flight:
On February 6, 2026, at about 0920 local time, a Cirrus SR22, N705CD, registered to LearjetJohn Flying Club LLC out of Moulton, Alabama, was substantially damaged when it impacted trees and terrain near the Whiteplains Airport (SC99), Lexington, South Carolina. The pilot flying sustained serious injuries, and passenger sustained fatal injuries. The cross-country personal flight originated from the Columbia Metropolitan Airport (CAE/KCAE), 
Columbia, South Carolina, and was destined to Decatur-Pyor Airport (DCU/KDCU), Decatur, Alabama.

According to preliminary automatic dependent surveillance-broadcast (ADS-B) data, at 0905:00, the airplane departed runway 29 at KCAE and proceeded to climb to an altitude of 8,000 ft. At about 0913:30, the airplane initiated a descending left hand turn from that altitude after the pilot reported engine issues. A few moments later, the pilot reported an engine failure and that he was looking for a place to land. The controller gave the pilots vectors to Whiteplains (SC99). At 19:18:25, the airplane was descending through 1,800 ft and was less than a mile from the airport, but was too high and fast for an approach to runway 9. The airplane then entered a right pattern for runway 27. At 0919:27, the airplane was at 1,300 ft when it entered a base-to-final turn for the runway. However, the airplane ended up impacting trees about 1,800 ft short of the runway (see figures).

Figure 1: Overall review of flight (Flightradar24 KML file)

Figure 2: Altitude when aircraft started descent

Figure 3: Approach to SC99

Figure 4

- Pilot Information:
Unknown.

- Airplane Information:
The accident aircraft, MSN 0005, was manufactured in 2001. It was a four-seat low-wing monoplane aircraft of composite construction. It was powered by a 310 HP Continental TSIO-550-K engine driving a three-blade constant speed governor-regulated propeller. The airplane was IFR capable and did not have any known damage history.

According to section 10 of the Pilot Operating Handbook (POH):

"Cirrus Airframe Parachute System (CAPS) The Cirrus Airframe Parachute System (CAPS) is designed to lower the aircraft and its passengers to the ground in the event of a lifethreatening emergency. CAPS deployment is likely to result in damage to the airframe and, possible injury to aircraft occupants, its use should not be taken lightly. Instead, possible CAPS activation scenarios should be well thought out and mentally practiced by every Cirrus pilot. Pilots who regularly conduct CAPS training and think about using CAPS will often have a higher probability of deploying CAPS when necessary. 

The following discussion is meant to guide your thinking about CAPS activation. Cirrus also recommends that pilots discuss CAPS deployment scenarios with instructors as well as fellow pilots through forums such as the Cirrus Owners and Pilots Association. In the event of a spin or loss of aircraft control, immediate CAPS activation is required. (See Section 3) In other situations, CAPS activation is at the informed discretion of the pilot in command. The following discussion is intended to be informative, not directive. It is the responsibility of you, the pilot, to determine when and how the CAPS will be used. It is important to understand, however, that numerous fatalities that have occurred in Cirrus aircraft accidents likely could have been avoided if pilots had made the timely decision to deploy CAPS. It is also important to note that CAPS has been activated by pilots at speeds in excess of 180 knots on multiple occasions with successful outcomes. While the best speed to activate CAPS is below 140 knots indicated airspeed, a timely activation is most important for loss of control situations."

Landing Required in Terrain not Permitting a Safe Landing
"If a forced landing on an unprepared surface is required CAPS activation is recommended unless the pilot in command concludes there is a high likelihood that a safe landing can be accomplished. If a condition requiring a forced landing occurs over rough or mountainous terrain, over water out of gliding distance to land, over widespread ground fog or at night, CAPS activation is strongly recommended. Numerous fatalities that have occurred in Cirrus aircraft accidents likely could have been avoided if pilots had made the timely decision to deploy CAPS. 

While attempting to glide to an airfield to perform a power off landing, the pilot must be continuously aware of altitude and ability to successfully perform the landing. Pilot must make the determination by 2000' AGL if the landing is assured or if CAPS will be required."

General Deployment Information Deployment Speed 

"The maximum speed at which deployment has been demonstrated is 140 KIAS. Deployment at higher speeds could subject the parachute and aircraft to excessive loads that could result in structural failure. Once a decision has been made to deploy the CAPS, make all reasonable efforts to slow to the minimum possible airspeed. However, if time and altitude are critical, and/or ground impact is imminent, the CAPS should be activated regardless of airspeed. Deployment Altitude No minimum altitude for deployment has been set. This is because the actual altitude loss during a particular deployment depends upon the airplane's airspeed, altitude and attitude at deployment as well as other environmental factors. In all cases, however, the chances of a successful deployment increase with altitude. In the event of a spin, immediate CAPS activation is mandatory regardless of altitude. In other situations, the pilot in command may elect to troubleshoot a mechanical problem or attempt to descend out of icing conditions if altitude and flight conditions permit. As a data point, altitude loss from level flight deployments has been demonstrated at less than 400 feet. Deployment at such a low altitude leaves little or no time for the aircraft to stabilize under the canopy or for the cabin to be secured. A low altitude deployment increases the risk of injury or death and should be avoided. If circumstances permit, it is advisable to activate the CAPS at or above 2,000 feet AGL. 

While CAPS activation above 2,000 feet is not necessarily safer than activation at 2,000 feet in terms of the altitude needed to deploy the parachute and slow the descent of the aircraft, there are other risks associated with delaying deployment. Distraction, deterioration in flight conditions, aircraft damage, pilot injury or incapacitation all could take place above 2,000 feet and prevent a timely deployment. 

At any altitude, once the CAPS is determined to be the only alternative available for saving the aircraft occupants, deploy the system without delay."

- Wreckage and Impact Information:
According to the NTSB IIC, the airplane impacted trees about 1800 ft short of runway 27 at  SC99, which resulted in damage to both wingtips. The airplane tumbled out of control and rolled about 200 ft before coming to rest inverted. There was no post accident fire. The Cirrus Airframe Parachute System (CAPS) was not deployed, and the IIC was waiting for a Cirrus representative to arrive on scene to disarm it before the on-scene examination.

- Airport Information:
SC99 sits at an elevation of 524 ft. The airport features a single asphalt runway 9/27.

- Weather:
Weather was reported good at the time of the accident.

METAR KCAE 061356Z 24004KT 8SM CLR 01/M03 A2991 RMK AO2 SLP129 T00061028

METAR KCAE 061456Z 25008KT 10SM CLR 04/M03 A2990 RMK AO2 SLP125 T00391033 58005

- Additional Information:
No