Casualties unknown

2006-07-01: Raytheon Aircraft Company A36 (N615M) — Somis, CA

Somis, CA, US

On July 1, 2006, a Raytheon Aircraft Company A36 (registration N615M) was involved in an aviation accident near Somis, CA. Investigators recorded the probable cause as: a ground collision during an emergency landing for undetermined reasons. This summary draws on records from the U.S. National Transportation Safety Board (NTSB) historical archive.

Sourcesthe U.S. National Transportation Safety Board (NTSB) historical archivePrimary reportUpdated 1781061362Data APIEditorial standards

A pilot on a cross-country flight requested to land at the nearest airport, declined to declare an emergency, then later reported an unspecified emergency before colliding with terrain. Post-accident investigation found no mechanical issues but detected prescription medications not approved for use by the FAA.

Incident Overview

A pilot conducting a cross-country flight contacted an air traffic controller and stated that he needed to land at the nearest airport but did not specify the reason. The controller initially cleared him to one airport, but the pilot requested clearance to a closer airport. Multiple controllers communicated with the pilot after his initial request.

Controller Communications

During the first call, the initial controller and a second controller discussed the nature of the problem and whether the pilot was declaring an emergency. The primary controller reported that he believed the pilot was experiencing an engine problem and that the pilot was not declaring an emergency. After being handed off to the second controller, the pilot was asked if he had an engine problem and if he wanted to declare an emergency. The pilot answered no to both questions.

Final Approach and Collision

The pilot was then handed off to the final controller at the intended landing airport. He was unable to advise that controller of his position. He was cleared to land but subsequently reported an unspecified emergency and collided with terrain approximately three 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 the north side.

Investigation Findings

An engine inspection and teardown revealed no mechanical anomalies that would have precluded normal operation. No evidence of any airframe system malfunction or flight control problem was found. The pilot has not responded to requests from the investigator-in-charge for a statement regarding the source of the problem and subsequent emergency.

Toxicology Results

Post-accident toxicology testing detected a metabolite of a prescription antidepressant that the pilot was taking. He was also reported to have recently begun using a prescription anti-anxiety medication, which was not detected on testing because therapeutic levels are below the detection threshold. Neither medication would have been approved for use by the Federal Aviation Administration. The pilot had not reported any mental conditions or medication use at the time of his most recent application for an airman medical certificate nearly two years prior to the accident.

Investigation report by the U.S. National Transportation Safety Board (NTSB) historical archive. Original record: https://carol.ntsb.gov/event/20060708X00900. This page is a structured re-presentation; facts and quotes are in the National Transportation Safety Board (NTSB), United States.