ATL82DA193 · Piper PA-32-300
Piper PA-32-300 · Accident: overrun during landing
From Somerset, NJ to W93 · ORANGE COUNTY, VA
Event
- NTSB case
- ATL82DA193
- 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
- N4371X
- Operator
- A. Grah Schneider
- Onboard fatalities
- Unknown
- Route
- From Somerset, NJTo W93 · ORANGE COUNTY, VA
- 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
- Landing · landing roll
- 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
- Overrun
- 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 › Distance, misjudged
- Pilot in command › Go-around, not performed
- Pilot in command › Wrong runway, selected
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
WHILE ON A CROSS-COUNTRY FLIGHT, THE PILOT ELECTED TO MAKE AN UNSCHEDULED STOP AT A UNFAMILIAR AIRPORT TO CHECK THE EN ROUTE WEATHER. HE CIRCLED THE AIRPORT AND THOUGHT THE WIND INDICATED FAVORED RUNWAY 31, BUT LATER, HE FOUND THAT THE WIND WAS CALM. NO RESPONSE WAS RECEIVED WHEN HE ATTEMPTED TO CONTACT THE AIRPORT UNICOM. RUNWAY 31 SLOPED DOWNHILL AND HAD A 280 FT DISPLACED THRESHOLD. THE PILOT WAS UNAWARE THAT ONLY 1550 FT OF RUNWAY WAS AVAILABLE SINCE HIS SECTIONAL CHART INDICATED THAT IT WAS 1800 FT LONG. ALSO, HE WAS UNAWARE THAT MOST PILOTS USED RUNWAY 13 WHEN POSSIBLE TO AVOID THE DOWNSLOPE ON RUNWAY 31. DURING THE LANDING, HE TOUCHED DOWN NEAR MIDFIELD. HE RECOGNIZED THEN THAT THERE MIGHT NOT HAVE BEEN SUFFICIENT RUNWAY TO STOP, BUT RAISED THE FLAPS AND BRAKED HARD, RATHER THEN GO AROUND, BECAUSE OF TREES BEYOND THE END OF THE RUNWAY. DESPITE HEAVY BRAKING, THE AIRCRAFT CONTINUED OFF THE END OF THE RUNWAY AND COLLIDED WITH A DITCH.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record ATL82DA193
- Event ID
- 20020917X02776
- Case number
- ATL82DA193
- 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: bcd68eb47724aae35b1e6b36c98fb08a70dc7b8c2f4559cffcabaf2889e7577c; retrieved 2026-09-22T02:59:38.335Z.