FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI89FA039 · Cessna 210D

1 Jan 1989 · ALVIN, IL, United States

Cessna 210D · Accident: in flight encounter with weather en route

From Tullahoma Regional Airport William Northern Field (THA) to 3HA · Lansing, IL

Report a problem

Event

NTSB case
CHI89FA039
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 210D

Aircraft type
Cessna 210
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
N3767Y
Operator
Unknown
Onboard fatalities
Unknown
Route
From Tullahoma Regional Airport William Northern Field (THA), Tullahoma, TNTo 3HA · Lansing, IL
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); Tree(s); Utility pole
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 › Proper altitude, not maintained
  • Pilot in command › VFR flight into imc, continued

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

NTSB narrative

AFTER A WX BRIEFING AT 0545 EST, THE PLT & 3 PAX DEPARTED FT MYERS, FL, AT 0926, ON A FLT TO LANSING, IL. A REFUELING STOP WAS MADE AT TULLAHOMA, TN, BUT THERE WAS NO EVIDENCE OF AN UPDATED WX BRIEFING & NO FLT PLAN WAS FILED. SUBSEQUENT-LY, THE ACFT CRASHED ABOUT 5 MI NORTH OF THE VERMILLION COUNTY ARPT ON A HEADING OF 230 DEG. INITIAL IMPACT WAS WITH A TREE, ABOUT 35' AGL. THE ACFT THEN HIT A POLE (ABOUT 190' FROM THE TREE) BEFORE IMPACTING THE GROUND. WRECKAGE DEBRIS EXTENDED ABOUT 625' FROM THE INITIAL IMPACT POINT WITH THE TREE. THE RPRTD WX AT THE ARPT WAS IN PART: INDEFINITECEILING, VIS 1/4 MI WITH FOG, WIND FROM 200 DEG AT 7 KTS. NO PREIMPACT PART FAILURE OR MALFUNCTION OF THE ACFT OR ENG WAS EVIDENT.

Probable cause

CONTINUED FLIGHT BY THE NON-INSTRUMENT RATED PILOT INTO INSTRUMENT METEOROLOGICAL CONDITIONS (IMC), AND HIS FAILURE TO MAINTAIN SUFFICIENT ALTITUDE. FACTORS RELATED TO THE ACCIDENT WERE: DARKNESS, ADVERSE WEATHER CONDITIONS, THE PILOT'S LACK OF INSTRUMENT EXPERIENCE, AND HIS FAILURE TO UPDATE HIS WEATHER INFORMATION.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI89FA039
Event ID
20001213X27552
Case number
CHI89FA039
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: def8e579b1c08bcc53487177cd407fd7f2b668e3da1cffcc06f1c92bcf629299; retrieved 2026-09-21T03:26:28.424Z.