DEN99LA007 · Cessna 210A
Cessna 210A · Accident: total loss of engine power (non-mechanical) on approach
From U77 · Spanish Fork, UT to Provo Municipal Airport (PVU)
Event
- NTSB case
- DEN99LA007
- 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 210A
- 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
- N9449X
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From U77 · Spanish Fork, UTTo Provo Municipal Airport (PVU), 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
- Approach · VFR pattern final
- 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
- Total loss of engine power (non-mechanical)
- 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 › Flight manuals, not followed
- Pilot in command › Throttle/power control, abrupt
Approximate · Estimated position: the centre of Provo, UT, the place the record names. Not the accident site.
NTSB narrative
The pilot was low on the approach to runway 36, and so he 'quickly pushed the throttle in' and there was a total power loss. The pilot turned the fuel pump to HIGH boost, and pushed the mixture in to full rich. He then pulled the mixture back to idle cut-off. The engine sputtered momentarily. Attempts to restart the engine were unsuccessful. The airplane was ditched in Utah Lake, just short of the approach end of runway 36. The engine was later functionally tested and it operated satisfactorily at all power settings. A mechanic told the pilot he had flooded the engine when he 'quickly pushed the throttle in.'
Probable cause
The pilot's abrupt throttle control movement that caused the engine to flood, and his failure to follow emergency procedures contained in the Airplane Flight Manual. Factors were increasing the mixture control to full rich and switching the fuel pump to high boost.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DEN99LA007
- Event ID
- 20001211X11240
- Case number
- DEN99LA007
- 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: 5e969bc7e25abf711ece85331d03522de7784c3f2dce75e6e52ea64688d16f6c; retrieved 2026-09-22T16:32:41.979Z.