NYC07FA055 · Piper PA-60-601P
Piper PA-60-601P · Accident: total loss of engine power (non-mechanical) during initial climb
From Chautauqua County-Jamestown Airport (JHW) to Buffalo Niagara International Airport (BUF)
Event
- NTSB case
- NYC07FA055
- 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
- Unknown
- 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
Piper PA-60-601P
- 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
- N720Z
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Chautauqua County-Jamestown Airport (JHW), Jamestown, NYTo 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
- Initial climb
- 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
- Total loss of engine power (non-mechanical)
- 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
- Fuel starvation
- 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 › Fuel tank selector position, incorrect
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
During the initial climb, a "throbbing or surging" sound was heard as the airplane departed in gusting wind conditions with a 600-foot ceiling and 1/2 mile visibility in snow. Moments later the airplane came "straight down" and impacted the ground. During examination of the wreckage, it was discovered that that the fuel selector switch for the right engine had been in the "X-FEED" position during the accident. Examination of documents discovered in the wreckage revealed, three documents pertaining to operation of an Aerostar. These documents consisted of two airplane flight manuals (AFMs) from two different manufacturers, and a checklist. Examination of the first of the AFMs revealed, that it had the name of both the pilot and the operator on the cover of the document. Further examination revealed that it had been published 4 years prior to the manufacture of the accident airplane, and contained information for a Ted Smith Aerostar Model 601P, which the operator had previously owned. This document contained no warnings regarding the use of the crossfeed system during takeoff. Examination of the second of the two AFMs found in the wreckage revealed that it was the Federal Aviation Administration (FAA) approved AFM for the accident airplane. Unlike the first AFM, the second AFM advised that the fuel selector "X-FEED" position should be used in "level coordinated flight only." It also advised that each engine fuel selector "must be in the ON position for takeoff, climb, descent, approach, and landing." It also warned that, if the airplane was not in a level coordinated flight attitude, "engine power interruptions may occur on one or both engines" when "X-FEED" is selected "due to unporting of the respective engine's fuel supply intake port." Review of the checklist contained in the FAA approved AFM for the Piper Aircraft Model 601P under "STARTING ENGINES," required a check of the crossfeed system prior to engine start by selecting each fuel selector to "ON," then selecting "X-FEED," and after verifying valve actuation and annunciator light illumination, returning the fuel selector to "ON." Additionally, under "BEFORE TAKEOFF" It also required that the fuel selectors be checked in the "ON" position, and that the "X-FEED" annunciator light was out, prior to takeoff. Examination of the pilot's checklist revealed that, it consisted of multiple pages inserted into plastic protective sleeves and included both typed, and hand written information. A review of the section titled "BEFORE TAKEOFF" revealed that the checklist item "Fuel Selectors - ON Position," which was listed in the AFM, had been omitted.
Probable cause
The pilot's incorrect selection of the right engine fuel selector position, which resulted in fuel starvation of the right engine, a loss of the right engine's power, and a loss of control during initial climb. Contributing to the accident were the pilot's inadequate preflight planning and preparation, and his improper use of the manufacturer's published normal operating procedures.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC07FA055
- Event ID
- 20070118X00066
- Case number
- NYC07FA055
- 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, coordinates. 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: 7811f0f40144f9be18509dd7c070c36c88e90dff928d23ad61672dfa2b14356e; retrieved 2026-09-20T16:54:56.085Z.