Airbrakes

You can press CTRL + K to turn off the joystick.

I didint get it with the 767 but maybe its because of the airport I landed in ( KDEN ). Ill fly to RJAA tomorrow with some of my other addons to see if I get the same result.I have quite a few planes that have a CAT3 Autoland so this could take me a while :-eek.

>I'm not sure if the airport has a bearing on this particular>issue.>>I say that because Kevin has indicated that the autopilot is>disconnected by this point so it isn't following rollout>guidance via the Localiser, as positioned in the AFCAD file.>>Beyond that I can't think of anything airport-specific that>would cause an uncommanded turn on the ground.>>This is a bit of a puzzler. At some point this weekend I'll do>a couple of circuits at RJAA to see if I can replicate this.>>Kevin, some important questions before I do this:>>- What version of FSUIPC do you have installed>- What brand of joystick are you using?>- This is the default RJAA right?>- What runway(s) at RJAA does this happen on? >- Does it only occur following an autoland or is it on any>landing?>- Are you running real weather such as activesky?>- Roughly what weight would you have been at landing?>- Where had you flown from?I have FSUIPC ver 3.7 ( registered )Im using the Saitek X52Yes, I have no addon scenerySo far its happend at every runway at every airport. The runway at RJAA I landed at was 16L.It only occurs after autoland. This dosent happen if I land manually.Im running Active Sky 6.5Don't quite remember the weight but my VREF speed was 155KTS.The route was KSFO-RJAA.

Negative on the joystick, I checked the EICAS to confirm that. The 763 didint go right like I expected it to. Now Im a little confused. It just seems to be isolated with the PMDG planes. Well I guess untill I figure this out, Im ganna have to land the planes manually which is alroght with me, the Queen is fun to fly.

>Did it still occur at 80 knots or sooner?>>Any other differences or were the symptoms the very same?It seems to occur right at 80KTS. The autobrakes dont matter ( I found that out last night ). I know this affects both of the PMDG aircraft in my hanger, so Im going to try the LDS 763 to see if I get the same problem there. The symptoms were identical.I know the plane isint trying to keep inline with the ILS because I have the autopilot disengaged after the rollout. If I let the rutter go, the plane just goes in circles. Im thinking this is a problem with the settings in FS9 and not in particular with the PMDG planes. Thats why Im testing the LDS 763 to see if I get the same problem.

Well turning the autobrakes off didint help any :-hmmm.

>From 747-400 FAQ at PMDG Ops:>>Why does the 747-400/400F pull to either side after>landing?>>After performing an autoland you must disconnect the autopilot>after slowing down. The PMDG 747 uses the runway's localizer>signal to hold the centerline while in ROLLOUT mode. Due to an>MSFS limitation, this signal can become eratic further down>the runway. The result is that the plane starts pulling to>whichever side it thinks it needs to go to to continue>following the signal. Once you disengage the AP either by>pulling the command bar out or by pressing the yoke switch,>the plane should steer normally on the ground.>>Regards,>StjepanThanks for the reply but I stated above that I disconnect the autopilot after the rollout. This problem seems to occur after I apply the manual brakes and continues untill I shut down the sim. Even as I increased the throttle the plane still pulled. It dosent pull to either side, just to the right.

I do have a button on my controller assigned to the brakes, but its not the differintal brakes. Im doing a flight right now back to KSFO from RJAA and Ill try the autoland without the autobrakes to see if it helps.

Yes, I use the saitek X-52 and there are more than 1 control(s) for the rutter. You can go almost a whole flight with no issues, but if you move one of the rutter controls accidently this will happen.

On the top of the screen where I highlighted, click on the button labled EICAS. When the EICAS pops up, click on the other button I highlighted STAT. This will display the rutter, spoiler, and alerions positions... sorry if my typing isint the best.

Check the EICAS STAT. It looks like the rutter might be out of allignment.

I usually disconnect the autopilot after the rollout. It happens at every airport not just RJAA. It even happens with the 737NG. As soon as the speed drops below 80 KTS and I engage the manual brakes it steers to the right. A quick check of the ECAS STS revealed everything was normal: the rutter wasint out of place etc. Ill try letting the autobrakes stop the plane completly on the runway, or not use them at all and see if this helps. I have FSUIPC ver 3.7 ( registered ) so maybe there is a tweak I can do?

I have a question requarding the autoland of the 744. I have the latest version installed and Ive noticed a problem when performing a autoland, the plane wants to turn violently to the right once under 80KTS. This only happens during the autoland.I did a flight today KSFO-RJAA using FSACARS so I could see what kind of touchdown rate the autoland was giving me: -56FPM.... Wow.Is this normal for a autopilot??? The autopilot didint float down the runway and landed me right where it was supposed to, but I never seen an autopilot give that low of a touchdown rate ( on any aircraft ). Could this be the issue?

I would like to see a 707 or a 717. Not that much competition out there for the old school planes.....

>>Kevin,>>>>Have you tried the screw? Or in VC the TO/GA buttons on the>>throttle lever?>>>>Hope it helps,>>>No I havent tried the screw.... Is it in the same place as the>744?Hey I just answered my own question... The screw works, thanks :-jumpy

>Kevin,>>Have you tried the screw? Or in VC the TO/GA buttons on the>throttle lever?>>Hope it helps,No I havent tried the screw.... Is it in the same place as the 744?

Hi guys I was just wondering how to get the TO/GA thrust to arm on takeoff. I have the FMC completly programmed Vspeeds, route, perf., etc, but I cant get it to work. I even tried the CTR + SHIFT + G combination with no luck. F/D and A/T is armed also. Im running FS9, with Active Sky ver 6.5, FSUIPC ver 3.7 ( registered ).Thanks in advance for the help.

WOW :-beerchug

The 2D plane is just what it sounds like, only the 2D panel is visible.To view the side views fly the VC or the VC and Cabin.

I own the 767 training video and it is great. As stated above, very detailed training in all phases of flight. Even non-normal procedures. I cant imagine why the 747 video would be any different.

Did you select the 738/9 with no VC ( virtual Cockpit )?Just a thought.

Actually i think the FS weather isint that bad.the real issues is when you log into VATSIM and use the Squawk Box weather :-lol

>Ron's solution hits right on. Microslop shouldn't have>backcourse enabled for all approaches, which they do, but only>those with published backcourse approaches.>>Someone suggested getting a sidstar from navdata... don't do>this unless you want something that is more than a year old.>Besides, it has nothing to do with the problem. The ILS info>used by the FMC comes from the navdata, not the sidstars.the navdata, sids/stars are all in the same file. or so i thought.

i wasint referring to them i was referring to RTO's in general. they did make the right desision hense thats why i think it was the cargo.

a high speed RTO is a very complicated manuver to accomplish. ill give an example here: youre weight is over 700000LBS and youre V1 speed is around 165KTS.if your barreling down the runway and you get a problem at 140KTS ( and youre already half way down the runway ), that plane is not going to stop in time. even with a non contaminated runway with 0 slope or an uphill slope. it would be safer for you and the plane if you took whatever problem you had into the air.i would rather take my chances at around 140KTS with full flaps out at the runway touchdown zone, than being at 150KTS halfway down the runway.on another note im willing to bet 10:1 odds that the noise the flight crew heard on the aborted takeoff was the freight not being properly secured.