NYC84FA022 · Cessna 210L
Cessna 210L · Accident: in flight encounter with weather during initial climb
From 46N · RHINEBECK, ME to an unrecorded destination
Event
- NTSB case
- NYC84FA022
- 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
- Visual Meteorological Cond
Cessna 210L
- 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
- N1177Q
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From 46N · RHINEBECK, METo not recorded
- 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
- Initial climb
- 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)
- 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 › Aircraft handling, uncontrolled
- Pilot in command › Preflight briefing service, not obtained
- Pilot in command › Spatial disorientation
- Pilot in command › VFR flight into imc, initiated
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE ABOVE REPORTED BASIC WX DATA WAS THE 2050 OBSERVATION AT POUGHKEEPSIE, NY LOCATED ABOUT 20 NM SOUTH OF THE ACCIDENT SITE. HOWEVER, A WITNESS WHO WAS 1,000 FT NORTH OF THE ACCIDENT SITE STATED THE WX CONSISTED OF A LOW OVERCAST & THAT THE VISIBILITY WAS CLOSE TO ZERO. HE OBSERVED THE ACFT PASS OVERHEAD THREE TIMES AT ABOUT 300 FT AGL & SAW THE ACFT'S LIGHTS PARTIALLY HIDDEN IN FOG. THE ACFT THEN EMERGED OUT OF THE FOG IN A RIGHT TURN & DESCENDED TO THE GROUND. A PILOT REPORTED THAT THE SKY WAS CLEAR ABOUT 15 MI SOUTH OF THE ARPT BUT AT 10 MI SOUTH OF THE ARPT THE WX DROPPED TO 2,000 FT OVERCAST WITH 5-7 MI VISIBILITY IN LIGHT DRIZZLE.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record NYC84FA022
- Event ID
- 20001214X45172
- Case number
- NYC84FA022
- 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 1983-11-06.
- API snapshot SHA-256: 27c1e053bdab3cf8e7437e22da28f779ae68cbb04a59c248603e586eecff2c33; retrieved 2026-09-21T05:55:46.431Z.