FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Daedalus Inc Dba Cessna 402B accident

22 Sept 2009 · Omaha, NE, United States

Cessna 402B · Accident: collision with terrain/object (non-CFIT) while taxiing

From Eppley Airfield (OMA) to Sioux Falls Regional Airport (FSD)

Report a problem

Event

NTSB case
CEN09CA600
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
Visual Meteorological Cond

Cessna 402B

Aircraft type
Cessna 402
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
N1048
Onboard fatalities
Unknown
Route
From Eppley Airfield (OMA), Omaha, NETo 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
Taxi
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
Collision with terrain/object (non-CFIT)
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

  • Personnel issues › Action/decision
  • Personnel issues › Psychological

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

NTSB narrative

The pilot arrived for the morning cargo flight with the twin-engine airplane parked directly into the sun and condensation on the windscreen. Using his hand, the pilot attempted to clear the condensation from the windscreen only to have it reappear. The pilot elected to start taxiing with the left crew door open to aid his visibility; however, while executing a left turn onto the cargo ramp the airplane's left wing and left propeller impacted an unattended airplane. Once both engines were secured, the pilot was able to exit the airplane unassisted. An examination following the accident revealed that the parked airplane sustained structural damage to the forward nose area, and the taxiing airplane sustained structural damage to the left wing.

Probable cause

The pilot’s improper decision to taxi with an obstructed windscreen and his failure to maintain clearance from the parked airplane.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN09CA600
Event ID
20090922X51734
Case number
CEN09CA600
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. 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: 9a3c8405d068fcd40904d5a84e92f326b317570b426d512d717772b4ee2d53cf; retrieved 2026-09-15T13:20:23.889Z.