Author Topic: \"Intercept LLZ\" question  (Read 5639 times)

Offline EHM-2097 Andrei

  • Administrator
  • Intergalactic!!
  • ***
  • Posts: 1,968
  • Karma: 6
\"Intercept LLZ\" question
« on: October 10, 2007, 06:44:03 am »
Hi all,

I'm trying to find out which is the "best practice" for both pilots and ATC.

As a pilot (with not so many hours online), whenever I am instructed to "intercept localizer" I assume I have to maintain latest assigned heading (for a while if necessary) until my NAV instruments tell I am close to crossing the localizer axis.

I assumed the same as approach controller so I used to instruct pilots to intercept localizer with some time in advance.

It work nicely until the day when i issued this instruction a little to early and the pilot IMMEDIATELY pressed "APP" on his autopilot. This resulted of course in a very large zig-zag before he finally was stable on the runway centerline.

My instructor at the time told me I should expect this interpretation from most pilots on IVAO. And this is why I am posting this question here, I assume there are a few :) pilots around so please tell me how you react to the "intercept localizer" instruction.

I am worried because I see obvious risks when issuing this instruction too late so I'm still looking for a method to make everyone happy.

Thanks for your good advice

Andrei
Andrei Vatasescu // EHM-2097


Offline EHM-0654 Murray

  • Administrator
  • Intergalactic!!
  • ***
  • Posts: 4,531
  • Karma: 5
  • VA Management
    • The Ponderings of PMUK
\"Intercept LLZ\" question
« Reply #1 on: October 10, 2007, 08:22:40 am »
Funnily enough, I'd agreed with your personal interpretation Andrei - maintain alt/heading (as required) until the instruments have you on both the localizer and glideslope.

Might I suggest you use the phrase "to intercept the localizer", at the end of something else for instance ("Turn right hdg XXX to intercept the localizer rwy YY, report established", sort of thing)
Murray Crane // EHM-0654 // Twitter
VA Management

KEEP CALM AND CARRY ON

Offline EHM-1651 Christian

  • Martian transfer
  • *******
  • Posts: 616
  • Karma: 0
\"Intercept LLZ\" question
« Reply #2 on: October 10, 2007, 08:38:01 am »
When issued the: Cleared ILS runway ..... report established, I always maintain heading and altitude until i can turn directly onto the localizer, then I engage the approach function on the autopilot or fly the ILS manually. From my point of view this is the correct method of intercepting the ILS, rather then turn so you get onto the LLZ right away which results in a large zig zag pattern most times.
EHM-1651 CHRISTIAN BAKKE "A pilots ego equals the wingspan" Stated by a Captain of Widerøe

Offline EHM-1759 Ricardo

  • Climbing
  • ****
  • Posts: 181
  • Karma: 0
\"Intercept LLZ\" question
« Reply #3 on: October 10, 2007, 11:42:56 am »
Do not forget when ATC instructs you to intercept ILS he must give you at the most 30º degrees in relation centerline of the runway to intercept localizer and perform ILS approach.

Let see a simple example: You have runway 03, the ATC must give you at the most hdg 060 (if you come from the left of the runway) to intercept ILS of this runway, or if you come by the right side of centerline the ATC must give you at the most hdg 001 to intercept the localizer.

Well, about to click APP button, personally I prefer to perform the first part of ILS approach manually to avoid several turns you have talk. When I see I am +/- established I do push APP button. However, do not forget that ILS must be intercepted by the bottom side because of altitude to be read by the glideslope, otherwise the aircraft do not descend...

I hope it helps.
Capt. Ricardo Plácido
EHM-1759
IVAO Senior Flight Captain
IVAO Controller 3

EHM-2029 Sotiris

  • Guest
\"Intercept LLZ\" question
« Reply #4 on: October 10, 2007, 01:56:54 pm »
Hello All,

while I agree with everyone who wrote till now, in my view the confusion is in how you phrase the instruction.

1) Intercept Radial X VOR or Intecept Localiser
This is a fairly direct instruction and it is likely to result in a pilot going for it as a matter of priority.

2) Report established Radial X VOR or Localiser
This is a subtle but important difference. The instruction here is not to intercept ASAP but to report when they do, thus allowing pilots time to perform this in their prefered and usually most effective manner. Usually this should be preceded by a finish in your last command like thus: "When finishing my last command, expect to intercept Radial X or Localiser"

I favour the latter approach to issuing tracking/establishing commands.

EHM-1617 Iain

  • Guest
\"Intercept LLZ\" question
« Reply #5 on: October 10, 2007, 07:21:10 pm »
Hi

I can only comment on the situation on IVAO in the UK, which mirrors what happens in real life in the UK.

First of all, we do not use the phrase "Cleared ILS runway XX". The reason for this is simple: using that phrase gives away control of the altitude to the pilot. Many pilots, on hearing this, descend immediately to the published Glideslope Intercept altitude and this could create problems with traffic below or even terrain.

Instead, we use "report established on the localiser" or "report localiser established". These phrases mean that you should maintain heading until you can make a smooth turn on the localiser. Realistic add-on autopilots simulate this very well - even at extreme intercept angles. (Incidentally Ricardo, here we are allowed intercept angles between 30 and 45 degrees, with 30 or 40 degrees being the norm).

Then, when the pilot reports established on the localiser, we say "descend on the ILS". This means that altitude should be maintained until intercepting the glide and then a smooth descent should be initiated. During periods of heavy traffic, the two phrases can be combined into "when established on the localiser, descend on the ILS", to which the response is exactly the same.

Let me try an example; EHM123 is inbound into Heathrow's 27L from the north side. '...' denotes a pause.

"EHM123 turn left heading 120 degrees, 26 miles" (26 miles refers to the distance from touchdown, for descent planning)
"EHM123 descend to altitude 4000 feet QNH 997 millibars" (self-explanatory)
"EHM123 contact Director 120.4 callsign only" (transfer to the final director; the check-in should be just "EHM123")
...
"EHM123 good evening 19 miles" (the distance from touchdown again)
...
"EHM123 turn right heading 180 degrees, speed 180 knots" (base leg)
"EHM123 descend to altitude 3000 feet, 14 miles" (final descent and check of distance to go)
...
"EHM123 turn right heading 240 degrees report localiser established runway 27L" (the pilot begins a right turn to heading 240 and maintains it until he intercepts the localiser)
...
(reports established)
"EHM123 descend on the ILS speed 160 knots until 4 DME" (maintains 3000 until intercepting glide)
"EHM123 contact Heathrow Tower 118.5"

That's how things work on IVAO and in real life in the UK. Hope I have helped some.

EHM-0641 Rico

  • Guest
\"Intercept LLZ\" question
« Reply #6 on: October 12, 2007, 06:44:02 am »
Iain, not even Gaz could have explained it better :P

Offline EHM-2097 Andrei

  • Administrator
  • Intergalactic!!
  • ***
  • Posts: 1,968
  • Karma: 6
\"Intercept LLZ\" question
« Reply #7 on: October 15, 2007, 07:59:17 am »
Hi all,

First of all, thanks for your answers. Then, taking into account these answers, I think it's time to draw some conclusions.

First, I think most of us agree on the right way to intercept the localizer - as a pilot: start manually the turn into the localizer and intercept glideslope from below.

About the ATC instructions, I also red the iCAO 4444 document and it gives a few hints (= rules, in fact :) ) :

Quote
The pilot should be instructed to follow a heading within 30 degrees before LLZ interception AND must be granted at least 1nm of straight flight before intercption. There is no indication of upper limit here.


(Of course, local procedures may override this as I suppose it is the case in the UK according to Iain's detailed example.)

In this case I keep my opinion that "intercept" should be read as "clear to intercept as you approach the LLZ axis" and not as "turn now to intercept".

However, it may well be a reality on IVAO that some pilots may misinterpret (well, I saw one :) ) the instruction so ATC should be prepared for it. As "tactical" preparation I see two measures:

- The angle between last assigned heading and LLZ - the lower it is, the less zigzag turns occur if APP is triggered too early;

- The timing - the later the "intercept" instruction is isued, the lesser the effect of any misinterpretation is. Personally I will impose myself a 5nm limit (before intercepting).

HOWEVER... the main issue here remains the phraseology, as this is what causes or dissipates misinterpretations.

I agree with Sotiris that little nuances can do much (good and bad). In this directon I think that "cleared to intercept" is better than "intercept", because it does not suggests immediate action to be taken (like pressing the unfortunate APP button).

However, "report established" alone is not sufficient in my opinion because this does not clear the pilot to turn when reaching LLZ axis.

By the way, "report established localizer" is also subject to different interpretations. I've heard pilots reporting as soon as they pressed "APP" while others did not report until the heading was completely stabilized. And of course I don't dare skip the "localizer" from the "report established" sentence because in this case some pilots may only report when established on glideslope too.

(I must add to this that official documents like the 4444 above mentioned are not very specific about this topic - the exact meaning of "established").

See you online
Andrei
Andrei Vatasescu // EHM-2097


 

anything