FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Martinaire Aviation Cessna 208 B accident

9 Dec 2019 · Victoria, TX, United States

Cessna 208 B · Accident: loss of control in flight during initial climb

From Victoria Regional Airport (VCT) to George Bush Intercontinental Airport (IAH)

Report a problem

Event

NTSB case
CEN20FA032
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
1 · 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 208 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
N4602B
Onboard fatalities
Unknown
Route
From Victoria Regional Airport (VCT), Victoria, TXTo George Bush Intercontinental Airport (IAH), Houston, TX
Aircraft age
About 31 years (built 1988)
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
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
Loss of control in flight
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Aircraft › Aircraft systems
  • Personnel issues › Psychological
  • Personnel issues › Task performance

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

NTSB narrative

The airline transport pilot departed on a night cargo flight into conditions that included an overcast cloud ceiling and “hazy” visibility, as reported by another pilot. About one minute after takeoff, the pilot made a series of course changes and large altitude and airspeed deviations. Following several queries from the air traffic controller concerning the airplane’s erratic flight path, the pilot responded that he had “some instrument problems.” The pilot attempted to return to land at the departure airport, but the airplane impacted terrain after entering a near-vertical dive. The airplane was one of two in the operator’s fleet equipped with an inverter system that electrically powered the pilot’s (left side) flight instruments. Examination of the annunciator panel lighting filaments revealed that the inverter system was not powered when the airplane impacted the ground. Without electrical power from an inverter, the pilot’s side attitude indicator and horizontal situation indicator (HSI) would have been inoperative and warning flags would have been displayed over the respective instruments. The pilot had a history of poor procedural knowledge and weak flying skills. It is possible that he either failed to turn on an inverter during ground operations and did not respond to the accompanying warning flags, or he did not switch to the other inverter in the event that an inverter failed inflight. Due to impact damage, the operational status of the two inverters installed in the airplane could not be confirmed. However, the vacuum-powered flight instruments on the copilot’s (right side) were operational, and the pilot could have referenced these instruments to maintain orientation. Based on the available information, the pilot likely lost control of the airplane after experiencing spatial disorientation. The night marginal visual flight rules conditions and instrumentation problems would have been conducive to the development of spatial disorientation, and the airplane’s extensive fragmentation indicative of a high-energy impact was consistent with the known effects of spatial disorientation. Ethanol identified during toxicology testing may have come from postmortem production and based on the low levels recorded, was unlikely to have contributed to this accident. Morphine identified in the pilot’s liver could not be used to extrapolate to antemortem blood levels; therefore, whether or to what extent the pilot’s use of morphine contributed to the accident could not be determined.

Probable cause

The pilot’s loss of control due to spatial disorientation. Contributing to the accident were the inoperative attitude indicator and horizontal situation indicator on the pilot’s side of the cockpit, and the pilot’s failure to reference the flight instruments that were operative.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN20FA032
Event ID
20191210X03219
Case number
CEN20FA032
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, cause areas. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2019-12-10.
  • API snapshot SHA-256: 82f0f583ca9d32ab49dac88eb40c5bfd54c1cb2309798338b2caffd923238537; retrieved 2026-09-15T07:09:30.516Z.