# NTSB WPR14LA099: Piper PA 24-250, N6570P, San Jose, CA, January 18, 2014 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: January 17, 2014, 16:39 local (Jan 18, 2014, 00:39 UTC) - Place: San Jose, CA - Coordinates: 37.336387, -121.821662 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=37.3364&lon=-121.8217&mi=10 - Phase of flight: [Takeoff](https://openairdocs.org/ntsb-phases/300) (OpenAirDocs' grouping) - Defining events: [Takeoff: Fuel contamination](https://openairdocs.org/ntsb-events/193); [Taxi-from runway: Ground collision](https://openairdocs.org/ntsb-events/200) - Highest injury: No injuries - Injuries: 3 uninjured - Status: Completed, report September 24, 2014 - Report: Approved by Office Director - NTSB office: Western Pacific Region - Parties: Federal Aviation Adminstration - NTSB case key (mKey): 88687 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR14LA099 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/88687/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=88687 - Page: https://openairdocs.org/ntsb/WPR14LA099 ## Probable cause (aircraft 1) The pilot’s failure to sump the fuel tanks, which resulted in water contamination, a partial loss of engine power during takeoff, and collision with a taxiing airplane during the subsequent forced landing. ## Probable cause (aircraft 2) The other pilot’s failure to sump the fuel tanks, which resulted in water contamination, a partial loss of engine power during takeoff, and collision with the taxiing airplane during the subsequent forced landing. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Not determined](https://openairdocs.org/ntsb-findings/05000000): Not determined › Not determined · Unknown/Not determined (probable cause), aircraft 1; cases with it: [Piper PA-24-250, 13 cases](https://openairdocs.org/ntsb-findings/05000000/cases.md?model=7102404), [All aircraft, 2,247 cases](https://openairdocs.org/ntsb-findings/05000000/cases.md) - [Inspection: preflight inspection](https://openairdocs.org/ntsb-findings/02061510): Personnel issues › Task performance · Pilot (probable cause), aircraft 1; cases with it: [Piper PA-24-250, 6 cases](https://openairdocs.org/ntsb-findings/02061510/cases.md?model=7102404), [All aircraft, 551 cases](https://openairdocs.org/ntsb-findings/02061510/cases.md) - [Object/animal/substance: aircraft](https://openairdocs.org/ntsb-findings/03022040): Environmental issues › Physical environment · Contributed to outcome (probable cause), aircraft 1; cases with it: [Piper PA-24-250, 1 case](https://openairdocs.org/ntsb-findings/03022040/cases.md?model=7102404), [All aircraft, 116 cases](https://openairdocs.org/ntsb-findings/03022040/cases.md) - [Action](https://openairdocs.org/ntsb-findings/02041000): Personnel issues › Action/decision · Pilot of other aircraft (probable cause), aircraft 2; cases with it: [Cessna 172N, 1 case](https://openairdocs.org/ntsb-findings/02041000/cases.md?model=2072434), [All aircraft, 111 cases](https://openairdocs.org/ntsb-findings/02041000/cases.md) - [Object/animal/substance: aircraft](https://openairdocs.org/ntsb-findings/03022040): Environmental issues › Physical environment · Contributed to outcome (probable cause), aircraft 2; cases with it: [Cessna 172N, 4 cases](https://openairdocs.org/ntsb-findings/03022040/cases.md?model=2072434), [All aircraft, 116 cases](https://openairdocs.org/ntsb-findings/03022040/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Takeoff: Fuel contamination](https://openairdocs.org/ntsb-events/193) (defining event), aircraft 1; cases with it: [Piper PA-24-250, 3 cases](https://openairdocs.org/ntsb-events/193/sequence.md?model=7102404), [All aircraft, 225 cases](https://openairdocs.org/ntsb-events/193/sequence.md) - [Landing: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470), aircraft 1; cases with it: [Piper PA-24-250, 55 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=7102404), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) - [Taxi-from runway: Ground collision](https://openairdocs.org/ntsb-events/200) (defining event), aircraft 2; cases with it: [Cessna 172N, 16 cases](https://openairdocs.org/ntsb-events/200/sequence.md?model=2072434), [All aircraft, 618 cases](https://openairdocs.org/ntsb-events/200/sequence.md) ## Analysis (aircraft 1) This was the first flight for the Piper airplane in the last 3 months, during which time, it was parked on a ramp outside in the winter. The pilot reported that he performed a preflight inspection but that he did not sump the fuel system. The airplane's main fuel tanks were full with fuel, and the fuel selector valves were set to the main fuel tanks. Shortly after takeoff at an altitude of about 300 to 400 feet above ground level, the engine began to "sputter" with a corresponding partial loss of power. The pilot cycled the throttle control with no change in engine power and then turned back toward the airport. The airplane did not have sufficient altitude to reach a runway, so the pilot performed a gear-up landing onto a taxiway. After landing, the airplane slid across the taxiway surface and struck a taxiing Cessna airplane; both airplanes sustained substantial damage. Postaccident examination of the engine did not reveal any anomalies that would have precluded normal operation, and it started and ran smoothly during a subsequent test run. Given the pilot's failure to sump the fuel system and the fact that the engine did not experience a total loss of engine power, it is likely that the fuel system became contaminated with water while the airplane sat on the ramp for the preceding 3 months. ## Analysis (aircraft 2) The Cessna airplane was taxiing when a Piper airplane collided with it. This was the first flight for the Piper airplane in the last 3 months, during which time, it was parked on a ramp outside in the winter. The pilot reported that he performed a preflight inspection but that he did not sump the fuel system. The airplane's main fuel tanks were full with fuel, and the fuel selector valves were set to the main fuel tanks. Shortly after takeoff at an altitude of about 300 to 400 feet above ground level, the engine began to "sputter" with a corresponding partial loss of power. The pilot cycled the throttle control with no change in engine power and then turned back toward the airport. The airplane did not have sufficient altitude to reach a runway, so the pilot performed a gear-up landing onto a taxiway. After landing, the airplane slid across the taxiway surface and struck the taxiing Cessna airplane; both airplanes sustained substantial damage. Postaccident examination of the engine did not reveal any anomalies that would have precluded normal operation, and it started and ran smoothly during a subsequent test run. Given the pilot's failure to sump the fuel system and the fact that the engine did not experience a total loss of engine power, it is likely that the fuel system became contaminated with water while the airplane sat on the ramp for the preceding 3 months. ## Factual narrative (aircraft 1) On January 17, 2014, at 1639 Pacific standard time, a Piper PA 24-250, N6570P, struck a taxiing Cessna 172N, N737CL, following a loss of engine power during takeoff from Reid-Hillview Airport, San Jose, California. The Piper airplane was registered to 6570P LLC and operated by the pilot as a personal cross-country flight under the provisions of 14 Code of Federal Regulations Part 91. The Cessna airplane was registered to a private individual and operated by Nice Air as an instructional flight under the provisions of 14 Code of Federal Regulations Part 91. Neither the private pilot in the Piper, nor the flight instructor (CFI) and student pilot in the Cessna were injured; both airplanes sustained substantial damage. The Piper had a planned destination of Sonoma Skypark Airport, Sonoma, California; The Cessna had just landed after a local flight. Visual meteorological conditions prevailed, and no flight plans had been filed.The pilot of the Piper stated that this was the first time the airplane had been flown since October 2013, and that it had been sitting on the ramp outside during that time. He performed a preflight inspection, but did not sump the fuel tanks. He confirmed that the main fuel tanks were full with fuel from the year prior, and that the fuel selector valves were set to the main fuel tanks. Following takeoff from runway 31R, he retracted the landing gear, and as the airplane reached an altitude of about 300 to 400 feet above ground level, the engine began to "sputter" with a corresponding partial loss of power. He cycled the throttle control with no change, and initiated a right turn in an effort to return to the airport. As the airport came into view he did not have sufficient altitude to land on a runway, so aimed the airplane for a taxiway. The airplane landed on the taxiway with the landing gear retracted and slid across the surface, striking the tailcone of the taxing Cessna. The CFI in the Cessna stated that they had just landed on runway 31L, and were taxing north on taxiway Z. He observed the Piper airplane takeoff, and could see that it was having difficulty maintaining altitude. It turned right and back towards the airport, and looked like it was going to collide with a hangar to the northeast. The airplane then turned again, and was now flying directly towards him. He pushed the engine throttle control fully forward in an attempt to get out of the way, but the airplane collided with the right side of their tailcone. The Piper was examined by an inspector from the Federal Aviation Administration (FAA) the day following the accident. He reported that both main fuel tanks were full with fuel, and that the auxiliary tip-tanks were empty. Blue colored fuel was present in the belly-mounted fuel strainer, both firewall-mounted electrically driven fuel pumps, and the carburetor bowl. He did not observe any water contamination in the fuel. The NTSB investigator-in-charge performed a follow-up examination of the engine and fuelsystem. The fuel lines were continuous and clear from the main tanks through to the carburetor, and both the screens within the fuel strainer and electrically driven fuel pumps were free of debris. The main fuel tanks and left tip tank fuel cap seals were pliable and free of cracks and fitted firmly in place at their filler necks. The right tip tank cap was loose within the filler neck, and could be easily removed when in the locked position. The engine sustained minimal damage during the accident sequence. All engine controls were continuous from the control arms through to their respective cabin controls, and moved smoothly through full range of travel when operated. The induction air lines were free of obstruction. The oil sump contained about 9 quarts of oil when viewed utilizing the dipstick. The top spark plugs were removed, and examined. Their electrodes remained mechanically undamaged, coated in light grey deposits, and displayed normal-to short service life wear signatures when compared with the Champion Spark Plugs AV-27 Check-A-Plug chart. Visual inspection of the combustion chambers was accomplished through the spark plug bores utilizing a borescope; there was no evidence of foreign object damage and all combustion surfaces exhibited light grey deposits consistent with normal operation. Further examination did not reveal any anomalies with the engine that would have precluded normal operation. Two engine test runs were performed with the main fuel tanks selected, for a total running time of 5 minutes. The engine started within 5 seconds, and operated smoothly from idle through to a maximum speed of 1,800 rpm. Damage to the propeller and engine mount prevented a test at maximum rpm. Both the fuel and oil pressures remained at their nominal values throughout the test, and a magneto check resulted in the appropriate speed drop. ## Factual narrative (aircraft 2) On January 17, 2014, at 1639 Pacific standard time, a Piper PA 24-250, N6570P, struck a taxiing Cessna 172N, N737CL, following a loss of engine power during takeoff from Reid-Hillview Airport, San Jose, California. The Piper airplane was registered to 6570P LLC and operated by the pilot as a personal cross-country flight under the provisions of 14 Code of Federal Regulations Part 91. The Cessna airplane was registered to a private individual and operated by Nice Air as an instructional flight under the provisions of 14 Code of Federal Regulations Part 91. Neither the private pilot in the Piper, nor the flight instructor (CFI) and student pilot in the Cessna were injured; both airplanes sustained substantial damage. The Piper had a planned destination of Sonoma Skypark Airport, Sonoma, California; The Cessna had just landed after a local flight. Visual meteorological conditions prevailed, and no flight plans had been filed.The pilot of the Piper stated that this was the first time the airplane had been flown since October 2013, and that it had been sitting on the ramp outside during that time. He performed a preflight inspection, but did not sump the fuel tanks. He confirmed that the main fuel tanks were full with fuel from the year prior, and that the fuel selector valves were set to the main fuel tanks. Following takeoff from Runway 31R, he retracted the landing gear, and as the airplane reached an altitude of about 300 to 400 feet above ground level, the engine began to "sputter" with a corresponding partial loss of power. He cycled the throttle control with no change, and initiated a right turn in an effort to return to the airport. As the airport came into view he did not have sufficient altitude to land on a runway, so aimed the airplane for a taxiway. The airplane landed on the taxiway with the landing gear retracted and slid across the surface, striking the tailcone of the taxing Cessna. The CFI in the Cessna stated that they had just landed on runway 31L, and were taxing north on taxiway Z. He observed the Piper airplane takeoff, and could see that it was having difficulty maintaining altitude. It turned right and back towards the airport, and looked like it was going to collide with a hangar to the northeast. The airplane then turned again, and was now flying directly towards him. He pushed the engine throttle control fully forward in an attempt to get out of the way, but the airplane collided with the right side of their tailcone. The Piper was examined by an inspector from the Federal Aviation Administration (FAA) the day following the accident. He reported that both main fuel tanks were full with fuel, and that the auxiliary tip-tanks were empty. Blue colored fuel was present in the belly-mounted fuel strainer, both firewall-mounted electrically driven fuel pumps, and the carburetor bowl. He did not observe any water contamination in the fuel. The NTSB investigator-in-charge performed a follow-up examination of the engine and fuelsystem. The fuel lines were continuous and clear from the main tanks through to the carburetor, and both the screens within the fuel strainer and electrically driven fuel pumps were free of debris. The main fuel tanks and left tip tank fuel cap seals were pliable and free of cracks and fitted firmly in place at their filler necks. The right tip tank cap was loose within the filler neck, and could be easily removed when in the locked position. The engine sustained minimal damage during the accident sequence. All engine controls were continuous from the control arms through to their respective cabin controls, and moved smoothly through full range of travel when operated. The induction air lines were free of obstruction. The oil sump contained about 9 quarts of oil when viewed utilizing the dipstick. The top spark plugs were removed, and examined. Their electrodes remained mechanically undamaged, coated in light grey deposits, and displayed normal-to short service life wear signatures when compared with the Champion Spark Plugs AV-27 Check-A-Plug chart. Visual inspection of the combustion chambers was accomplished through the spark plug bores utilizing a borescope; there was no evidence of foreign object damage and all combustion surfaces exhibited light grey deposits consistent with normal operation. Further examination did not reveal any anomalies with the engine that would have precluded normal operation. Two engine test runs were performed with the main fuel tanks selected, for a total running time of 5 minutes. The engine started within 5 seconds, and operated smoothly from idle through to a maximum speed of 1,800 rpm. Damage to the propeller and engine mount prevented a test at maximum rpm. Both the fuel and oil pressures remained at their nominal values throughout the test, and a magneto check resulted in the appropriate speed drop. ## Aircraft 1 - Registration: [N6570P](https://openairdocs.org/deregistered/N6570P-2014-10-28), registration cancelled 2014-10-28, S/N 24-1692, built 1960 (OpenAirDocs) - Reported make and model: PIPER PA 24-250 - Registry model: [Piper PA-24-250](https://openairdocs.org/model/piper-pa-24-250) (registry code 7102404) (OpenAirDocs) - Registry engine: [Lycoming 0-540 series](https://openairdocs.org/engine/lycoming-0-540-series) (registry code 41532, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 24-1692 - Year built: 1960 - Airframe hours: 5600 - Engines: LYCOMING O-540 SERIES 250 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Last inspection: Annual, April 12, 2013, 5 hours before - Departed: RHV, San Jose, CA - Destination: 0Q9, Sonoma, CA - Airport: RHV, Reid-Hillview Of Santa Clara C, runway 31R, 3,100 × 75 ft, asphalt - Equipment: Stall warning system, Angle of attack indicator, Auto-pilot, Electronic multifunction display, Handheld GPS ## Aircraft 2 - Registration: [N737CL](https://openairdocs.org/deregistered/N737CL-2018-03-07), registration cancelled 2018-03-07, S/N 17269313, built 1977 (OpenAirDocs) - Reported make and model: CESSNA 172N - Registry model: [Cessna 172N](https://openairdocs.org/model/cessna-172n) (registry code 2072434) (OpenAirDocs) - Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 17269313 - Year built: 1977 - Airframe hours: 14770 - Engines: LYCOMING O-320 SERIES 160 horsepower reciprocating - Damage: Substantial damage - Flight: Instructional, Part 91 - Operator: Nice Air - Registered owner: Hiroyasu Takai - Airworthiness certificate: Standard, Normal; Standard, Utility - Last inspection: 100 hour, January 3, 2014, 15 hours before - Departed: RHV, San Jose, CA - Destination: RHV, San Jose, CA - Airport: RHV, Reid-Hillview Of Santa Clara C, runway 31L, 3,099 × 75 ft, asphalt - Equipment: Stall warning system ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot, aircraft N6570P; age 53; injuries: none; private; airplane ratings: single-engine land; medical: class 3, without waivers/limitations; last flight review May 10, 2012; seat: left; restraint: 3-point; flight hours: 850 total, 100 in this make and model, 0 in the last 90 days, 0 in the last 30 days, 0 in the last 24 hours - Flight instructor, aircraft N737CL; age 26; injuries: none; commercial, flight instructor; airplane ratings: single-engine land, multi-engine land; instrument ratings: airplane; medical: class 3, without waivers/limitations; last flight review June 9, 2013; seat: right; restraint: 3-point; flight hours: 1,000 total, 350 in this make and model, 900 as pilot in command, 150 in the last 90 days, 60 in the last 30 days, 1 in the last 24 hours - Student pilot, aircraft N737CL; age 29; injuries: none; student; medical: class 1, with waivers/limitations; seat: left; restraint: 3-point; flight hours: 38 total, 38 in this make and model ## Weather - Conditions: Visual (VMC), Day - Wind: calm - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 70 °F, dew point 32 °F - Altimeter: 30.11 inHg - Observed at: KRHV ## FAA reports on this event (2) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20140117003132A](https://openairdocs.org/incident/20140117003132A), Jan 17, 2014: Piper PA-24-250, San Jose, CA, Substantial damage. Aircraft departed VFR. At 300-400 feet, the pilot issued a mayday radio call to Reid-Hillview tower stating that he had lost power. The aircraft made a right… - [Accident 20140117003192A](https://openairdocs.org/incident/20140117003192A), Jan 17, 2014: Cessna 172N, San Jose, CA, Substantial damage. On January 17th, 2014 at 1639 local time an aircraft N6570P PA-24-250 lost engine power after rotating off of runway 31R at reid hillview (rhv). The aircraft… ## Docket (10 files) The files NTSB released with the investigation on April 16, 2014, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=88687. 8.0 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (N6570P) (item 1, .PDF, 1.7 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40409440&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1%20(N6570P)-Redacted.PDF - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (N737CL) (item 2, .PDF, 1.5 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40409441&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1%20(N737CL)-Redacted.PDF - FAA Inspector Record of Conversation (item 3, .PDF, 42 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40411209&FileExtension=.PDF&FileName=FAA%20Inspector%20Record%20of%20Conversation-Master.PDF - Annual Inspection N6570P (item 4, .PDF, 83 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40409449&FileExtension=.PDF&FileName=Annual%20Inspection%20N6570P-Redacted.PDF - Airframe and Engine Examination (item 5, .PDF, 52 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40411210&FileExtension=.PDF&FileName=Airframe%20and%20Engine%20Examination-Master.PDF - Release of Aircraft Wreckage, NTSB Form 6120.15 (item 6, .PDF, 184 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40409840&FileExtension=.PDF&FileName=Release%20of%20Aircraft%20Wreckage,%20NTSB%20Form%206120.15-Redacted.PDF - Photo 1 - Damage to N737CL (item 7, .PDF, 1.1 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40409442&FileExtension=.PDF&FileName=Photo%201%20-%20Damage%20to%20N737CL-Master.PDF - Photo 2 - Damage to N6570P (item 8, .PDF, 1.1 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40409444&FileExtension=.PDF&FileName=Photo%202%20-%20Damage%20to%20N6570P-Master.PDF - Photo 3 - Right Tip Tank Fuel Cap N6570P (item 9, .PDF, 1.1 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40409445&FileExtension=.PDF&FileName=Photo%203%20-%20Right%20Tip%20Tank%20Fuel%20Cap%20N6570P-Master.PDF - Photo 4 - Top Spark Plugs N6570P (item 10, .PDF, 1.1 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40409446&FileExtension=.PDF&FileName=Photo%204%20-%20Top%20Spark%20Plugs%20N6570P-Master.PDF From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.