New EZY Alphanumeric c/s's
Join Date: Jan 2003
Location: UK
Posts: 22
Likes: 0
Received 0 Likes
on
0 Posts
Perhaps we will get used to them eventually, however, I can admit that since their introduction I have missed more ATC calls to me, and answered more calls not intended for me than ever before. Obviously more concentration required; good way forward!
Join Date: May 1999
Location: Vancouver, BC.
Posts: 748
Likes: 0
Received 0 Likes
on
0 Posts
Topofthestack
This was indeed considered, we looked at giving all STN based a/c a different callsign, the proposal was 'jaffa' for the very reason you mention, however when it came to allocating another three letter identifier this posed a problem, nothing to do with the AOC. We probably could have asked ICAO for another three letter code, however, that in itself opens up a can of worms, and in the end was only dealing with part of the issue.
Your final suggest occurred to me to, why not get your SATCO to speak with our man in Luton?
This was indeed considered, we looked at giving all STN based a/c a different callsign, the proposal was 'jaffa' for the very reason you mention, however when it came to allocating another three letter identifier this posed a problem, nothing to do with the AOC. We probably could have asked ICAO for another three letter code, however, that in itself opens up a can of worms, and in the end was only dealing with part of the issue.
Your final suggest occurred to me to, why not get your SATCO to speak with our man in Luton?
Join Date: Jul 2001
Location: London
Posts: 389
Likes: 0
Received 0 Likes
on
0 Posts
As per the previous post, the initial requirement to move to Alphanumerics was due to the amount of (potential) confusion which was already out there....235, 253, etc. and a concern that it would be totally unmanageable when the Go routes adopted EZY callsigns.
My previous company used alphanumerics, and a lot of thought was put into how easy each callsign was to actually pronounce.....some are virtually impossible! However, given the size of the eJ operation (and timescale to introduce them), the main priority was around avoiding conflicts, and 'niceities' such as pronounciation were probably not considered.
To talk of an "out and back" system (A for outbounds and B for inbounds) doesn't really fit the eJ network, with multiple bases and (on the continent) many interlinked stations. ("Join the dots"!)
Of course in many areas, the fact that eJ were (because of the Go integration) forced to start using 4-digit commercial flight numbers may have actually resolved many of the conflicts anyway, without any need for the coding and de-coding.
My previous company used alphanumerics, and a lot of thought was put into how easy each callsign was to actually pronounce.....some are virtually impossible! However, given the size of the eJ operation (and timescale to introduce them), the main priority was around avoiding conflicts, and 'niceities' such as pronounciation were probably not considered.
To talk of an "out and back" system (A for outbounds and B for inbounds) doesn't really fit the eJ network, with multiple bases and (on the continent) many interlinked stations. ("Join the dots"!)
Of course in many areas, the fact that eJ were (because of the Go integration) forced to start using 4-digit commercial flight numbers may have actually resolved many of the conflicts anyway, without any need for the coding and de-coding.
Join Date: Feb 2002
Location: UK
Age: 46
Posts: 642
Likes: 0
Received 0 Likes
on
0 Posts
I am sure that if I was expecting to land at Luton and got told "vectors down wind RH for 23" I would soon sus it and a gentle reminder that I am for the other field.
Buzz use to manage with alpha numerics, only the CDG had numbers, ie "Ukay 272". We had a nice card that had all the flight numbers on it and next to them the relevant callsign.
When was a Fighter Controller in the RN I sat down in my seat onboard one of Her Majesty's destroyers, to be informed by the Chief Ops Radar that our callsign for the day was Sierra Zero Zulu (have a go people - sit there and try saying Sierra Zero Zulu in a hurried fashion like what you have to when you say "localiser from the right, descend with ILS, 160 til four, 123.8... whilst adjusting the speed bug. selecting flap 5 and identing the ILS....." . After about 15 minutes of tongue twisting gymnastics the aircraft suggested I adopt the callsign "Zulu" which I duly did, cue much banter from the rest of the Ops room about "dont point that chinagraph at me" etc etc!!!!
Buzz use to manage with alpha numerics, only the CDG had numbers, ie "Ukay 272". We had a nice card that had all the flight numbers on it and next to them the relevant callsign.
When was a Fighter Controller in the RN I sat down in my seat onboard one of Her Majesty's destroyers, to be informed by the Chief Ops Radar that our callsign for the day was Sierra Zero Zulu (have a go people - sit there and try saying Sierra Zero Zulu in a hurried fashion like what you have to when you say "localiser from the right, descend with ILS, 160 til four, 123.8... whilst adjusting the speed bug. selecting flap 5 and identing the ILS....." . After about 15 minutes of tongue twisting gymnastics the aircraft suggested I adopt the callsign "Zulu" which I duly did, cue much banter from the rest of the Ops room about "dont point that chinagraph at me" etc etc!!!!
