FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI04FA069 · Piper PA-28-180

17 Feb 2004 · Rich Hill, MO, United States

Piper PA-28-180 · Accident: in flight encounter with weather en route

From Allen County Airport (K88) to Spirit of St Louis Airport (SUS)

Report a problem

Event

NTSB case
CHI04FA069
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
2 · 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-28-180

Aircraft type
Piper PA-28
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
N7876W
Operator
Unknown
Onboard fatalities
Unknown
Route
From Allen County Airport (K88), Iola, KSTo Spirit of St Louis Airport (SUS), 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 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 encounter with weather
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 › Aircraft control, not maintained
  • Pilot in command › Spatial disorientation

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

NTSB narrative

The aircraft was destroyed during an in-flight collision with terrain following a loss of control during cruise. A witness who resided approximately one mile northwest of the accident site reported that he was awakened from a "deep sleep" to the sound of an airplane engine. He stated that he looked out the window and saw the aircraft's lights at what appeared to be "tree top height" about 1/4 to 1/2 mile to the east-southeast. He went outside but at that point the aircraft was out of site. He heard no sound at all at that time. He recalled that it was foggy. As it got light that morning, he noted that there was a low cloud layer. The accident site was located in an uninhabited wetlands conservation area on a 150-foot wide by 10-foot high hill, situated between a small river and a marsh area. Initial impact was on the north side of the hill. The main wreckage came to rest on the opposite side of the hill, about 120 feet from the initial impact. A detailed post-accident examination of the aircraft was conducted. No evidence consistent with a pre-impact failure or malfunction was observed. Weather reporting in the vicinity of the accident site was limited. The departure airport recorded visibilities of one statute mile (sm) at the approximate time of departure. Airports in the vicinity of Kansas City, about 50 miles north and northwest of the accident site, recorded instrument meteorological conditions (IMC), with visibilities of 1/4 sm in fog and vertical visibilities of 100 feet. Airports south of the route of flight reported visual meteorological conditions (VMC). Satellite imagery depicted an area of low stratus and fog over the region, with cloud tops of approximately 5,000 feet msl. The non-instrument rated pilot contacted a Flight Service Station and obtained a pre-flight weather briefing. The briefer advised the pilot that an advisory for instrument flight rules (IFR) conditions was in effect for his route of flight and that visual flight rules (VFR) flight was not recommended. The briefer provided weather conditions at Emporia, 47 miles northwest of the departure airport, as overcast clouds at 200 feet agl and 3/4 sm visibility in mist. Conditions at Chanute, 13 miles south of the departure airport, were clear below 12,000 feet agl and 6 miles visibility in mist. The briefer commented on the limited weather reporting in the area, stating: "The problem in that area where you are there is very limited weather reporting . . . except for Emporia and Chanute and . . . they're just drastically different." The pilot replied: "Well we're pretty close to Chanute so I think I'll be OK." The area forecast in effect at the time of the accident was for broken ceilings at 1,000 feet agl and cloud tops at 5,000 feet mean sea level (msl) over the eastern one-third of Kansas. The southwest quarter of Missouri was forecast to have overcast ceilings at 5,000 feet agl. The northwest quarter of Missouri was forecast for overcast ceilings at 1,000 feet agl and cloud tops to 4,000 feet msl. Civil twilight began at 0641 and sunrise was at 0708. Radar track data depicted the accident aircraft proceeding from a point about 1-1/2 miles east of the departure airport, on an east-northeast course at a maximum altitude of 5,200 feet msl. Final radar contact was at 4,900 feet msl, about 1/2 mile northwest of the accident site. In the 1-1/2 minutes immediately prior to the final radar data point, the aircraft entered a marked right turn. The radar track depicted was consistent with a gradually decreasing turn radius. The lowest expected radar coverage in the vicinity of the accident site was 3,800 feet msl. The pilot's total logged flight time was 158.3 hours, including 11.1 hours simulated instrument and 0.2 hours actual instrument flight time.

Probable cause

Spatial disorientation experienced by the non-instrument rated pilot due to a lack of visual references and his subsequent failure to maintain control of the aircraft. Contributing factors were the pilot's intentional flight into adverse weather conditions, the overcast cloud layer, low lighting conditions (night) and fog.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI04FA069
Event ID
20040219X00206
Case number
CHI04FA069
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: 451a366b975364ec550a1798a5df6e93cd0964b252ac86a9ef3e51d9adbe2e9d; retrieved 2026-09-20T18:33:21.527Z.