# Accident 19980620028379A: Gulstm 112, Las Vegas, NM, June 20, 1998

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: June 20, 1998, 12:30 local time
- Place: Las Vegas, NM
- Damage: Substantial damage
- Phase of flight: Fcd/Prec Ldg From Cruise
- Operating rules: General operating rules (Part 91)
- Location: 35.5898° N, 105.2209° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=35.5898&lon=-105.2209&mi=10
- Aircraft: N1188J, a cancelled registration (https://openairdocs.org/deregistered/N1188J-2013-11-04) (OpenAirDocs)
- Registry model: Aero Commander 112 (registry code 0144701, https://openairdocs.org/model/aero-commander-112) (OpenAirDocs)
- Registry engine: Lycoming I0360 SER A&C (registry code 41511, https://openairdocs.org/engine/lycoming-i0360-ser-a-c) (OpenAirDocs)
- Reported make and model: GULSTM 112
- Reported engine: LYC IO360C1D6
- Fatal injuries: 0
- Pilot flight hours: 78 total, 7 in this make and model, 14 in the last 90 days
- NTSB investigation: [NTSB FTW98LA281](https://openairdocs.org/ntsb/FTW98LA281) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19980620028379A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

(.4)THE PILOT RECEIVED HIS PILOT'S LICENSE ON MAY 11, 1998 AND HAD ACCUMULATED 78 HOURS OF FLIGHT EXPERIENCE. HE RECENTLY PURCHASED THIS COMPLEX AIRPLANE AND HAD 7.3 HOURS OF EXPERIENCE IN IT BEFORE THE ACCIDENT FLIGHT. HE WAS CONDUCTING A CROSS-COUNTRY FLIGHT AND DIVERTED SOUTH THROUGH NEW MEXICO DUE TO TURBULENCE.  THE PILOT STATED THAT HIS INITIAL TIME EN ROUTE WAS 1.5 HOURS, HOWEVER, INVESTIGATION REVEALED THAT HE HAD AIRBORNE FOR 2.5 HOURS AND THAT THE AIRCRAFT NORMALLY BURNS 10-14 GALLONS PER HOUR.  HE SAID HE LOST ENGINE POWER NEAR LAS VEGAS, NEW MEXICO, DUE TO 'FUEL EXHAUSTION' AND LANDED IN SOFT VEGETATED TERRAIN.  THE PILOT REPORTED THAT 'HIS FUEL GAUGES INDICATED THAT HE HAD FUEL, SO HE CONTINUED TO FLY.'  HE LATTER REPORTED THAT HE HAD PUT 25 GALLONS OF FUEL ON THE AIRPLANE BEFORE THE FLIGHT IN WHICH THE ACCIDENT OCCURRED.                                                     (-23) ON 06/20/98, APPROXIMATELY 1300 MOUNTAIN DAYLIGHT TIME, AN AERO COMMANDER MODEL 112, N1188J, OWNED BY MR. TODD L. FLANNERY, WAS SUBSTANTIALLY DAMAGED WHEN IT IMPACTED TERRAIN DURING A FORCED LANDING APPROXIMATELY 15 MILES SOUTHEAST OF THE LAS VEGAS, NM (LVS) AIRPORT. THE PILOT-IN-COMMAND, AND  SOLE OCCUPANT OF THE AIRCRAFT, HOLDS A PRIVATE PILOT CERTIFICATE WITH AIRPLANE, SINGLE ENGINE, LAND RATING. THE PILOT RECEIVED MINOR INJURIES WHEN THE AIRCRAFT STRUCK A JUNIPER TREE DURING LANDING. VISUAL METEOROLOGICAL CONDITIONS PREVAILED, AND NO FLIGHT PLAN WAS FILED FOR THE PERSONAL FLIGHT, WHICH WAS CONDUCTED UNDER 14 CFR PART 91. THE FLIGHT ORIGINATED FROM CORTEZ, CO, AND WAS ENROUTE TO DENVER, CO. THE PILOT STATED HE DIVERTED SOUTH ACROSS NEW MEXICO TO AVOID TURBULENCE HE HAD ENCOUNTERED OVER THE MOUNTAINS. PERSONNEL ON THE GROUND AT THE LAS VEGAS, NM AIRPORT REPORTED HEARING THE PILOT CALL THAT HE HAD EXPERIENCED ENGINE FAILURE AND BELIEVED HE HAD "RUN OUT OF GAS." DUE TO DAMAGE TO THE AIRCRAFT, THE INVESTIGATION BY FAA PERSONNEL WAS UNABLE TO POSITIVELY DETERMINE IF THE AIRCRAFT HAD SUFFERED FUEL EXHAUSTION.

## The NTSB's investigation of this event (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB FTW98LA281](https://openairdocs.org/ntsb/FTW98LA281), Jun 20, 1998: Rockwell Commander 112 (N1188J), Las Vegas, NM, substantial damage. Probable cause: The pilot's improper preflight planning/preparation for a cross country flight resulting in fuel exhaustion and subsequent loss of engine power. Factors were, unsuitable terrain, lack of total…

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.