FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ATL86FA239 · Cessna P206-B

1 Sept 1986 · WHT SULPHUR SPR, WV, United States

Greenbrier Airlines Cessna P206-B · Accident: in flight encounter with weather while maneuvering

From James M. Cox Dayton International Airport (DAY) to SSU

Report a problem

Event

NTSB case
ATL86FA239
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
Instrument Meteorological Cond

Cessna P206-B

Aircraft type
Cessna 206
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
N4782F
Onboard fatalities
Unknown
Route
From James M. Cox Dayton International Airport (DAY), Dayton, OHTo SSU
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
Maneuvering
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)
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, poor
  • Pilot in command › Missed approach, not performed
  • Pilot in command › Preflight planning/preparation, inadequate
  • Pilot in command › Procedures/directives, not followed
  • Pilot in command › Self-induced pressure
  • Pilot in command › VFR flight into imc, attempted

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

NTSB narrative

AFTER COMPLETING THE REVENUE PRODUCING PORTION OF THIS TRIP THE COMPANY PRESIDENT CALLED HIS COMPANY OPERATIONS AND TOLD HIS SECRETARY TO SEND EVERYONE HOME SINCE IT WAS A HOLIDAY. HE WAS GOING TO RETURN THE ACFT TO ITS HOME BASE HIMSELF. THE PLT DEPARTED VFR, AIR FILED AND FLEW AN IFR FLT PLAN TO THE FINAL APCH FIX TO THE CLOSEST ARPT WITH AN INSTRUMENT APCH, CANCELLED THE IFR FLT PLAN AND HEADED TOWARD THE HOME ARPT VFR. FOG AND LOW CEILINGS WERE IN THE AREA AT THE TIME. THE ARPT WAS EQUIPPED WITH RWY LIGHTS BUT DID NOT HAVE STROBES ON EITHER END, IT WAS LOCATED IN A VALLEY. AN ACFT WAS OBSERVED EAST OF THE APT LATER IN THE NIGHT. IT HAD ALREADY PASSED THE ARPT AND WAS IN A TURN WHEN LAST OBSERVED. AN ALNOT WAS ISSUED DURING THE NIGHT FOR THE MISSING ACFT. IT WAS DISCOVERED THE NEXT DAY ABOUT ONE-HALF MILE WEST AND NORTH OF THE ARPT, ON THE SOUTH-WEST SIDE OF A MOUNTAIN.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record ATL86FA239
Event ID
20001213X34690
Case number
ATL86FA239
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 1986-09-02.
  • API snapshot SHA-256: 0de7ed6e45c6923e4a5f5f15c35d0805e685e8e04937f71b925184e96e769f0f; retrieved 2026-09-21T04:24:35.518Z.