FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN19FA177 · Beech A36

20 Jun 2019 · Elida, OH, United States

Beech A36 · Accident: loss of control in flight en route

From Maquoketa Municipal Airport (OQW) to Toledo Executive Airport (TDZ)

Report a problem

Event

NTSB case
CEN19FA177
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
2 · 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
Instrument Meteorological Cond

Beech A36

Aircraft type
Beechcraft 36
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
N6150X
Operator
Unknown
Onboard fatalities
Unknown
Route
From Maquoketa Municipal Airport (OQW), Maquoketa, IATo Toledo Executive Airport (TDZ), Toledo, OH
Aircraft age
About 38 years (built 1981)
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
En route
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

  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Action/decision
  • Personnel issues › Experience/knowledge
  • Personnel issues › Psychological
  • Personnel issues › Task performance

Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.

NTSB narrative

The noninstrument-rated private pilot and passenger departed on the cross-county flight under visual flight rules (VFR) in visual meteorological conditions and proceeded on course at an altitude of about 9,000 ft mean sea level (msl). As the flight progressed, the weather conditions deteriorated, and about halfway through the flight, the pilot appeared to deviate before resuming flight toward the destination and descended to about 2,000 ft msl over about 30 minutes. Within 20 miles of the accident site, the pilot executed multiple course changes, including two 360° turns. The airplane then entered a right turn from a southeasterly course to a southwesterly course, and about 1 minute before the accident, the airplane re-entered the right turn, which progressed into a right graveyard spiral that continued until impact.

Weather observations and satellite imagery indicated that instrument meteorological conditions (IMC) prevailed in the vicinity of where the pilot began making the multiple course changes and at the accident site. It is likely that the pilot encountered rain, and possibly heavy rain, during the final portion of the flight. There was no record of the pilot obtaining a preflight weather briefing from an official source.

Examinations of the airframe and engine did not reveal any anomalies consistent with a preimpact failure or malfunction.

Toxicology testing of the pilot revealed the presence of carboxy-delta-9-tetrahydrocannabinol (THC), an inactive metabolite of THC. The low-level presence of the inactive THC metabolite suggests that the pilot was not under the influence of THC at the time of the flight, and therefore, it is unlikely that any effects from the pilot's prior use contributed to the accident. The testing also revealed the presence of diphenhydramine; however, it did not provide a blood level. Therefore, whether the pilot might have been impaired from the diphenhydramine at the time of the accident or whether his prior use contributed to the accident could not be determined.

The restricted visibility conditions present in the area were conducive to the development of spatial disorientation, and the airplane's maneuvering and spiraling descent are consistent with the known effects of spatial disorientation. It is likely that the pilot experienced spatial disorientation during an encounter with instrument meteorological conditions, which resulted in a loss of control.

Probable cause

The noninstrument-rated pilot's decision to continue visual flight rules flight into an area of instrument meteorological conditions, which resulted in a loss of control due to spatial disorientation. Contributing was the pilot not obtaining a weather briefing prior to the flight.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN19FA177
Event ID
20190620X80853
Case number
CEN19FA177
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: 96319dcc901a7ab9c1f9242231df491956cdd6136d669773715176a9b97a783d; retrieved 2026-09-15T07:00:26.185Z.