FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI83FA022 · Cessna R182

20 Oct 1982 · Lemont, IL, United States

TK Aviation Cessna R182 · Accident: in flight encounter with weather en route

From Chicago Midway International Airport (MDW) to Fayetteville, AR

Report a problem

Event

NTSB case
CHI83FA022
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
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
Visual Meteorological Cond

Cessna R182

Aircraft type
Cessna 182
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
N736NA
Operator
TK Aviation
Onboard fatalities
Unknown
Route
From Chicago Midway International Airport (MDW), Chicago, ILTo Fayetteville, AR
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
Tree(s)
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 › In-flight planning/decision, improper
  • Wing › Ice

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

THE PILOT TOOK OFF AT 0642 CDT, AND AT 0645, HE REPORTED LEVEL AT 4000 FT MSL. AT 0659:08, HE PREPORTED THAT HE WAS ENCOUNTERING ICING CONDITIONS AND REQUESTED A CLIMB TO 6000 FT. AT 0700:16, AFTER CHANGING FROM TRACON TO CENTER FREQUENCY, HE WAS CLEARED AS REQUESTED. AT 0700:37, THE PILOT REPORTED THAT HE THOUGHT HE WOULD HAVE TO DESCEND. THE CONTROLLER WAS UNABLE TO APPROVE A LOWER ALTITUDE ON COURSE, BUT CLEARED THE PILOT FOR A TURN (TO REVERSE COURSE) AND DESCEND TO 3000 FT. NO OTHER TRANSMISSIONS WERE RECEIVED FROM THE AIRCRAFT AFTER THAT. JUST PRIOR TO THE ACCIDENT, WITNESSES OBSERVED THE PLANE DESCENDING ON A NORTHERLY HEADING WITH THE WINGS ROCKING. THEY REPORTED THAT THE ENGINE WAS OPERATING. INITIAL IMPACT WAS WITH A TREE ON RISING TERRAIN. THE AIRCRAFT THEN STRUCK THE GROUND ON SLIGHTLY HIGHER TERRAIN, 16 FT BELOW AND 95 FT FROM THE INITIAL IMPACT POINT. THE WIND WAS STRONG FROM THE SOUTHWEST. PRIOR TO THE FLIGHT, THE PILOT WAS ADVISED OF THE POTENTIAL FOR ICING AND TURBULENCE.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record CHI83FA022
Event ID
20020917X04427
Case number
CHI83FA022
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: af510cb23a6bbdba82d028a26dcd03ba9cddf40c2181bc94d9f4bd6572b21655; retrieved 2026-09-21T07:38:51.128Z.