1 Mar 2024: CIRRUS DESIGN CORP SR20

1 Mar 2024: CIRRUS DESIGN CORP SR20 (N1108T) — Unknown operator

No fatalities • Key Largo, FL, United States

Probable cause

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

— NTSB Determination

Accident narrative

On March 1, 2024, about 1243 eastern standard time, a Cirrus SR20 airplane, 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 flight departed Pompano Beach Airpark (PMP), Pompano Beach, Florida, destined for Ocean Reef Airport (07FA), Key Largo, Florida.

According to the pilot, after departing PMP, the flight was unremarkable. He entered the traffic pattern at 07FA at 1,000 ft on the left downwind leg for runway 5, joined the base leg at 800 ft with approach flaps, and then selected full flaps and turned onto the final leg at 600 ft. His final approach was stable. Then, 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.

According to ADS-B data provided by the FAA, the flight departed about 1207, turned on course, and while enroute climbed to a GPS altitude of about 700 ft before entering the left downwind leg of the traffic pattern for runway 5 at 07FA about 1238. The flight then joined the left base leg at 1239:29 at approximately 650 ft, and then turned onto the final leg at 1240:33 at approximately 525 ft. The last ADS-B position was recorded at 1242:03 over the Card Sound Golf Club, at an altitude of about 50 ft, approximately 104 ft to the left of the centerline of runway 5.

The propeller was found separated from the crankshaft and was near the initial impact point at the beginning of the debris field, which continued to the main wreckage. The engine had been partially separated from its mounting position and the nose wheel landing gear assembly had separated from its mounting position. The outboard 4-ft of the right wing had broken off and the leading edge of the left wing displayed a fracture along the wingtip and leading edge.

Flight control continuity was confirmed from the flight control surfaces to the cockpit. The mixture control was found in the full rich position and the power lever was found to be in about the three-fourths forward travel position. The wing flaps were in the up (0%) position.

The propeller displayed evidence of blade polishing and chordwise scratching and the separated crankshaft flange displayed a 45° shear-type break. Oil was discovered in the engine rocker boxes and oil sump. Thumb compression and suction were obtained on all six cylinders. All the intake and exhaust valves were functional and drivetrain continuity was confirmed from the front of the engine to the rear gears. Both magnetos also produced spark and no anomalies were noted with the fuel injection system.

The recorded weather at 07FA, at 1235 (about 8 minutes before the accident), included: winds 120 at 10 knots, gusting to 16 knots, 10 miles visibility, clear skies, temperature 27° C, dew point 21° C, and an altimeter setting of 30.18 inches of mercury.

The recorded weather at 07FA, at 1255 (about 12 minutes after the accident), included: winds 110 at 11 knots, gusting to 17 knots, 10 miles visibility, clear skies, temperature 27° C, dew point 21° C, and an altimeter setting of 30.17 inches of mercury.

Review of data downloaded from the airplane’s remote data module 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, with flaps fully retracted, as it entered an aerodynamic stall to the left and impacted terrain.

Review of an airplane flight manual for the make and model airplane revealed instructions to set the flaps at 50% extension for a go-around procedure.

Contributing factors

  • Pilot
  • Pilot
  • Incorrect use/operation
  • Performance/control parameters — Not attained/maintained

Conditions

Weather
VMC, wind 120/10kt, vis 10sm

Loading the flight search…

What you can do on Flight Finder

  • Search flights between any two airports with live fares.
  • By aircraft — pick a plane model (e.g. Boeing 787, Airbus A350) and see every route it flies from your origin.
  • Route map — click any airport worldwide to explore its destinations, or draw a radius to find nearby airports.
  • Global aviation safety — aviation accident database, 5,200+ records since 1980, with map and rankings by aircraft and operator.
  • NTSB safety feed — recent U.S. aviation accidents and incidents from the official NTSB CAROL database, updated daily.

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.