SEA92LA194 · Piper PA-46-310P
Piper PA-46-310P · Accident: total loss of engine power (non-mechanical) en route
From Salt Lake City International Airport (SLC) to an unrecorded destination
Event
- NTSB case
- SEA92LA194
- 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
Piper PA-46-310P
- Aircraft type
- Piper PA-46
- 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
- N1005B
- Operator
- Shrontz, Joanne L. · private individual
- Onboard fatalities
- Unknown
- Route
- From Salt Lake City International Airport (SLC), Salt Lake City, UTTo not recorded
- 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 · descent
- 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 › Planned approach, misjudged
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
DURING A BUSINESS CROSS COUNTRY FLT, THE PLT REPORTED THAT HE WAS AWARE OF A LOW FUEL STATUS WHILE EN ROUTE, BUT THOUGHT THAT HE COULD MAKE IT TO HIS FINAL DESTINATION WITHOUT STOPPING FOR FUEL. THE FLT WAS CLEARED TO DESCEND AT 96 MILES FROM THE ARPT. AT APRX 16 TO 18 MILES FROM THE ARPT, THE ENGINE LOST POWER. DURING THE DESCENT, THE PLT FELT THAT THE AIRPLANE WAS HIGH ON THE APPROACH AND EXTENDED THE LANDING GEAR AND LOWERED ONE NOTCH OF FLAPS. AT APRX ONE HALF MILE FROM THE RWY, THE AIRPLANE BEGAN TO DESCEND BELOW THE INTENDED GLIDE. UNABLE TO REACH THE RWY, THE AIRPLANE TOUCHED DOWN APRX 200 FT SHORT OF THE RWY, COLLIDING WITH THE TERRAIN DURING THE LANDING ROLL. AFTER THE ACCIDENT, THE PLT REPORTED THAT HE APPARENTLY DID NOT HAVE AS MUCH FUEL ON BOARD AS HE THOUGHT HE DID BEFORE TAKEOFF, AND MISJUDGED THE APPROACH BY LOWERING THE LANDING GEAR TOO SOON.
Probable cause
A MISJUDGED APPROACH. FACTORS TO THE ACCIDENT WERE: INACCURATE FUEL CONSUMPTION CALCULATIONS AND FUEL EXHAUSTION.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA92LA194
- Event ID
- 20001211X15770
- Case number
- SEA92LA194
- 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: f3cc85c6db706bf9f4c7bbf804ffa752fad557aac235545675d9908c64a1731e; retrieved 2026-09-23T02:41:27.352Z.