Grand Aire Express Flight GAX179
Dassault Aviation DA-20C · Accident: total loss of engine power (non-mechanical) on approach
From Del Rio International Airport (DRT) to St. Louis Lambert International Airport (STL)
Event
- NTSB case
- CHI03FA099
- 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
- Unknown
- 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
- Charter & commuter
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Instrument Meteorological Cond
Dassault Aviation DA-20C
- Aircraft type
- Dassault DA-20
- 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
- N179GA
- Operator
- Grand Aire Express
- Onboard fatalities
- Unknown
- Route
- From Del Rio International Airport (DRT), Del Rio, TXTo St. Louis Lambert International Airport (STL), St Louis, MO
- 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 135: Air Taxi & Commuter
- 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
- 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 › In-flight planning/decision, improper
- Pilot in command › Unsafe/hazardous condition, not relayed
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The twin engine turbofan powered airplane was ditched into a river after a complete loss of power from both engines. The airplane was on a second approach to land on runway 30R after having been instructed by air traffic control (ATC) to climb during the final approach segment of the first approach due to inadequate separation from another airplane. Subsequent to the first approach, the airplane was issued vectors for the second approach by ATC. Communications transcripts show that the flight crew asked ATC how far they would be vectored during the second approach, but the flight crew did not inform ATC of their low fuel state until the airplane was already on a "base turn...to join final." The airplane subsequently lost power from both engines. During interviews, both pilots stated that there were no problems with the airplane. The second-in-command (SIC) stated that the airplane "ran out of fuel" and that the fuel quantity indicators read 0 and 100 pounds when each respective engine stopped producing power. The SIC also stated that after being instructed to climb to 5,000 feet after their first approach, he questioned the pilot-in-command about landing at another airport located about 14 nautical miles west-southwest of the destination airport. The SIC said that the PIC elected to continue with the second approach to the original destination. Research indicated that the flight crew did not obtain a weather briefing prior to the accident flight. Additionally, the Terminal Aerodrome Forecast that was valid at the time the aircraft's flight plan was filed showed a forecast ceiling consisting of overcast clouds at 1,500 feet above ground level at the aircraft's arrival time at the destination. 14 CFR Part 91.169 requires that an alternate airport be listed in the flight plan when forecast ceilings are less than 2,000 feet. No alternate was listed in the flight plan for the accident flight. Additionally, 14 CFR Part 91.167 requires that aircraft operated in instrument meteorological conditions maintain fuel reserves that allow flight to the intended destination and then continued flight to the listed alternate, and an additional 45 minutes at normal cruise speed. In 1993, the FAA/industry advisory committee developed advisory material for fuel planning and management for 14 CFR Part 121 and 135 air carrier flight operations, but the material was never published.
Probable cause
The pilot in command's improper in-flight decision not to divert to an alternate destination resulting in the exhaustion of the airplane's fuel supply, and his failure to relay his low fuel state to air traffic control in a timely manner.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI03FA099
- Event ID
- 20030418X00531
- Case number
- CHI03FA099
- 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, coordinates. 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: 5c2f595b0ee91000a932da92eb08b066bc5041a10f64ea9f18bcb9bf6719c0c1; retrieved 2026-09-18T15:52:39.164Z.