LAX99FA150 · Beech 36
Beech 36 · Accident: in flight collision with terrain/water on approach
From Calexico International Airport (CXL) to Montgomery-Gibbs Executive Airport (MYF)
Event
- NTSB case
- LAX99FA150
- 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
- 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
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
- N7706R
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Calexico International Airport (CXL), Calexico, CATo Montgomery-Gibbs Executive Airport (MYF)
- 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 final 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
- Destroyed
Cause areas
No findings designated as a cause are recorded in the NTSB data yet.
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot contacted FSS and requested weather at several local San Diego airports. He was told to expect low IFR conditions with visibility less than 1/4 mile in fog and indefinite ceilings of 100 feet. The pilot then obtained a clearance to enter the Class B airspace using a fictitious call sign. He requested and was issued an IFR clearance to the airport, and was later cleared for the ILS runway 28R approach. Prior to issuing the approach clearance, the controller asked the pilot what his intentions would be when he made the missed approach. The pilot replied that he would want radar vectors for a second approach. Numerous times on the approach the controller either asked the pilot if he was receiving the glideslope satisfactorily, or told him his position and what his altitude along the approach segments should have been. The controller issued two low altitude alerts; the final one at the outer marker where the airplane was observed 300 feet low. Recorded radar data showed that the airplane was consistently below ATC assigned and charted minimum descent altitudes for most of the approach. The airplane collided with trees and the ground about 1 mile short of the runway. Two ground witnesses reported hearing a loud noise and began looking for the source of the noise. They almost ran over the downed trees and the burning aircraft wreckage before acquiring it visually due to the dense fog. None of the pilot's personal logbooks or aircraft records could be located to establish his instrument currency, although the pilot's daughter stated that he flew fairly frequently. A postaccident examination of the airplane revealed no abnormalities in either the engine or the airframe. The day before the accident the same airplane had been observed entering Class B airspace and landing at a controlled field without an ATC clearance.
Probable cause
The pilot's failure to maintain the proper glidepath during an ILS approach. A factor in the accident was the pilot's disregard for the weather reports, which showed the airport as being below landing minimums.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX99FA150
- Event ID
- 20001205X00487
- Case number
- LAX99FA150
- 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. 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: b2862083f87cf0add066b5f65c88aafddd5370132fa96dbaf0292f13352c07a8; retrieved 2026-09-20T22:09:45.302Z.