Callouts & Communications Flashcards

Review ATI Callouts (40 cards)

1
Q

When any Master Caution or Master Warning light illuminates what phrase must be said, followed by the EICAS message displayed?

A

Master Caution Reset “EICAS MSG”
Master Warning Reset “EICAS MSG”

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What is an example of a thrust settings callout?

A

Set Go-Around Thrust

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

When passing controls the callout’s are?

A

“You have control”
Pilot Taking the controls responds with:
“I have control”

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

When passing responsibility for ATC communications the callouts are?

A

You have ATC
Pilot taking ATC communications responds with: I have ATC

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

FMA recognition callouts occur for?

A

For all changes or expected changes

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Flap speed limits are acknowledged prior to flap handle movement. A general callout of what?

A

Speed Checks, Flaps 1, 5, etc.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Approaching a new altitude, a general callout of what is made by the PM and acknowledged by the PF?

A

One thousand to level

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

What are the two callouts when a new altitude is dialed into the MCP?

A

The PM points to and verbally confirms the altitude “Flight Level ____ set”
The PF points to the MCP and verbally confirms the correct altitude “Flight Level ____ checked”

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

What should be said to ground personal during pushback when both engines are started?

A

“Two normal starts”

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

For lateral route modification where we are in heading mode the PM states”

A

LNAV Available

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

To confirm a CDU modification the PF states?

A

Execute

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

The callout “CHECK” means?

A

Distinctly visible and verified.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

The callout “Roger” means?

A

I understand.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

In the event the PM does not make the callouts who should?

A

The PF should accomplish the callouts.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

What callout is made when the LNAV or Localizer is Captured?

A

Localizer Capture
LNAV Capture

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

What callout is made when the LNAV or Localizer is moving toward Capture?

A

Localizer Alive
Course Alive

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

What callout is made approximately 2NM from the FAF on a LNAV or Localizer approach?

18
Q

If the “Landing” Callout is made, does the PM still need to make all the appropriate callouts to minimums?

A

No, all callouts after can be omitted.

19
Q

When completing non-normal procedures, the PF should call “Check EICAS Messages”. What should the PM say / do?

A

Read aloud any current messages and address whether they are related to the non-normal issue and if everything is addressed say “Cancel Messages”

20
Q

“MISSED APPROACH”
Decision -

A

PF: Push either TOGA switch
“GO-AROUND”
“SET GO-AROUND THRUST”
“FLAPS 20” (or FLAPS 5 if single engine)

PM: Confirm GA FMA pitch
Set commanded flaps:
“FLAPS 20” or “FLAPS 5”

Verify thrust:
“GO-AROUND THRUST SET”

21
Q

“Missed Approach”
After liftoff -

A

After liftoff:
PM: “POSITIVE RATE”
PF: “GEAR UP, CHECK MISSED APPROACH ALTITUDE”

22
Q

“Missed Approach”
At or above 400’ AFE -

400’: lateral mode Trigger

A

At or above 400’ AFE:
PF: “LNAV” or “HEADING SELECT”

23
Q

“Missed Approach”
At or above 1,000’ AFE -

1,000’: vertical mode Trigger

A

At or above 1,000’ AFE:
PF: “SET SPEED REF ___”

24
Q

“Missed Approach”
At Flaps UP and VREF 30 +80 -

A

At Flaps UP and VREF 30 +80:
PF: “VNAV” or “FLIGHT LEVEL CHANGE”
“SET CLIMB THRUST” (or “SET MAX CONTINUOUS THRUST” if single engine)

25
"Engine Failure on Takeoff" Before VR -
Before VR: PF: “N1” or “EPR” PM: “THRUST SET” PM: “80 KNOTS” PF: “CHECKED” PM: “V1” PM: “ROTATE” (unless PF calls it)
26
"Engine Failure on Takeoff " After liftoff -
After liftoff: PM: “POSITIVE RATE” PF: “GEAR UP”
27
"Engine Failure on Takeoff " At 400’ AFE - | 400’: lateral mode Trigger
At 400’ AFE: PF: “HDG SELECT” or “LNAV”
28
"Engine Failure on Takeoff " At 1,000’ AFE or acceleration height - | 1,000’: vertical mode (VS) Trigger
At 1,000’ AFE or acceleration height: PF: “SET VERTICAL SPEED ___” (0 to +200 FPM)
29
"Engine Failure on Takeoff " Cleanup At VREF/Acceleration Height -
At VREF 30 +20: PF: “FLAPS 5” PM: “SPEED CHECK, FLAPS 5” At VREF 30 +40: PF: “FLAPS 1” PM: “SPEED CHECK, FLAPS 1” At VREF 30 +60: PF: “FLAPS UP” PM: “SPEED CHECK, FLAPS UP”
30
"Engine Failure on Takeoff" At VREF 30 +80 - | Clean Aircraft Trigger
At VREF 30 +80: PF: “FLIGHT LEVEL CHANGE, SET Max Continuous Thrust” Optional: Engage autopilot if stable PF: “ENGINE STATUS”
31
What’s the speed target in Engine Failure vs. Go-Around?
Engine Failure: Maintain V2 to V2+15 Go-Around: Climb as flaps retract, then set speed ref at 1000’
32
How is climb thrust managed in Engine Failure vs. Go-Around?
Engine Failure: Use MCP (approx 80% N1) at acceleration height Go-Around: PF calls “SET CLIMB THRUST” or “SET MAX CONTINUOUS THRUST” at flaps up
33
Is there an immediate checklist in either procedure (Engine Failure vs. Go-Around)?
Engine Failure: Yes, call for appropriate Non-Normal Checklist and then After Take-off Checklist Go-Around: After Take-off Checklist unless a mechanical issued caused the go-around.
34
Here are some memory anchors for Engine Failure vs. Go-Around:
Engine Failure: Comes after V1, so no abort. Emphasis is on stability, minimum bank, and V2 profile. PF is mostly quiet until 400’ (rotates, commands gear/flaps). Go-Around: Is a commanded escape, so PF drives the pace early: “GO-AROUND,” “THRUST,” “FLAPS.” PM follows and verifies. Think of it as “PF in control” mode.
35
How is climb thrust managed in an Engine Failure on Takeoff?
PF manually reduces thrust after reaching MCP altitude Target: Maintain approx Vref30 + 80, which aligns with ~80% N1 No VNAV or FLCH call; hand-flown or manually managed
36
How is climb thrust managed in a Go-Around?
PF calls: “SET CLIMB THRUST” or “SET MAX CONTINUOUS THRUST” (if SE) Triggered after reaching Flaps Up and Vref + 80 May follow with a call for “VNAV” or “FLCH” to resume vertical profile
37
How is thrust adjusted manually in both procedures (Engine Failure vs. Go-Around)?
Engine Failure: manually reduced to stabilize climb speed Go-Around: thrust is set by PM per PF’s callout, no fine-tuning unless needed
38
What's the final climb speed target in each (Engine Failure vs. Go-Around)?
Engine Failure: Vref30 + 80 (approx), aiming for a conservative single-engine climb Go-Around: Vref + 80 (per flap retraction schedule), then normal climb profile resumes
39
# Engine Failure vs. Go-Around Initial Aircraft State | Mentally link each procedure to the aircraft’s initial configuration
*Config Before Event:* *Engine Failure* Takeoff Thrust already set *Missed Approach* idle or partial thrust *Flaps* Takeoff setting (5, 15) Landing configuration (25/30) *Gear* Down for both
40
# Engine Failure vs. Go-Around Autopilot and FD Usage | Pilots often stumble on when to engage automation.
Engine Failure: Hand-fly until stable, then use FD/AP only if trimmed, with stable modes. Go-Around: FD engaged; AP disengaged manually or automatically. Re-engage when ready. | Memorize by linking autopilot use to “stability” not “altitude.”