Friday, March 13, 2026

Aerodynamic stall/spin: Cirrus SR20, N1108T, accident occurred on March 1, 2024, at Ocean Reef Club Airport (07FA), Key Largo, Florida

  • Location: Key Largo, Florida 
  • Accident Number: ERA24LA126 
  • Date & Time: March 1, 2024, 12:43 Local 
  • Registration: N1108T 
  • Aircraft: CIRRUS DESIGN CORP SR20 
  • Aircraft Damage: Substantial 
  • Defining Event: Aerodynamic stall/spin 
  • Injuries: 1 Serious 
  • Flight Conducted Under: Part 91: General aviation - Personal

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

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

On March 1, 2024, about 1243 eastern standard time, a Cirrus SR20, N1108T was substantially damaged when it was involved in an accident in Key Largo, Florida. The pilot was seriously injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. 

The pilot was attempting to land on a 4,451-ft-long, 70-ft-wide asphalt runway. A right 60° quartering crosswind prevailed at 10 knots, gusting to 16 knots. The pilot reported that he selected full flap extension (100%) and turned onto the final leg of the airport traffic pattern at 600 ft. Just above touchdown, while in the landing flare, the airplane drifted to the left due to a wind gust. He announced and initiated a go-around and gained altitude. The propeller and landing gear then struck the top of a tree and he lost control of the airplane. The airplane subsequently came to rest on a golf course adjacent to the runway.

Data downloaded from the airplane’s remote data module, and a postaccident examination of the wreckage, did not reveal evidence of any preimpact mechanical malfunctions. Review of airport security video revealed the airplane in about a 45° left crab to the runway, at very low altitude, with flaps fully retracted, as it entered an aerodynamic stall to the left and impacted terrain. The airplane’s flight manual indicated that the flaps should be set at 50% extension for a go-around procedure. Based on this information, the pilot’s full retraction of the flaps during the attempted go-around resulted in a loss of lift, sink, and aerodynamic stall at an altitude too low for recovery.

- Probable Cause: The pilot’s improper go-around technique, which resulted in an aerodynamic stall at an altitude too low for recovery.

Thursday, March 12, 2026

Cessna A185F Skywagon, N7574N, fatal accident occurred on February 15, 2026, near Everglades City, Florida

  • Location: Everglades City, FL 
  • Accident Number: ERA26FA115 
  • Date & Time: February 15, 2026, 11:55 Local 
  • Registration: N7574N 
  • Aircraft: Cessna A185 
  • Injuries: 1 Fatal, 1 Serious 
  • Flight Conducted Under: Part 91: General aviation - Personal 

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

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

On February 15, 2026, about 1155 eastern standard time, a Cessna A185F, N7574N, was substantially damaged when it was involved in an accident near Everglades City, Florida. The pilot was seriously injured, and the passenger was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.

According to preliminary ADS-B data, the airplane departed from Marco Island Executive Airport (MKY), Marco Island, Florida at 1116 and flew southeast toward the coastline. The airplane followed the coastline and performed multiple turns until it reached Pavilion Key, Florida. After flying over Pavilion Key, the airplane turned northwest and proceeded back up the coastline. About 5 miles west of Everglades City, Florida, the airplane made multiple low altitude maneuvers while flying over the Ten Thousand Islands portion of the Everglades National Park. The last ADS-B data point was about .5 mile east of the accident site.

The airplane was located in the Ten Thousand Islands portion of the Everglades National Park upside down in the water. At high tide, it was observed that only the floats of the airplane were above the water line, during low tide, the floats and about half of the airplane’s fuselage were above the water line. The airplane was equipped with amphibious landing gear which was found in the “UP” (water landing) position. The water rudders were also found in the “UP” position. During the recovery of the wreckage, the airplane was turned upright, onto its floats, and towed to shore. The floats supported the weight of the airplane for several hours during the tow. After recovery, a postaccident examination of the wreckage revealed the airplane had sustained substantial damage to the fuselage, with the majority of the damage contained to the forward portion of the airplane.

Flight control continuity was established from the cockpit to all associated flight controls by manipulating the cockpit controls and observing corresponding surface movement. Binding was noted in the rudder pedals consistent with damage to the right water rudder sustained during recovery. No other flight controls exhibited unusual resistance. The flap handle was impact damaged and found in the 1st detent which is equal to 10° of flaps; however, the flaps operated normally. The horizontal stabilizer trim jack screws were measured to be 5.5 inches and was near the nose up stop.

The airplane was equipped with a 3-point shoulder harness seatbelt system for the front seats. The pilot side restraint remained attached to its installation points and was undamaged. The belt buckle was found unlatched and operated normally during testing. The copilot side restraint system remained attached to its attach points, and one of the harness restraints was cut. The belt buckle was found unlatched and operated normally during testing. The pilot seat was equipped with the inertia reel secondary seat stop, which functioned normally during testing.

The wreckage was retained for further examination.

Pipistrel Taurus 503, N414HG, accident occurred on February 9, 2026, at Willis Gliderport (FA44), Boynton Beach, Florida

  • Location: Boynton Beach, FL 
  • Accident Number: ERA26FA110 
  • Date & Time: February 9, 2026, 15:14 Local 
  • Registration: N414HG 
  • Aircraft: Pipistrel TAURUS 503 
  • Injuries: 1 Serious 
  • Flight Conducted Under: Part 91: General aviation - Personal

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

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

On February 9, 2026, about 1514 eastern standard time, a Pipistrel Taurus 503 motorglider, N414HG, was substantially damaged when it was involved in an accident at Willis Gliderport (FA44), Boynton Beach, Florida. The pilot was seriously injured. The motorglider was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.

Video with audio from a Ring camera captured the motorglider taxiing to the west end of the gliderport where it stopped facing east with the engine running for about 2 minutes and 10 seconds. The audio captured the sound of the engine rpm increasing followed by the motorglider beginning the takeoff roll. The video captured the motorglider rotating about 570 ft down the runway, the motorglider exited the camera’s field of view but the audio continued to record.

A pilot rated witness located inside his residence on the north side of the gliderport about 1,900 ft east of the western edge of the runway reported hearing the motorglider depart. When the motorglider was past his house he heard the engine quit. He went outside and observed it flying in a westerly direction about 350 ft south of the runway at an altitude of between 200 and 300 ft. He noted the engine was extended but was not running. The motorglider continued to the west a “few hundred feet” before banking to the right; the right wing dropped, and the glider descended in a nose-low attitude while rotating to the right. The motorglider impacted the ground in a near vertical position and fell back, coming to rest upright.

Postaccident examination of the motorglider which was equipped with an airframe rescue parachute revealed it was not deployed and a safety pin was in the emergency parachute release handle.

The wreckage was retained for further examination.

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

  • Location: Mapleton, IA 
  • Accident Number: ANC26LA020 
  • Date & Time: October 29, 2025, 12:00 Local 
  • Registration: N735ZD 
  • Aircraft: Cessna 182Q 
  • Injuries: 4 None 
  • Flight Conducted Under: Part 91: General aviation - Personal 

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

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

On October 29, 2025, at about 1200 Central daylight time, a Cessna 182Q, N735ZD, was substantially damaged when it was involved in an accident near Mapleton, Iowa. The pilot and three passengers were not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91personal flight.

The pilot reported that during takeoff, just after liftoff, one propeller blade lost pitch control, and the airplane was unable to climb. He said that the stall warning horn continued to sound after liftoff, and a passenger described a loud buzzing sound starting before liftoff. The airplane subsequently impacted an area of rising terrain in a harvested bean field, sustaining substantial damage to the fuselage.

After the accident, the pilot told his passengers that he needed to get the airplane back to the airport, and the passengers demanded to get out, exited the airplane and called 911. Without shutting down the engine, the pilot taxied the airplane down the hill and made an unsuccessful takeoff attempt on the flat open field.

A post examination of the wreckage is pending. 

Tuesday, March 10, 2026

Bell 407, N56AZ, fatal accident occurred on February 4, 2026, in Flagstaff, Arizona

  • Location: Flagstaff, AZ 
  • Accident Number: WPR26FA098 
  • Date & Time: February 4, 2026, 22:16 Local 
  • Registration: N56AZ 
  • Aircraft: Bell 407 
  • Injuries: 2 Fatal 
  • Flight Conducted Under: Public aircraft

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

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

On February 4, 2026, at 2216 mountain standard time, a Bell 407 helicopter, N56AZ, was substantially damaged when it was involved in an accident near Flagstaff, Arizona. The pilot and tactical flight officer (TFO) were fatally injured. The helicopter was operated as a Title 14 Code of Federal Regulations Part 91 public use flight.

The pilot and TFO began their 24-hour shift at 0800 on the day of the accident. They completed a previous flight to rescue hikers and returned to their base in Kingman about 2005. They subsequently received a request for a mission flight in Flagstaff involving an active shooter in a neighborhood southeast of downtown. The flight was performed with the TFO occupying the left-front seat and utilizing a forward looking infrared (FLIR) camera to assist law enforcement personnel in assessing the scene from the air.

A review of Federal Aviation Administration (FAA) automatic dependent surveillance-broadcast (ADS-B) data, video and audio recorded by law enforcement body cameras, and residents’ security cameras revealed that the helicopter departed Kingman about 2110 and continued east toward Flagstaff. As the helicopter approached the city, the TFO was in communication with law enforcement personnel on the ground, who provided the approximate location of the active shooter. At 2205, the helicopter descended and operated between about 300 and 500 ft agl while performing a 360° turn over the neighborhood in the vicinity of the active shooter. The helicopter then performed a gradual climbing left turn south of the active shooter before establishing a northerly course. (See figure 1.)

The pilot maneuvered the helicopter in a gradual climb north of the neighborhood and performed a left 180° turn to return south to allow clearance for a helicopter that was inbound to Flagstaff Medical Center. At 2212:10, while the helicopter was at an altitude of 9,950 ft msl, it passed in the vicinity of the hospital-bound helicopter, which was on a northeast route at about 7,200 ft msl. Thereafter, the helicopter performed a left 360° turn and returned south toward the law-enforcement scene while descending to 8,900 ft msl (see figure 2 below). The helicopter then turned north and performed a gradual climbing left turn, consistent with aligning for an out-of-ground-effect (OGE) hover to maintain visual contact of the suspect. At 2216:24, the TFO initiated a radio transmission to law enforcement personnel on the ground; there were no indications of any abnormalities during the communication.

A review of available video showed the helicopter in a slow climb and then at 2216:43, the helicopter began a rapid rotation to the right. The rotation coincided with an unidentified verbal sound on the radio, followed by two loud banging sounds from the helicopter. The helicopter then descended rapidly toward terrain and at 2216:51, the TFO stated over the radio, “we’re going down.” During the descent, the helicopter’s spotlight was observed in video to flash periodically, consistent with continued aircraft rotation.

The main wreckage was located on a flat dirt access road about 3 nm north of the Flagstaff Airport at an elevation of 7,010 ft msl. A section of the Burlington Northern Santa Fe (BNSF) railway tracks was located about 100 ft south of the main wreckage. The wreckage was distributed along a debris path on a median bearing of 250°; the most distant wreckage was located more than 6,150 ft from the main wreckage.

The main wreckage consisted of the cockpit, cabin, and aft fuselage, which came to rest on its right side. The cockpit and cabin exhibited extensive postaccident fire damage. The tail rotor, vertical stabilizer, and a section of the tailboom came to rest about 135 ft northwest from the main wreckage. The tail rotor driveshaft remained attached to the tail rotor gearbox and exhibited angular cuts at the forward section; the surrounding skin exhibited deep grooves with blue paint transfer consistent with contact with a main rotor blade.

The tailboom was fractured at its forward location just aft of the intercostal support, with the structural remnants of the upper-right attachment fitting exhibiting bending outboard. A section of forward tailboom and connected aft fuselage were torn away from the fuselage with one tailboom attach bolt intact connecting the two halves. The remaining three tailboom attach bolts were intact at the tailboom/fuselage joint. The tailboom and the upper portion of the vertical fin exhibited multiple impact marks and punctures consistent with main rotor blade strikes sustained during the separation sequence. A comprehensive review of the aircraft's logbooks and maintenance records established that there had been no recent maintenance actions, reported anomalies, or structural repairs involving the tail boom or tail rotor assemblies prior to the accident sequence.

The main rotor hub, main rotor transmission, and three main rotor blades were located about 165 ft south of the main wreckage (see figure 3 below). The fourth main rotor blade, blade grip, and portion of its respective yoke were not located with the main rotor assembly; it was separated from the rotor hub and located 650 ft northeast of the main wreckage. All blades were lightly coated with an orange/yellow oil film.

Postaccident examination of the helicopter revealed no evidence of ballistic punctures. A review of video and ADS-B data revealed that the helicopter’s closest proximity to the suspect at the time shots were fired was about 7,500 ft.

The engine control unit (ECU) was recovered from the wreckage, and its data was successfully downloaded (see figure 4 below). A review of the recovered log revealed 16 trend records and 4 high-resolution snapshots, totaling 20 lines of data over an 18.4-second period. For the initial 6 seconds of the recording, the helicopter was operating at high power; the gas generator speed (Ng) was between 100% and 101%, and the main rotor speed (Nr) remained stable at 100%. Engine torque (Q) was between 76% and 80%, and the collective position (CP) was 64%. The power lever angle (PLA) was constant at 66°, which was consistent with the FLY detent range of 62° to 70°. During the following 1.2 seconds, Ng remained at 101%, Nr increased to 101%, and fuel flow (FF) decreased to 296 pph.

During the next 1.2 seconds, the collective was reduced to 48%, and fuel flow decreased to 284 pph. Simultaneously, Ng reduced to 97%, and Nr and power turbine speed (Np) both reduced to 98%. The following 1.2-second interval, beginning 9.6 seconds after the initial record, showed Nr and Np at 98%, while Ng increased to 102% and torque increased to 92%, with a fuel flow of 420 pph and an increase of measured gas temperature (MGT) to 1460°F. The next recorded data, 1.2 seconds later, showed that Ng decreased to 95%, Nr to 97%, Np to 96%, and torque to 60%; the collective was reduced to 10%.

During the subsequent 1.1 seconds, spanning four lines of data, the ECU recorded a transition to the reversionary governor. Nr decreased to 0%, while Np increased to 112% (overspeed). Simultaneously, engine torque decreased to 2%, consistent with an instantaneous removal of the rotor load from the power turbine. During the final 5.2 seconds, the PLA was reduced to 28°. The engine core remained operational with Ng stabilized at 63%, which is the specified ground idle speed.

According to the operator, the pilot would have been operating with night vision goggles. The pilot’s total flight hours are unknown, although he reported to the FAA that he had amassed more than 3,500 hours flying civil helicopters. He served in the Marine Corps from 1988-2010, a portion of his service was attached to Marine Helicopter Squadron One (HMX-1) as a pilot. 

The pilot of another helicopter, which was en route to land at the hospital at the same time the accident helicopter was operating in the area, stated that at 7,200-7,500 ft msl the wind was from the northeast at about 10 to 15 kts. A high-resolution rapid refresh (HRRR) model over the time of the accident displayed that the wind between about 9,500-10,200 ft msl was about 20 kts from 095°-115°. According to the U.S. Naval Observatory, Department of Astronomical Applications, the phase of the moon was waning gibbous (just past full) with 87.6% of the moons visible disk illuminated. Moonrise was at 2113 and at the time of the accident the moon was about 11° above the horizon (including refraction) on an azimuth (direction) of 99°.

Cessna 210B Centurion, N9735X, fatal accident occurred on February 15, 2026, near Camarillo Airport (CMA/KCMA), Camarillo, California

  • Location: Camarillo, CA
  • Accident Number: WPR26FA103
  • Date & Time: February 15, 2026, 18:05 Local
  • Registration: N9735X
  • Aircraft: Cessna 210B
  • Injuries: 1 Fatal, 1 Serious
  • Flight Conducted Under: Part 91: General aviation - Personal

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

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

On February 15, 2026, about 1805 Pacific standard time, a Cessna 210B, N9735X, was substantially damaged when it was involved in an accident near Camarillo, California. The pilot was fatally injured and the passenger sustained serious injuries. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.

A review of FAA ADS-B data revealed that the pilot departed Harry Reid International Airport (LAS), Las Vegas, Nevada at 1623. The airplane flew southwest and maintained an altitude of about 8,500 ft mean sea level (msl). While approaching Camarillo, California, the pilot declared an emergency with air traffic control and requested to land at Camarillo Airport (CMA), Camarillo, California after he lost engine power. According to the flight track, the airplane then turned direct to CMA as the airplane began to descend. No further communications were received by the pilot.

The airplane impacted a large tree and a fence before it came to rest on a water canal access gravel road in a residential neighborhood about 2-1/4 mile from the approach end of runway 26 at CMA. The accident site was at an elevation of 133 ft msl and on a magnetic heading of 58° from the approach end of runway 26. The debris field was about 1,190 ft long and on a directional heading of about 178°. The right outboard wing separated and was located in the impacted tree. The right wing strut was the furthest in the debris field and was found in the bottom of the canal.

During the recovery of the wreckage, the left wing was removed from the fuselage and about 20 gallons of fuel was removed from the tank. The right wing was breached near the wing root area and a small amount of fuel was noted.

The wreckage was retained for further examination.

Pitts S-2B Special, N58DE, incident occurred on March 8, 2026, at North Texas Regional Airport (GYI/KGYI), Sherman/Denison, 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=N58DE

 History of Flight:
On March 8, 2026, at 1345 local time, a Pitts S-2B Special, N58DE, sustained unknown damage when it was involved in an incident at the North Texas Regional Airport (GYI/KGYI), Sherman/Denison, Texas. The pilot was not injured. The local flight originated from KGYI at 1312 LT.

The FAA reported: "Aircraft veered off runway during departure due to canopy separating."