ERA10CA496 · Piper PA-28-161
Plane Nonsense Piper PA-28-161 · Accident: landing area overshoot
From Norwood Memorial Airport (OWD) to 9B1 · Marlboro, MA
Event
- NTSB case
- ERA10CA496
- 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
- Unknown
- 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
- N260ND
- Operator
- Plane Nonsense
- Onboard fatalities
- Unknown
- Route
- From Norwood Memorial Airport (OWD), Norwood, MATo 9B1 · Marlboro, MA
- 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
- Defining eventThe 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
- Landing area overshoot
- 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
- Personnel issues › Action/decision
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
According to the pilot, he verified the wind direction and speed by observing the windsock before attempting to land. During the first attempt, he executed a go-around due to excessive altitude. During a second attempt, the pilot initiated a forward slip and landed the airplane two-thirds down the runway. After touchdown, he applied brake pressure, but the airplane continued off the end of the runway and impacted a fence, substantially damaging the fuselage and wings. A postaccident examination of the airframe and engine revealed no mechanical malfunctions or failures that would have precluded normal operation. The pilot reported that it was the first time he had landed at the airport and that it was the shortest runway he had ever attempted to land on. The pilot stated that the accident could have been prevented if he had performed a go-around.
Probable cause
The pilot’s improper touchdown point and failure to perform a go-around in a timely manner, which resulted in a runway excursion.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA10CA496
- Event ID
- 20100923X42153
- Case number
- ERA10CA496
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, coordinates. 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: 8d0e336f7972317d6c2a65bcea9b2475352817ddb7bd487111093e46e6486609; retrieved 2026-09-15T15:19:31.290Z.