Virtual Airlines on Waypoint — claim yours! (Beta) ✈️

We’ve been building a Virtual Airline area into Waypoint, and it’s now live in beta. If you run a VA or fly for one, this is for you.

What your VA gets:

:world_map: Your logo above your aircraft on the live map — anyone who switches the VA label on sees your fleet flying in your colours, worldwide.
:house: A public page (waypoint-live.app/va/your-airline) — your logo, banner, description, hubs, route network and who’s flying right now. Share-ready: the link shows a branded preview card in Discord.
:busts_in_silhouette: A crew centre — roster with your own ranks and permissions, applications (via our form, your Discord or your website — your choice), flight reports, fleet with bookings, tours, challenges and events.
:bell: Discord webhooks — takeoffs, landings and “who’s flying” round-ups straight into your VA’s channel.
:framed_picture: An embeddable live map for your own website, configured in your colours.
:mobile_phone: A home-screen widget (Android, iOS soon) showing how many pilots are flying your colours.

How to claim your VA (takes 2 minutes):

  1. Go to waypoint-live.app/va and sign in.
  2. Hit Claim and enter your VA’s name, code and your IFC username.
  3. Our staff approves the claim (we check with the VA so nobody claims an airline that isn’t theirs).
  4. In the crew centre under Admin → Edit branding: upload your logo — that’s what appears above your aircraft on the map. Square and simple works best; you can optionally upload a separate, simplified map badge just for the map. Every image is reviewed by a human before it goes live.
  5. Pick your accent colour — it’s used across your page, your embed and your widget.

You also decide who wears your badge on the map: everyone flying with your virtual organization tag in Infinite Flight, or only pilots registered on your Waypoint roster.

This is a beta — things will move fast and some rough edges are expected. Feedback, wishes and bug reports are very welcome, right here in this thread. Tell us what your VA needs!

5 Likes

I love this! Cant wait to use it for my VA

1 Like

Maaan, Waypoint is becoming the central waypoint of everything (hehe). Like the old dudes and dudines used so say back then in the 1100s: all (air-)roads lead to Waypoint. :smirking_face:

Is this intended to be a replacement for VA Crew Centers or can this be used as an addition to those?

2 Likes

Thank you so much!

Well long term is the Plan to make a Hub for the community.
But if you use it instead of a Crew Center or as addition is up to you :smiley:

1 Like

Since I don’t have access yet, a few feature suggestions based on your features description:

1. Routes Database

  • Each VA has their own routes database.
  • Columns: Flight Number, Departure ICAO, Arrival ICAO, Aircraft (multiple), Flight Time, Codeshare (yes/no), Comments
  • Routes search function
  • Usually VAs restrict their aircraft, i.e. each aircraft requires a minimum rank. Show (filter) only those routes to the pilot that can be flown by the pilot based on their rank.
  • Routes import function (csv file)
  • Function to randomly choose a flight from the routes database to fly

2. PIREPs — (Automatic) ACARS

  • When filing a PIREP, offer button to automatically fill out the fields of the PIREP based on the last flown flight. If the entered data matches with a route in the VA’s routes database (exact same Flight Number, Dep ICAO, Arr ICAO and similar flight time with a margin), then the PIREP gets automatically reviewed and accepted. In case of discrepancies a manual review by VA’s staff team is necessary. Also in the case where the entered data doesn’t match with any route in the database, a manual review must be done.
  • PIREP must always be checked whether pilot has minimum required rank for the flown aircraft.
  • Certain flight programs within VAs (like ROTW) allow pilots to use aircraft outside their rank. For this, you could add a dropdown menu field to the PIREPs form so that the pilot can choose which flight program this PIREP belongs to and if it’s not a “normal flight”, then it needs a manual review by staff team.
  • Ability for staff to add flight programs / flight types besides “normal flight”: ROTW (Routes of the Week) etc. And for each flight type staff can specify a multiplier which is then applied to the pilot’s PIREP flight time. E.g., if pilot chooses “ROTW” from the dropdown menu field then the multiplier set by staff for this flight type is applied automatically (e.g., ×1.5 for ROTW). “Normal flight” is always ×1.

3. Career Mode (simplified)

  • Pilots of the VA need to be manually unlocked for this mode by staff team.
  • Automatic flight schedule generation for the month.
  • Flight schedule consists of continuous routes, i.e. pilot starts at airport a, lands at airport b, then starts from airport b and lands at airport c. I.e., always start from where they landed at.
  • Pilots earn virtual money $VA (VAD – Virtual Airline Dollars) for flights flown within career mode.
  • Pilots can spend the money in the shop for specific items that staff team put there (like maybe buyable one-time multiplier that can be used for normal flying, outside of career mode; or a relocation item specific to the career mode to let the pilot relocate to another location, maybe simulate the relocation time — i.e. not instant relocation —and also two different type of items where one randomly relocates and another more expensive item which enables choosing a specific location to relocate to)
  • Flight schedule must only contain routes that are flyable by the pilot based on their rank, i.e. no aircraft outside their rank.
  • When a pilot finished flying a route, they can tap somwhere in the career mode tab to file the current career mode flight.
  • A multiplier chosen by staff is automatically applied to career mode flights (e.g., ×1.25)
  • Optionally add a performance score to judge how good landings etc are (landing rate, centerline deviation); level 1 violations could potentially lower the score as well

4. (Bush) Missions (Mode)

  • This feature is a more a niche one and most likely not used by many VAs. This is especially interesting for bush flying missions for example in a VA.
  • Pilots must be manually unlocked for this mode
  • Staff team releases missions with mission description, route (route doesn’t necessarily have to be part of the VA’s routes database, i.e. freely entering ICAO codes possible; multi leg routes should be possible as well), PAX/Cargo load number, mission pay $VA
  • Prior to mission begin, the pilot needs to calculate fuel needed for the mission on their own (or use a tool like simbrief) and buy it in a specific fuel tab with their own $VA money
  • Fuel will always be fully reimbursed after the flight by the mission “company”, i.e. in the end every pilot gets the same mission pay for completing the same mission (mission pay can have a modifier based on a so called reputation score). Buying fuel upfront is primarily an immersion feature and it requires pilots to have some money in the first place to start a mission since they have to buy fuel first before flying. It’s more fair if fuel buying doesn’t impact the total money earned through the mission since fuel amount is impacted by the environment (winds, etc) and can be different for each pilot.
  • Staff provides the total fuel that is available for a mission, i.e. simulating the fuel provider. E.g., for mission A, they provide “PABE FUEL JET A” (i.e. Jet A fuel at airport PABE) with a total quantity of 6,500,000 lbs and a price of 1.11 per lbs.
  • Reputation Score: Each pilot has a personal reputation score. A good (high) reputation score modifies the pay of missions positively (e.g., increasing pay of missions by +10%) and a bad (low) reputation score modifies the pay of missions negatively (e.g., reducing pay of missions by -10%). After every mission, reputation points are either added or deducted based on the mission performance. Mission performance is based on landing rate, centerline deviation, fuel safety (score reduction if fuel remaining at final target airport is < 30 minutes), overfueling (score reduction if loaded fuel is > 200% expected block fuel), level 1 violations received.
  • Money earned through missions can be spent in the same shop mentioned in the career mode section. That shop is the general VA’s shop where earned $VA money can be spent, no matter in which mode the money was earned.

5. Misc

  • If we wanna get really adventurous, one could also implement simulating a bit of a pilot’s real life besides flying by letting pilots buy property with their $VA, improve their property (with objects), basically spend money on things that a normal human-being spends money on in real life. And pilots can visit each other’s inventory to have a look and gaze in amazement :laughing:.

These are all merely suggestions of course (points 1. and 2. being the primary requests) and also, if some of these are already implemented, please kindly ignore those specific suggestions.

2 Likes

You should have Access now :smiley:

1 Like

Thank you!

Just saw this:

If we manually enter our flight data when filing a PIREP, the PIREPs info gets stored in the database. So, the flight hours can be summed up and then an automatic rank up should be possible?

I was actually also asking myself how other CC systems (legally) store Live API data (using ACARS which automatically fetches the flight data to fill out the PIREP form):

Forgot about that issue when I suggested the ACARS feature above.

1 Like

I will write IF about it today.

If they approve it i will implement it. But i rather ask then just break the rules.

Yes if you manually input the hours it does work :smiley:

1 Like

#0

Please add the feature to reject an already approved PIREP and to approve an already rejected PIREP. This way, a mistake can be undone.

Also, the possibility to “hold” a PIREP could be useful. It’s for those PIREPs that need further clarification/discussion with the pilot who submitted it.

So, there would be “Accept”, “Hold” and “Reject”.

#1

Also, please give us the ability to set the branding accent color using a hex color code.


#2

Currently only pilot name available. Ability to give pilot callsign missing. Pilot callsign is an alphanumeric value, e.g. “ASVA003”.


#3

Regarding the following feature:


Please add an option so that only pilots in our Waypoint VA’s roster are “selected” when they use their VA callsign on their flight. Because them being in our Waypoint VA roster doesn’t mean they’ll always be performing flights for this VA.

{AirlineCallsign} {PilotNumber}{AirlineSuffix}

VA’s use 2 different callsign formats:

  1. Example Alaska Airlines Virtual
  • Alaska 324AS, Alaska 223AS, Hawaiian 756AS, Speedbird 324AS, etc.
  • I.e., the unique identifier is the suffix “AS”. The suffix “AS” uniquely identifies the pilot performing a flight for Alaska Airlines Virtual.
  1. Example FedEx Virtual
  • FedEx 324VG, FedEx 543VG, FedEx 123VG
  • I.e. if the suffix is “VG” (or “VA” or “VO”) the unique identifier is the airline callsign, in this case: “FedEx”. If the suffix is VG/VA/VO, the airline callsign uniquely identifies the pilot performing a flight for the airline.

So, the conditions are:

  1. pilot in Waypoint va roster + specified suffix
  2. pilot in Waypoint va roster + suffix is VG/VA/VO AND specified airline callsign

Same with the “Everyone flying our tag” option. Only select those that are also actually using their VA callsign.


#4

Webhook “A round-up of who is flying right now” displays as if option “Everyone flying our tag” is selected although option “Only pilots registered on Waypoint” is selected.

1 Like


This is a neat idea — like an Infinite Flight Live Lite. Will this be expanded / synced with Infinite Flight Live once it (IF Live) has been fully released?

1 Like

VA area got its biggest update yet — career mode, missions, a shop and badges. Almost all of it came straight out of this thread, so: thank you.

What’s new:

:spiral_calendar: Career mode — a month of flying as one chain. The roster is built from your own route network, always departing from where the last leg landed, filtered to what the pilot’s rank may fly. Pilots are paid in your airline’s currency and can spend it on a bonus multiplier or a relocation (with travel time, so it costs them something).

:camping: Missions, for the bush-flying side — post jobs between any airports, in several legs if you like. The pilot buys the fuel up front and gets it back in full when you approve the job, on top of the fee.

:shopping_cart: Your own shop — put anything on the shelf: a livery of the pilot’s choice, a special flight, a seat on a charter. Your picture, your price, stock and a limit per pilot. Pilots pay with the points they already earn for approved flights, tours and challenges — you simply give those points your own name, so they can be Miles, Credits or whatever suits your airline. You get a list of what’s been bought and still needs handing over, a refund button, and a column showing who holds how much.

:sports_medal: Badges you draw yourself — create one, upload your artwork, hand it out by name or attach it to a tour so finishing that tour awards it. Every badge a pilot has earned across every airline now lives on one shareable page: waypoint-live.app/pilot/your-if-username

:chart_increasing: Automatic promotions — set the hours a rank expects, tick promote automatically, and the rank is given the moment a pilot reaches it. You can count only certain aircraft, so “Captain after 50 hours on the 787” works. It only ever promotes — a rank you gave by hand is never taken away. The hours come from the reports you approved, so nothing counts before you’ve seen it.

:locked: Aircraft can require a rank — the 777 for Senior First Officers and above, say. Pilots below that see it greyed out with the reason, on routes, on the fleet board and when filing a report.

:clipboard: Routes database, rebuilt — scheduled flight time, a codeshare flag and a comment per route, and routes are editable now instead of delete-and-retype. Import a CSV file straight from your spreadsheet: it works out the separator itself and matches columns by their headings. There’s a dice button for when nobody knows what to fly, and a filter for “only what I’m allowed to fly”.

:tada: Events can pay — give an event a point value, and pilots tick it when they file the flight afterwards. Signing up beforehand stays a headcount, and forgetting to press it doesn’t cost anyone their flight.

:pause_button: Reviewing got its middle option — Accept, Reject and now Hold, plus a “recently decided” list and the ability to change your mind.

:white_check_mark: Reports that match a live flight are approved on the spot — file right after landing and, if what you typed matches the flight we can see, it goes straight through and tells the pilot so. Anything we can’t see goes to a reviewer exactly as before; it can never reject anyone.

:artist_palette: Smaller things you asked for — a hex field for your branding colour, a company callsign per pilot on the roster, and a third option for who wears your badge on the map: everyone flying your callsign scheme. The “who’s flying right now” round-up now obeys that setting, which it genuinely didn’t before. A retired aircraft’s registration is free to use again.

:wastebasket: Closing an airline down is possible at last, and it belongs to the owner alone: type the name, and 24 hours run during which your whole crew sees a countdown in the crew centre and in your Discord. You can call it off at any point. Separately, any pilot can now leave an airline and have their own record erased, without needing anyone’s help.

Where to find it:

  1. Open your crew centre at waypoint-live.app/va/your-airline/crew.
  2. Career, Missions and Shop are new tabs in the sidebar.
  3. Badges live under Challenges — create one there, then attach it to a tour under Tours.
  4. Automatic promotions are under Admin, in the rank editor: set the hours, tick the box, optionally name the aircraft that count.
  5. Name your currency at the top of the Shop tab — everything keeps calling it “points” until you do.

Still a beta — this round moved a lot at once, so if something looks wrong, say so here and we’ll get on it. Feedback and wishes just as welcome. Tell us what your VA needs next!

1 Like

Incredible, thank you!

Quick question regarding the auto-approval implementation: PIREPs should only be auto-approved

  1. if they match the recent flight in IF exactly (departure ICAO, arrival ICAO, aircraft, exact flight time)

AND

  1. if they match a route in the VA’s route database at the same time (flight number, departure ICAO, arrival ICAO, aircraft, flight time within a tolerance since flight times in the VA’s routes database are approximations/averages).

Otherwise, pilots could fly and file any flight and get it auto-approved even though it’s not in the VA’s route database.

Has the auto-approval feature been implemented like that?

1 Like

Excatly how it works :smiley:

1 Like

Awesome, thank you! :grin:

1 Like

Waypoint for Virtual Airlines — the second feedback round

Route of the Week

Pick a route, give it a window, and it becomes the week’s headline flight. You can set a flight-time multiplier for it, a minimum rank, and lock it to certain weekdays. It can auto-create on a schedule and post itself to your Discord when it opens, and pilots can filter the routes list down to “Route of the week only” so it’s easy to find.

Multipliers

Every reward multiplier now feeds the same number:

  • Codeshare routes can carry their own flight-time multiplier and a minimum rank.
  • Events can carry a flight-time multiplier and a minimum rank, on top of the points they already pay.
  • Route of the Week has its own multiplier (and now a dedicated codeshare-on-ROTW multiplier for when a route is both).
  • Tours can carry a per-leg flight-time multiplier.
  • Staff can set a custom multiplier on a single PIREP when a flight deserves it.

Multipliers can be entered as decimals now (1.5×, not just whole numbers), and when a report is approved the pilot sees exactly which multiplier was applied to their time.

Network and route maps

Your VA now has a proper map of where it flies. The public page carries a great-circle route-network map, My desk shows the pilot’s own flown routes, and every route has its own preview with the coastline behind it and ICAO codes on the airports.

The routes tab

  • A full search and filter mask — by flight number, departure, arrival, duration, aircraft, and codeshare
  • File straight from a route: the PIREP form opens prefilled with the number and the leg, and you fill in the rest.
  • Each route shows a times-flown count and opens a detail panel with its own map, and imports now validate the aircraft as they come in.

Filing and reviewing reports

  • Each flying programme now files its report from its own button — a Route of the Week, a tour leg, a career leg, an event — instead of hunting for it in a dropdown on the general form. The claim is made where you started the flight.
  • Staff can edit a submitted PIREP and see a currency transactions view — who was paid what, and why.
  • A report that carries a comment goes to manual review rather than being auto-approved, so anything a pilot wants to explain is actually read. Multi-leg flight numbers are handled properly.

Ranks and roster

  • Ranks can start at 0 hours, and a joining pilot is given the entry rank automatically so nobody sits rank-less.
  • The owner (and staff) can hold a rank too, and rank requirements now apply to everyone.
  • Callsigns are unique within an airline now.
  • Staff can fix a pilot’s Infinite Flight username on the roster, and on phones the tabs scroll sideways only instead of fighting the page.

My desk

  • ATC & your routes: the live controllers that are open right now, matched against the routes your VA flies, so you can see where there’s someone to talk to.
  • A “Next from …” card suggesting a sensible next leg from where you’re standing.
  • An activity-streak figure, and staff NOTAMs pinned to the top — with a streak period you can configure (daily through weekly). NOTAMs are collapsed to just their count until you open them.

Tours

  • A tour can pay a flight-time reward and, if you like, require staff sign-off before it completes.
  • The aircraft type is enforced per leg, tours and missions take uploadable, moderated thumbnails, and a finished tour posts a generated completion card to your Discord.

Activity policy

Set how long a pilot can be inactive before they’re flagged and, separately, retired — with opt-outs per rank and a rule that keeps staff out of it. It’s there to keep a roster honest without punishing the people who run the place.

Webhooks

Filter a webhook to specific live servers, support several callsign schemes for one airline, and split notifications into per-kind channels so takeoffs, landings and the rest can each go where they belong. Take-off and landing pings now honour your VA’s scope, not just the tag.

Smaller things

  • Career: staff can hand-adjust a pilot’s VA dollars and look up anyone’s VAD history
  • The whole site (and your VA pages) can switch to a light theme with a slide toggle, independent of the map’s own day/night.

2 Likes

Thank you so much for your work on this CC and for listening to the feedback of the community!

1 Like

Thank you so much!

1 Like

This app is actually insane. The UI is amazing and I have uploaded some photos!

1 Like