Compare Airbus vs Boeing cockpit callouts, including take-off, FMA, ECAM/EICAS, minimums and why Airbus says RETARD before touchdown.
In real-world aviation, Airbus and Boeing cockpit callouts differ mainly in wording, automation philosophy and the cues crews monitor, not in their safety purpose. Airbus crews use Airbus FMA terms, thrust-detent calls and ECAM actions; Boeing crews use Boeing FMA/MCP terms, moving-thrust-lever cues and, on equipped types, EICAS messages. Operator SOPs control the exact script.
Three things are often grouped together as callouts: words spoken by pilots, automated altitude or mode announcements, and warning-system voices. The aircraft manufacturer strongly influences the latter two, while each airline or operator determines most crew-spoken calls.
Which Airbus and Boeing callouts are genuinely different?
The clearest differences are the aircraft-specific mode and alert terms; fundamental operational calls such as V1, rotate and gear up remain similar. Our system-by-system comparison of the A320 and 737 explains the cockpit philosophies behind these differences.
| Situation | Typical Airbus cue | Typical Boeing cue |
|---|---|---|
| Flight-guidance modes | Crews monitor Airbus FMA terms such as SRS, NAV, CLB, OP CLB, FINAL APP and A/THR. They also distinguish managed from selected guidance. | Terms can include TO/GA, LNAV, VNAV, LVL CHG or FLCH, APP, N1 and THR REF, depending on the Boeing model. |
| Take-off speed check | Many Airbus SOPs use a 100 knots cross-check. | Many Boeing SOPs use an 80 knots cross-check. This is common rather than universal. |
| Thrust | Airbus thrust levers remain in detents such as FLEX/MCT, TOGA, CL and IDLE. Crews verify the commanded mode on the FMA. | Autothrottles physically move the thrust levers on many Boeing types. Crews monitor the relevant N1, THR REF or speed mode. |
| Landing flare | Many Airbus types provide the automated RETARD prompt. | Boeing autothrottle systems may reduce thrust automatically, but generally do not provide an equivalent spoken RETARD prompt. |
| Abnormal conditions | ECAM presents the failure and, where applicable, sequenced actions. Crew calls often refer directly to the ECAM title or action. | EICAS-equipped aircraft use EICAS messages followed by the applicable procedure. The 737 is a major exception: it does not have EICAS. |
Control transfer also sounds different. Airbus sidesticks are not mechanically linked, so the aircraft can announce DUAL INPUT or PRIORITY LEFT/PRIORITY RIGHT. Conventional Boeing yokes are generally linked, although pilots must still make an unambiguous verbal handover.
Mode names should not be translated casually between manufacturers. Airbus managed climb and Boeing VNAV may serve comparable purposes, but they are not interchangeable callouts. Our guide to the A320’s controls, FMA and displays provides the Airbus context for these terms.
Why does Airbus say RETARD during landing?
The Airbus RETARD callout reminds the pilot to move the fixed thrust levers to IDLE during the flare. On an A320-family manual landing it is normally heard at about 20 feet radio altitude, although timing can differ during autoland and between Airbus types or configurations.
RETARD does not mean select reverse thrust, reject the landing or pull the levers back prematurely. Reverse is selected only after touchdown. On many Boeing aircraft, the autothrottle drives the thrust levers rearwards during the flare, so a matching spoken reminder is generally unnecessary.
Are take-off and approach callouts standard?
No single Airbus or Boeing script applies to every airline, model and flight. Manufacturer procedures establish the system language, but operator SOPs decide the precise wording, trigger point and which pilot responds.
A typical shared take-off sequence contains:
- A thrust-setting or thrust-verification call
- An 80-knot or 100-knot cross-check
- V1 and rotate
- Positive climb or positive rate, followed by gear up
Approach calls commonly cover the operator’s stabilised-approach gate, radio altitude, decision minimum and the decision to land or go around. Automated wording such as hundred above, approaching minimums, minimum or minimums depends on the installed equipment and its configuration. These differences do not change ATC phraseology, which is governed by local aviation procedures rather than the aircraft manufacturer.
How should simulator pilots use authentic callouts?
Authentic simulator callouts come from matching one aircraft variant with one coherent operating procedure, rather than mixing familiar phrases from several cockpits.
- Choose the exact aircraft type. A 737, 777 and 787 do not share one complete Boeing script; nor do all Airbus families.
- Separate crew calls from automated voices. Decide which words belong to the pilot flying, pilot monitoring and aircraft warning system.
- Watch the FMA. A spoken mode that does not match the annunciation is wrong, however convincing it sounds.
- Use one SOP consistently. Keep its speed checks, stabilised-approach calls and minimums wording together.
- Keep callouts beside, not inside, the checklist. The normal A320 checklist sequence and cockpit flow show where the two processes meet without treating them as the same task.
A mistake we see constantly is using generic Boeing language in an Airbus cockpit: calling VNAV instead of an Airbus managed mode, referring to the FCU as the MCP, or calling EICAS on a 737. Another is treating every automated voice as an instruction; altitude announcements provide awareness, while warnings and SOP decision calls require the appropriate crew response.