Overall Trends
Total, fatal, and serious accidents in the selected range.
Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.
Fast key and full-text search with live filters, watches, and precise metadata.
Use quotes for exact phrase matches (for example "fuel selector valve").
Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.
Major cases, deep-report coverage, and investigation media across decades of NTSB history.
Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.
NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.
The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.
The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.
Covington, WA
The pilot reported that he had just dropped off a passenger and was returning to his home base. The pilot stated that after departure and climbing through 5,000 feet, he heard a noise. He continued to climb to altitude, and the noise appeared to have stopped, but he noticed that the oil temperature was increasing. The pilot enrichened the mixture and the oil pressure suddenly dropped. The pilot turned back to his departure airport, and when about eight miles from the airport, he heard a "knocking" noise, then the engine lost power. The pilot could not locate the airport, so he opted to make an off airport landing to a road. During the maneuver for landing, the right wing collided with trees, substantially damaging the outboard about five feet of wing structure. During the post-accident inspection of the engine it was found that engine oil was present on the belly of the fuselage from the nose to the tail. Approximately 20 gallons of fuel was present in the wing fuel tanks. The forward crankshaft seal was only partially seated in the nose of the engine case. The lower numbers 1 and 4 spark plugs were removed and showed signs of lead fouling. The numbers 3 and 4 primer lines were found loose at the cylinder. The numbers 1 and 3 connecting rods failed and the numbers 2 and 4 connecting rod bearing material was melted and squeezed between the rod cap and the crankshaft. The engine case halves displayed several holes. The number 2 cylinder cracked the case around the cylinder base and was attached to the engine by two studs.
The failure of connecting rods during cruise flight resulting in a loss of engine power. Trees were a factor.
On March 7, 2005, about 1900 Pacific standard time, a Cessna 152, N65579, registered to a private individual and flown by the pilot as a 14 CFR Part 91 personal flight, experienced a loss of engine power followed by a forced landing to a road near Covington, Washington. During the emergency descent for landing, the aircraft collided with trees. Visual night meteorological conditions prevailed at the time. The aircraft was substantially damaged and the private pilot, the sole occupant, was not injured. The flight departed from Auburn, Washington, about 30 minutes prior to the accident. During a telephone interview, the pilot reported that he had landed at Auburn to drop off his passenger and was returning to Yakima, Washington. The pilot stated that after departure and climbing through 5,000 feet, he heard a noise. He continued to climb to altitude, and the noise appeared to have stopped, but he noticed that the oil temperature was increasing. The pilot enrichened the mixture and the oil pressure suddenly dropped. The pilot turned back to Auburn, and when about eight miles from the airport, he heard a "knocking" noise, then the engine lost power. The pilot could not locate the airport, so he opted to make an off airport landing to a road. During the maneuver for landing, the right wing collided with trees, substantially damaging the outboard about five feet of wing structure. On March 9, 2005, Inspectors from the Federal Aviation Administration, Seattle, Washington, Flight Standards District Office, inspected and tore down the engine. The inspector reported that engine oil was present on the belly of the fuselage from the nose to the tail. Approximately 20 gallons of fuel was present in the wing fuel tanks. The forward crankshaft seal was only partially seated in the nose of the engine case. The lower numbers 1 and 4 spark plugs were removed and showed signs of lead fowling. The numbers 3 and 4 primer lines were found loose at the cylinder. The numbers 1 and 3 connecting rods failed and the numbers 2 and 4 connecting rod bearing material was melted and squeezed between the rod cap and the crankshaft. The engine case halves displayed several holes. The number 2 cylinder cracked the case around the cylinder base and was attached to the engine by two studs. The pilot was asked to provide the maintenance logbooks for the airframe and engine. To this date, the pilot has not complied nor has he completed the National Transportation Safety Board Pilot Operator Aircraft Accident Report Form 6120.1/2.