![]() |
Russian operator in UK?
Just a bit puzzled by a 429 , G-HPIN, squawking a Russian operator's Callsign. KNM08. Anyone know why?
|
FYI, G-HPIN is operated by GB Helicopters. Their callsigns are 'Kingdom XX', normally abbreviated to KDM08 etc. I suspect that KNM08 was just a typo when inputting the callsign into the transponder.
|
Originally Posted by Bravo73
(Post 11992133)
FYI, G-HPIN is operated by GB Helicopters. Their callsigns are 'Kingdom XX', normally abbreviated to KDM08 etc. I suspect that KNM08 was just a typo when inputting the callsign into the transponder.
|
Originally Posted by Bravo73
(Post 11992133)
FYI, G-HPIN is operated by GB Helicopters. Their callsigns are 'Kingdom XX', normally abbreviated to KDM08 etc. I suspect that KNM08 was just a typo when inputting the callsign into the transponder.
|
Really?
It certainly seems to be in the helicopters that I fly. |
Originally Posted by chevvron
(Post 11992209)
'Into the transponder?' Code/callsign conversion is not done that way.
|
Originally Posted by chevvron
(Post 11992209)
'Into the transponder?' Code/callsign conversion is not done that way.
Typo's in the mode-S callsign, happen regularly and are corrected on the fly by the crew whenever requested by ATC. (and using the registration as callsign is more common in the GA world) |
Originally Posted by chevvron
(Post 11992209)
'Into the transponder?' Code/callsign conversion is not done that way.
The transponder on the machine I fly has pilot changeable inputs for registration and callsign / flt number. OH |
I was thinking ATC transponders. ATC units having SSR displays can enter their own callsigns independently of mode S inputs because not all ATC units have access to Mode S and this means duplicated callsigns can be displayed either on radar displays or other surveillance displays as in the examples at #1 and #2.
How this is resolved I haven't a clue. |
GB Helicopters has used KNM “Kingdom” since at least May 2013
see https://www.faa.gov/air_traffic/publ...section_1.html |
I stand corrected :O
|
24 bit address and resultant hex code is not a typical "user configuration" but Flight ID is by the operator. How the Flight ID is then interpreted can lead to mismatch by certain platforms.
|
| All times are GMT. The time now is 11:16. |
Copyright © 2026 MH Sub I, LLC dba Internet Brands. All rights reserved. Use of this site indicates your consent to the Terms of Use.