WPR11LA362 · Cessna 172S
Leading Edge Aviation Cessna 172S · Accident: loss of engine power (partial) en route
From Salt Lake City International Airport (SLC) to Ogden Hinckley Airport (OGD)
Event
- NTSB case
- WPR11LA362
- 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
- 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
- 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 172S
- Aircraft type
- Cessna 172
- 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
- N235GW
- Operator
- Leading Edge Aviation
- Onboard fatalities
- Unknown
- Route
- From Salt Lake City International Airport (SLC), Salt Lake City, UTTo Ogden Hinckley Airport (OGD), Ogden, 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
- 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
- Loss of engine power (partial)
- 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
- Aircraft › Aircraft power plant
- Personnel issues › Task performance
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 reported that during cruise flight, the engine started running rough and began losing power. The pilot manipulated the throttle and mixture controls, but the engine continued losing power. All engine power was lost on approach during the forced landing to an alfalfa field, and the airplane nosed over during the landing roll. The engine had received a factory major overhaul and was installed in the airplane about 14 operational hours before the accident. Since installation, it had not received any maintenance. Postaccident examination of the engine found that the B-nut fitting on the fuel supply hose that goes from the fuel injection servo to the distribution spider was loose, which caused a fuel starvation-induced loss of engine power. No other mechanical malfunctions or failures were identified that would have precluded normal operation.
Probable cause
The failure of the maintenance technicians who installed the engine to properly tighten the fuel injection servo to a spider supply line, which caused a loss of engine power due to fuel starvation.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR11LA362
- Event ID
- 20110803X74307
- Case number
- WPR11LA362
- 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: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2011-08-02.
- API snapshot SHA-256: a54e709bc445d0e4c46b6b2477fd33d5f7ffa7b75d65d1b4c66f30d8cf296ad5; retrieved 2026-09-15T16:33:43.267Z.