Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

GearDown71

Members
  • Joined

  • Last visited

Everything posted by GearDown71

  1. To be honest I don't see any difference here. Now my problem is the following, maybe I didn't make it clear enough above there, so I'll explain step by step. Before descent I check the weather at my destination airport and set the pressurization to the local ones, but don't activate it, just set the correct value. Now I'm passing Transition Level, then push the QNH-button to switch the primary altimeter to the local QNH and call for the approach checklist. My FO says for example "altimeter 1017", I confirm, he answers "Approach checklist complete". That's all fine to me. Now on further descent, when passing the Transition Altitude of my departure's airport, FS2Crew switches back to standard QNH 1013 calling "Transition Altitude, altimeter 1013" like if I were climbing out. But I'm not, as I'm approaching my destination. Am I doing something wrong here? I can't see any difference to your explanation. And here comes my full name, finally: Manuel Hirsch ;)
  2. Damien, I can't quite follow you. For the first one: When exactly do you switch to the local QNH if you don't do that when passing the TL? For the second one: Maybe it's company procedure. Could you tell me/us which company you oriented yourself on that does in fact turns off the beacon lights as soon as the engine levers moved to cutoff position? Manuel
  3. Hi all, I have a few problems/suggestions I'd like to make for an eventual update for the FS9-IFly-VoiceSoftware by FS2Crew. 1.) When I'm on descent and switch to the local pressurization at TL, my FO automatically switches back to the standard pressurization at TA. That's quite annoying as I have so switch it back then again. And as far as I've seen from other topics on this forum, I'm not the only user having problems with the TA/TL behaviour. 2.) When I'm going on blocks and shutting the engines down (as soon as my FO calls himself ready), my FO switches the anti collision light (beacon light) to the off position right away. I've never seen any cockpit crew doing this when I was at the airport and I'm confident, somewhere on the internet I've read that although it's company procedures, a lot of operators leave the beacon light blinking until the N1 is nearly 0% and N2 is below 1-5%. As you can imagine this probably has safety reasons. You still can be 'hit' by the engine exhaust stream at low N1/N2 rate. So what do you think of an update?

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.