Phases Of Flight: Cruise And Descent Flashcards
How do we do descent planning?
This basically involves the three times tables, plus a distance added to sort your bits and bobs out.
- Above FL100, use 3x altitude TO LOSE, plus 10nm.
- Below FL100, use 3x altitude TO LOSE plus 5nm.
- Plan to Slow to 210 around 6000-4000’ (ie around 25nm)
- Slow to flap 5 speed before 10nm prior to descent on the glide slope and 3000’ or plat alt.
NOTE SPEED LIMIT ANY PROCEDURAL APPROACH IS 185kts.
What happens while in the cruise?
We consider now what we are going to do next.
Firstly the PM will get the ATIS. He will discuss this with the PF and the PF will use the information to form an approach brief, given in a moment.
With the ATIS, the PM can set this on the stby alt. He can also set the performance data in the FMC and work out VRef.
The PF then can make a passenger brief, and then setup the aircraft for an approach, using the 6 Bs.
Bugs Bug Boxes Bearings Brakes Brief.
The PF then requests the descent checklist.
What happens when ready to begin the descent from cruise? Stop at the descent checks.
Descending, the PM calls passing 100.
The PF responds as normal, “checked, altimeters set, passing FL100, MSA _ft.”
The PM now begins to prep for descent. He checks:
Fixed landing lights ON
seatbelt signs ON
“Cabin crew prepare for landing”
When cleared to an altitude, we set QNH and crosscheck and report alt passing. Update the MCP as ness.
Continue with the SEVEN Bs (mostly checked in cruise)
Bugs bug boxes bearings brakes briefing BIRDS, meaning how are the cabin crew getting on?
What happens from the moment you are descending deem yourselves ready and start the approach checks?
PF calls “Approach Checklist”
PM Read and do “Approach Checklist complete”
PF Call for flap extension as required and set appropriate speed if AP engaged.
PM Respond to call, check speed, position Flap Lever as directed and monitor Flap extension (Sets Speed Bug when AP not engaged)
Call for or select FCU modes as required: “Heading”, “Arm VOR/LOC”, “Arm Approach”
Prior to LOC Capture: Both pilots identify Approach Aids
Whoever first hears rad alt alive calls it and the other responds checked.
Further descent from localiser established.
PM When localiser alive: “Localiser alive”
PF “Checked” and call for or select Heading Bug to R/W hdg.
When localiser established & cleared to descend on the Glideslope or cleared for approach: APP Arm
PM Memory items: Retractable Ldg Lights On When Glideslope alive: “Glideslope alive”
PF “Checked” 2 nm to ‘D’: “Gear Down, Flaps 15, Landing Checklist down to Flaps” and selects / calls for appropriate speed
PM Respond “Gear Down, Flap 15”, select Gear and Flap and complete memory items:
Start Switches On
Speedbrake Arm
Then Reads checklist and PF responds, followed by “Holding at Flaps”
PF 1 nm to ‘D’: “Flap 30, ___kts” (state Vref+5 speed) At G/S intercept set MAA in MCP Alt window “Flap 30, Green Light” Review GA actions when time allows
PM When flaps set report checklist complete. Report 4d and height. Report 500 if stable. Report minimums.
Landing procedure
PM At 100 above: Look for Visual Reference and call “One hundred above” Decision alt: “Minimums”
PF “Checked” Look for visual reference and call “Continue” or “Go-around, Flap 15” Disconnect the A/P and A/T no later than 135ft agl for a manual landing
After touchdown select Idle Reverse Thrust unless runway / conditions require up to 74% N1.
PM “Speedbrakes up”
Call “60 kts”
Capt. should plan to take control at normal taxi speed and as the A/C approaches R/W turn-off: “I have control”
Go around procedure:
Decision to go around made:
PF “Go around flap 15” presses TOGA switch, and rotates to initial attitude 15 degrees.
PM “positive climb”
PF Gear Up
PM checks the GA thrust.
400’ PF “HDG SEL” and presses AP HDG SEL.
1000 AP B to CMD. (This reengages the speed window control)
1500 CLEAN SPEED
Flap 5 at VRef+15
Flap 1 at 170
Flap up at 190. Report flaps up no lights.
Complete an after take off checklist.
