Lajes (Azores) LPLA/TER - 2017 MIL

[DBarty]

My moneys on it being a Navy C-130T that dept Rota or Moron on the 6th at about 09.00z

[DBarty]

I've just seen photos of 165351 & 165130 both at Rota 5/1/17, Looking at the SBS data there's a hell of a lot that does not add up and searching the code 29CBB8 it throws up a lot of what looks like C-130`s due to flight levels, it looks like the dodgy code is used a lot more than thought and id not take any C-130/Navy/USMC number now unless I can put an eyeballed log or photo to back it up which thankfully you can in most instances.

[raameagle]

Did somebody actually read 165160 going into Jacksonville or was that an SBS sighting too?

Regards

[Le Addeur noir]

That's a default hex code and is not a reliable guide as to which airframe is being used by it.

Similarly the hex code 249249, or any combination of those numbers should be ignored.

[Thunderbolt]

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!!!

163591 was caught at Lajes on February 13th wearing RU on tail

[Thunderbolt]

March 4th
RRR9801-3 TOR dep
RRR9401 A330 ZZ338 dep
RCH177 C17 00-0182 dep
GAF689 BD700 1402 arr
EGY1104 C130 1292/SU-BEY arr

RRR9801 ZA607 / EB-X
RRR9802 ZA559 / 049
RRR9803 ZA560 / EB-Q

[Thunderbolt]

March 5th
EGY1105 C130 1277/SU-BAI arr
RCH6360 C130 74-1670 arr and dep
RCH470 C130 74-1671 arr and dep
GAF689 BD700 1402 dep
HKY05 C130 04-3142 dep

[Thunderbolt]

March 6th
EGY1105 C130 1277/SU-BAI dep
EGY1104 C130 1292/SU-BEY dep
AME4571 F900 T18-4 arr and dep
AME3128 C130 TL10-01 arr

[Thunderbolt]

March 7th
AME3128 C130 TL10-01 dep
PAAF392 C130 4177 arr

[catbird]

Departed 8 maart PAF 392

[Thunderbolt]

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?

According to a friend, the right serial of this CNV3422 is 165160/JW and not 165352 like I said. My apologizes for that.

[Hans van Herk]

According to a friend, the right serial of this CNV3422 is 165160/JW and not 165352 like I said. My apologizes for that.

Hello Thunderbolt, thank you for the confirmation on the navy aircraft.
But please put in your future logs if the serials were actually read or obtained through ADS-B. That saves a lot of discussion.

Thank you in advance.
Regards,
Hans van Herk

[raameagle]

Which also proves that the report of 165160 landing at Jacksonville must have been an SBS report too.
When will people learn not to trust SBS when it comes to military aircraft...
Regards

[DBarty]

Thanks for the confirmation on the serial Thunderbolt , now knowing the serial for sure this dept Jacksonville on the 6th or late on the 5th, into Lajes on a gas & go and ended up at Rota by sun down. The sighting of it at Jacks on the 5th was an SBS report and on its correct code, it must have then departed Jax on 29CBB8 and then the code shows back in in the USA on the 11th January. This code shows up too many times to be a technical issue with the boxes I would guess they put certain flights on this code for a reason not known. Initially for some reason I thought it was going westbound which was throwing me out. That's the 3rd Navy C-130 I know of so far this year using that code, 163311 went into Stuttgart 1st March using 29CBB8 and 165158 into Shannon 8th February.

[DBarty]

and your quite correct raameagle never trust sbs 100% only any good as a tool