FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN16FA062 · Piper PA46 500TP

10 Dec 2015 · Council Bluffs, IA, United States

Airsea Charters Piper PA46 500TP · Accident: controlled flight into terrain/object (CFIT) on approach

From Eppley Airfield (OMA) to Perry Stokes Airport (TAD)

Report a problem

Event

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

Piper PA46 500TP

Aircraft type
Piper PA46
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
N145JR
Onboard fatalities
Unknown
Route
From Eppley Airfield (OMA), Omaha, NETo Perry Stokes Airport (TAD), Trinidad, CO
Aircraft age
About 12 years (built 2003)
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 pattern base
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
Controlled flight into terrain/object (CFIT)
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 › Psychological
  • Personnel issues › Task performance

Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.

NTSB narrative

The private pilot was conducting a personal cross-country flight. Shortly after takeoff, the pilot told the air traffic controller that he needed to return to the airport due to an attitude heading reference system (AHRS) "miscommunication." Air traffic control radar data indicated that, at that time, the airplane was about 1.75 miles north of the airport on a southeasterly course about 2,000 ft. mean sea level. About 20 seconds after the pilot requested to return to the airport, the airplane began to descend. The airplane subsequently entered a right turn, which appeared to continue until the final radar data point. The airplane struck power lines about 3/4 of a mile from the airport while maneuvering within the traffic pattern. The power lines were about 75 ft. above ground level.

A postaccident examination of the airframe and engine revealed no preimpact mechanical malfunctions or failures that would have precluded normal operation. Although the pilot reported a flight instrumentation issue to air traffic control, the investigation was unable to confirm whether such an anomaly occurred based on component testing and available information. Examination of the standby airspeed indicator revealed that the link arm had separated from the pin on the rocking shaft assembly; however, it likely separated during the accident sequence. No other anomalies were observed. Functional testing indicated that the standby airspeed indicator was likely functional and providing accurate airspeed information to the pilot throughout the flight. Finally, examination of the left and right annunciator panel bulb filaments associated with the left fuel pump advisory revealed that they were stretched, indicating that the left fuel pump advisory indication annunciated at the time of the accident; however, this likely occurred during the accident sequence as a result of an automatic attempt to activate the left fuel pump due to the loss of fuel pressure immediately after the left wing separated.

Toxicology testing of the pilot detected low levels of three different sedating antihistamines; however, antemortem levels could not be determined nor could the underlying reason(s) for the pilot's use of these medications. As a result, it could not be determined whether pilot impairment occurred due to the use of the medications or the underlying condition(s) themselves.

Although the pilot reported a flight instrumentation issue, this problem would not have affected his ability to control the airplane. Further, the pilot should have been able to see the power lines given the day/visual weather conditions. It is possible that the pilot become distracted by the noncritical anomaly, which resulted in his failure to maintain clearance from the power lines.

Probable cause

The pilot's failure to maintain clearance from power lines while returning to the airport after becoming distracted by a noncritical flight instrumentation anomaly indication.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN16FA062
Event ID
20151211X65337
Case number
CEN16FA062
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: 6c649937ff2e1acbdb44e6d8fab6bb63779beb505e35041caffc8a8ea3ea8bc3; retrieved 2026-09-14T21:35:24.960Z.