LAX02FA073 · Piper Aerostar 601P
Piper Aerostar 601P · Accident: in flight collision with terrain/water en route
From Chico Regional Airport (CIC) to Ukiah Municipal Airport (UKI)
Event
- NTSB case
- LAX02FA073
- 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
- 1 · all aircraft and ground
- Ground fatalities
- Unknown
- 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
- Visual Meteorological Cond
Piper Aerostar 601P
- Aircraft type
- Piper AEROSTAR 601
- 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
- N3636M
- Operator
- John Michael Turner
- Onboard fatalities
- Unknown
- Route
- From Chico Regional Airport (CIC), Chico, CATo Ukiah Municipal Airport (UKI), Ukiah, 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
- En route · cruise
- 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 collision with terrain/water
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Altitude/clearance, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The twin engine airplane impacted mountainous terrain at the 6,700-foot level during moonless night flight operations. The instrument rated pilot radioed the Air Route Traffic Control Center (ARTCC) and requested flight following and a vector to the destination airport. The pilot indicated he was flying at 6,700 feet and was descending. The controller radar identified the airplane and issued the recommended heading. The pilot asked for additional distance and airspeed information, which was provided by the controller, and no further radio contact with the pilot was attained. The airplane impacted a mountain approximately 50 feet below its crest in the approximate direction of the radar ground track. A post accident examination of the airplane and engines revealed no anomalies that would have prevented its normal operations. Interviews with the air traffic controllers, who were providing the accident airplane's flight following information, indicated they did not think the airplane was in imminent danger of impacting terrain; therefore, they did not issue a low altitude alert. Controllers are required to immediately issue an alert to an airplane if they are aware the airplane is at an altitude, which in the controllers judgment, places it in unsafe proximity to terrain/obstructions. The controllers reported they have worked numerous airplanes in that area at similar altitudes as the accident airplane and did not think the accident airplane was any different. The controllers added that they did not have terrain information overlaid on their video map for the accident area. The responsibility to maintain terrain clearance during visual meteorological conditions rests with the pilot. The accident area sectional chart depicts a maximum elevation figure (MEF) for the accident site quadrant as 7,400 feet.
Probable cause
the pilot's failure to maintain terrain clearance during cruise flight, which resulted in the in-flight collision with mountainous terrain. Factors in the accident were the mountainous terrain and the dark night light conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX02FA073
- Event ID
- 20020205X00185
- Case number
- LAX02FA073
- 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, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2002-01-31.
- API snapshot SHA-256: d36fe7f3f5aa138c408a62e968b940b688c4ad07234ef2ada246df0d566f9bb9; retrieved 2026-09-20T20:13:26.418Z.