skyrider

I have the same issue: recently installed the 737 NGX into my desktop & laptop computers, both running Windows 10 Pro, with the Fall Creator's update installed. Neither machine shows anything relating to PMDG in the Start Menu: no Ops Center, no Aircraft Manuals, nothing at all. I have tried a number of options to manually install these into the Start Menu, but they still do not appear. A little help, please?

Thanks. As an side, this function is (correctly) enabled in the Aerosoft A320, so you can easily switch between the two.

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.

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?

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.

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:

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

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.

As previously posted, the A/T retards the thrust levers to IDLE at 27' radio, as signalled by the #1 radio altimeter. The A/T will completely disconnect 2 seconds after touchdown.

I completely agree, no argument there. Safe flying :-)

Well, it's down to company SOPs: some allow it, some don't. Some people worry that the A/T may kick in as speed reduces in the flare: in which case you can completely disconnect the A/T at a late stage of the approach, just prior to the flare. Having seen many instances of people getting slow during approach & go-around & subsequently exceeding flap limiting speeds when accelerating (when using manual throttle), I'm in favour of it. Doug Boynton

There is a very good reason for leaving autothrottle engaged: speed protection. Yes, Boeing recommend that you should use manual throttle when flying manually, to avoid instability in pitch as has been mentioned earlier (the exception being during takeoff & initial climb, which is flown manually but with autothrottle engaged). With autothrottle engaged, it will prevent speed dropping below minimum manoeuvre speed, or exceeding maximum speed for the current configuration: this protection is lost when A/T is disengaged. An alternative technique is leave the A/T latched ON, but deselect SPEED on the MCP. The A/T now goes into ARMED mode & you control thrust by manually moving the thrust levers. However, should the speed reduce towards minimum manoeuvre speed during approach (or go-around), the A/T will become active again & add thrust as necessary, thus potentially saving your neck. Following a go-around, should the speed increase towards the current limiting speed, the A/T will become active & reduce thrust to avoid exceeding the current limit. I'm talking real world here, I've not tried it to see if it is modelled in the NGX. Doug Boynton

Yes, but it's a lot of fun! :(

Works for me.Cheers,Doug

A Flap 40 approach produces more drag hence more power is required: in this case you should see approx 60% N1Doug

For the real aircraft?Doug

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

And there was me believing every word! Doug

That fixed it for me; good catch

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

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

After installing SP1 I am unable to cycle through the views using the 'A' key on my keyboard.Cheers,Doug

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

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