CEN14LA129 · Cessna 525
Brink Constructors Cessna 525 · Accident: controlled flight into terrain/object (CFIT) on approach
From Rapid City Regional Airport (RAP) to Elk City Regional Business Airport (ELK)
Event
- NTSB case
- CEN14LA129
- 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
- Instrument Meteorological Cond
Cessna 525
- Aircraft type
- Cessna 525
- 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
- N61YP
- Operator
- Brink Constructors
- Onboard fatalities
- Unknown
- Route
- From Rapid City Regional Airport (RAP), Rapid City, SDTo Elk City Regional Business Airport (ELK), Elk City, OK
- Aircraft age
- About 16 years (built 1998)
- 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 · IFR final approach
- 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 › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The airline transport pilot was conducting a business flight with six passengers on board. Radar data showed that, after crossing the final approach fix for an instrument approach at the destination airport, the airplane descended below the minimum descent altitude (MDA) of 2,480 ft mean sea level (msl); dark night, instrument meteorological conditions existed at that time. Subsequently, when the airplane was about 2 miles from the airport and about 2,070 ft msl, the airplane impacted a utility pole, which was 10 ft above ground level (agl). After impacting the pole, the pilot executed a missed approach, and about 40 minutes later, he landed the airplane without further incident at another airport. On-scene examination showed that the impact had scattered debris from the separated utility pole for about 200 ft into a snow-covered field. Examination of the airplane revealed that the impact resulted in substantial damage to the nose structure, lower and upper fuselage, and horizontal stabilizer. Further examinations of the airplane, including its static system, both altimeters, both vertical speed indicators, and the radar altimeter system revealed no evidence of preaccident mechanical malfunctions or failures that would have precluded normal operation.
The pilot reported that he thought he had leveled the airplane at an altitude above the MDA and that at no time during the descent and approach did the airplane's radar altimeter sound an alert indicating that the airplane was below 400 ft agl radar altitude. He also reported that he never saw the terrain, any obstructions, nor the runway lights or airport environment. Despite the pilot's statement, given the radar data and the impact evidence, it is apparent that he descended the airplane below the MDA, which resulted in the subsequent impact with the utility pole. It could not be determined why the radar altimeter did not alert the pilot that the airplane was only 10 ft above the ground.
The pilot's second-class medical certificate, which had been issued more than 20 months before the accident, had expired. The medical certificate limitation section in the expired certificate stated, "Not valid for night flying or by color signal control." There is no evidence that these restrictions contributed to the accident.
Probable cause
The pilot’s descent below the published minimum descent altitude for the instrument approach procedure, which resulted in impact with a utility pole.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN14LA129
- Event ID
- 20140204X20036
- Case number
- CEN14LA129
- 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. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2014-02-04.
- API snapshot SHA-256: 46fc1d637b548947ec8ba1a959fb384707e8be716384853b5d6de33d7a3e570c; retrieved 2026-09-15T23:18:06.486Z.