CHI90FA263 · Cessna 172N
Cessna 172N · Accident: in flight encounter with weather on approach
From Vermilion Regional Airport (DNV) to an unrecorded destination
Event
- NTSB case
- CHI90FA263
- 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
- 0
- 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
- N75785
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Vermilion Regional Airport (DNV), Danville, ILTo not recorded
- 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
- Approach · VFR pattern base
- 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 › VFR flight into imc, continued
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE FLIGHT ORIGINATED FROM AUSTIN, MN AT 2010. DURING THE WEATHER BRIEFING THE PILOT WAS ADVISED OF RESTRICTED VISIBILITIES REPORTED BY THREE REPORTING STATIONS IN THE AREA OF THE DESTINATION, AND A 3 DEG TEMP/DEW POINT SPREAD AT TERRA HAUTE, IN (23 MI NE OF PARIS, IL). THE PILOT DECLINED RECEIVING FORECASTS. DURING THE INTERMEDIATE STOP AT DANVILLE, THE DEPLANED PASSENGER STATED THAT THE LANDING LIGHTS WERE PENETRATING 'THE FOG WE WERE IN', AND THAT THE LIGHT MADE A 'SHAFT' IN THE FOG AREA. SHORTLY THEREAFTER THE AIRPLANE CRASHED 1 MI SE OF THE APPROACH END OF RWY 27 AT THE PARIS, IL AIRPORT. THE ACCIDENT LOCATION WAS CONSISTENT FOR A BASE LEG TO THE RWY. ACCORDING TO THE AIRPORT MANAGER THE AIRPORT BEACON COULD NOT BE SEEN BEYOND 600-700 FT HORIZONTALLY.
Probable cause
THE PILOT'S CONTINUATION OF VFR FLIGHT INTO INSTRUMENT METEOROLOGICAL CONDITIONS. FACTORS CONTRIBUTING TO THE ACCIDENT WERE THE FOG AND THE DARK NIGHT.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI90FA263
- Event ID
- 20001212X24213
- Case number
- CHI90FA263
- 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. 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: e980e016f7225807d2bf873c24675093bec096dbcf9987a40f28142aa827b9ac; retrieved 2026-09-21T02:12:59.445Z.