FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Ameriflight Beech C 99 accident

1 Aug 2016 · Spanish Fork, UT, United States

Beech C 99 · Accident en route

From Carbon County Regional Airport / Buck Davis Field (PUC) to Salt Lake City International Airport (SLC)

Report a problem

Event

NTSB case
WPR16LA155
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
Charter & commuter
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 C 99

Aircraft type
Beechcraft C-99
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
N234AV
Operator
Ameriflight
Onboard fatalities
Unknown
Route
From Carbon County Regional Airport / Buck Davis Field (PUC), Price, UTTo Salt Lake City International Airport (SLC), Salt Lake City, UT
Aircraft age
About 30 years (built 1986)
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 135: Air Taxi & Commuter
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
En route · climb to cruise
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
Miscellaneous/other
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

  • Personnel issues › Psychological

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The commercial pilot of the scheduled cargo flight reported that, during cruise flight about 8,000 ft indicated altitude, he heard a small impact noise and believed that the airplane was struck by a bird. There was no loss of directional control, change in control configuration, or impact shudder. He continued the flight and subsequently landed without further incident. After exiting the airplane, the pilot noticed that about 12 inches of the top of the vertical stabilizer was missing, and that there was substantial damage to the rudder.

The separated top of the vertical stabilizer section was not recovered. The fracture surface of the upper section of the remaining vertical stabilizer was in a nearly horizontal plane. The skin was deformed adjacent to the fracture into curled rolls turning downward and aft. Some areas were crushed, consistent with the vertical stabilizer moving forward relative to another object. Sliding contact marks were observed at the leading edges, vertical spars, and deformed faces of the skin panel adjacent to the fracture. No evidence of any biological or manufactured foreign material transfer was observed associated with any of the fracture surfaces either visually or under optical magnification. Closer examination identified deposits of particles consistent with aluminum alloy 2024 and similar metallic element peaks. Other particles had spectra consistent with a low alloy steel, stainless steel, brass, and a nickel-base alloy with iron and chromium. The curling deformation to the skin and the deformation through the airplane structure was consistent with contact with a stationary object, such as a suspended cable. Given the diameter of the impact deformation and the materials found, it is likely that the airplane impacted overhead power transmission lines during a portion of the flight that was conducted at an altitude much lower than reported.

Probable cause

An in-flight collision with power lines.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR16LA155
Event ID
20160802X22428
Case number
WPR16LA155
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: local date, investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2016-08-02.
  • API snapshot SHA-256: 45403669b1081ae0d20215fbf87006b3a3fa6c7eaee93917abd67f178d4940a1; retrieved 2026-09-16T03:44:10.583Z.