FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

GAA16CA173 · Beech F35

30 Mar 2016 · Long Island, NC, United States

Beech F35 · Accident: low altitude operation/event while maneuvering

From Long Island Airpark (NC26) to Lake Norman Airpark (14A)

Report a problem

Event

NTSB case
GAA16CA173
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

Beech F35

Aircraft type
Beechcraft 35
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
N4212B
Operator
Unknown
Onboard fatalities
Unknown
Route
From Long Island Airpark (NC26), Long Island, NCTo Lake Norman Airpark (14A), Mooresville, NC
Aircraft age
About 61 years (built 1955)
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
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

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Action/decision

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

NTSB narrative

The pilot reported that during the initial climb, he leveled off at about 65 feet above the ground and made a right turn to follow a river. After maneuvering down the river for about one minute, the airplane struck uncharted and unmarked power lines that spanned across the entire length of the river. He reported that the impact from the power lines cracked the windscreen and damaged the vertical stabilizer, but aircraft control was not affected and he was able to continue to the destination airport about 3 nautical miles away. The pilot further reported that he never saw the power lines that the airplane impacted, but he did observe larger charted power lines about one mile ahead.

The left vertical stabilizer was substantially damaged.

The pilot did not report any mechanical malfunctions or failures with the airplane that would have precluded normal operation.

Probable cause

The pilot's decision to maneuver at low altitude, which resulted in a collision with power lines and substantial damage to the vertical stabilizer.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record GAA16CA173
Event ID
20160404X31701
Case number
GAA16CA173
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: 0754143497fd66b0eb05fdc4e62467c296bdeb895f2979c60440294a17488971; retrieved 2026-09-16T03:16:06.884Z.