NYC03LA003 · Piper PA-28-181
Piper PA-28-181 · Accident: loss of control in flight on approach
From Rhode Island T. F. Green International Airport (PVD) to Katama Airpark (1B2)
Event
- NTSB case
- NYC03LA003
- 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
- N8071Z
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Rhode Island T. F. Green International Airport (PVD), Providence, RITo Katama Airpark (1B2), Edgartown, 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
- Approach · VFR go-around
- 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
- Loss of control in flight
- 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
- Stall/mush; 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 › Airspeed, inadequate
- Pilot in command › Weather evaluation, inadequate
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
Arriving in the airport area, the pilot determined that the wind was favoring runway 06. While on approach to runway 06, severe turbulence and a wind shift was encountered. After crossing the threshold of the runway, the airplane appeared to be landing with a tailwind, and the pilot initiated a go-around. During the go-around, as the pilot pulled back on the control yoke, the airplane continued to descend towards the ground. The airplane struck a tree, touched down in a grass field located beyond the departure end of the runway, and came to rest upright. The recorded weather at a nearby airport, about the time of the accident, included winds from 250 degrees at 16 knots, gusting to 21 knots.
Probable cause
The pilot's inadequate in-flight evaluation of the landing facilities wind conditions, and inadequate airspeed resulting in a stall/mush. A factor related to the accident was the tailwind condition.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC03LA003
- Event ID
- 20021018X05340
- Case number
- NYC03LA003
- 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, 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: 48bdd5c34cd6faa7c769f8ddca532960e817cfe2850b79f67c0336122f856847; retrieved 2026-09-22T10:09:46.975Z.