English R/T procedures.
Luvverley!
Join Date: Jun 2004
Location: --
Posts: 259
Likes: 0
Received 0 Likes
on
0 Posts
Many good and valid points already expressed here. Particularly with "homeguard" who states:
Any ATCO worth their licence only needs accurate information from participating pilots to do that. And it's done well, generally.
To IO540: many ATSUs will have a "discrete" squawk which can be allocated. This allows adjacent radar-equipped units to see instantly exactly who is talking to that a/c, and if necessary "request co-ordination."
The FIS controller dosn't need to see a screen to give good general advice relevant to the position, altitude and routing passed to them and they do the job well.
To IO540: many ATSUs will have a "discrete" squawk which can be allocated. This allows adjacent radar-equipped units to see instantly exactly who is talking to that a/c, and if necessary "request co-ordination."
Join Date: Jun 2003
Location: EuroGA.org
Posts: 13,787
Likes: 0
Received 0 Likes
on
0 Posts
Any ATCO worth their licence only needs accurate information from participating pilots to do that. And it's done well, generally.
Of course, we know that pilots never give duff position info. Why would they? Navigation is always perfect, and nobody ever wants to get an earlier clearance to fly an approach (than somebody else they can hear on the radio who is also flying to the same place) because avgas costs virtually nothing
Many times I have seen somebody give totally duff position info (within an ATZ) so they could beat somebody else to be cleared to the OHJ position, etc.
To IO540: many ATSUs will have a "discrete" squawk which can be allocated. This allows adjacent radar-equipped units to see instantly exactly who is talking to that a/c, and if necessary "request co-ordination."
