Multi-Aero Cessna 208B B accident
Cessna 208B B · Accident: abrupt maneuver while taxiing
From Gogebic Iron County Airport (IWD) to Chicago O'Hare International Airport (ORD)
Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- CEN16LA052
- 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 B
- 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
- N732MD
- Operator
- Multi-Aero
- Onboard fatalities
- Unknown
- Route
- From Gogebic Iron County Airport (IWD), Ironwood, MITo Chicago O'Hare International Airport (ORD), Chicago, IL
- Aircraft age
- About 11 years (built 2004)
- 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 · from runway
- 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
- Abrupt maneuver
- 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
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
After landing in night visual meteorological conditions, the commuter flight proceeded to taxi to the ramp. Upon coming to a service road perpendicular to the taxiway, a vehicle moved directly across the airplane's taxi path. The flight crew immediately applied brakes to stop. While braking, the airplane's tail rocked aft and struck the ground. The flight crew contacted ground control to inform them about the vehicle incident and resumed taxi to the ramp, and the driver of the vehicle radioed the tower, informing them that he had cut off an aircraft. An inspection of the airplane by the operator revealed structural damage to the aft pressure bulkhead resulting from the tail strike.
Probable cause
The failure of the driver of the service vehicle to yield to the taxiing airplane, which resulted in a near-collision and tail strike.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN16LA052
- Event ID
- 20151204X01344
- Case number
- CEN16LA052
- 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 2015-11-03.
- API snapshot SHA-256: eb4e7c03679e9a64fe9eea93845865523d68eb156609b7507fc0c244bb954d0a; retrieved 2026-09-16T03:00:36.179Z.