LAX06FA243 · Raytheon Aircraft Company G36
Raytheon Aircraft Company G36 · Accident: in flight collision with terrain/water during landing
From Eagle Airpark (A09) to A09
Event
- NTSB case
- LAX06FA243
- 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 G36
- 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
- N241JL
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Eagle Airpark (A09), Bullhead City, AZTo A09
- 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
- Landing · aborted
- 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 › Aborted landing, improper
- Pilot in command › Impairment(alcohol)
- Pilot in command › Proper touchdown point, not obtained
- Pilot in command › Recovery from bounced landing, inadequate
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 a dirt berm during an aborted landing. A bartender reported that about 5.5 hours prior to the accident, she served the pilot four alcoholic beverages, though he never appeared to be intoxicated. The pilot and the two passengers left the bar together about 1 to 2 hours prior to the accident, and a designated driver transported them to the airport. According to the designated driver, the pilot did not appear to be intoxicated. A witness observed the airplane taxi past his hangar to the active runway and takeoff. He reported that the airplane made erratic s-turns up the taxiway and also climbed out in an erratic manner. According to the surviving passenger, who was in the front-right seat, after a 25-minute flight, the pilot made an approach to the airport and touched down over halfway down the runway. The airplane landed hard and bounced back airborne, continuing down the runway about 2 to 3 feet above ground level (agl). After reaching the end of the runway, the airplane touched back down on the surface. The pilot attempted to abort the landing, but the airplane continued into the brush and impacted a dirt berm. Post accident examinations of the airframe and engine revealed no evidence of mechanical malfunctions or failures. The FAA toxicological tests on the pilot's specimens found that the post-mortem blood ethanol level was 0.365 percent, with a post-mortem urine ethanol level at 0.357 percent. Although there was evidence of putrefaction, careful analysis established that most of the ethanol found in the specimens was a result of ingestion, and at the time of the accident, the pilot's blood alcohol concentration (BAC) was at or above 0.30 percent. On his FAA application for a medical certificate, the pilot reported one Driving Under the Influence (DUI) conviction, which occurred over 5 years prior to the accident (2 years prior to submitting the application); the FAA medical records contained no details of that DUI, but review of the arrest records noted that the pilot's BAC was 0.28 percent during that arrest. Review of Federal Bureau of Investigation (FBI) records indicated that the pilot actually had three additional convictions for drug and/or alcohol related offenses, including another DUI about 12 years prior to the accident. The FAA specifically disqualifies pilot applicants with a history or clinical diagnosis of substance dependence, which is defined in 14 CFR 67.107, 67.207, and 67.307 as "evidenced by (A) increased tolerance, (B) manifestation of withdrawal symptoms, (C) impaired control of use, or (D) continued use despite damage to physical health or impairment of social, personal, or occupational functioning." The FAA additionally requires that airmen report any convictions involving driving while intoxicated or while under the influence of alcohol or a drug, and performs a National Driver Register (NDR) inquiry for each medical application to verify that all such convictions are in fact reported. Because of individual state variances on the length of time convictions stay on record, and periodic purges of convictions by States from the NDR, the data in the NDR may not show all convictions for a specific individual. The only national database that retains all convictions is the FBI's records. The FAA only references FBI records for an applicant in the rare instance when credible information suggests that multiple unreported convictions may exist. A senior legal attorney for the FAA reported that the agency does not have legal authority to routinely access FBI criminal records.
Probable cause
The pilot's misjudged distance and speed that led to a long landing, and his inadequate recovery from a bounced landing, all due to the effects of impairment from alcohol consumption, which resulted in an in-flight collision with terrain during an aborted landing attempt. A contributing factor was the Federal Aviation Administration's failure to identify existing evidence of substance (alcohol) dependence in the pilot due to an inadequate and incomplete process of screening medical applications.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX06FA243
- Event ID
- 20060727X01040
- Case number
- LAX06FA243
- 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: fa1710a8291735e1243993d8ec7bd5799f739418f9aa69fbe22880de5999365a; retrieved 2026-09-20T17:08:37.754Z.