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

Piper PA-28-151 accident near Danbury, Connecticut, January 7, 2004

On January 7, 2004 at about 4:30 pm local time, a Piper PA-28-151, registered N1558X, was substantially damaged in an accident near Danbury, Connecticut (Danbury Municipal Airport). It was a flight test under general aviation rules (Part 91). 1 person was seriously injured. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The loss of engine power for undetermined reasons, and the pilot's failure to maintain adequate airspeed.

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

What the record shows

Date
January 7, 2004 · about 4:30 pm local time
Place
Danbury, Connecticut · Danbury Municipal Airport · map
Type
Accident
Injuries
1 person was seriously injured.
Weather
visual conditions (good weather)
Aircraft
Piper PA-28-151 · all PA-28-151s on the register
Registration
N1558X · no longer on the register · serial 28-7515423
Damage
Substantial damage
Flight
Flight test · general aviation rules (Part 91)

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

During the takeoff climb, as the airplane approached the departure end of the runway, the pilot heard a "pop," the airplane began to shudder, and he felt a "decrease in aircraft performance." The pilot unsuccessfully attempted to evaluate the problem, and then at 400 feet, he initiated a turn back to the airport. During the turn, the airplane "stalled," impacted a tree, and a post-crash fire ensued. During the takeoff climb, witnesses observed a thin "puff" of smoke trailing from the airplane's exhaust, prior to the pilot initiating the turn back to the runway. On-scene examination of the airplane and engine did not reveal any mechanical deficiencies.

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: flight instructor, commercial pilot
  • Ratings: multi-engine land; single-engine land; instructor: airplane multi-engine; instructor: airplane single-engine; instructor: instrument airplane; instrument: airplane
  • Flight time: 1,454 hours in all; 177 in the last 90 days; 38 in the last 30 days; 1,427 as pilot in command; 1,067 on instruments
  • Last flight review: February 20, 2002
  • Medical certificate: Class 2 (valid medical--w/ waivers/lim.)
  • Seat: left
  • Injury: serious injuries

The aircraft

  • Airframe total time: 3,292.2 hours
  • Last inspection: annual inspection, September 13, 2003; 26 hours since
  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming O-320 (piston); 0 hours total
  • Fire on the ground

The flight

  • Departed from: DXR Danbury CT at 4:25 pm
  • Destination: DXR
  • Flight plan: none
  • Runway 26

Weather at the time

  • Light: daylight
  • Wind: from 300° at 13 knots, gusting 20
  • Visibility: 10 statute miles
  • Sky: overcast at 3,100 ft
  • Temperature: 19°F (-7°C), dew point 1°F (-17°C)
  • Altimeter: 30.12 inHg
  • Observation at 4:53 pm from DXR

Injuries

FatalSeriousMinorNone
Crew1

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.