NYC95LA048 · Aero Commander 560F
Aero Commander 560F · Accident: overrun during takeoff
From 4O18 to Chautauqua County-Jamestown Airport (JHW)
Event
- NTSB case
- NYC95LA048
- 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
- 0 · 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
Aero Commander 560F
- Aircraft type
- Aero Commander 560
- 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
- N560WM
- Operator
- Robert J. Brocker, JR · private individual
- Onboard fatalities
- Unknown
- Route
- From 4O18To Chautauqua County-Jamestown Airport (JHW), Jamestown, 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
- Takeoff · rejected takeoff
- 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
- Overrun
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Pilot in command › In-flight planning/decision, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT ABORTED THE TAKEOFF ON A 3100 FT LONG RUNWAY, WHICH WAS COVERED BY SNOW AND ICE, DUE TO A PERCEPTION THAT THE ENGINES WERE NOT DEVELOPING FULL POWER. HE WAS UNABLE TO STOP ON THE RUNWAY, DEPARTED THE END, WENT THROUGH A FENCE, AND STRUCK TREES. A FULL POWER RUN WAS ACCOMPLISHED BY THE FAA AFTER THE ACCIDENT. NO ANOMALIES WERE FOUND WITH THE ENGINES. THE PILOT REPORTED HE LOWERED THE FLAPS TO FULL DURING THE ABORTED TAKEOFF. NO SPECIFIC PROCEDURES ARE LISTED IN THE FAA APPROVED FLIGHT MANUAL FOR ABORTED TAKEOFFS; HOWEVER, FOR LANDINGS, THE FLIGHT MANUAL CALLS FOR THE FLAPS TO BE RAISED AFTER TOUCHDOWN.
Probable cause
The pilot's decision to abort the takeoff on a snow and ice covered runway, and once made, the pilot's decision to lower the flaps.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC95LA048
- Event ID
- 20001207X02909
- Case number
- NYC95LA048
- 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: e9603a2f34642b1b0904b801d56e20d8d1d5829d082fcc4d06718a08bbf9de5f; retrieved 2026-09-23T00:20:23.170Z.