Pilot2ATC Simbrief import uses wrong Callsign

[Bam2000]

Hi, 

just tested you awesome ATC Program and discovered that the Simbrief import always selects the Simbrief Flight Number as a Callsign, instead of the Callsign as a Callsign 😄

Do you think you can do anything about it ? would be nice not to have edit it always manual, thanks 🙂

[Dave-Pilot2ATC]

If you put in the Airline Code, like AAL for American or BAW for British Airways, in the top left box labeled Airline, then P2A selects the CallSign based on the Airlines maintained in TaxiMnt.

The next update will override that with the CallSign, if entered.  It will still require the Airline box to be filled in or it will assume you are not flying an Airline flight and will create a GA call sign with the CallSign you enter and the tail number.

Dave

[Bam2000]

Hey, sadly Pilot2ATC still uses the Flight Number as a callsign, instead of the Entry in the ATC Callsign field from simbrief? Can you fix that? Thanks

[TexasGary]

I am running version 2.7.0.2 of P2ATC.  I generate my Simbrief flight without an airline or flight number, and I enter "LEAR" for ATC callsign and "0BM" for the registration.  Prior to the last 2.7.0.2 update this was reflected correctly when I imported the plan via the "FP Import" button in P2ATC.  But now with 2.7.0.2 whenever I import the plan the Call Sign and Flight/Tail Number are always incorrect.  And although it's a GA Call Sign P2ATC always imports it as an Airline Call Sign Type.  The release notes for 2.7.0.2 say "Fixes SimBrief Import Call Sign handling."  But for me it's still an issue.  

[TexasGary]

OK, I found a solution for this.  I created a new Simbrief flight plan and this time I unchecked the "Import Call Sign" box.  Then I hit "Import SimBrief" and the Call Sign and Flight/Tail Number were imported correctly.