CHI03FA071 · Cessna 172N
Cessna 172N · Accident: in flight encounter with weather en route
From Wiley Post Airport (PWA) to Augusta Municipal Airport (3AU)
Narrative check · The NTSB narrative appears to contradict this record's damage. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- CHI03FA071
- 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
- 1 · 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
Cessna 172N
- Aircraft type
- Cessna 172
- 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
- N5898E
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Wiley Post Airport (PWA), Oklahoma City, OKTo Augusta Municipal Airport (3AU), Augusta, 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 · 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 Possible conflict
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 substantially damaged during an in-flight collision with terrain. The pilot encountered instrument meteorological weather conditions during a visual flight rules (VFR) flight and subsequently lost control of the aircraft. Weather conditions in the vicinity of the accident site were reported as 800 feet above ground level (agl) overcast. The pilot obtained VFR flight following enroute. Approximately 43 miles from his intended destination, the pilot reported to the controller, "I'm going to have to drop down . . . I went into cloud cover here [at] three thousand five hundred feet." The controller then notified the pilot that weather conditions in the vicinity of the intended destination were below VFR weather minimums. The pilot elected to divert to an alternate airport 14 miles east of the aircraft's position. This decision was based on an automated report, current at the time but taken nearly an hour earlier, of clear skies. An automated report for the alternate airport, coincidentally taken at the time of the accident, reported 800 feet agl broken. A pilot conducting practice instrument approaches in the area at the time reported conditions as overcast with tops about 3,000 feet mean sea level (msl). He noted that it was clear above the clouds and somewhat hazy. He recalled that there was "not much of a horizon" visible. A motorist driving on the interstate reported seeing the aircraft three times. On the third occasion he stated the aircraft flew across the roadway, perpendicular to it, descending at approximately a 45 degree angle relative to the horizon. He reported the aircraft was traveling at a "high rate of speed". He recalled thinking the aircraft was approaching to land. The motorist recalled the weather conditions as very windy and gusty, with a low overcast. According to the motorist, the cloud bases were "rugged", but visibility below the clouds was good. The pilot obtained a preflight weather briefing approximately four hours prior to initiating the accident flight, however no record of an update briefing was found. The pilot was a non-instrument rated private pilot. He had logged 35.0 hours of night flight time and 3.6 hours of simulated instrument time. No actual instrument flight time was recorded in his logbook. His most recently logged flight was nearly four months earlier. A post-accident examination of the airframe and engine revealed no anomalies consistent with a pre-impact failure.
Probable cause
Spatial disorientation experienced by the pilot and his subsequent failure to maintain control of the aircraft. Contributing factors were the pilot's failure to obtain an updated preflight weather briefing prior to the return flight, his attempted flight into known adverse weather, the lack of lighting (night) and the low ceilings.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI03FA071
- Event ID
- 20030219X00239
- Case number
- CHI03FA071
- 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 2003-02-15.
- API snapshot SHA-256: d4e5296650f118304ff0bc6779e4c55f3e222e3bf0849ed626f38f3f5f33833f; retrieved 2026-09-20T19:28:14.923Z.