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

Piper PA-30 accident near Watkins, Colorado, September 28, 1996

On September 28, 1996 at about 11:35 am local time, a Piper PA-30, registered N37P, was substantially damaged in an accident near Watkins, Colorado (Front Range airport). It was a personal flight under general aviation rules (Part 91). 2 people had minor injuries; 1 other was unhurt. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

the pilot-in-command's failure to use proper procedures and engage the turbochargers for takeoff from a high altitude airport. A factor was the high density altitude.

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

What the record shows

Date
September 28, 1996 · about 11:35 am local time
Place
Watkins, Colorado · Front Range · map
Type
Accident
Injuries
2 people had minor injuries; 1 other was unhurt.
Weather
visual conditions (good weather)
Aircraft
Piper PA-30 · all PA-30s on the register
Registration
N37P · registry record · serial 30-1457
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

While taking off on a cross-country flight, the aircraft became airborne but would neither climb nor accelerate. The aircraft weight was 3,670 pounds, which was approximately 100 pounds below maximum. The density altitude was 6,000 feet msl. The aircraft was equipped with manual turbochargers which were not being used. According to the operating instruction for the aircraft, the turbochargers should be used for high altitude takeoff to obtain the desired manifold pressure of 29.5 inches at 2,700 rpm. The engines were capable of producing only 23.5 inches of manifold pressure without the turbochargers engaged and this power was insufficient for climb at the weight and speed used.

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

Pilot

  • Certificate: commercial pilot
  • Ratings: multi-engine land; single-engine land; instrument: airplane
  • Flight time: 345 hours in all; 36 in this make and model; 15 in the last 90 days; 2 in the last 30 days; 278 as pilot in command
  • Medical certificate: Class 2 (valid medical--w/ waivers/lim.)
  • Seat: left

The aircraft

  • Airframe total time: 5,607 hours
  • Last inspection: annual inspection, March 10, 1996; 141 hours since
  • Maximum gross weight: 3,725 lb
  • Seats: 4
  • Landing gear: retractable
  • Engine: Lycoming IO-320-B1A (piston); 0 hours total
  • Fire on the ground

The flight

  • Departed from: FTG CO at 11:35 am
  • Destination: O61 Sacramento CA
  • Flight plan: none
  • Runway 26, 8,000 ft by 100 ft

Weather at the time

  • Light: night, bright
  • Wind: from 210° at 12 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 45°F (7°C), dew point 34°F (1°C)
  • Altimeter: 30.00 inHg
  • Observation at 11:53 am from FTG, 2 miles away

Injuries

FatalSeriousMinorNone
Crew11
Passengers1

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

The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.

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 never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.