Very interesting info, thanks for sharing! I will point out though that that twitter link features RUDY33, not RUDY30 as in my post. It would be nice to know which HEX ID this RUDY33 was squawking, as that is independent from the callsign and bound to the ICAO number of the aircraft itself.

I also found this link https://www.cdcr.ca.gov/facility-locator/conservation-camps/miramonte/ which is an official state of California site describing that detention center RUDY30 appeared to have taken off from yesterday. It mentions that the camp produces basic welding products and signs, so this may have just been the navy picking up some stuff to use around the base.

Still kinda feels odd to me, especially with them squawking ANON briefly. I'll admit to not knowing an awful lot about their transponder system though, so that may just be what the transponder announces its callsign as in different situations. I did notice another V22 squawk ANON another time last night, and its reported flight path was EXTREMELY erratic, which led me to believe it may have been experiencing issues with the wiring to its GPS antenna, or the antenna itself. That system is separate from the transponder though, even if it feeds data to it, so I can't really see how the erratic POS data could be linked, at least from an avionics perspective, to the aircraft's transponder. Maybe they share a connector somewhere that was getting loose? Thinking about it even more, if there was a loose connection anywhere in the transponder wiring chain, especially between the box and the antenna, I would expect a complete loss of data transmission, not just a loss of callsign. That, and this is a military aircraft...wiring and boxes should all have multiple redundancy layers. Idk. This has been interesting regardless.

Thanks for contributing to my shit show!

EDIT: I just found this link https://twitter.com/tropicostation/status/1334668794917048323 in the comments on your twitter link and realized it may have been what you were referring to. It does indeed claim it is RUDY30 and the ICAO number matches with my ANON/RUDY30. They say that the bird was just delivered to the navy in June 2020, so it's pretty dang new. Also claims it was the first bird of its configuration to be built and delivered. Sheds new light on my brainstorming about wiring issues. Most people would think that a brand new, first of its configuration bird would be less likely to have wiring issues, but anybody who has worked in the aviation industry will laugh hysterically at that notion.

Very interesting info, thanks for sharing! I will point out though that that twitter link features RUDY33, not RUDY30 as in my post. It would be nice to know which HEX ID this RUDY33 was squawking, as that is independent from the callsign and bound to the ICAO number of the aircraft itself.

I also found this link https://www.cdcr.ca.gov/facility-locator/conservation-camps/miramonte/ which is an official state of California site describing that detention center RUDY30 appeared to have taken off from yesterday. It mentions that the camp produces basic welding products and signs, so this may have just been the navy picking up some stuff to use around the base.

Still kinda feels odd to me, especially with them squawking ANON briefly. I'll admit to not knowing an awful lot about their transponder system though, so that may just be what the transponder announces its callsign as in different situations. I did notice another V22 squawk ANON another time last night, and its reported flight path was EXTREMELY erratic, which led me to believe it may have been experiencing issues with the wiring to its GPS antenna, or the antenna itself. That system is separate from the transponder though, even if it feeds data to it, so I can't really see how the erratic POS data could be linked, at least from an avionics perspective, to the aircraft's transponder. Maybe they share a connector somewhere that was getting loose? Thinking about it even more, if there was a loose connection anywhere in the transponder wiring chain, especially between the box and the antenna, I would expect a complete loss of data transmission, not just a loss of callsign. That, and this is a military aircraft...wiring and boxes should all have multiple redundancy layers. Idk. This has been interesting regardless.

Thanks for contributing to my shit show!

Very interesting info, thanks for sharing! I will point out though that that twitter link features RUDY33, not RUDY30 as in my post. It would be nice to know which HEX ID this RUDY33 was squawking, as that is independent from the callsign and bound to the ICAO number of the aircraft itself.

I also found this link https://www.cdcr.ca.gov/facility-locator/conservation-camps/miramonte/ which is an official state of California site describing that detention center RUDY30 appeared to have taken off from yesterday. It mentions that the camp produces basic welding products and signs, so this may have just been the navy picking up some stuff to use around the base.

Still kinda feels odd to me, especially with them squawking ANON briefly. I'll admit to not knowing an awful lot about their transponder system though, so that may just be what the transponder announces its callsign as in different situations. I did notice another V22 squawk ANON another time last night, and it's reported flight path was EXTREMELY erratic, which led me to believe it may have been experiencing issues with the wiring to its GPS antenna, or the antenna itself. That system is separate from the transponder though, even if it feeds data to it, so I can't really see how the erratic POS data could be linked, at least from an avionics perspective, to the aircraft's transponder. Maybe they share a connector somewhere that was getting loose? Thinking about it even more, if there was a loose connection anywhere in the transponder wiring chain, especially between the box and the antenna, I would expect a complete loss of data transmission, not just a loss of callsign. Idk. This has been interesting regardless.

Thanks for contributing to my shit show!