FTW98LA281 · Rockwell COMMANDER 112 COMMANDER
Rockwell COMMANDER 112 COMMANDER · Accident: loss of engine power en route
From Cortez Municipal Airport (CEZ) to FTG · Denver, CO
Event
- NTSB case
- FTW98LA281
- 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
Rockwell COMMANDER 112 COMMANDER
- Aircraft type
- Rockwell 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
- N1188J
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Cortez Municipal Airport (CEZ), Cortez, COTo FTG · Denver, CO
- 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
- Loss of engine power
- 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 › Procedures/directives, misjudged
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot received his pilot's license on May 11, 1996 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.
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 aviation experience, and lack of total experience in make/model of aircraft.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW98LA281
- Event ID
- 20001211X10323
- Case number
- FTW98LA281
- 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: 3d53b2dc1c8cfe9562afa838e7077e487651c05fcd47e9db6a5142d798b095c7; retrieved 2026-09-21T20:48:36.802Z.