FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI06LA005 · Cessna 172RG

9 Oct 2005 · Union City, OH, United States

Cessna 172RG · Accident: in flight encounter with weather en route

From D96 · Coldwater, MI to Lexington, KY

Report a problem

Event

NTSB case
CHI06LA005
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 172RG

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
N6085R
Operator
Unknown
Onboard fatalities
Unknown
Route
From D96 · Coldwater, MITo Lexington, KY
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
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
Visual flight rules (VFR) flight into instrument meteorological conditions (IMC)
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
  • Pilot in command › VFR flight into imc, inadvertent
  • Pilot in command › Weather evaluation, not performed

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 when it impacted the ground and subsequently burned. The airplane was being operated by a non-instrument rated private pilot who was fatally injured during the accident. Weather reporting stations near the accident site recorded instrument meteorological conditions with low ceilings and reduced visibilities. There was no record of the pilot having received a weather briefing or filing a flight plan for the flight. On-scene examination of the airplane and its systems did not reveal any evidence of a pre-impact failure.

Probable cause

The pilot's failure to perform a preflight weather evaluation which led to his inadvertent flight into instrument meteorological conditions and his spatial disorientation. The low ceilings and the dark night were contributing factors.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI06LA005
Event ID
20051017X01659
Case number
CHI06LA005
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: baefd3f545db5e95c41ca67d91e0ba279f678be928a97d92f6dfc70de68b5cfc; retrieved 2026-09-20T17:49:57.094Z.