Hi,I haven't seen this reported before, but if I missed it please excuse me.Myself and some other people have talked to have problems with the FO going crazy when setting things on the MCP. For instance, calling "set altitude 7000" has him changing the altitude all the way up to 40,000. Similarly, saying "set course on my side 218" made him indefinitely turn the course knob. In any of the cases it never slowed down around the correct point before it stopped. It just continued to turn at the same high speed.This was especially irritating as it may be less approach unusable in very foggy weather. I had to switch to RNAV which luckily worked out for me :-)Anyway, the next flight things worked normally again. At the time I was running Active sky 2012, NGX sp1c, fs2crew, ezdoc, AivlaSoft EFB.

Hi,That's the result of the speech recognition system hearing something it can't process like "Set Heading One Three Thousand".If you get a "runaway" like that use the command "CANCEL LAST COMMAND".It's important the proper syntax be used as described in the manuals.Best,

Thanks for the clarification.Even with a welltrained voice profile there will still be recognition mistakes once in awhile. is it possible to filter out such obvious missrecognitions? I would suppose it is easy to detect whether a course, heading, or altitude is outside of the range of the instruments?

It currently does attempt to weed out junk inputs, but it's not 100 percent fool proof.For speed, if the speech system detects a speed input < 400 or > 400, the FO will say "Are you sure about that?"For course, the required condition is that 'heard' value be less than 360.So I'm not sure why you got the 'runaway' with course.If it happens again, send me your CVR log via the Config Manager so I can see what the speech engine actually 'heard'.Cheers,

The technology is amazing and every flight, I discover some other task that my new F/O is able to do. But I do have troubles when I ask him to set an altitude. Flight levels are okay. But we'll often have a miscommunication on altitude. I suspect user error on my part. I need to spend a bit more time learning proper phrasing for this particular command. But good to know the "cancel last command" for the next time the altitude dial starts spinning.But overall, an amazing product, very seamless and a largely bug-free roll-out so congrats Bryan.

Hi Bruce,For altitudes, try this:"SET ALTITUDE ONE ZERO THOUSAND"."SET ALTITUDE FIVE THOUSAND"Maybe you're trying to set altitudes like 4200?Send me your CVR log if you ever get another runaway.Cheers,

I thought this was a feature. RW FOs sometimes have trouble figuring out what in the world the CA just asked for too. :-)

The technology is amazing and every flight, I discover some other task that my new F/O is able to do. . . .

Yep . . . Just amazing what your virtual FO can do . . . My very favorite is when he sets the cabin cruise and landing altitude for you . . . Or when he reads off the entire descent checklist items for vref, etc on approach . . Very nice work . . Joe