FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Aberdeen Flying Service Cessna 414A accident

22 Mar 2011 · Aberdeen, SD, United States

Cessna 414A · Accident: loss of control on ground during takeoff

From Aberdeen Regional Airport (ABR) to Sioux Falls Regional Airport (FSD)

Report a problem

Event

NTSB case
CEN11LA273
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
Charter & commuter
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Instrument Meteorological Cond

Cessna 414A

Aircraft type
Cessna 414
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
N4057C
Onboard fatalities
Unknown
Route
From Aberdeen Regional Airport (ABR), Aberdeen, SDTo Sioux Falls Regional Airport (FSD), Sioux Falls, SD
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 135: Air Taxi & Commuter
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 on ground
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 › Action/decision

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot reported that there was snow and ice on the runway. During takeoff, a strong crosswind gust forced the airplane to veer off the left side of the runway and the airplane struck runway lights. The pilot managed to maneuver the airplane back on the runway and he shut down the engines. A postaccident inspection of the airplane revealed substantial damage as a result of a puncture in the pressure vessel of the airplane. The pilot reported that there was no preimpact mechanical malfunction or failure of the airplane.

Probable cause

The pilot's inadequate compensation for gusty crosswinds during takeoff, which resulted in a loss of directional control.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN11LA273
Event ID
20110407X35115
Case number
CEN11LA273
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2011-03-23.
  • API snapshot SHA-256: 2917001c5ca26c5a5db89825d2bd6f58b1e37566be00cffb0456054f40b285f2; retrieved 2026-09-15T16:01:15.785Z.