But I have another question about departure procedures. When selecting one occasionally altitudes will appear, and as we all know VNAV doesn’t work for climbing. My question is are these altitudes in the departure procedures there to guide the climb of the aircraft until cruise, if not then why are they there?
Yes. (However these do sometimes get cancelled by ATC in real life, depending on traffic levels or whether or not direct-to clearances are received that effectively mean skipping part of the SID.)
There are in fact several types of altitude constraint:
Minimum prescribed altitudes
Maximum prescribed altitudes
Specific altitude requirements (i.e. you have to cross x waypoint at y ft)
Others that give a range (e.g. between 5000 and 8000 inclusive)
All altitude constraints, however, are represented in IF as the third category - it’s a good idea to double check with charts to find out which of those they actually are.
I’ve always took it as working in conjunction with the STARS altitudes. So your restricted so you stay below or above aircraft on arrivals coming in from the way you are going out.
Like for airports around EGLL. You stay at 6000ft until out of the vicinity for examples.
So the listed altitudes are overall an idea of the altitudes in which the plane should be around such as SPOON being below 15,000ft and ROVER being above 12,000ft so when flying in between those two points that is around the range in altitude you should attempt to be at?
In theory yes. However the actual altitude at each waypoint will be dependent on your climb profile and climb rate (which will differ between aircraft and at different weights.)
So it’s just a general idea of how the climbs should look. But a lighter aircraft will obviously be able to climb quicker than a heavier one. My climb out of RJTT to KJFK with a very heavy load was much lower anywhere from 1,400 to 2,200 v/s. Which is typically lower than I would with a shorter flight due to weight.