NYC00LA003 · Piper PA-60-700P
Piper PA-60-700P · Accident: on ground/water collision with object during landing
From Laurence G Hanscom Field (BED) to 3B1
Event
- NTSB case
- NYC00LA003
- 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-60-700P
- Aircraft type
- Piper PA-60
- 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
- N407SA
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Laurence G Hanscom Field (BED), Bedford, MATo 3B1
- 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
- On ground/water collision with object
- 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 › Preflight planning/preparation, inadequate
- Pilot in command › Visual lookout, inadequate
Approximate · Estimated position: the centre of Greenville, ME, the place the record names. Not the accident site.
NTSB narrative
After entering VFR conditions at 6,000 feet MSL, the pilot canceled his IFR flight plan and made a straight-in, visual approach to a Runway 14, which had been NOTAM'd closed. During the landing, the airplane struck a lighted barricade and it's left wing contacted a 5 to 6 foot high pile of gravel located about 3,100 feet beyond the approach end of the runway. The pilot stated he re-checked the NOTAMS for the airport after the accident, and observed the NOTAM for the closed runway. The pilot said it was possible that he did not scroll all the way down the computer screen when he originally checked the NOTAMS.
Probable cause
The pilot's inadequate preflight planning and his inadequate visual lookout.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC00LA003
- Event ID
- 20001212X20028
- Case number
- NYC00LA003
- 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: fc345f870f3c1dee85fb8b9e47f230e43bf7673a5e95e8b481d6f2b57722ffc6; retrieved 2026-09-22T13:57:52.708Z.