NTSB CAROL · Event
Event CEN17LA097
Aircraft involved
Probable cause & findings
The pilot's failure to adequately monitor the environment and to maintain sufficient altitude to clear power lines.
Factual narrative
On January 26, 2017, about 1525 central standard time, a Beech BE35 single engine airplane, N4213B, registered to a private individual, sustained substantial damage when it impacted the ground after a collision with power lines while on VFR approach to the Gimlin Airport (18MO), Ozark, Missouri. The private pilot sustained minor injuries and one pilot-rated passenger sustained serious injuries. The personal local flight was being conducted under the provisions of Federal Code of Regulations Part 91. Visual meteorological conditions prevailed throughout the area and a flight plan was not filed. The flight originated from 18MO about 1430. According to the pilot, the flight was intended to gain some experience in his recently purchased airplane. After completing about 10 touch and go landings at a nearby airport, the flight was returning to 18MO for a full stop landing. The pilot announced the he was entering a left downwind to runway 36, reduced speed, and lowered the landing gear. Upon turning to final approach, the pilot lowered the flaps and was concentrating on lining up the airplane on runway centerline. The pilot stated that he did not see the power lines, nor was he looking for any, because they "had not been a factor" in his previous three approaches. The last thing he remembered is "something had exploded" in his face," and opening his eyes inside the wreckage. After the accident, the pilot stated that there were no mechanical issues with the airplane. The pilot-rated passenger stated that the airplane was lined up with the runway on final and he felt that the airplane was a little low, but thought that the pilot was making a flat, power-on approach, due to the crosswinds. Upon passing over a tree line, he stated that the pilot surprised him by pulling back the power instead of adding power. The airplane seem to sink into the power lines. After colliding with the power lines, the airplane impacted the ground and tumbled inverted, resulting in substantial damage to the fuselage and wings. The power lines were located about 1/4 mile from the airport. Evidence at the accident site showed that the airplane had collided with the top 2 lines of a 4-line power line. The propeller struck the top line and the nose gear hit the second line down. The airplane hit the ground with the right wing, tumbled, and came to rest inverted. The purpose of the flight was for the pilot to gain some experience, with a pilot-rated passenger onboard, in his recently purchased airplane. The pilot reported that, after completing about 10 touch-and-go landings at a nearby airport, he flew the airplane back to his home airport for a full-stop landing. The pilot announced the he was entering a left downwind, reduced the speed, and lowered the landing gear. After turning to final approach, the pilot lowered the flaps and was concentrating on lining up the airplane on the runway centerline. The pilot-rated passenger stated that the airplane was lined up on the runway but that it seemed a little low. The passenger stated that, after passing over a tree line, the pilot surprised him by reducing the power rather than increasing it. Subsequently, the airplane descended into power lines and then impacted the ground and tumbled inverted. The pilot stated that he did not see the power lines nor that he was looking for any because they "had not been a factor" in his previous approaches. The power lines were located about 1/4 mile from the airport. Evidence at the accident site revealed that the airplane had impacted the top two lines of a four-line power line. After the accident, the pilot stated that there were no mechanical issues with the airplane that would have precluded normal operation. It is likely that the pilot failed to adequately monitor the environment and to maintain sufficient altitude to clear the power lines. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or F (Factor).
- C Personnel issues-Psychological-Attention/monitoring-Monitoring environment-Pilot - C
- C Personnel issues-Action/decision-Info processing/decision-Decision making/judgment-Pilot - C
- C Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Altitude-Not attained/maintained - C
- C Environmental issues-Physical environment-Object/animal/substance-Wire-Effect on operation - C
Verbatim from NTSB's published report. Source file
NTSB_2017_CEN17LA097.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.