Mil/Civ Operations
Join Date: Sep 2005
Location: Dreamland
Posts: 89
Likes: 0
Received 0 Likes
on
0 Posts
Mil/Civ operations.
The point I was trying to make, as I think was GMST's in starting this thread, is that we need standardisation.
I was not aiming to be critical of the military ATCO involved, but of the system which required her to undergo such a palaver.
In answer to rej's question, if an aircraft is unable to squawk mode c, for whatever reason, then I, or any other civil ATCO may *not* authorise it to climb to FL100+. In the unlikely event, at least with civil aircraft capable of operating at these levels, that the failure occurred above FL100, then it WOULD be descened asap.
Is it so difficult for the military authorities to permit their controllers to deem a track observed on a valid civil squawk, with NMC, to be below FL100?
This is just one of the many points which need addressing (VFR at night, not permitted under civil rules)!
The point I was trying to make regarding ex-military ATCOs is that as we work alongside them ever day, we probably have a better understanding of military controlling than you think. In fact the watch that I am on is made up entirely of controllers who are ex-military (yes, myself included)!
I was not aiming to be critical of the military ATCO involved, but of the system which required her to undergo such a palaver.
In answer to rej's question, if an aircraft is unable to squawk mode c, for whatever reason, then I, or any other civil ATCO may *not* authorise it to climb to FL100+. In the unlikely event, at least with civil aircraft capable of operating at these levels, that the failure occurred above FL100, then it WOULD be descened asap.
Is it so difficult for the military authorities to permit their controllers to deem a track observed on a valid civil squawk, with NMC, to be below FL100?
This is just one of the many points which need addressing (VFR at night, not permitted under civil rules)!
The point I was trying to make regarding ex-military ATCOs is that as we work alongside them ever day, we probably have a better understanding of military controlling than you think. In fact the watch that I am on is made up entirely of controllers who are ex-military (yes, myself included)!
Guest
Posts: n/a
From the AIP
1.3.3.2 In specific cases where short notice exemption from the carriage and operation of SSR Transponder equipment is required
by an operator, entry may be permitted on an individual flight basis provided that the approval of the ATC Unit responsible for the airspace has been obtained and that the pilot complies with the appropriate Rules of the Air and ATC which apply to the airspace concerned. Operators should note that this does not apply in respect of the London TMA where for safety and practical purposes short notice exemptions cannot be accommodated and the procedure detailed in paragraph 1.3.3.1 must be followed. The controlling ATC Unit is to be contacted prior to departure or, in exceptional circumstances, on the appropriate ATC frequency prior to entry to the specified airspace. Entry under an exemption is not guaranteed in normal circumstances and will only be permitted at the discretion of ATC where it does not impinge on the safe operation within the airspace involved. Short notice exemptions will only be granted on a case by case basis and will not be given to operators who require regular access to airspace to which mandatory carriage and operation of SSR regulations apply. Such applications should be submitted to AUS in accordance with paragraph 1.3.3.1. Cases in respect of transponder failure are to be dealt with in accordance with the SSR Operating Procedures as promulgated in ENR 1.6.2,
paragraph 3. An aircraft in an emergency situation will be afforded the appropriate level of priority which shall include implicit exemptions from the appropriate legislation for the purpose of saving life.
and
3.2 Failure after departure
3.2.1 If the transponder fails after departure or en-route, ATS Units will endeavour to provide for continuation of the flight in
accordance with the original flight plan. In certain traffic situations this may not be possible particularly when the failure is detected shortly after take-off. The aircraft may then be required to return to the departure aerodrome or to land at another aerodrome acceptable to the operator and to ATC. After landing, pilots shall make every effort to have the transponder restored to normal operation. If the transponder cannot be repaired then the provisions in paragraph 3.1.1 apply.
3.3 At present the temporary failure of SSR Code C alone would not restrict the normal operation of the flight.
Toadpool, it would appear to me that ATSUs are permitted to allow NMC flight above FL100.
... and before anyone starts, in this respect mil aircraft are subject to exactly the same regulations.
1.3.3.2 In specific cases where short notice exemption from the carriage and operation of SSR Transponder equipment is required
by an operator, entry may be permitted on an individual flight basis provided that the approval of the ATC Unit responsible for the airspace has been obtained and that the pilot complies with the appropriate Rules of the Air and ATC which apply to the airspace concerned. Operators should note that this does not apply in respect of the London TMA where for safety and practical purposes short notice exemptions cannot be accommodated and the procedure detailed in paragraph 1.3.3.1 must be followed. The controlling ATC Unit is to be contacted prior to departure or, in exceptional circumstances, on the appropriate ATC frequency prior to entry to the specified airspace. Entry under an exemption is not guaranteed in normal circumstances and will only be permitted at the discretion of ATC where it does not impinge on the safe operation within the airspace involved. Short notice exemptions will only be granted on a case by case basis and will not be given to operators who require regular access to airspace to which mandatory carriage and operation of SSR regulations apply. Such applications should be submitted to AUS in accordance with paragraph 1.3.3.1. Cases in respect of transponder failure are to be dealt with in accordance with the SSR Operating Procedures as promulgated in ENR 1.6.2,
paragraph 3. An aircraft in an emergency situation will be afforded the appropriate level of priority which shall include implicit exemptions from the appropriate legislation for the purpose of saving life.
and
3.2 Failure after departure
3.2.1 If the transponder fails after departure or en-route, ATS Units will endeavour to provide for continuation of the flight in
accordance with the original flight plan. In certain traffic situations this may not be possible particularly when the failure is detected shortly after take-off. The aircraft may then be required to return to the departure aerodrome or to land at another aerodrome acceptable to the operator and to ATC. After landing, pilots shall make every effort to have the transponder restored to normal operation. If the transponder cannot be repaired then the provisions in paragraph 3.1.1 apply.
3.3 At present the temporary failure of SSR Code C alone would not restrict the normal operation of the flight.
Toadpool, it would appear to me that ATSUs are permitted to allow NMC flight above FL100.
... and before anyone starts, in this respect mil aircraft are subject to exactly the same regulations.
Join Date: Aug 2002
Location: where should i be today????
Age: 57
Posts: 342
Likes: 0
Received 0 Likes
on
0 Posts
London Mil
Toadpool, it would appear to me that ATSUs are permitted to allow NMC flight above FL100.
That is one of the points that I was trying to make. However, I would like to know why Toadpool has not responded to my point
'However, IMHO if you have time to explain to that civil ATCOs can not permit traffic to operate FL100+ without mode C, I would suggest that you would have had time to bite your tongue and carry out the coordination as requested.'
when I instructed ab-initios and examined controllers I taught them to deal with controlling first and then resolve any disagreements off console via landline. Is this not one of the first principles of control before admin?
Toadpool, it would appear to me that ATSUs are permitted to allow NMC flight above FL100.
That is one of the points that I was trying to make. However, I would like to know why Toadpool has not responded to my point
'However, IMHO if you have time to explain to that civil ATCOs can not permit traffic to operate FL100+ without mode C, I would suggest that you would have had time to bite your tongue and carry out the coordination as requested.'
when I instructed ab-initios and examined controllers I taught them to deal with controlling first and then resolve any disagreements off console via landline. Is this not one of the first principles of control before admin?
I'd be prepared to wager a large proportion of Toadpool's salary that, when examined carefully, there are few differences in the regulations for civ/mil. Some of the aircraft operating procedures may differ (VFR at night), but the ATC rules are drawn from the same pot and then put into the appropriate documents. If I'm talking bolleaux, please give concrete examples (with references) and I'll retract.
Canary Boy,
You are correct. It is the interpretation of those rules that are different, sometimes corrupted by people in the training environment putting on their own little spin on things.
You are correct. It is the interpretation of those rules that are different, sometimes corrupted by people in the training environment putting on their own little spin on things.
Join Date: Sep 2005
Location: Dreamland
Posts: 89
Likes: 0
Received 0 Likes
on
0 Posts
Mil/Civ operations.
This is danger of becoming a debate on one incident, rather than answering the original question posed.
Rej, if this were an isolated incident, then perhaps I may have bit my tongue. However it is not, it seems to happen several times a day every day.
Let me explain from my viewpoint. Ignoring the issue of mode c and FL100 for now, I had given the other ATCO all the information she needed in that she was told that the track was a FIS (i.e. not under control), and not above 3000'. As far as I was concerned this made it known traffic to her, and if that information subsequently changed the onus would be on me to inform her, so no RNGrommit it was not dead information. As she was going to achieve a minimum vertical separation of 18000'+, no co-ordination was required and I did not wish to get into a lengthy discussion regarding traffic that was not really relevant.
Now for the FL100 discussion.
London Mil's quote has missed off the start of the relevant part of the AIP, which states that aircraft operating IFR in CAS, and outside CAS FL100+ are required to have a serviceable transponder with both mode A and C. Also just before London Mil's quote it states that exemptions from the requirement are not normally granted.
It then goes on to state that in exeptional circumstances exemptions may be granted, etc.
I would suggest that a civil unit considering granting such an exemption would weigh the benefits very carefully against the extra workload created, as they would be expected to notify any other unit on the aircraft's track of the non-compliance. At the very least they would be expected to initiate any co-ordination required against conflicting tracks.
With reference to the failure of mode C only, why does the sentence refer to "temporary failure", not just "failure". I may be wrong (again), but I would interpret that to mean "intermittent".
Canary Boy, I would agree that the basic regulations are broadly similar, but there are differences in the operating practices. Coming up with concrete examples (with references) will, as I'm sure you're aware, be difficult and time consuming.
One example would be the understanding of a "handover". I can take, and hand over traffic to other units without any direct interaction with the other controller, in other words, silent handovers. Military handovers normally involve direct controller/controller communication.
I could go on but I think thats enough. I'll sit back now and await the flack.
Rej, if this were an isolated incident, then perhaps I may have bit my tongue. However it is not, it seems to happen several times a day every day.
Let me explain from my viewpoint. Ignoring the issue of mode c and FL100 for now, I had given the other ATCO all the information she needed in that she was told that the track was a FIS (i.e. not under control), and not above 3000'. As far as I was concerned this made it known traffic to her, and if that information subsequently changed the onus would be on me to inform her, so no RNGrommit it was not dead information. As she was going to achieve a minimum vertical separation of 18000'+, no co-ordination was required and I did not wish to get into a lengthy discussion regarding traffic that was not really relevant.
Now for the FL100 discussion.
London Mil's quote has missed off the start of the relevant part of the AIP, which states that aircraft operating IFR in CAS, and outside CAS FL100+ are required to have a serviceable transponder with both mode A and C. Also just before London Mil's quote it states that exemptions from the requirement are not normally granted.
It then goes on to state that in exeptional circumstances exemptions may be granted, etc.
I would suggest that a civil unit considering granting such an exemption would weigh the benefits very carefully against the extra workload created, as they would be expected to notify any other unit on the aircraft's track of the non-compliance. At the very least they would be expected to initiate any co-ordination required against conflicting tracks.
With reference to the failure of mode C only, why does the sentence refer to "temporary failure", not just "failure". I may be wrong (again), but I would interpret that to mean "intermittent".
Canary Boy, I would agree that the basic regulations are broadly similar, but there are differences in the operating practices. Coming up with concrete examples (with references) will, as I'm sure you're aware, be difficult and time consuming.
One example would be the understanding of a "handover". I can take, and hand over traffic to other units without any direct interaction with the other controller, in other words, silent handovers. Military handovers normally involve direct controller/controller communication.
I could go on but I think thats enough. I'll sit back now and await the flack.
Join Date: Aug 2002
Location: where should i be today????
Age: 57
Posts: 342
Likes: 0
Received 0 Likes
on
0 Posts
Toadpool
I don't want to keep on about this but you are never thorough enough in your application of the rules.
First of all she (the mil controller) needed coordination as the traffic information that you issued became dead information and of no use to her once it was passed. She quited rightly needed this act of negiation between 2 or more controllers to agree a course of action as the ac had no mode C. Even though the FIS ac was 'not under control' you could have effected coordination by identifying the ac and obtaining compliance from the pilot that he/she would not fly above a certain altitude that meets the coordination criteria.
Lets not make this into a p1$$ing match but, had the ac been under RAS with unknown traffic with no mode C as a conflictor, she was spot on with her actions.
And if it is not an isolated incident have you tried to get your supervisors or watch manager to speak to the relevant unit and work towards understanding why the mil controllers insist on what you consider to be superfluous control actions. Without intruding on what seems to be inter-unit disagreement, the only way to resiolve it is to discuss it.
I don't want to keep on about this but you are never thorough enough in your application of the rules.
First of all she (the mil controller) needed coordination as the traffic information that you issued became dead information and of no use to her once it was passed. She quited rightly needed this act of negiation between 2 or more controllers to agree a course of action as the ac had no mode C. Even though the FIS ac was 'not under control' you could have effected coordination by identifying the ac and obtaining compliance from the pilot that he/she would not fly above a certain altitude that meets the coordination criteria.
Lets not make this into a p1$$ing match but, had the ac been under RAS with unknown traffic with no mode C as a conflictor, she was spot on with her actions.
And if it is not an isolated incident have you tried to get your supervisors or watch manager to speak to the relevant unit and work towards understanding why the mil controllers insist on what you consider to be superfluous control actions. Without intruding on what seems to be inter-unit disagreement, the only way to resiolve it is to discuss it.
Join Date: Jun 2003
Location: europe
Posts: 38
Likes: 0
Received 0 Likes
on
0 Posts
JSP318A as was and now 55.....
MATS Pt1
Take the best from both and put them together.... what a fantastic system we'd have!!
There are some really good things in the JSP and MATS...it's high time that everyone got together to produce an even better system.... crumbs this is the 21st century after all!
MATS Pt1
Take the best from both and put them together.... what a fantastic system we'd have!!
There are some really good things in the JSP and MATS...it's high time that everyone got together to produce an even better system.... crumbs this is the 21st century after all!
Join Date: Aug 2002
Location: where should i be today????
Age: 57
Posts: 342
Likes: 0
Received 0 Likes
on
0 Posts
yellowplane, couldn't agree more.
In Canada they have MANOPS which suits both roles; it has a mil specific pages that deal with the mil-specific issues such as formation splits etc
In Canada they have MANOPS which suits both roles; it has a mil specific pages that deal with the mil-specific issues such as formation splits etc
Join Date: Sep 2005
Location: Dreamland
Posts: 89
Likes: 0
Received 0 Likes
on
0 Posts
Mil/Civ operations.
Rej, the rules you refer to may be yours, but they are not mine.
Surely this was the whole point in this thread being started. To a civil ATCO co-ordination is the act of negotiation,etc,etc. The phraseology "your traffic not above xxx, my traffic not below xxx" and "co-ordination agreed" is not required.
As I have said before, I fully understand that the mil ATCO was only following her instructions.
If the other ATCO concerned was civilian the exchange wolud probably have been something like " XXXX here, what's the xxxx 10 miles east of you doing?" , "Not above 3000' " , "Roger, Thanks". This is if the call was made at all.
Flower says in his post at the start of this thread that it takes 3 times as long to hand an aircraft to a military ATCO than to a civil one. This is often time we do not have.
Why does it take so long? Is it because military procedures cause an unnecessary increase in workload? Are civil ATCOs really being gash and unprofessional?
It is not for me to say, but I do feel it needs addressing.
Surely this was the whole point in this thread being started. To a civil ATCO co-ordination is the act of negotiation,etc,etc. The phraseology "your traffic not above xxx, my traffic not below xxx" and "co-ordination agreed" is not required.
As I have said before, I fully understand that the mil ATCO was only following her instructions.
If the other ATCO concerned was civilian the exchange wolud probably have been something like " XXXX here, what's the xxxx 10 miles east of you doing?" , "Not above 3000' " , "Roger, Thanks". This is if the call was made at all.
Flower says in his post at the start of this thread that it takes 3 times as long to hand an aircraft to a military ATCO than to a civil one. This is often time we do not have.
Why does it take so long? Is it because military procedures cause an unnecessary increase in workload? Are civil ATCOs really being gash and unprofessional?
It is not for me to say, but I do feel it needs addressing.
Toadpool, I'm sorry but if that was the coordination phraseology that you use and it was transcripted and presented to the UKAB in the event that an ac under your or the other unit's control broke that coordination, then you wouldn't have a leg to stand on as you have not agreed to anything. As Rej said, the mil controller needed coordination and was right to pusue the matter with you. I cannot believe that JSP552 and MATS Pt 1 differ to the extent that coordination was not required under the terms of MATS Pt 1. While what you are saying is very common-sensical, it's not right at the moment. It would be interesting to hear from some of the guys at Norwich who deal with this situation on a daily basis. As I've said before, the problem is one of interpretation. You only have to look at the differences in application of RAS between mil and civ to see that.
As Rej and Yellow plane have said, what we need is a single document MATS Pt 552(?) which does not leave items open to interpretation.
The silent handovers that you mentioned are, in military terms, written agreements in which a series of terms have to be met for the silent handover to take place. One of these is a pre-note. I'm guessing that when you do these silent handovers between your local units that you do a pre-note first? Otherwise it's just a free-call. If you've got the time to do a pre-note, then you have time to do a radar handover: there is very little difference in the time taken! Besides, they don't take that long if you follow the format...
As Rej and Yellow plane have said, what we need is a single document MATS Pt 552(?) which does not leave items open to interpretation.
The silent handovers that you mentioned are, in military terms, written agreements in which a series of terms have to be met for the silent handover to take place. One of these is a pre-note. I'm guessing that when you do these silent handovers between your local units that you do a pre-note first? Otherwise it's just a free-call. If you've got the time to do a pre-note, then you have time to do a radar handover: there is very little difference in the time taken! Besides, they don't take that long if you follow the format...
Join Date: Sep 2002
Location: UK
Posts: 1,294
Likes: 0
Received 0 Likes
on
0 Posts
If you've got the time to do a pre-note, then you have time to do a radar handover:
PS Flower is a she not a he
Join Date: Sep 2005
Location: Dreamland
Posts: 89
Likes: 0
Received 0 Likes
on
0 Posts
Mil/Civ operations.
Whowhenwhy you are correct in that the phraseology example I used is not co-ordination. This is because a civilian ATCO would not require it as the traffic would be "known" once its intentions (not above 3000') had been passed.
If the situation were to be changed, and the other traffic was descending towards mine, then I would expect the other controller to say something like " Roger I'll descend on top with my xxxx, let me know if yours climbs". Response "Wilco". S/he (sorry Flower) could then descend to a level below FL110, making sufficient allowance for any pressure difference, say FL50, and then further once lateral separation was achieved.
What I'm saying may not be right under military procedures, but it is acceptable under civilian ones.
As an aside, I do find it worrying that a military ATCO will, and has to my knowledge, disregard co-ordination because the phrase "co-ordination agreed" has not been used. I believe that this is one matter that is under investigation following at least one airprox.
Changing the subject slightly, an ex-colleague, a former Squadron Leader at a fast jet base before getting his civilian licences, so with a fair bit of military experience, once said to me that he had never worked so hard until he came to our unit.
If the situation were to be changed, and the other traffic was descending towards mine, then I would expect the other controller to say something like " Roger I'll descend on top with my xxxx, let me know if yours climbs". Response "Wilco". S/he (sorry Flower) could then descend to a level below FL110, making sufficient allowance for any pressure difference, say FL50, and then further once lateral separation was achieved.
What I'm saying may not be right under military procedures, but it is acceptable under civilian ones.
As an aside, I do find it worrying that a military ATCO will, and has to my knowledge, disregard co-ordination because the phrase "co-ordination agreed" has not been used. I believe that this is one matter that is under investigation following at least one airprox.
Changing the subject slightly, an ex-colleague, a former Squadron Leader at a fast jet base before getting his civilian licences, so with a fair bit of military experience, once said to me that he had never worked so hard until he came to our unit.
Okay, that sounds better. I did want to have a proper look in MATS Part 1 but only having dial-up somewhat limits me at the moment. Like I said, what you're suggesting is certainly a common-sense approach. If it really is legislated in this way for you guys and different for us, I wonder if that's because mil ac are expected to follow unpredictable flt paths in all 3 dimensions conducting high energy maneouvers which could quickly see a confliction arise which was not there before??
The 'coordination agreed' statement is an old chestnut that constantly does the rounds. We (the mil) binned it sometime ago and any mil controller who still uses it is not following the standard. Anyone who dis-regards and breaks coordination because that phrase wasn't used will get themselves in trouble. If that was the only reason for breaking the coordination.
As far as your change of subject goes be careful of ex-squadron leaders who say they work hard. It depends on how hard he actually worked as a mil ATCO!
(tongue was in cheek, but now hunkered down preparing for incoming!)
Flower, do you have written silent handover arragements with other local units that you use following your ATSAs pre-note. Or is it a local ladies/gentlemens agreement?
The 'coordination agreed' statement is an old chestnut that constantly does the rounds. We (the mil) binned it sometime ago and any mil controller who still uses it is not following the standard. Anyone who dis-regards and breaks coordination because that phrase wasn't used will get themselves in trouble. If that was the only reason for breaking the coordination.
As far as your change of subject goes be careful of ex-squadron leaders who say they work hard. It depends on how hard he actually worked as a mil ATCO!
(tongue was in cheek, but now hunkered down preparing for incoming!)Flower, do you have written silent handover arragements with other local units that you use following your ATSAs pre-note. Or is it a local ladies/gentlemens agreement?
Last edited by whowhenwhy; 25th Sep 2005 at 13:54.
Join Date: Sep 2002
Location: UK
Posts: 1,294
Likes: 0
Received 0 Likes
on
0 Posts
Whowhenwhy,
pre-notes are in the standard format that are used throughout civil ATC, however this style of pre-note is also used by Military units who also it would seem have absolutely no issue with them, I can think for example that we use the same style with St Athan, Yeovilton, St Mawgen , Lyneham and Brize.
DX, DY, DG and DL seem very familiar with this style of handover and generally speaking all that happens is a squawk and frequency are issued and traffic is always handed clean or the appropriate traffic information passed dependant of type of service.
Of course at our unit we are so familiar with the Military way of doing things that perhaps we have just got very quick at it, but I do feel that since London Military has become Swanwick Military that a greater deal of flexibility has appeared. bearing in mind it should be exactly the same ATCOs I am not entirely sure of this.
There are still some issues that I find as i have already said frustrating, but some of the " we know best" attitude that pervades both sides of this argument I do find rather tiresome.
For all our sakes , either we try to get a standard approach to everything , don't think that will necessarily work, or we just try to get to visit our Civil or military colleagues and gain an understanding of how each other works. I suspect the Military ATCOs are equally bothered by a lack of funds that we Civil ATCOs are regarding liaison visits.
pre-notes are in the standard format that are used throughout civil ATC, however this style of pre-note is also used by Military units who also it would seem have absolutely no issue with them, I can think for example that we use the same style with St Athan, Yeovilton, St Mawgen , Lyneham and Brize.
DX, DY, DG and DL seem very familiar with this style of handover and generally speaking all that happens is a squawk and frequency are issued and traffic is always handed clean or the appropriate traffic information passed dependant of type of service.
Of course at our unit we are so familiar with the Military way of doing things that perhaps we have just got very quick at it, but I do feel that since London Military has become Swanwick Military that a greater deal of flexibility has appeared. bearing in mind it should be exactly the same ATCOs I am not entirely sure of this.
There are still some issues that I find as i have already said frustrating, but some of the " we know best" attitude that pervades both sides of this argument I do find rather tiresome.
For all our sakes , either we try to get a standard approach to everything , don't think that will necessarily work, or we just try to get to visit our Civil or military colleagues and gain an understanding of how each other works. I suspect the Military ATCOs are equally bothered by a lack of funds that we Civil ATCOs are regarding liaison visits.
then I would expect the other controller to say something like " Roger I'll descend on top with my xxxx, let me know if yours climbs".
As an aside, I do find it worrying that a military ATCO will, and has to my knowledge, disregard co-ordination because the phrase "co-ordination agreed" has not been used. I believe that this is one matter that is under investigation following at least one airprox.
There is no difference between the MATS part 1 definition of co-ordination and that in JSP552. MATS part 1 refers controllers to MATS part 2 and this is where it all falls to pieces. There is only one section that helps the whole issue and that is the MACC section.
Coordination (Tactical)
Coordination is defined as - the act of negotiation between two or more controllers each vested with the
authority to make executive decisions appropriate to the task.
Put simply, coordination is effected when the controllers agree a course of action to resolve a
confliction or potential confliction.
However, when undertaking tactical coordination with the Military, MACC controllers need to bear the
following in mind, since this is a different mode of operation to the civilian operation:
• Coordination should take place with the unit/console working the conflicting traffic.
• Use the correct phraseology, which is use of the word “Coordination” not “Traffic Information”
• It is important to be clear (when coordinating) on exactly which traffic is being coordinated
against which traffic. Note: the fact that the MACC traffic may be “known traffic” to the
Military is not sufficient to ensure separation from further traffic that is working the
military.
• If there is more than one confliction, then separate coordination should take place for each
individual track. This may include coordinating with a different console at London (Mil).
• In order to avoid misunderstandings between MACC and London Military over the question of
crossing clearances of CAS, controllers need to bear the following in mind:
– What MACC understand as a ‘crossing clearance’ is understood by the Military as being
a Cleared Flight Path (CFP).
This difference in terminology should not alter MACC procedures since MACC can still issue a
Crossing Clearance/CFP with restrictions, for example, “cross after a certain identified flight”.
Nevertheless, it is important to ensure that when undertaking coordination with the Military,
that any conflicting traffic to the CFP is clearly pointed out to them, understood by them, and
acknowledged.
12.3.3 Phraseology
Where coordination is effected between MACC and military controllers, MACC controllers are to ensure
that the correct phraseology is used and that the action agreed is unambiguous.
Phraseology example for Tactical Coordination:
MACC: “Manchester East– request coordination my traffic EZE226 15nm southeast of Newcastle
heading 170 squawking 6310”
Mil: Wait for the Mil controller to say, “Contact”
MACC: “Maintaining FL150 until south of Leeming then descending FL100, under (Type of Service
RAS/RIS). Your traffic Ottringham 330/25nm tracking northwest squawk/callsign xxxx”
Mil: “Maintaining FL130 on that track (Type of Service RAS/RIS)”
MACC: ”Roger. My traffic maintaining FL150 until clear of your traffic" (Could specify vertical or
horizontal separation)
Both controllers terminate the conversation by exchanging console numbers and Unit callsign.
Mil: “Roger. London Controller 15”
MACC “Manchester East”
So the issue was obviously resolve by MACC and the military sitting down, working the whole problem out and writing an instruction.
Why can't other units do the same.
Coordination (Tactical)
Coordination is defined as - the act of negotiation between two or more controllers each vested with the
authority to make executive decisions appropriate to the task.
Put simply, coordination is effected when the controllers agree a course of action to resolve a
confliction or potential confliction.
However, when undertaking tactical coordination with the Military, MACC controllers need to bear the
following in mind, since this is a different mode of operation to the civilian operation:
• Coordination should take place with the unit/console working the conflicting traffic.
• Use the correct phraseology, which is use of the word “Coordination” not “Traffic Information”
• It is important to be clear (when coordinating) on exactly which traffic is being coordinated
against which traffic. Note: the fact that the MACC traffic may be “known traffic” to the
Military is not sufficient to ensure separation from further traffic that is working the
military.
• If there is more than one confliction, then separate coordination should take place for each
individual track. This may include coordinating with a different console at London (Mil).
• In order to avoid misunderstandings between MACC and London Military over the question of
crossing clearances of CAS, controllers need to bear the following in mind:
– What MACC understand as a ‘crossing clearance’ is understood by the Military as being
a Cleared Flight Path (CFP).
This difference in terminology should not alter MACC procedures since MACC can still issue a
Crossing Clearance/CFP with restrictions, for example, “cross after a certain identified flight”.
Nevertheless, it is important to ensure that when undertaking coordination with the Military,
that any conflicting traffic to the CFP is clearly pointed out to them, understood by them, and
acknowledged.
12.3.3 Phraseology
Where coordination is effected between MACC and military controllers, MACC controllers are to ensure
that the correct phraseology is used and that the action agreed is unambiguous.
Phraseology example for Tactical Coordination:
MACC: “Manchester East– request coordination my traffic EZE226 15nm southeast of Newcastle
heading 170 squawking 6310”
Mil: Wait for the Mil controller to say, “Contact”
MACC: “Maintaining FL150 until south of Leeming then descending FL100, under (Type of Service
RAS/RIS). Your traffic Ottringham 330/25nm tracking northwest squawk/callsign xxxx”
Mil: “Maintaining FL130 on that track (Type of Service RAS/RIS)”
MACC: ”Roger. My traffic maintaining FL150 until clear of your traffic" (Could specify vertical or
horizontal separation)
Both controllers terminate the conversation by exchanging console numbers and Unit callsign.
Mil: “Roger. London Controller 15”
MACC “Manchester East”
So the issue was obviously resolve by MACC and the military sitting down, working the whole problem out and writing an instruction.
Why can't other units do the same.
Join Date: Aug 2002
Location: where should i be today????
Age: 57
Posts: 342
Likes: 0
Received 0 Likes
on
0 Posts
Maybe we should start a new thread: 'Coordination'
The first post would be the correct /approved phraseology used by civilian controllers and that used by military controllers.
The next 20,000 would be bitching over who is right and who is wrong. THERE ARE DIFFERENCES BUT THE COAL-FACE CONTROLLERS ARE NOT IN A POSITION TO DO OTHER THAN WHAT IS RIGHT FOR THEIR TASK.
I think that it is appauling that such a fundimental,vital aspect of our job has differences and the day that it is rationalized is long overdue. I also think that, whilst there are 2 different types of phrases out there, we should aim to go for the one which makes it legally binding for both controllers (ie the lowest common denominator). At the end of the day we have to keep the aircraft safely apart and in doing so often requires 'legally' binding agreements; the only way to make the agreement such is by doing it properly and understanding the other controllers requirements to help them. Yes call it covering your a$$ but if you do thinks corrctly then your aircraft are safe and you are not exposed.
The first post would be the correct /approved phraseology used by civilian controllers and that used by military controllers.
The next 20,000 would be bitching over who is right and who is wrong. THERE ARE DIFFERENCES BUT THE COAL-FACE CONTROLLERS ARE NOT IN A POSITION TO DO OTHER THAN WHAT IS RIGHT FOR THEIR TASK.
I think that it is appauling that such a fundimental,vital aspect of our job has differences and the day that it is rationalized is long overdue. I also think that, whilst there are 2 different types of phrases out there, we should aim to go for the one which makes it legally binding for both controllers (ie the lowest common denominator). At the end of the day we have to keep the aircraft safely apart and in doing so often requires 'legally' binding agreements; the only way to make the agreement such is by doing it properly and understanding the other controllers requirements to help them. Yes call it covering your a$$ but if you do thinks corrctly then your aircraft are safe and you are not exposed.
Last edited by rej; 26th Sep 2005 at 12:11.
Join Date: Jan 2003
Location: wherever I lay my headset
Posts: 538
Likes: 0
Received 0 Likes
on
0 Posts
I've just read through Widger's lengthy post, detailing the MATS rules for corrdination... and, surprise, surprise, they are virtually identical to the JSP552 rules... as has been said before, the difference comes in interpretation and implimentation?
The military controllers who are saying their method is the "right way" are taught to do it "the right way" at Shawbury, which is then re-enforced by every ATCEEB visit... But conversely, the Civil Controllrs have the similar reassurances that what they are doing is perfectly acceptable?
Have we ALL got too pedantic in our standardisation?
How can we be "standard" when the interpretation of mil/civ rules is so different... This is a real challenge for SRG/ATCEEB?
The military controllers who are saying their method is the "right way" are taught to do it "the right way" at Shawbury, which is then re-enforced by every ATCEEB visit... But conversely, the Civil Controllrs have the similar reassurances that what they are doing is perfectly acceptable?
Have we ALL got too pedantic in our standardisation?
How can we be "standard" when the interpretation of mil/civ rules is so different... This is a real challenge for SRG/ATCEEB?