FTW95LA120 · Cessna T210M
Cessna T210M · Accident: airframe, component or system failure en route
From Aspen-Pitkin County Airport (Sardy Field) (ASE) to Telluride Regional Airport (TEX)
Event
- NTSB case
- FTW95LA120
- 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
- 0
- 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 T210M
- Aircraft type
- Cessna 210
- 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
- N6094B
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Aspen-Pitkin County Airport (Sardy Field) (ASE), Aspen, COTo Telluride Regional Airport (TEX), Telluride, CO
- Aircraft age
- Not recorded
- 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
- First occurrenceThe 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
- Airframe, component or system 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
- Landing gear, emergency extension assembly › Bent
- Weather condition › Icing conditions
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
WHILE IN CRUISE FLIGHT, A TOTAL LOSS OF ELECTRICAL POWER OCCURRED. THE PILOT CIRCLED AN AIRPORT TO BURN OFF FUEL AND ATTEMPTED TO LOWER THE LANDING GEAR BY THE ALTERNATE METHOD. THE NOSE LANDING GEAR EXTENDED AND THE MAIN LANDING GEAR WOULD NOT EXTEND BEYOND THE TRAIL POSITION. THE PILOT CONDUCTED A PRECAUTIONARY LANDING AND THE AIRCRAFT DEPARTED THE SIDE OF THE RUNWAY DURING THE LANDING ROLL. A MECHANIC, WHO EXAMINED THE AIRCRAFT IMMEDIATELY FOLLOWING THE LANDING, FOUND A CONSIDERABLE AMOUNT OF AIRFRAME ICE. THE SAME MECHANIC LATER EXAMINED THE ELECTRICAL SYSTEM AND COULD FIND NO DISCREPANCIES. A BENT EXTENSION ROD WAS FOUND ON THE LANDING GEAR EXTEND MECHANISM.
Probable cause
THE BENT LANDING GEAR EMERGENCY EXTENSION ASSEMBLY AND THE ACCUMULATION OF AIRFRAME ICE WHICH INTERFERED WITH LANDING GEAR ACTIVATION. A FACTOR WAS THE ALTERNATOR FAILURE FOR UNKNOWN REASONS.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW95LA120
- Event ID
- 20001207X02969
- Case number
- FTW95LA120
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: e25d3705f94e520fc10c6707135c0ce5ac01fd20e3fabb1b425850978e3ccccb; retrieved 2026-09-23T00:14:58.041Z.