Airforce One

[fossie1]

Hi all, Is it normal to see Airforce One show up on RB? Just had it flash up, see screen shot.

Stephen

[RodBearden]

Hi Stephen - no it's not normal to see it on the map - just in the grid. As far as I recall, it hasn't broadcast its position before - very nice to see!

I got an alert for it an hour or so ago, but it had disappeared before I found it.

Rod

[fossie1]

It was only on for about a minute, but as you say it was nice to see on map.

Thanks

Stephen

[freqhopping]

So MyLog is correct then.  I was wondering about this when I checked it today.

[DaveReid]

So MyLog is correct then.  I was wondering about this when I checked it today.

I would treat the position report with the same caution as the altitude, which is shown as 125,100'  :-)

[freqhopping]

I would treat the position report with the same caution as the altitude, which is shown as 125,100'  :-)

I don't doubt the position.  That's a typical route for an ADW or DCA departure.

[RodBearden]

Anyone know what circumstances trigger the VENUS ID - or the S- ID, come to that?

Rod

[freqhopping]

Venus is a squadron callsign, used when just flying around, doing approaches and stuff.  The SAM callsign is used when they're flying an actual mission without the president.  82-8000 I've never logged as anything other than AF1, they never change it.

[RodBearden]

Thanks for that, freqhopping.

Rod

[DaveReid]

I would treat the position report with the same caution as the altitude, which is shown as 125,100'  :-)

I don't doubt the position.  That's a typical route for an ADW or DCA departure.

Come to think of it, the groundspeed looks pretty dubious too.

It's hard to believe that the White House's response to the latest security situation is for the President's aircraft to start transmitting its position and fly around nearly 200kt slower than normal :-)

My money would be on the known bug where details for one aircraft get incorrectly shown against a second one, I'm not aware of any fix to that having been announced yet.

[freqhopping]

Come to think of it, the groundspeed looks pretty dubious too.

It's hard to believe that the White House's response to the latest security situation is for the President's aircraft to start transmitting its position and fly around nearly 200kt slower than normal :-)

My money would be on the known bug where details for one aircraft get incorrectly shown against a second one, I'm not aware of any fix to that having been announced yet.

What's wrong with the speed?  Looks normal to me.

Even it was a different aircraft, a different aircraft isn't going to be transmitting VENUS02 and AF1 for flight IDs.  Besides sometime actually heard VENUS02 on the departure frequency at 1205 and that matches perfectly with my picking it up at 3100ft.  Further down MyLog I logged an ADS-B hit for it back in August too.

[johnboy]

I picked up AF1 early Dec. no position on map but showing Alt. 30000,flight Id. as Hank44 and airline Hansung. Seems  strange info but Reg. correct for AF1.
Logged on same day as Pres. flew back from climate change conference.

[freqhopping]

I picked up AF1 early Dec. no position on map but showing Alt. 30000,flight Id. as Hank44 and airline Hansung. Seems  strange info but Reg. correct for AF1.
Logged on same day as Pres. flew back from climate change conference.

That wasn't Air Force-1.  Air Force-1 will always display AF1.   You need to fix the information in your database for ADFEB6.  What you logged was E-4B 75-0125.  ADFDF9 92-9000 is the one that has been used as AF1 since October.

[DaveReid]

I picked up AF1 early Dec. no position on map but showing Alt. 30000,flight Id. as Hank44 and airline Hansung. Seems  strange info but Reg. correct for AF1.
Logged on same day as Pres. flew back from climate change conference.

It's likely that you were picking up both AF1 and HANK44 and encountering the known bug where details for one aircraft are wrongly displayed against the other.