Simbrief is fantastic, make no mistake. But I have found it increasingly frustrating that it seems to be ATIS “dumb” when it comes to real world traffic - just now I was flying into YSSY and it gave me 16L to land - only to find the real world traffic injected into my sim from BATC linked to Navigraph to be using 34L and 34R on departures.
I really think now Navigraph has real world data via the arrangement with Flight Radar that we shouldn’t be seeing basic mistakes like this. Why should Simbrief or indeed Navigraph Hub be relying on anything but real world ATIS now they have access to such data?
Can I please be assured that there will be big improvements in this area and that the departure and destination ATIS be correct at the time of planning and only changes when it changes in real life?
The Navigraph experience is usually fantastic but this is a massive immersion killer.
Hi, real-world Sydney has been landing on 16L for the past 3 hours (including at your planned arrival time, based on checking recent arrivals on FlightRadar24). So in this case SimBrief was correct.
But it does look like real-world Sydney switched around from the 34s to the 16s about an hour before you landed. Even if BATC wanted to switch to the 16s as soon as real-world did, there’s probably going to be a bit of a delay as it can’t simply “teleport” all existing traffic to the other runway instantly. It needs to reroute them realistically and let the imminent departures/arrivals clear out first.
But to be honest, I am really not familiar with how BATC handles runway selections or changes, feel free to reach out to them directly for more clarifications!
Thank you for your reply. I only use BATC for its injected traffic using FSLTL models and the FR24 data via my Navigraph linked account.
I continuously monitored the ATIS via the Navigraph hub on my flight and there was no indication of a runway switch, but that explanation would make sense (however my flight was less than 3hrs - from NZQN - so I am puzzled why I was given 16L in the first place from Simbrief). It seems that a change of runway use is an issue here and that the Hub software seems to struggle when there is such a switch.