LAX99LA173
1999-05-07 · CHANDLER, Arizona, United States · Minor · 1 aircraft · Status: Completed
Airport P19
Aircraft involved
Probable cause & findings
The pilot's improper use of the carburetor heat and throttle control (rapid movement), which induced an overly rich condition and a loss of power.
Factual narrative
On May 7, 1999, at 2219 hours mountain standard time, a Cessna 152, N48845, lost engine power and collided with obstacles and terrain approximately 1/4 mile from the Stellar Airpark in Chandler, Arizona. The aircraft, operated by South Bay Aviation, Torrance, California, and rented by the pilot for the personal cross-country flight, sustained substantial damage. The private pilot and passenger suffered minor injuries. The flight, conducted under the provisions of 14 CFR Part 91 of the Federal Aviation Regulations, originated in Torrance about 1840, and was en route to the Stellar Airpark. Night visual meteorological conditions prevailed. A visual flight rules (VFR) flight plan was filed and activated, and, VFR flight following was being provided to the pilot during the course of the flight. The pilot reported that he topped off both fuel tanks before takeoff and checked the tanks visually to verify that they were full. He opened a VFR flight plan approximately 10 minutes into the flight. His flight plan information indicated that he estimated the trip to take about 3 hours 15 minutes. The pilot reported that he flew at 7,500 feet agl and leaned the mixture for best economy fuel burn. The pilot reported that he had trouble locating the airport and received radar vectors from Phoenix TRACON. He stated that the vectors set him up for left traffic to runway 35. He first flew over the airport to get a feel for the layout of the runway. The pilot reported that he remained in left traffic, announced his landing intentions over the radio, and setup for a normal approach. He checked his fuel gauges and noted that both sides reflected 1/4 tank, which he estimated to be about 3 gallons in each side. About 200 feet agl, he noted that the runway appeared shorter than what was depicted on the chart or noted in the airport facility directory. The pilot performed a go-around and came back to setup for a short approach. He heard someone else on the radio frequency announcing that he was taxiing onto the active runway. The pilot couldn't see the aircraft, but decided to go around. He reported that he applied full power, pushed the carburetor heat in, and established a positive rate of climb. About 100 feet agl, the engine quit completely, with no coughing or sputtering. The pilot wasn't able to restart the engine and headed for a field about 15 degrees off the runway heading. The aircraft touched down in the field, impacted a berm, and became airborne again. The pilot stated that the airplane hit a tree with the right wing about 20 feet agl, then hit a light post with the left wing about 8 feet agl. The aircraft rotated forward and impacted the street in a nose down attitude. The aircraft nosed over and the tail hit a tree. The airplane came to rest inverted, with its tail resting against the tree. The Airport/Facility Directory information for Stellar Airpark indicates that the lighting for runway 35 is "non-standard." The runway is 4,004 feet long and only the last 2,000 feet are lighted; there are no threshold lights. A witness stated that because of the nonstandard lighting, approaches to Stellar Airpark are normally made from the north. The pilot reported that he assisted with the aircraft recovery following the accident. He noted that while the airplane was being trailered to the airport, a steady stream of fuel flowed out of the bottom fuel sump. The aircraft was later moved to another location. The aircraft recoverer reported that he removed approximately 1 gallon of fuel from the aircraft after it arrived at his facility. An examination of the engine was conducted following recovery of the aircraft. External examination of the engine revealed that the oil pan was cracked and oil was leaking out. No oil remained in the tank. The crankshaft was also cracked. The propeller was rotated through. The spark plugs were removed and it was noted that they exhibited wear and color patterns consistent with a short service time and correct heat range according to the Champion Aviation Check-A-Plug chart. Both magnetos produced sparks when rotated. Crankshaft rotation produced thumb compression in each cylinder, and, accessory gear and valve train continuity was established. Visual inspection of the induction system revealed a dark black discoloration. The carburetor was removed and disassembled and was noted to exhibit dark sooty deposits in the throat. The carburetor bowl contained approximately 1 inch of fuel, which appeared to be absent of debris or water. The carburetor was not equipped with an accelerator pump. During a go-around about 100 feet agl, the pilot applied full power and pushed in the carburetor heat and the engine quit completely, with no coughing or sputtering. The pilot reported that he headed for a field about 15 degrees off the runway heading. The aircraft touched down in the field and impacted a berm, a tree, and finally a light post. During recovery operations as the airplane was being trailered to the airport, a steady stream of fuel flowed out of the bottom fuel sump. The aircraft was later moved to another location where approximately 1 gallon of fuel was found in the tanks. An examination of the engine was conducted following recovery of the aircraft. No mechanical discrepancies were found with the engine or fuel system components. Dark sooty deposits were found in the carburetor throat. The carburetor does not have an accelerator pump. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_1999_LAX99LA173.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Search this event elsewhere
External sources are reported, not agency: signal that something happened, not fact about what happened.
- TallyAero Live Wire Aviation press
- NTSB CAROL Agency ↗
- NTSB Docket Agency ↗
- Aviation Safety Network Aviation press ↗
- Kathryn's Report Aviation press ↗
- Aviation Herald Aviation press ↗
- AVweb Aviation press ↗
- Pilots of America Community ↗
- Reddit /r/flying Community ↗
- FlightAware Aviation press ↗
- AOPA accident database Aviation press ↗
- Google News News ↗
- DuckDuckGo News ↗
Related research
Matched on aircraft type or causal vocabulary (go-around). All research papers
- NASA NTRS 2025 · Conference Paper A Training Study to Improve Monitoring During A Go-Around
As part of an FAA program to improve go-around (GA) safety, we were asked to determine if we could improve the performance of the Pilot Monitoring (PM) during a GA maneuver.
- Flight Safety Foundation 2024 · FSF / AeroSafety World Go-Around Safety Forum Findings
Foundation Go-Around Safety Forum technical findings — examines why pilots fail to execute go-arounds when criteria are met (stabilized approach gate not met, energy state out of envelope, traffic con…
- Semantic Scholar 2022 · Article (Journal of Safety Research) Go-around accidents and general aviation safety.
INTRODUCTION Changes in General Aviation (GA) accident rates, specifically in the go-around phase, are examined by comparing the number of accidents, the proportion of fatal accidents, and the proport…
- Semantic Scholar 2021 · Article (Aerospace) Classification and Analysis of Go-Arounds in Commercial Aviation Using ADS-B Data
Go-arounds are a necessary aspect of commercial aviation and are conducted after a landing attempt has been aborted. It is necessary to conduct go-arounds in the safest possible manner, as go-arounds …
- NASA NTRS 2021 · Accepted Manuscript (Version with final changes) Go-Around Criteria Refinement for Transport Category Aircraft
Presently, airline pilots are trained to go around if, when lower than 500 ft above the ground, they are outside of a handful of parameters such as airspeed, position, and rate of descent.
- NASA NTRS 2019 · Conference Paper Validation of Proposed Go-Around Criteria Under Various Environmental Conditions
This paper evaluates the effects of environmental conditions on touchdown performance under varying approach states and validates proposed go-around criteria developed using data from a previously con…