FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI00LA312 · Cessna 208B

14 Sept 2000 · Belleville, MI, United States

Cessna 208B · Accident: cargo shift during takeoff

From Willow Run Airport (YIP) to Virgil I Grissom Municipal Airport (BFR)

Report a problem

Event

NTSB case
CHI00LA312
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
N806BF
Operator
Unknown
Onboard fatalities
Unknown
Route
From Willow Run Airport (YIP), Belleville, MITo Virgil I Grissom Municipal Airport (BFR), Bedford, 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 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 · roll/run
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
Cargo shift
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

  • Cargo/baggage › Shifted
  • Pilot in command › Security of cargo, improper

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

NTSB narrative

The airplane sustained substantial tail section damage on contact with the ramp surface while standing on the ramp. The flight encountered a shift in cargo on takeoff roll, aborted its takeoff, and taxied back to the ramp where its tail contacted the ramp on engine shutdown. The pilot was uninjured. A FAA inspector's record of interview stated, "According to [the pilot], prior to this incident only three to four straps were used. ... [The pilot] went on to explain that the cargo shifted upon the takeoff roll. ... Upon returning to the ramp he shut down the engine and that's when the aircraft fell on its tail. ... He also said that he was glad that it didn't happen after he had rotated because he was sure that he would have been a fatal accident." A FAA inspector's record of interview stated, "[The witness] stated that when the aircraft sat on its tail, [the Fixed Base Operator (FBO) there] was asked to unload the cargo, which only had one strap holding it down, the 'D' ring had come loose from the floor attachment, and that the cargo was still on rollers under the skid. [The witness] stated that they initially loaded the cargo on the aircraft only, and that the pilot was the one that secured the cargo prior to the incident. After the incident [the FBO] un-loaded the cargo on request of the pilot ... and then was asked to reload the cargo by [the pilot] because the pilot stated something about a hernia. [The witness] stated that the only way they would load the cargo on the airplane again was if they loaded and secured the cargo per their procedures because when [the pilot] secured the cargo he only used one strap and left the load on the rollers. ... [The witness] stated that the plane departed the airport with the cargo about 45 minutes after the accident." The NTSB Materials Laboratory Factual Report number 01-069 stated, "Examination of the plunger revealed that there were portions of the pin in each end of the pin hole. The portion that would have retained the plunger over the body was missing. ... The distance from the lowest point on the plunger pin ... to the underside of the plunger ... was measured and found to be 0.684 inches. The fracture face, [of one of the roll pins], displayed a shiny granular appearance typical of a brittle fracture. ... The side view ... illustrates the plunger in its lowest position with the pin contacting the bottom of the stud body hole.... In this position there is a gap of 0.09 inches between the bottom of the plunger ... and the bottom of the stud body...."

Probable cause

the pilot's improper securing of the cargo that led up to the cargo shift during takeoff roll. A factor was the cargo restraint failure.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI00LA312
Event ID
20020201X00156
Case number
CHI00LA312
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2000-09-15.
  • API snapshot SHA-256: 839f432bdebd266b50dd0a9c3a24379e690c28f5c9ff286818164f80be0b9061; retrieved 2026-09-18T16:25:53.985Z.