13 Oct 2015: CESSNA T210K — SP Aircraft

13 Oct 2015: CESSNA T210K (N8273M) — SP Aircraft

No fatalities • Boise, ID, United States

Probable cause

The pilot’s improper in-flight fuel management due to distraction and self-induced pressure, which resulted in fuel starvation and a total loss of engine power. Contributing to the accident was the pilot’s failure to conduct the descent checklist, which included a task to manage fuel.

— NTSB Determination

Accident narrative

On October 13, 2015, about 0700 mountain daylight time, a Cessna T210K airplane, N8273M, was substantially damaged during a forced landing attempt near Boise Air Terminal (BOI), Boise, Idaho. The airplane was registered to a private individual and operated by SP Aircraft under the provisions of Title 14 Code of Federal Regulations Part 135. The commercial pilot and sole occupant of the airplane was not injured. Night visual meteorological conditions prevailed and no flight plan was filed for the non-scheduled cargo, cross country flight that departed Spokane International Airport (GEG), Spokane, Washington at 0422 Pacific daylight time and was destined for BOI.

According to the pilot's statement, he departed GEG on a time-sensitive flight with about 30 gallons of fuel in each wing fuel tank. During the flight the pilot became preoccupied with some paperwork in the cockpit and "failed to switch tanks" as he had planned at the halfway point. About 2 miles from BOI and approximately 650 feet above ground level, the engine "surged" and subsequently lost power. The pilot advanced the mixture, propeller, and throttle controls to their full forward positions and engaged the fuel boost pump, but was unable to regain engine power. He did not verify the fuel selector position or attempt an engine restart. He quickly evaluated the possible landing sites and decided to land on the lighted interstate adjacent to the airport. The airplane was "a few hundred" feet above the ground when the pilot attempted to lower the landing gear, but "the landing gear didn't have enough time to extend." The airplane touched down on its belly and came to rest near the shoulder of the interstate. In his written statement, the pilot remarked that the engine failure could also have been prevented "by using the checklist provided in the aircraft during descent", which includes the task "manage fuel." During a follow-up telephone conversation, the pilot stated that he was distracted during the descent phase of the flight and failed to use the checklist.

The pilot reported no mechanical malfunctions or anomalies that could have precluded normal operation with the exception of the landing gear, which failed to extend during the approach. He attributed the landing gear failure to the loss of engine power, but was not able to verify this assumption.

Postaccident examination of the airplane by a Federal Aviation Administration (FAA) inspector revealed substantial damage to the left aileron. The FAA inspector recorded 22 gallons in the left tank and observed no evidence of fuel in the right tank. According to photographs taken at the accident site by FAA, the landing gear and doors were in the retracted position and the landing gear position handle was in the neutral position. The inspector also verified fuel system continuity and functionality for both fuel boost pumps. An airframe and powerplant mechanic tested the landing gear under the supervision of the FAA, which revealed no anomalies as all three landing gear extended to their respective down and locked positions.

According to the aircraft manufacturer, the retractable tricycle landing gear is operated by hydraulic actuators and powered by an engine-driven hydraulic pump. To cycle the landing gear to the up or down position, the landing gear handle must be pulled out, moved to the respective position and released. Pressure from the engine-driven hydraulic pump will then actuate the gear into the selected position. The landing gear handle will be held in place by a detent until the cycle is completed; then the handle will automatically return to the neutral position.

Contributing factors

  • cause Fluid management
  • cause Pilot
  • cause Fluid level
  • factor Pilot
  • cause Pilot
  • cause Pilot

Conditions

Weather
VMC, wind 210/04kt, vis 3sm

Loading the flight search…

What you can do on Flight Finder

  • Search flights between any two airports with live fares.
  • By aircraft — pick a plane model (e.g. Boeing 787, Airbus A350) and see every route it flies from your origin.
  • Route map — click any airport worldwide to explore its destinations, or draw a radius to find nearby airports.
  • Global aviation safety — aviation accident database, 5,200+ records since 1980, with map and rankings by aircraft and operator.
  • NTSB safety feed — recent U.S. aviation accidents and incidents from the official NTSB CAROL database, updated daily.

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.