tcas_climb

True, it was also said that the autopilot cannot perform miracles and there will be situations, such as what you described where you have no choice but to turn off the automatics and take over.

This was discussed in length in another post. There's a particular blog where a 777 pilot speaks about go around and acceleration and meeting requirements for turns required in the missed approach procedure where a smaller radius turn may be required to conform to the missed approach track and you achieve this by preventing the aircraft from acceleration, and also possibility of busting altitudes when the engines accelerate when the speed bug jumps up. From what i remember reading, and from what I understood, there's a certain point during the climb to the missed approach altitude, given the rate of climb among other parameters where the aircraft will calculate a level off path and if there is a big enough thrust change during this level off path it can cause an overshoot. Anyway long story short the procedure they use at his company is after pressing the toga switch, increase the MCP speed by 1 kt until you level off, I have tried it and it works well but i prefer to just change the speed upwards to the Flaps 20 manoeuvring speed. Making this speed change, even by 1 kt will prevent the autopilot from increasing speed automatically and reduce the likelihood of a massive overshoot in our desktop sims

I know one method is the put in a VOR on the FIX page, then manually tune the VOR and compare the raw data (radial and dme) to the bearing and distance in the Fix page. Another method involves the the FMC page that has the inertial positions on it, cant remember which at the moment.

Since you're taking a look at this Bryan is fs2crew able to see the fuel quantity? Because the procedure is to turn the center fuel pumps off in the cruise when it reaches 3,000lbs and have the aircraft transfer the remaining fuel via scavenge pumps which happens automatically when the wing tanks reach about half

Yeah the additional voice pack is something you buy and install on top of v2

This is a very weird SOP. One would think the more lights the merrier when looking at a safety standpoint.

Interesting.

Is it your fuel level that is increasing? If so then you probably have the ground ops enabled.

Hmmm seeing that you have been away for 9 years, may I suggest going with the time tried and reliable FSX, I don't have any experience with the steam version but be sure to use the acceleration when going for the old box version, then aim to go to p3d v3, while yes there are some issues with it, it is still new and developers all over seem to be excited about it so their issues will soon be resolved.

Hello everyone. I've had an idea for the longest while to do a tutorial type video on how to properly escape windshear for flight sim especially now since that is a real possibility with the breakthrough that is Activesky Next. Although the video isnt as professionally done as i would have liked (ive just started to record gameplay video) and the audio is messed up, i still wanted to share it with you, as someone here might learn something they never knew before. I know the Sim sounds are very loud, i will work on that if i ever do another FSX video, but i hope you can still hear and understand what i am saying. I tried to provide a solution by creating sub titles but boy is that a painful process that has surely taught me a lesson in making sure the audio levels are okay before doing a full video. I know some things i explain will have errors but the main aim of the video is to show how the escape maneuver is done. Anyway, here are the links, read the short video description and if you're into sim racing, check out those videos too! thanks for your time. video 1 video 2 video 3

Not sure it's a bug will have to check the manuals, but as noted it's usually an option purchased by airlines.

That option is only available on the pmdg 777 I'm afraid. You just have to engage lnav again.

When the [19JUL15] The view from the top topic gets unpinned then you'll know something is brewing.

Interesting tidbit I learnt, in the 777 fmc you use P/P### (# being heading you want to fly) to fly a heading from present position to infinity and beyond in LNAV, and WP### to fly a heading after passing a way point in LNAV, doesn't work in the NG though, I wonder why Boeing thought that would be useful, kind of like the automatic step climbs in the MD 11.

I suppose then to prevent a massive over shoot in the sim aside from doing things manually would be to select a speed after selecting toga or hitting vnav after passing acceleration altitude.

You know what, come to think of it I think the FO might be messing with me, the speed window remains open so the fms shouldn't have control of that. Fs2crew might be treating it as a manual go around and sets 220 as an approximate min clean speed without the aircraft being totally clean.

In my video I did not change the speed from Vapp and it's when alt capture engages that's when the speed bug jumps to 220 causing the engines to accelerate and causing the overshoot. Next time I get the chance I'll try changing the speed as you did and see if that makes a difference.

What did the speed bug do? Did it move? Did you leave it at Vapp throughout the procedure? Or did you set it to something else? What is the acceleration altitude set to?

I've never experienced an overshoot after takeoff though even when the altitude is set to 3000. I have a few work around that may or may not work to prevent this but I won't be able to try them for a few days, but maybe you could to see if it helps. 1. Try using vnav or flch during takeoff or go around after you've passed acceleration altitude. Or 2. If you really really really want to use v/s during the go around, after passing acceleration altitude try setting your mcp speed higher so you beat the autopilot to it and don't get that huge burst of thrust at the last moment that the autopilot can't keep up with. Only the real T7 pilots or pmdg themselves can look at the video and tell if something wonky is going on, but until then, stay ahead of the aircraft and takeover manually if things don't work as they should.

I believe this is what the OP is experiencing. Sorry for the jerkiness, this is the first time i am recording fsx and the sim was smooth until i started the recording. It seems that as ALT capture occurs the thrust accelerates to full G/A thrust, because the mcp speed is set automatically to 220, and this increase in thrust is what causes the overshoot. it is worse if you have poor framerates.

OP I feel your pain. I have experienced this a few times in the past. The behavior during this phase seemed illogical from a common sense point. Now I can understand if it was a matter of the aircraft configuration being changed and messing up the path/arc logic (some form of calculation involving current altitude, target altitude, rate of climb/descent and a few other parameters) that is calculated by the afds for altitude capture (for example making major configuration changes during ALT capture could cause an under shoot or overshoot of the altitude). Sorry but anytime I talk about the technical stuff that happens in the background I get all excited and what I want to say makes sense in my head but comes out jumbled and poorly put together. Anyway the last time I did an autopilot go around, the missed approach altitude was 5000 and I decided for whatever at the time to use v/s. Now the speed was stable, the v/s was stable at the established rate, then somewhere during ALT capture, the engines accelerated to almost full thrust and the v/s shot up through +4000 fpm, overshot by almost 2000ft before coming back down to 5000 ft. Keep in mind however that this was before the most recent update which I believe was to contain a fix for this and I haven't done a G/A since, but I will the next time I fly a full flight and report back, with possibly a video if it happens. With all due respect, and a lot is due trust me I highly respect your knowledge and your input on this forum, but sometimes one should not always be so quick to dismiss things. I know you require cold hard absolute facts when certain claims are made but I've learned sometimes common sense (which is a rare thing these days) and intuition are sometimes very valuable. Take for example on initial release how persons were complaining that the fbw behavior wasn't quite right.

I'm still on ASN SP2 but i remember there being an option called "enhanced turbulence effects" or something of the sort, they said this might cause handling issues, maybe this is enabled?

Yeah thats the cost index i used to use myself, until i discovered that simbrief appears to sort of calculate a cost index for you. It seems to be accurate with a cost index of 80, but the further you deviate from that, is the less accurate it seems to become, at least the TAS that is.

I figure, i just thought i'd cover whatever angles i can. Yeah when using fixed cruise speed vs cost index for planning it is spot on. So since no one has responded over at the other forum, ill just have to edit the performance file myself, oh the pain Thanks for your responses guys.

Hello all, this is basically a copy and paste from a topic i made at the PFPX forum which nobody seems to have an answer for, so i figure why not give it a shot here. There is an issue which has plagued me for some months now. Something seems to be up with PMDG 777-300ER and the same performance data in PFPX. When i use the bias tool and I enter the values i see real time in the sim, the calculated TAS value is off. For example, when i enter these conditions GW - 635,000 (lbs) Alt = FL340 Cruise/Cost Index = 200 SAT = -49 Act Fuel Flow = 18000 Act TAS 487 And leave the Ground speed blank, the TAS calculated is 496kts which is almost 10 knots higher than i am seeing in the sim, however when i change the Cruise/Cost Index field from 200 to M.83, while the 777 in the sim is crusing at M.835, the TAS calculated by the bias tool (485) is closer to what i am seeing in the sim (487). Can anyone help me figure out what is going on? It's almost as if the Cost Index data is off in either PMDG or PFPX. I understand that there can be discrepancies between flight planning software and the aircraft but the only reason i bring this up, is that it used to line up almost perfectly (within 0-3 knots) on every flight, and somewhere along the lines, when updates for both the 777 and pfpx were released, this discrepancy shows up. So i'm asking here to see if anyone else that uses this combo notices this and what they think could be the issue.