NYC98LA119 · Piper PA-32-300
Piper PA-32-300 · Accident: in flight collision with terrain/water on approach
From Williamsport Regional Airport (IPT) to Potomac Airfield (VKX)
Event
- NTSB case
- NYC98LA119
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- 0
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Piper PA-32-300
- Aircraft type
- Piper PA-32
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N43108
- Operator
- Kenneth H. Bernstein · private individual
- Onboard fatalities
- Unknown
- Route
- From Williamsport Regional Airport (IPT), Williamsport, PATo Potomac Airfield (VKX), Friendly, MD
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Approach
- First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- In flight collision with terrain/water
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Pilot in command › Information, not obtained
- Pilot in command › Unsuitable terrain or takeoff/landing/taxi area, selected
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
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.
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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC98LA119
- Event ID
- 20001211X10183
- Case number
- NYC98LA119
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 0a29f32ef5dba58f7202283528c0ece04615fd00f5b3f928b0d5f6ff4aed9341; retrieved 2026-09-22T17:44:40.367Z.