ERA16CA218 · Piper PA32 260
Piper PA32 260 · Accident: landing area overshoot
From Tweed New Haven Airport (HVN) to Block Island State Airport (BID)
Event
- NTSB case
- ERA16CA218
- 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 PA32 260
- Aircraft type
- Piper PA32
- 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
- N44255
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Tweed New Haven Airport (HVN), New Haven, CTTo Block Island State Airport (BID), Block Island, RI
- Aircraft age
- About 42 years (built 1974)
- 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 · flare/touchdown
- 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
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Task performance
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, while on final approach to land on a 2,502-ft-long, asphalt runway, he observed another airplane back-taxiing on the runway and then depart. He continued the approach, performed a "normal" full-flaps landing, and the airplane touched down about midfield. During the rollout, he determined that there was insufficient runway remaining to stop and chose to attempt a go-around. The airplane subsequently struck the airport perimeter fence and then a roadway guard rail before it impacted terrain, which resulted in substantial damage to the wings and fuselage. The pilot reported that there were no preaccident malfunctions or failures with the airplane that would have precluded normal operation. He also stated that the accident might have been prevented by aborting the landing earlier.
Probable cause
The pilot's failure to attain the proper touchdown point and the airplane’s subsequent collision with obstacles during an attempted go-around.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA16CA218
- Event ID
- 20160620X91456
- Case number
- ERA16CA218
- 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: 44f8a9fee7576a392fc318d7461c3cdb86bb862a5d0cc957cc6a968f384496bd; retrieved 2026-09-16T03:31:48.937Z.