LAX01LA052
2000-12-11 · SAN DIEGO, California, United States · Serious · 1 aircraft · Status: Completed
Airport SDM
Aircraft involved
Probable cause & findings
The pilot's inadequate preflight planning and weather evaluation that resulted in the inadvertant entry into instrument meteorological conditions while conducting visual flight. A factor was fog and the night visual conditions.
Factual narrative
On December 11, 2000, about 1930 hours Pacific standard time, a Cessna 172H, N4959R, operated by the North Island Navy Flying Club, was substantially damaged when it collided with San Miguel Mountain about 7 nautical miles north-northeast of Brown Municipal Airport, San Diego, California. The commercial pilot and commercial rated passenger both received serious injuries. Visual meteorological conditions prevailed at the departure point for the personal flight that was operated under 14 CFR Part 91. A visual flight rules flight plan was filed. The flight originated at NAS North Island, San Diego, about 1920, and was destined for landing practice at Brown, Gillespie, and Montgomery airports before returning to NAS North Island. The pilot contacted the Brown Field Federal Aviation Administration Air Traffic Control Tower about 1925, when approximately 5 miles west of the airport, and reported inbound for touch-and-go landings. He was instructed to enter a right downwind for runway 26R, and to change to the correct frequency. The pilot said he did not have the current Automated Terminal Information Service (ATIS) for weather information. After changing frequency he was given the current weather. The controller noticed the airplane just west of "Poggi" VOR (2.3 nautical miles north of the runways), and it appeared to be headed northbound away from the airport. The controller asked the pilot if he had the airport in sight and he responded he did not, but that he was just practicing some maneuvers and he was a little busy in the cockpit. A couple of minutes later the airplane was observed to be about 7 miles north. The controller advised the pilot to report the prison if he was still inbound for a right base entry for runway 26R. The next readable transmission from the pilot was "encountering some soup." According to the operator's report of the accident, upon entering the clouds, the pilot started a 75 mph climb, followed by a right turn just before impact. The pilot did not respond to additional calls from the controller and was no longer observed on the D-Brite radar system. The airplane had collided with a 2,791-foot mountain about 7 miles north of the intended airport. After the accident the pilot called 911 on his cell phone. The California Highway Patrol answered and relayed the call to Hartland Fire Department for rescue. The pilot stated to fire rescue personnel that they were on approach to Brown Airport when they ran into a fog bank and collided with the terrain. Located on Sectional Aeronautical and VFR Terminal Area Charts are maximum elevation figures (MEF). They establish the highest known feature in each quadrangle, including terrain and obstructions (trees, towers, antennas, etc.). The MEF for the accident area is 4,100 feet above mean sea level. The pilot filed a visual flight plan to practice night landings. He contacted the tower about 1930, when approximately 5 miles west of the airport, and reported inbound for touch-and-go landings. The pilot was instructed to enter a right downwind for runway 26R, and to change to the correct frequency. The pilot said he did not have the current Automated Terminal Information Service (ATIS) for weather information, and was given the current weather after he changed frequencies. The controller noticed the airplane just west of "Poggi" VOR (2.3 nautical miles north of the runways), and it appeared to be headed northbound away from the airport. The controller asked the pilot if he had the airport in sight and he responded he did not, but that he was practicing some maneuvers and was a little busy in the cockpit. A couple of minutes later the airplane was observed to be about 7 miles north. The controller advised the pilot to report the prison if he was still inbound for a right base entry for runway 26R. The next readable transmission from the airplane was "encountering some soup." According to the operator, upon entering clouds, the pilot started a 75 mph climb, followed by a right turn just before impact. The pilot did not respond to additional calls from the controller and was no longer observed on the D-Brite radar system. The airplane had collided with a 2,791-foot mountain about 7 miles north of the intended airport. According to VFR charts, the maximum elevation figure for the accident quadrangle/sector is 4,100 feet mean sea level. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2000_LAX01LA052.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 (icing). All research papers
- arXiv 2026 · arXiv preprint Enabling Beyond-Visual-Line-of-Sight Drones Operation over Open RAN 5G Networks with Slicing
Among the foretold claims of the transition from 5G to 6G, Beyond-Visual-Line-of-Sight (BVLoS) drone operation has emerged as a prominent Internet-of-Robots enabler.
- NASA NTRS 2026 · Contractor Report (CR) Icing Physics Studies Using the 3D SIDRM Test Article: 2023 Icing Tests Analysis
In-flight icing is an important safety issue and is a factor that affects aircraft design and performance. Newer regulations are driving a need for improvements in airframe and engine icing simulation…
- arXiv 2025 · arXiv preprint Multi-Agent Deep Reinforcement Learning for UAV-Assisted 5G Network Slicing: A Comparative Study of MAPPO, MADDPG, and MADQN
The growing demand for robust, scalable wireless networks in the 5G-and-beyond era has led to the deployment of Unmanned Aerial Vehicles (UAVs) as mobile base stations to enhance coverage in dense urb…
- NASA NTRS 2025 · Presentation NASA Icing Update – March 2025
This NASA Icing Update was prepared for presentation to the SAE International AC-9C Inflight Icing Technology Committee. This update includes the following topics: planned Rotational Icing Scaling tes…
- Embry-Riddle Scholarly Commons 2025 · Journal article (JAAER) A Mathematical Model on the Temporal Dynamics of Aviation Competitive Pricing
This study investigates the competitive dynamics of airport pricing using U.S. airport data to validate the findings. It employs linear and nonlinear ordinary differential equation models to analyze t…
- arXiv 2024 · arXiv preprint An energy-stable phase-field model for droplet icing simulations
A phase-field model for three-phase flows is established by combining the Navier-Stokes (NS) and the energy equations, with the Allen-Cahn (AC) and Cahn-Hilliard (CH) equations and is demonstrated ana…