CEN19FA259 · Air Tractor AT502 B
Air Advantage Air Tractor AT502 B · Accident: low altitude operation/event while maneuvering
From Mount Pleasant Municipal Airport (MPZ) to Oelwein Municipal Airport (OLZ)
Event
- NTSB case
- CEN19FA259
- 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
Air Tractor AT502 B
- Aircraft type
- Air Tractor AT502
- 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
- N6113C
- Operator
- Air Advantage
- Onboard fatalities
- Unknown
- Route
- From Mount Pleasant Municipal Airport (MPZ), Mt. Pleasant, IATo Oelwein Municipal Airport (OLZ), Oelwein, IA
- Aircraft age
- About 25 years (built 1994)
- 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
- Low altitude operation/event
- 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
- Personnel issues › Physical
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot overflew the intended destination airport and continued about 14 miles north before turning to the south. Witnesses located about 2-1/2 miles north of the accident site reported observing the airplane overfly their homes at a low altitude. One witness noted that the airplane appeared to be in level flight, and the engine seemed to be operating normally.
A witness near the accident site observed the airplane approach from the west-northwest. The airplane struck power lines; however, the airplane's flightpath was not affected. The airplane then nearly struck a building before it struck a second set of power lines. It then veered left, and the nose dropped. The airplane subsequently impacted a road, skidded across the road, and impacted the ground near a large tree. A postimpact fire ensued. According to witnesses, there was nothing unusual about the airplane before the initial wire strike. The airplane seemed to be intact, and the engine sounded normal. The airplane remained in a shallow left turn as it struck the power lines and did not appear to be climbing or descending.
A postaccident airframe examination did not reveal any evidence of an in-flight structural failure or flight control system anomaly. An engine examination revealed circumferential contact marks throughout the engine consistent with rotation at impact. No anomalies consistent with a preimpact failure or malfunction were observed.
Review of the pilot’s medical records, toxicology testing, and autopsy results revealed that he was at significant risk of impairment from multiple serious medical conditions and the use of multiple potentially impairing medications. The pilot had heart disease, a subarachnoid hemorrhage that appeared to be several days old, chronic kidney disease treated with dialysis, poorly controlled diabetes, hypertension, chronic pain, and anxiety. In addition, the pilot was taking hydrocodone, fentanyl, trazodone, and yohimbine, any of which had the potential to be impairing.
Further, the investigation revealed that the pilot was involved in another wire strike event 8 days before the accident. Witnesses noted that after that wire strike, the pilot seemed shaken, and he was heard coughing and vomiting several days later. The timing of the pilot’s subarachnoid hemorrhage suggests that it may have resulted from this previous wire strike event. Although additional details about the events surrounding the wire strike are not known, the wire strike event itself suggests a possibility of some manifestation of pilot impairment that began before the accident flight.
While it could not be determined which specific medical factor or factors played a role in this accident, it is likely that one or more of the pilot's multiple medical conditions, medications, or the previous wire strike impaired his performance during the accident flight, as evidenced by his overflight of the intended destination airport and his continued low altitude flight in the vicinity of power lines and buildings without a change in flightpath or any apparent effort to avoid them.
Probable cause
The pilot’s impairment by medical conditions and/or medications, which resulted in the airplane’s impact with power lines and terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN19FA259
- Event ID
- 20190808X54033
- Case number
- CEN19FA259
- 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: 17426990026be795abc69520c46ea29fdc5f3aeec7e48a2ec89263a72ab0ba3c; retrieved 2026-09-15T07:03:09.914Z.