LAX06FA066 · Beech 36
Beech 36 · Accident: in flight collision with terrain/water on approach
From Santa Barbara Municipal Airport (SBA) to Livermore Municipal Airport (LVK)
Event
- NTSB case
- LAX06FA066
- 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
- 2 · 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
- Instrument Meteorological Cond
Beech 36
- Aircraft type
- Beechcraft 36
- 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
- N5942S
- Operator
- Edwin Mack
- Onboard fatalities
- Unknown
- Route
- From Santa Barbara Municipal Airport (SBA), Santa Barbara, CATo Livermore Municipal Airport (LVK), Livermore, 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
- Approach · IFR initial approach
- 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
- Substantial
Cause areas
- Pilot in command › Proper glidepath, 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 airplane collided with terrain 9 miles from the destination airport. The pilot was cleared for the instrument landing system approach into the airport. During the descent, the airplane was below the glideslope but tracking the localizer. The pilot contacted the air traffic control tower controller and was cleared to land. The last recorded radar target for the airplane was at 1,600 feet mean sea level (msl) and the initial impact occurred at 1,400 feet msl. The radar data indicated that the target maintained a descent rate of about 1,100 feet per minute during the last minute of flight and was flying at a radar derived ground speed of approximately 112 knots. Though the en route controller received a minimum safe altitude alert (MSAW), he had transferred control of the airplane 1 minute prior to the receipt of the initial MSAW alert. However, the airplane crossed a named intersection at 3,300 feet msl after it was cleared to cross the intersection at 4,000 feet msl while under the en route controller's control. The en route controller did not advise the pilot of the altitude deviation. The air traffic control tower controller did not issue an MSAW to the pilot, even though the equipment was configured to receive MSAW alerts. The tower controller said that he did not recall receiving the alerts and no recording was available to indicate whether or not an aural MSAW alert was received. An evaluation of the operation of the MSAW alerting system following the accident showed that it was functional. Examination of the airframe and engine did not reveal any mechanical anomalies to preclude normal operation. Metallurgical examination of the altimeter showed that the 10,000-foot pointer was not at its correct position at the time of impact and at an undetermined time prior to the accident, moved aft on its shaft and became loose. The effect of the 10,000-foot pointer on the pilot's flight performance could not be ascertained with the available evidence.
Probable cause
The pilot's failure to maintain the appropriate glidepath alignment during an instrument landing system approach, resulting in collision with terrain. A contributing factor to the accident was the failure of the air traffic controllers to issue a minimum safe altitude warning (MSAW) alert.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX06FA066
- Event ID
- 20051229X02031
- Case number
- LAX06FA066
- 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: investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 2b9ae082850d835bfa027d38d4bfdf07b52a3759a6c5da4ce45fb3c55a070a2d; retrieved 2026-09-20T17:41:20.193Z.