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.

skyrider

Members
  • Joined

  • Last visited

Everything posted by skyrider

  1. Thanks. As an side, this function is (correctly) enabled in the Aerosoft A320, so you can easily switch between the two.
  2. In the real world you will see both active & secondary databases: normally the secondary one is installed ready for you to select when the active one expires. For simming purposes, it is handy to be able to either select the previous one of there is a problem with the new one, or to select another source as there are always differences in the databases provided by the two source providers. Often, something that is missing/incorrect in one database can be found in the other.
  3. I notice that only the active nav database is shown in the CDU. Is there any way of viewing the secondary database, either the previous, backed up one, or one installed from another source, i.e. Navigraph & NavDatPro?
  4. Yes, the initial climb is STRAIGHT AHEAD to 750' (QNH). The GPWS occurs during this phase & clears once the gear is up & locked, i.e. no red lights. I have just experienced the same issue following a go around from an ILS approach to Rwy 33 at Birmingham, UK (EGBB). I have filed a support ticket via the PMDG website.
  5. On this occasion the GA followed a Cat I ILS approach to Rwy 23R at Manchester, UK (EGCC). The GA was commenced at the Cat I ILS DA of 449' (baro). I do not have any third party scenery installed. I have experienced the same issue following a GA at other UK airports, but have not posted before now as I wanted to make sure that it is a repetitive event. Needless to say, it has gone in the tech log :wink:
  6. Hi, I am getting a spurious GPWS warning during go-around: When carrying out a dual channel auto go around, I am getting an aural "Too low, gear" warning with a red PULL UP on the PFD after raising the landing gear. This is despite carrying out the correct procedure, i.e. selecting TOGA, Flaps 15, positive rate, gear up... Currently running P3D 3.3 in Windows 10. Doug Boynton
  7. I'm in agreement with 'roarkr': I'm located in the UK & have major problems accessing this site, as well as anything to do with AVSIM. An improvement in service would be very much appreciated.
  8. Yes, but it's a lot of fun! :(
  9. A Flap 40 approach produces more drag hence more power is required: in this case you should see approx 60% N1Doug
  10. For the real aircraft?Doug
  11. This seems to occur following an early turnback to the departure airfield. I.e. the planned cruise altitude has not been reached & the SID abandoned for an early return to the departure airport. I will investigate further & get back to you...Doug
  12. And there was me believing every word! Doug
  13. That fixed it for me; good catch
  14. There will always be shortcomings in these programmes but please see this extract from the 'Introduction' manual:“Simulation” should mean nothing short of incredible depth, detail and feature richness that allows for the proper application of real-world operating procedures and techniques without offering excuses as to why parts of the airplane behave differently than what is described in the flight manual. “Simulation” means that when you engage the autopilot and put the airplane into LNAV/VNAV, it should behave like it would if you were actually flying the airplane. This means that it behaves not just in easy to manage climbs and descents, but it reacts appropriately when you punish the airplane with rapid changes and demands near the limits of the airplane’s capabilities. “Simulation” shouldn’t leave you saying: “Well… it is just a flight-sim product.” Cheers, Doug
  15. Has anyone else noticed incorrect thrust mode annunciations at various stages of flight?I regularly see 'CLB' or 'CRZ' in the TMA when on final approach when it should be showing 'GA' (Yes, AUTO is selected in the N1 page in the FMC.)Cheers,Doug
  16. After installing SP1 I am unable to cycle through the views using the 'A' key on my keyboard.Cheers,Doug
  17. We now get a much more realistic 'reduced go-around thrust' setting when commencing a go-around. However the pitch setting is a bit on the low side at approx 12.5 degrees with V/S a bit on the high side at 2700 FPM. More realistic would be a pitch setting of 15 degrees with V/S 1000-2000 FPM.Also a problem is that the GPWS is being triggered during the go-around with 'PULL UP' showing on the PFD with an aural 'TOO LOW GEAR' warning evne though established in a positive climb.Cheers,Doug
  18. Still unable to engage N1 mode by pressing the N1 switch even though above 800R with A/T in 'ARM' mode.At Aa the underspeed symbol still flashes in the MCP speed window until a higher speed is set.On the plus side the FD now commands a sensible pitch setting when 'Flaps Up' speed is set.Cheers,Doug
  19. That seems a bit low to me; you should be seeing around 55% N1 for a Flap 30 approach.Cheers,Doug
  20. To clarify: Initially you will have V2 set in the MCP speed window for take-off. At lift off the FD initially commands 15 degrees nose up, then as ROC builds it commands a pitch which will give a speed of V2+20 even though you still have V2 set in the speed window. At acceleration altitude you set 'UP' speed in the speed window & the FD pitch bar should lower to command you to lower the nose & accelerate to 'UP' speed so that you can retract the flaps. The problem with the NGX at the moment is that the FD is not giving this lower pitch command at this stage & so if you continue to follow it you will not accelerate. Another problem is that, before you reset the speed to 'UP' speed, the underspeed symbol is flashing in the speed window: this should not be occuring. Cheers, Doug
  21. I can reproduce this in FSX with the NGX. I will try it out the next time I am in a RW Level D sim (soon). The reason I have not seen this combo before is that it is not normal to have a different altitude to your platform altitude set in the altitude window at this stage of the approach. Normally you will be at, or descending to the platform altitude as set in the altitude window so you will not see V/S armed. Once you have captured the glideslope (G/S GREEN) you will reset the altitude in the window to that required by the missed approach procedure if different. Sadly RW sims are not perfect either. Despite continuous quality checks & updates they still exhibit various inaccuracies & can misbehave like any other computer based device! This can make things very confusing, to say the least! Doug
  22. Thanks for the info. It looks like the AoA product for the NGX is still under development, I will stay tuned... Doug
  23. I'd be interested in seeing that; where can I get a copy & how much is it? Doug
  24. Yes indeed. Have you noticed how less & less information is provided as time goes by? Doug

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.