NTSB CAROL · Event
Event LAX98LA270
Aircraft involved
Probable cause & findings
The pilot's selection of the wrong runway for the wind conditions, his inadequate compensation for the existing quartering tailwind condition, and, his failure to maintain directional control.
Factual narrative
On August 18, 1998, at 1736 hours mountain standard time, a Silvaire Luscombe 8F, N1616Z, veered off runway 3 while landing at the Tucson, Arizona, International Airport. The aircraft, which was destroyed, damaged an Air National Guard (ANG) fence, and substantially damaged an ANG security truck. The commercial pilot sustained serious injuries and the driver of the truck incurred minor injuries. The aircraft was owned and operated by the pilot under the provisions of 14 CFR Part 91 of the Federal Aviation Regulations. Visual meteorological conditions prevailed and included winds from 280 degrees at 8 knots. The flight originated from Falcon Field, Mesa, Arizona at 1630. There was no flight plan filed for the personal flight. The pilot is a military aviator with the Arizona Air National Guard, stationed at the Tucson Airport, and flies the F-16. In his written report, the pilot stated that during contact with the Tucson Air Traffic Control Tower, he had requested runway 3 for landing. The tower issued the requested clearance along with the wind direction and speed, which was 280 degrees at 7 knots. He said that just before the tail wheel touched the ground, the plane veered left and he applied right rudder to no avail. He went on to state that he applied full power for a go-around, rotated the aircraft, but the engine did not respond and he was unable to make a successful climb. He clipped the fence and collided with the roof of a parked security truck behind the first row of F-16's. Witnesses reported that the aircraft landed fast on the main wheels, began veering left off the runway, became airborne, touched down in a dirt area, became airborne again, went through a chain link fence, and collided with an occupied security truck in the Arizona Air National Guard compound. Following recovery of the aircraft to a salvage facility in Phoenix, Arizona, the Safety Board examined the airframe and engine. No discrepancies were noted with the airframe. With a supply of fuel plumbed into the aircraft fuel lines at the wing root, the engine was started and found to respond to throttle inputs. Witnesses reported that the aircraft landed fast on the main wheels, began veering left off the runway, became airborne, touched down in a dirt area, became airborne again, went through a chain link fence, and collided with an occupied security truck in the Arizona Air National Guard compound. The airport was using runway 11 for takeoffs and landings. During initial contact with the Tucson Air Traffic Control Tower, the pilot had requested runway 3 for landing, and, the tower issued the requested clearance, along with the wind direction and speed of 280 degrees at 7 knots. The airframe and engine were examined following recovery with no discrepancies noted. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_1998_LAX98LA270.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 (go-around). 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 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…
Browse the full corpus — academia portal ↗