FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR15FA195 · Short Brothers PLC S312 TUCANO T MK1

22 Jun 2015 · Maricopa, CA, United States

Short Brothers PLC S312 TUCANO T MK1 · Accident: low altitude operation/event while maneuvering

From Camarillo International Airport (CMA) to Camarillo International Airport (CMA)

Report a problem

Event

NTSB case
WPR15FA195
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
Visual Meteorological Cond

Short Brothers PLC S312 TUCANO T MK1

Aircraft type
Short Brothers S312
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
N206PZ
Operator
Unknown
Onboard fatalities
Unknown
Route
From Camarillo International Airport (CMA), Camarillo, CATo Camarillo International Airport (CMA), Camarillo, CA
Aircraft age
About 26 years (built 1989)
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
Maneuvering · low-altitude flying
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
Low altitude operation/event
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 private pilot was performing airwork and was in contact with an air traffic controller. The pilot informed the controller that he would be performing airwork between 2,500 and 10,000 ft mean sea level (msl). The controller explained that he would probably lose radio contact and would not be able to provide flight following below 7,000 ft msl. About 1 hour later, the pilot advised the controller that he would be descending, then would climb to 9,000 ft msl and return to the airport, and the controller acknowledged. Subsequently, the controller made several attempts to contact the pilot, but no further response was received from him. Shortly thereafter, an airplane flying in the area of the accident site reported to air traffic control that a small fire was located in a river bed. Local authorities responded to the fire and confirmed that it was the accident site.

A review of Federal Aviation Administration radar data showed the airplane performing multiple turns and rapidly changing altitude and airspeed while performing the airwork. At one point, the airplane descended to less than 100 ft above a mountain ridgeline. The last radar targets showed the airplane heading eastbound about 1,600 ft agl while approaching the area of the accident site. Two witnesses located near the accident site stated that, as the airplane flew overhead, they noted no engine anomalies.

Postaccident examination of the wreckage did not reveal any preimpact malfunctions that would have precluded normal operation. Wreckage and impact signatures were consistent with a high-energy high-angle impact with terrain. It is likely that as the pilot continued to perform low level airwork, he did not properly gauge the airplane's distance from terrain and failed to control the airplane in time to avoid impacting terrain.

The pilot's high cholesterol and the medications he was using to treat it likely did not cause any acute symptoms. Limited samples were available for toxicology testing; therefore, it could not be determined whether the ethanol detected in the pilot's muscle tissue was due to ingestion or postmortem production nor whether impairment due to ethanol contributed to the accident. The testing also detected butalbital and codeine, both of which are impairing. The butalbital was within the therapeutic level, indicating that he was likely impaired by it. The presence of both codeine and butalbital indicates that the pilot had likely recently used a combination product that contained at least these two medications. Therefore, it is likely that the pilot's mental and/or physical abilities required for the duration of the high workload flight performance was impaired by the combined effects of butalbital and codeine and that this impairment contributed to the accident.

Probable cause

The pilot's failure to maintain clearance from terrain during low-level airwork, which resulted in uncontrolled collision with terrain. Contributing to the accident was the pilot's impairment from the combined effects of butalbital and codeine.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR15FA195
Event ID
20150622X64755
Case number
WPR15FA195
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: f41c1c43ab0ab3b3109fb8dc592f6b7f86e400628d3e17230afea5bcf642e4ed; retrieved 2026-09-14T19:31:17.135Z.