Plane crash map Find crash sites, wreckage and more

N2913F accident description

Oregon map... Oregon list
Crash location 44.915556°N, 122.897777°W
Nearest city Salem, OR
44.942898°N, 123.035096°W
7.0 miles away
Tail number N2913F
Accident date 15 May 2003
Aircraft type Cessna 182J
Additional details: None
Advertisement

NTSB Factual Report

On May 15, 2003, approximately 1600 Pacific daylight time, a Cessna 182J, N2913F, collided with the terrain during the landing roll when the pilot attempted a forced landing in an open field about four miles east of Salem, Oregon. The commercial pilot, who was the sole occupant, was not injured, but the aircraft which is owned by a relative of the pilot, but operated primarily by the pilot, sustained substantial damage. The 14 CFR Part 91 personal pleasure flight, which departed Hillsboro, Oregon, about 40 minutes earlier, was being operated in visual meteorological conditions. No flight plan had been filed. There was no report of an ELT activation.

According to the pilot, while cruising at 11,500 feet in order to get over some clouds, the engine slowly started losing power. Because it appeared to him that it might be carburetor icing, the pilot applied carburetor heat, but the engine continued to lose more power. Eventually the engine lost enough power that the pilot was unable to hold altitude, and he therefore found it necessary to descend and attempt a forced landing in an open field. Prior to reaching the field, the engine lost all power, but the pilot was able to reach the field he was aiming for. Although the touchdown was uneventful, during the landing roll the aircraft encountered some rough terrain, resulting in substantial damage.

According to the FAA inspector who responded to the scene, the engine crankcase had fractured and although the oil filler cap was in place, all but a very small amount of engine oil was missing. During a post-accident engine inspection it was observed that there was a large hole in the top of the crankcase between cylinders #1 & #2. Connecting rods #1 & #3 were disassociated from their rod journals. Connecting rods #4, 5 and 6 were dry and brown in color. The crankshaft cheeks adjacent to these rods were discolored, as were the rod journals for #1 & #3 connecting rods. The four connecting rod bolts for rods #1 & #3 were all a dark blue color and separated at mid bolt with the points of separation severely necked down. All of the recovered parts of the connecting rods #1 & #3 were a dark blue color. Both pistons #1 & #2 had been broken up during the failure event. The tops of piston's #1, 3, 4, 5 and 6 all exhibited normal operating signatures. The top of piston #2 had been fragmented and was in the oil sump. The chrome cylinder walls were blue in color and heavily scored. All valves were found to be intact. The oil sump was removed and was found to contain most of the fragment engine parts and very little oil. The exterior of the engine was checked for oil leaks as well as the oil filter, oil filter adapter, propeller governor, push rod seals, oil pressure line, dipstick tube, oil sump quick drain, oil pump, tachometer drive, and oil filler port/cap, and no evidence of a leak was noted. According to the pilot, he added one quart of oil just prior to the flight, and this brought the oil level to a point about half way between the low-oil mark and the fully filled line.

Although the engine displayed the aforementioned signs of catastrophic internal failure, the event initiating that failure sequence could not be determined.

NTSB Probable Cause

Loss of power in cruise flight due to a catastrophic engine failure for undetermined reasons.

Advertisement
(c) 2009-2018 Lee C. Baker / Crosswind Software, LLC. For informational purposes only.