Departure

Clearance, runway, SID, pushback, taxi

From the gate to airborne.

Departure runway and SID#

Choose Override departure runway in the flight plan dialog before pressing File Flight Plan. The default follows the airport and wind selection. The following departure dialog keeps that runway fixed; in manual mode it offers:

Don't use SID — climb on your own without a published SID.
Choose SID — pick a SID from the list manually.
Automatic SID — let the plugin select one.
On Screen Preview — see the runway and SID geometry on the Nav Display while choosing.

VFR flights force SID off because SIDs are IFR procedures.

If a SID looks greyed-out, it exists but is not recommended (for example, your cruise altitude is outside its restrictions, or the heading does not match your route).

Request and read back clearance#

After the runway/SID is confirmed:

Tune Delivery (or Ground / Tower if no Delivery).
The Radio Log offers Request IFR clearance or Request VFR clearance.
Press Handoff.
The controller issues the clearance. The Radio Log shows the readback button.
Press Handoff again, or use voice (see Voice & Push-to-Talk).

Pushback and engine start#

After clearance, tune Ground. The Radio Log offers:

Request engine startup (when the airport workflow includes it).
Request engine startup and pushback (combined call at gates that support it).
Request pushback (at gates that need it).
Request taxi (when ready).

Some airports skip pushback or combine actions. The Radio Log only shows what is appropriate.

Built-in tug reliability has been improved. The View tug control in Options -> Flight Assistance lets you inspect the active vehicle.

Taxi#

You are cleared to a holding point. Follow the green taxi guide on the ground. The guide uses X-Plane's airport taxi-route data. Some airports have gaps; the plugin falls back to centerline data where possible.

While taxiing:

The Radio Log may offer Report holding point or similar progress actions.
If your route crosses an active runway, Ground may tell you to hold short. Cross only after a crossing clearance.
If you have to deviate, the plugin tries to reroute automatically.

Holding point and Tower#

At the runway holding point:

Tune Tower.
The Radio Log offers Report ready for takeoff.
Tower issues Line up and wait or directly Cleared for takeoff.
Read back, line up, take off.

Backtrack and intersection departures#

Some airports use backtrack departures. The plugin handles this when the runway data supports it; you may see Backtrack and line up instead of a direct lineup.

Intersection departures (entering a runway from a taxiway intersection short of the threshold) are also supported when the airport has a usable crossing.

After takeoff#

Tower hands you to Center (or to Approach for short flights). See Enroute.

"The runway selection seems wrong"#

The flight plan dialog's Override departure runway selector defaults from wind, airport flow, your position, and procedure data. Choose another runway there before filing, or import the planned runway from SimBrief. The following departure dialog selects only the SID for that fixed runway.

"I do not see a SID list"#

Causes:

The runway has no published SIDs in the navdata.
Your first enroute waypoint does not connect to any SID.
Your cruise level is outside SID restrictions and Respect SIDs and STARs restrictions is on.

Use Don't use SID as a workaround. The plugin still builds a sensible initial climb.

"Taxi guide does not appear"#

Enable Draw taxi guide on ground in Options.
Some airports lack usable taxi-network data. Centerline fallback is used where possible.
The guide is only drawn while taxiing — not while parked or airborne.

"The tug takes a long time to arrive"#

The tug is dispatched to your aircraft and drives there along the airport surface, so a wait after the request is part of the service. While the tug is on its way, the bindable command NextATC/ground_service_skip advances it along its route, up to 75 m per press. The same command advances a Follow Me car.