LAX83FUM01 · Beech A35
Beech A35 · Accident: loss of control in flight on approach
From Montgomery-Gibbs Executive Airport (MYF) to Bellingham International Airport (BLI)
Event
- NTSB case
- LAX83FUM01
- 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
- 4 · 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
- Visual Meteorological Cond
Beech A35
- Aircraft type
- Beechcraft 35
- 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
- N696B
- Operator
- Bruno Carl Bossard
- Onboard fatalities
- Unknown
- Route
- From Montgomery-Gibbs Executive Airport (MYF), San Diego, CATo Bellingham International Airport (BLI), Bellingham, WA
- 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 · VFR pattern base
- 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
- Loss of control in flight
- 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
- Stall/spin
- 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 › Airspeed, inadequate
- Pilot in command › Stall/spin, inadvertent
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
DURING ARRIVAL, THE AIRCRAFT ENTERED DOWNWIND FOR A RIGHT TRAFFIC PATTERN TO RUNAY 24. AT THAT TIME, A WITNESS (A WELL QUALIFIED PILOT) NOTED THAT THE WIND WAS FROM THE NORTHEAST AT ABOUT 8 KTS. ANOTHER PILOT-WITNESS STATED THAT THE WIND WAS FROM THE NORTHEAST AT ABOUT 10 KTS OR MORE. ABOUT 7 MI SOUTHEAST AT AN OFFICIAL WEATHER OBSERVATION FACILITY, THE WIND WAS FROM 320 DEG AT 8 KTS. AS THE AIRCRAFT CONTINUED ON DOWNWIND, IT REPORTEDLY ANGLEO TOWARD THE RUNWAY, WAS AT A LOWER-THAN-NORMAL ALTITUDE, AND THE AIRSPEED WAS SLOW. REPORTEDLY, THE AIRCRAFT WAS IN A DESCENDING TURN TOWARD THE RUNWAY, WHEN IT ENTERED A SPIN AND CRASHED. NO PREIMPACT ABNORMALITIES WERE FOUND DURING AN EXAMINATION AT THE CRASH SITE.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record LAX83FUM01
- Event ID
- 20020917X04821
- Case number
- LAX83FUM01
- 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: e97e69be4e07d215812fc158db03e5ffc6eb9c89d2b3df4ec90b8e1795f39396; retrieved 2026-09-21T07:40:51.143Z.