ATL85FA113 · Cessna 182
Cessna 182 · Accident: in flight encounter with weather en route
From Springfield, MO to WOODBARDY, VA
Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- ATL85FA113
- 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 182
- 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
- N5430B
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route Possible conflict
- From Springfield, MOTo WOODBARDY, VA
- 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
Cause areas
- Pilot in command › Altitude, improper
- Pilot in command › Flight into known adverse weather, continued
- Pilot in command › Weather evaluation, disregarded
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE ACFT IMPACTED TREES AND CAME TO REST 400 FT DOWNSLOPE FROM THE TOP OF CLINCH MOUNTAIN. THE NON-INSTRUMENT RATED PLT DEPARTED SPRINFIELD, MO, WITH A CEILING OF APRX 300-400 FT AGL. THE PLT THEN LANDED AT COOKEVILLE, TN, WHERE HE RECEIVED A WX BRIEFING AND FUEL. THE PLT STATED TO THE FSS BRIEFER, HE HAD TO DEVIATE SOUTH OF HIS ORIGINALLY PLANNED COURSE BECAUSE OF WX AND HE WANTED TO EXTEND HIS FLT PLAN. THE PLT WAS ADVISED DURING THE BRIEFING THAT VFR WAS NOT RECOMMENDED ALONG THE ROUTE OF FLT BECAUSE OF RAINSHOWERS, LOW CEILINGS AND LOW VISIBILITIES. COOKEVILLE WAS MVFR BUT IFR WAS FORECAST ALONG THE ROUTE AS THE DETERIORATING WX MOVED SOUTH. WX IN THE AREA OF THE ACCIDENT AT THE TIME WAS REPORTED AS BEING MARGINAL.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record ATL85FA113
- Event ID
- 20001214X35820
- Case number
- ATL85FA113
- 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: 541693543ba606f8763158d207cb808fc95b73025a3ab75177303a5059dbf5ab; retrieved 2026-09-21T05:07:11.395Z.