ASN Wikibase Occurrence # 268870
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information.
If you feel this information is incomplete or incorrect, you can submit corrected information.
| Date: | Monday 11 December 2000 |
| Time: | 19:30 LT |
| Type: |  Cessna 172H |
| Owner/operator: | |
| Registration: | N4959R |
| MSN: | 172-56280 |
| Total airframe hrs: | 11148 hours |
| Engine model: | Continental O-300-D |
| Fatalities: | Fatalities: 0 / Occupants: 2 |
| Aircraft damage: | Substantial |
| Category: | Accident |
| Location: | SAN DIEGO, California -
 United States of America
|
| Phase: | Unknown |
| Nature: | Private |
| Departure airport: | North Island, CA (NZY) |
| Brown Field, CA (SDM) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
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.
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.
Accident investigation:
 |
|
Sources:
NTSB LAX01LA052
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 15-Oct-2021 12:55 | ASN Update Bot | Added |
Corrections or additions? ... Edit this accident description
The Aviation Safety Network is an exclusive service provided by:
Quick Links:
| ASN Home | Send Correction / Feedback |
| FSF Home | Disclaimer | Copyright |
| Contact Us | Privacy Policy |
| Press / Media |
CONNECT WITH US:
©2024 Flight Safety Foundation