A320 Callouts
Joined: Jun 2006
Posts: 201
Likes: 53
From: FLXXX
The example from FCOM only relates to Altitude and FL but why not speed? For example I call “Speed 250 blue” or “Heading 180 blue”. Also “Speed 250 magenta”. I understand the Guidance mode is either Selected or Managed however there is no Standard Call-out for “Selected”, “Managed” relates to a request from the PF to PM to push a knob on the FCU when the AP is off. The only way we can cross check the change in guidance mode is by the colour.
Joined: Mar 2012
Posts: 2,605
Likes: 154
From: Having a margarita on the beach
The example from FCOM only relates to Altitude and FL but why not speed? For example I call “Speed 250 blue” or “Heading 180 blue”. Also “Speed 250 magenta”. I understand the Guidance mode is either Selected or Managed however there is no Standard Call-out for “Selected”, “Managed” relates to a request from the PF to PM to push a knob on the FCU when the AP is off. The only way we can cross check the change in guidance mode is by the colour.
MANAGE/PULLThe “MANAGE” command means pushing an FCU knob to engage, or arm, a managed mode or target.
The “PULL” command means pulling an FCU knob to engage, a selected mode or target. Example:
- “PULL HDG 090” (heading knob is turned and pulled).
- “MANAGE” NAV (heading knob is pushed).
- “FL 190 PULL” (altitude knob is turned and pulled).
- “FL 190 MANAGE” (altitude knob is turned and pushed).
- PULL SPEED 250 KNOTS (speed knob is turned and pulled).
- MANAGE SPEED (speed knob is pushed).
The above are the commands that would be made by the PF to the PM.
Regarding the heading, it can only be “blue” so no need to verbalise the colour.
Regarding the speed, if flying with AP ON and going selected (e.g. for turbulence, energy management, Atc, etc..) the call-out is simply “speed xxx”. When going back to managed it will be simply “speed managed”.
Specific operators policies may vary of course.
Joined: Dec 2020
Posts: 160
Likes: 123
From: nowhere
as per FCOM:
”All actions performed on the FCU and MCDU must be checked on the PFD and ND (eg.: “FL350 blue”, “FL 200 magenta”).
Why limit ‘blue’ or ‘magenta’ to just altitude? Because the FCOM only gave altitude as the example? The blue / magenta philosophy extends to speed / Mach also. The key words in the above FCOM extract are ‘all’ and ‘eg.’ That is why you call ’blue’ or ‘magenta’ after your speed ie ‘speed 250 blue’.
Last edited by Jester64; 13th October 2024 at 01:35.
Joined: Mar 2012
Posts: 2,605
Likes: 154
From: Having a margarita on the beach
That is what is commonly said on the line, but it is not entirely correct…
as per FCOM:
”All actions performed on the FCU and MCDU must be checked on the PFD and ND (eg.: “FL350 blue”, “FL 200 magenta”).
Why limit ‘blue’ or ‘magenta’ to just altitude? Because the FCOM only gave altitude as the example? The blue / magenta philosophy extends to speed / Mach also. The key words in the above FCOM extract are ‘all’ and ‘eg.’ That is why you call ’blue’ or ‘magenta’ after your speed ie ‘speed 250 blue’.
as per FCOM:
”All actions performed on the FCU and MCDU must be checked on the PFD and ND (eg.: “FL350 blue”, “FL 200 magenta”).
Why limit ‘blue’ or ‘magenta’ to just altitude? Because the FCOM only gave altitude as the example? The blue / magenta philosophy extends to speed / Mach also. The key words in the above FCOM extract are ‘all’ and ‘eg.’ That is why you call ’blue’ or ‘magenta’ after your speed ie ‘speed 250 blue’.
You will not find anywhere in Airbus documentation "speed 250 blue" or so, because the speed simply does not change color, the speed target does. Same concept for the heading or track.
When You select an altitude or a FL, the selected value itself will be either blue or magenta.
Joined: Jun 2006
Posts: 201
Likes: 53
From: FLXXX
The only way of seeing the Guidance Mode change is through the colour of the value or target. Many pilots I’ve flown with will manipulate the speed/heading knob on the FCU and call “selected” and not actually pulled it, so they’ve set the value but not confirmed it on the PFD.
Joined: Mar 2012
Posts: 2,605
Likes: 154
From: Having a margarita on the beach
The only way of seeing the Guidance Mode change is through the colour of the value or target. Many pilots I’ve flown with will manipulate the speed/heading knob on the FCU and call “selected” and not actually pulled it, so they’ve set the value but not confirmed it on the PFD.
Joined: Dec 2020
Posts: 160
Likes: 123
From: nowhere
Joined: Dec 2020
Posts: 160
Likes: 123
From: nowhere
I have no doubt it’s what’s said in your company, as it is what’s said generally. The question being raised though, is what is actually correct based on correct interpretation of the Airbus FCOM?
Joined: Jul 2006
Posts: 1,100
Likes: 111
From: Somewhere over the rainbow
The FCOM tells you that
My understanding and this is how the training department interprets in my outfit: This is just a visual check. They don’t ask you to announce the color. If we are clear to climb to a new altitude or speed, the PF will announce “Thrust Climb, Climb, Alt blue, FL330”. If it’s a speed, he will announce “ speed managed”(if previously in selected speed)or “speed pull 270 kt”( or “speed 270 kt “ if already in selected mode at a different speed )or just “speed pull” if you just pull the speed and no change is made to the speed)
But the FCOM states that:
Only These items are mandatory call out. The altitude value and speed are not considered part of the FMA.
We follow the FCOM. We just have a note in our FOM stating that it’s not required to read the color of the number.
“All actions performed on the FCU and MCDU must be checked on the PFD and ND ( eg.:,”FL350 blue”, “ FL200 magenta”.
But the FCOM states that:
the PF should call out any FMA change., -All armed mode with the associated color and all active mode without the associated color.
We follow the FCOM. We just have a note in our FOM stating that it’s not required to read the color of the number.
Joined: Mar 2012
Posts: 2,605
Likes: 154
From: Having a margarita on the beach
I will give You one example: at acceleration altitude, the speed target jumps from the actual SRS speed target (V2+10) to the next climb speed, depending on SID constraints, ECON climb, etc..
There is no mentioning of the speed, which could be 250 magenta, 200 magenta (e.g. SID constraint), 220 blue (e.g. for a pilot pre-selected speed) and so on.
There is no mentioning of the speed, which could be 250 magenta, 200 magenta (e.g. SID constraint), 220 blue (e.g. for a pilot pre-selected speed) and so on.
Joined: Dec 2020
Posts: 160
Likes: 123
From: nowhere
I will give You one example: at acceleration altitude, the speed target jumps from the actual SRS speed target (V2+10) to the next climb speed, depending on SID constraints, ECON climb, etc..
There is no mentioning of the speed, which could be 250 magenta, 200 magenta (e.g. SID constraint), 220 blue (e.g. for a pilot pre-selected speed) and so on.
There is no mentioning of the speed, which could be 250 magenta, 200 magenta (e.g. SID constraint), 220 blue (e.g. for a pilot pre-selected speed) and so on.
Joined: Dec 2020
Posts: 160
Likes: 123
From: nowhere
