LAX01LA052 · Cessna 172H
Cessna 172H · Accident: in flight encounter with weather while maneuvering
From North Island Naval Air Station-Halsey Field (NZY) to Brown Field Municipal Airport (SDM)
Event
- NTSB case
- LAX01LA052
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- 0
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Instrument Meteorological Cond
Cessna 172H
- Aircraft type
- Cessna 172
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N4959R
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From North Island Naval Air Station-Halsey Field (NZY), North Island, CATo Brown Field Municipal Airport (SDM), Brown Field, CA
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Maneuvering
- First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- In flight encounter with weather
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Visual flight rules (VFR) flight into instrument meteorological conditions (IMC)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Pilot in command › Preflight planning/preparation, inadequate
- Pilot in command › VFR flight into imc, inadvertent
- Pilot in command › Weather evaluation, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX01LA052
- Event ID
- 20001218X45440
- Case number
- LAX01LA052
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2000-12-12.
- API snapshot SHA-256: a016a9423b422a6ad01ba3d039e28b53d3c2225a988e42de9751c8f9bfa5658a; retrieved 2026-09-21T10:17:57.578Z.