FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

DEN83FA027 · Cessna P210

30 Nov 1982 · Sioux Falls, SD, United States

Cessna P210 · Accident: in flight collision with terrain/water on approach

From 3V5 · FT. COLLINS, CO to Youngstown Warren Regional Airport (YNG)

Report a problem

Event

NTSB case
DEN83FA027
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 P210

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
N4721P
Operator
Robert G. Ocheltree · private individual
Onboard fatalities
Unknown
Route
From 3V5 · FT. COLLINS, COTo Youngstown Warren Regional Airport (YNG), Youngstown, OH
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
Approach · IFR final approach
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 › Decision height, below
  • Pilot in command › IFR procedure, improper
  • Pilot in command › Missed approach, not performed

Approximate · Estimated position: the centre of Sioux Falls, SD, the place the record names. Not the accident site.

NTSB narrative

AT 1915 WHILE ENROUTE THE PLT WAS ADVISED THAT THE DESTINATION WX WAS 100 FT OBSCURED, 3/8 MI IN FOG. AT 2140 THE PLT CONTACTED APPROACH CONTROL & WAS ADVISED THE WX WAS 100 FT OBSCURED & 1/8 MI WITH AN RVR FOR RWY 3 OF 2,400 FT. HE WAS CLEARED FOR AN ILS RWY 3 APPROACH & ADVISED THE RVR WAS NOW 1,600 FT. DURING THE APPROACH THE PLT WAS ADVISED TWICE OF BEING FIRST RIGHT OF COURSE & THEN LEFT OF COURSE. AT ABOUT 2207 THE PLT EXECUTED A MISSED APPROACH & AT 2217 WAS CLEARED FOR A SECOND APPROACH. DURING THE SECOND APPROACH THE PLT WAS AGAIN ADVISED OF GOING LEFT OF COURSE. THE ACFT CRASHED APPROXIMATELY 1,250 FT LEFT OF THE LOCALIZER COURSE & APPROXIMATELY 3,250 FT PAST THE THRESHOLD TO RWY 3.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record DEN83FA027
Event ID
20020917X04535
Case number
DEN83FA027
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 1982-12-01.
  • API snapshot SHA-256: 37c62783891c8da2946e98a4f5204d556ecee61b1bec783435b2fcc0d1f3f562; retrieved 2026-09-21T07:26:33.674Z.