NYC87FA192 · Cessna 182P
Cessna 182P · Accident: in flight collision with terrain/water en route
From New York Stewart International Airport (SWF) to Syracuse Hancock International Airport (SYR)
Event
- NTSB case
- NYC87FA192
- 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
- 4 · 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 182P
- Aircraft type
- Cessna 182
- 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
- N722DD
- Operator
- Harold T. Limpert · private individual
- Onboard fatalities
- Unknown
- Route
- From New York Stewart International Airport (SWF), NEWBURG, NYTo Syracuse Hancock International Airport (SYR), Syracuse, 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 · climb to 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 collision with terrain/water
- 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 › VFR flight into imc, continued
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE ACFT COLLIDED WITH RISING TERRAIN IN A MOUNTAINOUS AREA OF MINNEWASKA STATE PARK WHILE CLIMBING TO CRUISE ON A VFR FLIGHT. THE CRASH SITE WAS ABOUT 1,430 FEET HIGHER IN ELEVATION THAN THE DEPARTURE AIRPORT. THE WEATHER AT THE DEPARTURE AIRPORT WAS 1000 FEET BROKEN, 2000 FEET OVERCAST. PARK RANGERS SAID THE MOUNTAINTOPS WERE OBSCURED IN THE AFTERNOON ON THE ACCIDENT DATE. THE SPECIALIST AT THE POUGHKEEPSIE FSS STATED THAT AFTER HE COPIED THE PLT'S REQUESTED IFR FLT PLAN, HE ASKED IF THE PLT WANTED A WX BRIEF. THE PLT REPLIED NO AND ACCORDING TO THE SPECIALIST, HUNG UP THE PHONE. ABOUT TWO MINUTES AFTER BEING GIVEN TAXI INSTRUCTIONS AND PUTTING HIS CLEARANCE ON REQUEST, THE PLT WAS ADVISED THAT THERE WAS NO FLT PLAN STORED AND HE WOULD HAVE TO COME IN AND FILE ONE. SHORTLY THEREAFTER, THE PLT REQUESTED A VFR DEPARTURE AND WAS CLEARED FOR TKOF.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record NYC87FA192
- Event ID
- 20001213X31298
- Case number
- NYC87FA192
- 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: 09a3048dd2969579971abfd2a0bf68d8d369b6926613f48468118a223d07fb46; retrieved 2026-09-21T04:05:48.185Z.