Crew chat arrives, position reports gain fuel/payload/passenger detail, dispatch editing moves to its own page, and SimBrief dispatches build the OFP themselves without a browser popup.
What's new
-
Crew Chat
The Chat page is live. Four rooms are available: General, Dispatch and Support for your airline's crew, and one System-wide room shared across every airline on the platform. Opening a room shows the recent conversation rather than starting blank, and messages from other pilots — in the web app too — appear instantly without refreshing. Airline rooms follow whichever airline is currently active, so switching airlines switches who you're talking to.
-
Fuel, Payload and Passenger Reporting
Position reports now include fuel on board, payload (derived from total weight minus fuel and the airframe's operating empty weight), and passenger count, and the arrival log entry now records fuel remaining. Airlines running persistent fleet state use this to keep an aircraft's state current between flights without waiting for the PIREP.
What's improved
-
Dispatch Editing Has Its Own Page
Editing a dispatch now opens on a dedicated page instead of inline where it was before.
-
Route, Altitude and Cost Index Prefill On Dispatch
The route, altitude and cost index fields on the dispatch form are now filled in for you automatically.
-
SimBrief Generates Itself
Dispatching with SimBrief no longer opens a browser window for you to fill in. vAOMS now builds the OFP server-side through SimBrief's new API, so the dispatch returns immediately and the SimBrief panel waits for the finished plan on its own. The completed briefing is shown in the app under View OFP instead of on simbrief.com. Generating requires a linked Navigraph account — the option is disabled with an explanation until you link one in the web app under Settings → Integrations.
-
Platform Notices Reach The Client
Platform-wide notices now reach VAOMS Connect rather than only the web app.
What's fixed
- Server Faults Reported As Raw JSON — When the server failed on a request, the app showed the server's own error body verbatim — "Unexpected response for timetable: { \"message\": \"Server Error\" }" on the timetable, for instance — and filed it as a connection problem, sending pilots off checking a network that was working fine. Such a reply is now recognised as a fault on the server's side and reported as one, with the raw body kept in the log for support.