Learn the correct ground taxi phraseology for an intersection departure at AAC Airport: using the proper ground controller, Runway 28R at C, taxi route GBC, and hold-short of Runway 16. Focus on selecting the right ground facility, stating runway, intersection, route, and hold point for clear, safe coordination.

Multiple Choice

At AAC Airport, what is the correct phraseology to taxi an aircraft from Spartan Aviation, that is requesting an intersection departure?

The main idea here is using proper ground taxi phraseology with the correct airport ground controller name, the correct runway, and the exact hold-short instruction for an intersection departure. You should contact the airport’s designated ground facility, not the FBO’s name, and you must state the runway you’ll be using, the intersection you’ll taxi from, the published taxi route, and the hold-short point. In this scenario, the correct ground contact is Academy Ground, not Spartan Ground, because Academy Ground is the designated ground controller for AAC Airport. The runway specified is 28R, which is the active runway for this departure, and you’re departing from the intersection at taxiway C. The route to the runway is the published taxi path GBC, and you must hold short of Runway 16 to ensure you don’t cross it until clearance is given. Putting it together, the standard call is: C172PT, Academy Ground, Runway 28R at C, taxi via GBC, hold short of Runway 16. The other options don’t fit because they use the wrong ground facility, reference the wrong runway, or state a hold-short point that doesn’t match the intended intersection departure.

Ground taxi phraseology: getting from gate to runway with precision

When you’re piloting a small aircraft into a busy field, the chain of communication matters just as much as the taxiway map tucked into your knee board. The moment you call ground, you’re setting the tone for safe, smooth movement on the ground. That means using the right controller’s name, the correct runway, and the exact hold-short instruction for the intersection departure you have in mind. It can feel like fiddling through a tiny, loud orchestra, but when you tune it right, everyone moves in harmony.

Let’s ground this in a concrete example. Imagine you’re flying a Cessna 172P with the tail number C172PT, arriving at AAC Airport. You want to taxi from Spartan Aviation, but your clearance depends on contacting the right ground controller and following the published taxi plan that leads you to Runway 28R via a specific intersection, then holding short of Runway 16. In real life, that means the call looks like this: “C172PT, Academy Ground, Runway 28R at C, taxi via GBC, hold short of Runway 16.” Not only does that line tell the controller exactly where you are and where you’re going, it also confirms the precise hold-short point you’ll respect as you prepare for departure.

The right ground controller makes a huge difference

One of the first things you learn as a student pilot is that ground control isn’t the same everywhere, and the airport has a designated ground facility that you should contact for taxi instructions. In this scenario, Academy Ground is the correct entity, not Spartan Ground. Why? Because Academy Ground is the designated ground facility for AAC Airport. If you call Spartan Ground, you’re talking to the wrong station and you risk miscommunications, delays, or—worst of all—an unexpected crossing of a runway while you’re still taxiing.

Ground controllers don’t just assign a route; they’re weaving together safe sequencing with movements from arrivals, other ground vehicles, and the array of aircraft poking around the ramp. A clean, concise call helps them slot you into the flow without hesitation. That’s the essence of good ground control: clear, correct, and timely.

Runway choice matters, not by flair but by current operations

The runway part of the call is not a creative flourish. It reflects the actual active runway and the departure plan. In our example, Runway 28R is the active runway being used for the departure. It wouldn’t be unusual to see a mixed-day scenario where winds flip, and the active runway changes, but the pilot’s job remains the same: specify the exact runway you intend to use in the taxi call.

Why Rnwy 28R and not 28L? Because the departure path you’re following and the associated taxi route depend on the runway in use. If you mix up Runway 28R with Runway 28L, you risk crossing paths with traffic or missing a taxiway corridor that’s designated for a particular direction. The phraseologist’s goal is to leave as little room for interpretation as possible.

The exact route and hold-short point are the anchors

After you name the controller and the runway, the taxi route must reflect the published path you’ll follow. In this scenario, the taxi route is “via GBC.” This is a published taxiway route that takes you from your current position to the runway safely while keeping you out of restricted or high-traffic areas. Saying “via GBC” isn’t optional flair—it’s a precise instruction that tells the controller and other pilots where you’re headed.

The hold-short instruction is equally important. You’ll tell the controller the exact point at which you’ll stop and wait for clearance to cross or enter a runway. In this case, the hold-short point is Runway 16. By stating “hold short of Runway 16,” you’re clarifying that you’ll stop at the intersection with Runway 16’s boundary and wait for specific clearance to cross or proceed. That clarity reduces the chance of misinterpretation, which is crucial when you’re negotiating busy ground operations near active runways.

Why the intersection departure is special (and worth understanding)

An intersection departure changes the usual dynamic of takeoff clearance. Instead of starting at the end of a runway, you’re beginning from an intersection—often a shorter taxi distance, but with unique rules. The hold-short point becomes critical because it marks the boundary where you must wait for proper clearance to enter or cross the active runway. It’s not just about getting wheels rolling; it’s about slotting into traffic in a way that preserves safety margins for everyone.

Common pitfalls to watch for

  • Using the wrong ground controller. If you call Spartan Ground when Academy Ground is the responsible entity, you’ll create confusion and slow things down. Always verify the airport’s official ground facility designation before you call.

  • Getting the runway wrong. If you say you’re taxiing to Runway 28L when 28R is active, you’ve introduced a mismatch that can lead to a near miss or a hold-short error. Double-check current runway status and NOTAMs if they apply.

  • Omitting the taxi route. “Via GBC” isn’t negotiable—without the route, you’re leaving room for misinterpretation about where to turn and how to progress to the runway.

  • Forgetting the hold-short point. The point at which you’ll stop is a critical safety cue. If you forget it, you might cross a line you’re not cleared to cross, which is exactly what the hold-short instruction is designed to prevent.

A practical way to internalize this

Here’s a simple habit you can adopt to keep phraseology tight without breaking stride:

  • Always confirm the ground controller’s name and the facility’s proper designation before you key the mic. If you’re unsure, a quick “Academy Ground, C172PT, with you” buys you a moment to verify.

  • State the exact runway clearly: “Runway 28R.” If the controller shortcuts, they’ll correct you.

  • Include the taxi route: “taxi via GBC.” If you’ve practiced the route before, the path should roll off your tongue with minimal hesitation.

  • End with the hold-short instruction for the intended intersection: “hold short of Runway 16.” The more precise you are here, the smoother the handoff to tower once you’re ready to depart.

Putting it together: the standard call you want to remember

C172PT, Academy Ground, Runway 28R at C, taxi via GBC, hold short of Runway 16.

That line is compact, clear, and complete. It tells the controller exactly who you are, where you’re starting from (Runway 28R at Charlie, in the shorthand you’re using), which route you’ll follow (GBC), and where you’ll pause for clearance (Runway 16). It’s the kind of call that makes communication quick and safe.

A few real-world nuances you’ll appreciate

  • The tone you use matters. Ground control appreciates a concise, professional cadence. You don’t need to sound formal, but you should be confident and direct.

  • If you’re unsure about the hold-short point during a busy moment, it’s perfectly fine to ask for confirmation. A simple, “Hold short of Runway 16, please” is a legitimate line that buys you clarity.

  • Weather and field operations can alter the procedure. If you notice a temporary restriction or a change in taxi routes, adjust your call accordingly and keep your mental map updated.

Analogies that help the memory stick

Think of taxiing like navigating a subway map. The ground controller is the station maestro, the runway is a platform, and the hold-short point is a safety barrier that prevents trains from colliding. The taxi route is your rail line—GBC in our case. When all pieces align, you glide toward the runway with the precision of a well-timed transfer.

A few tangents that connect back

If you’ve ever flown into a regional airport where the ground patterns change with seasons or with air traffic density, you’ve probably felt the difference a single word can make. A tiny change—Runway 28R instead of 28L, or switching from Spartan to Academy Ground—can ripple into several seconds saved or a smoother taxi for everyone around you. And that ripple matters. It keeps pilots calm, saves fuel, and reduces the cognitive load on the tower as they manage a chorus of radios.

The bigger picture: safety, discipline, and context

Ground taxi phraseology isn’t about sounding fancy or clever. It’s about shared mental models. When every pilot uses the same language to indicate position, intention, and constraints, the chances of miscommunication drop dramatically. This is especially true at busy airports where the ground traffic is dense, and the runway system is complex. By grounding your calls in the right controller, the right runway, and the correct hold-short point, you contribute to a safer, smoother airfield environment.

A gentle reminder: practice in the real world, with attention

The best way to get comfortable with this is to combine study with real-world practice. Review the airport’s ground charts, confirm the correct ground facility, memorize the typical taxi routes, and rehearse the precise phrases you’ll use. In practice, you’ll find that saying the exact line becomes almost automatic, leaving you more time to scan for traffic, check fuel levels, and keep the cockpit dialogue flowing naturally.

Bottom line: clarity wins

When it comes to taxiing from Spartan Aviation toward an intersection departure at AAC Airport, the winning call is: C172PT, Academy Ground, Runway 28R at C, taxi via GBC, hold short of Runway 16. It’s straightforward, it’s precise, and it respects the flow of the airport’s ground operations. If you keep that structure in your toolkit, you’ll move with confidence, and that confidence translates into safer, more efficient flights for everyone sharing the airfield.