NYC86FA237 · Cessna 337D
Cessna 337D · Accident: in flight encounter with weather en route
From Florence Regional Airport (FLO) to N17 · Endicott, NY
Event
- NTSB case
- NYC86FA237
- 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 337D
- Aircraft type
- Cessna 337
- 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
- N2680S
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Florence Regional Airport (FLO), Florence, SCTo N17 · Endicott, NY
- 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
- 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 › Altitude, not maintained
- Pilot in command › In-flight planning/decision, improper
- Pilot in command › Preflight planning/preparation, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE ACFT COLLIDED WITH THE TERRAIN DURING THE PLTS ATTEMPT TO COMPLETE A NIGHT X-COUNTRY IN IMC WX CONDITIONS. THE FLT HAD PROGRESSED APRX 4 HRS & 34 MIN FROM SC TO NY PRIOR TO THE CRASH. THE PLT WAS NOT CURRENTLY RATED TO FLY IFR. THE PLT REPORTED BY RADIO TO SYRACUSE APPRCH CONTROL THAT HE LOST AN ENG TRYING TO APPROACH HIS DEST AND HE WAS GOING TO BINGHAMTON NY. THE WX WENT BELOW MINIMUMS AT BINGHAMTON AND THE CONTROLLING AGENCIES WERE UNABLE TO MAINTAIN RADIO CONTACT WITH N2680S. CONTACT WAS TRIED THRU OTHER ACFT . ONE ACFT SAID HE HEARD TRANSMISSIONS FROM N2680S BUT NO ANSWERING ACKNOWLEDGEMENTS. A SHORT TIME LATER RADAR CONTACT WAS LOST. THE ACFT CRASHED IN A FIELD WITH A TREE LINE NEAR LAPEER NY. ON SITE INVESTIGATION DETERMINED THAT BOTH ENGINES WERE PRODUCING PWR AT IMPACT. ALL CHECKS INDICATED NORMAL OPERATION. THERE WAS NO EVIDENCE OF ANY MALFUNTION OF THE ACFT. TOXICOLOGY SCREENING RESULTS WERE NEGATIVE FOR THE PLT.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record NYC86FA237
- Event ID
- 20001213X34857
- Case number
- NYC86FA237
- 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: c82d5383d7a31913fa04056238193ef2245ee0a440b6814e3ac0edd7d0154432; retrieved 2026-09-21T04:23:38.479Z.