M and M Aviation Gulfstream 500B accident
Gulfstream 500B · Accident: total loss of engine power (non-mechanical) on approach
From OKC Will Rogers World Airport (OKC) to Charles B. Wheeler Downtown Airport (MKC)
Event
- NTSB case
- CHI97LA110
- 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
- Charter & commuter
- 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
Gulfstream 500B
- Aircraft type
- Gulfstream 500
- 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
- N4918
- Operator
- M and M Aviation
- Onboard fatalities
- Unknown
- Route
- From OKC Will Rogers World Airport (OKC), Oklahoma City, OKTo Charles B. Wheeler Downtown Airport (MKC)
- 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
- Pole
- 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
- Fuel system › Exhaustion
- Pilot in command › Preflight planning/preparation, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot was on the fourth leg of a night flight when he reported to air traffic control that both engines had sustained a total loss of power. The airplane contacted a pole and landed hard during the off airport forced landing. The pilot had flown this route previously in the same make and model aircraft, however this was the pilots first time flying this route in this airplane. Only trace amounts of fuel were found in the airplane's center fuel tank which feeds both engines. No compromised fuel tanks were found on the airplane, and no odor of fuel, or fuel stains were found in the area around the accident site. Testing of the airplane's fuel gauge, and fuel sender following the accident did not reveal any discrepancies.
Probable cause
the pilot's inadequate preflight planning which resulted in fuel exhaustion.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI97LA110
- Event ID
- 20001208X07688
- Case number
- CHI97LA110
- 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: 70e942bd467975604bfaf6adff790f74842fe9e9224e0686c1ee412fd6e4c369; retrieved 2026-09-18T17:37:36.958Z.