FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA24LA041 · Cessna 421 B

11 Nov 2023 · Lake City, FL, United States

KMC Aviation Leasing Cessna 421 B · Accident: landing gear not configured

From an unrecorded airport to Fort Lauderdale Hollywood International Airport (FLL)

Report a problem

Event

NTSB case
ERA24LA041
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
0
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Cessna 421 B

Aircraft type
Cessna 421
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N977SM
Onboard fatalities
Unknown
Route
From not recordedTo Fort Lauderdale Hollywood International Airport (FLL), Fort Lauderdale, FL
Aircraft age
About 49 years (built 1974)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Landing · flare/touchdown
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Landing gear not configured
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Aircraft › Aircraft systems
  • Not determined › Not determined
  • Personnel issues › Task performance

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The pilot reported that, just after rotation during takeoff, he began to accelerate the airplane to 120 knots. About 20 ft above the runway, he noticed that the airplane’s airspeed and altitude started to decrease, though he reported no issues with either engine. Assessing the length of runway remaining, the pilot chose to abort the takeoff and lowered the landing gear using the normal method. The airplane touched down on the runway before the gear was fully extended, and the landing gear collapsed. The airplane came to rest upright about 1,000 ft before the end of the runway and incurred substantial damage to the airplane’s wings. The pilot stated that there was nothing mechanically wrong with the landing gear, which operated satisfactorily during recovery of the airplane using the emergency extension system. The departure runway was about 8,000 ft long. The airplane’s flight manual indicated that, given the airplane’s gross weight near its maximum and the environmental conditions present at the time of the accident, a minimum of 3,100 ft was required to accelerate, rotate, and climb to 50 ft; however, flight track data was not available to determine the maximum altitude the airplane reached during the takeoff or the point at which the pilot decided to abort the takeoff. The pilot attributed the loss of airspeed and altitude to a microburst during takeoff. Review of weather conditions revealed that a quasi-stationary front passed through the area around the time of the accident with a resulting slight wind shift; however, there was no significant wind shear associated with the front. Additionally, no convective echoes associated with microbursts or outflow boundaries were detected in radar data or satellite imagery, and recorded weather observations did not detect any strong gusting winds until well after the accident. Thus, there was no available evidence to support that wind shear or microburst conditions existed at the time of the accident. Although a reason for the airplane’s degraded climb performance could not be determined, its operation near the maximum gross weight and the ambient temperature at the time of the accident were likely factors. Any delay in the pilot’s recognition of the airplane’s reduced performance and aborting the takeoff would have resulted in the airplane continuing about 200 additional feet along the runway every second.

Probable cause

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

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA24LA041
Event ID
20231117193397
Case number
ERA24LA041
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates, cause areas. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 6981e47a369cc3967851a6ef9395a148af1300142140fdc085649b9e6fe3335a; retrieved 2026-09-16T18:18:01.460Z.