|
Post by Lucas on Jul 8, 2014 7:24:53 GMT -5
No - I use only knob on EFIS control panel to set altimeter. Yes - I set local QNH before takeoff and after passing TL when descending to approach.
|
|
|
Post by Dutch Owen on Jul 8, 2014 8:48:34 GMT -5
I got the penalty by not setting the transition altitude in the FMC but pressing the STD button to switch to standard altimeter setting crossing 6500 feet. The NGX didn't actually make the switch until 18,000 feet because that's when it thought it should even though I pressed STD at 6,500 feet on climbout. It colored the "STD" indication yellow to indicate that it hadn't really done it until we crossed 18,000 - when it turned green.
When I rotated the knob to change to 29.92 instead of pressing the STD button, I didn't get any penalty. Also, I didn't get a penalty when I changed the transition altitude in the FMC to 6,500 and pressed the STD button - it went immediately to green instead of the yellow it had been when I didn't make the correction in the FMC.
Dutch
|
|
|
Post by Lucas on Jul 8, 2014 10:51:10 GMT -5
Dutch, forgive me... I misleaded you. Of course, I also set TA in FMC before every flight (whole in my mind ). However, please tell me - did you set TA=6500 on the PERF INIT page in FMC or in NGX SETUP page as a default Transition Altitude? Lucas EDIT: Dutch, why FO tells me about passing TA while descending? I've just finished flight from LSZH to EPWA. TA in LSZH was 7000 (local QNH was 1013, so equal to standard) and about 7200ft FO remembered me about this so I set altimeter to STD by button (I was flying PMDG 777 this time). But, when I descend to EPWA, where Transition Level is FL80, I set altimeter to local QNH=1009 just after passing FL80 (at about 7700ft) but when I was crossing 6500ft FO tells me about passing TA again (?!) - why? Result: penalty again
|
|
|
Post by Lucas on Jul 14, 2014 7:22:21 GMT -5
Dutch,
...could you look at above post?
Thanks. Lucas
|
|
|
Post by Dutch Owen on Jul 14, 2014 10:19:28 GMT -5
The FO tells you about passing TA when ascending or descending. It's possible that there's an issue with the TA database and EPWA is coded as 6500 and not 8000. I'll check into that. But I will be on vacation for the next week, and Travis will be here providing support until I return.
Dutch
|
|
|
Post by Lucas on Jul 15, 2014 2:59:08 GMT -5
Ok Dutch. Thanks. Have a nice holiday!
|
|
|
Post by Travis on Jul 17, 2014 23:19:38 GMT -5
Lucas, You don't get penalties for not setting your altimeter on descent for two reasons. First, there are different ways that local Transition Levels are calculated and in early testing we weren't always able to get METAR data from some of our bush flights. We could get the "local" pressure, but it didn't feel right at the time to have too many variables, so we stuck with setting standard pressure as the only penalty condition. Your friendly FO tells you that you're passing Transition Altitude on decent just because he likes showing off.
|
|
|
Post by Lucas on Jul 21, 2014 8:53:15 GMT -5
Hi Travis! Thanks for reply...so could you give me recipe for this problem? I still get penalties...yesterday, ENZV to EHAM, transition altitude 7000, changed to standard at about 7300 ft (just after FO told me about it) via altimeter knob rotate, not by press STD button (aircraft NGX737). Please.... I don't know what I'm doing wrong
|
|
|
Post by Travis on Jul 21, 2014 11:17:25 GMT -5
About the shortcut: I don't think there is one, but that's realistic. You also don't have a shortcut for setting the transponder to 7700, so in my eyes that's one of the disadvantages of not having a copilot . I am missing one on each arrival when I have to switch COM frequencies from approach to tower. Cheers, Peter Peter, you've just sparked an idea. What if the ACARS were to auto-submit an emergency to the company if it detects that the transponder has been set to 7700 for a good length of time (say, for 30 or 60 seconds)? Conversely, it might be possible to add an EMGC button to the FCDU (Sorry FCOM!!!) that would need to be followed up with by an EXEC.
|
|
|
Post by Travis on Jul 21, 2014 11:38:06 GMT -5
What does it LI.{2}=6000 mean? By the way… how to add new airport and related TA? Entry: „ICAO=TA” is sufficient? Lucas, The code you've noted is a REGEX expression that means "all ICAO codes that start with LI and are followed by 2 characters should be given a value of 6000." It's toward the end of the "block of L codes" to act as a "catchall." LICC would match 7000 because it's expressly noted earlier in the block. A fictitious airport with the code LIZZ would match LI.{2} and then be given a TA of 6000. Data in that file is very specifically placed - one entry out of place will make it untrustworthy. For instance if you moved that line to the beginning of the "block of L codes" then all LE & LI airports would have a TA of 6000. If you moved that line to the end of the "L block" then the LE & LI leftovers would match the L.{3}=5000 value. I try to update this file at least once a year, and I use one of the NAVDATA sources for my master data. If you have a new airport - or a correction to an existing one - please pass me the data and I'll check and issue an update.
|
|
|
Post by Travis on Jul 21, 2014 12:14:33 GMT -5
Hi Travis! Thanks for reply...so could you give me recipe for this problem? I still get penalties...yesterday, ENZV to EHAM, transition altitude 7000, changed to standard at about 7300 ft (just after FO told me about it) via altimeter knob rotate, not by press STD button (aircraft NGX737). Please.... I don't know what I'm doing wrong Lucas, I don't have the PMDG 737 so I'm basing this on what I've seen Dutch write. The PMDG 737 should be interfaced so that it take the "PMDG altimeter value" and sets the "FSX altimeter value." It should immediately do so if you move the knob, but the STD button may not change the PMDG value for a while. So try this - on your next flight, use the VC knob to set it for your aircraft when your FO tells you it's time. Then use the FSX key command (it's usually SHIFT-B) to set FSX standard pressure. (I assume the PMDG aircraft will ignore the SHIFT-B command, so no harm there.) The ACARS should see the FSX pressure change to standard and be happy. Or if you really want to "cheat," while you're on the ground, after you set your PMDG altimeter to local pressure, use the FSX key command to set the "FSX value" to standard. I'd guess that once you pass TA, the ACARS would see that standard pressure is set. Now for something that I may have mislead you on earlier.... I had written this: You don't get penalties for not setting your altimeter on descent for two reasons. But what I didn't write was, " You would get a penalty if you set your altimeter to a non-standard value before crossing the TA (plus 1000 ft.) on descent." So if you're descending into EHAM and you set local pressure above 3000+1000, ding. Penalty. However the ACARS would be perfectly happy if you landed at EHAM with standard pressure set, no matter the local pressure. So never set the local pressure until your FO let's you know it's okay. (But if you forget to do so on descent, no penalty.)
|
|
|
Post by Travis on Jul 21, 2014 14:06:17 GMT -5
There is a new AIRAC cycle that's about to begin, so I will endeavor to update the transitions.cfg file within a week....
|
|
|
Post by Lucas on Jul 22, 2014 9:02:28 GMT -5
...and this is probably IT! I always set local pressure on descend just after passing TL which stated in destination ATIS. If TL is more then 1000 ft bigger then TA - I have penalty. So I should always check TA on destination airport, not TL. Thank you Travis However, this is little unrealistic...I think...pilot should set local qnh after passing TL on descend, which sometimes is much higher then TA. Example: Poland, TA is 6500 but TL is 80 or 90 in case low local pressure.
|
|
|
Post by Travis on Jul 22, 2014 12:18:26 GMT -5
However, this is little unrealistic...I think...pilot should set local qnh after passing TL on descend, which sometimes is much higher then TA. Example: Poland, TA is 6500 but TL is 80 or 90 in case low local pressure. We don't have a definitive method to specify the TL for any possible airport... there are lots of rules around the world and I've not yet collected them all. Then too, some TL rules are based on the local pressure, and sometimes that information isn't completely reliable (or obtainable) from within the sim. So for now just consider all TLs are TA + 1000. It's not realistic of course, but it's a decent compromise until something reliable can be worked out. When Dutch returns, I may have a fudgy idea ready for him to consider....
|
|
|
Post by Lucas on Jul 22, 2014 15:49:30 GMT -5
...thanks again Travis. I hope I will not come back with this problem again All the best! Lucas
|
|