ATL82DA130 · Piper PA-28-161
Piper PA-28-161 · Accident: overrun during landing
From Frederick, MD to Mitchellville, MD
Event
- NTSB case
- ATL82DA130
- 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-28-161
- Aircraft type
- Piper PA-28
- 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
- N3563W
- Operator
- Marvin Renich
- Onboard fatalities
- Unknown
- Route
- From Frederick, MDTo Mitchellville, 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
- 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 › Airspeed, misjudged
- Pilot in command › Distance, misjudged
- Pilot in command › Go-around, not performed
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT TOOK OFF ON A DARK NIGHT TO AN AIRPORT THAT HE HAD NEVER LANDED AT BEFORE. WHILE EN ROUTE, HE BECAME DISORIENTED AND CALLED A FLIGHT SERVICE STATION FOR HELP. A MILITARY HELICOPTER PILOT RENDEZVOUSED WITH THE LOST PILOT AND PROVIDED VECTORS TO THE DESTINATION. POWER LINES WERE LOCATED NORTH OF THE AIRPORT. MOST OF THE PILOTS THAT WERE FAMILIAR WITH THE AIRPORT PLANNED THEIR APPROACHES TO GO INSIDE THE POWER LINES. HOWEVER, THE PILOT OF N3563W APPROACHED OVER THE LINES WHICH NECESSITATED A HIGH PATTERN. ALSO, THE PILOT STATED THAT AFTER HIS EN ROUTE EXPERIENCE, HE FORGOT TO LOWER HIS FLAPS. WHILE LANDING, HE FLOATED AND TOUCHED DOWN ABOUT 500 TO 700 FT FROM THE DEPARTURE END. WITNESSES HEARD THE BRAKES SQUEALING AS THE PILOT CONTINUED OFF THE RUNWAY. AFTER DEPARTING THE RUNWAY, THE AIRCRAFT CONTINUED DOWN A GRADE AND INTO A GULLY AND WAS SUBSTANTIALLY DAMAGED. AN EXAMINATION OF THE AIRCRAFT REVEALED NO MECHANICAL PROBLEMS.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record ATL82DA130
- Event ID
- 20020917X02727
- Case number
- ATL82DA130
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1982-05-14.
- API snapshot SHA-256: 18bcd880d807a0913000d130f0e40600527939a14a175e58129b78f3158ba691; retrieved 2026-09-22T03:04:55.663Z.