I sometimes run into some sort of FO blockage it seems.

 

When commanding a new flight level value, I can see the read text showing exactly what I've said, but the FO suddenly responds 'ok, flight level (no value)'. Then I repeat the command in full, but he answers 'yeah, but what's the value you meant' or something. I then say 40 or whatever value and he doesn't change anything.

 

He remains on replying 'yeah, flight level (no value)' but never acknowledges the actual value. Other FO texts are 'ok, I beg your pardon, flight level (no value)' while the red texts shows a correct number.

 

It takes a few seconds and everything is back to normal. But in that mentioned phase, MCE always prompts the correct command in red text, but the FO just keeps asking about what to do, but doesn't change a thing.

 

I can't figure out what triggers that hang up, but it happens from time to time and is a bit nasty on the approach. :lol:

 

 

On rare occasions, I also see this problem with the speed setting or the flaps. Note that the red text always shows correct commands, so I guess the actual voice engine is fine with what I've said, it's just that something triggers the blocking FO.

cp

 

have had the same from time to time ... not using text showing.

 

i'm guessing here but i think one needs to command altitude 4000 below the transition level & flight level above ... seems to work for me (transition level set in mce @ 180 ??)

Good point on the transition altitude/level, John.

 

The reason I use 'flight level' commands down to the ground is that my 'altitude' sometimes comes in as attitude for the FO, which lets him confirm 'attitude 2000ft' or something, means no change on the autopilot panel.

 

With using 'flight level', he always gets the value right, except for those cases mentioned above. Now he sometimes seems to have the same trouble with the speeds or the flaps, so my guess is that something else triggers this blockage.

 

The red text display just helps to confirm that the voice engine did get the right command. Which, in my cases, it does. So there must be something on the FO logics. Perhaps something I am missing so far. :unsure:

 

 

Would there be a way to set a transition altitude and level in MCE by the way? I was flying around LGAV where the TA is 9000ft. I actually like that MCE does not require such a setup, but one could link it to the callout 'transition altitude' and 'transition level'.

 

However, I would prefer that he always accepts both ways of calling for another autopilot altitude, which, in my eyes, he currently does.

Good point on the transition altitude/level, John.

 

The reason I use 'flight level' commands down to the ground is that my 'altitude' sometimes comes in as attitude for the FO, which lets him confirm 'attitude 2000ft' or something, means no change on the autopilot panel.

 

With using 'flight level', he always gets the value right, except for those cases mentioned above. Now he sometimes seems to have the same trouble with the speeds or the flaps, so my guess is that something else triggers this blockage.

 

The red text display just helps to confirm that the voice engine did get the right command. Which, in my cases, it does. So there must be something on the FO logics. Perhaps something I am missing so far. :unsure:

 

 

Would there be a way to set a transition altitude and level in MCE by the way? I was flying around LGAV where the TA is 9000ft. I actually like that MCE does not require such a setup, but one could link it to the callout 'transition altitude' and 'transition level'.

 

However, I would prefer that he always accepts both ways of calling for another autopilot altitude, which, in my eyes, he currently does.

 

Thanks for feedback CoolP

 

Did check it today. It’s working fine.

 

You’re right about something being there in the logic though.

 

In order to deny FO dialling dangerous altitudes (below 800 feet), whenever he hears something below that value, he’ll ask for confirmation. In fact he won’t dial that sort of altitude. You’ll have to do it manually.

 

There are rare occasions where the user says “set altitude 4000” (and it’s displayed correctly), and FO somehow ends up understanding “set altitude 400”.

 

However, when you confirm, you just need to speak the number.

 

For the altitude above, just say “4000”

If it was a command for flight level 40, confirmation would be “40”. If you confirm “4000”, he’ll see it as a wrong FL value, and will keep prompting for the correct one.

 

Maybe we should remove the “set attitude mode” command, which apparently nobody uses, and causes more confusion to the speech engine. That should help the “set altitude XXX” commands go through smoothly.

 

MCE reads the transition altitude from a table provided by Travis Guy.

 

It doesn’t cover the whole world, but it’s very useful.

 

For aircraft that have an SDK like PMDG 737 or iFly 737, MCE will read the transition level or altitude you set in FMC-CDU, as well as V1, VR, V2 and a few other things.

 

For other aircraft, you can set the takeoff or landing data (including the transition level or altitude) via the <Monitor> section of the user interface.

 

The data in the <Monitor> section is what’s used for the various callouts.

Thanks, that makes sense and helps.

 

Maybe we should remove the “set attitude mode” command, which apparently nobody uses,

Yes, I'd say so. Well, it would help me a lot as he really goes for attitude 90% of the time. If that was fixed, I would have no trouble really using the altitude command instead of going 'flight level' all the time.

 

If it was a command for flight level 40, confirmation would be “40”.

I've tried that one a lot. It never succeeds although the read text is showing my answer being '40'. He sticks to that 'sorry, what did you say' loop or confirms 'ok, flight level (no value)' and nothing happens.

 

MCE reads the transition altitude from a table provided by Travis Guy.

It doesn’t cover the whole world, but it’s very useful.

 

For aircraft that have an SDK like PMDG 737 or iFly 737, MCE will read the transition level or altitude you set in FMC-CDU, as well as V1, VR, V2 and a few other things.

That's a very neat feature indeed.

"

Maybe we should remove the “set attitude mode” command, which apparently nobody uses, and causes more confusion to the speech engine. That should help the “set altitude XXX” commands go through smoothly.

 

MCE reads the transition altitude from a table provided by Travis Guy.

 

It doesn’t cover the whole world, but it’s very useful.

 

For aircraft that have an SDK like PMDG 737 or iFly 737, MCE will read the transition level or altitude you set in FMC-CDU, as well as V1, VR, V2 and a few other things.

 

For other aircraft, you can set the takeoff or landing data (including the transition level or altitude) via the <Monitor> section of the user interface.

 

The data in the <Monitor> section is what’s used for the various callouts."

 

 

gently guys

 

i use "altitude" below the transition level / flight level above .... it is the nomenclature of the real / different QNH's etc.

i use "altitude" below the transition level / flight level above .... it is the nomenclature of the real / different QNH's etc.

 

No worries,

 

Will be removing only the voice command to ask FO to switch "Auto-pilot to Attitude mode" (mainly default aircraft)

gerald

 

thanks ... & i apologise for misreading your notes (read - remove the “set attitude mode” - as altitude).

Watch your attitude, John. No, I mean altitude.