Status of K35R 57-1419 ?

[AirScan]

57-1419, the oldest KC-135, was last noted on ADSB-X landing in PHX on July 10, 2020. The same day it appears its HEX code, AE04B0, was taken over by a C-130. Anyone know the status of 57-1419, is it operating with different HEX code now ?

 

[RaleighGuy]

Plane Finder shows it flying today with that hex.

https://planefinder.net/data/aircraft/57-1419

 

[AirScan]

Plane Finder shows it flying today with that hex.

That's the C-130. The Plane Finder database has not been updated.

 

[freqhopping]

The C-130 using the hex is 165810. I'm not sure what's up with 57-1419. Some tankers that were assigned to AZ ANG have more recently been flying out of McConnell Air Force Base and using 22nd ARW callsigns.

 

[AirScan]

The C-130 using the hex is 165810.

Thanks.

I'm not sure what's up with 57-1419. Some tankers that were assigned to AZ ANG have more recently been flying out of McConnell Air Force Base and using 22nd ARW callsigns.

These are the PHX based K35Rs (using the COPPER callsign) noted since May 2020, with the date last seen (month.day)

AE04B0 57-1419 07.10
AE0266 57-1469 11.03
AE035E 58-0077 11.04
AE047D 59-1450 10.30 - departed on Middle East Tour 09.29
AE07A7 59-1498 10.29 - > transferred from BGR between 08.24 to 09.11 on loan ?
AE07B0 61-0284 06.05
AE0667 61-0317 11.07 - departed on Middle East Tour on 09.28
AE026C 62-3516 09.08
AE038A 62-3531 11.05 - various Coronet/CAP
AE07B9 62-3550 10.26
AE014F 63-8036 10.12 - returned from Middle East Tour
AE05A4 62-3500 11.07

That's based on callsigns only so maybe the IAB ones you are talking about transferred before May and I missed them ? Or you are using another source beside ADSB-X ?

 

[AirScan]

Looks like old 57-1419 is back in the air as of January 7th, 2021. COPPER 08 out of PHX which looks legit. Looks like the last time the C-130 used that hex was December 18, 2020 at OTIS 81 to Europe. So what code is the C-130 using now ?

 

[AvionicEng747]

Looks like old 57-1419 is back in the air as of January 7th, 2021. COPPER 08 out of PHX which looks legit. Looks like the last time the C-130 used that hex was December 18, 2020 at OTIS 81 to Europe. So what code is the C-130 using now ?

Hello, I know this is a very late reply but I've just found this forum when searching for for other info. I saw your question about this and you were correct in that 165810 was using AE04B0 but it was merely a miscode of one of the transponder boxes. 57-1419 KC-135 was always the correct user of this code.

165810 was transmitting both AE04A8 and AE04B0 at various times, so it looks as if one of the transponders has had the incorrect code set up.

To solve the mystery of what has happened to 165810, you can look here:

Getting back to the rogue transponder code, it can be quite common to see an incorrect code on older aircraft. I've had experience setting up these codes on [civil] aircraft and on older generation aircraft, it's not as simple as you might think. A lot of older generation aircraft the actual code is not generated in the transponder unit at all, it is generated by program pins on the aircraft wiring side, so once set-up any transponder plugged into that aircraft will automatically generate the correct code. Obviously, in this situation the actual hex code has to be converted into binary as the aircraft digital systems only actually work in binary [with normally a positive voltage being a "1" and a ground being a "0"] That binary figure then has to be transferred to wiring on the connector on the back on the transponder unit [normally a plug with many pins] so the potential for a coding error is quite high. That said, any decent engineer would always set up a ground test set after the installation had been done to check the hexcode outputs [on both systems].

This is also one of the reasons that aircraft when they change hands [and registrations] quite often fly around for a while with the code of the previous identity, as it's not a five minute job to recode on the older aircraft that are hard wired.

 

[AvionicEng747]

Sorry just realised the link only above only shows the video. The text that was on the youtube clip is as below:

Several months ago Marshall ADG announced the awarding by the USMC of a MRO contract on their fleet of KC-130Js. Marshall being the global leaders in Hercules MRO having done so for over 50 years now on the Royal Air Force fleet among over 2 dozen other operators. With Christmas nearing the inaugural USMC visitor, 165810" arrived after an 8 hour flight in from Bangor using call-sign "Otis 81". She will spend several months at the Cambridge site before returning to operational duties.

Hello, I know this is a very late reply but I've just found this forum when searching for for other info. I saw your question about this and you were correct in that 165810 was using AE04B0 but it was merely a miscode of one of the transponder boxes. 57-1419 KC-135 was always the correct user of this code.

165810 was transmitting both AE04A8 and AE04B0 at various times, so it looks as if one of the transponders has had the incorrect code set up.

To solve the mystery of what has happened to 165810, you can look here:

Getting back to the rogue transponder code, it can be quite common to see an incorrect code on older aircraft. I've had experience setting up these codes on [civil] aircraft and on older generation aircraft, it's not as simple as you might think. A lot of older generation aircraft the actual code is not generated in the transponder unit at all, it is generated by program pins on the aircraft wiring side, so once set-up any transponder plugged into that aircraft will automatically generate the correct code. Obviously, in this situation the actual hex code has to be converted into binary as the aircraft digital systems only actually work in binary [with normally a positive voltage being a "1" and a ground being a "0"] That binary figure then has to be transferred to wiring on the connector on the back on the transponder unit [normally a plug with many pins] so the potential for a coding error is quite high. That said, any decent engineer would always set up a ground test set after the installation had been done to check the hexcode outputs [on both systems].

This is also one of the reasons that aircraft when they change hands [and registrations] quite often fly around for a while with the code of the previous identity, as it's not a five minute job to recode on the older aircraft that are hard wired.

 

[AvionicEng747]

Thanks.



These are the PHX based K35Rs (using the COPPER callsign) noted since May 2020, with the date last seen (month.day)

AE04B0 57-1419 07.10
AE0266 57-1469 11.03
AE035E 58-0077 11.04
AE047D 59-1450 10.30 - departed on Middle East Tour 09.29
AE07A7 59-1498 10.29 - > transferred from BGR between 08.24 to 09.11 on loan ?
AE07B0 61-0284 06.05
AE0667 61-0317 11.07 - departed on Middle East Tour on 09.28
AE026C 62-3516 09.08
AE038A 62-3531 11.05 - various Coronet/CAP
AE07B9 62-3550 10.26
AE014F 63-8036 10.12 - returned from Middle East Tour
AE05A4 62-3500 11.07

That's based on callsigns only so maybe the IAB ones you are talking about transferred before May and I missed them ? Or you are using another source beside ADSB-X ?

Of your listing above two of the KC-135 are no longer with the AZ ANG as of Jan 2021. Note that 58-0077 is actually a KC-135T variant.

58-0077 is currently with the 147thARS/PA ANG at Pittsburgh
59-1498 is currently with the 132ndARS/ME ANG at Bangor

 

[AirScan]

Hello, I know this is a very late reply but I've just found this forum when searching for for other info.

Hi, thanks for the reply, great information.