CHI04FA066 · Beech B90
Beech B90 · Accident: in flight collision with terrain/water en route
From Wichita Dwight D. Eisenhower National Airport (ICT) to Dodge City Regional Airport (DDC)
Event
- NTSB case
- CHI04FA066
- 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
- 3 · 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
- 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
Beech B90
- Aircraft type
- Beechcraft 90
- 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
- N777KU
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Wichita Dwight D. Eisenhower National Airport (ICT), Wichita, KSTo Dodge City Regional Airport (DDC), Dodge City, KS
- 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 · descent
- 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
- In flight collision with terrain/water
- 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
- Pilot in command › Clearance, not maintained
- Pilot in command › Fatigue(lack of sleep)
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The emergency medical services (EMS) airplane was destroyed by terrain impact and post impact fire about 7 nautical miles (nm) west of its destination airport, Dodge City Regional Airport (DDC), Dodge City, Kansas. The 14 Code of Federal Regulations Part 91 positioning flight departed the Wichita Mid-Continental Airport (ICT), Wichita, Kansas, about 0215 central standard time and was en route to DDC. Night visual meteorological conditions prevailed when the accident occurred about 0257 central standard time. The flight had been on an instrument flight rules (IFR) flight plan, but the pilot cancelled the IFR flight plan about 34 nm east of DDC and initiated a descent under visual flight rules. Radar track data indicated that the airplane maintained a magnetic course of about 265 degrees during the flight from ICT to DDC. The rate of descent was about 850 to 950 feet per minute. During the descent, the airplane flew past the airport on a 270 degree course. Witnesses in the area reported hearing the engine noise of a low-flying airplane followed by the sound of impact. One of the witnesses described the engine noise as sounding like the engines were at "full throttle." The on-site inspection revealed that the airplane impacted the terrain in a gear-up, wings-level attitude. The inspection of the airplane revealed no anomalies to the airframe or engines. A review of the pilot's 72-hour history before the accident revealed that it had been 14 hours and 32 minutes from the time the pilot reported for duty about 1225 central standard time until the time of the accident. It had been 20 hours 57 minutes from the time the pilot awoke (0600) on the morning before the accident until the time of the accident. No evidence of pilot impairment due to carbon monoxide, drugs, or medical incapacitation was found. The accident occurred during a time of day that was well past the pilot's normal bedtime and also at a time of day when the physiological need to sleep is especially strong. The findings from a Safety Board's human performance analysis indicates that the pilot was likely fatigued. A review of 14 CFR 135.267 indicated that the pilot had adhered to the flight time limitations and rest requirements specified in the regulation.
Probable cause
The pilot failed to maintain clearance with terrain due to pilot fatigue (lack of sleep).
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI04FA066
- Event ID
- 20040220X00214
- Case number
- CHI04FA066
- 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: b4a4f3feffaa9b73732612f44e34481b69a5741419584a361c2f02bd85b8f602; retrieved 2026-09-20T18:33:31.260Z.