FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN10CA301 · Cessna 421B

4 Jun 2010 · Anderson, IN, United States

Great Lakes Aviation Cessna 421B · Accident: runway excursion during takeoff

From Anderson Municipal Darlington Field (KAID) to Porter County Municipal Airport (KVPZ)

Report a problem

Event

NTSB case
CEN10CA301
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
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 421B

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
N421KB
Onboard fatalities
Unknown
Route
From Anderson Municipal Darlington Field (KAID), Anderson, INTo Porter County Municipal Airport (KVPZ), Valparaiso, IN
Aircraft age
Not recorded
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 · rejected 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
Runway excursion
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
  • Personnel issues › Experience/knowledge
  • 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 did not identify any anomalies during his before takeoff engine run-up. After the successful engine run-up, he selected 15 degrees of flaps and set the pitch trim for takeoff. After receiving a takeoff clearance he taxied the airplane onto the runway, aligning with the runway centerline with 3,300 feet of runway remaining. Before commencing the takeoff roll, he held the brakes as he increased engine power to achieve maximum takeoff power. The takeoff roll was unremarkable until reaching 90 knots, when he attempted to rotate for liftoff. According to the pilot, aft movement on the control column did not result in the airplane becoming airborne. The pilot decided to abort the takeoff when the airplane had reached 100 knots and had not become airborne after passing the halfway point on the runway. He retarded the engine throttles and applied maximum braking, but the airplane was unable to stop before the end of the runway. The main landing gear collapsed during the overrun, damaging the left wing and fuselage primary structure. A postaccident inspection of the runway revealed heavy tire skid markings, consistent with heavy braking, which began 900 feet from the departure threshold. These heavy tire skid markings continued until the airplane exited the runway surface. The airplane came to rest on its lower fuselage structure, approximately 100 feet west of the extended centerline and about 250 feet from the departure threshold. The pilot reported that there were no preimpact mechanical malfunctions or failures that would have precluded normal operation of the airplane. Additionally, postaccident inspection did not reveal any anomalies that would have prevented the normal operation of the airplane or its engines. Based on available airport and weather information, the airplane’s pilot operating handbook (POH) indicated that the normal takeoff ground roll at a takeoff weight of 6,400 pounds, without flaps and without a headwind, was about 2,160 feet. The accelerate-stop distance under the same conditions was about 3,600 feet. The POH listed the rotation speed as 115 mph (100 knots) and that normal liftoff was achieved at 120 mph (104 knots). The handbook did not provide performance data for a 15-degree flap takeoff.

Probable cause

The pilot’s failure to establish proper rotation and liftoff speed during the takeoff roll.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN10CA301
Event ID
20100607X24400
Case number
CEN10CA301
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. 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: 321a1546a5d42e6e9230dfcb7b7b5b5d507b216f22c4cbd8234602df237b2814; retrieved 2026-09-15T14:22:26.874Z.