Plane crash map Locate crash sites, wreckage and more

N1270P accident description

California map... California list
Crash location 37.605556°N, 122.035277°W
Nearest city Hayward, CA
37.668821°N, 122.080796°W
5.0 miles away
Tail number N1270P
Accident date 19 Jun 2016
Aircraft type Piper Pa 23-150
Additional details: None

NTSB Factual Report

***This report was modified on 12/11/17. Please see the docket for this accident to view the original report.***

HISTORY OF FLIGHT

On June 19, 2016, about 1149 Pacific daylight time, a Piper PA-23-150, N1270P, was destroyed when it collided with a building following a loss of engine power during an approach to land at Hayward Executive Airport (HWD), Hayward, California. The airline transport pilot was fatally injured. The airplane was registered to and operated by the pilot under the provisions of 14 Code of Federal Regulations (CFR) Part 91. Visual meteorological conditions prevailed, and no flight plan was filed for the local personal flight that departed HWD about 1035.

Federal Aviation Administration (FAA) air traffic control (ATC) audio captured multiple communications between ATC and the pilot who continuously requested taxi tests on runway 28L over a time span of approximately 2 hours. He did not report any anomalies to the air traffic controller.

FAA radar data showed that the airplane departed HWD to the south, turned east, crossed over a mountain range, and turned north. The airplane maneuvered over the north end of San Francisco Bay, and then flew a reverse course back toward HWD. At 1145:06, when the airplane was about 10.5 nautical miles (nm) southeast of the airport, the pilot contacted the HWD air traffic control tower for a landing clearance. The local controller instructed the pilot to enter a straight in approach for runway 28L and to advise when he was 3 miles from the airport.

At 1147:30, when the airplane was about 6.5 nm from the airport and approaching several grass fields to the right of its flight path, the pilot notified the controller that he was experiencing "difficulty" with his left engine and could not maintain altitude. At the request of the controller, the pilot reported that he was the only person onboard and had about 60 gallons of fuel remaining. Seconds later, the pilot informed the controller that he would "not be able to make it to the airport." The controller then asked the pilot if he saw any landing sites around him. At 1148:51, the pilot informed the controller that he could see a field near a set of Bay Area Rapid Transit (BART) commuter train tracks and would attempt to land there. According to radar and map data, the airplane passed the grass fields to the right of its flight path at about 1148:33, and, seconds later, it turned about 45° left. As the airplane began its left turn near the end of the flight, the airplane's groundspeed was recorded at 59 knots (about 68 mph) at an altitude of 375 ft mean sea level (msl). The airplane never exceeded this groundspeed during its subsequent descent to impact. Additionally, about 20 seconds before the last radar return, the airplane's groundspeed reached a minimum of 52 knots (60 mph) at an altitude of about 225 ft msl (about 173 ft above ground level).

Three witnesses were interviewed: two who saw the airplane flying inbound to land (witnesses 1 and 2) and one who saw the airplane moments before it impacted the building in the rail yard (witness 3). As shown in Figure 1, Witness 1 was located near the airplane's inbound leg, about 9 nm southeast of HWD. Witness 1 reported that she heard an abnormal sound from inside her home. She went outside and saw an airplane approaching her house from a group of hills located to the east. The airplane appeared to be losing altitude, and the engine made a "sputtering sound," which she also described as "cutting out." The sound repeated when the airplane flew above her property and again seconds later after it passed her home.

Witness 2 was located about 10 miles southeast of HWD near the airplane's outbound leg and about 1 mile south of the airplane's inbound leg. Witness 2 stated that he was working in his yard all morning and initially saw a red and white airplane on a southeast heading about 1,750 ft. He never saw any smoke but heard a sound that resembled an engine "backfiring." The airplane subsequently made a left turn, proceeded eastbound, and disappeared behind a group of hills. About 30 minutes later, he saw the same airplane northeast of his house flying toward the airport. The witness reported hearing sounds like an engine "popping" and "backfiring." He added that he did not see any smoke, foreign object debris, or fluids coming from the airplane, and he further said that the engine "backfiring" sounds were much louder than those he heard during the airplane's outbound leg.

Witness 3 was located about 1/2 mile from the accident site. He saw the airplane flying abnormally low over a group of houses. He reported that the airplane was in a wings level descent for a few seconds before it suddenly entered a steep left turn, with the right wing about 70 degrees to the horizon. The airplane then disappeared behind a residential area. About 10 seconds later he heard a loud impact sound, and, shortly thereafter, plumes of smoke came from the airplane's direction.

Figure 1 – Witness Locations

BART surveillance video showed the airplane in a slight left-wing-low attitude, which gradually increased as the airplane flew across a set of railroad tracks. The forward fuselage and right wing impacted the east wall of a small building. A mist covered the right wing, empennage, and tail as they fell to the ground, and a postcrash fire ensued.

PERSONNEL INFORMATION

The pilot held an airline transport certificate with ratings for airplane multi-engine land and a flight instructor certificate for airplane single-engine land. He held a first-class medical certificate issued on January 13, 2016, at which time he reported 2,161 total flight hours. The medical certificate included one restriction: "must have available glasses for near vision."

According to the pilot's logbook, he had accumulated about 19 hours of total flight time in the accident airplane of which 1.4 hours were in the 90 days preceding the accident. His first flight in the accident airplane took place in August 2015 when he ferried the airplane to California. After the ferry flight, the pilot accrued a total of about 27 additional flight hours in other airplanes and performing flight instruction.

The flight instructor who administered the pilot's most recent flight review reported that the flight review was conducted in March 2015 in the pilot's BE60 airplane and included two simulated left engine failures. The first simulated engine failure took place during an instrument landing system approach, and the pilot completed the engine out procedure and continued the approach successfully. The instructor noted that, during the simulated engine failure, the pilot's yaw control was "good" and that the airplane's descent was "smooth and right on." A subsequent simulated engine failure took place at 5,000 ft when the flight instructor reduced the left engine manifold pressure to 13 inches. He then asked the pilot to complete a 45° turn and hold his altitude, but the airplane was unable to maintain altitude due to the combination of a low power setting and a higher-than-standard rate turn. During both simulated engine failures, the pilot successfully kept the airspeed above the airplane's minimum controllable airspeed (Vmc).

AIRCRAFT INFORMATION

According to FAA records, the airplane was manufactured in 1955 and registered to the pilot on September 2, 2015. The airplane was powered by two Lycoming O-320-A, normally-aspirated, direct-drive, air-cooled, 150-horsepower engines. The pilot's family furnished the original aircraft logbooks, which included service information from May 1986 to July 2015. A review of the logbooks revealed that the airplane's most recent 100-hour inspection was completed on July 15, 2015, at which time the left engine tachometer read 4,051 flight hours, and the right engine tachometer read 4,059 flight hours.

According to the logbooks, at the time of the most recent 100-hour inspection, the left and right engines had accumulated about 1,955 hours and 1,957 hours, respectively, since their most recent major overhauls. Records of the left and right engine overhauls could not be located in the available aircraft records, and the dates of the overhauls could not be determined.

The airplane total time at the time of the accident was estimated using the right engine tachometer time as the airplane's recording hour meter was not recovered. Based on the pilot's approximate 19 hours of accumulated time in the airplane make and model, the airplane's total time at the time of the accident was estimated to be about 4,077 hours.

Records furnished by a fixed base operator at HWD indicated that the pilot had purchased fuel from their self-service facility 11 times in the previous 10 months. The records showed that the pilot did not purchase fuel at HWD on the day of the accident; they showed that he last purchased fuel for the airplane at HWD in September 2015.

The pilot's logbook showed that he flew the airplane to Nut Tree Airport (VCB), Vacaville, California on May 1, 2016. VCB refueling records indicated that the pilot purchased about 15 gallons of 100LL gasoline that day. Before that, the pilot had purchased about 28 gallons of 100LL gasoline at VCB on September 27, 2015.

A procedure to feather the propeller of an inoperative engine was included in the airplane's aeronautical flight manual (AFM). According to the AFM, the procedure included the following steps:

1. Throttle "CLOSED".

2. Prop Control "FEATHERED". PROP CANNOT BE FEATHERED UNDER 700 RPM.

3. Mixture control "IDLE CUT-OFF".

4. Ignition switches "OFF".

5. Electric fuel pump (if in use) "OFF".

6. Main valve "OFF".

The manufacturer's published Vmc for the airplane is 85 mph.

METEOROLOGICAL INFORMATION

The 1152 recorded weather observation at HWD included wind 280° true at 11 knots, visibility 10 statute miles, clear skies, temperature 27°C, dew point 8°C, and an altimeter setting of 30.06 inches of mercury.

According to an employee of a fixed base operator at HWD, the airport received significant levels of rain during the winter of 2016 that resulted in an overflow of the airport's drainage ditch. However, the investigation was unable to determine whether the airplane was parked outside during the winter of 2016.

WRECKAGE AND IMPACT INFORMATION

Initial examination of the accident site by the National Transportation Safety Board investigator-in-charge revealed that the airplane came to rest at the base of a fiberglass railroad car wash building, about 5 nm southeast of HWD. All major structural components of the airplane were accounted for at the accident site, which was contained within an area about 35 ft long and 25 ft wide. The fuselage came to rest inverted on a heading of 095° magnetic and was destroyed by fire. With the exception of some thermal damage, the empennage was intact and remained connected to the fuselage by the airplane's rudder control cables. The right wing was destroyed by fire, and its corresponding engine was inverted and covered in soot. The left wing was co-located with the main wreckage in a near vertical position, at rest against the southeastern end of the building, and exhibited an odor of fuel near the left wingtip. Both sets of propeller blades remained attached to their respective hubs; the left engine propeller blades were in the feathered position and did not display any damage. The right engine propeller blades were in a low pitch position and displayed nicks, gouges, and tip curling.

Left aileron control continuity was confirmed from the left aileron bell crank to the wing root where the cables had been cut by recovery personnel. The rubber seal to the inboard left tank fuel cap was rusted, and the cap did not form a seal inside the fuel tank ring when installed. The fuel cap rubber seal to the left outboard tank displayed some corrosion and did not form a seal when installed in the fuel tank ring. The left fuel selector valve displayed 3/4 inches of space between the lever and the valve. According to the manufacturer, this position was consistent with an auxiliary tank setting. A trace amount of fuel was drained from the left engine gascolator into a plastic container that had been cleaned and dried. The fuel odor and appearance resembled 100LL aviation grade gasoline; however, a SAR-GEL fuel purity test indicated that the fuel was contaminated with water. The left electric fuel boost pump was not recovered.

The right wing aileron bell crank was damaged by fire but remained intact and attached to the primary aileron and balance cables. The right aileron cable was continuous from the bell crank to the chain, which had fracture signatures consistent with overload separation.

The right electric fuel boost pump was disassembled, and the gasket and internal components displayed carbon coloring consistent with exposure to fire. The pump was void of fuel, and the fuel screen was found free of debris.

One arm from the control T-bar assembly separated at the T-section, and the assembly was damaged by fire; however, the remaining three sprockets were intact. A portion of elevator control tube remained attached to the tube stem.

Continuity of the rudder assembly was traced from the rudder torque tube through a control cable located on the right side of the airplane to the rudder flight control surface. A rudder control cable on the opposing side was traced from the rudder to the cockpit; however, the cable had separated from the torque tube arm, which had separated from the torque tube.

The flap actuator measured about 20 inches, which was consistent with partial deployment of the flaps. According to the airplane manufacturer, an actuator measurement of 18.35 inches corresponds to a full flap extended position and 25.50 inches corresponds to a full flap retracted position. While the flap actuator rod displayed significant fire damage on the fore and aft ends, the intermediate section was shiny in appearance with only some blue discoloration.

Elevator continuity was traced from the elevators to a fractured control tube near the aft fuselage.

The rudder trim jackscrew displayed about 1 inch of exposed threads. According to the manufacturer, this measurement was consistent with a neutral trim position.

The elevator trim displayed about 17 threads, which correlated to a near full nose-up trim position. However, the elevator trim cables were loosely fixed to the trim drum, which indicated that the trim jackscrew may have moved during the accident sequence.

Left Engine

Mechanical continuity of the left engine was confirmed from the propeller throughout the valve train to the accessory section when the propeller was rotated by hand. Thumb compression and suction were established on each of the engine's four cylinders, and the valve train moved in the proper firing order. An examination of each cylinder's internal combustion chamber revealed no evidence of foreign object ingestion or detonation.

A magneto synchronizer confirmed the magneto breaker points opened at 25° below top dead center. Both the left and right magnetos were timed within 1° of each other. The magnetos were then removed from their respective mounting pads to facilitate a magneto examination. Hand rotation of each drive produced spark at each of the four plug leads.

The top and bottom spark plugs were secured in their respective positions and undamaged. The plugs were oil-soaked, but displayed coloration consistent with normal operation as shown on the Champion Spark Plug "Check-A-Plug" chart AV-27. The static oil soaking of the spark plugs was attributed to the engine positioning at the mishap site and post recovery.

The carburetor was attached to the engine accessory case at the mounting flange, and the throttle/mixture controls were secured to their respective controls arms at the carburetor. The carburetor fuel screen was free of debris, and the carburetor floats were intact. Trace amounts of residual fuel were discovered in the carburetor fuel bowl and in the accelerator pump. A subsequent SAR-GEL wa

NTSB Probable Cause

The failure of the left engine due to water contamination and the pilot's subsequent failure to maintain single-engine minimum control airspeed, which resulted in an uncontrolled descent. Contributing to the accident was the pilot's lack of total and recent flight experience in the accident airplane make and model, which reduced his capacity to manage an inflight loss of power.

© 2009-2020 Lee C. Baker / Crosswind Software, LLC. For informational purposes only.