ABEAM

Run group flights from your Discord server.

ABEAM posts the event in your channel, keeps track of seats and the waiting list, imports each pilot’s SimBrief flight plan and publishes a briefing with weather and online ATC before departure.

Add to Discord
Capitals tourOfficial OPS · A20N, A21N, B738
  1. 1LFPGEGLL18:30Z6/8 pilots
  2. 2EGLLEIDW20:15Z8/8 pilots · 2 waiting
  3. 3EIDWLFPG22:00Z3/8 pilots

Fictional example: the three legs of an official OPS.

An OPS, from announcement to departure

An OPS is a flight event: one or more legs flown together at set times. Everything happens in Discord, with buttons and forms.

  1. Announcement

    Create the OPS in a channel

    /ops create opens a form: title, up to 10 legs, UTC departure times, seats per leg and allowed aircraft. The bot posts the announcement with its buttons. Everyone reads times in their own time zone.

    • OfficialOn behalf of the server. Created by admins or the official roles.
    • MemberCreated by any member, in the channels admins open for it.
    • PrivateOn request: the organiser accepts each pilot, who then gets a private thread.

  2. Until departure

    Pilots pick their legs

    A pilot joins one leg or several. When a leg is full, they join its waiting list; when a seat frees up, the first in line is registered and told.

    1. @kestrel left leg 2
    2. @vortac, first in line, is registered on leg 2 and notified
    3. Leg 2: 8/8 pilots · 1 waiting

  3. Before the flight

    Each pilot imports their flight plan

    Link SimBrief once, then import your latest OFP when you choose. ABEAM checks it against your leg: airports, day, aircraft and off-block time. A mismatch is flagged, never silently fixed.

    /simbrief link alias:nimbus

    • @nimbusAFR1946 · A20Nvalid for this leg
    • @kestrelBAW306 · A333to check: aircraft not in the OPS list
    • @sigmetAFR1080 · A21Ninvalid: planned for another day

  4. 30 min before (adjustable)

    The briefing is posted

    A reminder and a collective briefing: METAR and TAF, connected ATC and ATC bookings for each airport, and where each pilot’s flight plan stands. It shows the state at that moment: ATC coverage is never promised.

    OPS briefing · Capitals tour

    State at 18:00Z: weather and OFPs may change.

    OFP: 5/6 imported · 1 to check

    1. LFPG → EGLL

    Departure 18:30Z (in 30 minutes)

    🛫 LFPG 211800Z 24012KT 9999 FEW030 12/07 Q1018 NOSIG

    ATC LFPG_TWR 118.650 · LFPG_GND 121.805

    🛬 EGLL 211750Z 22015G25KT 9999 BKN025 13/09 Q1012

    Booked EGLL_APP 18:00–21:00Z

    • ✅ @nimbus · AFR1946 · A20N
    • ⚠️ @kestrel · BAW306 · A333
    • ➖ @contrail · no OFP
    • … and 3 more
    For flight simulation only · no ATC coverage promised · METAR: aviationweather.gov

Also useful between two OPS

/metar /taf
Latest METAR or TAF of an airport, with its observation time.
/atc
VATSIM controllers connected at an airport, and the ATC bookings.
/flight find
A real airline flight to fly, from the community catalogue: by aircraft, airline, airports or duration.
/flight surprise
A random flight from the catalogue, with optional filters.
/flight submit
Propose a real flight; the ABEAM team checks it before it is listed.
/privacy
See the data ABEAM holds about you, or delete it.

For server admins

Adding ABEAM asks for the permissions below and nothing else. The bot does not read your messages: it reacts to its commands and buttons only.

View Channels, Send Messages, Read Message Historypost the reminder as a reply to the OPS announcement
Embed Linksshow the briefing in that reminder
Create Private Threads, Send Messages in Threadsgive each private OPS its own thread

Permissions integer: 343597468672

Add to Discord

Settings, with /config

  • official roles, who create OPS on behalf of the server
  • channels where members may create their own OPS
  • callsign prefixes of the server
  • language of the messages the bot posts on its own
  • when the reminder and briefing are sent
  • audit log: who changed what

Managing an OPS does not require admin rights: its organiser, admins and anyone with an official role can edit, cancel or accept requests. Settings stay with “Manage Server”.