xkoote

Members
  • Content count

    320
  • Joined

  • Last visited

Community Reputation

41 Neutral

About xkoote

  • Rank
    Member
  • Birthday 02/18/1977

Flight Sim Profile

  • Online Flight Organization Membership
    VATSIM
  • Virtual Airlines
    No

Contact Methods

  • ICQ
    0

Profile Information

  • Gender
    Male
  • Location
    Curacao
  • Interests
    Aviation, automotive

About Me

  • About Me
    MD-80 Captain
  1. I believe that the autopilot couldn't keep up. It's a software and it has limitations. On the real aircraft operators usually set the restriction, until it is assured that it will be complied with by VNAV. However it is not a requirement for VNAV to have the hard altitude set in addition to the FMC programmed restriction. I have flow empty 777 freighters, and reached FL390 12 minutes after takeoff. This airplane is a beast. To isolate weather it was user error, did your FMA switch to VNAV ALT? At these rates of climb, capture occurs 2000-3000 feet before the restriction. If it switched and busted anyways, I would chalk it up to software limitations. What I would recommend you do next time is to switch to V/S. The speed window will open to the last FMC set speed (1. Flap placard -5 kts, or 2. FMC speed restriction for the active SID waypoint, or 3. 250 knots if the flaps have been retracted already and no speed restrictions exist). Reduce V/S to 2000 fpm or below and set speed accordingly. The only thing is that now YOU are resposible for meeting the restriction if you choose not to have the MCP set at the restriction altitude. But that is what we are there for right? Enjoy!
  2. I seem to recall that this issue was addressed in a recent update. Do you have all updates installed for the 747? Cheers,
  3. This has been a recurring topic. It has never been addressed to my liking and I still feel the 777's autothrottle to lag behind actual conditions. The 747 is way better at this. I have just learned to cope with it by helping with F2/F3 keys. But the system is by far not the way the real one handles. cheers,
  4. Good for you ! 👍🏽👍🏽
  5. In my experience this happens when the SIM autostart feature has been triggered. I forgot how I solved it, I believe E 1 2 (to select both engines) then CTRL E to disable the autostart. Cheers...
  6. IF you want to go down this route, I recommend deleting the axes in the SIM. And then assign the same axes as direct to FSUIPC calibration. This saves you from having issues with the speedbrake lever if you are going to assign it to an axis. I had a lot of trouble with that. CAUTION.... As Kyle has warned many times. Be prepared to do a LOT of reading and research when going the FSUIPC route. It's not for the faint of heart. Good Luck (In Taken phone voice) 😀
  7. It does not on the 777 for sure. This is what you have turnoff lights for. Regards,
  8. PMDG changed the way panels and scenarios get saved, adding that previous states might not work properly (Changelog). Was this by any chance a pre update panel state or scenario?
  9. Adding to HighBypass's comments, remember that the core jet is not being reversed on these engines, as opposed to e.g. an MD-80, where the combined exhaust is being reversed. So add to that that you also have positive thrust on the core, you have a closed reverse system, while that huge fan is still spinning down. That is a lot of total forward thrust.
  10. Is that the original QOTS 747 for FSX? I can't figure out what is wrong. You can; - Check your gross weight under the FSX payload menu. (Don't change anything, just not the gross weight). - Is/was your speedbrake extended? The TAT looks OK for 350 KIAS. At 1st I thought it might have been the FSX realism setting of displaying TAS on the IAS display, but it is not it when you look at the ND. So it beats me. Hope you figure it out.
  11. Also, in this case, highlight does not seem to mean you are exceeding a restriction. Actually it seems to be telling you that may exceed the MZFW if you fill the cabin with passengers. That is all.
  12. Exactly, however. Those values highlight at the same values every time. Be it an empty, or partly filled cabin too as you mention. So it must be a heads up of some sorts that passing those values will limit pax load.
  13. No it's not. I can load up more than 66500 lbs of lower deck cargo and still be under MZFW. What I believe now is that if you fill the plane full of passengers, that will be the amount of cargo left over before reaching MZFW. Not sure but I'm going to check after I land. This assumes again that all seats are filled with 190 lb adults. It is probably also why you can still go over the mentioned amounts, as it only tells you that if you go over a certain amount, you can't go full adult pax anymore..
  14. Well I would think the same thing. However the limits are: 30270/28279/5990 in pounds. Which is 66500 pounds. I hardly think that it is all the 744 can carry in its underbelly. At LD1 max weights, that means 9 units in lower front and 8 in lower aft. The capacity is 16/14. Now I already know that volume capacity and floor loading are 2 different things, but the difference in full LD1 qty against volume capacity doesn't match up. Also, there is a point where you get invalid entry in the cargo hold when you enter a value that is too high. That would probably be the load limit. But there is no desription of what the highlighted text means. I don't believe it is related to CG as it always changes at the same value. Doesn't matter in what sequence you enter them. Anything above the mentioned values turns highlighted...at any time on the ground. Cheers,
  15. Nevermind. I figured out that when the GPS date becomes available, it will no longer accept manual entry. If yo want to try it, inhibit GPS NAV in POS REF, then go back to ACARS. Now suddenly you can insert the date as stated before :-)