CEN21LA315 · Cessna 421C
Cessna 421C · Accident: loss of control in flight during takeoff
From an unrecorded airport to Aspen-Pitkin County Airport (Sardy Field) (KASE)
Event
- NTSB case
- CEN21LA315
- 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
- Event fatalities
- Unknown
- Ground fatalities
- Unknown
- 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 421C
- 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
- N66NC
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo Aspen-Pitkin County Airport (Sardy Field) (KASE), Aspen, CO
- Aircraft age
- About 43 years (built 1978)
- 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
- Takeoff
- 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
- Loss of control in flight
- 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
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Action/decision
- 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 he performed the “before starting engine” and “starting engine” checklists and everything was normal before taking off in the twin-engine airplane. He performed an engine runup and then started his takeoff roll. The pilot reported that about halfway down the runway the airplane was not accelerating as fast as it should. He attempted to rotate the airplane; however, “the airplane mushed off the runway.” The airplane settled back onto the runway, then exited the departure end of the runway, where it sustained substantial damage to the wings and fuselage. The airplane engine monitor data indicated the airplane’s engines were operating consistent with each other at takeoff power at the time of the accident. Density altitude at the time of the accident was 7,170 ft and according to performance charts, there was adequate runway for takeoff. The reason for the loss of performance could not be determined.
Probable cause
The loss of performance for reasons that could not be determined.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN21LA315
- Event ID
- 20210713103460
- Case number
- CEN21LA315
- 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: 8b2952bd5f6ea5097f8b512a72835e9636c95f1e1bd61f58689479a7abc1b364; retrieved 2026-09-16T14:16:44.884Z.