an example among others : FZQA apch RNAV rwy 07 (DIVKO) - from Navigraph data AIRAC cycle 1204

 

D9.2 LUB altitude constraint 7620 ft

FAF D4.2 LUB altitude constraint 5960 ft

 

how can I preset altitudes that are not exact multiples of 100 ft ?

 

How do they do in the RW ? are 20 ft or 40 ft differences acceptable or not ?

You can set the altitude in 50 ft steps. AFAIK, so correct me if I'm wrong and it's not according to the RW OPS, you set it to the closer value.

 

So let's say if you want to land at 7620 ft, you set it to 7600. If you want to land at 5960, you set it to 5950.

 

That's what I think is the correct way, and that's also the way the NGX automatically sets the landing altitude on the pressurization panel if you don't do it manually. It also makes sense, since you can only go by 50 ft steps. It worked fine for me so far.

These are presumably altitude or above constraints right? IOW these are the minimum altitudes you may fly, rather than the exact altitudes you should hit. In that case just round up to the nearest number you can enter.

I think the Boeing guidance is round down and when crossing is assured set the next constraint.

 

Boeing has to methods and they can be found in the Flight Crew Traing Manual.

 

I set field elevation rounded down when inside the IAF.

an example among others : FZQA apch RNAV rwy 07 (DIVKO) - from Navigraph data AIRAC cycle 1204

 

D9.2 LUB altitude constraint 7620 ft

FAF D4.2 LUB altitude constraint 5960 ft

 

how can I preset altitudes that are not exact multiples of 100 ft ?

 

How do they do in the RW ? are 20 ft or 40 ft differences acceptable or not ?

 

Always round the numbers up to the nearest 50 or 100 value.

7620 = 7650

5960 = 6000

I am assuming that this is an approach procedure.

 

You may round the recommended altitude to the nearest 50FT, but not below the segment MDA.

"You can set the altitude in 50 ft steps"

 

how can I ? altitude range is 0 to 50,000 feet in 100 foot increments

 

is there a way to get 50 ft increments instead ? via the PMDG setup ?

 

thanks

RW, the MCP only has 100' increments.

 

You guys are posting a lot of preferences and personal techniques, but nothing from manuals or SOPs. Check out the FCTM.

For an approach procedure, always set the MCP altitude window to the closest 100 feet above MDA/DA.

 

Example: For a VNAV PTH, and MDA/DA is 420 feet then set MCP altitude window to 500 feet. During the descent to MDA/DA, you’re going to reset the MCP altitude window to the MAP altitude. The airplane will descend to the MDA/DA of 420 feet because it's an altitude restraint on the LEGs page.

 

"FAF D4.2 LUB altitude constraint 5960 ft"

I have never seen a FAF with a altitude constraint like this one? For simplicity, they are rounded off to the nearest 100 feet. I this something found in Europe?

 

 

John Floyd

Typical to round up to the nearest 100. It's been that way in all of the heavies and light jets i've flown RW.

I think the Boeing guidance is round down up and when crossing is assured set the next constraint.

 

Well, that's what I get for referring to a manual that has been translated from Englishy to Korean and back to Englishy. At a certain airline that eats a lot of kimchi, they round down. I don't know why they changed it, but I'd be willing to bet it started as a mistranslation.

 

There's a fair bit of variation on this. One airline I worked at would set the cleared altitude in the MCP on the way up, but set hard restricions on the way down. Another allows for user discretion, but allows field elevation (rounded down) for VNAV approaches.

 

In my FCTM, it's on page 1.39.

"FAF D4.2 LUB altitude constraint 5960 ft"

 

"I have never seen a FAF with a altitude constraint like this one? For simplicity, they are rounded off to the nearest 100 feet. I this something found in Europe"

 

see chart below FZQA Lumbumbashi Intl Democratic Republic of Congo

Jean-Louis,

This is not used for aeronautical navigation.

Does anyone have an actual FZQA RWY 07 RNAV appraoch plate used for aeronautical navigation they can post?

The MDA for this approach is 4750, when you add your 50' to it to get the DDA of 4800'

 

When doing a NPA you must add 50 feet to the MDA and then this is treated as a "derived decision alititude" all non precision approaches must be flown as CANPA ie no level segment, the missed approach must be commenced at the DDA.

 

50 feet is added to the MDA as you may never go below the MDA. A DA on an ILS you may descend through momenterially when doing a go around - this is calculated in the design criteria for the procedure.

 

With an MDA no such allowance is made

Sorry, with the 50ft steps I was refering to the LANDING ALT not to the CRUISE.

 

I just posted the way I do it and the way the NGX is automatically setting it to the nearest value. It sometimes sets it DOWN as well if I remember correctly, I'm not sure though, as I stated before, these are just personal techniques and the way I've experienced it, but to be safe you round it up that's what others say using manuals or procedures as reference I believe.