NYC01LA182 · Piper PA-28-181
Piper PA-28-181 · Accident: overrun during landing
From Igor I Sikorsky Memorial Airport (BDR) to Mattituck Airport (21N)
Event
- NTSB case
- NYC01LA182
- 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-181
- 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
- N17AV
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Igor I Sikorsky Memorial Airport (BDR), Bridgeport, CTTo Mattituck Airport (21N), Mattituck, NY
- 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
- 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 › Proper touchdown point, not attained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot followed another airplane into the airport, and landed about halfway down the 2,200-foot runway at a high rate of speed. The airplane then departed the end of the runway at 10-15 mph. The pilot stated that the windsock indicated winds varying from approximately 35-80 degrees off the runway heading, but that during the approach, the wind shifted to a tailwind. Recorded winds at an airport 10 nautical miles away also indicated a tailwind. According to the Pilot's Operating Handbook, at 2,500 pounds, with a full-stall touchdown and full flaps in a zero wind, the airplane should have required about 950 feet of runway. With a 5-knot tailwind, it should have required about 1,280 feet of runway.
Probable cause
The pilot's failure to attain a proper touchdown point. A factor was the tailwind.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC01LA182
- Event ID
- 20010724X01494
- Case number
- NYC01LA182
- 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: 0abb0b1238e45f30ad934c2b805d8481f8d7d4a6f7eb0e69afce3551106c4430; retrieved 2026-09-22T11:45:07.769Z.