Changelog

MTOW/MLW Scorer Changes

It’s a breaking change; Existing MTOW and MLW Scorers were removed.

[Image: ]

• Bound enforcement can be configured from both, only over or only under

• Weight Source can be configured between SimBrief (planned) or Structural.Structural MTOW and MLW weights are taken from Aircraft → SimBrief Overrides and, if not available, from Fleet → SimBrief Overrides.

• Removed unnescessary Under/Over value limits.

Taxi Overspeed Scorer & AutoReject

[Image: ]

Added Scorer to Penalise Taxi Overspeed events (or reward for no overspeeding)

• Evaluation can be done on All events (i.e. total time spent in taxi overspeed condition) or one event (i.e. maximum allowed overspeed for one overspeed event)

• Rule name and points configurable for each scoring type

AutoReject can be configured to perform action on PIREP with similar configuration options.

Pegasus v2 operates on fixed taxi speed maximum of 30kts and this cannot be currently changed.

Other Scorer & AutoReject Changes:

• Shared Cockpit Scorer can now be set to add points as Bonus Points instead of regular points.

• Engine Start Sequence scoring rules gained the options to:

• Flap Scoring Rules can now be configured to accept ‘Human’ values; For compatible addons, Pegasus v2 will record Flap position in human value - for example -

  "UP", "0", "DIAL-A-FLAP", "6°", "11°", "0", "1", "1+F", "2", "3", "FULL" and so on; These values can now be used to configure the scorer, eliminating inconsistencies between flap levels among addons of the same aircraft type.

• All AutoRejects which have Type Override option have gained an option to provide custom rule name which will be shown in the PIREP review.

• Added Scoring Rules Overview table under Scoring Groups; It shows all the configured rules, the Scoring Groups it’s enabled in and has an option to delete the scoring rule from selected scoring groups.

Departures in next x hours

[Image: ]

[Image: ]

[Image: ]

Added an option to enable Departures in next x hours filtering via Orwell → Settings → Booking & Dispatch.

VAs can configure this to their needs with custom min/max times; For the options to be available, Route Times must be enabled and populated.

Other fixes and changes:

• Improved flight dispatch page loading speed (VAMSYS-D, VAMSYS-2F)

• Improved airport information loading speed

• Fixed broken links throughout the system

• Added validation to prevent invalid callsigns and flight numbers (VAMSYS-1DP)

• Fixed Discord integration errors when airline data is missing

• Fixed email errors when sending pilot removal notifications (VAMSYS-1DQ)

• Prevented system from sending emails to deleted user accounts (VAMSYS-1CZ)

• Fixed live flights display errors

• Fixed errors when accessing routes with invalid IDs (VAMSYS-1CB)

• Fixed background job errors when restoring pilot accounts (VAMSYS-AF)

• Fixed errors when generating route callsigns

• mproved system performance when loading activity history (VAMSYS-1DH)

• Improved error messages when Discord authorization is denied

• Fixed errors from outdated statistics data

• Improved error tracking and reporting system

Converted 3 more Event related maps to our new map arhitecture;

Converted Orwell Airport map to the new map architecture;

1 more map remains - the My Profile flight map.

Known issues:

• Book Flight, Available Destination and Live Flight Maps have interactivity issues in iOS devices - iPhones and iPads; We are still investigating cause of this issue;

And to think it was 5.3.10 ~48 hours ago.

New Scorers:

• On-Time Route Departure

• Missed Route Departure Time

• On-Time Route Arrival

• Missed Route Arrival Time

Similar to the previous Booking time scorers, but these are based on the VA populated route departure and arrival times.

With 5.3.15 Route Departure and Arrival times must now be entered in UTC:

[Image: ]

For the VAs who chose to enter these times in Local timezone - after convering to UTC (manually, via Export/Import or API) - you can enable ‘Show Local Route Times’ setting in Orwell → Settings → Booking & Dispatch → Dispatch Functions

[Image: ]

When enabled, Route tables will list the ETD and ETA in Local time, with hover revealing UTC:

[Image: ]

Route table filters will filter in Local time as well, Dispatch page will also show local time.

Thrice in 24 hours; Tackling some of the low hanging fruit from Featurebase suggestions:

• Changed - PIREP Filter in Orwell to use Select field in Departure/Arrival Filters

• New - Preparations for vAMSYS-wide notification of Pegasus v2 once v1 is shut

• New - Added Shared Cockpit information in Takeoff/Landing message sent in Discord

• Changed - In Airport Setup in Orwell, changed maximum container count in select to 500

• New - Redesigned Login, Register and similar pages

• Changed - PIREP pages now have a bullet point list of triggered AutoRejects

• New - Aircraft Resource Page in Phoenix - Added links to tracker websites for aircraft registration; Only shows tracker services enabled for dispatch page

• New - Added Updated column in Airport Resource table in Phoenix and Orwell

New - Stabilzed Approach Criteria at Altitude Gates Scorer - in BETA

See documentation for it here.

It is a Beta scorer - there may be errors or issues - our recommendation is to set it up to your liking and set point rewards/deductions to 0 during testing so that pilots are not affected in case of issues;

Another good idea would be to set up the rules and then go over some of the already filed Pegasus v2 PIREPs (you can easily tell them apart by the presence of G value in said column in PIREP table in Orwell) to test if it works as you expect.

Please report all issues regarding the scorer to Featurebase Bugs. Thank you.

Small update to assist VAs migrating from FPM to G only scoring; Currently, FPM and G landing scorers will be applied to Pegasus v2 PIREPs.

If your plan is to migrate to G only scoring and you do not wish to apply FPM scorers to Pegasus v2 PIREPs - there is a temporary setting in Orwell → Settings → Reward Settings

[Image: ]

Pegasus v2 Landing Scorer - G Only - once enabled, it will not apply FPM scorer on Pegasus v2 PIREPs.

This toggle will go away by 1st November - giving you ample time to remove FPM scorer from the scoring groups if you wish not to keep FPM based rewards.

Additional Autoreject and Scorer options added:

AutoRejects:

• Liftoff Roll Excessive - Triggers when the aircraft roll magnitude during liftoff exceeds acceptable limits.

• Liftoff Pitch Excessive - Triggers when the maximum aircraft pitch during liftoff is outside acceptable limits.

• Takeoff Above MTOW - Triggers when takeoff weight exceeds the Maximum Takeoff Weight (MTOW) from SimBrief plus tolerance.

• Landing Above MLW - Triggers when landing weight exceeds the Maximum Landing Weight (MLW) from SimBrief plus tolerance.

Scorers:

• Liftoff Pitch Outside Range

• Liftoff Pitch Within Range

• Liftoff Roll Outside Range

• Liftoff Roll Within Range

• Takeoff Weight Outside MTOW

• Takeoff Weight Within MTOW

• Landing Weight Outside MLW

• Landing Weight Within MLW

All MTOW/MLW scorers and autorejects require a SimBreif OFP dispatched via vAMSYS or imported prior to flight.

We are happy to announce that Pegasus v2 is going public.

There are some mandatory actions Virtual Airlines need to take - we cover them in Pegasus v2 Launch | Your Actions Needed notice in Orwell. Please login to your Orwell Dashboard and execute as soon as you can - within the next 7 days.

[Image: ]

Pegasus Changes

Pegasus v2 is a complete rebuild and shares very little with v1. Major improvements:

• Improved layout - less bulky, just as intuitive.

• Flap Detection - for most aircraft we will now also have accurate Flap value name - i.e. Flaps value of 2 will be shown as Flaps 15 and so on.

• Improved FSUIPC stability - our interface with FSUIPC changed to be more stable and less error prone; Users are still urged not to run Pegasus/FSUIPC/Sim as admin - if they do - they then need to run everything as admin.

• MSFS 2024 Support - we now correctly detect liveries used in MSFS 2024.

• Landing Rate G-force - we now also record and detect G force on landing, sampled at 40Hz

• Improved runway turnoff and taxi start detection on landing

• Expanded landing summary messages

• Many other changes too on a new solid foundation which we will expand in the future.

vAMSYS 5.3.10 - Map Changes

We have rewritted Available Destinations, Book Flight, Live Flights, Booking and PIREP maps on our new architecture;

This has added tons of new interactivity, improved filtering and a host of other features.

It is best if you explore these 4 maps yourself to see the differences and changes; The 3 key maps - Book Flight, Live Flights and Available Destinations also have a helper modal which will show on the first load to brief you on the new maps;

We will upgrade the remaining maps over the course of the year;

Orwell → Important Notices

[Image: ]

We have added Important Notices section to Orwell, to higlight important changes, breaking changes or any other important information one needs to be aware of; In essence, it replaces/supplements our Discord Announcements.

Statistics Rewrites

As part of our ongoing efforts to streamline vAMSYS operation, we were optimising our database queries for maximum performance. Everything to do with statistics generation were proving to be a bottleneck. With 5.3.9 we have addressed it by completely changing how statistics are stored and calculated.

They are now real-time everywhere, including Leaderboards.

This required an update to Pilot Profile and Phoenix Dashboard Statistics modules:

[Image: ]

[Image: ]

Changing tabs will load the revelant data for said tab.

In Phoenix Dashboard, the Details tab was replaced with the link to Pilot Profile.

Leaderboard Changes

[Image: ]

Leaderboards (Phoenix → Community → Leaderboard) has been completely rewritten to utilise our changes to the max.

It is now one table; At the top - you can change between various leaderboard types enabled by the VA:

[Image: ]

The Leaderboard has tab toggles for various time periods and Sort By selectors.

Most importantly, the Leaderboard is now not limited to 20 people - you can see exactly where you are in the table, as well as in the blue summary box.

And finally, a feature suggested more than 8 years ago is also finally in - the Change column, showing how position in the leaderboard changed period to period.

API Changes

With the changes to statistics, it is now time to speed up migration to API v3 and retire old APIs - we posted a note about this in the Orwell Dashboard.

API v3 has a breaking change where /operations/statistics endpoint has been retired; For a short period of time /operations/statistics-legacy is available.

Pilots can now automatically lookup and select which aircraft flew their route recently using real-world FlightRadar24 data.

Airline Admins

This feature can be enabled/disabled in: Orwell → Settings → Booking & Dispatch → Dispatch Extras → Enable FR24 Aircraft Lookup

How It Works

When booking a flight, click the "Lookup from FR24" button next to the aircraft selector. The system will:

1. Query FlightRadar24 for recent flights matching your flight number

2. Find the most recently landed aircraft's registration

3. Automatically select that aircraft (if present)

Querying the Flight Radar data is done by your browser, not our servers

Where to Find It

The FR24 lookup button appears in two locations:

• Aircraft Picker modal - When initially selecting an aircraft

• Dispatch Details section - The main aircraft dropdown after initial selection

Privacy & Technical Details

The aircraft lookup is performed directly by your web browser, not by vAMSYS servers. When you click the lookup button:

• Your browser contacts FlightRadar24 (FR24 sees your personal IP address)

• You receive the flight data

• Your browser sends the response back to vAMSYS for setting the selector field

✅ Respects your current fleet filters and availability restrictions

✅ Prioritizes fresh data, falls back to historical cache if API is unavailable

✅ Shows clear notifications:

• Success: "Found [registration] and auto-selected"

• Not Available: "Found [registration] but it's not available in your fleet" (aircraft exists but is filtered out, already booked, or not in your fleet)

• Not Found: "No recent flights found for this flight number"

• Orwell - Rewards → Scoring Groups → Scoring Group. Added option to copy individual scoring rules to other Scoring Groups

• Orwell - Pilots → List:

• Orwell - Routes → Routes:

• Orwell - Data → Exports:

• Phoenix - Dispatch Table and Dispatch Page:

• Phoenix - Documents → Scores - Scoring Groups ordered by name of the group.

• PIREP Processor: Fixed an issue where PIREPs would get stuck in Scoring when a badge is to be awarded and it does not have an image.

• Airport Briefing URL - 255 character limit removed

Small maintenance update:

• Improvement: Rutes in Orwell can now be sorted by ID

• Fix: Some Activities, in the activities page listing only 1 route when multiple are available.

• Fix: Route Create/Update error in API

• Fix: Bonus Sum calculation error for statistics

• Fix: Bonus Point rewards for Activities which should not have rewarded points

• Fix: Badge award Discord Notification

• Fix: PIREP Bonus Point editor throwing error when PIREP has no existing bonus points.

Small maintenance update:

• Internal: Centralised version management for better QoL

• Orwell: Dashboard - integrated version management and added button to show release notes with links to full changelog for each version, backfilled to 5.3.0

• Fix: 5.x added the option for ranks to require a number of PIREPs to be filed; Our rank and Pilot Invite system was not made aware of this, which made it impossible to get a transfer pirep to rank with pirep count requirement; Transfer processor is now aware of pirep count requirement and Pilot Invite has an option to specity PIREP Weight as well now, fixing this logic oversight.

• Fix: Focus Airport and Event activities would not award points correctly

• Fix: Badge notifications not sending out to discord

Several fixes making their way into 5.3.4 - due to the nature of the issues the release is rushed to fix them instead of adding or changing functionality and working off Featurebase backlog.

• Fixed: Restoring pilot account via Orwell and creating new pilot username did not transfer booking records from old account, causing statistics issues in the new account. New restores will work correctly.

• Fixed: Made it impossible to try and open PIREPs with no route (transfer PIREPs).

• Fixed: Appending airline remarks when the Operator or ATC Callsign is not set by the VA.

• Fixed: Book Flight Map not updating properly when jumpseating to new location.

• Change: Increased jumpseat marker size

• Change: Swapped Jumseat and Dispatch button colors

• Fixed: various Tour/Roster/Curated Roster logbook issues when reprocessing pilot PIREPs - they were affecting already completed rosters and causing all sorts of mess; The Tour/Roster/Curated Roster tracking system improved yet again which should resolve these issues and all logbooks for all current activities are being updated to reflect correct leg completion.

• Orwell: PIREP Table received individual and bulk actions for Accept/Reject/Invalidate/Reprocess as appropriate.

• Orwell: AutoReject rules table now shows vAMSYS Rule name as well as your configured rule name.

• Phoenix: Dispatch Table (via Book Flight Map when multiple routes are available for city pair or directly via Book Flight From […]) - added drop-down to VA Enabled flight trackers light FR24, AirNav, FlightAware and route edit page in Orwell.

• Phoenix/Orwell: Paused Airborne time had an erroneous nm notation next to time.

• Phoenix: Fix a Discord notification related error when filing a claim.

• Internal: Updated ban message when user is banned by vAMSYS Robot when multiple accounts are detected.

• Orwell: Fix PIREP Reprocessing will erroneusly award points for activities which are set to only reward once and there already exists another PIREP which got the activity points;

• Improved: PIREP Reprocessing logic towards activity logbook for Tours/Rosters/Curated rosters; On reprocess it will do a better reconstruction of logbook to see if we can rebuild the logbook to be as complete as possible given the PIREPs pilot has filed in relation to activity settings. This also handles the cases of removing PIREP and related PIREPs from activity logbook if the PIREP reprocessed (and related PIREPs in the logbook) no longer meet activity requirements.

• Phoenix: Fix Pilot configured SimBrief OFP layout was not taken into account when generating OFP or Preview.

• Phoenix: Fix Book Additional Flight Map filters having values based on current pilot location and not on destinations available from previously booked arrival airport.

New Scorers and AutoRejects

• Scorer: Pushback Fuel Outside Planned Range - Deducts points when pushback fuel is outside SimBrief planned ramp fuel ± tolerance range provided.

• Scorer: Pushback Fuel Within Planned Range - Awards points when pushback fuel is within SimBrief planned ramp fuel ± tolerance range provided.

• AutoReject: Pushback Fuel Outside Planned Range - triggers autoreject action when pushback fuel is outside SimBrief planned ramp fuel ± tolerange range provided. Has fleet overrides.

• Scorer: Takeoff Fuel Outside Planned Range - Deducts points when takeoff fuel is outside SimBrief planned takeoff fuel ± tolerance range provided.

• Scorer: Takeoff Fuel Within Planned Range - Awards points when takeoff fuel is within SimBrief planned takeoff fuel ± tolerance range provided.

• AutoReject: Takeoff Fuel Outside Planned Range - triggers autoreject action when takeoff fuel is outside SimBrief planned takeoff fuel ± tolerange range provided. Has fleet overrides.

• Scorer: Landing Fuel Below Reserve - Landing with fuel below SimBrief final reserve.

• Scorer: Landing Fuel Above Reserve - Landing with fuel above SimBrief final reserve.

• AutoReject: Landing Fuel Below Reserve - Landing with fuel below SimBrief final reserve.

• Scorer: Touchdown Pitch Outside Range - Deduct points when touchdown pitch is outside specified min and max angle.

• Scorer: Touchdown Pitch Within Range - Award points when touchdown pitch is within specified min and max angle.

• AutoReject: Touchdown pitch angle is excessive - Action triggered when touchdown pitch angle is outside safe operational limits.

• Scorer: Touchdown Roll Outside Range - Deduct points when touchdown roll is outside specified max angle.

• Scorer: Touchdown Roll Within Range - Award points when touchdown roll is within specified max angle.

• AutoReject: Touchdown roll angle is excessive - Action triggered when touchdown roll angle indicates potential wingtip/engine strike.

• AutoRejects: 4 autorejects for Softer/Heavier landing for G rates (for Pegasus v2 users)

• AutoRejects: 4 autorejects for Softer/Heavier landing for FPM or G rate.

• Scorer: Graduated Landing (G) - similar to FPM counterpart, provides scoring rules for landing G Force.

Destination Map

[Image: ]

• Added Cloud Layers for low, mid, high and total cloud coverage

• Added Visibility overlay

Book Flight Map

• Update to use the same engine as the Destination Map

This changelog will be updated as things are added to 5.3.3

• Orwell: PIREP Table received individual and bulk actions for Accept/Reject/Invalidate/Reprocess as appropriate.

• Orwell: AutoReject rules table now shows vAMSYS Rule name as well as your configured rule name.

• Phoenix: Dispatch Table (via Book Flight Map when multiple routes are available for city pair or directly via Book Flight From […]) - added drop-down to VA Enabled flight trackers light FR24, AirNav, FlightAware and route edit page in Orwell.

• Phoenix/Orwell: Paused Airborne time had an erroneous nm notation next to time.

• Phoenix: Fix a Discord notification related error when filing a claim.

• Internal: Updated ban message when user is banned by vAMSYS Robot when multiple accounts are detected.

• Orwell: Fix PIREP Reprocessing will erroneusly award points for activities which are set to only reward once and there already exists another PIREP which got the activity points;

• Improved: PIREP Reprocessing logic towards activity logbook for Tours/Rosters/Curated rosters; On reprocess it will do a better reconstruction of logbook to see if we can rebuild the logbook to be as complete as possible given the PIREPs pilot has filed in relation to activity settings. This also handles the cases of removing PIREP and related PIREPs from activity logbook if the PIREP reprocessed (and related PIREPs in the logbook) no longer meet activity requirements.

• Phoenix: Fix Pilot configured SimBrief OFP layout was not taken into account when generating OFP or Preview.

• Phoenix: Fix Book Additional Flight Map filters having values based on current pilot location and not on destinations available from previously booked arrival airport.

New Scorers and AutoRejects

• Scorer: Pushback Fuel Outside Planned Range - Deducts points when pushback fuel is outside SimBrief planned ramp fuel ± tolerance range provided.

• Scorer: Pushback Fuel Within Planned Range - Awards points when pushback fuel is within SimBrief planned ramp fuel ± tolerance range provided.

• AutoReject: Pushback Fuel Outside Planned Range - triggers autoreject action when pushback fuel is outside SimBrief planned ramp fuel ± tolerange range provided. Has fleet overrides.

• Scorer: Takeoff Fuel Outside Planned Range - Deducts points when takeoff fuel is outside SimBrief planned takeoff fuel ± tolerance range provided.

• Scorer: Takeoff Fuel Within Planned Range - Awards points when takeoff fuel is within SimBrief planned takeoff fuel ± tolerance range provided.

• AutoReject: Takeoff Fuel Outside Planned Range - triggers autoreject action when takeoff fuel is outside SimBrief planned takeoff fuel ± tolerange range provided. Has fleet overrides.

• Scorer: Landing Fuel Below Reserve - Landing with fuel below SimBrief final reserve.

• Scorer: Landing Fuel Above Reserve - Landing with fuel above SimBrief final reserve.

• AutoReject: Landing Fuel Below Reserve - Landing with fuel below SimBrief final reserve.

• Scorer: Touchdown Pitch Outside Range - Deduct points when touchdown pitch is outside specified min and max angle.

• Scorer: Touchdown Pitch Within Range - Award points when touchdown pitch is within specified min and max angle.

• AutoReject: Touchdown pitch angle is excessive - Action triggered when touchdown pitch angle is outside safe operational limits.

• Scorer: Touchdown Roll Outside Range - Deduct points when touchdown roll is outside specified max angle.

• Scorer: Touchdown Roll Within Range - Award points when touchdown roll is within specified max angle.

• AutoReject: Touchdown roll angle is excessive - Action triggered when touchdown roll angle indicates potential wingtip/engine strike.

• AutoRejects: 4 autorejects for Softer/Heavier landing for G rates (for Pegasus v2 users)

• AutoRejects: 4 autorejects for Softer/Heavier landing for FPM or G rate.

• Scorer: Graduated Landing (G) - similar to FPM counterpart, provides scoring rules for landing G Force.

Destination Map

[Image: ]

• Added Cloud Layers for low, mid, high and total cloud coverage

• Added Visibility overlay

Beta is available at https://beta.vamsys.io

A little update from the seaside:

• Fixed dependency issues preventing automatic updating of AIRAC cycle; Starting with AIRAC 2510 there should be no need for any manual intervention for the cycle to update.

• Added AIRAC cycle information box in Orwell Dashboard under vAMSYS Links & Information so you’re always aware which cycle is loaded into vAMSYS.

It’s time for our first update to 5.3 and this one packs a punch!

Bug Fixes

• PIREP Time not getting calculated on 5.3 launch

• Live Flight List not being generated for VAs in trial version

• Fix filters not being applied correctly to Dispatch Page when attempting to book via Activities

• Fix Activity markers not showing in Book Flight Map

• Fix popup persistence issue when markers rebuild after zoom

• Fix ETE indicator alignment in destination map timeline

• Fix being unable to delete pilot account via Orwell Pilot View

• Fix PIREP map refusing to draw when there are position reports with extreme negative altitude values

• Fix some route-model binding issues with API routes for Fleet and Containers

• Fixed broken Paused Percent autoreject - it was looking for variable which did not exist

• Fixed an issue with notification showing that simbrief is unavailable in Dispatch Page even though user has no linked SimBrief account

• Fixed related issue to flight information not loading in dispatch page for repositioning flights when user has no linked SimBrief Account

• Fixed error codes not being shared in API requests when they fail

• Fixed 504 errors when trying to leave comments on a PIREP Claim

Destination Map

Our 5.3 release rewrote all the map code and added some eye candy and weather layers; With 5.3.1 we are taking things it a bit further. Whilst attempting to add more weather overlays to Destinations Map, we’ve uncovered very poor performance and - instead of trying to fix it - we’e decided it’s better to rewrite a rewrtite.

So there we have it - a brand new Destination Map:

[Image: ]

You will find that it’s very familiar - it’s the same airports after all, but under the hood - it’s all very different. Since all our maps have a lot of interactivity, we’ve simply outgrew raw typescript/javascript and opted for Vue as the framework to manage it all; Whilst at it - replaced the mapping engine from mapbox to maplibre. Result - a better performing map with more features

Filters

First thing you’re bound to notice is that the map is ‘bigger’ - we removed the filter row on top of the map and shrunk the footer to give the map more room. Filters now live in top-right corner.

[Image: ]

Sidebar

Most of the magic is in the sidebar:

• Departure and Arrival airport boxes are clickable which will open the search for available airports

• Reverse lookup - want to see arrival routes into an airport? Enter arrival airport and leave departure airport empty - Destination Map will enter ‘Reverse’ mode

• Swap Airports - a button to swap between arrival and departure airports

• New weather layers - surface level wind gust overlay

[Image: ]

Lastly - you should find the map quicker to load and quicker to apply filters; Airport to airport ‘navigation’ is also improved as we pre-load airport connection mappings, so no more need to wait for destinations to load when you click the marker.

Hope you find the reverse mode useful!

New PIREP Scorers

With 5.3.1 we are also bringing new and improved PIREP Scorers:

• Arrival / Departure

• Landing Rate Autorejects can now have fleet overrides

• Added conditional engine warmup logic, if enabled:

• Approach Flaps Set/Not Set - award/deduct points if flaps were not set to acceptable level for landing.

World Clock

The clock on the top-right hand side in both Orwell and Phoenix now has a dropdown:

[Image: ]

It shows the current UTC time (like the topbar) - your local time as well as the time at your pilots location.

Virtual Airline speficied hubs are grouped by timezone and listed as well.

What’s next?

The plan is to update Book Flight map to the new engine with 5.3.2; Pegasus v2 is still on the horizon for initial release in first half of September; And we plan to start work on Hangar v2 in earnest this September as well.

But for now - it’s time for summer holiday - we are away till 9th of September - ticket replies, bug fixes and/or replies to your featurebase posts will take longer than usual.

vAMSYS 5.3 represents a massive leap forward in functionality, performance, and developer capabilities. This release brings a number of firsts for vAMSYS - a comprehensive API, real-time weather systems, and powerful webhook integrations.

Map Rewrite

All maps - be it in Phoenix or Orwell have been completely rewritten to be more modular and easier to work with in the future.

This work has nicely lent itself to adding some things we wanted for quite a while - weather radar.

Book Flight and Available Destination maps have wind overlays on several flight levels, including a timeline scrubber for full 24 hour forecast across the entire world.

Map rewrite also means we can enable full SPA-like navigation across all pages on vAMSYS - no more annoying white flashes when navigating from page to page in dark mode.

Pilot Flight Map

Your flight history Map available via My Profile → Map has seen performance improvements as well as ability to draw flight paths with gradients

[Image: ]

Be mindful that large datasets can take a little while to load.

Live Flights

Live Flight map (Flight Centre → Flight Map) has new filters for airports, aircraft and online network; The sidebar is more modern and clean and, in addition to already familiar flight path - we not also show planned route line and waypoints.

[Image: ]

Other Maps

All the maps with a sidebar (Book Flight, Flight Map, Available Destinations) have new sleek sidebars; all maps feature improved hover popups for more information.

There are probably still a bug or two hiding in these - if you come across anything unusual be sure to esclate so it can be worked on.

API and Webhooks

The primary Focus of 5.3 release was the API; For the first time in our rather long history, we have an incredible Operations API, replicating most of the functions achievable via Orwell.

[Image: ]

Do have a look at Orwell → HQ → Settings → API section for the new API as well as link to the documentation detailing all our API endpoints.

What’s next for 5.3

With the release of 5.3.0 the rest of the week will be taking in your feedback and resolving any bugs - with 5.3.1 planned for Friday morning, save for any hotfix we need to push, but that will be under 5.3.0 release moniker.

API v3 is not fully complete yet - the Operations API will receive Activity Management endpoints and we will start work on Pilots API, which will enable API integrators to perform actions on Pilot behalf - like making bookings.

Further vAMSYS 5.3 updates will also see introduction of new weather map overlays - clouds, rain, thunderstorms. Lastly - at the start of September we hope to relase Pegasus v2 - there’s plenty to look forward to there as well.

Acknowledgements

This massive release wouldn't have been possible without the feedback and support from our virtual airline community. Special thanks to all beta testers who made sure 5.3 release is not completely broken :)

• Various changes, tweaks and additions for Pegasus v2 Log parsing

• Fixed Route SB Options not being taken into account correctly when dispatching

• Fixed Create & Create another save issue in Activities

• Added Route Tag columns in PIREP tables in Phoenix and Orwell

• Fixed TAF processing internally

• Fixed old references to fuel configuration on Routes

• Added more Alternate Fields in Routes, including export/import