FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC03LA078 · Piper J3C-65

2 Apr 2003 · Taunton, MA, United States

Piper J3C-65 · Accident: loss of control on ground/water during landing

From Taunton Municipal King Field (TAN) to Tangalooma Airport (TAN)

Report a problem

Event

NTSB case
NYC03LA078
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 J3C-65

Aircraft type
Piper J3
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
N88387
Operator
Unknown
Onboard fatalities
Unknown
Route
From Taunton Municipal King Field (TAN), Taunton, MATo Tangalooma Airport (TAN)
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
Loss of control on ground/water
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
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, not maintained
  • Pilot in command › Compensation for wind conditions, inadequate

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, prior to takeoff, he noted the wind sock was 70 to 90 degrees different to the wind he physically felt on the ground. He departed runway 30, and while in flight he observed smoke near the airport which indicated a crosswind of approximately 135 degrees to the runway, which he thought appeared to be the same as on take off. The pilot said when he landed on runway 30, the wind shifted and the tail of the airplane was picked up by the "tail/cross wind." The airplane then veered left and started to depart the runway. Unable to correct with rudder or brakes, the pilot applied full power to abort the landing. After lift off, to avoid trees, the pilot banked right which, "...caused the right wing to stall and slide into the ground by the wind sock." The pilot did not report any pre-impact mechanical difficulties with the airplane. Winds at the airport were reported to be from 110 degrees at 7 knots about 20 minutes after the accident, and as calm 45 minutes before the accident.

Probable cause

The pilot's inadequate compensation for the winds, and his failure to maintain airspeed which resulted in the inadvertent stall. A factor in the accident was the tailwind.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC03LA078
Event ID
20030410X00472
Case number
NYC03LA078
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: 13628301d91cfa90ec5bc891eb4da3fa9b3bddd3c90903648ae08116a513a5d1; retrieved 2026-09-22T09:26:50.942Z.