CHI04LA213 · Cessna 208B
Cessna 208B · Accident: airframe, component or system failure en route
From Gerald R. Ford International Airport (GRR) to Cherry Capital Airport (TVC)
Event
- NTSB case
- CHI04LA213
- 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 208B
- Aircraft type
- Cessna 208
- 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
- N1037N
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Gerald R. Ford International Airport (GRR), Grand Rapids, MITo Cherry Capital Airport (TVC), Traverse City, MI
- 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
- En route · cruise
- First occurrenceThe 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
- Airframe, component or system failure
- 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
- Door, cargo/baggage › Not secured
- Door, cargo/baggage › Open
- Pilot in command › Aircraft preflight, inadequate
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane was substantially damaged when the cargo door inadvertently opened in-flight and a box departed the aircraft, striking the horizontal stabilizer. The pilot reported that after loading the cargo, he and the loaders had to "muscle the cargo door closed due to a large volume of freight." The taxi and takeoff were normal, but a few minutes after leveling at cruising altitude the door ajar light illuminated. The pilot stated that "shortly after this illumination, there was a loud thud and [he] figured that a box had departed the aircraft and struck the tail." The pilot reported that aircraft control was normal after the accident. He stated that he employed the door ajar checklist, diverted to an intermediate airport, and landed uneventfully. When he exited the aircraft, the pilot saw the damage to the left horizontal stabilizer. An inspection of the cargo door installation on the accident aircraft revealed the door structure and locking mechanism were intact and appeared undamaged. The door closed and latched properly. The cargo door had a window installed. The inspection noted that with this design the door had enough flexibility to allow the forward frame of the door to be seated in the door jamb and latched, while the aft frame was outside the jamb and unlatched. The micro-switch for the DOOR WARNING annunciator light was located on the forward jamb. Therefore, it was possible in that configuration for the aft cargo door latch not to be engaged without the annunciator light being illuminated.
Probable cause
The pilot's failure to verify that the cargo door was latched properly prior to flight and the subsequent in-flight opening of the door. A contributing factor was the box which departed the cargo compartment and struck the horizontal stabilizer.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI04LA213
- Event ID
- 20040901X01340
- Case number
- CHI04LA213
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: a49666277f2b5e9aaad99c8091ec18be09d53cba65fceb9c9063dc6b69c79e31; retrieved 2026-09-18T15:19:58.846Z.