adamant365

Was your fuel freezing? PMDG accurately simulated the affects of very cold temperatures on the fuel system of the MD11. Were you able to relight the engines after descending to a lower altitude? A Google search of "PMDG MD11 fuel freezing" will bring up loads of threads on the topic and how to resolve it pre-flight. Hint, you can change the "freezing point" of the fuel on the "FUEL INIT" page 3/3 while on the ground by using Jet A1 or by directly changing the fuel freeze temp by entering a ower number.

What do you have your setting for throttle override set to? In the PMDG options in the FMC you have the option to have your throttle lever override the A/T: Always, Never, or Only in Hold Mode. Look at the Introduction Manual starting on page 93. If it's set to "Never" then that's not the problem. "Always" can definitely be an issue if your throttle is creating "noise" and overriding the A/T. If it is set to "Only in Hold Mode" that could also be the issue, especially if you see the issue only at times the A/T is in "HOLD" mode. As for your near stall on approach, that sounds eerily like what happened to OZ214. What A/P / A/T modes were active at the time of your near-stall??

EK (Emirates) fly to many destinations in their network that are <6 hours. There are other European and Asian carriers that fly <6 hour flights as well. I've been flying the 300ER more than the 200LR since the 300ER came out and I was worried I wouldn't get the opportunity to fly it much.

In addition to what Dan said, I completely unmapped the "Engine" E key from FSX. I used to have the same issue constantly. On the fly, one way to make sure you have both engines selected is to press the "E" key followed quickly by the "1" (top row number) key followed quickly again by the "2" (top row number) key. You DON'T press the keys at the same time... just do it in sequence E then 1 then 2. That will select engines 1 and 2 so that both are being affected by your throttle.

I'm glad my limited knowledge/experience could help someone else. There's something in the FCOM about the A/C not allowing trim inputs that oppose the elevator commands. I can't remember if it applies only on the ground or not though. Glad you got it sorted!

Also make sure your yoke is centered. I had the same issue with the 200LR back in February and I found my yoke was commanding slight nose up so it wouldn't allow my nose down trim input on the ground.

I definitely had the trim issue prior to SP1b and I can report that it is much better with the latest update. Prior to the patch, I was all over the place, particularly in turns. Although I do have to apply yoke back pressure in turns, otherwise, trimming seems to work much better. I have my main flight controls (rudder, elevator, aileron) mapped in FSX. The only flight controls I have mapped in FSUIPC are the trim switch, throttle, and reversers. I have a 10% "null zone" set in the PMDG menu. Regarding the back pressure in turns...I thought the 777 FBW was supposed to apply the elevator correction automatically in turns. I didn't think pilot elevator input was required in turns to maintain level flight. Am I incorrect?? Because if the FBW is supposed to handle the elevators in turns, that piece definitely isn't working.

Good job guys. Much much smoother on approach. I just did a few circuits around KTUL (AA maintenance) and it was as smooth as could be. Great work!

Speedbrake doesn't need to be armed for T/O. Some things that will cause T/O Config warning are improper flaps, improper trim, or speedbrakes deployed. I'm sure there are others but whether or not speedbrakes are armed makes no difference. Didn't realize the comment about armed speedbrakes wasn't aimed at the OP. Armed speedbrakes shouldn't cause a config warning on descent either. If flaps are 20 or higher, you will get the gear horn though.

Apparently I can't quote or multi-quote posts.... Thanks admin for the friendly reminder, I have removed system specs from my sig line. Thanks Ryan for the FBW/Trim confirmation. That's the only issue I've experienced so far.

Very excellent. I can't wait. Thanks for the update! Oh wait...meant to ask. Will the update correct the odd FBW/trim behavior?

It does happen with the 77L, but since the 77L is much shorter in length, it is less pronounced.

In the CDU, there are options defined per livery "Airline Options." You have to look there, not the Addons menu. The option is also in the PMDG Operations Center. This is all in the introduction manual. Give it a read...lots of good info there and the "solution" to about 85% of the "issues" reported here.

There are several topics on this subject. If you are familiar with using EditVoicePack X, here's a link that will help you: http://forum.avsim.net/topic/422862-ground-control-not-recognizing-boeing-777/#entry2818722 Otherwise you can also do what Kyle says.

If you are referring to ICAO codes...it's only B772, B773, B77W, and B77L...there's no 77E or 77F for ICAO, although sometimes individual airlines do use codes like that. That is really quite interesting...never knew that. Is there a list or database of those /x codes where I could find the others? I've always been curious about those.

772/L is different than 77L. I'm not all that sure what the /L means but it has something to do with the subvariant or something. The first 4 digits is the ICAO aircraft identifier ("B772"). BA don't have any 77L's, only 772 and 77W. Nor is this a codeshare flight...it is actually BA2037 operated by a BA 772.

Excellent, thanks!

Did you ever get a response from PMDG?? I don't see that this item has been added to the Issue Tracking Thread as of yet.

This has something to do with FSUIPC assignments if I remember correctly. The gear is "up" but the PMDG code thinks it's down. Do a search for Google search for "PMDG nose down" and you'll find what you are looking for. It caught NGX users as well.

Unless you have an EZDOK profile for the PMDG 777, that will cause you to have to create a new EZDOK profile. If you have EZDOK and are familiar with EditVoicePackX, here is a link to a better way to fix the ATC issue: http://forum.avsim.net/topic/422862-ground-control-not-recognizing-boeing-777/#entry2818722

Can anyone confirm if AT being on at touchdown prevents reverser deployment until nose wheel touchdown in the real aircraft?

So can someone confirm for me if this is an issue with the PMDG sim or not? It seems odd that using the AT (per Boeing recommendation) would prevent reverser operation until after NWG touchdown.

I have always left the A/T engaged until touchdown with the T7 and I have gotten into the habit of pulling my hardware throttle to idle at TOD (hardware throttle override is set to Never, BTW) just to eliminate potential issues later on. Therefore my hardware throttle and the A/T throttle should be at idle at main gear touchdown or very shortly after. Either way, I HOLD down F2 as soon as the mains are down which would certainly bring the thrust levers to idle in FSX. Even when I hold the nose off for a bit, I still don't get REV in yellow on the EICAS telling me the reverses are unlocked until the moment the nose gear is down. Should I have to disconnect the AT when the mains touch? Or is it possible the AT isn't really commanding full idle and also isn't disengaging until after the NWG touches therefore preventing my F2 press and hold from having any effect? It's a minor inconvenience and I have yet to run off the runway...of course I'll only put more wear on my brakes with REV not coming available in a timely fashion. As for the spoilers, like I said, 8 out of 10 panels are deploying on MLG touchdown which should be plenty to put weight on wheels for braking effectiveness. It's just the last 2 panels for the ground spoilers that aren't coming up until NWG touchdown.

Hello Experts, Can someone explain to me the logic behind the ground sensing mechanism and the reverse/ground spoiler lockouts? The reason I ask is that I am unable to unlock and engage reverse thrust until the nosewheel is on the ground. In addition, the ground spoilers only deploy when the nose wheel is on the ground. I get all of the flight spoilers, but I do not get the ground spoilers until NWG touchdown. I don't think this is correct because I've seen many a 777 video where reverse and all spoiler panels come in before the NWG is on the ground. Here's how I perform the landing: 1. Flare 2. Land 3. As SOON as the Main Gear are on ground, I hold F2 until the reversers unlock. 4. I then proceed to use my hardware throttle assigned to reverse to set the amount of reverse I desire. But no matter what I do or how long I hold F2, the reversers don't unlock and those last two panels of spoilers that make the "Ground Spoilers" don't deploy until the nose wheel is down. Can someone else give this a try and see what happens? I have read about this in the manual (FCTM and FCOM) but there is some vagueness about when these two systems are available.

I think Luke is spot on. When you cycle through the views in FSX, but there is no tower around and therefore the view cycles from cockpit to spot view and back to cockpit, it will freeze the displays. As Luke says, simply cycle through the interior views to restore them. It's a strange bug in FSX itself that never got fixed, but it definitely has something to do when you are in remote locations that don't have any tower views available and you try to cycle through the main views.