NTSB CAROL · Event
Event LAX98LA214
Aircraft involved
Probable cause & findings
Oil system contamination with an unidentified metal substance that traveled through the oil system and blocked the number 4 main bearing and number 6 connecting rod bearing oil ports, resulting in oil starvation and failure of the engine. The source of the contamination is undetermined.
Factual narrative
On June 27, 1998, at 0605 hours mountain standard time, a Cessna 172, N7188A, experienced a loss of engine power after takeoff from runway 21 and came to rest inverted in a sewage pond near the Flagstaff Pulliman Airport, Flagstaff, Arizona. The aircraft, operated by the pilot/owner under 14 CFR Part 91, sustained substantial damage. The private pilot was not injured. Visual meteorological conditions existed for the local area personal flight and no flight plan was filed. In an interview with a Safety Board investigator, the pilot reported that the aircraft had been refueled with 36 gallons prior to the accident flight. He reported that he had completed the preflight inspection, which included visually checking the fuel level in the aircraft, and drained a fuel sample from both fuel sumps. He did not note any visual abnormalities with the fuel samples. The pilot stated that after he started the aircraft, he waited for ATIS information to be broadcast. He said that since the ATIS begins at 0600, and he was a few minutes early, the engine had ample opportunity to warm-up. The pilot reported that all systems were indicating normal, including the oil pressure and temperature, during his wait. After obtaining ATIS, he contacted ground control and requested a taxi clearance. The pilot performed a run-up, taxied to the departure end of runway 21, and requested takeoff clearance with closed traffic. During the initial climbout at 75 knots, aircraft performance began to deteriorate as the aircraft began losing airspeed and rpm's; although engine oil pressure remained in the green. Shortly after that, the propeller stopped. He switched the fuel selector from "both" to "left"; checked the throttle position, and richened the mixture in an attempt to restart the engine. The pilot reported that by this time his airspeed dropped to 60 knots and he was approximately 200 feet above ground level (agl). The airplane landed in the sewage pond and nosed over. The airplane was inspected on-scene by the general manager of the airport, who was interviewed by a Federal Aviation Administration (FAA) inspector. He stated that the quick release on the oil was found to be open and the engine was low on oil; however, an oil slick was present in the sewage pond. The general manager reported that the fuel system had not been compromised in the accident sequence, and the fuel tanks were full. He further reported that no fuel had spilled out into the sewage pond. The FAA inspector interviewed the pilot who stated that the airplane had been refueled with 36 gallons of 100LL fuel from a 55-gallon drum on the morning of the accident. The FAA took samples from the airplane and the drum. The airplane samples were green in color. The samples from the drum were yellow in color. The FAA inspector stated that the drum was equipped with a contamination filter, but he was unable to determine if the inside of the drum was contaminated. The engine was inspected by Safety Board Investigators at Air Transport, an aircraft recovery company, in Phoenix, Arizona, July 14, 1998. Mechanical continuity was established throughout the engine. Crankshaft rotation produced thumb compression in each cylinder, and, accessory gear and valve train continuity was established. The spark plugs were removed for examination. According to the Champion Aviation Spark Plug Check-A-Plug chart, the spark plugs were fouled with lead. Champion writes "lead fouled hard, cinderlike deposits from poor fuel vaporization, high T.E.L. content in fuel or engine operating too cold." The magnetos were rotated and produced sparks at the spark plug leads in proper firing order. The exhaust system was inspected and no obstructions were noted. The oil filter and suction screen were clean. Review of the maintenance records revealed that an annual inspection, which included an oil change, had been completed on June 6, 1998. Approximately 1 hour of flight time had been completed since the annual inspection. The carburetor was inspected and it was noted that there was sewage water in the bowl, and the air bleed jet and main discharge nozzle air orifices were found to be blocked with a white substance. The cylinders were taken off of the engine and the crankcase was separated. According to the Glacier Vandervell, Inc., "How to prevent bearing failures and determine their causes," the number 4 main bearing exhibited evidence of rubbing on the crankshaft and a portion of that bearing insert was severely worn, heat distressed, and had flowed over the edge of the crankcase bearing journal. White metal flakes were found on the bearing insert. The number 6 connecting rod insert exhibited an unidentified white metal substance located in the oil port and its bearing insert was scored and heat discolored. No further discrepancies were noted with the other five connecting rods. The engine was further inspected at Lynn's Aircraft, Mohave Valley, Arizona, on July 21, 1998. A representative from Teledyne Continental Motors, a party to the investigation, assisted in the examination of the engine under the supervision of a Safety Board investigator. According to the representative, the bearings, pistons, and cylinders exhibited heat discoloration. The crankshaft was placed on a crankshaft balance tester, and found to be out of manufacturer's limits. The oil pump was disassembled. It exhibited a nick on one of the driven gear teeth, which corresponded to circumferential scoring on the oil pump housing. Oil galleries were inspected for blockage, and found to be clear. The engine manufacturer representative stated that an overheating of the journal and bearing and " . . . eventual seizure of the shaft in the bearing," resulted from an unidentified white metal traveling through the main oil gallery and being ejected out the number 4 main bearing and cam bore. Metal fragments were found wedged between the number 4 main journal and the corresponding bearing insert and scored the bearing and blocked the clearance between the journal and bearing. According to the carburetor icing probability chart, moderate icing during cruise power conditions existed at the time of the accident. The pilot stated that the preflight and run-up were conducted with no anomalies noted. After takeoff, the airplane experienced a loss of engine power followed by a loss of altitude and collision with terrain. The airplane came to rest inverted in a sewage pond near the airport. After the power loss, the pilot made an unsuccessful attempt to restart the engine utilizing the emergency checklist. The engine was inspected and mechanical continuity of the engine was established. The crankcase was separated and it was noted that the bearings, pistons, and cylinders exhibited heat discoloration. The number 4 main bearing exhibited evidence of rubbing on the crankshaft and a section of that bearing insert was severely worn, heat distressed, and had flowed over the edge of the crankcase bearing journal. The number 6 connecting rod bearing insert exhibited an unidentified metal substance in the oil port. The remaining crankcase oil journals were found to be clear. The oil pump was disassembled and revealed a nick on one of the driven gear teeth, which corresponded to circumferential scoring on the oil pump housing. The oil filter and suction screen were clean. No further discrepancies were noted with the engine. Review of the maintenance records revealed that an annual inspection, which included an oil change, had been completed approximately 1 hour prior to the accident flight. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_1998_LAX98LA214.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (icing, maintenance). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- NASA NTRS 2019 · Conference Paper
Crash Testing and Simulation of a Cessna 172 Aircraft: Pitch Down Impact Onto Soft Soil
During the summer of 2015, NASA Langley Research Center conducted three full-scale crash tests of Cessna 172 (C-172) aircraft at the NASA Langley Landing and Impact Research (LandIR) Facility.
- NASA NTRS 2019 · Technical Memorandum (TM)
Simulating the Impact Response of Three Full-Scale Crash Tests of Cessna 172 Aircraft
During the summer of 2015, a series of three full-scale crash tests were performed at the Landing and Impact Research Facility located at NASA Langley Research Center of Cessna 172 aircraft.
- Embry-Riddle Scholarly Commons 2023 · Faculty research project
Reconfigurable Guidance and Control Systems for Emerging On-Orbit Servicing, Assembly, and Manufacturing (OSAM) Space Vehicles
Dynamic response to emergent situations is a necessity in the on-orbit servicing, assembly, and manufacturing (OSAM) field, because traditional on-orbit guidance and control (G&C) cannot respond effic…
- Embry-Riddle Scholarly Commons 2019 · Journal article (IJAAA)
Satellite Maintenance: An Opportunity to Minimize the Kessler Effect
Recently, there has been an emphasis on the growing problem of orbital debris. While the advantages of placing satellites into space are numerous, advances in satellite technology combined with the gr…
- Embry-Riddle Scholarly Commons 2015 · Conference paper
The Implementation of Safety Management Systems in Maintenance Operations
Literature for Safety Management Systems (SMS) that apply to flight operations is abundant, but there is a limited supply of SMS-related literature for maintenance operations.
- Embry-Riddle Scholarly Commons 2026 · Journal article (IJAAA)
From Reactive to Predictive: A hybrid Trust-Mediated Adoption Framework for Data-Driven Maintenance in Distributed-Authority Aviation Environments
Modern aviation maintenance operates within increasingly data-intensive technological environments, yet the operational integration of predictive maintenance into routine decision-making remains incon…
Browse the full corpus — academia portal ↗