PMDG 737 Discussion (Xbox Series S|X version)

Thanks man, I may have worded that poorly.

My question is whether or not the autobrakes actually engage above 90(88) when you idle the thrust, for me it doesn’t seem to but maybe the game doesn’t realize the thrustlevers are closed without an additional input like, maybe “reverse” or “decrease thrust”. Because like you said: once you’ve closed the T/Ls and reached for the speedbrake those brakes should be putting you in your seatbelts before Reverse is even selected.
Have you noticed something like that?

Thx all :wave:

1 Like

Interesting. Can’t reproduce. I think in the PC version it works as it should but I haven’t checked if it’s exactly 88kts. I don’t think this would be the kind of thing that PMDG would get wrong so it could be the case that this is an XBOX version specific bug that they’d need to look at.

1 Like

Anyways……

I set the “decrease throttle” input instead of the “reverse” input to my HOTAS which works great. Push the button when closing the throttles and the reversers open, N1 increases, the spoilers deploy and the brakes go to RTO. Love watching the BRAKE TEMPS on the Lower DU go thru the roof.

I found that in the PMDG “simulation options” there’s a setting to manually override the autothrottle which was set to “NEVER” which isn’t helpful when trying to reject a takeoff, set that to “THR HLD/DES ARM ONLY” which is way better for initiating an RTO with the HOTAS throttle although the “ALWAYS” option might be even better because otherwise it won’t let you close the throttles with autothrottles in TOGA until the FMA goes to THR HLD.

Anyway, blablabla, most of you will probably either know this OR think it’s utter gobbledeegook. Either way, just thought I’d share :blush:

:pray:

3 Likes

What’s the rationale for the flaps 40 setting? Is it to aid evacuation if required?

If you mean during rejected take off, yes.
On any “on ground emergency” situation there are actions done immediately by memory. By on ground emergency I mean anything that happens on the ground, including during taxi or while parked. In our QRH the On Ground Emergency is defined:

CAPTAIN:
-Stop the airplane.
-Set parking brake.
-Advise cabin crew through PA (In all cases except during rejected take off). It could be a PA call like “Cabin crew stand by” or “Attention cabin crew at stations”… it varies between companies but it usually means: “Something happened. We’re aware. Be prepared. We’re not incapacitated and we’re dealing with it”. It’s important for the cabin crew to know this before their own potential big deal decision to evacuate without pilot command.

FIRST OFFICER:
-Once parking brake is set, set Flaps 40 to facilitate a potential evacuation through over-wing exits.
-Inform ATC giving position of the aircraft and nature of the emergency followed by the word “stand by” so that they don’t interrupt us during assessment and checklists.

Then the flight crew will evaluate the situation calmly and decide the course of action (QRH, Evacuation, etc).

Two possible outcomes. Evacuation command or communication with cabin crew by making a PA like “Attention purser to flight deck” or “Number 1 to the flight deck” after which an “All Call” through the interphone will take place.

3 Likes

Brilliant insight. Thanks.

I’ve had one RTO* on the 737 in Innsbruck that went according to the numbers I think the only bit I missed was the flaps 40! I had to sit a while and cool my brakes!

*Root cause was someone not following a complete checklist! Can’t imagine who that would be!

Had a flight from CYUL to CYYZ this morning in the 737 and all went well. Tried yesterday leaving KBOS to CYYZ and it failed at the gate!

Not sure what airports to try as it seems it is hit and miss with 3rd party ones, and may be even Asobo’s!

Could someone tell me what went wrong in my flight this morning…

Coming in to land at Colorado Springs ILS 35R, I wanted to try out the auto land in the 737-800 as I’ve not used it for a while.

I set both FD to on, both courses to 352, both Nav 1 & 2 to 109.10 and set the airport elevation. Once established on the GS, I then selected both AP. Everything seemed to be going as intended until around 100ft from touchdown when I got a “too low terrain” warning. I disengaged the AP and manually landed, hard.

Any idea as to what I did wrong, did I miss something or was it just “one of those things” in MSFS…?

Anyone else having issues with the MCDU when you use an Xbox controller and touch the BRT button it gets stuck on the brightness going all then way down to pitch black and there is no way to go back up.

Did you set your minimums to zero?

You shouldn’t get a “too low terrain” if you’re established on an ILS. What do you mean when you “set the airport elevation” btw? The minimums for the approach, I’m guessing (in this case set the MINS knob to 200AGL for BARO and something like 50 on the RADIO, depends on all kinds of details, and leave it set to RADIO usually for an autoland)

Sounds like a simulation f*ck up to me :thinking:

In the airplane we might suspect an incorrect EGPWS database, but even then it seems unlikely…

That sucks, sounds a little like the “spinning knobs” glitch, can you use a different input? Maybe try with a mouse, just plug it straight into the Xbox.

I don’t know but I usually hit APP once or very close to the point I am on/near the localizer- about 10 miles out and I put the wheels down with flaps 10. Then I hit the other AP and I move into the GS (about 4-5 nm out) for landing and adjust the flaps, usually at 30 degrees and adjust the speed for 30 degrees. I have set the VNAV (in your case it would be set to 8100 feet) and LNAV on long before this so the plane can descend at the T/D marker. The frequencies and courses you listed are okay and the DA(H) is at 6318+40. I do not know if this helps but on the Des button I hit forecast and then put in the temp/baro pressure and hit execute. I keep track of the barometric pressure and although I have it set on the PFD wnen STD is on, I nevertheless use “B” on my keyboard at lower elevations just to be sure.

I will try things later but meanwhile that should get you there and down. If you have followed what I wrote then I guess it might just be “one of those things.” Good luck and happy flying!

The airport/runway elevation is on the overhead panel on the right side, just below where you set the cruise altitude for cabin pressure.

Ah, the pressurization panel…yeah that won’t lead to a EGPWS warning, just the OFF SCHEDULE DESCENT annunciations the sim likes to give

1 Like

Just for fun, here’s an example of what Boeing might say about autolands:

It’s somewhat conservative, you could delay Landing Flaps and checklists to be done by 1000AGL at busy airports assuming poor weather conditions

3 Likes

What is the figure out of and is it available on a site?

It’s from a Boeing 737NG Flight Crew Training Manual. It should be online somewhere (just Google 737 FCTM pdf) but this is a quick snippet from a company iPad Electronic Flight Bag

Cheers, it’s detailed enough and I am sure I can find it online!

1 Like

That’s very useful for us novice sim pilots