Go Back  PPRuNe Forums > Flight Deck Forums > Tech Log
Reload this Page >

747-4/8 "NG FMC" - VNAV ALT not changing to VNAV PATH automatically on approach

Wikiposts
Search

Notices
Tech Log The very best in practical technical discussion on the web

747-4/8 "NG FMC" - VNAV ALT not changing to VNAV PATH automatically on approach

Thread Tools
 
Search this Thread
 
Old 4th July 2024 | 09:49
  #1 (permalink)  
Thread Starter
10 Anniversary
 
Joined: Mar 2011
Posts: 195
Likes: 4
From: Earth
747-4/8 "NG FMC" - VNAV ALT not changing to VNAV PATH automatically on approach

Aircraft in question is the B-747-400 and 747-8 NG FMC with blockpoint 4.0 software.

When when descending in VNAV SPD and below the VNAV path, the vertical flight mode annunciation changes to VNAV ALT once capturing the MCP altitude. When cleared for the approach, on a non-ILS or a published transition route to an ILS, typically the pilots will set either minimums or final approach fix altitude in the MCP altitude window depending on the type of approach. When on approach logic (flaps out of up, first approach waypoint sequenced, or close to the airoprt) and in VNAV ALT, most of the time, the FMA will automatically changet to VNAV PATH and begin a descent toward the next altitude constraint in the FMC or end of descent point, automatically as the VPI/VNAV path intersects the aircraft's altitude from above.

My question is: Why does VNAV ALT sometimes automatically change to VNAV PATH and resume descent when the the Vertical Path indicator crosses the airplanes altitude from above, but not always? Why does it sometimes remain in VNAV ALT and require a pilot to press the "altitude intervene" switch on the MCP to follow the path down? I realize you can press altitude intervene early and get VNAV path while level and below path (VPI), however I would just like to know why the FMC will automatically do this sometimes, and others not. I could not find this scenario mention in the FCOM Vol II; the scenario of VNAV ALT automatically changing to VNAV PATH on approach isn't specifically addressed that I could find.
RandomPerson8008 is offline  
Reply
Old 10th July 2024 | 11:13
  #2 (permalink)  
15 Anniversary
 
Joined: May 2006
Aviation Qualifications: ATPL
Posts: 231
Likes: 5
From: Here, there and everywhere
One situation could be reaching an altitude restriction before the waypoint associated with the restriction. Even if the altitude window has a lower altitude, VNAV logic will keep the restriction until getting to the waypoint. Pressing altitude intervent will get rid of the restriction on the active waypoint, and any press afterwards on the subsequent waypoints.


Broomstick Flier is offline  
Reply
Old 18th July 2024 | 22:37
  #3 (permalink)  
Thread Starter
10 Anniversary
 
Joined: Mar 2011
Posts: 195
Likes: 4
From: Earth
Originally Posted by Broomstick Flier
One situation could be reaching an altitude restriction before the waypoint associated with the restriction. Even if the altitude window has a lower altitude, VNAV logic will keep the restriction until getting to the waypoint. Pressing altitude intervent will get rid of the restriction on the active waypoint, and any press afterwards on the subsequent waypoints.
OK, thank you!
RandomPerson8008 is offline  
Reply
Old 19th July 2024 | 00:16
  #4 (permalink)  
50 Countries Visited
5 Anniversary
 
Joined: Sep 2016
Aviation Qualifications: ATPL
Posts: 52
Likes: 5
From: Australia
When on approach logic (flaps out of up, first approach waypoint sequenced, or close to the airoprt) and in VNAV ALT, most of the time, the FMA will automatically changet to VNAV PATH and begin a descent toward the next altitude constraint in the FMC or end of descent point, automatically as the VPI/VNAV path intersects the aircraft's altitude from above.
This statement above doesn't seem correct. Unless a vertical mode is armed, VNAV ALT will not change to another mode. The normal intervention would be to push the Altitude Selector to arm or engage VNAV PTH so that further descent in that mode can be accomplished.
andmiz is offline  
Reply
Old 19th July 2024 | 03:40
  #5 (permalink)  
 
Joined: May 2005
Posts: 203
Likes: 0
From: F370
Andmiz,

That would be true for the legacy FMC. With the -8, and the 747NG FMC the logic was revised so that an RNP/RNAV approach behaved more like an ILS.

In order to leave the VNAV ALT without pressing the MCP, the FMC must know that it is “on approach”. There are various triggers such as flaps being extended and within 20nm, etc but they don’t always work perfectly in the NG FMC. Hence the need to pay attention as you come onto the VNAV path and make sure the aircraft chooses PATH over VNAV ALT.
AtoBsafely is offline  
Reply
Old 20th July 2024 | 01:51
  #6 (permalink)  
50 Countries Visited
5 Anniversary
 
Joined: Sep 2016
Aviation Qualifications: ATPL
Posts: 52
Likes: 5
From: Australia
Originally Posted by AtoBsafely
That would be true for the legacy FMC. With the -8, and the 747NG FMC the logic was revised so that an RNP/RNAV approach behaved more like an ILS.
Sorry, yes, I missed the NG qualifier in the question.
andmiz is offline  
Reply

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are Off



Contact Us - Archive - Advertising - Cookie Policy - Privacy Statement - Terms of Service

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