Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

May 25, 1998 · Piper PA-32-300 · N43108

Hanover, PA

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
May 25, 1998
Injury Outcomes
No injuries (1 uninjured)
Location
Hanover, PA
Aircraft
Piper PA-32-300
Tail Number
N43108
Operator
Kenneth H Bernstein
Injuries
None
Aircraft Damage
Substantial
NTSB Number
NYC98LA119

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.

NTSB Probable Cause

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.

Full Narrative

On May 25, 1998, about 1950 Eastern Daylight Time, a Piper PA-32-300, N43108, was substantially damaged during landing at Hanover Airport (6W6), Hanover, Pennsylvania. The certificated private pilot was not injured. Visual meteorological conditions prevailed at the time of the accident. No flight plan had been filed for the flight between Williamsport Regional Airport (IPT), Williamsport, Pennsylvania and Potomac Airfield (VKX), Friendly, Maryland. The personal flight was conducted under 14 CFR Part 91. According to the pilot's written statement, he diverted to Hanover Airport due to impending darkness, concerns for weather along the route of flight, and an "already long, frustrating, and somewhat tiring day." Hanover was determined to be the nearest airport by utilizing a GPS database. The pilot called on the Unicom frequency, and received a response that the "direction of the active" was Runway 27. The pilot entered a downwind and flew a "normal approach." Then, about 3 feet off the ground on final approach, the "gear apparently struck a dirt pile on the approach end of the runway." The airplane touched down, initially maintained forward directional control, then veered to the left. It came to rest in a wheat field with a collapsed left main landing gear and substantial left wing damage. Post flight inspection revealed that the pilot had not landed on the published runway. The actual turf runway was parallel to, and to the right of the surface the pilot had landed on. According to the airport owner, the area the pilot landed on was a runway under construction, and there were no runway markings on it. He also said the ground-based Unicom was not operating when the accident occurred because no one was at the airport at that time. The pilot wrote: "In retrospect, I think my judgement was clouded by fatigue, since I invariably plan more and better." He also wrote: "Importantly, there was [also] no "X" or other markings indicating the hard surfaced runway was closed - nor was there any lighting on the immediately adjacent turf runway or elsewhere. Since only the closed runway was visible and it matched the direction and location of the adjoining turf runway, and there [was] no visible warning that it was closed, it is difficult to imagine a more misleading and confusing set-up." According to the Airport/Facility Directory, Northeast U.S., effective April 23, 1998, the airport was attended until 1900 Eastern Daylight Time. Runway 27 was marked with barrels, tires and cones; tires were painted yellow, and orange cones marked the south side of the runway. The Directory also stated that there was an "elevated runway fill area" south of the runway, and that night flying was not allowed.

Flight

Event TypeAccident
Event Time19:50 EDT
Nearest AirportHANOVER (0nm)
Runway27
Runway Length2700 ft
Runway Width140 ft
Flight Plan FiledNone
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftPiper PA-32-300
Tail NumberN43108
Aircraft CategoryAir
DamageSubstantial
OperatorKenneth H Bernstein
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · IO-540-K1A5 · Reciprocating · 300
Seats6

People & Injuries

Injury SummaryNo injuries (1 uninjured)
Fatal0
Serious0
Minor0
Uninjured1
Total1
Crew 1Age 51 · Third Class

Conditions

ConditionsVMC
LightDusk
Wind290° @ 11 kt, gusting 19 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point57
Altimeter29.00 inHg
Observation Time23:45
Weather SourceWFAC

Appendix: Source Data