SEA92LA170 · Cessna 411
Jump West Cessna 411 · Accident: total loss of engine power (non-mechanical) while maneuvering
From Salt Lake City International Airport (SLC) to Cedar Valley Airport (UT10)
Event
- NTSB case
- SEA92LA170
- 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 411
- Aircraft type
- Cessna 411
- 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
- N136CH
- Operator
- Jump West
- Onboard fatalities
- Unknown
- Route
- From Salt Lake City International Airport (SLC), Salt Lake City, UTTo Cedar Valley Airport (UT10), CEDAR FORT, 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
- Maneuvering
- 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 › Airspeed(vmc), not maintained
- Pilot in command › Gear extension, not performed
- Pilot in command › Lowering of flaps, not performed
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT WAS FERRYING THE ACFT BACK TO BASE AFTER ANNUAL INSPECTION AND WAS PERFORMING FUEL SYSTEM CHECKS AT A LOW ALTITUDE AGL WHEN THE RIGHT ENGINE QUIT. HE LOST ALTITUDE AND AIRSPEED WHILE ATTEMPTING TO RESTART THE ENGINE, AND THE ACFT STARTED TO ROLL WHEN HE INCREASED POWER ON THE LEFT ENGINE. HE REDUCED THE LEFT THROTTLE AND MADE A FORCED LANDING IN AN OPEN FIELD WITH THE LANDING GEAR AND FLAPS RETRACTED.
Probable cause
THE FAILURE BY THE PILOT TO MAINTAIN AIRSPEED ABOVE VMC, RESULTING IN LOSS OF CONTROL IN FLIGHT, AND HIS FAILURE TO LOWER THE FLAPS AND LANDING GEAR FOR THE FORCED LANDING. A FACTOR RELATING TO THE ACCIDENT WAS THE PILOT'S DECISION TO PERFORM FUEL SYSTEM CHECKS IN FLIGHT AT A LOW ALTITUDE AGL.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA92LA170
- Event ID
- 20001211X15269
- Case number
- SEA92LA170
- 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: 751af790b1dfb1e1ab7eeb42811494268ab14f9819b4612db7540a58eedacedc; retrieved 2026-09-23T02:53:17.983Z.