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

Piper PA-28-140 accident near E. Stroudsburg, Pennsylvania, August 6, 2000

On August 6, 2000 at about 3:30 pm local time, a Piper PA-28-140, registered N5731U, was substantially damaged in an accident near E. Stroudsburg, Pennsylvania (Stroudsburg-Pocono airport). It was a personal flight under general aviation rules (Part 91). 3 people had minor injuries. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot's decision to takeoff with only partial engine power available.

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

What the record shows

Date
August 6, 2000 · about 3:30 pm local time
Place
E. Stroudsburg, Pennsylvania · Stroudsburg-Pocono · map
Type
Accident
Injuries
3 people had minor injuries.
Weather
visual conditions (good weather)
Aircraft
Piper PA-28-140 · all PA-28-140s on the register
Registration
N5731U · no longer on the register · serial 28-26547
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

The pilot taxied onto the runway and advanced the throttle. The engine responded, and rpm stabilized about 300 less than maximum. During the first takeoff attempt, the airplane was nose high, slow, and flying in ground effect. The pilot cut power and landed. The pilot then taxied for a second attempt. He advanced throttle for takeoff and when the airplane was about 1/3 of the way down the runway, it was nose high, slow, and flying in ground effect. About 2/3 of the way down the runway, it had reached an altitude of 10-15 feet. At this point, the airplane was still nose-high, slow, and had developed a pitch oscillation. The airplane continued past the runway, and impacted the ground. According to the pilot, during both takeoff attempts, the engine ran smoothly, but only developed 2,400 RPM. Takeoff engine RPM was listed to be 2,700.

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
  • Flight time: 148 hours in all; 147 in this make and model; 34 in the last 90 days; 3 in the last 30 days; 34 as pilot in command
  • Medical certificate: Class 3 (valid medical--w/ waivers/lim.)
  • Seat: left

The aircraft

  • Airframe total time: 5,806 hours
  • Last inspection: annual inspection, November 20, 1999; 58 hours since
  • Maximum gross weight: 2,150 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming O-320-E3D (piston); 0 hours total

The flight

  • Departed from: N53 at 3:30 pm
  • Destination: 22B Burlington CT
  • Flight plan: none
  • Runway 8, 3,087 ft by 30 ft

Weather at the time

  • Light: daylight
  • Wind: from 200° at 8 knots
  • Visibility: 8 statute miles
  • Sky: scat at 3,400 ft
  • Temperature: 63°F (17°C), dew point 61°F (16°C)
  • Altimeter: 30.00 inHg
  • Observation at 3:56 pm from MPO, 13 miles away

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.

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.