Dispatching a flight

Dispatching is where you tell AnyAirline what is about to happen: which flight, which cabin, which voice. Everything the connector does later — what it says, when it says it, in which language — is decided here and sent to the connector as a plan.

There are two ways in, and they lead to the same place.

Dispatch flight

Give it your SimBrief username and it pulls your latest OFP: route, aircraft, airline, flight number, scheduled times and, if the OFP carries one, the gate.

Then it fills the gaps you would otherwise have to fill yourself:

Stand and gate. If the airport is mapped, a stand is assigned automatically from the same data the stand editor uses — matched on wingspan, and on your airline where the airport has a preference. A gate is only filled in when SimBrief and the schedule left it empty, so your own choice always wins.

Languages. Picked from the route (see how languages work).

Your flight profile. The rules you set once under Settings are applied to every dispatched flight, so you are not re-deciding the same things every time.

Before you confirm, you get an estimate of what the announcements will cost in credits, itemised. That estimate is the point at which to change your mind about a second language.

Choosing what runs

Whichever route you take, you are choosing three things.

Which announcements happen at all. The full cabin programme is boarding calls, welcome, safety, cruise updates, service, descent, arrival and farewell. You can run all of it or a fraction.

How each one is voiced. Per announcement you can pick the full AI voice, AI Lite, the local voice, or turn its sound off entirely. That is also the main lever on cost.

What plays alongside. Boarding music and the order it plays in, the safety video or recording, the terminal chime. Picks you make for an airline or an airport are remembered and offered again next time.

Boarding groups

Boarding can either be one announcement or a sequence: an intro explaining the process, priority boarding, then group calls, then a call for everyone remaining, then the last call. The connector paces the sequence itself against the time you have left at the gate — if boarding is short, the filler is skipped and the backbone still runs in order.

With GSX ground services switched on, the pacing follows the real GSX boarding instead of the clock.

The manifest

You can have a passenger and crew manifest generated for the flight — names, seats and the cabin layout for your aircraft. It feeds the announcements that refer to passengers and the IFE.

What the connector receives

Not a list of times. The connector gets a plan: what should be said, and the conditions under which each part becomes due — a flight phase, an elapsed time, an altitude, another announcement having finished, or a signal from the aircraft such as the seatbelt sign.

That is why the flight adapts when you fly it differently from the plan. A long taxi, an early descent or a held departure moves the announcements with it rather than firing them at the wrong moment.

Re-dispatching

Dispatching again replaces the flight. If you dispatch a new flight while one is running — even the same route — the connector treats it as a new flight and resets its progress, so nothing is left over from the previous leg.