DEN00LA033 · Cessna T210M
Cessna T210M · Accident: airframe, component or system failure en route
From Salt Lake City International Airport (SLC) to St George Regional Airport (SGU)
Event
- NTSB case
- DEN00LA033
- 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
- N6029N
- Operator
- Gary G. Sackett · private individual
- Onboard fatalities
- Unknown
- Route
- From Salt Lake City International Airport (SLC), Salt Lake City, UTTo St George Regional Airport (SGU), Saint George, UT
- 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
- Pilot in command › Procedures/directives, not followed
Approximate · Estimated position: the centre of Cedar City, UT, the place the record names. Not the accident site.
NTSB narrative
While in cruise flight, electrical power was lost due to an alternator failure. The pilot elected to conduct a precautionary landing at an airport short of his destination. When he lowered the landing gear, the nose gear extended and locked down and the main landing gear remained in the up position. The pilot attempted to lower the main landing gear by the alternate method but failed to follow the complete procedure and the mains remained in the up position. He landed the aircraft with the nose landing gear extended and the mains retracted. During the landing sequence, the aircraft incurred damage to horizontal stabilizers and elevators.
Probable cause
The pilot's failure to follow alternate landing gear extension procedures. Factors were the main landing gear failure to extend and a loss of electrical power.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DEN00LA033
- Event ID
- 20001212X19233
- Case number
- DEN00LA033
- 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: ed9479d745db47f0be2b24b3899f97787e8490df974af1078f9b22846cec1eda; retrieved 2026-09-22T14:30:15.732Z.