Copper Valley Air Service Cessna 185 E accident
Cessna 185 E · Accident: aircraft structural failure en route
From Gulkana Airport (PAGK) to PMXY · McCarthy, AK
Event
- NTSB case
- ANC21FA015
- 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
- 2 · 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
Cessna 185 E
- Aircraft type
- Cessna 185
- 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
- N9725Z
- Operator
- Copper Valley Air Service
- Onboard fatalities
- Unknown
- Route
- From Gulkana Airport (PAGK), Glennallen, AKTo PMXY · McCarthy, AK
- Aircraft age
- About 55 years (built 1966)
- 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 · 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
- Aircraft structural failure
- 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
- Not determined › Not determined
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot was conducting a scheduled passenger flight in the single-engine airplane in day visual meteorological conditions. Recovered data from an onboard GPS unit revealed that, after reaching a GPS altitude of about 7,500 ft, the airplane flew on a southeast track for about 10 minutes with a groundspeed between 120 and 130 knots. About 2 minutes before the accident, the airplane initiated a gradual right turn to the south and began a descent that averaged about 734 ft per minute. The last fully recorded in-flight data point showed the airplane at a GPS altitude of 5,715 ft with a groundspeed of 154 kts.
The distribution of the wreckage at the accident site indicated a high-speed, near vertical impact, with portions of the right wing and empennage scattered between 400 and 700 ft from the main wreckage, consistent with an in-flight breakup. Fractured areas of the right wing, the left deformation of the vertical stabilizer and rudder, and the fractured attach points were consistent with overload separation of the right wing, which caused the airplane to snap roll to the right, creating the necessary torsional forces to deform the vertical stabilizer and twist the empennage from the fuselage. Examinations on the engine and airframe did not reveal evidence of any pre-existing anomalies that would have precluded normal operation. Flight control continuity was established, and the propeller showed evidence of rotation at impact.
All of the fractured surfaces exhibited a dull, grainy appearance consistent with overstress separation. There was no evidence of fatigue or corrosion noted on any of the areas examined. The reason for the overstress and subsequent in-flight breakup could not be determined based on the available information.
Probable cause
An in-flight breakup during cruise flight for reasons that could not be determined based on available evidence.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC21FA015
- Event ID
- 20210205102605
- Case number
- ANC21FA015
- 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, cause areas. 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: 13ea868cdc079d28473379e87a9fa1f7ed62acf079bc2a13c0ba534cfe67d26d; retrieved 2026-09-15T07:25:06.144Z.