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

Piper PA-32-300 accident near Hanover, Pennsylvania, May 25, 1998

On May 25, 1998 at about 11:50 pm local time, a Piper PA-32-300, registered N43108, was substantially damaged in an accident near Hanover, Pennsylvania (Hanover airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

failure of the pilot to obtain current information for the divert airfield, and his selection of an unsuitable area for landing. Related factors included: the lower ambient light conditions at dusk, construction on the airfield, and an over-reliance on the limited information provided by the GPS database.

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

What the record shows

Date
May 25, 1998 · about 11:50 pm local time
Place
Hanover, Pennsylvania · Hanover · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Piper PA-32-300 · all PA-32-300s on the register
Registration
N43108 · registry record · serial 32-7440116
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

With dusk approaching, the pilot decided to divert to an alternate airport. Information about the airport and its position was found on a GPS database. After making an approach to land, while approximately 3 feet off the ground, the airplane hit a pile of dirt, touched down, and then veered into a wheat field. Postflight inspection revealed the airplane had not landed on the airport's turf runway, but instead had landed on a parallel, 'elevated fill' runway under construction. Runway and construction information was available in the Airport/Facility Directory.

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: 2,487 hours in all; 1,663 in this make and model; 26 in the last 90 days; 11 in the last 30 days; 2,437 as pilot in command
  • Medical certificate: Class 3 (valid medical--no waivers/lim.)
  • Seat: left

The aircraft

  • Airframe total time: 3,671 hours
  • Last inspection: annual inspection, July 10, 1997; 149 hours since
  • Maximum gross weight: 3,400 lb
  • Seats: 6
  • Landing gear: fixed
  • Engine: Lycoming IO-540-K1A5 (piston); 0 hours total

The flight

  • Departed from: IPT Williamsport PA at 11:22 pm
  • Destination: VKX Friendly MD
  • Flight plan: none
  • Runway 27, 2,700 ft by 140 ft

Weather at the time

  • Light: dusk
  • Wind: from 290° at 11 knots, gusting 19
  • Visibility: 10 statute miles
  • Sky: scat at 6,000 ft
  • Temperature: 84°F (29°C), dew point 57°F (14°C)
  • Altimeter: 29.00 inHg
  • Observation at 11:45 pm from W54, 9 miles away

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.