The U.S. aircraft register, updated daily · Carbon Free Flight by 2050
Accidents · NTSB WPR25LA217 · Preliminary: the investigation is not finished

Cessna TR182 accident near Tuba City, Arizona, July 17, 2025

On July 17, 2025 at about 9:47 pm local time, a 1979 Cessna TR182, registered N182KC, was substantially damaged in an accident during enroute near Tuba City, Arizona. It was a personal flight under general aviation rules (Part 91). 1 person had minor injuries; 1 other was unhurt. The weather was visual conditions (good weather).

Preview. This page is not yet listed for search engines.

The NTSB's probable cause their words, unchanged

The NTSB has not yet published a probable cause for this accident. Investigations usually take one to two years; this page updates when the final report is released.

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

What the record shows

Date
July 17, 2025 · about 9:47 pm local time
Place
Tuba City, Arizona · map
Type
Accident
Injuries
1 person had minor injuries; 1 other was unhurt.
Weather
visual conditions (good weather)
Aircraft
Cessna TR182, built 1979 · all TR182s on the register
Registration
N182KC · registry record · serial R18201139
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

On July 17, 2025, about 1447 mountain standard time, a Cessna TR182, N182KC, was substantially damaged when it was involved in an accident near Tuba City, Arizona. The pilot and passenger were not injured. The airplane was operated as a Title 14 Code of Federal Regulation Part 91 personal flight. The pilot reported that he departed with 62 gallons of fuel onboard and that he had verified the fuel quantity multiple times with a calibrated dipstick prior to departure. While enroute, and after switching to the right tank, which indicated about 31 gallons at the time, the engine began to run rough and sputter. He attempted to switch to BOTH fuel tanks, but the engine continued to sputter. The pilot activated the fuel boost pump, which displayed no fuel pressure at which time the engine lost all power. He executed a forced landing to the side of road to avoid vehicular traffic and with the landing gear stowed due to rough terrain. During landing the airplane belly contacted the ground, which substantially damaged the right wing and left elevator. Postaccident examination of the fuel tanks revealed that they were both empty; however, the pilot suspected a leak in the fuel delivery system. The airplane was recovered to a secure facility for further examination.

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. Fuel exhaustion during enroute defining event
  2. Collision during takeoff/land during landing (landing roll)

The aircraft

  • Airframe total time: 6,061.5 hours
  • Last inspection: annual inspection, December 20, 2024
  • Maximum gross weight: 3,112 lb
  • Seats: 4
  • Landing gear: retractable

The flight

  • Departed from: SNA Santa Ana CA at 6:55 pm
  • Destination: FMN Farmington NM
  • Flight plan: none

Weather at the time

  • Light: daylight
  • Wind: from 210° at 8 knots, gusting 16
  • Visibility: 10 statute miles
  • Sky: a few clouds at 11,000 ft
  • Temperature: 81°F (27°C), dew point 45°F (7°C)
  • Altimeter: 30.20 inHg
  • Observation at 12:53 pm from KRQE, 62 miles away

Weather report (METAR): METAR KRQE 171953Z AUTO 21008G16KT 160V260 10SM FEW110 27/07 A3020 RMK AO2 LTG DSNT SE AND W AND NW SLP096 T02720067=

Injuries

FatalSeriousMinorNone
Flig1
Passengers1

Other NTSB records under N182KC the same tail number, which may have belonged to a different aircraft at the time

2000-09-08CHI00LA292 · accident near Ellington, MO · substantial damage · minor injuries

About this page

Everything above comes from the NTSB's public accident database: the narrative, probable cause and findings are the NTSB's own words, and the coded tables behind its report (pilot, aircraft, flight, weather, injuries, sequence of events) are written out in plain English. Pilots' ages, home towns and medical details are left out on purpose. The docket at the NTSB holds the report as a PDF and the investigation's photographs and documents. This site never names pilots, passengers or anyone else involved. A preliminary report describes what is known soon after the event and can change; the final report, with the probable cause, usually follows one to two years later and this page is refreshed when it does. Case number WPR25LA217.