LAX98FA106 · Piper PA-31-350
Piper PA-31-350 · Accident: in flight collision with terrain/water en route
From Charles M. Schulz Sonoma County Airport (STS) to Oakland San Francisco Bay Airport (OAK)
Event
- NTSB case
- LAX98FA106
- 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
- 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
Piper PA-31-350
- Aircraft type
- Piper PA-31
- 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
- N257NW
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Charles M. Schulz Sonoma County Airport (STS), Santa Rosa, CATo Oakland San Francisco Bay Airport (OAK), Oakland, 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 · descent
- 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 › Clearance, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The airplane was on a VFR dusk cross-country flight when it collided with the 1,500-foot level of a hill. Radar data showed the aircraft in a descent from 2,000 feet until radar contact was lost about 1,500 feet msl, with a final ground speed of 194 knots. The route taken by the pilot was about 5 miles west of the route that the company pilots routinely flew, but while crossing higher terrain, it was a more direct route to the destination. A company pilot flying a few minutes ahead of the accident flight reported it was necessary to descend to between 1,200 and 1,500 feet msl in order to maintain VFR. A low-pressure system approaching the area from the west had resulted in low stratus, rain, and fog. At the time of the accident, a nearby weather reporting facility reported a 1,300-foot broken ceiling with 5- to 6-mile visibility in light rain and mist. On the evening of the accident, the pilot was scheduled to give a speech as her final examination in an evening college course. She had informed the instructor that she might be late, but had been told that he could not hold the class past its scheduled dismissal time to accommodate her late arrival.
Probable cause
the pilot's failure to maintain adequate terrain clearance after initiating a descent over mountainous terrain at night and under marginal VFR conditions. The pilot's self-induced pressure to arrive at class with enough time remaining to take the final examination was a factor in the accident.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX98FA106
- Event ID
- 20001211X09697
- Case number
- LAX98FA106
- 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 1998-03-06.
- API snapshot SHA-256: faee193f743300abeac5d04878253a48d5b2b3d5728d7e9210f6ff8f39aa7af7; retrieved 2026-09-20T22:39:54.213Z.