
Let’s pick this up right where the rules get practical. We’re looking at two separate but related pieces of air law: the call sign you use when you’re being intercepted, and what air traffic services must do the moment they learn an interception is happening in their airspace.
First, the call sign. When an aircraft is intercepted, the pilot is expected to give a call sign — but not just any call sign. The rule says the call sign to be given is the one used in RT communications with ATC, and that call sign must correspond to the aircraft identification on the flight plan. So think of it this way: the flight plan is the master record. The call sign you use on the radio with air traffic control is the same one you file on that flight plan, and that’s the one you use in an interception situation. Why does this matter? Because the intercepting aircraft and the ground units need to positively identify you. If you switch to some random call sign, you break the link between the radar target, the flight plan, and the voice transmission. So the rule locks you to the RT call sign that matches the flight plan identification.
Now, the second point is a practical caveat. The rule says circumstances may not always permit, or make it desirable, to use the word ‘HIJACK’. So the standard phraseology for a hijack situation is to transmit the word ‘HIJACK’ — but the rule acknowledges that sometimes you can’t say it, or it’s not wise to say it. Maybe the hijacker is listening, maybe the radio situation doesn’t allow it. So the law builds in that flexibility: you’re not always required to use that exact word if the situation makes it impractical or unsafe. That’s the nuance — the rule anticipates real-world constraints.
Now let’s move to the bigger block: Rule 6.56, Action by ATS in the Event of Interception. This is about what air traffic services must do once they learn an aircraft is being intercepted in their area of responsibility. And note the trigger: “as soon as air traffic services learns that an aircraft is being intercepted in its area of responsibility.” So the moment that knowledge lands, a sequence of mandatory steps kicks in.
Step (a): Attempt to establish communications with the intercepted aircraft via any means available, including 121.5 MHz. That’s the international VHF emergency frequency — the guard frequency. So the first move is to try to raise the intercepted aircraft on any channel you can, and 121.5 is the designated one to try.
Step (b): Inform the pilot of the intercepted aircraft of the interception — if it does not already know. That’s a nice touch: the pilot might be unaware they’re being intercepted, so ATS tells them.
Step (c): Establish communications with the ATSU maintaining communication with the intercepting aircraft, and provide that ATSU with details of the intercepted aircraft. ATSU is air traffic services unit. So ATS doesn’t just talk to the intercepted aircraft — it also reaches out to the unit that’s talking to the interceptor, and shares the intercepted aircraft’s details.
Step (d): Relay messages as required between the ATSU of the intercepting aircraft and the intercepted aircraft. So ATS becomes the message relay between those two parties when needed.
Step (e): In co-ordination with the above ATSU, take all necessary steps to ensure the safety of the intercepted aircraft. Note the spelling in the excerpt — “incepted” — but the intent is the intercepted aircraft. So safety is the overriding duty, coordinated with the other unit.
Step (f): Inform ATS units serving adjacent FIRs if it appears that either aircraft has strayed into any one of them. FIR is flight information region. So if it looks like the intercepted aircraft or the intercepting aircraft has drifted into a neighbouring FIR, ATS must alert the units serving those regions.
Now, there’s a second scenario: what if the interception happened outside ATS’s area of responsibility? Then the duties change. First, ATS must inform the ATS unit serving the airspace where the interception took place — give them the circumstances and any information that will help identify the intercepted aircraft — and request that unit to take the actions itemised in the previous paragraph. So the unit on the scene is asked to run through steps (a) through (f). Second, ATS must relay messages as required between the intercepted aircraft and the appropriate ATS unit or the intercepting aircraft. So even from outside the area, ATS still acts as a relay.
Let me tie this together. The call sign rule is about identification — you use the RT call sign that matches the flight plan. The hijack caveat is about flexibility — you’re not forced to say ‘HIJACK’ if circumstances make it impractical. And Rule 6.56 is the ATS response playbook: establish comms on 121.5, inform the pilot, coordinate with the intercepting unit, relay messages, ensure safety, and alert adjacent FIRs — and if the interception is outside your area, hand the action list to the unit that owns that airspace and keep relaying messages.
That’s the full picture for this part of the rules.
This is one saved preview. Continue from this exact book or paper with BlueFlash voice AI.
Continue in BlueFlash