LAX93LA169 · Aero Commander 112
Aero Commander 112 · Accident: total loss of engine power (non-mechanical) en route
From Hunt Field (LND) to an unrecorded destination
Event
- NTSB case
- LAX93LA169
- 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
Aero Commander 112
- Aircraft type
- Aero Commander 112
- 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
- N1024J
- Operator
- Albert L. Seamands · private individual
- Onboard fatalities
- Unknown
- Route
- From Hunt Field (LND), LANDERS, WYTo 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 · cruise
- 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
- Destroyed
Cause areas
- Fluid, fuel › Exhaustion
- Pilot in command › Fuel consumption calculations, inaccurate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT REPORTED THAT THE ENGINE LOST POWER WHILE HE WAS ENTERING A DOWNWIND FOR RUNWAY 26 DUE TO FUEL EXHAUSTION AND HE COULD NOT GLIDE TO THE AIRPORT. HE ELECTED TO LAND IN A NEARBY STRAWBERRY FIELD. HE STATED THAT HE HAD FUELED THE AIRPLANE BEFORE DEPARTING LANDERS, WYOMING, BUT DID NOT REFUEL DURING THE FLIGHT. THE WRECKAGE EXAMINATION DISCLOSED THAT BOTH FUEL TANKS WERE EMPTY.
Probable cause
THE PILOT'S INACCURATE FUEL CONSUMPTION CALCULATIONS WHICH RESULTED IN FUEL EXHAUSTION. FACTORS RELATED TO THE ACCIDENT WERE: IMPROPER PREFLIGHT PLANNING/PREPARATION, INADEQUATE FUEL SUPPLY, REFUELING STOP NOT PERFORMED, AND NO SUITABLE TERRAIN FOUND IN THE EMERGENCY LANDING AREA.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX93LA169
- Event ID
- 20001211X12166
- Case number
- LAX93LA169
- 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: dc5183c6882bb016ed0d392e9aa44e73403ed95d85da3a24ea4287d6041fa56c; retrieved 2026-09-21T14:29:14.488Z.