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

Piper PA-25-235 accident near Boulder, Colorado, May 28, 2014

On May 28, 2014 at about 9:00 pm local time, a 1971 Piper PA-25-235, registered N8808L, was substantially damaged in an accident during enroute (descent) near Boulder, Colorado (Boulder Municipal Airport). It was a glider-towing flight under general aviation rules (Part 91). 1 person had minor injuries. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot's failure to adequately monitor the airplane's actual fuel consumption rate, which resulted in a total loss of engine power due to fuel exhaustion.

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

What the record shows

Date
May 28, 2014 · about 9:00 pm local time · cases in 2014
Place
Boulder, Colorado · Boulder Municipal Airport · cases near this airport · map
Type
Accident
Injuries
1 person had minor injuries.
Weather
visual conditions (good weather)
Aircraft
Piper PA-25-235, built 1971 · all PA-25-235s on the register
Registration
N8808L · no longer on the register · serial 25-5306
Damage
Substantial damage
Flight
Glider-towing flight · general aviation rules (Part 91)

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

The pilot reported that the accident occurred during his fifth glider aero-tow flight since the airplane had last been refueled. He stated that the aero-tow and glider release were uneventful. However, as he was returning to the departure airport, the engine began to run intermittently before it eventually experienced a total loss of engine power. During the subsequent forced landing, the airplane became entangled with a chain-link fence and impacted a road before it slid into a drainage ditch. A postaccident examination of the airplane's single fuel tank established that it was undamaged and void of any usable fuel. Before the first flight of the day, the airplane was refueled, and the total usable fuel was about 32.5 gallons. The airplane recording tachometer indicated that 2.2 tachometer hours had been accumulated since that time. Although the airplane operator reported that, according to historical fueling and flight data, the airplane's average fuel consumption rate was about 10.2 gallons per tachometer hour, the calculated average fuel consumption rate was 14.8 gallons per tachometer hour since the last refueling. Although the total loss of engine power was caused by fuel exhaustion, the investigation could not determine the reason for the above-normal fuel consumption rate. However, if the pilot had determined the actual fuel consumption rate between flights, he should have identified that insufficient fuel was available to complete the accident flight.

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 (descent) defining event
  2. Loss of engine power (total) during enroute (descent)
  3. Off-field or emergency landing during landing
  4. Collision with terrain or object (not controlled flight into terrain) during landing

The NTSB's findings

  • cause Aircraft › Fluids/misc hardware › Fluids › Fuel › Related operating info other cases naming the fuel system
  • cause Aircraft › Fluids/misc hardware › Fluids › Fuel › Fluid level other cases naming the fuel system
  • cause Personnel issues › Task performance › Planning/preparation › Fuel planning › Pilot
  • cause Personnel issues › Action/decision › Info processing/decision › Identification/recognition › Pilot

Pilot

  • Certificate: commercial pilot
  • Ratings: single-engine land
  • Flight time: 926 hours in all; 19 in this make and model; 10 in the last 90 days; 7 in the last 30 days; 888 as pilot in command
  • Last flight review: July 6, 2013
  • Medical certificate: Class 2 (without waivers/limitations)
  • Seat: sngl
  • Injury: minor injuries

The aircraft

  • Airframe total time: 8,847.3 hours
  • Last inspection: annual inspection, April 24, 2014
  • Maximum gross weight: 2,299 lb
  • Seats: 1
  • Landing gear: fixed
  • Engine: Lycoming O-540-B2C5 (piston); 3,609 hours total
  • Operator: Soaring Society of Boulder Inc.

The flight

  • Departed from: BDU Boulder CO at 8:30 pm
  • Destination: BDU Boulder CO
  • Flight plan: none
  • Runway 08, 4,100 ft by 75 ft

Weather at the time

  • Light: daylight
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 86°F (30°C), dew point 41°F (5°C)
  • Altimeter: 30.10 inHg
  • Observation at 8:56 pm from BDU, 1 miles away

Injuries

FatalSeriousMinorNone
Flight crew1

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

4 documents, released by the NTSB on October 2, 2014. 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.

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

1995-07-31SEA95LA168 · accident near Shelley, ID · substantial damage · minor injuries

Connections how this case links to the rest of the register

Aircraft
Place
Record

The whole map of how records connect · these connections as data: /graph/accident/CEN14LA261.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.