The U.S. aircraft register, updated daily
Accidents · NTSB WPR26LA222 · Final report

Cessna 172S accident near Death Valley, California, June 17, 2026

On June 17, 2026 at about 5:30 pm local time, a 2005 Cessna 172S, registered N96FA, was substantially damaged in an accident during landing (landing roll) near Death Valley, California (Furnace Creek Airport). It was a personal flight under general aviation rules (Part 91). 3 people had minor injuries. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot’s failure to maintain airspeed and encounter with a tailwind while landing on a rough runway, which resulted in a runway overrun and subsequent nose over.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
June 17, 2026 · about 5:30 pm local time
Place
Death Valley, California · Furnace Creek Airport · map
Type
Accident
Injuries
3 people had minor injuries.
Weather
visual conditions (good weather)
Aircraft
Cessna 172S, built 2005 · all 172Ss on the register
Registration
N96FA · registry record · serial 172S10002
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

The pilot flew over his destination airport, which featured a 3,065 ft long asphalt runway, noted to be in poor condition, to observe the windsock. The pilot determined that the windsock indicated calm wind and maneuvered the airplane for landing on runway 33. He extended the flaps to the full down position while on final approach. The pilot stated that the airplane touched down about 1,300 ft beyond the runway threshold, and that he applied maximum braking. During the landing roll, he realized that the airplane was not slowing down as he expected. The airplane subsequently overran the runway and nosed over, which resulted in substantial damage to both wing lift struts and the fuselage. The pilot added that a stronger-than-anticipated tailwind and the rough, uneven runway surface may have reduced braking effectiveness. Flight data recovered from the airplane’s avionics revealed that the airplane landed on runway 33 with wind from about 174° at 17 knots. Additionally, the data revealed that as the airplane crossed over the threshold of the runway, the airplane’s indicated airspeed was about 74 knots and groundspeed about 93 knots. The Pilot’s Operating Handbook specifies that, during a short-field landing, the airplane should be flown at 61 knots indicated airspeed when 50 ft above ground level. It further stated that, “for operation with tailwinds up to 10 knots, increase [landing] distances by 10% for each 2 knots.” Post accident examination of the airplane revealed that there were now mechanical malfunctions or failures with the wing flaps that would have precluded normal operation.

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

  1. Nose over/nose down during landing (landing roll)
  2. Runway excursion during landing (landing roll) defining event
  3. Other weather encounter during landing (flare/touchdown)

The NTSB's findings

  • Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Surface speed/braking › Not attained/maintained
  • Environmental issues › Conditions/weather/phenomena › Wind › Tailwind › Awareness of condition
  • Personnel issues › Action/decision › Info processing/decision › Identification/recognition › Pilot
  • Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Airspeed › Not attained/maintained
  • Environmental issues › Physical environment › Terrain › Rough terrain › Contributed to outcome
  • Environmental issues › Conditions/weather/phenomena › Wind › Tailwind › Effect on operation

Pilot

  • Certificate: foreign licence, private
  • Ratings: single-engine land
  • Flight time: 200 hours in all; 75 in this make and model; 200 as pilot in command
  • Last flight review: June 16, 2026
  • Medical certificate: Class 2 (without waivers/limitations)
  • Seat: left
  • Injury: unkn

Passenger

  • Seat: rgt
  • Injury: minor injuries

Passenger

  • Seat: rear
  • Injury: minor injuries

The aircraft

  • Airframe total time: 8,057.3 hours
  • Last inspection: annual inspection, May 28, 2026; 37.7 hours since
  • Maximum gross weight: 2,550 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming IO-360-L2A (piston); 8,057 hours total

The flight

  • Departed from: VNY Van Nuys CA at 2:51 pm
  • Flight plan: VFR
  • Runway 33, 3,065 ft by 70 ft

Weather at the time

  • Light: daylight
  • Wind: from 200° at 13 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 93°F (34°C), dew point 37°F (3°C)
  • Altimeter: 29.89 inHg
  • Observation at 10:00 am from KDRA, 42 miles away

Weather report (METAR): METAR KDRA 171653Z AUTO 20013KT 10SM CLR 34/03 A2989 RMK AO2 SLP062 T03390028

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers2

Photographs from the investigation 3 pictures from the NTSB's docket, as the NTSB released them

The NTSB's photographs with the NTSB's captions, at screen size. Open a picture to see it full size or to report one that should not be shown.

Documents from the investigation the NTSB's docket: the evidence folder behind the report

8 documents, released by the NTSB on September 17, 2026. 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.