LNAV/VNAV
Thread Starter
Join Date: May 2010
Location: EARTH
Posts: 7
Likes: 0
Received 0 Likes
on
0 Posts
LNAV/VNAV
Example is EDDF RNAV(GPS) Z Rwy 25C. If the temp is bellow -15 C then baro VNAV is not authorised. So you use LNAV minima. If you have temp -18 C and do the temperature corrections according with the FCOM and enter the corrected altitudes in the FMS. During the approach can you use LNAV/VNAV? ( with the corrected altitudes and descend to LNAV minima)? Many people say that you have to do it LNAV and FPA or V/S because baro LNAV/VNAV minima are not authorised. My opinion is that you can use LNAV/VNAV during the approach with the corrected altitudes. Thank you in advance
Join Date: Jan 2006
Location: Between a rock and a hard place
Posts: 1,267
Likes: 0
Received 0 Likes
on
0 Posts
You can do it in any vertical speed mode as you like as long as the minimum altitudes are adhered to. Your company may have some SOP/restrictions but we do it in LNAV/VNAV yes.
If you temp comp, yes LNAV/VNAV because the limits are there to "protect" the aircraft from descending outside the altitude limits. By compensating, you are flying true altitudes.
Join Date: Nov 2005
Location: Zulu Time Zone
Posts: 730
Likes: 0
Received 0 Likes
on
0 Posts
toseg, I believe what you are saying is correct. If you have an uncompensated baro VNAV system you cannot use the LNAV/VNAV DA outside the temperature limits. You can still use the baro VNAV for vertical guidance but you have to fly to the LNAV MDA (and apply temperature correction to each segment altitude including MDA). If you have compensated baro VNAV you can use the LNAV/VNAV DA but you must still apply temperature correction to each altitude including DA. Ref AIM 5-4-5 and AC 90-105A App B.4.2
Join Date: Jun 2006
Location: CASEY STATION
Posts: 191
Likes: 0
Received 0 Likes
on
0 Posts
The FCOM states that the approach procedure cannot be modified from FAF to MAPt, so adjusting altitudes to compensate the final segment for temp is not possible. Our company policy describes this as the reason LNAV/VNAV minima cannot be used when below the minimum temp. FCOM also says a vertical selected mode is available and consequently the minima will change to the published LNAV only minima. ( That's our company guidance anyway )
Only half a speed-brake
GF: the Airbus kit does not have TEMP correction feature.
The only way to do it is to manually modify the altitudes over waypoints which:
a) is rejected by the FMS as 3° profile is the basis of construction
b) is explicitly forbidden by VNAV OPS approval.
So, no (in our case). If temps are below what's charted then no (uncompensated) VNAV. Manual correction is not an approved TEMP compensation standard and would invalidate the coding.
The only way to do it is to manually modify the altitudes over waypoints which:
a) is rejected by the FMS as 3° profile is the basis of construction
b) is explicitly forbidden by VNAV OPS approval.
So, no (in our case). If temps are below what's charted then no (uncompensated) VNAV. Manual correction is not an approved TEMP compensation standard and would invalidate the coding.
It should be borne in mind that the methodology used for obstacle protection for an LNAV/VNAV approach is quite different to that for an LNAV procedure. The VNAV functionality in the aircraft is not directly related to the procedure design.
Join Date: Aug 2013
Location: PA
Age: 59
Posts: 30
Likes: 0
Received 0 Likes
on
0 Posts
The chart is very specific Baro-VNAV operations N/A below -15C...non-comp or comp N/A
Pretty amazing the understanding of flight procedures exhibited here on PPRUNE....Care to revise?
Thank you.
My opinion is that you can use LNAV/VNAV during the approach with the corrected altitudes.
You can do it in any vertical speed mode as you like as long as the minimum altitudes are adhered to. Your company may have some SOP/restrictions but we do it in LNAV/VNAV yes.
If you temp comp, yes LNAV/VNAV because the limits are there to "protect" the aircraft from descending outside the altitude limits. By compensating, you are flying true altitudes.
So, no (in our case). If temps are below what's charted then no (uncompensated) VNAV. Manual correction is not an approved TEMP compensation standard and would invalidate the coding.
The FCOM states that the approach procedure cannot be modified from FAF to MAPt, so adjusting altitudes to compensate the final segment for temp is not possible
Last edited by underfire; 23rd Mar 2017 at 03:49.
Join Date: Mar 1999
Posts: 363
Likes: 0
Received 0 Likes
on
0 Posts
The FCOM states that the approach procedure cannot be modified from FAF to MAPt, so adjusting altitudes to compensate the final segment for temp is not possible. Our company policy describes this as the reason LNAV/VNAV minima cannot be used when below the minimum temp. FCOM also says a vertical selected mode is available and consequently the minima will change to the published LNAV only minima. ( That's our company guidance anyway )
Join Date: Oct 2004
Location: N5552.0W00419.0ish
Posts: 87
Likes: 0
Received 0 Likes
on
0 Posts
Now, I thought/understood this was slightly different.
The LNAV part of the procedure remains the same.
The VNAV part is where the anomalies arise.
You may use VNAV as your descent profile/method, with any altitude/temperature corrections up to, but not inside the FAF.
Within the published temperature (o/p gives -15c as the lower temperature limit) constraint of the procedure, then VNAV minima apply; LNAV/VNAV.
once outside of the published temperature constraint, the LNAV only minima apply, which are likely higher. This does not mean that VNAV cannot be used; it simply means that your minima are higher.
The LNAV part of the procedure remains the same.
The VNAV part is where the anomalies arise.
You may use VNAV as your descent profile/method, with any altitude/temperature corrections up to, but not inside the FAF.
Within the published temperature (o/p gives -15c as the lower temperature limit) constraint of the procedure, then VNAV minima apply; LNAV/VNAV.
once outside of the published temperature constraint, the LNAV only minima apply, which are likely higher. This does not mean that VNAV cannot be used; it simply means that your minima are higher.
Thread Starter
Join Date: May 2010
Location: EARTH
Posts: 7
Likes: 0
Received 0 Likes
on
0 Posts
First i would like to thank you all very much for your answers . At FCTM is written the following : "Boeing airplanes have uncompensated Baro-VNAV systems and are prohibited from using LNAV/VNAV minima on approach charts when operating outside of published temperature restriction limits. However, if cold temperature altitude corrections are applied as described in the Cold Temperature Operations Supplementary Procedures chapter of the FCOM, descent to the corrected LNAV (MDA) minima is allowed." It says for minima not for VNAV mode.
Is mentioning to descent to LNAV minima but does not clarify if you can use VNAV mode. At the part C of my company, if you are above -15 C you correct the FAF altitude and the DA only by 10% .Not all the altitudes between. Bellow -15 C you correct all the altitudes and the MDA from the classic table. In the FMS you don't insert new points. Just correct the altitude of the existed ones in the FMS.
Is mentioning to descent to LNAV minima but does not clarify if you can use VNAV mode. At the part C of my company, if you are above -15 C you correct the FAF altitude and the DA only by 10% .Not all the altitudes between. Bellow -15 C you correct all the altitudes and the MDA from the classic table. In the FMS you don't insert new points. Just correct the altitude of the existed ones in the FMS.
Join Date: May 2003
Posts: 409
Likes: 0
Received 0 Likes
on
0 Posts
Like Galaxy Flyer says, if you can enter the temperature in the FMS, then it will compensate for the altitudes in the approach procedure. The IF, and FAF will then have increased minimum altitudes, and then you must increase your LNAV or LNAV/VNAV minimums. Then compensate for the IAF altitude (talk to ATC if necessary). For us, ATC always says to cross the IAF "at or above" 3500 feet so that's not a problem.
With a cold temperature input to the FMS, the FMS adjusts the VNAV angle up a bit to compensate for the reduced altitude clearances that would exits if you used the somewhat lower altitudes that the altimeter reads on cold days.
If the approach says NA, then it's NA, though I can only surmise that is old school before temp compensation was allowed by the designers.
aTerpster will probably chime in.
With a cold temperature input to the FMS, the FMS adjusts the VNAV angle up a bit to compensate for the reduced altitude clearances that would exits if you used the somewhat lower altitudes that the altimeter reads on cold days.
If the approach says NA, then it's NA, though I can only surmise that is old school before temp compensation was allowed by the designers.
aTerpster will probably chime in.
Thread Starter
Join Date: May 2010
Location: EARTH
Posts: 7
Likes: 0
Received 0 Likes
on
0 Posts
The next approach at the same airport is RNAV (GPS) Y Rwy 25C. Does not mention any temperature restriction and has LNAV minima. In this one why you can use the VNAV mode? With the same logic you shouldn't. You do only the altitude corrections to ensure the 3 deg. descend angle and use LNAV/VNAV. Any objection?
*** completely re - edited having reread your question again and having read FDs excellent post below: There is no minimum temp on the chart you mention because it is not a "VNAV procedure" , IMHO the chart/minima is drawn on the basis of you using LNAV and VS or FPA having applied the appropriate corrections i.e. It is what FD describes as a 2D approach. Can you substitute VNAV? What does your ops manual say (we can in certain circumstances)?
On a more general point if no minimum temp is published for a "VNAV procedure" our ops manual says, to paraphrase "In the case of an RNAV approach where no minimum temperature is published....... pilots should assume a minimum temperature of ISA -25 for the use...of VNAV."
FWIW We have uncompensated baro VNAV and are not allowed to alter RNAV altitudes in the FMC.
On a more general point if no minimum temp is published for a "VNAV procedure" our ops manual says, to paraphrase "In the case of an RNAV approach where no minimum temperature is published....... pilots should assume a minimum temperature of ISA -25 for the use...of VNAV."
FWIW We have uncompensated baro VNAV and are not allowed to alter RNAV altitudes in the FMC.
Last edited by wiggy; 23rd Mar 2017 at 10:29.
Only half a speed-brake
toseq: there seems to be still a little confusion over the terminology because VNAV is used for two independent things. Let me try to split them so we can be certain of reading the same page. Most likely I'd be preaching to the converted, reader's patience is appreciated.
a) The LNAV+VNAV sub-version of RNP APCH. A stand-alone type of instrument approach procedure. Different from the others in its own manner, similar as with CAT II being different from a simple CAT I approach. Procedures for RNP LNAV+VNAV which is a 3D approach type (=with vertical guidance) require specific design, need to be published as such and operator must be authorized by their CAA to fly them, with all the bells and whistles normally associated such as training for the specifics of the operation.
Maybe it is possible to call this "3D APCH (LNAV+VNAV)" for the purpose of this conversation.
Note 1: The a) above is somewhat obscured by the fact that the printed chart is normally combined for "3D APCH (LNAV+VNAV) and "2D APCH(LNAV only)", the only visible difference being the two boxes of different minima. But they are fundamentally different, just like ILS and LOC approaches that also commonly share one page.
b) The VNAV mode of autoflight vertical guidance. If the on-board system is capable of generating a vertical profile, a mathematical glide path for the final approach, the Flight Director may be set up to follow that guidance and provide steering commands for AP / human at controls.
I'd call this VERTICAL GUIDANCE OF FMS/FD FOR FINAL APPROACH SEGMENT but it is such a mouthful. Settle for VNAV (FD mode)?
Note: This b) is a widespread technology, commonly used to fly NDB and VOR approaches for decades. We let the machine calculate the profile and follow it, whilst checking from the underlying decisive NAVAID approach chart that the altitude / distance is reasonable. Just let the clever box sort out the guesswork of target and desired vertical speed values.
These points should be visible now:
If I read the thread and your questions correctly:
Topic 1 (closed): Can you perform a 3D APCH (VNAV+LNAV) approach outside temp envelope? ->> NO.
Topic 2 (your last posted question): Please re-phrase.
a) The LNAV+VNAV sub-version of RNP APCH. A stand-alone type of instrument approach procedure. Different from the others in its own manner, similar as with CAT II being different from a simple CAT I approach. Procedures for RNP LNAV+VNAV which is a 3D approach type (=with vertical guidance) require specific design, need to be published as such and operator must be authorized by their CAA to fly them, with all the bells and whistles normally associated such as training for the specifics of the operation.
Maybe it is possible to call this "3D APCH (LNAV+VNAV)" for the purpose of this conversation.
Note 1: The a) above is somewhat obscured by the fact that the printed chart is normally combined for "3D APCH (LNAV+VNAV) and "2D APCH(LNAV only)", the only visible difference being the two boxes of different minima. But they are fundamentally different, just like ILS and LOC approaches that also commonly share one page.
b) The VNAV mode of autoflight vertical guidance. If the on-board system is capable of generating a vertical profile, a mathematical glide path for the final approach, the Flight Director may be set up to follow that guidance and provide steering commands for AP / human at controls.
I'd call this VERTICAL GUIDANCE OF FMS/FD FOR FINAL APPROACH SEGMENT but it is such a mouthful. Settle for VNAV (FD mode)?
Note: This b) is a widespread technology, commonly used to fly NDB and VOR approaches for decades. We let the machine calculate the profile and follow it, whilst checking from the underlying decisive NAVAID approach chart that the altitude / distance is reasonable. Just let the clever box sort out the guesswork of target and desired vertical speed values.
These points should be visible now:
- For 3D APCH (LNAV+VNAV) the availability and use of VNAV (FD mode) is a technical pre-requisite. Many other rules apply as well.
- A 3D APCH (LNAV+VNAV) may only be flown within the published temperature envelope which actually is an integral and critical part of the procedure's design. In certain cases, only if temperature compensation feature is embedded into the internal logic of VNAV (FD mode), it may be permissible fly 3D APCH (VNAV+LNAV) below the procedure's LO TEMP limit. Or maybe not, rules do vary.
- There is no temperature envelope for 2D APCH (LNAV only), similar to VOR APCH. But cold temp corrections, the ordinary variety with ground OAT <= 0 should be applied to all minimum altitudes.
- It is entirely possible and actually desirable to fly 2D APCH (LNAV only) using the VNAV (FD mode) feature.
If I read the thread and your questions correctly:
Topic 1 (closed): Can you perform a 3D APCH (VNAV+LNAV) approach outside temp envelope? ->> NO.
Topic 2 (your last posted question): Please re-phrase.
Last edited by FlightDetent; 23rd Mar 2017 at 10:16.
Join Date: Jan 2000
Location: FL410
Posts: 860
Likes: 0
Received 0 Likes
on
0 Posts
To add to confusion, it depends on software logic loaded into FMS as well...
VNAV can be activated/loaded in several methods, depending on which it will fly (e.g. geometric is what is loaded into our FMS).
Geometric will allow VNAV to be used to fly a vertical profile as long as corrections are made.
Note: though VNAV can be flow their minima cannot be used
VNAV can be activated/loaded in several methods, depending on which it will fly (e.g. geometric is what is loaded into our FMS).
Geometric will allow VNAV to be used to fly a vertical profile as long as corrections are made.
Note: though VNAV can be flow their minima cannot be used
Join Date: Nov 2005
Location: Zulu Time Zone
Posts: 730
Likes: 0
Received 0 Likes
on
0 Posts
toseg
Your company rules seem to be compliant with the regs. In your example, due to the temperature restriction you must use the LNAV minima (and apply temperature correction to it). But as a commercial operator you must make a CDFA so what vertical mode you use depends on your particular system and SOPs.
However, if you had WAAS (or equivalent type of SBAS) you CAN still use the LNAV/VNAV minima (and apply temperature correction to it).
First i would like to thank you all very much for your answers . At FCTM is written the following : "Boeing airplanes have uncompensated Baro-VNAV systems and are prohibited from using LNAV/VNAV minima on approach charts when operating outside of published temperature restriction limits. However, if cold temperature altitude corrections are applied as described in the Cold Temperature Operations Supplementary Procedures chapter of the FCOM, descent to the corrected LNAV (MDA) minima is allowed." It says for minima not for VNAV mode.
Is mentioning to descent to LNAV minima but does not clarify if you can use VNAV mode. At the part C of my company, if you are above -15 C you correct the FAF altitude and the DA only by 10% .Not all the altitudes between. Bellow -15 C you correct all the altitudes and the MDA from the classic table. In the FMS you don't insert new points. Just correct the altitude of the existed ones in the FMS.
Is mentioning to descent to LNAV minima but does not clarify if you can use VNAV mode. At the part C of my company, if you are above -15 C you correct the FAF altitude and the DA only by 10% .Not all the altitudes between. Bellow -15 C you correct all the altitudes and the MDA from the classic table. In the FMS you don't insert new points. Just correct the altitude of the existed ones in the FMS.
However, if you had WAAS (or equivalent type of SBAS) you CAN still use the LNAV/VNAV minima (and apply temperature correction to it).
