NYC85FA083 · Cessna 401A
Cessna 401A · Accident: in flight encounter with weather en route
From Essex County Airport (CDW) to Rutland - Southern Vermont Regional Airport (RUT)
Event
- NTSB case
- NYC85FA083
- 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
- Visual Meteorological Cond
Cessna 401A
- Aircraft type
- Cessna 401
- 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
- N12CQ
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Essex County Airport (CDW), Caldwell, NJTo Rutland - Southern Vermont Regional Airport (RUT), Rutland, VT
- 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
- 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 › Clearance, not maintained
- Pilot in command › VFR flight into imc, initiated
- Pilot in command › Visual lookout, not possible
Approximate · Estimated position: the centre of Dorset, VT, the place the record names. Not the accident site.
NTSB narrative
THE PLT WAS ABOUT 30 MILES FROM RUTLAND WHEN HE RADIOED THE ARPT FOR WEATHER INFO. HE WAS INFORMED THAT CLOUDS WERE 1500 FT BROKEN AND 2700 FT OVERCAST WITH SNOW, LIGHT FOG AND 5 MILES VISIBILITY. THE PLT RESPONDED THAT HE WOULD CALL AGAIN WHEN HE GOT CLOSER TO THE ARPT. THERE WAS NO FURTHER TRANSMISSION RECEIVED FROM THE PLT. THE ACFT COLLIDED WITH DORSET MT, LOCATED ABOUT 18 MILES SOUTH OF THE ARPT. THE ACFT WAS IN A LEVEL ATTITUDE AND AT A ELEVATION OF 3300 FT. DORSET MT IS 3515 FT HIGH. EXAMINATION OF THE ACFT DID NOT DISCLOSE EVIDENCE OF MALFUNCTION. NO FLT PLAN WAS FILED.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record NYC85FA083
- Event ID
- 20001214X36023
- Case number
- NYC85FA083
- 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 1985-03-18.
- API snapshot SHA-256: 3d38b3bd2677724dd5d6c1156409fd88b510d4869cdff6fe74fb8e9f43faa25c; retrieved 2026-09-21T05:06:18.969Z.