FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN16FA005 · Beech P35

6 Oct 2015 · Chadron, NE, United States

Beech P35 · Accident: controlled flight into terrain/object (CFIT) en route

From Chadron Municipal Airport (CDR) to Alliance Municipal Airport (AIA)

Report a problem

Event

NTSB case
CEN16FA005
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
Instrument Meteorological Cond

Beech P35

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
N877DM
Operator
Unknown
Onboard fatalities
Unknown
Route
From Chadron Municipal Airport (CDR), Chadron, NETo Alliance Municipal Airport (AIA), Alliance, NE
Aircraft age
About 52 years (built 1963)
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
En route · 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
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
Destroyed

Cause areas

  • Environmental issues › Conditions/weather/phenomena
  • Environmental issues › Physical environment
  • 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 airline transport pilot departed in the single-engine airplane on a cross-country flight under visual flight rules (VFR) in visual meteorological conditions (visibility 9 miles and ceiling broken at 1,500 ft above ground level); however, instrument meteorological conditions existed along the planned route of flight. Shortly after departure, the pilot established radio communications with air traffic control and requested activation of the instrument flight rules (IFR) flight plan he had previously filed. The flight was issued a discrete transponder code; however, due to other workload in his airspace sector, the controller did not immediately confirm radar contact or issue an IFR clearance to the pilot. Because the pilot had not received an IFR clearance, he remained under VFR and responsible for maintaining terrain, obstacle, and cloud clearance. According to track data and topographic elevation data, the airplane encountered rising terrain as it flew south from the departure airport. The airplane subsequently impacted treetops and a ridgeline about 10 miles south of the departure airport at 4,200 ft msl. The height of the ridgeline was about 900 ft above the departure airport elevation. An individual working outside near the accident site reported that weather conditions included light precipitation, mist, fog, and low clouds that obscured the surrounding ridgelines. Thus, the airplane likely encountered instrument meteorological conditions before it collided with the ridgeline during cruise flight. Further, a postaccident wreckage examination did not reveal any anomalies that would have precluded normal operation of the airplane during the flight. Although the departure airport was equipped with a remote communication outlet, it was out of service at the time of the accident and could not be used to obtain an IFR clearance. However, the pilot could have obtained an IFR clearance on the ground by telephoning a flight service station. Alternatively, the pilot could have departed under VFR and maneuvered over the airport in visual meteorological conditions until he received an IFR clearance. The pilot's decision to attempt VFR flight into instrument meteorological conditions resulted in controlled flight into rising terrain during cruise flight.

Probable cause

The pilot's continued visual flight rules flight into instrument meteorological conditions, which resulted in controlled flight into rising terrain during cruise flight.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN16FA005
Event ID
20151006X15935
Case number
CEN16FA005
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: f12da4b62aca7be76480b6ec308f75d60c935ff01d5de97e462eadbd5224c2f3; retrieved 2026-09-14T21:32:09.078Z.