NYC95FA042 · Piper PA-60-600
Piper PA-60-600 · Accident: loss of control in flight en route
From Boston Logan International Airport (BOS) to Buffalo Niagara International Airport (BUF)
Event
- NTSB case
- NYC95FA042
- 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
Piper PA-60-600
- Aircraft type
- Piper PA-60
- 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
- N6069T
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Boston Logan International Airport (BOS), Boston, MATo Buffalo Niagara International Airport (BUF), Buffalo, 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
- Loss of control in flight
- 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 › Aircraft control, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE AIRPLANE WAS ON A POSITIONING FLIGHT AT NIGHT, CRUISING AT 6000 FT. ALSO, THE PILOT WAS OPERATING ON AN IFR FLIGHT PLAN AND WAS ON HIS 6TH FLIGHT AFTER REPORTING FOR DUTY AT 1530 EST. DURING A FREQUENCY CHANGE AND RADIO CHECK AT 0207 EST, THE PILOT'S RESPONSE WAS NORMAL. RADAR DATA REVEALED THAT ABOUT 16 MINUTES LATER, THE AIRPLANE ENTERED A RIGHT TURN, THEN DISAPPEARED FROM RADAR AT ABOUT 0222 EST AFTER ABOUT 255 DEGREES OF TURN. IT IMPACTED THE GROUND IN A STEEP NOSE DOWN DESCENT; DEBRIS FROM THE AIRPLANE WAS FOUND DOWN TO 6 FT BELOW THE SURFACE. DURING THE FINAL 15 MINUTES OF FLIGHT, THERE WERE NO RADIO TRANSMISSIONS ON THE ASSIGNED FREQUENCY. NO PREIMPACT MECHANICAL FAILURE OR MALFUNCTION WAS FOUND. THE PROPELLER BLADES HAD S-CURVES OR WERE BENT FORWARD; THEY ALSO HAD LEADING EDGE IMPACT DAMAGE AND ROTATIONAL SCORING. THE PILOT HAD FLOWN IN EXCESS OF 120 HOURS (110 HRS AT NIGHT) IN THE PRECEDING 30 DAYS. THERE WAS EVIDENCE THAT HE MAY HAVE LACKED CREW REST DURING THE DAY(S) BEFORE THE ACCIDENT.
Probable cause
FAILURE OF THE PILOT TO MAINTAIN CONTROL OF THE AIRCRAFT, POSSIBLY FROM FALLING ASLEEP.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC95FA042
- Event ID
- 20001206X02784
- Case number
- NYC95FA042
- 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: 5c7a9d18ee68164e3ba0ee6be8f237f4e663caf743d0f86338dc54cc83aa2f83; retrieved 2026-09-20T23:55:01.230Z.