FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN09CA470 · Raytheon Aircraft Company C90A

23 Jul 2009 · Bismarck, ND, United States

UND Aerospace Foundation Raytheon Aircraft Company C90A · Accident: system/component malfunction/failure (non-power) during initial climb

From Bismarck Municipal Airport (BIS) to Grand Forks International Airport (GFK)

Report a problem

Event

NTSB case
CEN09CA470
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

Raytheon Aircraft Company C90A

Aircraft type
Beechcraft 90
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
N405DD
Onboard fatalities
Unknown
Route
From Bismarck Municipal Airport (BIS), Bismarck, NDTo Grand Forks International Airport (GFK), Grand Forks, ND
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
Initial climb
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
System/component malfunction/failure (non-power)
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 structures

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 had the copilot close the cabin entry door, which later came open while the airplane climbed through 500 feet above ground level after takeoff. The pilot executed a return to the departure airport where the airplane was landed without further incident. The door remained attached at the hinge and about half of the door skin was pulled away resulting in damage to the airplane pressure vessel. The pilot stated that the CABIN DOOR annunciator was never illuminated. The operator reported that all the door latches were in the extended positions after the accident.

Probable cause

The cabin entry door inadvertently opening during initial climb.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN09CA470
Event ID
20090728X63439
Case number
CEN09CA470
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: c619b637f9d4479c56cb4c7f0185b300bb6df1679c8251444b8bafb98dbc5918; retrieved 2026-09-15T12:03:03.912Z.