Obviously, there's a lot that goes on in the database that we don't see. Would it not be possible to separate the data that we input manually...
What changed, James? I was under the impression that it was a process, which ran every 24hrs.
Possibly a test hex. Also noted as using callsigns RAFB302, FZJTJ, FZWTV recently.
It could be either. Should be 72291, but both using the same hex. 72291 also still using A3DB0B of N348AE [pre delivery civil reg] on one box....
Callsign changed to 3378 today, so ties it nicely to 80-23378.
Yes, that's the general consensus of opinion.
It was added to LMMS a few weeks ago, and I'm not sure where the info came from. I don't think it was added by me, because I can't find any...
Yes and yes, just don't expect to see a change anytime soon.
Is that a calculated guess? I've not seen a callsign that confirms it yet.
After rechecking, it looks like the AW169 has now been recoded correctly.
Note the exclamation mark ! AW169 G-VSKP is miscoded and using the same hex, instead of 407139. Appears to be on one box only.
Yes, I also amended the LMMS entry recently, along with AE1139, callsign 023670. Only very recently are we seeing USAF TEX2s using callsigns on...
It's possible, but also used CLV731 last year. I have... 0731 as 49848F 0928 as 4984A1 or 49844C
Thanks, FAF have 17 PC-21s, registered as 01 to 17. All are at Cognac, except 03/F-ZXAC which, according to Scramble, is at CEAM. From...
It's something like... the volume of data being received/stored, and then stripping out gigabytes of unwanted data before it can be loaded live.
I wouldn't get your hopes up too much. There's no fix in sight any time soon.
The above are already in the database. I've no idea when the updates will get loaded live, though. Due to technical problems, it's not been...
Mil already in d/b. 3B-NBU added.
Amended some time ago, thanks.
Yes, quite a while ago.
Separate names with a comma.
