CEN18LA205 · Cessna 150L L
Sky Soaring Cessna 150L L · Accident: loss of control in flight on approach
From Sky Soaring Airport (55LL) to Sky Soaring Airport (55LL)
Event
- NTSB case
- CEN18LA205
- 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
- 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
Cessna 150L L
- Aircraft type
- Cessna 150
- 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
- N19366
- Operator
- Sky Soaring
- Onboard fatalities
- Unknown
- Route
- From Sky Soaring Airport (55LL), Union, ILTo Sky Soaring Airport (55LL), Union, IL
- Aircraft age
- About 45 years (built 1973)
- 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
- Approach · VFR go-around
- 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
- 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 from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airline transport pilot reported that he was returning from a routine glider tow flight when he thought "something was wrong." He noted that it seemed to "get dark" although there was plenty of daylight. The airplane was high on the approach. The pilot continued the flight inbound but was unsure of the airplane's exact altitude or airspeed as it crossed the runway threshold, and he did not recall verifying that the engine power was at idle. The airplane "bounced down the field" and he flew toward an opening in the trees off the end of the runway. The pilot did not see the power lines until the airplane struck them and then came to rest in a field. The pilot recalled not having an "aviation related thought" during the landing. A postaccident examination of the airframe and engine did not reveal any evidence of preimpact mechanical malfunctions or failures that would have precluded normal operation.
The pilot had completed the Federal Aviation Administration BasicMed medical certification, which was valid at the time of the accident. The pilot described symptoms consistent with fainting or nearly fainting, which commonly occur when blood pressure is low and would have led to an inability to safely fly the airplane. The pilot thought that dehydration or heat exhaustion might have caused his symptoms. However, given his long-standing paroxysmal atrial fibrillation, his difficulty effectively controlling it after the accident, his documented low blood pressure during those episodes, and his lack of symptoms during the episodes of atrial fibrillation other than "feeling bad," it is likely that his symptoms during the flight were related to an episode of atrial fibrillation associated with a rapid heart rate and low blood pressure. Therefore, symptomatic near fainting as a result of uncontrolled paroxysmal atrial fibrillation likely caused the accident.
Probable cause
The pilot’s medical impairment at the time of the accident, which resulted in a collision with power lines off the end of the runway.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN18LA205
- Event ID
- 20180528X34948
- Case number
- CEN18LA205
- 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: 3ca22e2fe589fd290f4fa333bbdf2d670b0eaf48598176e754c535989825115f; retrieved 2026-09-16T07:16:39.954Z.