# NTSB LAX01LA052: Cessna 172H, N4959R, San Diego, CA, December 12, 2000 - Type: NTSB accident investigation - Classification: Accident · Serious injuries · Limited investigation · Final report - Date: December 11, 2000, 19:30 local (Dec 12, 2000, 03:30 UTC) - Place: San Diego, CA - Coordinates: 32.55001, -117.040763 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=32.5500&lon=-117.0408&mi=10 - Phase of flight: [Maneuvering](https://openairdocs.org/ntsb-phases/450) (OpenAirDocs' grouping) - Highest injury: Serious injuries - Injuries: 2 serious - Status: Completed, report May 28, 2002 - Report: Approved by Office Director - Parties: FAA Flight Standards District Office - NTSB case key (mKey): 50744 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=LAX01LA052 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/50744/pdf - Page: https://openairdocs.org/ntsb/LAX01LA052 ## Probable cause 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. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - In flight encounter with weather, maneuvering - weather condition - fog (contributing factor) - vfr flight into imc - inadvertent, pilot in command (cause) - weather evaluation - inadequate, pilot in command (cause) - In flight collision with terrain/water, maneuvering - light condition - dark night (contributing factor) - preflight planning/preparation - inadequate, pilot in command (cause) ## Analysis 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. ## 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. ## Aircraft - Registration: [N4959R](https://openairdocs.org/deregistered/N4959R-2001-05-14), registration cancelled 2001-05-14, S/N 17256280 (OpenAirDocs) - Reported make and model: Cessna 172H - Registry model: [Cessna 172H](https://openairdocs.org/model/cessna-172h) (registry code 2072424) (OpenAirDocs) - Category: Airplane - Serial number: 172-56280 - Airframe hours: 11148 - Engines: Continental O-300-D 145 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Registered owner: North Island Navy Flying Club - Airworthiness certificate: Standard, Normal - Last inspection: Annual, November 14, 2000, 50 hours before - Departed: NZY, North Island, CA - Destination: SDM, Brown Field, CA - Flight plan: VFR - Airport: SDM, Brown Field ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 34; injuries: serious; commercial; airplane ratings: single-engine sea, multi-engine land, single-engine land; instrument ratings: helicopter, airplane; medical: class 1, valid medical--no waivers/lim.; last flight review July 23, 2000; seat: left; flight hours: 377 total, 102 in this make and model, 297 as pilot in command, 20 in the last 90 days, 8 in the last 30 days ## Weather - Conditions: Instrument (IMC), Night/dark - Wind: 310° at 5 knots - Visibility: 5 statute miles - Lowest ceiling: 2,000 ft broken - Temperature: 54 °F, dew point 50 °F - Altimeter: 30.00 inHg - Observed at: SDM, 7 nm away ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20001211038729A](https://openairdocs.org/incident/20001211038729A), Dec 11, 2000: Cessna 172H, San Diego, CA, Substantial damage. (-23) On December 11, 2000, at about 1938 PST, a Cessna N4959R, operated by the north island navy flying club, piloted by robert a. volk collided with san… From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.