Do the callsigns in your daily logs match ....

[freqhopping]

the callsigns that were actually used that day?

Mine don't when that aircraft has been logged prior displaying a callsign.  I receive my daily logs by email at 7pm every day.


Some examples, beginning with the one in which I first noticed this on Sunday.

99-0004 which was SAM-4242 (displayed S4242).  In the log it showed AF2 (Air Force-2) which is what is was on 12/10 and 12/20 last year.  Since it was last AF2 it has had several other SAM callsigns. 

From this evening:

E-4B 74-0787 departed KADW displaying CAPON63.  The log shows GORDO91 which is what it was displaying on January 29.

00-9001 Boeing C-32B USAF/FEST was displaying TERRA52.  However in my log, it shows CLOP76 which is what was actually used on January 24.

00-1934 USAF C-130 displayed BATON91.  The log shows BATON61 which was used on January 8.

It's like this for every flight I've bothered to check. The log perpetually sends out the first callsign that was ever logged.  In MyLog it obviously correctly lists all the callsigns as they have been logged.

[tarbat]

It's a known bug.  I've posted some SQL in previous posts about this bug that you can use instead to generate a daily log that includes all Flight IDs used that day.  See http://www.airnavsystems.com/forum/index.php?topic=2190.msg18265#msg18265

An example of my log is at http://www.tarbat.gofreeserve.com/data.html
In that example, you'll see aircraft such as G-DBCD listed with 4 flight IDs - BMA668 (EGLL-EGPD), BMA669 (EGPD-EGLL), BMA678 (EGLL-EGPD), BMA679 (EGPD-EGLL).  Hopefully that's the sort of daily log Airnav can provide in a future version of RB.