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

Piper PA-46-310P accident near Englewood, Colorado, July 6, 2003

On July 6, 2003 at about 4:52 pm local time, a Piper PA-46-310P, registered N4386G, was substantially damaged in an accident near Englewood, Colorado (Centennial airport). It was a business flight under general aviation rules (Part 91). No one was hurt; 3 people were on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

the pilot's improper flare which resulted in a hard landing. Contributing factors were the out-of-calibration waste gate actuator, a blown tire, and the airport sign.

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

What the record shows

Date
July 6, 2003 · about 4:52 pm local time
Place
Englewood, Colorado · Centennial · map
Type
Accident
Injuries
No one was hurt; 3 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Piper PA-46-310P · all PA-46-310Ps on the register
Registration
N4386G · no longer on the register · serial 46-8508037
Damage
Substantial damage
Flight
Business flight · general aviation rules (Part 91)

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

The pilot was cleared for takeoff and was instructed to maintain runway heading. The pilot said he aborted the takeoff after lifting off "due to poor airplane performance" and "landed very hard." The left main tire blew out and the airplane departed the left side of the runway and struck a taxiway sign. The engine was later functionally tested. Manifold pressure was found to be "3 [inches] low at full takeoff power," and the engine was producing "approximately 95-97 [per cent] full power at the takeoff setting." An adjustment to the wastegate actuator raised the manifold pressure to the correct setting.

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: private
  • Ratings: single-engine land; instrument: airplane
  • Flight time: 1,883 hours in all; 252 in this make and model; 75 in the last 90 days; 50 in the last 30 days; 1,883 as pilot in command
  • Last flight review: June 26, 2003
  • Medical certificate: Class 3 (valid medical--w/ waivers/lim.)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 1,711 hours
  • Last inspection: annual inspection, February 17, 2003; 96 hours since
  • Maximum gross weight: 4,100 lb
  • Seats: 6
  • Landing gear: fixed
  • Engine: Continental TSIO-520 (piston); 0 hours total

The flight

  • Departed from: APA Englewood CO at 4:52 pm
  • Destination: ANE Minneapolis MN
  • Flight plan: IFR
  • Runway 17L, 12,000 ft by 150 ft

Weather at the time

  • Light: daylight
  • Wind: from 080° at 8 knots
  • Visibility: 10 statute miles
  • Sky: a few clouds at 8,000 ft
  • Temperature: 86°F (30°C), dew point 34°F (1°C)
  • Altimeter: 30.03 inHg
  • Observation at 10:53 pm from APA

Injuries

FatalSeriousMinorNone
Crew1
Passengers2

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.

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

2005-07-04CHI05FA162 · accident near Grand Rapids, MN · destroyed · fatal

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.