A Part 135 pilot operating out of a shared non-towered airport in Rhode Island has raised a serious safety concern involving a banner-towing operation flying tight, low-altitude patterns that conflict with other traffic. According to the pilot's account, the banner tow operator and its pilots rarely communicate on CTAF during pick-up and drop-off maneuvers, and when they do fly, their patterns are aggressive enough that the reporting pilot has already executed two go-arounds at or below 300 feet AGL to avoid a conflict. Despite direct conversations with the operator and a formal report filed with the Boston FSDO, no corrective action appears to have been taken, leaving the original poster searching for practical mitigation strategies while regulatory channels work through the complaint.
This scenario illustrates a persistent friction point at non-towered fields that host specialized low-altitude operations alongside transient and based traffic. Banner towing is inherently a low-altitude activity — pick-ups typically occur via a grappling hook system flown at or near ground level, and drops happen in a similarly low, often tightly circling pattern to keep the aircraft near the target drop zone. These maneuvers do not always conform to standard 45-degree entry, rectangular traffic pattern procedures that transient and instructional traffic expect, and when combined with inconsistent CTAF discipline, the risk of pattern conflicts rises sharply. The reporting pilot's experience — needing to go around at dangerously low altitudes — is precisely the kind of near-miss that FAA Advisory Circular 90-66 (recommended standard traffic pattern operations at non-towered airports) and AIM Chapter 4 radio communication guidance are designed to prevent, yet compliance is voluntary absent a tower or specific local agreement.
For working pilots, especially those flying revenue passenger operations under Part 135, this situation carries elevated liability and safety stakes. Part 135 operators are held to a higher standard of risk management than personal GA flying, and repeated low-altitude go-arounds due to traffic conflicts would be a significant finding in any post-incident investigation or FAA surveillance inspection. Pilots in this position should document every occurrence with dates, times, altitudes, and radio call specifics, since a paper trail strengthens both the FSDO complaint and any potential NASA ASRS filing, which offers limited liability protection while feeding data into the national safety reporting system. Airport sponsors and management also have a role here: many small municipal airports have advisory committees or letters of agreement that can establish local noise abatement or traffic pattern procedures, and enlisting airport management or a users' group to formalize expectations for the banner operator can sometimes succeed where individual pilot complaints have stalled.
More broadly, this incident reflects a recurring tension in the U.S. general aviation system between the light regulatory footprint of non-towered airports — which enables diverse, often mixed-use traffic including banner tow, glider, skydiving, and flight training operations — and the safety assumptions built into the see-and-avoid, self-announce framework. As banner towing, drone operations, and other specialized low-altitude activities continue to operate from smaller GA fields, the burden falls disproportionately on individual pilots to identify conflicts and self-separate, often with imperfect information. Incidents like this one, surfaced informally on pilot forums before working through official channels, underscore why FSDO responsiveness and enforcement follow-through matter: without visible consequences for chronic non-compliance, informal peer pressure and shared airspace discipline remain the primary safety net, a fragile arrangement when one operator's normal operating procedure includes flying tight low patterns that other traffic isn't expecting.