LAX06FA222 · Raytheon Aircraft Company A36
Raytheon Aircraft Company A36 · Accident: in flight collision with terrain/water during an emergency descent
From Santa Barbara Municipal Airport (SBA) to Wiley Post Airport (PWA)
Event
- NTSB case
- LAX06FA222
- 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
- Visual Meteorological Cond
Raytheon Aircraft Company 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
- N615M
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Santa Barbara Municipal Airport (SBA), Santa Barbara, CATo Wiley Post Airport (PWA), Oklahoma City, OK
- 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
- Emergency 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
- Reason for occurrence undetermined
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot was departing on a cross-country flight when he advised an air traffic controller that he needed to land at the nearest airport. The pilot did not specify why he needed to land. An air traffic controller initially cleared him to one airport, and then the pilot asked for a clearance to closer airport. Multiple controllers were in contact with the pilot after his initial call that he needed to land. During the first call, the initial controller and a second controller had a discussion about what the nature of the problem was, and if the pilot was declaring an emergency. The primary controller reported that he thought the pilot was having an engine problem, and he was not declaring an emergency. Once the pilot was handed off to the second controller, the pilot was asked if he had an engine problem and if wanted to declare an emergency. The pilot replied negatively to both questions. The pilot was then handed off to the final controller at the airport where he wanted to land. The pilot was unable to advise the air traffic controller at the landing airport of his position. The pilot was cleared to land, but then he reported an unspecified emergency and collided with terrain approximately 3 miles north of the airport. The airplane came to rest straddling a ditch, adjacent to a road, and was mostly consumed in the post-impact fire. The engine came to rest at the top of the ditch on the south side, and the tail section came to rest on top of the ditch on the north side. An engine inspection and teardown were conducted, with no mechanical anomalies noted that would have precluded normal operation. No evidence was found of any airframe system malfunction or flight control problem. To date, the pilot has not responded to requests from the investigator-in-charge for a statement as to the source of the problem and subsequent emergency. The investigation determined that the pilot was taking a prescription antidepressant, a metabolite of which was detected on post-accident toxicology testing. He was also reported to have recently begun using a prescription anti-anxiety medication, not detected on post-accident toxicology testing, but for which therapeutic levels are below the detection threshold on such testing. Neither medication would have been approved for use by the FAA. The pilot had not reported any mental conditions or use of medications at the time of his most recent application for airman medical certificate nearly 2 years prior to the accident.
Probable cause
a ground collision during an emergency landing for undetermined reasons.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX06FA222
- Event ID
- 20060708X00900
- Case number
- LAX06FA222
- 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: 278c2016555e060198ec22c130bfa3c2310674941dc7e224e314519cc1dd4dd9; retrieved 2026-09-20T17:13:51.819Z.