Now, here's my problem.A flight from LOWW to EDDM in a A318, FL260.LOWW GISPO UL856 SBG UL173 AMDID EDDMI am guided to FL260. Nice flight so far. Then I am told to descend to FL240, shortly afterwards to FL190.Then I am told "to descend to FL110 with a speed of 250" Controller needs me at this FL with this speed in 40 miles.I descend with -2500 and a target speed of 240, and I level off and hold this speed app. 10 miles before ADID.So I am crossing ADID at FL110, speed 240.At that moment, the controller contacts me that I haven't met my crossing restrictions and issues a vector. Huh? I did as he told and I didn't meet the restrictions?If I follow his vector, I can fly this course for hours and never hear of him again.This happens at quite some airports for me.So my question is: What am I missing?Please enlighten me.

Quite why you are descending at 2,500fpm seems a little excessive when you can easily get down to your target altitude within 22DME at 1,500fpm!! In a real situation ATC would not normally allow you to descend so fast. The only exceptions I am familiar with are LIMF and LIPZ where one has just crossed a mountain range and therefore needs a quick descent with speed brakes.I suggest you fly a proper descent profile first and then see what happens.vololiberista

Do you really think that it is because of the fast descent? Because It happened (for example at ELLX) with normal descent rates as well. I did the fast descent not to miss the restrictions...

Now, here's my problem.A flight from LOWW to EDDM in a A318, FL260.LOWW GISPO UL856 SBG UL173 AMDID EDDMI am guided to FL260. Nice flight so far. Then I am told to descend to FL240, shortly afterwards to FL190.Then I am told "to descend to FL110 with a speed of 250" Controller needs me at this FL with this speed in 40 miles.I descend with -2500 and a target speed of 240, and I level off and hold this speed app. 10 miles before ADID.So I am crossing ADID at FL110, speed 240.At that moment, the controller contacts me that I haven't met my crossing restrictions and issues a vector. Huh? I did as he told and I didn't meet the restrictions?If I follow his vector, I can fly this course for hours and never hear of him again.This happens at quite some airports for me.So my question is: What am I missing?Please enlighten me.

Darem,Although your descent rate is higher than normal it isn't the reason you missed your crossing restriction. My guess is that you had your altimeter set to the incorrect pressure. Were you on standard pressure (1013.2hPa) or on local QNH?

Local was 5000feet. I was on standard, because I descended from 19000to 11000 feet.I am really at a loss here...

In the vicinity of EDDM the transition altitude is 5,000 feet in the RC database. You were above this for your commmandeddescent altitude which is why RC commanded a flight level rather than feet for altitude with your crossing restriction at FL 110 stated, not 11,000 feet.For flight level altitudes your barometer needs to be at 29.92 in. or 1013 mb., the standard pressure for flight levels. With the altimeter pressure set to standard then FL x 100 (add two zeros) translates to feet on the altimeter. Some aircraft panels have a switch or button to do this on their panel. Some can switch between mb and in. as well for your reference.You can use this "clue" of whether to set your altimeter to standard or local pressure with RC's reference to feet or flight levels. In addition as you descend or climb through a transition altitude you'll hear a copilot voice state "altimeter check" as a reminder for you to adjust it if you have not already done so.If your altimeter was not set for standard pressure then RC saw you at the wrong altitude, probably above, and will keep issuing delay vectors until you descend to the correct FL altitude.There is also a bug in FSX and FS9. It has hard coded a global transition altitude of 18,000 feet as in the US. FS does not know local TAs and TLs. If you use the "B" key in FS to set altimeter pressure it will set it incorrectly where the TA is not 18,000 feet. If you wish to know the transition altitude before you start your flight, put up the Controller page in RC.Check out the section on transition levels and transition altitudes in the RC manual, version 43.If you followed all of these settings then I would make sure you have the minimum update of FSUIPC version from here as RC uses FSUIPC to get your altitude:http://www.schiratti.com/dowson.htmlIf you can reproduce this error you can alt-tab to RC and click debug to start a log and then alt-tab back to FS. After you quit RC zip up the log file in the RC folder and attach it to an e-mail as explained in the thread at the forum top here.

Thank you, that was most helpful. I will experiment with these things.