NYC92LA162 · Piper PA-18A-150
General Aerial Advertising Piper PA-18A-150 · Accident: airframe, component or system failure
From 1N6 · BARGINTOWN, NJ to an unrecorded destination
Event
- NTSB case
- NYC92LA162
- 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-18A-150
- Aircraft type
- Piper PA-18
- 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
- N9374D
- Operator
- General Aerial Advertising
- Onboard fatalities
- Unknown
- Route
- From 1N6 · BARGINTOWN, NJTo not recorded
- 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
- Other
- 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
- Airframe, component or system failure
- 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
- Production/design personnel › Acft/equip, inadequate handling/perf capabilities
- Sign towing equipment › Jammed
Approximate · Estimated position: the centre of Ocean City, NJ, the place the record names. Not the accident site.
NTSB narrative
DURING BANNER PICKUP THE TOW ROPE BECAME WRAPPED AROUND THE RELEASE HOOK AND THE PILOT WAS UNABLE TO RELEASE THE BANNER UPON THE COMPLETION OF THE FLIGHT. LANDING WITH A RIGHT CROSSWIND AND THE BANNER STILL ATTACHED, THE PILOT WAS UNABLE TO CONTROL THE DIRECTION OF THE AIRPLANE AS HE SLOWED, AND THE AIRPLANE DEPARTED THE RUNWAY TO THE LEFT SIDE, AND NOSED OVER. THE BANNER ATTACH POINT WAS A HOOK ON THE END OF A ROD, WHICH WAS ATTACHED TO THE MAIN LANDING GEAR, WHICH IS FORWARD OF THE CENTER OF GRAVITY. THIS MADE DIRECTIONAL CONTROL VERY DIFFICULT IF NOT IMPOSSIBLE AS THE AIRPLANE SLOWED. ACCORDING TO AN FAA INSPECTOR FAMILIAR WITH BANNER TOWING, ROPE IS MORE SUSCEPTIBLE TO TWISTING AROUND THE RELEASE HOOK THAN METAL CABLES. IN ADDITION, HE SAID THAT TAILWHEEL MOUNTED TOW HITCHES ARE SAFER THAN THOSE MOUNTED ON THE MAIN LANDING GEAR. ADDITIONAL INTERVIEWS DISCLOSED BOTH TOW HITCH SYSTEMS AND ROPE ARE IN COMMON USE FOR BANNER TOWING.
Probable cause
THE AIRPLANE NOSING OVER ON LANDING ROLL DUE TO INADEQUATE AIRPLANE HANDLING CHARACTERISTICS WHILE LANDING WITH THE BANNER ATTACHED. FACTORS RELATED TO THE ACCIDENT WERE THE USE OF ROPE INSTEAD OF STEEL CABLE, THE MAIN LANDING GEAR MOUNTED TOW HITCH, AND THE CROSSWIND.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC92LA162
- Event ID
- 20001211X15508
- Case number
- NYC92LA162
- 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: 6f76dd3895139f69bbf08c21d59174e504b4bb3296ab47991630f1c45ef61429; retrieved 2026-09-23T02:46:30.427Z.