FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA95FA207 · Cessna 210C

8 Aug 1995 · Dawsonville, GA, United States

Cessna 210C · Accident: in flight collision with terrain/water while maneuvering

From Roanoke–Blacksburg Regional Airport (ROA) to Lakefront Airport (NEW)

Report a problem

Event

NTSB case
MIA95FA207
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 210C

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
N3698Y
Operator
Unknown
Onboard fatalities
Unknown
Route
From Roanoke–Blacksburg Regional Airport (ROA), Roanoke, VATo Lakefront Airport (NEW), New Orleans, LA
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 collision with terrain/water
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 › Flight into known adverse weather, attempted
  • Pilot in command › Weather forecast, disregarded

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

NTSB narrative

THE PILOT DEPARTED VFR AND LANDED AT AN INTERMEDIATE AIRPORT TO CHECK ON THE WEATHER CONDITIONS ALONG HIS ROUTE OF FLIGHT. A WEATHER BRIEFING WAS OBTAINED FROM A FLIGHT SERVICE STATION. THE PILOT WAS ADVISED OF A STATIONARY FRONT, AND MARGINAL VFR TO IFR CONDITIONS ALONG HIS ROUTE OF FLIGHT. THE PILOT DEPARTED VFR. THE AIRPLANE COLLIDED WITH MOUNTAINOUS TERRAIN WHILE MANEUVERING IN A DESCENDING RIGHT TURN. IFR CONDITIONS PREVAILED AT THE TIME OF THE ACCIDENT. THE AIRPLANE WAS LOCATED 11 DAYS AFTER THE ACCIDENT. THE PILOT'S LOGBOOK WAS NOT FOUND BUT FRIENDS OF HIS REPORTED THAT HE 'HAD INDICATED VERBALLY, SEVERAL TIMES, THAT HE HAD NOT FLOWN ON INSTRUMENTS IN IMC FOR OVER 20 YEARS.'

Probable cause

THE PILOT'S DISREGARD OF THE WEATHER FORECAST AND FLIGHT INTO KNOWN ADVERSE WEATHER (INSTRUMENT FLIGHT CONDITIONS), RESULTING IN AN IN-FLIGHT COLLISION WHILE MANEUVERING IN MOUNTAINOUS TERRAIN. CONTRIBUTING TO THE ACCIDENT WAS THE PILOT'S LACK OF RECENT FLYING IN INSTRUMENT FLIGHT CONDITIONS.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA95FA207
Event ID
20001207X04314
Case number
MIA95FA207
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: a3a51a40bf38bf5cdb6d3a84d5cb950aba431b5165b973654bddd3c1e7add053; retrieved 2026-09-20T23:40:22.932Z.