FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI04FA157 · Piper PA-24-180

16 Jun 2004 · Great Bend, KS, United States

Piper PA-24-180 · Accident: in flight collision with terrain/water en route

From Great Bend Municipal Airport (GBD) to Great Bend Municipal Airport (GBD)

Report a problem

Event

NTSB case
CHI04FA157
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
4 · 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
Instrument Meteorological Cond

Piper PA-24-180

Aircraft type
Piper PA-24
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
N6698P
Operator
Unknown
Onboard fatalities
Unknown
Route
From Great Bend Municipal Airport (GBD), Great Bend, KSTo Great Bend Municipal Airport (GBD)
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
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 › Altitude/clearance, not maintained
  • Pilot in command › Flight into adverse weather, inadvertent
  • Pilot in command › Preflight planning/preparation, inadequate

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The airplane was destroyed during an in-flight collision with terrain in night instrument meteorological conditions. The non-instrument rated private pilot and three passengers sustained fatal injuries. The flight encountered a rapidly moving line of thunderstorms after takeoff and was attempting to return to the departure airport at the time of the accident. The pilot contacted Wichita Automated Flight Service Station (AFSS) while in-flight, about 15 minutes prior to the accident. He reported his position as 4 miles north of the airport and intended to conduct a local flight. The AFSS briefer stated that an area of "pretty severe thunderstorms" were immediately to the west and estimated that the storms would be getting into the area within the next 5 minutes. The briefer added: "I would not recommend . . . flying around the . . . area at this time." The pilot replied that he was turning around and returning to the airport. The were no further communications with the accident pilot. There was no record of a pre-flight weather briefing being obtained by the pilot. A witness reported seeing an aircraft flying near her home about 10 minutes prior to the accident. She commented, "the wind started to come up and the dirt started blowing, then raining. I could not see across the field in front of my house." A second witness stated that about the time of the accident, he and his wife were at their residence watching a thunderstorm in progress. He reported that they heard a low flying aircraft approaching from the east. He noted that he looked out a window and saw a plane at a low altitude. He added that as the aircraft banked toward the northwest, a bolt of lightning struck near the house. The accident site was located the following morning in a field immediately north of his residence. Weather recorded at the departure airport about 5 minutes after the accident noted northwest winds gusting to 23 knots, 1/2 mile visibility with thunderstorms, broken clouds 200 feet above ground level (agl), and overcast clouds at 900 feet agl. A convective SIGMET was in effect for severe thunderstorms moving through the area, with storm tops exceeding 45,000 feet mean sea level, moving to the east at 30 knots. Weather radar data depicted a line of thunderstorms moving through the area. About 30 minutes prior to the accident the extreme east edge of the thunderstorm line arrived over the area. In the image recorded about 25 minutes after the accident, this area had passed over and was located approximately 15 miles to the east. The Federal Aviation Administration (FAA) Civil Aero Medical Institute toxicology report stated that the pilot's blood alcohol level was 54 mg/dL (0.054 percent by weight). FAA regulations prohibited any person from acting as the pilot of a civil aircraft while under the influence of alcohol or while having a 0.04 or greater percent by weight of alcohol in their blood.

Probable cause

The pilot's inadequate preflight planning due to his failure to obtain a weather briefing prior to takeoff. Additional causes were the pilot's inadvertent flight into adverse weather and his failure to maintain clearance with the terrain during his attempt to return to the departure airport. Contributing factors were the pilot's impairment due to alcohol, the low altitude at which the aircraft was flying, the thunderstorms and associated turbulence in the area, the low ceilings, and the dark night lighting conditions.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI04FA157
Event ID
20040706X00907
Case number
CHI04FA157
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: local date, investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2004-06-17.
  • API snapshot SHA-256: 56d8262ded2c2256e6c87c9ce5c4dad98567533f2dc05a88bb4b320bcc38f588; retrieved 2026-09-20T18:26:35.382Z.