IAD96LA146 · Piper PA-28-235
Piper PA-28-235 · Accident: overrun during landing
From Martin State Airport (MTN) to Clearview Airpark (2W2)
Event
- NTSB case
- IAD96LA146
- 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-235
- 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
- N9074W
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Martin State Airport (MTN), ISSEX, MDTo Clearview Airpark (2W2)
- 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 · aborted
- 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
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- 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/speed, misjudged
- Pilot in command › Go-around, delayed
- Pilot in command › Proper touchdown point, not attained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot stated that he entered the traffic pattern behind a Cessna. He stated that there was no radio communication with the Cessna, and after it landed, it maneuvered as if to take the runway again. However, it stopped short with its nose over the right side of the runway. The pilot stated that he came in with 40 degrees of flaps at about 70 mile per hour (MPH). He said that he came in high over the Cessna, pulled power and descended to the runway. His last known airspeed was between 80 and 85 mph. He said he touched down below the numbers, applied the brakes, and the aircraft seemed to slow. He said that at about 10 to 15 feet from the end of the runway, he was too fast, and the aircraft was not slowing down properly. He said he applied power to go around, but the airplane struck the trees off the end of the runway.
Probable cause
the pilot's misjudgement of his speed and distance, his failure to attain the proper touchdown point during the landing, and his delay in executing a go-around (aborted landing), which resulted in an overrun.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record IAD96LA146
- Event ID
- 20001208X06755
- Case number
- IAD96LA146
- 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: 3e24769746ce4c789381c33a5bf3c6559d3a8c603fa628ab7a0521dc9a57c8dd; retrieved 2026-09-21T12:28:00.467Z.