FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX08FA300 · Beech A36

28 Sept 2008 · Carlsbad, CA, United States

Beech A36 · Accident: loss of control in flight on approach

From Lake Havasu City Airport (KHII) to McClellan-Palomar Airport (KCRQ)

Report a problem

Event

NTSB case
LAX08FA300
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
Instrument Meteorological Cond

Beech A36

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
N82TB
Operator
Unknown
Onboard fatalities
Unknown
Route
From Lake Havasu City Airport (KHII), Lake Havasu City, AZTo McClellan-Palomar Airport (KCRQ), Carlsbad, 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 final approach
Defining eventThe 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
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

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The airplane was on an Instrument Landing System (ILS) approach to Runway 24. The reported weather was 100-foot ceiling and 1/4-mile visibility in fog at the airport. The published weather minimums for the ILS 24 approach are 200-foot ceiling and 3/4-mile visibility. The tower controller relayed to the pilot that the runway visual range was 1,600 feet (1/4 mile), winds were 280 degrees at 5 knots, and the flight was cleared to land on Runway 24. About 2 minutes later the tower controller issued the pilot a low altitude alert, followed by a notification that it appeared that the pilot was south of course. About 2 minutes later, the pilot transmitted that he was going to ‘abort’ the approach. The pilot's last transmission 1 minute later stated "I’m in trouble." Despite numerous attempts, no further communications with the pilot were established. Radar data indicated that, 2 miles from the approach end of Runway 24, the airplane crossed over the final approach course at 800 feet msl (mean sea level) heading south. The track started a tight left-hand turn with altitude readings that fluctuated between 600 and 1,100 feet msl. The last radar return depicted the airplane at 900 feet msl and at a ground speed of 56 knots. The airplane wreckage was confined to the initial impact point, located on an approximate 40-degree sloping hillside, 1.3 miles southeast of the approach end of Runway 24, in the same vicinity as the last radar return. Post accident inspection of the airframe and engine found no evidence of a mechanical failure or malfunction. The pilot had received his instrument rating 2 months prior to the accident, and had accumulated approximately 41 hours of actual instrument time. Approximately 11.1 hours of dual instruction had been accumulated in the accident airplane. The pilot received no instrument flight training in the accident airplane.

Probable cause

The pilot's failure to maintain control during the instrument approach and attempted go-around.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX08FA300
Event ID
20081004X12046
Case number
LAX08FA300
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 9410cfc90ebb66bff9cd37f6376d7c87f8242a0c4443b4a0310c334f705bd73e; retrieved 2026-09-13T19:31:57.690Z.