11 Nov 2023: CESSNA 421 B — KMC AVIATION LEASING LLC

11 Nov 2023: CESSNA 421 B (N977SM) — KMC AVIATION LEASING LLC

No fatalities • Lake City, FL, United States

Probable cause

A landing gear collapse following an aborted takeoff due to degraded climb performance for reasons that could not be determined.

— NTSB Determination

Accident narrative

On November 11, 2023, about 1357 eastern standard time, a Cessna 421B, N977SM, was substantially damaged when it was involved in an accident near Lake City, Florida. The commercial pilot and five passengers were not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. The pilot stated that he had landed at Lake City Gateway Airport (LCQ) to refuel the airplane, and after fueling, he performed weather and flight planning for the next leg of the flight. The pilot taxied to runway 10, an 8,003-foot-long runway, and after lining up on the runway centerline for departure, set the power and started the takeoff roll operating about 45 lbs below the airplane’s maximum gross weight. Data from an airport operations and tracking system (AOTS) captured a portion of the takeoff roll, with the airplane attaining 80 knots groundspeed about 1,544 ft down the runway. No more data points from the AOTS, or ADS-B, were available for the accident flight. The pilot stated that, after rotation, he transitioned to a climb airspeed of 120 knots and retracted the landing gear (no information was available in the airplane’s Federal Aviation Administration [FAA] Approved Aircraft Flight Manual [AFM], airplane maintenance manual, or component maintenance manual that specified how long gear retraction or extension would take). When the airplane was about 20 ft above ground level with the engines developing normal rpm and manifold pressure, the airspeed started to decrease with a corresponding loss of altitude, which the pilot later attributed to be from a “microburst on takeoff.” He assessed the length of runway remaining versus continuing the flight and aborted the takeoff. He used the normal method to extend the landing gear, but it was not fully extended and collapsed upon touchdown. The airplane came to rest upright near the aiming point markings for runway 28. Postaccident review of pictures of the airplane revealed substantial damage in the form of abrasion to the wing carry-through structure, and damage to ribs in both wings. The pilot also stated that he did not perceive any issue with either engine during the flight and that there was nothing mechanically wrong with the landing gear extension system. He also indicated that in the previous 90 days, in which he had flown that airplane on 40 flights accruing about 58 hours, he had not experienced any issues with the landing gear or engines. During recovery of the airplane from the runway, the landing gear was extended via the emergency extension system with no discrepancies reported. Safety concerns due to potential fuel leakage prevented application of electrical power to extend the gear using the normal system. According to the airplane’s AFM, for the existing environmental conditions that day, operating at gross weight, no wind, and a takeoff speed of 106 knots indicated airspeed, the distance to take off and climb to 50 ft was about 3,100 ft. The AFM also indicated that the calculated rate of climb performance for the temperature that day and with the flaps and landing gear up, maximum continuous power and climbing at 106 knots calibrated airspeed, was about 1,559 ft per minute and the distance to land over a 50 ft obstacle and stop was about 2,218 ft. Review of weather information indicated that an east-to-west quasi-stationary front extended in the vicinity of the accident site about the time of the accident. The surface weather observations surrounding the time of the accident depicted a slight wind shift, but there were no significant weather echoes within 5 miles of the accident site at the time of the accident. Further, there was no support for significant low-level wind shear or turbulence below 10,000 ft outside of any potential convection, and there were no Convective SIGMETs, SIGMETs, Center Weather Advisories, or Graphic-AIRMETs over the airport surrounding the period between 1400 through 1600.

Contributing factors

  • Attain/maintain not possible
  • Gear extension and retract sys
  • Pilot

Conditions

Weather
VMC, wind 100/06kt, 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.