NTSB CAROL · Event
Event LAX05CA257
Aircraft involved
Probable cause & findings
the pilot's failure to select an adequate altitude, which would assure clearance from the mountainous terrain while flying into a box canyon in high density altitude conditions.
Factual narrative
On July 31, 2005 about 1615 Pacific daylight time, a Cessna A150M, N8166V, collided with mountainous terrain during an en route climb from the Trinity Center Airport, Trinity Center, California. The pilot/owner was operating the airplane under the provisions of 14 CFR Part 91. The private pilot, the sole occupant, sustained minor injuries; the airplane was destroyed in the impact sequence and post crash fire. The personal cross-country flight departed Trinity Center about 1550, with a planned destination of Weed Airport, Weed, California. Visual meteorological conditions prevailed, and a flight plan had not been filed. In a written statement, the pilot reported that after flying into Trinity Center earlier in the morning, he spent the day engaged in physical exercise including biking and hiking. The pilot opted to takeoff from runway 14, making a left downwind departure. He noted the temperature to be about 90 degrees Fahrenheit when he departed from the 2,390-foot mean sea level (msl) airport. In an effort to divert from cumulus clouds ahead, the pilot maneuvered the airplane in a north-easterly direction toward a pass in the mountainous terrain ahead. He additionally performed a 360-degree climbing turn. The pilot further stated that about 20 minutes into the flight, he realized that deceptively level-looking terrain below was in actuality the relatively steep walls of a narrowing canyon. He noted the air becoming more turbulent and an increase in downdraft conditions. He attempted to maneuver the airplane out of the canyon, but was too late; he made a forced landing on a logging road at an elevation of about 6,000 feet msl. Prior to touchdown, the left wing impacted a tree and the airplane subsequently landed hard on the road. After coming to rest, the pilot noticed that the airplane was becoming engulfed in flames and his clothes started to catch on fire. He egressed the airplane and extinguished the flames on his clothes. Only sustaining minor injuries to his left knee, the pilot began a 3-hour task of dousing the airplane's fire with water he found in a nearby waterhole. After being satisfied that the fire would not spread to the nearby trees, he hiked out of the mountains. The pilot reported no pre-impact mechanical malfunctions or failures with the airplane. In addition, the pilot stated that he believed the cause of the accident to be his failure to acknowledge cumulative warning signals in a timely manner. He stated that contributing factors to the accident were his fatigue from physical exercise and lack of food, as well as air turbulence associated with cumulous activity and high density altitude. At 1556 a Meteorological Aviation Routine surface weather report (METAR) was issued at the airport located in Mount Shasta, California, located about 26 miles northeast of Trinity Center. It reported a temperature of 30 degrees Celsius and an altimeter setting of 30.05 InHg. Based upon the atmospheric conditions provided by the METAR, a Safety Board computer program calculated the density altitude at the 3,537-foot airport to be 6,028 feet. Using the standard lapse rate of 3-degrees Celsius per 1,000 feet of altitude, the density altitude computed to be about 8,600 feet at the accident site. The airplane collided with mountainous terrain during an en route climb on a course that took it into a box canyon. After a day of physical exertion, the pilot departed from the airport and headed for a pass in mountainous terrain. He noted that the temperature at the 2,390-foot mean sea level (msl) airport was about 90-degrees Fahrenheit. As he approached the pass, about 20 minutes into the flight, he realized that deceptively level-looking terrain below was in actuality the relatively steep walls of a narrowing canyon. The pilot noted the air becoming more turbulent and an increase in downdraft conditions. He attempted to maneuver the airplane out of the canyon, but did not have adequate altitude and made a forced landing onto a logging road, at an elevation of about 6,000 feet msl. Prior to touchdown, the left wing impacted a tree and the airplane subsequently landed hard on the road. The pilot egressed the airplane as it became engulfed in flames. The pilot reported no pre-impact mechanical malfunctions or failures with the airplane. Using the standard lapse rate of 3-degrees Celsius per 1,000 feet of altitude, the density altitude was calculated to be about 8,600 feet at the accident site. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2005_LAX05CA257.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 (turbulence). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- arXiv 2026 · arXiv preprint
Direct Numerical Simulations of Ice-Ocean Boundary Turbulence
Turbulent heat and freshwater transport at ice-ocean interfaces controls glacier and iceberg melt rates, yet the underlying physics remains poorly constrained.
- Embry-Riddle Scholarly Commons 2025 · Journal article (JAAER)
Political Turbulence and Aviation Safety: A Cross-National Analysis of Political Stability's Effects on Aviation Accidents
To what extent does political stability affect aviation safety? This research aims to link domestic political conditions and public safety through the consideration of aviation accident frequency.
- arXiv 2025 · arXiv preprint
Explainable LiDAR 3D Point Cloud Segmentation and Clustering for Detecting Airplane-Generated Wind Turbulence
Wake vortices - strong, coherent air turbulences created by aircraft - pose a significant risk to aviation safety and therefore require accurate and reliable detection methods.
- arXiv 2024 · arXiv preprint
Does small-scale turbulence matter for ice growth in mixed-phase clouds?
Representing the glaciation of mixed-phase clouds in terms of the Wegener-Bergeron-Findeisen process is a challenge for many weather and climate models, which tend to overestimate this process because…
- arXiv 2023 · arXiv preprint
Effects of electrostatic interaction on clustering and collision of bidispersed inertial particles in homogeneous and isotropic turbulence
In sandstorms and thunderclouds, turbulence-induced collisions between solid particles and ice crystals lead to inevitable triboelectrification.
- SKYbrary (Eurocontrol) 2023 · SKYbrary article
Wake Vortex Turbulence — SKYbrary Knowledge Base
SKYbrary wake vortex turbulence comprehensive article — generation mechanics, dissipation factors, separation standards (ICAO LIGHT/MEDIUM/HEAVY/SUPER + recategorisation RECAT-EU).
Browse the full corpus — academia portal ↗