FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN18FA060 · X-Air LLC XA85

23 Dec 2017 · Oskaloosa, IA, United States

X-Air LLC XA85 · Accident: medical event while maneuvering

From Oskaloosa Municipal Airport (OOA) to Marshalltown Municipal Airport (MIW)

Report a problem

Event

NTSB case
CEN18FA060
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
General aviation
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

X-Air LLC XA85

Aircraft type
X Air XA85
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
N20XA
Operator
Unknown
Onboard fatalities
Unknown
Route
From Oskaloosa Municipal Airport (OOA), Oskaloosa, IATo Marshalltown Municipal Airport (MIW), Marshalltown, IA
Aircraft age
About 8 years (built 2009)
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
Maneuvering · low-altitude flying
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
Medical event
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Wire
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

  • Environmental issues › Physical environment
  • Personnel issues › Physical

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

NTSB narrative

The private pilot was intending to conduct a cross-country flight when the light sport airplane collided with a power line and terrain. Several witnesses reported seeing the airplane flying at low altitude near the accident site. There were no eyewitnesses to the final portion of the flight; however, an individual near the accident site heard the airplane's engine from inside his residence. After the crash, he saw the airplane in the field outside his residence and flames from the power lines along the road. A postaccident airframe examination and operational engine test revealed no evidence of a mechanical malfunction or failure that would have precluded normal operation.

The intended destination was 65 miles north-northwest of the departure airport. The accident site was located about 12 miles northwest of the departure airport, and according to engine data, the airplane crashed about 35 minutes after takeoff. The wreckage debris path was consistent with the airplane colliding with a 35-ft-tall power line while on a southerly heading. The pilot's partner reported that the pilot was familiar with the route of flight and that he had made the flight numerous times. She further noted that he typically flew at 3,500 ft mean sea level (msl) during cruise flight. A review of available air traffic control (ATC) radar data revealed no transponder or primary radar data associated with the flight. The lower limit of ATC radar coverage in the general area of the accident site was about 2,000 ft above ground level (2,750 ft msl). Based on the crash location, witness accounts, and the lack of ATC radar data for any portion of the flight, the pilot did not follow a direct route toward his intended destination or climb to his normal cruise altitude.

According to toxicological test results, the pilot was using two impairing medications, diphenhydramine and gabapentin, which likely impaired him during the flight. However, he had likely used these drugs during previous flights where he did not demonstrate unusual behavior; thus, these medications alone do not explain the pilot's performance during the accident flight. The pilot remained at low altitude and in the general vicinity of the departure airport; he did not fly toward his intended destination, which suggests that he may have become confused about where he was, what he was doing, and where he was going.

The pilot had several medical conditions that could have affected him during the flight; coronary artery disease, multiple previous ischemic and hemorrhagic strokes, and recent pneumonia. Another stroke or transient ischemic attack (TIA) during the flight could have made him confused or made it difficult to operate the airplane due to weakness in his arm and/or leg. The pilot's coronary artery disease and valvular heart disease could have also caused weakness and confusion due to low blood pressure as a result of an arrythmia, or an ischemia could have worsened his shortness of breath and caused him to become hypoxic (have low oxygen), which could also result in confusion. Any such physiologic event would have further worsened the psychoactive effects from the two sedating medications the pilot was using. Although the pilot was likely impaired by his use of two impairing medications, by themselves they do not explain the airplane's flight path and his behavior. Therefore, it is more likely that some physiologic event occurred that caused his inability to safely carry out the flight.

Probable cause

The pilot's low altitude flight into a power line due to his impairment from an acute physiologic event during the flight. Contributing to the pilot's impairment was his use of two sedating medications.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN18FA060
Event ID
20171223X73130
Case number
CEN18FA060
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. 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: 1556633bd921258ab86ee0ab6f44d5a38de69c5bbe059a21010640ba437fe3eb; retrieved 2026-09-15T06:28:28.842Z.