Changelog

A smaller change to wrap up our launch week.

• Fixed payload fields showing when dispatching Repositioning or Training flights

• Improved scoring rule creation by pre-populating default values

• Workaround to SimBrief ignoring bagwgt when paxwgt is not provided has been added

• Changed how activity logbooks recreation is triggered when updating Activity - changing leeway and start/end times will trigger it.

• Added a weekday checker to Route and Routing Imports, so non-weekday names cannot be entered

• Updated Route Create/Edit Turbo mode to remove fleets which do not exist

• Added invisible Timezone override system for users whose browser reports their timezone as Asia/Calcutta when using Time Setter in Dispatch. Correct timezone now is Asia/Kolkata

• Flight Dispatch page will now remember your ‘Dispatch via SimBrief' toggle setting

• Various changes and tweaks to Route Importer

Beta Branch

With the initial flurry of activity behind us, we will move back to utilising a Beta branch in some way, shape or form as we start working through some of the items in Featurebase for improvements and smaller feature ideas.

We’re not huge fans of keeping it under a separate subdomain - like beta.vamsys.io so will spend some time exploring the options on how to bring ‘experimental’ features to vAMSYS proper via a user toggle.

Stay tuned - we’ll be sure to let you know more when we have something in place.

Scorer Changes

• Change to Online Network scorer - it now bases connected % from blocks off to blocks on, as opposed to Pegasus tracking start/end.

• Online Network Scorer will update booking network if it was different to what was tracked

• New Multiple Flights Per Day scorer - it will add extra points or bonus points for each subsequent PIREP (including the PIREP number provided); i.e. if you put in 2 - second, third, fourth etc PIREP of the day will get extra points.

Other Changes

• Added VATSIM and IVAO callsign availability checked in the Dispatch page - it will check if the callsign is available on these networks (i.e. is not prefiled or currently in use)

• Changed SimBrief stock Aircraft Profile sync to include some of the missing profiles due to how SimBrief categorises some of them

• Fixed an issue with logbook tracking for Curated Rosters

• Fixed an issue with events edited in-between 5.0 and 5.2 Activity updates - the issue manifests with an error when opening an Activity one is registered for - the fix VAs can apply is by opening the Activity in Orwell and saving it - it will rebuild the Activity Logbook for each registered pilot.

• Fixed Route Importer not importing Pax and Bag weights

• Fixed Route Edit page not always having pre-populated fuel units - there should always be a default value

• Improved Estimated Time value in Flight Details section in View Booking

• Added Delete Routes bulk action in Routes table in Orwell - it will set end_date to now for live routes and will remove routes not yet started

• Changed Delete button visibility when Editing Route to only show when editing Route which has not started yet; Added End Route button

• Fixed an issue when creating a Scenery for an Airport via the View Airport Page

• Changed the ‘Completions’ table to ‘Logbooks’ when viewing Tour/Roster based Activity - it now lists all logbooks for you to view.

• Adjusted how the Table when booking a flight is filtered to show only routes from your departure airport, so that custom-created views can be re-used between your VAs.

5.2 is our milestone release and incorporates changes made in v5.1 which was not publicly released.

Changes for Pilots

Navigraph Integration

5.2 Features extended integration between Navigraph and SimBrief. We use new API provided by SimBrief to generate OFPs as well as some data from Navigraph to further enhance the experience.

To enable SimBrief Dispatch Integration, as well as map overlays for some Airports, users must link their Navigraph Accounts. This can be achieved via Phoenix → My Profile → Account Settings → Social, Online & 3rd Party. Whilst there also make sure you have your network IDs set up - dispatching to VATSIM, IVAO or POSCON requires network ID set up.

All users with linked Navigraph account will have the option to use SimBrief Dispatch.

Users with Navigraph Unlimited subscription will additionaly receive improved maps for some airports showing more detailed airport layout.

[Image: ]

New Flight Dispatch Page

We have added ‘Flights From’ page which lets you book a flight without the map and rewrote the Dispatch page.

[Image: ]

• Aircraft - a new, streamlined way to select the aircraft. Default picked aircraft will be one of your favorites, quickly change in the dropdown or use the Aircraft Picker.

• Callsign - if configured by VA, a generate callsign option will be available; Callsigns can now be restricted to pilot username or aircraft registration.

• Departure Time has a Time Setter to help you pick your departure time based on your timezone.

• Routings - Virtual Airlines now have the option to provide multiple routings to pick from for any given route.

• Payload section has improved, especially for Container use.

• SimBrief Settings has the option to pick the SB Airframe Profile - be it SimBrief Default ones, profiles provided by the Virtual Airline or your custom ones.

• Alternate Finder will help you pick best alternates based on the prevailing weather

• SimBrief Flight Plan preview lets you have a quick look at the generated SB OFP to see if you need to make changes to your payload or fuel load.

Most importantly, SimBrief dispatch is now done in the background; Any changes made to the OFP at SimBrief.com after the dispatch will be automatically synced back to vAMSYS

PausePlay

0:00

-0:00

UnmuteMute

Disable captionsEnable captions

Settings

AudioDefault

CaptionsDisabled

Disabled

QualityAuto (240p)

Auto

1080p

720p

480p

240p

SpeedNormal

0.25x

0.5x

0.75x

Normal

1.25x

1.5x

1.75x

2x

Exit PiPEnter PiP

AirPlay

Exit FullscreenEnter Fullscreen

Booking Page Changes

• Booking Page now includes SimBrief OFP details as well as the OFP itself - these are preserved for months and you or VA Staff can always refer to them.

• Do you hate having to go to Navigraph Charts -> Flights -> Import Flight -> Import from SimBrief then select the entry? We do; We’ve added ‘Open Navigraph Charts’ button in View Booking page to save you from all these clicks.

Changes to PIREP Claims

If enabled by the Virtual Airline, claims in 5.2 are virtually indistinguishable from PIREPs. Claims are handled just like PIREPs needing review. There is no separate Claim review like in 5.0 and claims inherit all PIREP functionality like comments and need reply flag. You will see your claims in your PIREP List;

PIREP View received a facelift

[Image: ]

Altitude/Groundspeed chart from v3 is back and better! We’ve added some events like engine starts, pushback, gear up/down, touchdown etc.

Also, as mentioned in Navigraph/Simbrief section above, we now persist OFP data; Furthermore, once 5.2 starts processing the PIREPs, we will note down the landing runway, landing location from runway start and LDA (the precision will improve with upgrades to Pegasus).

Changes for Virtual Airline Staff

There is a lot, lot more for VA Staff - we have summarised all the changes below; On the way to 5.2 we have also rewritten all our Documentation - all systems and functions have a docs page where they are explained.

Orwell Changes, Farewell to VDS

Orwell is now the one-stop-shop for VA Management and VDS has been retired in 5.2. All VDS functions related to Airports, Aircraft, Routes and Load Management have bbeen moved to Orwell.

Orwell itself has changed a lot - it is worth to take some time and explore all the pages to see what is new and what has changed.

Staff Permissions

Where? Orwell → HQ → Staff

There are two new Staff Permissions for managing Load Factors and Containers. You need to enable them for relevant Staff, including VA Owners.

PIREP Point and Comment Presets

Where? Orwell → Settings → Presets

This functionality has changed quite a bit in vAMSYS 5.2 and is no longer compatible with 5.0. Presets can now also be used when reviewing Pilot Registrations

Virtual Airline Timezone

Where? Orwell → Settings → Basic Settings

New to 5.2 is VA Timezone. vAMSYS executes some tasks on a schedule - for example, at midnight UTC we run checks to put pilots on grace and remove inactive pilots. Midnight UTC could be noon in your operating environment - but if you were to set Timezone to Australia/Brisbane, the same task will be executed at midnight Autralia/Brisbane time, not UTC.

There is no exaustive list of tasks affected yet, but anything to do with Pilot activity, pilot removal and statistics is affected by Timezone setting.

Activities

Where? Orwell → Operations → Activities

With vAMSYS 5.2, Activities replace the Events feature from version 5.0. Designed for easier creation, improved scoring, and enhanced tracking, Activities introduce new activity types and provide comprehensive controls for VA management.

We have added new Activity Types → Roster and Curated Roster; We’ve simplified activity creation and improved activity tracking.

Improvements Across All Activities

• Custom Sidebar Section: Add custom links such as charts, scenery, and external resources.

• Placeholder Badges: Automatically creates a placeholder Badge upon Activity Completion. VA staff can subsequently edit this badge to add images, descriptions, and further details.

• Leeway Settings: Adds configurable buffer times to activity start and end dates, ensuring slight deviations in actual departure or arrival times still earn points.

• Participation Limits: New toggle to determine if pilots can complete the activity once or unlimited times.

Orwell and Phoenix UI Enhancements

• Phoenix Dashboard ('Events' Component): Enhanced with quality-of-life features requested by VA Partners. You can now filter displayed activities by tag and type, enabling configurations such as separate event boxes for Focus Airports and Tours.

• Phoenix Events Page: Clearly lists each event with descriptions, offering filters by Type and Tags for ease of navigation.

• Detailed Event Views: Event specifics, airports/routes involved, and interactive route maps are displayed more clearly.

• Event Logbook: Tracks completions for all events, showing progress clearly for Tours and Rosters.

Customizing Activity Labels

Customize labels for Activity Types:

• Navigate to Orwell -> HQ -> Settings -> vAMSYS ModulesRename Events, Focus Airports, Tours, Rosters, or Curated Rosters to better align with your VA's terminology.

Callsign Generation

Where? Orwell → Setttings → Route Defaults Orwell → Operations → Routes → Routes

You can specify some route defaults for callsigns in 5.2 Flight Dispatch.

Options include:

• Allowing pilots to change Callsign

• Defaulting callsign to Pilots Username (Option 1)

• Defaulting Callsign to Pilot Username (Option 2)

• Defaulting Callsign to Aircraft Registration (Option 3)

When managing Routes, you will still be required to enter a callsign, but on Flight Dispatch the callsign will be forced if any of the ‘Defaulting’ options are enabled.

Another addition is Callsign Generator regex which determines the remaining 4 character generation for the callsign. Entry of [A-Z][A-Z][0-9][0-9] will generate a sample callsign EZYBL62 with 52,900 total possible options.

Booking Validity

Where? Orwell → Settings → Booking & Dispatch → Booking

By default, all bookings are ‘active’ for 24 hours. After said time, if no flight tracking has been started, the booking is cancelled.

In 5.2 you can change the validity for ‘regular’ and Diversion/Repositioning bookings.

Online Network Remarks

Where? Orwell → Settings → SimBrief Integration

We have added ‘Online Network Remarks’, ‘IVAO Remarks’ and ‘VATSIM Radar Remark’ options.

• Online Network Remarks adds specified text to all available network prefiles

• IVAO Remarks adds the specified text to Online Network Remarks when Booking is made for IVAO

• VATSIM Radar Remark toggle automatically adds VATSIM Radar compliant remark when dispatching to VATSIM.

Some examples of how remarks are constructed:

• VATSIM: Fleet/Aircraft Extra FPL Info (Item 18) + Online Network Remarks + VATSIM Radar Remark

• IVAO: Fleet/Aircraft Extra FPL Info (Item 18) + Online Network Remarks + IVAO Remarks

• Other Networks: Fleet/Aircraft Extra FPL Info (Item 18) + Online Network Remarks

Load Factor

Where? Orwell → Operations → Payload

As requested by our VA Partners, a new Load Factor generation option has been added. You can use ‘Average’ section which, if entered, will make load factor average set percentage.

Stands

Work on vAMSYS Stand Project continues and has not been finished in time for 5.2 release. As such, all stand functionality has been disabled in 5.2. All your custom stands and stand groups have not been lost, but are inactive pending new Stand feature in upcoming versions of vAMSYS.

Airport Management

Where? Orwell → Operations → Airports

With deeper SimBrief integration and Alternate Finder implementation in 5.2, Airport Management has expanded a little. This includes ‘Suitable Company Alternate’ toggle, Alternate Search parameter overrides, airport briefing URL and others.

Fleet / Aircraft SimBrief Options

Where? Orwell → Operations → Fleet

Our SimBrief integration is different than the one in 5.0 and as such - the overrides from 5.0 have not been transferred to 5.2.

Fleet Enforced Profiles

Orwell → Operations → Fleet → Fleets → Fleet → SimBrief Integration

You can select the SimBrief Aircraft Profiles that pilot will be able to choose from. If you do not select any, all will be allowed. This includes default SimBrief Aircraft profiles as well as VA Custom Profiles.

Pilot custom airframe profiles can always be used.

SimBrief Airframe Overrides

Orwell → Operations → Fleet → Fleets → Fleet → SimBrief Integration

Orwell → Operations → Fleet → Aircraft → Aircraft → SimBrief Integration

As with 5.0 Fleet settings apply to all Aircraft within the Fleet; Each option can also be entered in Aircraft and it will override that option from Fleet. In other words - Aircraft inherits from Fleet.

Please take a second to consider if you want to use this as this is a powerful all-or-nothing option which will force the entered values for all SimBrief Dispatches.

Particular sections which you may not want to override are Empty Weight, MZFW, MTW, MLW and Max Fuel Capacity. Generally, it is best to leave this to Airframe Profile to accomodate differences in weights between aircraft addons.

Please note that Route configuration is able to override fuel and cost index values. If entered in Route, these will take over from Aircraft/Fleet configuration.

Route Management

Where? Orwell → Operations → Routes → Routes

Turbo Mode

5.2 adds ‘Tubo’ mode to route editing and disables most of handholding in terms of inputs. It’s closer to VDS 1.0 experience and is great for those experienced with vAMSYS Data patterns.

Cost Index

Cost Index can now be left empty. Generally, it is preferred option, other than the cases where you want to force a specific Cost Index. If left empty, the SimBrief Dispatch will look at the Aircraft/Fleet SimBrief Integration settings and pick the Cost Index/Cruise Profile from there. This is great for routes where you have a mix of equipment operating which have their own preferred CI/CP.

Days of Operation

New to 5.2 is Days of Operation/Service days. This is an informational field, visible to pilots on Flight Dispatch, denoting what days of the week the flight operates. As is vAMSYS philosophy, this does not restrict pilots from booking a flight on a different day and is for information only.

Callsign options

Please see Callsign Generation above details. This is the autoritative setting on callsign generation.

Relationshiop Tables

At the bottom of the page, when editing a route, you will see 3 tabs - Routings, Bookings and PIREPs. These allow you to quickly see what routings exist between two airports and see bookings made / PIREPs filed using this route.

Routings

Where? Orwell → Operations → Routes → Routings

A new addition to 5.2. Think routings as ‘Routes-lite’. Currently, routings store information about departure airport, arrival airport, route, service days and AIRAC cycle.

For Virtual Airlines who provide routes (collection of waypoints and airways), Routings is a pefect and lightweight option to update routing data for routes.

City Pairs can have multiple routings. If multiple exist, pilots will be able to select a routing of their choice.

PIREPs

Where? Orwell → Flight Centre → PIREPs

PIREP view pages have received a significant facelift compared to 5.0

A change from how 5.0 did things, where we heavily encouraged you not to look at PIREP List as it was heavy to load, 5.2 features tables of Pending, Awaiting Pilot and All PIREPs.

Furthermore, PIREP review no longer works as a ‘conveyor belt’ where you are taken from one PIREP to the next. Accepting/Rejecting/Invalidating a PIREP will not automatically move you to next pending PIREP either - we have found that VA Staff during review will sometimes go back to enter comments/internal notes. We have, however, added ‘Next Pending PIREP’ button to take you to next PIREP to review. Also - if multiple members of Staff are looking at a PIREP,

There is quite a lot to explore with the new PIREP review page - including the chart noting PIREP events, greatly expanded data shown from the flight, handly links to Livery, Aircraft, Fleet, Route, Airports etc.

When 5.2 goes live and handles PIREP processing, the ‘Touchdown’ section will be populated by default and will note the arrival Runway, Distance from threshold on landing at LDA available at the time. You can test it by rescoring any PIREP in 5.2.

Claims

Where? Orwell → Flight Centre → PIREPs

Claims in 5.2 are virtually indistinguishable from PIREPs. What we do mean by that - Claims are handled just like PIREPs needing review. There is no separate Claim review like in 5.0 - the benefit of that being - Claims inherit all PIREP functionality like comments and needing reply.

This also makes claims editable after the fact - you can return to a claim in the future and reject it if it was accepted, accept it if it was rejected, change hours and points awarded as needed.

We are pleased to share the latest updates featuring several improvements and fixes within the vAMSYS ecosystem.

What a busy day! 24 code pushes today to production to solve some of the issues discovered on 5.2 launch. Code changes are very disruptive - for the ~5 minutes it takes for them to go live the CPU use explodes, vAMSYS.io gets unhappy and will sometimes throw errors or timeouts, our Pegasus servers will also be upset and take just a bit longer to store those position reports. All in all, our fast pace with pushing out fixes contributed a little to the overall headache experienced by our servers. Moving on - unless it’s an emergency - we will do a much better job in batching the updates so it’s a bit easier for everyone.

Overall, it went way better than expected without too many dramas or offline period.

PIREP Processing Issues

One thing which we could not really test in 5.2 Beta is how the newly created PIREPs are handled - this caused empty landing rates and autoreject issues. Behind the scenes it was caused by:

• Unusual timestamp formatting coming from users - hh.mm.ss instead of the usual hh:mm:ss

• PIREPs getting processed faster than the Position Reports get updated. One of the new features in 5.2 is touchdown evaluation - for that to work, we need the position reports stored and assigned to the PIREP. The way we scheduled the tasks meant PIREP processing started before position reports got assigned to PIREP.

Pegasus Server high load

Pegasus servers experienced a surge in CPU use which caused some issues with logging in and getting Airport and Stand data.

We’ve moved some of the tasks outside of our 3 servers responsible for Pegasus and this has stabilized the situation. We will be exploring in days and weeks to come to further optimize this.

Other Fixes:

• Pegasus had issues looking up SimBrief Alias (we no longer store aliases as of 5.2) via SimBrief API

• Error in our ‘Error 500’ error page, where it would not produce error ID to share

• Restored erroneusly deleted loadfactor calculator from Orwell

• Fixed Navigraph User account linking - it was refering to beta when it no longer exists

• Re-enabled Discord account linking - forgot to do so prior to 5.2 launch

• Fixed recurrent activity job - it was looking at the old Events

• Fixed VA Staff seeing Pilot Registration Review page in Orwell when they were not supposed to

• Fixed an error which would occur when logging out whilst in Orwell

• Fixed route importer wrongly lowercasing route tags

• Lots and Lots n+1 query and lazy loading improvements and fixes

• Fixed Ruiting edit in Orwell where it would try to null out wrong column

• Fixed View Booking page for users with SimBrief dispatches from 5.0

• Fixed SimBrief Airline - ICAO setting in SimBrief Integration in Orwell was not being applied

• Fixed an issue with creating a Fleet in Orwell

• Fixed an issue with editing Activity in Orwell when it is Route based

• Fixed an issue of not being able to select activity when creating a Badge rewarding activity participation

• Fixed internal remarks not being applied on Route on creation or edit

• Fixed containers assigned to route not displaying correctly in Orwell

Things to Look Forward to

There are still some gremlins lurking - we will keep resolving bugs as they crop up. Keep making reports in Featurebase so we can fix them!

Once the initial bug squashing is complete, we have a list of highly requested Improvements to add - we will be dedicating some time for that before moving on to 5.3.

Bug Reporting

[Image: ]

When you see a message like this - please do click where it says ‘Please Click on me’ and log a bug report, describing what you were doing when the error happened.

Bugs submitted this way do not need to include VA Identifier, but we do need a description on how you got to the error so we could reproduce and fix.

It is very imporptant bugs are logged - when you get this message - please make the effort to submit a bug report - if it’s reported, it can be fixed. If it’s not reported - it will not be fixed any time soon, if ever.

Tour Logbooks

We fixed couple of issues yesterday and today with Tour Logbooks not getting the progress updated or carried over from 5.0;

Should you or your pilots experience it, first step would be to reprocess the PIREPs eligible for tour in order - leg 1, then leg 2 and so on - this should add it to activity logbook for the Pilot.

If that fails - please log a bug in Featurebase containing - Activity ID, Affected Pilot Username and VA Identifier.

Nightly Jobs - Discord Stats

For Virtual Airlines who have UTC as their timezone (new in 5.2), the midnight job and discord statistics messages did not fire at midnight UTC. We think we resolved this issue and it will run as scheduled tonight.

You may have noticed a drop in Pilot accounts - this would be because of how Frozen accounts are handled in 5.2 - they are now removed after 2 days instead of 60 - the nightly job which we ran at noon to catch up will have deleted all Frozen accounts which were over 2 days old, but younger than 60.

Other changes and fixes

• Added a fallbabck in PIREP Processing when we do not have touchdown position reports, so that PIREPs do not get rejected/invalidated with null landing rate.

• Fixed PIREPs not being logged towards Tour completion if the Tour had restrictions configured. If you have any PIREPs like this - reprocessing them in Orwell ought to add them to activity logbook.

• Fixed an issue with Airport Import unable to process SimBrief settings

• Fixed an issue where Airport Manager Bonus Point setting would not get saved in Orwell

• Fixed more lazy load issues (you don’t see it as errors, but we log occurences to improve vAMSYS as it basically reduces number of database queries we make)

• Fixed Flight Length and Flight Distance fields not auto-populating on route import

• Fixed Altitude field in import not being parsed from FL380 to 38000 and similar

• Increased the Live Flights histogram in Orwell dashboard from 2 weeks to 1 month

• Fixed an issue with ‘Flights From XXX’ table where it would not show some routes due to tag issue.

Maintenance release combined of some bug fixes and smaller changes.

• Improved: Upcoming Tour events will no longer show Book Flight button if event has not started yet

• Improved: Backend AIRAC update functionality

• Fixed: Custom VA Pages not taking into account honorary ranks

• Fixed: AIRAC route drawing was not including first and last waypoint of route and caused erroneus drawings outside the expected path

• Fixed: METAR fetching in some cases was throwing errors

• Fixed: View Phoenix Profile button was not among Pilot table actions

This changelog summarizes silent changes made since 5.0.21;

• Fix: Accepting Livery would not accept pending PIREPs in some cases;

• Fix: Remove billing address after VA Owner change;

• Fix: Tweaks to User GDPR Anonymization;

• Improvement: Billing page now accessible by VA Owners Onlyl

• Fix: Pilot table tweaks to not display pilot accounts from deleted users;

• Fix: Leaderboards would sometimes not display previous years correctly;

• Fix: Badge for visited airports would not be awarded correctly;

• Fix: Staff permissions regarding pilot bans/unbans were incorrect in Pilot Table;

• Improvement: Rudimentary simbrief aircraft id validation in Favortited Aircraft;

• Fix: Deleting hubs will not unset hub location for deleted pilots - was causing an issue when pilot account was restored;

• Fix: Live Flights table spacing issues;

• Fix: An issue with VA Initiated merges which would never complete;

• 5.2 Compatibility: PIREP Comments made in 5.0 get sent to 5.2

• Fix: Multiple Landing AutoReject was broken and would not store multiple landings detected;

• Improvement: Made changes to Changed VA redirect socket job, reduced access log write frequency;

• Improvement: Added validation rules when creating containers for Size and Weight; Size ‘large’ and weight ‘heavy’ are no longer accepted in form input.

• Fix: Honorary rank was not shown in the topbar when honorary rank is preferred;

• Fix: Duplicate event point awards when reflying last leg of the tour;

• Fix: Dispatch issue with luggage weight when not dispatching via SimBrief;

• Improvement: Tour events now show start date for upcoming routes;

• Fix: Aircraft editor did not show inherited CI value from Fleet;

• Fix: Restoring pilot profile without ‘reuse username’ may sometimes lead to strange usernames;

• Fix: Fixes to weight units sent to SimBrief;

• Improvement: Clarify weight units in Phoenix Dispatch being sent to SimBrief;

• Fix: Booking count in Aircraft Resource page in Phoenix;

• Fix: Importing airports now correctly requires airport name;

• Fix: Flight Map was confused about local/UTC timestamps in SDT/ADT

• Fix: Select Hub modal on first visit would sometimes show hubs from another airline

• Fix: Book Flight map’s Tag filter was applied incorrectly and was not filtering completely

• Fix: Double weight conversion in View Booking page when using imperial units

• Disabled Stand Creation in 5.0 due to Stand Project

• Fix: Correct date/time logging for Pegasus required files so they are not downloaded needlessly when there has been no update

• Improvement: Featurebase integration in Error pages and in Orwell → vAMSYS Support

• Fix: Text Editor could not insert links

• Improvement: Change how routes are parsed and drawn on the map

• Disabled Pegasus Flight Map

• Fix: Danger alert did not have styling applied


Say Hello to a Smoother Flight Planning Experience

We’re thrilled to share that vAMSYS v5.1 Beta is finally here, bringing with it an all-new SimBrief and Navigraph integration that we think you’re really going to love. Here’s what’s new:

• **Easy Account Linking:**

Simply connect your Navigraph account, and if you’re a SimBrief user, your flight planning just got a whole lot simpler.

• **Better Maps for Navigraph Unlimited Subscribers:**

Enjoy improved airport maps loaded with new layers showing stands, taxiways, runways, de-ice zones, and more.

• **Cool SimBrief Features:**

- Your custom SimBrief Aircraft Profiles now sync directly to vAMSYS for a seamless dispatch process.

- You can preview your Operational Flight Plan (OFP) before taking off, making it a breeze to tweak payloads, fuel, or inspect TLR details.

- When you’re ready, the OFP is generated in the background, and any tweaks you make on SimBrief.com sync back automatically.

- Plus, Virtual Airlines can now set up fuel and cost overrides per fleet or aircraft, and your SimBrief OFP data sticks around for future reference.

Meet the new Orwell

We’ve given Orwell a complete makeover. Everything you need—from managing airports and fleets to handling sceneries—is now in one intuitive place. It might feel a bit different at first, but we’re sure you’ll grow to love the streamlined setup:

• **Everything in One Place:**

No more jumping between different systems. Manage hubs, fleets, and more all from Orwell.

• **New VA Statistics Page:**

Check out live flight histograms, PIREP review charts, fleet logbooks, and detailed airport movement tables. Play around with the date filters to see exactly what you need.

Heads-Up on What’s Missing

Since this is a beta release, there are a couple of things we’re still working on:

• **Stands Functionality:** Currently taking a backseat.

• **Importers/Exporters:** Not available just yet.

What Else Has Changed?

• **Airports:**

- New Airport Briefing URL linking to Phoenix resources.

- Bulk actions now let you manage base toggles, categories, and more.

• **Email Tweaks:**

- Subject lines can now include variables.

• **Global Search:**

- Find pilots, PIREPs, events, and more with our upgraded search feature.

• **Keyboard Shortcuts:**

- CTRL+K opens search, and CTRL+S saves your forms.

• **Navigraph AMDB Integration:**

- Enhanced airport maps with detailed layers.

• **SimBrief v2 Integration:**

- All the new SimBrief features are up and running.

• **Live Flights Histogram:**

- See real-time flight data like never before.

• **Enhanced PIREP and Payload Features:**

- Check out the new chart on the PIREP review page and improved random payload generation.

• **Callsign and Rank Updates:**

- Now you can use the aircraft registration or pilot username as your callsign, with rank abbreviations appearing upfront.

• **Commenting Improvements:**

- New comment options and presets on PIREP Claims and Registration Reviews.

• **Operational Boosts:**

- Runway detection, route-level overrides for PAX and bag weights, improved imperial unit support, and an experimental timezone feature for overnight actions.

• **UI Overhauls:**

- Redesigned Dispatch, PIREP View, and Review pages, plus a fresh Bookings page and more.

• **And so much more to explore…**

Feature: VA Pilot Account Merge Tool

In Orwell Pilot Table, VA Staff can now select and merge Pilot Accounts. This tool should be used as last resort and users should merge their user accounts.

This tool does not combine user accounts - meaning their network IDs, discord linking etc will not transfer - for that to happen user needs to perform full account merge.

Improvements:

• Take into consideration deleted pilot accounts when performing user account merge

• Exclude vAMSYS Robot from Leaderboards

• Add Year-To-Date leaderboard

• Add Historical leaderboard for previous years

• Show luggage weight in View Booking page

Fixes:

• Incorrect action applied when performing bulk ignore action in Livery Review in Orwell

• Process Pilot Invites one at a time, resolving potential duplicate pilot username assignment

We're thrilled to share exciting updates in vAMSYS Version 5.0.21! This release introduces notable features and improvements for enhanced user experience.

New Feature

VA Pilot Account Merge Tool

• Allows VA Staff to merge Pilot Accounts in the Orwell Pilot Table.

• Note: User networks or third-party integrations are not combined. Users must perform a full account merge for integrated feature continuity.

Improvements

• Consideration of deleted pilot accounts during user account merge actions.

• Exclusion of the vAMSYS Robot from leaderboard calculations.

• Addition of Year-To-Date and Historical leaderboards for previous years.

• Display of luggage weight on the 'View Booking' page.

Fixes

• Resolved incorrect actions during the bulk ignore function in Livery Review (Orwell).

• Improved invite processing to address events of duplicate pilot username assignment.

Fixes:

• Pilots not being correctly removed from linked Discords

• vAMSYS Staff being bannable

• Pending Pilot applications were not removed on User merge

• Book flight airport selector fix in case of no jumpseat options

• Visual issue with airport based tours not always registering as complete if route start date is null

• Issue with transfer PIREPs not always submittable

• Ensure staff entry is deleted when user is deleted

• Make Social Icons not collapsed in Orwell

• Make custom Buttons in Phoenix dashboard not grow in certain configurations

• Deleted aircraft were not being counted in profile most used aircraft

• Online Network remarks not sent to IVAO

• Incorrect display of aircraft being booked when dispatching

Improvements:

• NOTAM content formating

• Change Select page to grid layout for different display order of 'big' airlines

• Increase import line limit to 30k

• Breakdown STD, ATD, STA and ETA times in Flight Map and API

Fixes:

• Pilots not being correctly removed from linked Discords

• vAMSYS Staff being bannable

• Pending Pilot applications were not removed on User merge

• Book flight airport selector fix in case of no jumpseat options

• Visual issue with airport based tours not always registering as complete if route start date is null

• Issue with transfer PIREPs not always submittable

• Ensure staff entry is deleted when user is deleted

• Make Social Icons not collapsed in Orwell

• Make custom Buttons in Phoenix dashboard not grow in certain configurations

• Deleted aircraft were not being counted in profile most used aircraft

• Online Network remarks not sent to IVAO

• Incorrect display of aircraft being booked when dispatching

Improvements:

• NOTAM content formating

• Change Select page to grid layout for different display order of 'big' airlines

• Increase import line limit to 30k

• Breakdown STD, ATD, STA and ETA times in Flight Map and API

Discord-Related Fixes:

• **Discord Daily Statistics Summaries heading date was off by a day**: Corrected an issue where the heading date in daily statistics summaries was showing the wrong day.

• **Possible to link several users to the same Discord account**: Resolved a bug allowing multiple user accounts to be linked to the same Discord account.

• **User Merge would not merge linked Discord account**: Ensured that merging user accounts now correctly includes linked Discord accounts.

Route and Dispatch Management:

• **Route Importer would insert current time if departure or arrival time was empty**: Fixed default behavior when route times were left empty during import.

• **Tag filter in VDS Routes contains tags from deleted routes**: Updated the tag filter logic to exclude tags associated with deleted routes.

• **On SB Dispatch alternates number not sent to SB**: Corrected the dispatch logic to include the number of alternates in the data sent.

Pilot Management:

• **Ignore deleted users when validating online network ID uniqueness**: Ensured that deleted users are ignored when checking for unique online network IDs.

• **When banning a user, apply ban to deleted pilot accounts too in case of restore in the future**: Enhanced the banning process to apply bans to deleted pilot accounts as well.

• **Pilot Restore would sometimes not reset activity grace**: Fixed a bug that prevented resetting the activity grace period when restoring a pilot account.

• **Halt Pilot deletion for not meeting activity requirements if they have/had active flight in the last 30 minutes**: Safeguard added to stop pilot deletions if the pilot has recently been in-flight.

• **Halt Pilot deletion for not meeting activity requirements if they have a PIREP in processing or pending review**: Prevents deletion of pilots with pending or processing PIREPs.

• **It is possible to create multiple pilot invites for the same user when invite is already pending**: Restricted duplicate invites for a user who already has a pending invite.

Permissions and Security:

• **It is possible to ban VA Owner and VA Staff**: Corrected an issue allowing bans on VA Owners and Staff when it should be restricted.

• **Ban/Unban not properly tied to Staff permissions**: Ensured that the ability to ban/unban is now tied to proper staff permissions.

Rank, Badge, and Tour Management:

• **When editing a Rank PIREP requirements cannot be edited**: Resolved an issue preventing changes to PIREP requirements for ranks during editing.

• **Badge expected 'greater than' in PIREP count evaluation and not greater than or equal to**: Fixed badge logic to include "equal to" in PIREP count evaluations.

• **Tour would not register as complete in some cases where leg was flown more than once**: Ensured tours are marked complete even when legs are flown multiple times.

• **It is possible to create a tour with no legs**: Added validation to prevent creating tours without any legs.

Billing and Plans:

• **Billing page text descriptions not recognizing plans between per year and per month**: Addressed confusion in recognizing annual versus monthly plans.

System Performance and Stability:

• **Orwell Pilot list column sort error**: Fixed issues with sorting columns in the pilot list.

• **Memory Issues in VDS Routes and Orwell PIREP list tables**: Optimized tables to reduce memory consumption and improve stability.

• **PIREP Points sum would not update after adding Social Points for Group Flight or Shared Cockpit**: Ensured that PIREP points are recalculated correctly after adding social points.

Discord-Related Fixes:

• Discord Daily Statistics Summaries heading date was off by a day: Corrected an issue where the heading date in daily statistics summaries was showing the wrong day.

• Possible to link several users to the same Discord account: Resolved a bug allowing multiple user accounts to be linked to the same Discord account.

• User Merge would not merge linked Discord account: Ensured that merging user accounts now correctly includes linked Discord accounts.

Route and Dispatch Management:

• Route Importer would insert current time if departure or arrival time was empty: Fixed default behavior when route times were left empty during import.

• Tag filter in VDS Routes contains tags from deleted routes: Updated the tag filter logic to exclude tags associated with deleted routes.

• On SB Dispatch alternates number not sent to SB: Corrected the dispatch logic to include the number of alternates in the data sent.

Pilot Management:

• Ignore deleted users when validating online network ID uniqueness: Ensured that deleted users are ignored when checking for unique online network IDs.

• When banning a user, apply ban to deleted pilot accounts too in case of restore in the future: Enhanced the banning process to apply bans to deleted pilot accounts as well.

• Pilot Restore would sometimes not reset activity grace: Fixed a bug that prevented resetting the activity grace period when restoring a pilot account.

• Halt Pilot deletion for not meeting activity requirements if they have/had active flight in the last 30 minutes: Safeguard added to stop pilot deletions if the pilot has recently been in-flight.

• Halt Pilot deletion for not meeting activity requirements if they have a PIREP in processing or pending review: Prevents deletion of pilots with pending or processing PIREPs.

• It is possible to create multiple pilot invites for the same user when invite is already pending: Restricted duplicate invites for a user who already has a pending invite.

Permissions and Security:

• It is possible to ban VA Owner and VA Staff: Corrected an issue allowing bans on VA Owners and Staff when it should be restricted.

• Ban/Unban not properly tied to Staff permissions: Ensured that the ability to ban/unban is now tied to proper staff permissions.

Rank, Badge, and Tour Management:

• When editing a Rank PIREP requirements cannot be edited: Resolved an issue preventing changes to PIREP requirements for ranks during editing.

• Badge expected 'greater than' in PIREP count evaluation and not greater than or equal to: Fixed badge logic to include "equal to" in PIREP count evaluations.

• Tour would not register as complete in some cases where leg was flown more than once: Ensured tours are marked complete even when legs are flown multiple times.

• It is possible to create a tour with no legs: Added validation to prevent creating tours without any legs.

Billing and Plans:

• Billing page text descriptions not recognizing plans between per year and per month: Addressed confusion in recognizing annual versus monthly plans.

System Performance and Stability:

• Orwell Pilot list column sort error: Fixed issues with sorting columns in the pilot list.

• Memory Issues in VDS Routes and Orwell PIREP list tables: Optimized tables to reduce memory consumption and improve stability.

• PIREP Points sum would not update after adding Social Points for Group Flight or Shared Cockpit: Ensured that PIREP points are recalculated correctly after adding social points.


vAMSYS 5.0.17 and 5.0.18 have been released to the public.

User Account Improvements

5.0.18 carries on with additions introduced in 5.0.17 and reworks User Management page.

Users can now see their global statistics across all VAs they are in.

Various other tweaks and bug fixes

• Added filters to Profile Map for Flight Type, Aircraft Type, Operator and Tags

• Added date selection modifiers for quick changes +/- month/year, register date and Today

• Profile map start date defaults to show last 100 PIREPs by default, if that many are available

• Added notifications to My Profile and Account Settings if there are pending friend requests

• Clicking on Leaderboard user will now open profile page in the same tab

• Added forgotten Rank Transfer options from 5.0.17 to the My Profile -> Preferences Page

• Logbook is now sorted by flight count, not aircraft type

• Phoenix Event description uses more Markdown formatting options

• Added Server selector at the bottom of the page where 'Served By' lives

vAMSYS 5.0.17 and 5.0.18 have been released to the public.

User Account Improvements

5.0.18 carries on with additions introduced in 5.0.17 and reworks User Management page.

Users can now see their global statistics across all VAs they are in.

Various other tweaks and bug fixes

• Added filters to Profile Map for Flight Type, Aircraft Type, Operator and Tags

• Added date selection modifiers for quick changes +/- month/year, register date and Today

• Profile map start date defaults to show last 100 PIREPs by default, if that many are available

• Added notifications to My Profile and Account Settings if there are pending friend requests

• Clicking on Leaderboard user will now open profile page in the same tab

• Added forgotten Rank Transfer options from 5.0.17 to the My Profile -> Preferences Page

• Logbook is now sorted by flight count, not aircraft type

• Phoenix Event description uses more Markdown formatting options

• Added Server selector at the bottom of the page where 'Served By' lives

[vAMSYS 5.0.17 is now available for Public Testing on vAMSYS Next](https://next.vamsys.io)

We're excited to announce that **5.0.17** marks the first vAMSYS v5 release with a public beta testing period. Moving forward, we plan to leverage public testing more frequently to gather valuable feedback on new features and improvements.

A few important points to note for this initial public beta:

• **Shared Database**: vAMSYS Next and vAMSYS.io operate on the same database. Any actions taken on vAMSYS Next will be immediately reflected on the main vAMSYS.io platform

• **Open Access**: vAMSYS Next is available to all vAMSYS users

Pilot Profile Rework

My Profile

The **My Profile** section has been restructured into several dedicated pages:

• **Dashboard**: The previous "My Profile" page

• **Map**: A new flight history map

• **Statistics**: Charts showcasing your pilot statistics

• **Badges**: Displays badges (or awards, depending on your VA's terminology) you've earned

• **PIREPs**: A list of your PIREPs, relocated from the Flight Centre

• **Claims**: Your PIREP Claims, also moved from the Flight Centre

• **Preferences**: Manage your pilot-specific preferences

• **Account Settings**: Redirects to vAMSYS Auth for managing account details

Dashboard

• The **Statistics Breakdown** no longer includes a Settings tab

• The **Details Section** has been streamlined, and the Hub Change button now includes a tooltip explaining its purpose

• **Popular Aircraft** are now tracked based on PIREPs rather than bookings

• The Badge Breakdown has been moved to the bottom of the page

• The **Bookings Table** has been removed

Map

The long-anticipated **Flight History Map** is back, now better than ever and in full-page view

• Displays all your flights within a selected period (default: one month ago to today)

• Offers visualization options for both great circle routes and actual flight paths

Statistics

Introducing the **Pilot Statistics Center**, complete with detailed charts:

• **Aircraft Types**: Types used in PIREPs

• **Callsigns**: ICAO callsign prefixes used

• **Network**: Networks where flights were booked

• **Departures**: Day/night departure breakdown

• **Route Types**: Types of routes flown

• **Simulators**: Simulators used

• **Event Flights**: PIREPs with bonus points

• **Landings**: Day/night landing breakdown

• **Flights**: PIREPs flown per month (starting from your registration date)

• **Landing Rate**: Average landing rate per month

• **Logbook**: A detailed text summary of your aircraft types, total flights, passengers and freight carried, air time, distance flown, fuel used, and day/night takeoff/landing stats

Badges

For now, this page offers a basic breakdown similar to the one on the Dashboard. We plan to expand its functionality in the future.

Preferences

The previous settings drawer has been replaced with a full-page interface, retaining all previous options:

• Use Imperial Units

• Prefer Honorary Rank

• Preferred Network (pre-selected for dispatch)

• **SimBrief OFP Format**: Now always visible. If the VA disabled pilot overrides, it shows the default set by the VA. Otherwise, pilots can choose their preferred format

• **Delete Pilot Account**: Initiates a 60-day freeze before deletion

**New in 5.0.17**: If not disabled by your VA, pilots can now **Reset Pilot Account**. This option, requiring password confirmation, removes all bookings and PIREPs from your account. These records are reassigned to the VA's Robot Pilot to preserve overall VA statistics.

VAs can disable this option in Orwell -> Settings -> Airline -> Pilot -> Enable Pilot Account Reset toggle.

Day/Night Departures & Arrivals

vAMSYS 5.0.17 introduces a feature to evaluate whether your departures and landings occurred during day or night.

• This determination uses the airport's location and the times recorded on your PIREP to calculate whether the flight occurred before or after civil twilight

• Note: If your simulator is not set to real local time, these evaluations may be inaccurate, as we can't track simulator time

Testing Required

We've updated how **Profile Map**, **Book Flight Map**, and **Destination Maps** load and navigate. These maps now leverage navigation methods used in other areas of vAMSYS, eliminating the need for full-page refreshes.

If you experience issues where a map fails to load:

1. Hit **F5** to refresh the page

2. If the map loads after refreshing, try retracing your steps

3. If the issue recurs, report it to your VA Staff or Vision with **precise steps to reproduce the error**. Detailing each click and action is crucial for diagnosing the problem

Various other tweaks and bug fixes

• Updated Trigger Event for Flaps/Engine scorers to clarify the 30kts speed threshold

• Landing points are now limited to whole numbers; fractional points are no longer allowed

• SimBrief now supports fuel calculations in kilograms. Conversions have been implemented in vAMSYS for users preferring KG

• Multiple improvements to Tours Event pages, including correct leg sorting and hiding completed legs

• Switched to a cloud-based map tiles provider for enhanced performance and reliability

• Fixed an issue where activity grace periods were not removed when restoring a pilot account

• Disabled PIREP point editing when no scoring group is attached to the fleet used for the PIREP

• Resolved issues with holiday cancellations not fully restoring unused days

• Fixed validation of network IDs to prevent conflicts with deleted user accounts

• Removed the Pilot Data Export feature

• Social icon URLs now require a full URL, including the `https://` prefix

• Fixed a bug allowing pilot registrations for VAs on trial

• Addressed a rare issue where the Profile page failed to load due to missing booking data

We're excited to announce that 5.0.17 marks the first vAMSYS v5 release with a public beta testing period. Moving forward, we plan to leverage public testing more frequently to gather valuable feedback on new features and improvements.

A few important points to note for this initial public beta:

• Shared Database: vAMSYS Next and vAMSYS.io operate on the same database. Any actions taken on vAMSYS Next will be immediately reflected on the main vAMSYS.io platform

• Open Access: vAMSYS Next is available to all vAMSYS users

Pilot Profile Rework

My Profile

The My Profile section has been restructured into several dedicated pages:

• Dashboard: The previous "My Profile" page

• Map: A new flight history map

• Statistics: Charts showcasing your pilot statistics

• Badges: Displays badges (or awards, depending on your VA's terminology) you've earned

• PIREPs: A list of your PIREPs, relocated from the Flight Centre

• Claims: Your PIREP Claims, also moved from the Flight Centre

• Preferences: Manage your pilot-specific preferences

• Account Settings: Redirects to vAMSYS Auth for managing account details

Dashboard

• The Statistics Breakdown no longer includes a Settings tab

• The Details Section has been streamlined, and the Hub Change button now includes a tooltip explaining its purpose

• Popular Aircraft are now tracked based on PIREPs rather than bookings

• The Badge Breakdown has been moved to the bottom of the page

• The Bookings Table has been removed

Map

The long-anticipated Flight History Map is back, now better than ever and in full-page view

• Displays all your flights within a selected period (default: one month ago to today)

• Offers visualization options for both great circle routes and actual flight paths

Statistics

Introducing the Pilot Statistics Center, complete with detailed charts:

• Aircraft Types: Types used in PIREPs

• Callsigns: ICAO callsign prefixes used

• Network: Networks where flights were booked

• Departures: Day/night departure breakdown

• Route Types: Types of routes flown

• Simulators: Simulators used

• Event Flights: PIREPs with bonus points

• Landings: Day/night landing breakdown

• Flights: PIREPs flown per month (starting from your registration date)

• Landing Rate: Average landing rate per month

• Logbook: A detailed text summary of your aircraft types, total flights, passengers and freight carried, air time, distance flown, fuel used, and day/night takeoff/landing stats

Badges

For now, this page offers a basic breakdown similar to the one on the Dashboard. We plan to expand its functionality in the future.

Preferences

The previous settings drawer has been replaced with a full-page interface, retaining all previous options:

• Use Imperial Units

• Prefer Honorary Rank

• Preferred Network (pre-selected for dispatch)

• SimBrief OFP Format: Now always visible. If the VA disabled pilot overrides, it shows the default set by the VA. Otherwise, pilots can choose their preferred format

• Delete Pilot Account: Initiates a 60-day freeze before deletion

New in 5.0.17: If not disabled by your VA, pilots can now Reset Pilot Account. This option, requiring password confirmation, removes all bookings and PIREPs from your account. These records are reassigned to the VA's Robot Pilot to preserve overall VA statistics.

VAs can disable this option in Orwell -> Settings -> Airline -> Pilot -> Enable Pilot Account Reset toggle.

Day/Night Departures & Arrivals

vAMSYS 5.0.17 introduces a feature to evaluate whether your departures and landings occurred during day or night.

• This determination uses the airport's location and the times recorded on your PIREP to calculate whether the flight occurred before or after civil twilight

• Note: If your simulator is not set to real local time, these evaluations may be inaccurate, as we can't track simulator time

Testing Required

We've updated how Profile Map, Book Flight Map, and Destination Maps load and navigate. These maps now leverage navigation methods used in other areas of vAMSYS, eliminating the need for full-page refreshes.

If you experience issues where a map fails to load:

1. Hit F5 to refresh the page

2. If the map loads after refreshing, try retracing your steps

3. If the issue recurs, report it to your VA Staff or Vision with precise steps to reproduce the error. Detailing each click and action is crucial for diagnosing the problem

Various other tweaks and bug fixes

• Updated Trigger Event for Flaps/Engine scorers to clarify the 30kts speed threshold

• Landing points are now limited to whole numbers; fractional points are no longer allowed

• SimBrief now supports fuel calculations in kilograms. Conversions have been implemented in vAMSYS for users preferring KG

• Multiple improvements to Tours Event pages, including correct leg sorting and hiding completed legs

• Switched to a cloud-based map tiles provider for enhanced performance and reliability

• Fixed an issue where activity grace periods were not removed when restoring a pilot account

• Disabled PIREP point editing when no scoring group is attached to the fleet used for the PIREP

• Resolved issues with holiday cancellations not fully restoring unused days

• Fixed validation of network IDs to prevent conflicts with deleted user accounts

• Removed the Pilot Data Export feature

• Social icon URLs now require a full URL, including the https:// prefix

• Fixed a bug allowing pilot registrations for VAs on trial

• Addressed a rare issue where the Profile page failed to load due to missing booking data

View Event page changes for Tours

• Leg information in the sidebar replaced with a sorted list of airports involved in the tour

• Added Event Routes/Airports & Status table at the bottom of the page:

• Table lists all legs in order

• Route based Tours additionally list Callsign, Flight Number, Flight Length and Distance

• Legs flown are indicated as flown and also have a View PIREP button

• Legs to be flown have a book flight button if not booked, or View Booking if already booked

• In case of event restrictions and Airport based Tour - Book Flight button applies the restrictions as set by the event to the Flight Dispatch list

• In case of Route based Tour, Book Flight button only offers the selected route to be dispatched

Presence of Book Flight button does not mean that all qualifying PIREPs need to be booked via event page - if all event conditions are met, it does not matter whether booking was made via Flight Centre or via Event page.

Various other tweaks and bug fixes

• Route Exporter bugfix - it was not exporting routes with no routing

• Holidays being cancelled would not return unused days

• Rejecting Liveries in Livery Review would always apply an invalidate action on pending PIREPs

• Removed helpdesk submission form in Orwell until it can be implemented natively

• Landing Rate AutoRejects being applied incorrectly if landing rate is 0 and related adjustments

• Minor query improvements across event and Phoenix PIREP list pages

View Event page changes for Tours

• Leg information in the sidebar replaced with a sorted list of airports involved in the tour

• Added Event Routes/Airports & Status table at the bottom of the page:

• Table lists all legs in order

• Route based Tours additionally list Callsign, Flight Number, Flight Length and Distance

• Legs flown are indicated as flown and also have a View PIREP button

• Legs to be flown have a book flight button if not booked, or View Booking if already booked

• In case of event restrictions and Airport based Tour - Book Flight button applies the restrictions as set by the event to the Flight Dispatch list

• In case of Route based Tour, Book Flight button only offers the selected route to be dispatched

Presence of Book Flight button does not mean that all qualifying PIREPs need to be booked via event page - if all event conditions are met, it does not matter whether booking was made via Flight Centre or via Event page.

Various other tweaks and bug fixes

• Route Exporter bugfix - it was not exporting routes with no routing

• Holidays being cancelled would not return unused days

• Rejecting Liveries in Livery Review would always apply an invalidate action on pending PIREPs

• Removed helpdesk submission form in Orwell until it can be implemented natively

• Landing Rate AutoRejects being applied incorrectly if landing rate is 0 and related adjustments

• Minor query improvements across event and Phoenix PIREP list pages