FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR24FA185 · Rans S-12XL Airaile

8 Jun 2024 · Picacho Peak, AZ, United States

Rans S-12XL Airaile · Accident: loss of control in flight while maneuvering

From La Cholla Airpark (57AZ) to an unrecorded destination

Report a problem

Event

NTSB case
WPR24FA185
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

Rans S-12XL Airaile

Aircraft type
Rans S-12
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
N518D
Operator
Unknown
Onboard fatalities
Unknown
Route
From La Cholla Airpark (57AZ), Tucson, AZTo not recorded
Aircraft age
About 22 years (built 2002)
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
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
Substantial

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Action/decision
  • Personnel issues › Task performance

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

NTSB narrative

The pilot departed and flew to the area of Picacho Peak State Park, Arizona. Witnesses hiking near the accident site reported that the airplane was flying “dangerously close to the mountain” and subsequently impacted it’s the north side, about 81 ft below the summit. Meteorological conditions near the accident site about the time of the accident indicated that the wind was likely from the southwest at about 10 knots, gusting to 15 knots at the surface. Additionally, a 50° windshear was present with minimal change in magnitude between 3,000 to 4,000 ft msl. The density altitude at the time of the accident was 5,590 ft. Cell phone video of a previous flight conducted by the accident pilot was provided by a pilot-rated passenger who flew with the pilot on several occasions. This person indicated that the recorded flight illustrated the pilot’s standard practice of “buzzing the hikers.” The video showed the pilot and passenger in the accident airplane, orbiting the peak in a clockwise manner. The pilot subsequently initiated a flight path from north to south while converging on the north side of the ridgeline and flying over the summit at a low altitude. Another pilot-rated passenger who had previously flown with the pilot reported that during their flight, the accident pilot mentioned his interest in flying low to the ground, allowing him to interact with people or spot wildlife. During their flight, the pilot descended lower than the pilot-rated passenger was comfortable with and the passenger subsequently asked the accident pilot to return to the airport. The flight path in the video footage showed the pilot operating the airplane on a flight track that converged with the ridgeline just above the summit. The pilot’s standard practice of flying at low altitude above the summit would have subjected the airplane to mechanical turbulence perpendicular to the airplane’s direction of flight. The mechanical turbulence encountered by the airplane while converging on the summit at low altitude likely resulted in the pilot’s loss of control, resulting in the airplane’s subsequent impact with terrain just below the summit. Toxicology testing indicated evidence of the pilot’s use of the sedating antihistamine diphenhydramine. The diphenhydramine level measured in postmortem cavity blood could not be reliably compared to reference ranges in living individuals but indicated a possibility that the pilot might have been experiencing related drowsiness or cognitive/psychomotor slowing at the time of the accident. The pilot also had heart disease and a documented history of obstructive sleep apnea. Overall, the medical and toxicological evidence in this case indicated an increased risk of medical impairment but did not establish that impairment contributed to the accident.

Probable cause

The pilot’s decision to conduct a low-altitude flight in mountainous terrain and his subsequent loss of airplane control after encountering mechanical turbulence, which resulted in an impact with the terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR24FA185
Event ID
20240608194418
Case number
WPR24FA185
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, cause areas. 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: 1556b59a42db7fd80b9d4a65f3f949ec8af86bdf6be16ab350780d2e1d00aa28; retrieved 2026-09-15T08:16:45.581Z.