Good evening, pilots!
It’s been a couple of weeks since my last post, and so I wanted to give you a quick update on everything that’s been going on behind the scenes regarding the platform and other things that I mentioned previously.
NAVAID Updates (Completed)
The latest (April 2025) NAVAID updates have now been applied to our core databases (and synced to the WXG microservice). Our NAVAID data (VORs, DMEs and Waypoint data) is based on the very latest AIRAC navdata update.
This has been live for a couple of weeks now – we hope that you’ve benefited from these updates, specifically on your flight plans or when importing from the likes of SimBrief.
I have developed some semi-automated software that can now very quickly ingest the latest data and make it available across our platform and so, future navaid updates should also be made available to you super-quick (within a few hours of release)!
Screenshot migrations (Almost completed!)
Migrating (downloading, optimising and re-uploading to our new CDN-backed S3 storage) is, for the most part, now complete.
Our worker nodes still have approximately 80,000 images to process (convert from PNG to WEBP) and re-upload, but we’re nearly there – YAY!!
We have seen a substantial decrease in the amount of object storage space requirements, which is both good for the environment and our monthly operating costs of this platform!
Our object storage requirements (the type of storage used for storing and serving your uploaded content – screenshots, avatars and achievement badges/splash images) have dropped from just over 1TB to ~65GB – That’s an INSANE difference and props to the more-modern WEBP image format!
Search engine migration (Completed)
I took several days to monitor our K8S cluster to identify “other areas” for performance improvements, and one of the biggest “memory hogs” was identified as our Meilisearch index containers.
I decided to alleviate some resource pressure of the main cluster and moved our Meilisearch service to its own compute node (server) – The performance (general speed of navigating the site) was immediately noticeable with excellent feedback from the rest of the team too!
…hopefully, you guys have also noticed the speed improvements, too?
Database capacity & reporting improvements (Scheduled)
As mentioned in an earlier post, given the sheer amount of I/O and requests to our primary (R/W) database, my plan was to spin up one or more additional database servers to enable us to re-enable the VA reporting features of which are super resource-intensive and put extreme pressure on our master database.
Whilst this is still-onging (testing, mainly), I plan to bring into service, an additional two database servers that will be “in-sync” from our master database – these “slave” nodes (now known as a policially incorrect term and so, I’ll use “secondary” instead) will enable me to re-route all “read-only” API requests (of which, our platform recieves litterally hundreds of thousands A DAY to these secondary servers – ensuring that the “all important” writes hit the master database with total reliability.
This process however, will require ~40 minutes of downtime in order to complete the initial sync between our master DB cluster and the new “secondary” replicated databases.
Whilst I will communicate this ahead of time, I suspect that this “one off” task will take place on Tuesay the 6th of May (at 10:00am UK time). I will ensure that a platform message (warning) is visible a whole 24 hours ahread of time, and a message will ofcourse be posted to our status page during this “outage window” too.
Migration away from Google Maps (Ongoing)
To be honest, I’ve been so busy with the above-mentioned tasks these past couple of weeks (any “spare” moments that I’ve had) that this, unfortunately and whilst I’ve received yet another large bill this month, has had to take a backseat for the time being. I do plan to work on this very soon, though and we will have then finally and completely be migrated over to OpenStreetMap and our 3rd party tile-provider (Stadia Maps).
Public profile (Live flight status widget)
Some of you may have noticed a new “Live Flight Widget” on your public profile pages?!
I thought it would be fairly cool to provide similar information on the public profile pages that our Discord activity feature provides, regardless of whether you are logged in to Discord.
The widget shows general flight information such as where the pilot is “flying near”, current speed, altitude and, if the pilot have an active flight plan submitted, will output the departure and expected arrival information too.
Just a few “Live flight status” examples from this evening:-







I also plan to add the same “flight progress” bar and information to the public profile pages for pilots that have a flight plan entered – displaying further information and a progress bar, similar to what is displayed when clicking on an active aircraft from the Radar page:-

This should be coming soon!
LRM Client updates for MSFS2024 erroneous flight distances
As some of you may have noticed with MSFS2024 some flights appear to be logging with varying additional distance of which is due to the way that MSFS2024 (and MSFS2020) “places” the aircraft when you are in the game menus – essentially putting you at the centre of the globe (lat/lng).
Whilst one way to counteract this would be to open the LRM client once your aircraft is loaded in at the gate (and what we are recommending at this time), I understand that this is less than desirable.
I have a “fix” planned and hope to release in the next release of the LRM client – this should be happening (released) in the next couple of weeks, so keep those eyes peeled!
…we’d naturally love your feedback on this too!
Hoppie integration for airlines (Planned)
Hoppie provides in-aircraft ACARS functionality, from the website, this is described as:-
ACARS by itself is mostly a transport network, used to pass short messages back and forth between aircraft and ground facilities. It can be compared to e-mail, or even better, to cell phone text messaging. However it uses quite different technology, based on either classical VHF transmission or satellite communications. These aspects of ACARS are not simulated by the system that Hoppie Provides; we use the internet as transport layer.
If you know all about Hoppie and think this is cool – that’s awesome 🙂
We realise that we’ve not added too many cool integrations recently, and so, I have planned to integrate a new section within the Crew Portal (for VA managers) to enable them to communicate with their pilots (with a Hoppie-enabled aircraft).
VAs will be able to send/receive messages and other information to VA pilots directly from the Crew Portal (that’s the plan, at least!)
More details on this will be published soon and “early access” will be granted to a number of airlines in due course.
Aeroconomy updates!
I am extremely happy with the recent platform performance improvements and, with the additional databaes servers and some additional planned RabbitMQ nodes, this really will enable the platform to take on the additional load that Areoconomy (in it’s entirety) will bring.
I look forward to updating you in, hopefully in 3 – 4 weeks will a full rollout plan for Aeroconomy – I just have to complete the other mentioned tasks above first!
…now is certainly the time to be flying those Daily Flight challenges (to earn you and your VA’s those virtual dollars)
That’s all (for now) folks,
Bobby