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

RNAV and constant climb/descent

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

RNAV and constant climb/descent

Thread Tools
 
Search this Thread
 
Old 16th Feb 2011, 15:38
  #1 (permalink)  
Thread Starter
 
Join Date: May 2008
Location: UK
Posts: 200
Likes: 0
Received 0 Likes on 0 Posts
RNAV and constant climb/descent

Hi,

I'm struggling to find any information regarding how an FMC/FMS/FMGC (I think that is most types covered ) handles continuous climbs/descents.

The only time I've seen this is on RNAV departures/arrivals, and I wondered whether this particular way of flying was specific to RNAV procedures, and whether the flight management system can be persuaded to fly this way with pilot-entered waypoints (for example)?

e.g. suppose the aircraft is approaching a waypoint with the constraint CROSSING AT 8000 ft, yet the aircraft has the performance to be at 8000 ft 5 nm before the waypoint. On an RNAV departure I have seen the aircraft fly a path that will ensure it passes the waypoint at 8000 ft, but at a shallower climb angle than it is otherwise capable of. Is this standard for any type of waypoint, or only RNAV procedures?

ECAM Actions.

Last edited by ECAM_Actions; 16th Feb 2011 at 16:01.
ECAM_Actions is offline  
Old 17th Feb 2011, 09:15
  #2 (permalink)  
 
Join Date: Feb 2011
Location: Thule
Posts: 33
Likes: 0
Received 0 Likes on 0 Posts
RNAV contant climb v. alt constraint

It, the FMS, does not matter nor does it care whether or not you shallow climb to waypoint or climb and then level off due to a constraint.

If you shallow climb to a constraint as part of an RNAV procedure and you have experienced climbing to waypoints in a hard climb then levelling off at the waypoint, to continue climb after the waypoint, that is probably because your waypoints were close together like in a SID.
Upper Air is offline  
Old 18th Feb 2011, 09:21
  #3 (permalink)  
 
Join Date: Feb 2011
Location: Thule
Posts: 33
Likes: 0
Received 0 Likes on 0 Posts
As you know you cannot/should not build waypoint into a datbased STAR or SIS or DP If, you have a string of wpt as a . . . transition say then the aircraft will descend to the next constraint say: 4,000/Nicky - you will have a lower altitude set say 3,000 alt, so the aircraft will level out at 4,000, fly past the waypoint, then continue descent to the next constraint, if any, and so on all the way down to your selected altitude.

Same for the climb, the aircraft will be at your waypoint at the desired altitude when you have alt constraint on it. You can modify this by entering AT altitude, NOT ABOVE altitude or NOT BELOW altitude, which you would plug into your FMS, prior to departure - or it would already be in there as part of the Descent/Climb/STAR/SID/WHATEVER.

If you are receiving ATC Radar giving you alts (up or down - Dep or App) then you would naturally, clear the constraints, or disc AP or just clean up the box and leave in the approach.
Upper Air is offline  

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 © 2024 MH Sub I, LLC dba Internet Brands. All rights reserved. Use of this site indicates your consent to the Terms of Use.