Takeoff Clearance from intersecting runways

Runway incursion risk embedded in intersecting runway operations remains one of the most persistently misunderstood areas of ground operations, and the scenario described here illustrates precisely the kind of ambiguity that has contributed to dozens of runway incursion events worldwide. The question centers on whether a backtrack clearance on Runway 9 implicitly authorizes a pilot to cross the hold short line for an intersecting Runway 2, or whether that intersection requires a separate, explicit ATC instruction. Under both FAA and ICAO frameworks, the answer is unambiguous: no single clearance authorizes entry onto or across any runway other than the one specifically named in that clearance. A backtrack authorization on Runway 9 is a clearance to operate on Runway 9. The hold short line for Runway 2 represents a completely independent protected surface, and crossing it — regardless of operational context — requires an explicit, independent clearance from ATC.

The regulatory foundation for this is found in FAA Order JO 7110.65 (Air Traffic Control) and reinforced through Advisory Circular 91-73B, which governs pilot procedures during taxi operations. The hold short line is not a courtesy marking; it delineates the runway safety area and the protected zone that ATC is actively managing for separation. When a runway physically intersects another, each hold short line functions as a hard boundary that resets with every aircraft movement. A pilot cleared to backtrack Runway 9 who encounters the Runway 2 hold short line mid-backtrack must stop and request explicit clearance to continue through that intersection — whether the controller says "continue backtrack," "cross Runway 2," or incorporates the crossing into a broader taxi instruction. Similarly, a Line Up and Wait (LUAW) clearance for Runway 2 that requires the aircraft to taxi along Runway 9 first does not authorize penetration of the Runway 2 hold short line; it authorizes positioning on Runway 2, and the path to get there still requires distinct ATC authorization for each runway boundary crossed.

The original poster's observation that many pilots at their home airport routinely taxi to the runway edge without explicit clearance identifies a normalized deviation — one that mirrors the behavioral pattern seen in multiple NTSB investigations and NASA Aviation Safety Reporting System (ASRS) submissions. Normalization of deviance in runway operations is well-documented and is considered among the highest-risk precursors to runway incursions. What appears operationally routine at a low-traffic non-towered or less-busy controlled field can mask genuine risk exposure, particularly when traffic density increases, when visiting aircraft operate with different assumptions, or when ATC is managing multiple movements simultaneously. The FAA's Runway Safety Program has repeatedly flagged intersection crossings during backtrack and LUAW operations as a Category B and Category C incursion hot spot.

For professional crews operating under Part 121, 135, or 91K, Sterile Cockpit procedures during taxi add another layer of obligation. Standard Operating Procedures at virtually every major operator require explicit callout and verification of each hold short line, independent of what clearance was issued. Crew Resource Management protocols specifically address the hazard of assumed clearances — a co-pilot or captain who treats one clearance as covering multiple runway boundaries is operating outside both regulatory and procedural standards. Flight Operations Manuals at most Part 135 and Part 91K operators include runway crossing checklists precisely because the cognitive shortcut of "I'm already cleared to be on that runway complex" is both understandable and dangerous. The correct discipline is to treat every hold short line as a stop point pending explicit authorization, communicate promptly with ATC when the routing is ambiguous, and never interpret a clearance to backtrack or position as covering any surface beyond the one explicitly named.

The broader context here is the FAA's sustained multi-year campaign to reduce runway incursion rates, which remain stubbornly persistent despite significant investment in surface detection technology, Enhanced Ground Proximity Warning System (EGPWS) updates, and controller training. Intersecting runway environments at airports with crossing thresholds — common at general aviation reliever airports and smaller regional fields — represent a disproportionate share of incursion events precisely because the physical layout creates plausible-seeming assumptions about implied clearances. Pilots flying into unfamiliar airports should review published airport diagrams for runway intersections, identify potential hot spots listed in the Chart Supplement (formerly Airport/Facility Directory), and proactively request progressive taxi instructions when uncertainty exists. The professional standard is not to avoid asking ATC for clarification; it is to treat ambiguity about runway authorization as a mandatory stop condition until explicit clearance is received.