NTSB CAROL · Event
Event SEA03LA117
Aircraft involved
Probable cause & findings
The pilot's inadequate inflight decision by failing to refuel while en route, resulting in fuel exhaustion and the loss of power. A factor contributing to the accident was the unsuitable terrain for the forced landing.
Factual narrative
On June 22, 2003, approximately 1500 mountain daylight time, a Cessna T337D, N86182, was substantially damaged during a forced landing following a total loss of engine power while descending near Driggs, Idaho. The airplane was registered to and operated by the pilot. The private pilot and his sole passenger were not injured. Visual meteorological conditions prevailed for the 14 CFR Part 91 personal cross-country flight, and a flight plan was not filed. The flight originated from the Johnson Creek Airport (3U2), Yellow Pine, Idaho, at 1400, and was en route to the Driggs-Reed Memorial Airport (U59), Driggs, Idaho. According to the Pilot/Operator Aircraft Accident Report (NTSB Form 6120.1/2), the pilot reported that after departing 3U2 and climbing to 13,500 feet mean sea level (MSL), his intention was to check weather to the east and refuel in either Challis (LLJ) or Salmon (SMN), Idaho. The pilot stated that the distance to his destination, U59, was 201 nautical miles and estimated that he had 2 hours of fuel in the main tanks at the time of takeoff. After approximately .2 hours (12 minutes) the pilot related that the Global Positioning System (GPS) was indicating a groundspeed of 190 knots, with U59 only 59 minutes away. The pilot stated, "Assuming (incorrectly, as it turned out!) that we had near 1 3/4 hours of fuel remaining, I deleted LLJ from our GPS fight plan and decided to proceed direct to Driggs. We continued to achieve groundspeeds of 180 knots to 190 knots throughout the flight. Approximately 80 nautical miles from U59 the pilot began a slow descent to 8,000 feet MSL. Approximately 60 nautical miles northwest of U59, the pilot mentioned to his passenger that the right main fuel gauge seemed to be reading lower than usual. The pilot then switched the rear engine (normally feed off the right main and right aux tanks) over to the right aux tank. Two to three minutes later the engine [rear engine] started to "cough", prompting the pilot to switch it back over to the right main tank. The pilot reported that about 20 nautical miles from U59 the front engine began to fail from lack of fuel. "Knowing there was little fuel in the left aux tank, I tried to crossfeed the front engine to the right main tank while the engine was still coughing. I was unable to keep the engine running, so I feathered the front propeller and proceeded direct to U59 while maintaining 7,500 feet MSL." The pilot said he was about to make a radio call on the airport's Unicom frequency when the rear engine began to fail from lack of fuel. "I feathered the rear engine while there was still oil pressure, retracted the flaps I had put out for the descent, reduced airspeed to about 115 miles per hour, and began looking for a forced landing site. The pilot stated that at 7,000 feet MSL he turned toward the south, into the wind, looking for north/south roadways while the right seat passenger began to manually pump the gear down. With only the gear doors open and deciding that there was no suitable road within gliding range, the pilot elected to make a wheels up landing in a field. The pilot reported the airplane touched down "fairly hard and fast" due to having only 1/3 flaps on. After slowing, the airplane spun 90 degrees to the left and began sliding sideways before coming to a stop in an upright position. Both the pilot and his passenger exited the airplane uninjured. There was no post-impact fire. An FAA inspector, who traveled to the aircraft recovery site, reported the aircraft had sustained substantial damage to the lower fuselage frame where both wing struts are attached, as well as to the bottom of the fuselage. The right wing tip and the forward wheel well area were also damaged. In the Recommendation section of the NTSB Form 6120.1/2, the pilot reported, "Accident was caused by faulty fuel planning. Inadequate allowance for fuel consumed during startup, warm-up, taxi, and initial departure. Avoid by dipping tanks prior to every flight." The pilot calculated the distance to his destination at 201 nautical miles and estimated that he had 2 hours of fuel in the main tanks at the time of takeoff. Twelve minutes into the flight and leveling off at 13,500 feet MSL, the Global Positioning System was indicating a groundspeed of 190 knots, with the destination airport 59 minutes away. The pilot assumed he had close to 1 3/4 hours of fuel remaining, and elected to proceed directly to his destination rather than to stop and refuel. 80 nautical miles from the destination airport the pilot began a descent out of 8,000 feet MSL, and 60 nautical miles northwest of the airport he mentioned to his passenger that the right main fuel gauge, which feeds the rear engine, seemed to be reading lower than usual. The pilot switched over to the right aux tank, but two to three minutes later the rear engine started to cough. The pilot then switched back to the right main tank. Approximately 20 nautical miles from the destination airport the front engine began to fail from lack of fuel. The pilot attempted to crossfeed the front engine to the right main tank as the engine was starting to quit. Unable to keep the front engine running, the pilot feathered the front propeller. As the pilot was about to make a radio call on the airport's Unicom frequency, the rear engine began to fail from lack of fuel. The pilot feathered the rear propeller, retracted the flaps, reduced airspeed, and began looking for a forced landing site. The right seat passenger began to manually pump the gear down, but deciding that there was no suitable road within gliding range, the pilot elected to make a wheels up landing in a field. Touching down fairly hard and fast, the airplane spun 90 degrees to the left and began sliding sideways before coming to a stop in an upright position. There was no post-impact fire and neither the pilot or passenger sustained injury. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2003_SEA03LA117.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (fuel exhaustion). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- AOPA Air Safety Institute 2023 · Safety advisor
Safety Advisor: Fuel Awareness
AOPA Air Safety Institute safety advisor on preventing fuel-exhaustion and fuel-starvation accidents in general aviation. Covers pre-flight fuel planning, reserve requirements (14 CFR 91.151, 91.167),…
- NASA NTRS 2019 · Abstract
U.S. Civil Rotorcraft Accidents, 1963 through 1997
The U.S. National Transportation Safety Board (NTSB) has recorded 8,436 rotorcraft accidents during the period mid - 1963 through the end of 1997.
- NASA NTRS 2019 · Contractor Report (CR)
A study of carburetor/induction system icing in general aviation accidents
An assessment of the frequency and severity of carburetor/induction icing in general-aviation accidents was performed. The available literature and accident data from the National Transportation Safet…
- NASA NTRS 2018 · Other
Parachuting to Safety
NASA's Langley Research Center awarded Ballistic Recovery Systems, Inc., three Small Business Innovation Research (SBIR) contracts to research and develop a new, low cost, lightweight recovery system …
Browse the full corpus — academia portal ↗