NTSB CAROL · Event
Event LAX05CA307
Registry · N8063T
FAA Aircraft Registry record.
Make / Model
PIPER PA-32-301
Seats / Engines
7 seats · 1 engine
Last airworthiness date
19820120
ADS-B equipped
Yes — Mode-S AAFAFA
Registrant of record
HEAUSER FREDERICK M
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
the pilot's inadequate compensation for wind conditions and failure to maintain directional control. Contributing factors to the accident were the gusting quartering tail wind conditions.
Factual narrative
On September 16, 2005, at 1500 Pacific daylight time, N8063T, a Piper PA-32-301 (Saratoga), collided with a runway sign during landing at the Reno Tahoe International Airport (RNO), Reno, Nevada. The airplane was registered to a private company and being operated by the pilot under the provisions of 14 CFR Part 91. The private pilot and one passenger were not injured; the airplane sustained substantial damage. Visual meteorological conditions prevailed, and no flight plan was filed. The pilot departed from French Valley Airport (F70), Murrieta/Temecula, California, and was landing at his destination when the accident occurred. In a written statement, the pilot reported that the flight went as planned until arriving into the Reno vicinity. Approximately 20 nautical miles south of Reno, the pilot received the weather information. The winds were reported out of the west at 23 knots, gusting to 30 knots. He was cleared to land on runway 16R and while he was on final, the air traffic control tower controller requested that the pilot go-around due to inbound jet traffic. The pilot was then cleared to land on runway 16L. During touchdown on runway 16L, the airplane's indicated air speed (IAS) was 70 knots and 20 degrees of flaps were extended. As the airplane rolled down the runway, the IAS increased 10 to 15 knots. After 300 feet of roll out, a wind gust hit the airplane and pushed it to the left side of the runway. The pilot applied corrective action; however, the airplane impacted a runway sign approximately 6 to 10 feet from the runway edge. After the airplane impacted the sign, the nose gear collapsed and the airplane slid to a stop. The left wing spar attach was damaged and the firewall sustained impact damage. No mechanical problems were reported. The operations officer for the airport measured the distance between the runway sign and the runway surface. The runway is 150 feet wide and is made of concrete. There is a white runway edge line and next to that is an asphalt shoulder, approximately 35 feet wide and it is black. From the runway edge, the sign is located 60 feet from it. From the runway centerline to the sign, the distance is 135 feet. From the runway shoulder edge, the runway sign distance is 25 feet. The airplane collided with a runway sign during landing and the firewall and left wing spar attach point were damaged. The pilot said that the flight went as planned until arriving into the vicinity of his landing airport. Approximately 20 nautical miles south, the pilot received the weather information. The winds were reported out of the west at 23 knots, gusting to 30 knots. He was cleared to land on runway 16R and while he was on final, the air traffic control tower controller requested that the pilot go-around due to inbound jet traffic. The pilot was then cleared to land on runway 16L. During touchdown on runway 16L, the airplane's indicated air speed (IAS) was 70 knots and 20 degrees of flaps were extended. As the airplane rolled down the runway, the IAS increased 10 to 15 knots. After 300 feet of roll out, a wind gust hit the airplane and pushed it to the left side of the runway. The pilot applied corrective action; however, the airplane impacted a runway sign approximately 6 to 10 feet from the runway edge. After the airplane impacted the sign, the nose gear collapsed and the airplane slid to a stop. The left wing spar attach was damaged and the firewall sustained impact damage. No mechanical problems were reported. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2005_LAX05CA307.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 ↗