Thunderbolt wrote:January 6th
CNV3422 C130 165352 arr and dep
RCH225 C17 99-0060 arr and dep
Which tailcode for this 165352? It is normaly a QH and use here a CNV callsign?
Thunderbolt wrote:January 6th
CNV3422 C130 165352 arr and dep
RCH225 C17 99-0060 arr and dep
I have no idea which tailcode he was used. But not the first time I see this C130 using CNV callsignAMC wrote:Thunderbolt wrote:January 6th
CNV3422 C130 165352 arr and dep
RCH225 C17 99-0060 arr and dep
Which tailcode for this 165352? It is normaly a QH and use here a CNV callsign?
It hasnt been a QH for quite some time now. Perhaps several years already. It moved from VMGR-234 to VMGR-452 and now has the NY tail code.AMC wrote:Thunderbolt wrote:January 6th
CNV3422 C130 165352 arr and dep
RCH225 C17 99-0060 arr and dep
Which tailcode for this 165352? It is normaly a QH and use here a CNV callsign?
Thanks Thunderbolt. Yes tally. I mean NY and not QH. Looks like 352 switched to an VR-?? unit.tally wrote:It hasnt been a QH for quite some time now. Perhaps several years already. It moved from VMGR-234 to VMGR-452 and now has the NY tail code.AMC wrote:Thunderbolt wrote:January 6th
CNV3422 C130 165352 arr and dep
RCH225 C17 99-0060 arr and dep
Which tailcode for this 165352? It is normaly a QH and use here a CNV callsign?
It hasnt been a QH for quite some time now. Perhaps several years already. It moved from VMGR-234 to VMGR-452 and now has the NY tail code.[/quote]AMC wrote:Which tailcode for this 165352? It is normaly a QH and use here a CNV callsign?
Thanks Thunderbolt. Yes tally. I mean NY and not QH. Looks like 352 switched to an VR-?? unit.[/quote]tally wrote:It hasnt been a QH for quite some time now. Perhaps several years already. It moved from VMGR-234 to VMGR-452 and now has the NY tail code.AMC wrote:Which tailcode for this 165352? It is normaly a QH and use here a CNV callsign?
rh226 wrote:Would have been interesting to see a picture of this.
A similar situation occurred when 163311 was in Prestwick 02-04/12/2015 calling "CNV3702", but it had arrived/left St. Johns calling "YANKY96". The tail code had been covered over and it had "United States Navy" titles on the main u/c fairing. Possibly of note is that it was using the volatile hex [29CBB8].
Some months later, it re-appeared with VR-55 and coded "RU".
See http://www.fightercontrol.co.uk/forum/v ... lit=163311 ....... no login required
So, possibly, 165352 has been transferred to USN (reserve unit?).
AMC wrote:rh226 wrote:Would have been interesting to see a picture of this.
A similar situation occurred when 163311 was in Prestwick 02-04/12/2015 calling "CNV3702", but it had arrived/left St. Johns calling "YANKY96". The tail code had been covered over and it had "United States Navy" titles on the main u/c fairing. Possibly of note is that it was using the volatile hex [29CBB8].
Some months later, it re-appeared with VR-55 and coded "RU".
See http://www.fightercontrol.co.uk/forum/v ... lit=163311 ....... no login required
So, possibly, 165352 has been transferred to USN (reserve unit?).
164597, 164598, 164106, 163311, 163591 all ex NY and now flies with RU Navy!!! I expect 352 also as an RU aircraft!!!
Therefore to the persons providing logs, please make a note if the serials were actually read or obtained through ADSB !!DBarty wrote:This was not 165352, I noted this airframe back in November not using its correct Hex code and presumed it was using 29CBB8. Ran a check on CNV 3422 for Lajes 6/1/17 and yes it shows up on 29CBB8. This could be any number of C-130`s but was not 165352. This last month I've picked up 165158 & 163311 both using this hex code. 165352 was back on its correct hex code on 10/1/17. So unless someone actually read it off or photographed it the one it actually was will remain a mystery.