PPRuNe Forums

PPRuNe Forums (https://www.pprune.org/)
-   Tech Log (https://www.pprune.org/tech-log-15/)
-   -   FMC "INTC CRS" question (https://www.pprune.org/tech-log/489412-fmc-intc-crs-question.html)

adri737 1st Jul 2012 18:21

FMC "INTC CRS" question
 
Hello:),

I've a question concerning the "INTC CRS" feature :

When we are under radar vector for approach, I usually ask to set the FAF of the runway on top of the leg page and select the localizer course on the LSK 6R (INTC CRS). What does the VNAV deviation scale indicates when we perform this?Is it the deviation between the current altitude and the FAF altitude?Or the deviation from the altitude we should have when we intercept the LNAV route with the actual heading?

Thank you very much for your imputs:ok:

ImbracableCrunk 1st Jul 2012 19:06

There was a thread on this a couple years back. I *think* it was "decided" that the FMC transposes you laterally onto the FAC and does not include any offset for a base or downwind. So, if you were on a base 5 miles from the threshold, 3 miles from the centerline, it would say you're at 4 miles. (3-4-5 triangle.)

Now I need to look that up again. That doesn't sound right, now that I think about it.

sky-738 2nd Jul 2012 01:14

Crunk,
what I think is it would show 7 miles ,3+4,you know what I mean.

Andrén 2nd Jul 2012 09:10

Never tried this as i don't really need a VNAV Path, but if you're on an intercept course and you extend the centerline. I guess you could just click LNAV, then it will draw a line to the extended centerline and probably give you an accurate path then go back to HDG.

Again i've never actually done this for real.

RAT 5 2nd Jul 2012 14:20

I'd always thought the PROG 1 distance was the nm's from present position on your intercept HDG to capture the magenta line and fly the planned route thereafter. Your altitude relative to the required path to achieve the next alt constraint generates the VNAV deviation.

Noknoipobin 2nd Jul 2012 16:08

I think it calculates from aircraft position to that FAF and then the rest of the flight plan regardless of your aircraft track or heading.you can check it out by setting intercept course to at FAF and you will see the same distance at progress page in different intercept track even your track is from the runway(outbound ).
Another method to check,by selecting the same track to intercept but change your intercept point (may be FAF IF or the others),the distance is changed (on aircraft or simulator ).

ImbracableCrunk 2nd Jul 2012 18:25


Never tried this as i don't really need a VNAV Path, but if you're on an intercept course and you extend the centerline. I guess you could just click LNAV, then it will draw a line to the extended centerline and probably give you an accurate path then go back to HDG.

Again i've never actually done this for real.
That works, I've done it before. VNAV gives a real VTRK with LNAV and an intercept. It's not correct in HDG SEL if you're not on an LNAV direct course to the FAF or some fix along the way. In HDG SEL, it shows higher than LNAV until you get on the FAC.

FlightPathOBN 2nd Jul 2012 19:42

First, since you reference LNAV, and referencing a localizer, what type of approach procedure are you using?


Second, I would ask where you are getting altitude, and location of the FAF for the runway?

adri737 2nd Jul 2012 21:44

Thanks everybody for your explanations so far:ok:


First, since you reference LNAV, and referencing a localizer, what type of approach procedure are you using?
It's an ILS approach


Second, I would ask where you are getting altitude, and location of the FAF for the runway?
Sorry, I meant FAP...

FlightPathOBN 2nd Jul 2012 23:06

Okay, so that clears it up a bit...
The difficulty here is that the ac, using this method, you will intercept the ILS beam, perhaps 'at or above', then the ac will drop, to re-acquire the beam, especially when using baro-vnav to ILS intercept...

This is all very possible, but is certainly 'outside the box'...

adri737 3rd Jul 2012 17:47


Okay, so that clears it up a bit...
The difficulty here is that the ac, using this method, you will intercept the ILS beam, perhaps 'at or above', then the ac will drop, to re-acquire the beam, especially when using baro-vnav to ILS intercept...
I was just wondering how the FMC calculate the VNAV path when you put the extended centerline (FAP with the intercept course equal to the localizer course) when you are under radar vector for an ILS approach.

BOAC 3rd Jul 2012 19:17

So complicated, so confusing, and in effect absolutely **** useless :) (since ATC will probably never send you that way) which is why I never used the 'extend the centreline' (luddite!) but always knew where I was and what I height I needed to be. Much simpler. Is it that difficult?

Unfortunately it became the 'darling' 'clever trick to show' for those TC's who presumably did not really know where they were and every F/O came out of the sausage machine programmed to push the buttons and then not really know what to do with it.

The very best in FMC vertical guidance was with an un-executed (dotted white on 737) leg to a point, but that sadly fell out of favour with de management and became a no-no..

Long live range to waypoint and the three times table. Why complicate it?

adri737 3rd Jul 2012 19:31

Thank you OK645 for your good explanation!:ok:

As to your specific question (assuming you're speaking NG here)...
I'm speaking about the classic but I suppose it's the same as in the NG?

And how is the profile computed if we don't put the VNAV cruise altitude on the FMC? Imagine we "just" use LVL CHG and not VNAV...

Let's say we are on a 8Nm downwind (HDG SEL and ALT HOLD and the FAP is on top of the leg page with the correct intercept course) and the VNAV deviation indicates 2000ft high ... How is this value calculated?

adri737 3rd Jul 2012 19:39


So complicated, so confusing, and in effect absolutely **** useless http://images.ibsrv.net/ibsrv/res/sr...lies/smile.gif (since ATC will probably never send you that way) which is why I never used the 'extend the centreline' (luddite!) but always knew where I was and what I height I needed to be. Much simpler. Is it that difficult?

Unfortunately it became the 'darling' 'clever trick to show' for those TC's who presumably did not really know where they were and every F/O came out of the sausage machine programmed to push the buttons and then not really know what to do with it.

The very best in FMC vertical guidance was with an un-executed (dotted white on 737) leg to a point, but that sadly fell out of favour with de management and became a no-no..

Long live range to waypoint and the three times table. Why complicate it?
I was just wondering how the VNAV profile was computed when do the "extended centerline"on the FMC... just out of curiosity:ok:

BOAC 3rd Jul 2012 20:18

It does not need a 'VNAV' cruise entry - it uses current altitude. I was told it computed the 'direct to' vertical profile with no allowance for heading or turn radius, but that could be wrong - as I said, I never used it. If that is the case, the only time it would be meaningful would be when you were on that track, so I would wager that '2000ft high' would be just about perfect..That is why the 'un-executed' route was always more accurate as it 'drew' the turn.

BOAC 4th Jul 2012 07:47


BOAC, he's just asking how it works, not whether or not it's a 'clever' idea to use it.
- I doubt you have noticed inside your world, but I have actually been doing that too:ugh:


All times are GMT. The time now is 20:47.


Copyright © 2024 MH Sub I, LLC dba Internet Brands. All rights reserved. Use of this site indicates your consent to the Terms of Use.