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.

captJaz

Members
  • Joined

  • Last visited

  1. I'm calling the before start procedures when the FA inform me that the cabin is ready for pushback. According to the instruction, once the FA inform you the cabin is ready you call before start procedures then call before start checklist to the line. Once that is done, you call before start checklist below the line. Then we should see the call for cockpit to ground but it is not there. This option disappears if you don't call before the FA comes into the cockpit. I'm following exactly as you have it written in the manual. Again the only way I see this option to call the cockpit to ground is to so before the FA enters the cockpit. And, if I call cockpit to ground, the FA never comes into the cockpit.
  2. Hello, I noticed that if you wait until the flight steward comes into the cockpit to let you know that they are ready for pushback the call for cockpit to ground disappears and there is no way to get the call to come back. As a result, I end up having to push back using FSX default pushback with no guidance from FS2crew at all. In order to avoid this from happening you have to click cockpit to ground before the steward comes into the cockpit to let you know that the cabin is ready for pushback. And, if you call cockpit to ground before the steward comes into the cockpit, the steward never comes to the front to let you know they are ready for pushback. Thanks
  3. Yes once I take off, I wait until I'm about 1200ft then I select autopilot and the plane autopilot will connect. VNAV and LNAV work too. I'll work on this all day today to try to figure out what is going on.
  4. I think it maybe due to the trim. I know that ifly is very picky about trim that if you don't have it set just right it will not connect the autopilot. I'm not a real world pilot and I have no experience what it take to level a real 737 after take-off. Because of this I have really hate to fly the model. But I found out today that I brought a copy of fs2crew years ago and put it on the shelf when I couldn't get the ifly 737 autopilot to connect. However, recently I read that if you set the VNAV and autothrottle before t/o it will engage without having to fumble around trying to trim the aircraft. Yet this is the opposite of what is happening in FS2crew flow. Oh and yes I use CH for my yoke and Saitek x52 for my throttle. I don't mess with the trim once I'm in the air. I guess I'm going to shelves the ifly 737 because I just don't like how they have made it a real pain to figure out how to trim the thing so that it works with fs2crew.
  5. Hello, I'm not sure if I'm doing something wrong, but when I program the MDCU I put in that my crz level should be FL250. Everything goes well on the climb out until I suddenly realize my speed drops to almost stall. I can't figure out what I'm doing wrong. I don't know what the problem is because without using FS2crew, this doesn't happen. As my plane continues to climb to cruise level, it barely makes it without stalling. However, the nightmare is not over because once I reach cruise level the plane does not stop climbing. It continues to climb until I completely disengage autopilot and try to correct for the stall. By this time, I'm struggling to keep the plane in the air. Can someone please provide me with some suggestion on what I maybe doing wrong?

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.