Grumman AA5 accident near Jackpot, Nevada, November 23, 2019
On November 23, 2019 at about 2:38 am local time, a Grumman AA5, registered N310PD, was destroyed in an accident during initial climb near Jackpot, Nevada (Jackpot/Hayden Fld airport). It was a personal flight under general aviation rules (Part 91). 2 people were killed. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot’s loss of control due to spatial disorientation while departing in dark night conditions, which resulted in impact with terrain. Contributing to the accident was the pilot’s limited experience flying in night conditions.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- November 23, 2019 · about 2:38 am local time
- Place
- Jackpot, Nevada · Jackpot/Hayden Fld · map
- Type
- Accident
- Injuries
- 2 people were killed.
- Weather
- visual conditions (good weather)
- Aircraft
- Grumman AA5 B
- Registration
- N310PD · no longer on the register · serial AA5B0399
- Damage
- Destroyed
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The noninstrument-rated pilot and passenger were departing on a cross-country flight in dark night visual meteorological conditions. A witness and onboard data indicated that the airplane lifted off the runway about midfield, initiated a left turn near the departure end of the runway, and impacted the ground seconds later. The accident site, which comprised a long debris field, suggested a high-velocity impact. Examination of the wreckage did not reveal evidence of any preimpact mechanical anomalies. The elevator trim was discovered in the full nose-down position, which would have resulted in the pilot experiencing significant resistance to his control inputs during a takeoff and climb. It is possible that the trim position having been misconfigured to before the takeoff could have served as a distraction that led to the development of spatial disorientation. It is also possible that the airplane’s pitch attitude led to the pilot manually adding nose down trim. Thus, there was insufficient evidence to determine the role of the nose-down trim in the sequence of events. Although the pilot’s logbooks were not recovered during the investigation, discussions with friends and family members suggested that he did not normally fly at night and had experienced only a few nighttime departures at the accident airport before the accident. GPS data from previous flights revealed that the pilot departed the same runway at night on two occasions before the accident; however, the moon was prominently illuminated during both of the previous flights. The area of the accident airport was sparsely populated, with little to no cultural lighting present in the direction of the accident takeoff. On the night of the accident, the pilot’s visual references were limited, as the moon was not visible above the horizon. The pilot entered a climbing left turn as customary shortly after takeoff, likely to avoid an obstacle beyond the runway. The moonlight on previous takeoffs would have reduced his reliance on runway lighting. Given the lack of visual references and the pilot’s lack of experience in night operations, it is likely that during the turn, the pilot experienced spatial disorientation, which resulted in an inadvertent descent, and subsequent impact with the terrain.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Loss of control in flight during initial climb defining event
- Collision with terrain or object (not controlled flight into terrain) during initial climb
The NTSB's findings
- Personnel issues › Psychological › Perception/orientation/illusion › Spatial disorientation › Pilot
- Environmental issues › Conditions/weather/phenomena › Light condition › Dark › Effect on operation
- Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
- Personnel issues › Experience/knowledge › Experience/qualifications › Recent experience › Pilot
- Aircraft › Aircraft oper/perf/capability › Performance/control parameters › (general) › Not attained/maintained
Pilot
- Certificate: commercial pilot
- Ratings: single-engine land; rotorcraft: glider
- Flight time: 2,700 hours in all
- Medical certificate: None
- Seat: unk
- Injury: fatal
Passenger
- Seat: unk
- Injury: fatal
The aircraft
- Airframe total time: 2,493 hours
- Last inspection: annual inspection, December 3, 2018
- Maximum gross weight: 2,401 lb
- Seats: 4
- Landing gear: fixed
- Engine: Lycoming O-360-A4A (piston); 6,480 hours total
- Fire on the ground
The flight
- Destination: RXE Rexburg ID
- Flight plan: none
- Runway 15/3, 6,183 ft by 60 ft
Weather at the time
- Light: night
- Wind: from 216° at 6 knots
- Sky: clear
- Temperature: 27°F (-3°C), dew point 19°F (-7°C)
- Altimeter: 30.00 inHg
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
22 documents, released by the NTSB on October 27, 2021. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
