SEA95LA008 · Cessna R172K
Cessna R172K · Accident: total loss of engine power (non-mechanical) on approach
From Logan-Cache Airport (LGU) to St George Regional Airport (SGU)
Narrative check · The NTSB narrative appears to contradict this record's aircraft involved. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- SEA95LA008
- 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 R172K Possible conflict
- 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
- N7327K
- Operator
- Hoyt, Nathan K. · private individual
- Onboard fatalities
- Unknown
- Route
- From Logan-Cache Airport (LGU), Logan, UTTo St George Regional Airport (SGU)
- 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 base
- 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)
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Fuel exhaustion
- 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 › Fuel consumption calculations, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT REPORTED 'HALF TANKS' BEFORE DEPARTING FOR HIS DESTINATION AT 1740 HOURS. WHILE IN THE TRAFFIC PATTERN FOR LANDING AT THE DESTINATION, THE ENGINE SPUTTERED AND LOST POWER. THE PILOT TURNED THE AIRPLANE TOWARD THE RUNWAY AND THE ENGINE RESUMED POWER FOR A SHORT TIME BEFORE LOSING ALL POWER. THE PILOT WAS UNABLE TO MAKE THE RUNWAY AND LANDED ON THE PARKING RAMP. DURING THE LANDING ROLL, THE AIRPLANE COLLIDED WITH A PARKED AIRCRAFT. THE ACCIDENT OCCURRED APPROXIMATELY 2 HOURS AND 50 MINUTES AFTER TAKEOFF. A SMALL AMOUNT OF FUEL WAS FOUND IN BOTH WING FUEL TANKS. SEVERAL DAYS AFTER THE ACCIDENT THE ENGINE WAS STARTED AND FOUND TO RUN WITH NO NOTED ABNORMALITIES.
Probable cause
INADEQUATE FUEL CONSUMPTION CALCULATIONS. FACTORS TO THE ACCIDENT WERE: FUEL EXHAUSTION AND A PARKED AIRCRAFT IN THE LANDING PATH.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA95LA008
- Event ID
- 20001206X02533
- Case number
- SEA95LA008
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1994-10-10.
- API snapshot SHA-256: e1da0b1996e4270027a88efd83273afa56763ab44a1fe4bb6659a3a1b9d30317; retrieved 2026-09-21T22:28:05.992Z.