NYC91FA001 · Cessna 172P
Van Bortel Aircraft Cessna 172P · Accident: in flight collision with terrain/water en route
From Syracuse Hancock International Airport (SYR) to Bangor International Airport (BGR)
Event
- NTSB case
- NYC91FA001
- 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
- 3 · 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 172P
- Aircraft type
- Cessna 172
- 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
- N98438
- Operator
- Van Bortel Aircraft
- Onboard fatalities
- Unknown
- Route
- From Syracuse Hancock International Airport (SYR), Syracuse, NYTo Bangor International Airport (BGR), Bangor, ME
- 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 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 › Planning/decision, improper
- Pilot in command › Proper altitude, not maintained
Approximate · Estimated position: the centre of Gorham, NH, the place the record names. Not the accident site.
NTSB narrative
THE AIRPLANE WAS BEING FERRIED TO EUROPE & WAS ON A GREAT CIRCLE ROUTE AT NIGHT BETWEEN SYRACUSE, NY, & BANGOR, ME. THE PLANE WAS IN CRUISE FLIGHT AT 5500 FT MSL, WHEN IT STRUCK MT WASHINGTON. IT WAS EQUIPPED WITH AN AUTO PILOT & LORAN C. ACCORDING TO THE LORAN MFG, THE AIRPLANE WAS WITHIN 1/2 MILE OF COURSE & ON HEADING AT THE TIME OF THE ACCIDENT. THE TOP OF MT WASHINGTON WAS OBSCURED; HOWEVER, A WITNESS 7 MILES AWAY SAW THE LIGHTS OF THE AIRPLANE & A FIREBALL FROM THE IMPACT. THE PILOT HAD BEEN AWAKE FOR 22 HOURS, WHEN THE ACCIDENT OCCURRED.
Probable cause
IMPROPER PLANNING/DECISION BY THE PILOT, AND HIS FAILURE TO MAINTAIN PROPER ALTITUDE WHILE FLYING OVER MOUNTAINOUS TERRAIN. FACTORS RELATED TO THE ACCIDENT WERE: DARKNESS, MOUNTAINOUS TERRAIN, AND PILOT FATIGUE.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC91FA001
- Event ID
- 20001212X24519
- Case number
- NYC91FA001
- 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: d40004dae5627ff667b7f302a4030daaf501142e8665a3e3a9599d26eb85d3b1; retrieved 2026-09-21T02:08:00.031Z.