# NTSB WPR15LA157: Piper PA 32-300, N4124R, Redlands, CA, May 9, 2015

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Limited investigation · Final report
- Date: May 9, 2015, 10:15 local (17:15 UTC)
- Place: Redlands, CA
- Coordinates: 34.085277, -117.146385 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=34.0853&lon=-117.1464&mi=10
- Phase of flight: [Initial climb](https://openairdocs.org/ntsb-phases/350) (OpenAirDocs' grouping)
- Defining event: [Initial climb: Loss of engine power (partial)](https://openairdocs.org/ntsb-events/342)
- Highest injury: No injuries
- Injuries: 5 uninjured
- Status: Completed, report July 26, 2017
- Report: Approved by Office Director
- NTSB office: Western Pacific Region
- Parties: Federal Aviation Administration
- NTSB case key (mKey): 91142
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR15LA157
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/91142/pdf
- NTSB docket: https://data.ntsb.gov/Docket?ProjectID=91142
- Page: https://openairdocs.org/ntsb/WPR15LA157

## Probable cause

The partial loss of engine power during takeoff due to oil starvation.

## Findings

NTSB's coded findings; those marked are part of the probable cause.

- [Fluids: oil](https://openairdocs.org/ntsb-findings/01071020): Aircraft › Fluids/misc hardware · Fluid level (probable cause); cases with it: [Piper PA-32-300, 2 cases](https://openairdocs.org/ntsb-findings/01071020/cases.md?model=7103212), [All aircraft, 174 cases](https://openairdocs.org/ntsb-findings/01071020/cases.md)
- [Object/animal/substance: sign/marker](https://openairdocs.org/ntsb-findings/03022015): Environmental issues › Physical environment · Contributed to outcome; cases with it: [Piper PA-32-300, 3 cases](https://openairdocs.org/ntsb-findings/03022015/cases.md?model=7103212), [All aircraft, 214 cases](https://openairdocs.org/ntsb-findings/03022015/cases.md)

## Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event best describes what happened.

- [Initial climb: Loss of engine power (partial)](https://openairdocs.org/ntsb-events/342) (defining event); cases with it: [Piper PA-32-300, 10 cases](https://openairdocs.org/ntsb-events/342/sequence.md?model=7103212), [All aircraft, 1,858 cases](https://openairdocs.org/ntsb-events/342/sequence.md)

## Analysis

The commercial pilot reported that, about 30 seconds after takeoff, while the airplane was 250 ft above ground level, the engine began to emit an unusual sound, and he felt a vibration. He chose to land immediately and, due to obstacles ahead, he turned back toward the airport. He completed a steep turn and descended rapidly with the engine producing only partial power. Unable to maintain altitude, the airplane subsequently touched down hard on the runway. The pilot swerved to avoid oncoming traffic, which resulted in the right wing impacting a runway sign. A postaccident examination of the engine revealed that there was a large hole on the top of the crankcase. Two connecting rods were separated from the crankshaft and exhibited mechanical and thermal damage, consistent with oil starvation. Oil streaks were found near the taxiway and run-up area, consistent with the airplane extruding oil before takeoff. When compressed air was directed into the oil cooler, air expelled from a small gap between mating brazed plates, indicating that oil could have extruded from that location.

## Factual narrative

HISTORY OF FLIGHT On May 09, 2015, about 1015 Pacific daylight time, a Piper PA32-300 Cherokee Six, N4124R, made a forced landing following a total loss of engine power at the Redlands Municipal Airport, Redlands, California. Kamasano, LLC. was operating the airplane under the provisions of 14 Code of Federal Regulations (CFR) Part 91. The commercial pilot and four passengers were not injured; the airplane sustained substantial damage. The personal cross-country flight was originating from Redlands with a planned destination of Oceano County Airport, Oceano, California. Visual meteorological conditions prevailed, and a visual flight rules (VFR) flight plan had been filed. In a written statement, the pilot reported that about 30 seconds after takeoff, while the airplane was 250 feet above ground level (agl), the engine began to emit an unusual sound, and he felt a vibration. He noted that the cockpit gauges all displayed normal indications although the noise was disconcerting. The pilot opted to land immediately, and with obstacles and boulders in front of him, he turned back toward the airport. He completed a steep turn, and descended rapidly with the engine only producing partial power. Unable to maintain altitude, the airplane just cleared the airport's perimeter fence, and the airplane touched down hard on runway 08. The propeller contacted the asphalt, and the engine stopped. The pilot further stated that he swerved onto the gravel median to avoid oncoming traffic. The right wing impacted a runway sign resulting in substantial damage. A preliminary engine examination revealed that there was a hole in the engine case near the number four cylinder. Oil streaks were found near the taxiway and run-up area. AIRCRAFT INFORMATION The Piper PA32-300, serial number 32-40442, was manufactured in 1968. The engine's data plate indicated it was a Textron Lycoming IO-540-K1A5 engine, serial number L-5528-48. A review of the airplane maintenance logbooks revealed the last annual inspection occurred on November 3, 2014 at which time the engine had accumulated 4,911.6 hours total time, and about 465 hours since the last major overhaul. There was a notation that the mechanic added AVBLEND to the oil system at this time. The records indicated that during the last maintenance on March 30, 2015, the mechanic installed a new starter and changed the oil. The oil cooler was replaced in March 2014. TEST AND RESEARCH An external examination of the engine revealed that it remained attached to the airframe on all the engine mounts. There was a hole in the crankcase located between cylinders no. four and six extending from the cylinder bay upward to the crankcase backbone. A crack in the crankcase extended from the backbone to an area between the no. three and five cylinder bays. An examination of the no. one, two, five, and six cylinders revealed no evidence of foreign object damage or mechanical malfunction. The intake and exhaust valve faces were intact. The no. oneand two connecting rods were intact and undamaged; the no. three and four connecting rods were separated from the crankshaft with the rod caps separated. The connecting rods exhibited mechanical and thermal damage. The no. five and six connecting rods remained intact, however, they exhibited severe thermal discoloration. Portions of the no. five and six connecting rod bearings were partially extruded from the rod cap. The oil pressure relief valve was removed from the engine crankcase. The internal spring and ball remained intact; there were five washers in the assembly. A review of the Lycoming Overhaul Manual, Section 9, item 9-23, stated in part "…non-adjustable oil pressure relief valve – Although the valve is not adjustable, the oil pressure can be controlled by the addition of STD-425 washers under the cap as required (maximum of three) to increase oil pressure..." The oil cooler, stamped Aero-Classics Heat Transfer Products, part number 8000074, was previously removed and visually appeared intact. When compressed air was applied to one of the ports, air expelled from the side of the oil cooler, where there was a small gap between mating brazed plates. It could not be determined the rate at which the oil would seep from the oil cooler when the system was operating.

## Aircraft

- Registration: [N4124R](https://openairdocs.org/deregistered/N4124R-2018-08-02), registration cancelled 2018-08-02, S/N 32-40442, built 1968 (OpenAirDocs)
- Reported make and model: PIPER PA 32-300 (301)
- Registry model: [Piper PA-32-300](https://openairdocs.org/model/piper-pa-32-300) (registry code 7103212) (OpenAirDocs)
- Registry engine: [Lycoming TI0-540 series](https://openairdocs.org/engine/lycoming-ti0-540-series) (registry code 41533, turbo-prop) (OpenAirDocs)
- Category: Airplane
- Serial number: 32-40442
- Year built: 1968
- Airframe hours: 4967
- Engines: Textron Lycoming IO-540-K1A5 300 horsepower reciprocating
- Damage: Substantial damage
- Flight: Personal, Part 91
- Airworthiness certificate: Standard, Normal
- Last inspection: Annual, November 3, 2014
- Departed: REI, Redlands, CA
- Destination: L52, Oceano, CA
- Flight plan: VFR
- Airport: REI, Redlands Muni, runway 08, 4,504 × 75 ft, asphalt
- Equipment: Handheld GPS, Electronic flight bag or handheld device, Auto-pilot, ADS-B, Onboard weather

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 47; injuries: none; commercial, private; airplane ratings: single-engine land; medical: class 2, with waivers/limitations; last flight review April 4, 2015; seat: front; restraint: lap only; flight hours: 500 total, 55 in this make and model, 425 as pilot in command, 40 in the last 90 days, 15 in the last 30 days, 2 in the last 24 hours

## Weather

- Conditions: Visual (VMC), Day
- Wind: 240° at 5 knots
- Visibility: 7 statute miles
- Lowest ceiling: 4,000 ft overcast
- Temperature: 57 °F, dew point 45 °F
- Altimeter: 30.07 inHg
- Observed at: KSBD, 3 nm away

## FAA reports on this event (1)

The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs).

- [Accident 20150509007239A](https://openairdocs.org/incident/20150509007239A), May 9, 2015: Piper PA-32-300, Redlands, CA, Substantial damage. The aircraft was taxied to the run-up area and system checks were accomplished. Aircraft departed the runway, seconds later the engine vibrated and lost power.…

## Docket (3 files)

The files NTSB released with the investigation on June 7, 2017, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=91142. 6.2 MB in all.

- Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 4.0 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40449913&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF
- Engine Examination Report (item 2, .PDF, 9 photos, 2.0 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40449914&FileExtension=.PDF&FileName=Engine%20Examination%20Report-Master.PDF
- Engine Logbook Excerpts (item 3, .PDF, 221 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40449915&FileExtension=.PDF&FileName=Engine%20Logbook%20Excerpts-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.
