Events, tours and focus airports

Watch the video: Events, tours and leagues

How to give your pilots something to fly together: events with bonus points, tours of several legs, and focus airports that pay extra for a while.

Publish news

News posts are made on Staff → Community → News, under Publish news.

1. Enter a Title and the Text, and pick a Priority (how the post shows as a NOTAM on pilots' dashboards).
2. Optionally, set Publish at (UTC) to publish it later. Leave it empty to publish now.
3. Press Publish.

A post goes to your Discord news channel when it's published. Pilots who turned on News from my airline on their Profile also get it by email, and the weekly summary lists the week's posts.

A post with a publish time is hidden from pilots, from your airline's pages, from Discord and from email until then. You see it in News posts with Scheduled for and its time; open Edit to change the text or the time, or empty the time to publish it now. Delete removes it before it goes out. When the time comes, Discord and the emails go out once, within a few minutes.

NOTAMs for some pilots

With NOTAMs for some pilots on, Publish news has two more choices: Only for (a rank and the ranks above it) and Based at (one hub). Leave them on All ranks and Any hub to post for everyone. Only pilots in that group see the post as a NOTAM and get it by email. Your Discord news channel gets a short notice saying who it is for, with a link to read it on the site.

Staff switch it on under Staff → Airline settings → Optional features, in the Community group.

Airport NOTAMs

With Airport NOTAMs on (Optional features), Staff → Community → Airport NOTAMs posts a notice for one airport: a closed stand, a company procedure, an event's slot rules. Pilots flying from, to or diverting to that airport see it on the booking page while it's in force (and from 12 hours before its start, for flights planned by then), above the official NOTAMs of their SimBrief plan. Times are UTC. You need the News and NOTAMs permission.

Create an event

Events have their own page: Staff → Community → Events.

1. Under Create an event, enter a Title.
2. Set Starts (UTC) and Counts for (hours): how long after the start a flight still counts. This can be 1 to 72 hours.
3. Optionally, enter a From and To airport. Leave either one empty to allow any airport.
4. Pick the Callsign: Airline callsign (your code and a number the pilot picks, like WZZ123) or Free callsign (pilots choose any).
5. Tick the Aircraft types pilots can pick from. Tick none to allow any type in your fleet.
6. Optionally, write the Route every pilot gets, and Dispatch notes (gates, fuel, loads, runway).
7. Set Points on time (up to 500) and, if you like, Points if late: what a flight that departed late gets instead. Leave it empty to give the same either way.
8. Optionally, set a Flight level and whether it is A must (everyone flies it) or Optional (pilots may pick their own).
9. Add a Description, and optionally pick Repeat (Every week, Every two weeks or Every month) and How many times (2 to 12) to make a series in one go.
10. Click Create event.

A series makes one event for each date, at the same time. A monthly series keeps the same day of the month, or uses the month's last day when the month is shorter. Each date is its own event, so you can edit or delete one without touching the others.

If your airline has connected Discord, the new event is posted to your channel (for a series, the first date). The bot also posts when you change an event's time or airports, and when you delete one before it starts. Pilots reach events from Events & tours → Events or the Events tile on their dashboard, and open one to press Apply (Leave the event takes it back) or use Add to calendar. Pilots who subscribe to their own calendar link (Profile › Calendar) see the events they signed up for there automatically.

A PIREP gets the event's bonus when it's filed between the start time and the end of the window, and its airports match the event's. Pilots don't have to sign up to earn it.

With Event reminders switched on (Staff → Airline settings → Optional features), pilots who signed up get an email a day before the event, and your Discord channel gets a reminder an hour before it starts (when it posts new events). Pilots can turn the emails off on their profile.

Which flights count and the event's rules

Under Which flights count, pick By airports or By our routes:

• By airports: type one or more ICAO codes in From and To, split by commas. With AND a flight must leave from one of the From airports and land at one of the To airports. With OR either one is enough. Leave a side empty for any airport.
• By our routes: type a departure and an arrival (or a flight number, route number or aircraft type) to narrow the list, then pick one or more of your routes. Pilots of a co-hosting airline count when they fly between the same airports.

Counts when the flight chooses what must happen inside the event time: the take-off, the landing, both, or either. Leeway adds minutes before the start and after the end. Show from hides the event from pilots until that date and time.

Under Rules, nothing ticked means no limit. You can ask for Networks (Offline, VATSIM, IVAO), Callsigns starting with one of your codes, Ranks, and a Hardest and Softest landing. The aircraft types under What pilots pick also count here. Pilots must apply first gives the bonus only to pilots who applied, and Once per pilot gives it once each. Give a badge makes a badge named after the event for everyone who earns the bonus.

Only flights booked from the event is ticked on new events: only a flight the pilot booked on the event page (after applying, or from their slot) gets the bonus. Its PIREP shows the event and the slot number. Any other flight on the same airports gets a 0-point line saying it wasn't booked from the event. Events made before 3 Nov 2026 keep counting every matching flight until you tick it.

No rules or checks turns everything off for the event's flights: every flight booked from the event page that fits the airports and time gets the bonus (flights not booked from it keep every rule). It needs airports on both sides or picked routes, the rules above don't apply, and the PIREP checks about how it was flown (landing, procedures, network, schedule) take no points and send nothing to review. A flight that wasn't really flown (demo, slew, position jumps, timing) is still caught. Turning it on or off is in the activity log.

Copy next to an event fills in the create form with everything from that event except the start time. Set the new time and press Create event.

When every departure slot is taken, pilots can Join the waiting list. A slot given back, or one you free with Free up, goes to the first pilot waiting, who is told on the bell, unless it starts within 15 minutes. An event booking that runs out unflown gives its slot up too. A pilot who cancels their booking keeps the slot to book again. When a pilot leaves the airline, their slots go to the waiting list. A suspended pilot's slots go to it too. A pilot who gets a slot this way applies (aircraft and callsign) before booking it.

If you move the event or change the slot spacing, flights already booked from it move to the new time and their pilots are told. Pilots who lose a slot because you cut the number of slots, or because you delete the event, are told on the bell; a flight they booked stays booked.

Gates for the slots is optional: one gate per line with its name, latitude and longitude. Each slot gets a gate in turn. 15 minutes before a slot we look at VATSIM: if an aircraft is parked on that gate, the pilot moves to the next free gate and is told. A slot moves at most twice, and never once the pilot is on VATSIM or the flight has started. IVAO and offline aren't checked, and nothing is ever blocked.

Once an event is over, its page shows Results: flights, pilots, how many left on time, the softest landing and the badge.

If staff reject a flight chooses where the pilot and aircraft end up when you reject one of the event's flights: where it landed, back at the departure, or as the airline's setting (A rejected flight goes back to its departure under Settings › Flights, off by default). Going back also cancels the return flight or next trip leg that was booked from the arrival when it was filed.

When the network couldn't be checked, or you want to let a missed rule pass, open the PIREP and press Give the bonus for the event. The flight then counts as an event flight: in the results, for the badge and for once per pilot.

These rules are checked when the PIREP is filed, with nothing for staff to do. A flight that breaks one keeps its other points, and its PIREP shows a 0-point line saying why it got no event bonus.

Under Event page you can add Tags, a Picture link (and one for dark mode), and a side box with a title and text. The Description can use simple Markdown: bold, italic, lists, headings and links. Create and add another saves the event and opens an empty form. When you create an event you can tick Don't post it on Discord, or Mention @everyone to ping your whole server once with the post.

What pilots pick when they apply

On the event's page, a pilot presses Apply and picks:

• a Time slot, when the event has departure slots;
• an Aircraft, from the types you ticked (only the ones their rank lets them fly);
• a Callsign: your code and 1 to 4 letters or numbers, or any callsign of 3 to 7 letters and numbers when the event allows a free one. Two pilots can't use the same callsign in one event;
• a Flight level, only when you made it optional. Left empty, they fly yours.

They then see Your event flight: their slot, aircraft, callsign, flight level, the Route and your Dispatch notes. Book the event flight (or Book my slot) books it with that callsign, flight level and route, so they go on to SimBrief and ACARS. Change what I picked lets them change it until the event is over.

A flight that leaves the gate more than 15 minutes after its booked departure time gets Points if late instead of Points on time.

The Events list on the Events page shows each event with its sign-ups. Use Edit to change it, or Delete to remove it. Deleting an event keeps the PIREPs flown for it, but they no longer point to the event.

Departure slots

If your airline has turned on Event departure slots, the event form also has Departure slots and Minutes apart. Each slot leaves that many minutes after the one before, starting at the event's start time. You can have up to 200 slots. Set 0 for no slots.

Each pilot takes one slot on the event's page, which also signs them up. They can then book the event flight for their slot time. If you lower the number of slots later, pilots holding the later slots lose them.

To free a pilot's slot for someone else, open the event's page and press Free up under that slot. You need the Events, tours and awards permission. The pilot gets a notification, and any flight they already booked for it stays booked.

Events with other airlines

If your airline has turned on Events with other airlines, each event on Staff → Community → Events has Invite to co-host. Type the other airline's ICAO code or web address. Their staff see the invitation on their own Events page, under Events with other airlines, and press Co-host it or Decline; they need the same switch on. Once accepted, the event shows at both airlines, pilots of both sign up and fly it, and each flight counts, with the event bonus, at the pilot's own airline. Either side can stop co-hosting.

Create a tour

Tours are made on Staff → Community → Tours.

1. Under Create a tour, enter a Name.
2. Under Legs, list the flights. Write them as pairs, like HECA-LGAV, LGAV-LIRF, one per line or separated by commas. Or write a chain of airports: HECA LGAV LIRF LEMD.
3. Leave Award for finishing it ticked to create an award for pilots who fly every leg, and pick an Emoji for it.
4. Click Create tour.

Every airport must be in the airport list. If one is missing, add it on Staff → Operations → Hubs & airports first.

Pilots reach tours from Events & tours → Tours or the Tours tile on their dashboard. They see their progress and the airline's routes that fly each leg. Legs count only in order, and only with PIREPs that count (accepted or complete) filed after the tour was created.

In the Tours list, Hide takes a tour off the pilots' list, and Show brings it back. Delete removes it, with the pilots' progress on it.

Edit a tour

Edit in the Tours list opens the tour's form, with how many pilots started it and how many finished. You can change the Name, the Description, the Legs (one per line, in the order they are flown) and whether finishing it gives an award. Press Save tour.

Changing the legs never takes away progress on a leg that is still in the tour:

• A leg that stays, with the same airports, stays done for every pilot who flew it, also when you move it to another place in the order.
• A new leg, or a leg whose airports you changed, starts undone for everyone. Pilots fly it, and the legs after it, in order from there.
• A leg you remove is gone, with the progress on it.
• Pilots who already earned the tour's award keep it. Pilots who have done every leg after your change get it when you save.

Untick Award for finishing it to stop giving the award for this tour: it stays on the Awards list and with the pilots who earned it, and you can rename or delete it there. Tick it on a tour without one to create it. Each save is written to the Activity log.

Surveys

If your airline has turned on Feedback surveys, open Staff → Community → Surveys to ask pilots up to five questions: a rating from 1 to 5, one choice from a list (one choice per line), or free text. Ask all pilots, or only the pilots signed up for an event. Pilots find it under Events & tours → Surveys and answer once. Open a survey from the list to see the totals and each pilot's answers. Close stops new answers; deleting a survey deletes its answers too.

In Team challenges, you can also pick an Award for the winners: every pilot who flew for the winning team gets it when the challenge ends (not when it ends in a tie).

Points shop

If your airline has turned on Points shop, open Staff → Community → Shop to offer things pilots can buy with their points: a livery request, choosing their callsign, a hub swap, a seat on a staff-flown event. Give each item a Name, a Cost (points), and if you like a Stock (how many can be sold in all) and a limit Per pilot. Hide takes an item out of the shop without losing its orders; Edit changes it.

Pilots find the shop under Events & tours → Shop. They can spend the points they've earned (flights plus bonus points) less what they've already spent, and can add details for you with each order. Buying never lowers a rank: ranks and leaderboards keep counting the points earned.

Each order waits under Orders waiting until you hand the item over yourself, then click Handed over (with a note for the pilot if you like). Return points gives the points back, also after an order was handed over; a return is final. Your own orders are settled by the owner or another staff member.

Focus airports

If your airline has turned on Focus airports, open Staff → Operations → Bonuses.

1. Under Focus airports, enter the Airport, the First day and Last day, and the Bonus points.
2. Add a Note if you like.
3. Click Add focus airport.

Between those dates, a flight to or from that airport earns the bonus. If a flight touches more than one focus airport, it gets the biggest bonus. Pilots see current focus airports at the top of the flight list, and those routes are marked. Click Remove to end one early.

Points multipliers

If your airline has turned on Points multipliers, the Bonuses page also lets you multiply the points of some flights. You can choose:

• a route type, like cargo
• a route tag
• an aircraft type

Flying online already earns its points on the Scoring page, and a focus airport pays its own bonus, so they aren't multipliers any more. A multiplier for them made before stays and keeps working, with a warning, until you remove it.

Pick what the flights are under Flights that are, enter a Value where it's needed, set Multiply by, and click Add multiplier.

All matching multipliers apply together, up to ×3 in total. They only multiply points a flight earned, so penalties never grow. The extra points show as their own line on the PIREP.

See Scoring groups and failure rules for the rest of how points are worked out.