CEN16FA224 · Cessna 320E E
Rocky Mountain Aerial Surveys Cessna 320E E · Accident: loss of control in flight en route
From Central Colorado Regional Airport (AEJ) to an unrecorded destination
Event
- NTSB case
- CEN16FA224
- 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
- 3 · 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
Cessna 320E E
- Aircraft type
- Cessna 320
- 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
- N777GY
- Operator
- Rocky Mountain Aerial Surveys
- Onboard fatalities
- Unknown
- Route
- From Central Colorado Regional Airport (AEJ), Buena Vista, COTo not recorded
- Aircraft age
- About 48 years (built 1968)
- 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
- 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
- Loss of control in flight
- 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
- Aircraft › Aircraft power plant
- Not determined › Not determined
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The commercial pilot and crew were conducting aerial photography work under contract with the U.S. Department of Agriculture. Shortly after departure, the pilot noticed an engine vibration coming from the airplane's right side and returned to the departure airport to have a mechanic inspect the engine. The pilot called the company operator to notify the company's owner of the engine anomaly; the operator and the crew agreed that they would stop aerial photography work and return to the operator's base in Longmont, Colorado but that they would call the operator's base to provide an update on the mechanics' findings before departing; however, the operator received no further communications from the crew.
GPS data showed the airplane departing AEJ and then heading south in the opposite direction of the operator's base and overflying one aerial survey point near C24. The airplane maintained an altitude of between 11,300 and 13,000 ft mean sea level (msl) with a ground speed between 120 to 169 knots for most of the flight. The last two minutes of flight showed the airplane circling around C24 while decreasing in altitude and fluctuating in airspeed between 140kts and 98kts. During the last 3 minutes of the flight, the airplane was descending, and the groundspeed decreased from 141 knots to 98 knots, before increasing to 128 knots and then rapidly decreasing to 99 knots during a sharp, 90º left turn to the north. The last recorded parameter showed the airplane at 8,665 ft msl with a groundspeed of 99 knots.
Witnesses stated that the airplane was on a left base for the runway but did not appear to be correctly positioned or high enough for the pattern into the airport. One witness stated that the airplane appeared to yaw and then return to wings level while descending to the ground. One witness stated he saw the propellers turning; however, two witnesses reported that they did not hear engine sounds.
Flight control continuity was established from all control surfaces to the cockpit input controls. Left and right engine test-runs and examinations revealed no evidence of any preaccident mechanical malfunctions or failures that would have precluded normal operation. However, examination of the left and right propellers indicated that the engines were likely operating with low to no power at the time of impact. Additionally, both propellers had several indications consistent with operating near their low-pitch position and they were not in the feathered position, consistent with the engines not being shut down by the pilot. The flaps were set to the 10º position and the gear was up, consistent with an approach configuration.
The pilot's autopsy findings revealed that he had an enlarged heart and moderate coronary artery disease, which slightly increased his risk of impairment from a cardiovascular event. However, there was no evidence of recent or old ischemic damage to the heart muscle or evidence of pilot impairment or incapacitation. Therefore, it is unlikely the pilot's cardiovascular disease contributed to the accident.
Given the evidence, it is likely the engines experienced a loss of power and that the pilot subsequently lost airplane control during the descent to the airport for landing, which resulted in impact with terrain. The reason for the dual loss of engine power could not be determined based on available evidence.
Probable cause
The pilot's loss of airplane control during descent following a loss of engine power for reasons that could not be determined because postaccident examinations and engine test-runs of both engines revealed no evidence of any mechanical malfunctions or failures that would have precluded normal operation.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN16FA224
- Event ID
- 20160620X21154
- Case number
- CEN16FA224
- 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: 787a7bc746116f2bee2ad6515151354e3555456f8c3ece2d48a62b75a100b559; retrieved 2026-09-14T21:51:14.542Z.