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

Cessna T207A accident near Rock Springs, Wyoming, November 15, 2017

On November 15, 2017 at about 10:15 pm local time, a 1981 Cessna T207A, registered N9825M, was substantially damaged in an accident during landing near Rock Springs, Wyoming (Rock Springs-Sweetwater County airport). It was an aerial observation flight under public-use (government) rules. 2 people were seriously injured and 2 people had minor injuries. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot's improper in-flight fuel management and reliance on a faulty fuel gauge, which resulted in fuel starvation during approach for landing, and his failure to follow the emergency checklist after losing engine power.

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

What the record shows

Date
November 15, 2017 · about 10:15 pm local time · cases in 2017
Place
Rock Springs, Wyoming · Rock Springs-Sweetwater County · cases near this airport · map
Type
Accident
Injuries
2 people were seriously injured and 2 people had minor injuries.
Weather
visual conditions (good weather)
Aircraft
Cessna T207A, built 1981 · all T207As on the register
Registration
N9825M · no longer on the register · serial 20700739
Damage
Substantial damage
Flight
Aerial observation flight · public-use (government) rules

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

The public aircraft aerial survey flight with a commercial pilot and three survey crewmembers had a planned duration of 1 hour 45 minutes. The pilot stated that the airplane departed with full fuel in the left- and right-wing fuel tanks, which provided a usable fuel capacity of 36.5 gallons per tank. His fuel consumption calculations for the flight determined that a total of 27 gallons would be used for 1 hour 30 minutes of flight; he stated that he planned to use fuel from the left fuel tank for 1 hour 30 minutes and then switch to the right fuel tank. After 1 hour 30 minutes of flight time, when the airplane was 10 minutes from the destination, the pilot observed the left fuel gauge "rapidly shifting from full to 1/4." The pilot had observed similar indications before with the left gauge, as it was "often stuck at a full reading then flicked back and forth between full and the actual fuel level," on previous flights; he thought there was 1/4 tank of fuel remaining. He planned to switch to the right fuel tank when he entered the airport traffic pattern. When the airplane entered the base leg, the engine sputtered before the pilot switched fuel tanks. The pilot then selected the right fuel tank, pushed the throttle control full forward, and selected the auxiliary fuel pump to HI and then LOW; the engine continued to sputter. He did not follow the airplane manufacturer's emergency checklist for engine failure restart, which instructed to select the auxiliary fuel pump switch to ON, select the fuel tank containing fuel, position the throttle to half open, and then turn the auxiliary fuel pump switch off. Unable to restart the engine, the pilot chose a road for a forced landing. During his approach, the stall warning horn sounded periodically and the airspeed indicated 65 knots, which was below the recommended engine-out glide airspeed of 80 knots. The pilot lowered the airplane's nose to increase airspeed, and the airplane descended "rapidly." He was still unable to restart the windmilling engine. When the airplane was over the road, he fully extended the flaps and then veered the airplane right to land in the dirt next to the road to soften the landing. The airplane sustained substantial damage to the nose landing gear and fuselage. Postaccident examination of the airplane revealed that the left fuel tank contained no useable fuel, and the right tank contained full fuel. Further examination of the fuel system found that the left fuel quantity transmitter did not move smoothly from the upper stop to the lower stop and repeatedly stuck in place. There was no evidence of other preimpact engine or fuel system malfunctions or failures that would have precluded normal operation. Two of the survey crewmembers reported that they had witnessed a similar discrepancy with the left fuel gauge during flights 7 months before the accident. However, no writeups of the discrepancy were made. The airplane had annual and 50-hour inspections less than 1 month before the accident; the airplane service manual called for troubleshooting of the fuel gauges at these inspections. However, maintenance personnel were not aware of the discrepancy with the left fuel gauge and, therefore, did not troubleshoot it and identify that the transmitter needed replacement. Regardless, the pilot did not manage the fuel properly by switching fuel tanks when he planned and instead continuing toward his destination for another 10 minutes, relying on a faulty fuel gauge, which led to the fuel tank he was using becoming devoid of fuel, which led to fuel starvation. Further, once the airplane lost engine power, he did not follow the emergency checklist procedures for restoring power.

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. Aircraft maintenance event during prior to flight
  2. Flight instrument malf/fail during prior to flight
  3. Fuel starvation during approach (VFR pattern base)
  4. Attempted remediation/recovery during approach (VFR pattern base)
  5. Stall warn/stick-shaker/pusher during landing
  6. Hard landing during landing defining event
  7. Collision with terrain or object (not controlled flight into terrain) during landing

The NTSB's findings

  • cause Personnel issues › Action/decision › Action › Incorrect action performance › Pilot
  • cause Aircraft › Fluids/misc hardware › Fluids › Fuel › Fluid management other cases naming the fuel system
  • cause Aircraft › Aircraft systems › Fuel system › Fuel quantity indicator › Failure other cases naming the fuel system
  • cause Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot
  • cause Personnel issues › Task performance › Use of equip/info › Use of checklist › Pilot

Pilot

  • Certificate: commercial pilot
  • Ratings: single-engine land; instrument: airplane
  • Flight time: 2,386 hours in all; 1,116 in this make and model; 81 in the last 90 days; 33 in the last 30 days; 2,313 as pilot in command; 0 on instruments
  • Last flight review: September 21, 2017
  • Medical certificate: Class 2 (without waivers/limitations)
  • Seat: left
  • Injury: minor injuries

The aircraft

  • Last inspection: annual inspection, July 9, 2017
  • Maximum gross weight: 3,800 lb
  • Seats: 6
  • Landing gear: fixed
  • Engine: Continental TSIO-520-PcRc (piston); 4,047 hours total
  • Operator: Redtail Air, Inc

The flight

  • Departed from: BPI Big Piney WY at 8:20 pm
  • Destination: RKS Rock Springs WY

Weather at the time

  • Light: daylight
  • Wind: from 210° at 4 knots
  • Visibility: 10 statute miles
  • Sky: overcast at 11,000 ft; a few clouds at 8,500 ft
  • Temperature: 52°F (11°C), dew point 14°F (-10°C)
  • Altimeter: 30.02 inHg
  • Observation at 9:54 pm from RKS, 2 miles away

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers21

Photographs from the investigation 2 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

11 documents, released by the NTSB on August 9, 2019. 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.

Connections how this case links to the rest of the register

Aircraft
Place

The whole map of how records connect · these connections as data: /graph/accident/CEN18LA032.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

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 does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.