- Date
- July 25, 2004, 11:50 local (18:50 UTC)
- Place
- Ontario, CA
- Injuries
- 2 uninjured
- Damage
- Substantial damage
- Phase of flight
- Enroute
- Aircraft
- N5GCPiper PA-32RT-300
- Weather
- Visual (VMC) · Day
- Status
- Completed · report June 8, 2005
- Report
- Approved by Office Director
- Parties
- Federal Aviation Administration
- FAA report
- 20040725024229A
- Case key
- 59757
From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.
On this page
Probable cause
a catastrophic engine failure due to the overheating of a connecting rod bearing, and the resulting failure of the rod, for undetermined reasons.
Sequence of events
NTSB’s coding before 2008: each occurrence and phase of flight, and the causes and factors under it. The codes are defined in NTSB’s coding manual.
Analysis
The airplane collided with a berm during a forced landing in an open field about 3/4-mile from an airport following a loss of engine power. The pilot reported that initially during the flight the engine had operated normally. However, after flying for several minutes, the engine started running rough, and oil appeared on the front windshield. Thereafter, all engine power was lost. During the subsequent examination of the engine about 10 quarts of oil were found in the sump, and a hole was found in the engine's case next to the oil dipstick port. The teardown examination of the engine revealed that, for undetermined reasons, the connecting rod bearing on rod number 5 had overheated to failure, and the connecting rod broke. The engine had been operated 40 hours since its last inspection and 806 hours since last receiving a major overhaul. The airplane's total time was about 6,325 hours.
Factual narrative
On July 25, 2004, about 1150 Pacific daylight time, a Piper PA-32RT-300, N5GC, operated by the pilot-owner, experienced a total loss of engine power while cruising. The pilot made a forced landing in a field about 3/4-mile east of the Ontario International Airport, Ontario, California. Following touchdown, the airplane impacted a berm and was substantially damaged. Neither the airline transport pilot nor the passenger was injured. Visual meteorological conditions prevailed at the time of the personal flight, and no flight plan had been filed. The local flight was performed under the provisions of 14 CFR Part 91, and it originated from Upland, California, about 1130.
The pilot reported to the National Transportation Safety Board investigator that initially during his flight the engine seemed to be operating normally. After flying for several minutes the engine started running rough, and oil appeared on the front windshield. Thereafter, all engine power was lost. The airplane had insufficient altitude to glide to the nearest airport, and a forced landing ensued in a field.
Under the Safety Board investigator's direction, the airplane was recovered from the accident site and was examined under the supervision of a Federal Aviation Administration (FAA) aviation safety inspector. The external engine examination revealed the presence of a hole in the engine's case, next to the oil dipstick port.
The engine was removed from the airplane and disassembled by personnel at a FAA certificated repair station, while under FAA supervision. In pertinent part, the repair station personnel reported its examination observations and opined the following sequence of events:
1. The engine was noted to have approximately 10 quarts of oil in the sump;
2. The oil pan and finger screen were full of metal;
2. Connecting rod bearing, part number SL74309, on connecting rod number 5 appeared to have overheated to failure;
3. This overheat condition resulted in breakage of connecting rod number 5;
4. Debris from this breakage resulted in connecting rod number 6 punching a hole in the case.
According to the pilot-owner, he had recently purchased the airplane, which had a total time of 6,325.38 hours. The engine, serial number L17809-48A, had 806 hours since last receiving a major overhaul. The airplane had been operated about 40 hours since its last annual inspection in November 2003.
Aircraft
- Registration
- N5GC
- Reported as
- Piper PA-32RT-300
- Category
- Airplane
- Serial number
- 32R-7985030
- Airframe hours
- 6,325
- Engine
- Lycoming IO-540-K1G5D, 300 horsepower, reciprocating
- Damage
- Substantial damage
- Flight
- Personal · Part 91
- Airworthiness certificate
- Standard, Normal
- Last inspection
- Annual · November 19, 2003 · 40 hours before
- Departed
- CCB · Upland, CA
- Destination
- CCB · Upland, CA
- Airport
- ONT · Ontario, runway 26R, 12,198 × 150 ft, concrete
Flight crew
As NTSB recorded them. NTSB leaves out names.
- Role
- Pilot
- Age
- 36
- Injuries
- None
- Certificates
- Airline transport, Flight engineer
- Airplane ratings
- Single-engine land, Multi-engine land
- Instrument ratings
- Airplane
- Medical
- Class 1, Valid Medical--w/ waivers/lim
- Last flight review
- February 1, 2004
- Seat
- Left
- Flight hours
- 8,100 total · 600 in this make and model · 2,535 as pilot in command · 150 in the last 90 days · 50 in the last 30 days · 0 in the last 24 hours
Weather
- Conditions
- Visual (VMC) · Day
- Wind
- 260° at 10 knots
- Visibility
- 9 statute miles
- Lowest ceiling
- None
- Temperature
- 91 °F, dew point 59 °F
- Altimeter
- 29.95 inHg
- Observed at
- ONT, 1 nm away
Docket · 3
The files NTSB released with the investigation on March 31, 2005, on NTSB’s docket system: statements, records, photos and specialists’ reports. 558 KB in all.
FAA reports on this event · 1
The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.