G’day everyone, I fly for British Airways Virtual. When I use SimBrief, the ICAO code is always BA, and not BAW, which is the correct ICAO identifier for British Airways. Is this a bug in SimBrief, a bug in the British Airways Virtual interaction with the SimBrief API, or am I doing something wrong? Thanks in advance for your help.
Hi, can you please clarify where you see BA instead of BAW? In the generated briefing PDF or elsewhere?
Regards,
Tim
BAV uses the SimBrief API to create the OFP (I think). When I check the OFP itbsays BA in the ICAO airline code box. It may be an issue with how BAV is using the API, but I don’t know enough about how that works to know for sure.
But where is that box, can you post a screenshot?
Regards,
Tim
Hi Tim,
In the despatch page (before the OFP is created) the very first box is the airline ICAO indicator. After BAV has generated the OFP, I go into it and change certain parameters, like pax and setting the correct aircraft profile. When I open the OFP the airline ICAO code is just BA.
I have to go out now (8:29am here in NZ), I’ll be around to answer any questions you have this afternoon
Then yes, it’s most likely the BA Virtual code that’s setting the parameter incorrectly when generating the initial OFP.
When generating a flight manually and entering the ICAO code (BAW) myself, if I go back to change parameters (“Edit Flight”), the code I entered is retained properly, and presumably if BA Virtual were sending the ICAO code through the API in the first place, then when editing, the flight options page would also show BAW like in the manual case.
The Simbrief API documentation does not specifically indicate that an ICAO code is expected (as opposed to IATA), but the example value being 3-character long is a clue:
My guess is, BA Virtual’s code is incorrectly sending the IATA identifier instead.
Regards,
Tim
Thanks Tim, I’ll ask the BAV team to check the code they’re sending to the API
Mike