I have been using RC for a while, flying with the PMDG737NGX. But suddenly I have started to miss my crossing restrictions. I don't know why. I am not doing anything different from before. I am paying attention to the restriction given, I am getting down in time and I am at 250 knots at most, I am straight and level. Still I am missing the crossing. Why? I have tried to get down really early and slow down so that I meet the restrictions allready 50-60 miles out, but I still miss it. I just don't understand what I am doing wrong. It takes away the fun. I just turn off RC (cancel IFR) when I am told that I missed because I don't want to fly outbound when I'm doing my job.

 

It's so wierd, because I haven't changed any procedures or settings and suddenly I just misses it all the time. Is there anyone else with a similar problem?

Hi Vulcan,

 

Did you double check your plane type in RC4 ? Jet - Turboprop - Prop ??? I think you have to have a substantial VS to make those restrictions - I usually use 1800FPM or so...

 

Regards,

Scott

Since your flying the NGX I create a fix 40-42 miles from the destination waypoint and place it in my legs page. This will also put a range ring on the ND so you know when to be at the restriction by rc4. I then put 240/11000 or 260/12000 at the fix point on the leg page I created. This way vnav will get me down in time winds cooperating of course.

 

Hope this makes sense and helps.

The most common reference regarding crossing restriction problems is altimeter settings:

1. Using the 'B' key in FS to set the altimeter is basically only good for the FAA areas when it comes to the transition altitude. FS has it hard coded to 18,000 feet globally whereas RC uses the local transition level in the local approach area. You can see this in the controller tab for each airport. If RC gives you an altitude in feet use local altimeter pressure (QNH). If RC gives you an altitude as a flight level use standard altimeter pressure of 29.92 or 1013 mb.

 

2. I have the 757NF FS9 version from PMDG. Be sure you the BARO switch works in setting standard or dialed in local pressure. The dialed in pressure is always displayed on the PDF but when in standard there is an indication for this. Also, when in cruise and the altimeter is in standard mode I predial the altimeter setting to the expected QNH from the METAR in the destination area. That way it should be close with less manipulation to what the RC controller will state on your descent below the transition altitude.

 

3. If you are using ASE or its later variants in FSX there can be some discrepancies with using global weather mode required for DWC. First, current versions of fsuipc4 detect when global mode is being used and deliver the data from the expected METAR direct from ASE as opposed to reading it from the current destination pressure which can vary on the way in from what it will be when you get there. Be sure all service packs are installed for AS and fsuipc4 is current.

 

You might do the shift-z thing in FS to read the current pressure for the local altimeter. Regardless of the transition altitude where you are below 18,000 feet FS will show the local surface pressure where your aircraft is located. Compare that to what the controller delivers if the crossing restriction is below the transition level.

Thanks for the answers guys!

 

I fly in Europe, where the crossing is on FL, not altitude. I do not mess with the B-key. I always set the pressure with the wheel in the cockpit, and I am on STD when I fly on FL120 or FL110.

 

Yesterday I took flights with my 737-600 and 737-700 and I failed to meet the crossing three times in a row. The crossings where at EGLL, ESSA and ESMS. But today, I had a flight from ESSA to LOWS with the 737-800 (all are PMDG NGX) and at LOWS I managed to meet the crossing. I am doing the exact same thing every time. It couldn't be so that I meet the restriction with the 738 but not with the 737 or 736, could it?

 

I am doing that FIX-thing too to get a visual cue, and to be on the safe side I often put up one FIX at 40 and one at 50. Then I try to get down between them so that I am fully level when I reach 40, but as I said, that doesn't help.

 

I do use ASE. Can that possibly be the trouble even though I am on standard pressure?

i thought the crossings were in feet not FL

 

and yes, if you don't have the correct pressure when trying to cross at 12000, you're going to miss.

 

make a log, instructions pinned to the top of forum, send me a log of you missing. make sure you click debug before you load your .pln

 

jd

i thought the crossings were in feet not FL

Transition Altitudes in Europe vary widely. It's 3000ft at Amsterdam, 5000ft at Manchester. Only at airports at altitude will it be significantly higher. Madrid being one such example where the TA is 13,000ft. I can't think of any that come close to 18,000ft.

 

So it's quite usual to be cleared down to FL110 or FL120 rather than 11,000 or 12,000ft.

Yes, in Europe the TA is mostly in FL, so that is why I keep my altimeter at STD. Yesterday it worked fine at LOWS, but on my return flight to ESSA I was told that i missed the crossing again. I was level, I was on STD pressure, I was at FL120 (which I was assigned), I was a 260knots (not that that should matter with the higher restriction), and still I missed it. I still love RC and I am going to continue to use it, but this issue steals some fun away. Only me with this problem?

Vulkan,

 

Check the Altitude setting in Options / Settings. My guess is that you've set it to a different value and RC could then becomes very picky about your altitude. The default (from memory) is 200. What value do you have?

 

LATER: Click General on the Options area and in Deviations the default Altitude value is 300ft. I suspect that is different on yours.

Vulkan,

 

Check the Altitude setting in Options / Settings. My guess is that you've set it to a different value and RC could then becomes very picky about your altitude. The default (from memory) is 200. What value do you have?

 

LATER: Click General on the Options area and in Deviations the default Altitude value is 300ft. I suspect that is different on yours.

 

My deviation is 2000. I increased it from the default to make it easier to meet the restrictions. Was that a bad idea, am I thinking wrong about that?

 

The other setting that you are talking about, where do I find that?

 

 

My deviation is 2000. I increased it from the default to make it easier to meet the restrictions. Was that a bad idea, am I thinking wrong about that?

 

The other setting that you are talking about, where do I find that?

 

They are the same setting but my first para was from memory so forget that.

 

2000ft will certainly cause something strange to happen. I've never changed the default of 300 so change to that and see if it solves the problem. I'm guessing it will. I appreciate the value of 2000 should mean you can be between FL100 and FL140 for a FL120 restriction but it may have broken something in the code. If you create a log and recreate the scenario send the log to JD and he will tell you exactly what is wrong.

They are the same setting but my first para was from memory so forget that.

 

2000ft will certainly cause something strange to happen. I've never changed the default of 300 so change to that and see if it solves the problem. I'm guessing it will. I appreciate the value of 2000 should mean you can be between FL100 and FL140 for a FL120 restriction but it may have broken something in the code. If you create a log and recreate the scenario send the log to JD and he will tell you exactly what is wrong.

 

Hmm ok. Maybe it was stupid of me to try and outsmart the computer.. I will try to reset it to 300 and see if that helps. What are the other defaults? Mine are set at heading deviation of 30 and knots deviation of 50...

According to the manual they are:-

 

Heading 15 deg

Altitude 300ft

Speed 15kts.

Ok. Thanks, I will try with that settings. Hopefully it will work.

I have tested with the settings that you suggested and it works like a charm! Thanks!