No vehicle may pass between a marshaller or wing walker and the aircraft they are guiding while it is moving. The point is to keep visual guidance and communication unbroken — not merely to avoid a collision.
The rule is real and broadly enforced, but it is not written into any one global regulation. It lives in local ramp procedures, airport rules and ground-handler manuals, which is why the way it applies can differ from one airport to the next on a single itinerary.
Ask a ramp supervisor why nobody drives between a marshaller and the aircraft they’re guiding, and you’ll get a look that says the question answers itself. It’s obvious. Of course you don’t.
That obviousness is exactly why the rule is so thinly documented: everyone treats it as a corollary of a bigger principle about who has priority on the apron.
So the rule is real, broadly enforced, and almost never stated the same way twice. Searching airport rules, federal provisions and military instructions turns up not a statute but a patchwork — different mechanisms, at different levels of authority, all aimed at the same conflict.
What holds that patchwork together isn’t a legal citation. It’s a piece of safety logic about attention: a person focused on guiding a large aircraft cannot simultaneously scan for everything else moving around them. This article is about that logic, and about why the rule it produces lives in local manuals instead of one global code.
The rule everyone follows and nobody writes down
Start with the part that is settled. On the apron, aircraft hold right-of-way over every ground vehicle — a priority that applies whether or not air traffic control is directing movement in that area. Vehicle operators are expected to keep to designated service roads and lane markings, and reckless driving on the apron is prohibited outright.
From that principle follows the specific prohibition: no vehicle may pass between a marshaller or wing walker and the aircraft they are guiding while it is moving. The stated purpose is functional rather than merely physical — it protects the continuity of visual guidance and communication, the channel through which a pilot or tow operator learns whether the path ahead is clear.
Here’s where the story gets more interesting than the rule. Across the airport rules, federal provisions and military instructions reviewed for this piece, no single international or civil-federal document emerged that bans the maneuver in so many words. The prohibition is real. The universal statute behind it is not.
| Airport or jurisdiction | Governing document | Exact relevant wording or verified rule | Stated vehicle-to-aircraft clearance |
|---|---|---|---|
| Porto Alegre, Brazil | Operational Safety Requirements | Second person guides approach; stop immediately if guide leaves view; approach only after aircraft stopped and chocked. | No five-foot minimum stated; approach speed limited to approximately walking pace. |
| Pittsburgh International Airport, United States | Rules and Regulations, Article V | Push crew must include at least one wing walker; pushbacks must not conflict with nearby aircraft or ground-crew movements. | No five-foot minimum stated in reviewed provision. |
| United States military airfields | Air Force Instruction 13-213 and AMC supplement | Sets ramp, apron and taxiway vehicle procedures; permits supplements at multiple organizational levels. | No five-foot minimum or universal marshaller-crossing wording verified. |
| Canada | Airport Traffic Regulations, C.R.C., c. 886 | Requires motor-vehicle operators to hold provincial and municipal licences and permits. | No marshaller-crossing prohibition or five-foot minimum stated. |
| United States civil aviation guidance | Advisory Circular AC 00-65A | Describes wing walkers, tail walkers and cockpit observers as personnel ensuring clearance near obstructions. | No five-foot minimum stated in retrieved guidance excerpt. |
| Source: Porto Alegre International Airport; Allegheny County Airport Authority; U.S. Department of the Air Force; Department of Justice Canada; Federal Aviation Administration | |||
What the local rulebooks actually say
Five documents were detailed enough to compare, and the two clearest examples sit at opposite ends of the same idea. At Porto Alegre, specified aircraft-service vehicles — catering trucks, stairs, ambulifts, motorized belts — must have a second person guiding the approach, and the movement has to stop the instant that guide leaves the operator’s field of view. Approach speed is capped at roughly walking pace.
Pittsburgh International Airport takes a different route in Article V of its rules and regulations: the push crew must include at least one wing walker, and pushbacks must not conflict with adjacent pushes or aircraft moving nearby.
Neither approach restates a federal mandate. The U.S. Air Force instruction governing ramps, aprons and taxiways sets responsibilities and restrictions while permitting supplements at multiple organizational levels — the framework is built to be added to locally. Canada’s reviewed federal provision requires motor-vehicle operators to hold the licences and permits their provincial and municipal law demands, and stops there.
A November 2024 account filed with NASA’s Aviation Safety Reporting System shows what the rule guards against. During a pushback, a tow operator saw a bus drive past the wing walker and had to brake sharply to avert a possible collision.
The wing walker signalled stop; the bus kept rolling forward at first. The report names no flight, airport or individuals — it is a de-identified safety account, not a completed accident — but it captures the exact conflict in miniature.
Superdeals cover departures from North America, Europe and Australia.
Flight deals most people never see
Air Traveler Club monitors thousands of routes for pricing anomalies that traditional search engines miss. With ATC Superdeals members save up to 80% on each flight vs. regular fares.
Too good to be true? Check it out yourself. It's free.
Delivered weekly. Unsubscribe anytime.
Why a broken sightline stops the pushback
Ramp guidance is a controlled visual chain, not a series of commands. As the aircraft moves, the pilot or tow operator depends on marshallers and wing walkers to check clearance and relay stop-or-go signals. The specifics — who stands where, what a raised hand means, how the tow crew positions itself — are written by airport operators, airlines and ground handlers into local manuals and stand procedures, not into one global ramp code.
The chain breaks the moment a signal or sightline is lost. A vehicle that crosses between walker and aircraft does more than get close to a wing: it removes the pilot’s real-time information about that side of the airplane, and the walker cannot supply it, because the walker is what the driver is blocking.
The cognitive half of the argument rarely appears in public documents. A marshaller guiding a large aircraft is running a narrow, high-attention task — wingtip clearance, engine clearance, tow bar, stop signal. There’s little spare attention left for scanning which tug is about to cut across behind them. The driver, who can see the whole picture, is the party best placed to remove the conflict entirely rather than manage it in the moment.
Ramp work also runs in distinct phases. Before anyone approaches the fuselage for servicing or ground support, the aircraft must be fully stopped and chocked. Movement and servicing are not the same operation, and the rules around them aren’t either.
What this means for you
That a ramp rule can stop a departure with nothing mechanically wrong with the plane is the practical point for a traveler. A pushback halted because a sightline broke is a safe outcome — and also a delay. On a tight connection, ramp pauses stack: the tow crew waits, the slot slips, the onward flight gets tighter.
It also explains an inconsistency you may have noticed. Because these rules live at the airport and handler level rather than in one global code, the ground choreography around your aircraft can feel different from one hub to the next on the same itinerary. There’s no single standard to point to.
When weather or an obstruction limits visibility, ground operations have to stop until ramp personnel restore clear sightlines and communication — the same principle applied to conditions instead of a single vehicle.
On clearance distances, one figure circulates: vehicles near aircraft should keep a safe separation, often given as at least five feet. Treat that as a local convention rather than a universal number. The documents reviewed did not establish five feet as a global minimum.
Key terms
- Marshaller
- A marshaller is a ground crew member who directs an aircraft’s movement on the apron using hand signals. Marshallers work with wing walkers, tail walkers and cockpit observers, the team FAA guidance says keeps an aircraft clear of obstacles as it moves near terminals and hangars. Because the reviewed documents leave the crossing ban to local manuals, how well a marshaller is shielded from passing vehicles depends on the airport rather than one global rule.
- Wing walker
- A wing walker is a ground crew member who moves alongside an aircraft to watch for clearance on one side. FAA guidance groups wing walkers with tail walkers and cockpit observers as the personnel who ensure an aircraft has proper clearance near obstructions. No reviewed federal or international document names the role in a vehicle-crossing ban, so a wing walker’s protection rests on airport-level rules.
- Pushback
- A pushback is the procedure in which a tow crew moves an aircraft backward from its gate, typically because it cannot taxi out under its own power. At Pittsburgh International Airport, the push crew must include at least one wing walker, and pushbacks must not conflict with nearby aircraft or ground-crew movements. The reviewed documents treat pushback as a local procedure, so the wing-walker requirement that applies at one airport may not exist at the next.
- Apron
- The apron, also called the ramp, is the paved area at an airport where aircraft park, load and receive ground services. On the apron, aircraft hold right-of-way over ground vehicles, and drivers are expected to keep to designated service roads and lane markings. The apron is where this article’s conflict plays out, and its rules come from the airport operator rather than a single global code.
Questions? Answers.
What are the right-of-way rules in aviation?
On the apron, aircraft hold right-of-way over ground vehicles, and vehicle operators must keep to designated service roads and lane markings. The practical expression of that priority is local: Pittsburgh International Airport requires at least one wing walker during every pushback, and FAA guidance describes marshallers relying on wing walkers, tail walkers and cockpit observers to keep clearance. What the reviewed sources do not contain is one universal written rule covering every ramp.
Is there a universal five-foot clearance rule between ground vehicles and aircraft?
No. A five-foot minimum is often described, but it was not verified as a universal standard in the documents reviewed. Where a fixed figure is absent, airports substitute local controls: Porto Alegre requires vehicles to stop immediately if a guide leaves the operator’s field of view, and caps approach speed at about walking pace. The distance is a local convention, not an international number.
Why must a vehicle never drive between a marshaller and an aircraft?
Because that space is the guidance channel. The prohibition exists to keep visual guidance and communication unbroken while the aircraft moves — a walker who cannot be seen cannot pass along a stop or go signal. The reviewed sources do not trace the ban to a single international rule, so it is enforced mainly through local ramp procedures and airport rules.