B 777 Normal Procedures
B 777 Normal Procedures
B 777 Normal Procedures
Preflight Summary
1. Electrical Power Up 6. Exterior Inspection
2. Aircraft Documents 7. Preflight Procedure
3. Preliminary Preflight Procedure 8. Takeoff Performance
4. ATIS 9. Briefing
5. CDU Preflight 10. Checklist
* A file containing a list of required manuals/books to be on board needs to be checked. Latest revision file has to be
updated within the past 10 days.
A ADIRU switch - OFF 30 seconds, Verify ON BAT light and OFF light
An All then ON extinguished
Hydraulic quantity
Guards closed
Overhead Maintenance Panel
Lights extinguished
* Verify EICAS memo message PARKING BRAKE SET. Do not assume that the parking brake will prevent airplane
movement. Accumulator pressure can be insufficient.
ATIS
On TAKEOFF REF page, make data entries on page 2/2 before page 1/2.
Exterior Inspection
Preflight Procedure Captain and First Officer
Note: Before performing any preflight procedures, move the FMC selector switch to either L or R,
then back to AUTO. If this cycling is inadvertently overlooked prior to preflight, it can be done in flight
at any time. [Ref: Flight Crew Operation Manual Bulletin (PIA-51) for Un-commanded Autothrottle
Movement During Cruise Flight]
1) PFD:
FMA:
Auto-throttle mode blank
Roll mode TO/GA
Pitch mode TO/GA
AFDS status FLT DIR
3) EICAS Screen:
Non appearance of any of the following Five Messages is a clue that something has been left out
while carrying out the preflight preparation:
Parking Brake
Autobrake
APU
Doors
Seatbelts Sign
4) MFD:
5) FMC
RTE 2 (alternative route, different DEP / RW, or in-flight return route if required)
Check NAV RAD and POS REF Page to clear values if previously entered.
Route Data: W/V and FL Temperature (starting at first waypoint after TOC). Subsequent wind
data should be entered for a change greater than 10 deg or 10 knots and change in cruise
level. Enter temperature changes equal to or greater than 2 deg.
After execution of route, completion of initialization pages and completion of fuelling, enter the
estimated ZFW to check estimated TOGW. Also check the total distance & fuel remaining at
destination on progress page. Cross check it against the CFP.
5. Runway Information:
S Surface Condition
L Lighting
7. SID Procedure:
Transition Altitude
MSA
9. Miscellaneous:
Call out any malfunction or warning and silence the aural warning.
I will reject takeoff for any warning or condition that significantly affects the safety of the flight.
If I call STOP, I will take over control and reject the take off.
If I call GO, you will continue the take off until I say I HAVE CONTROLS.
Load and Trim Sheet
Max allowable difference between AZFW and EZFW is 7000 Kgs before a new trim is required.
th
Ref: OETB 25 September 2008
Last Minute Change (LMC): [Ref: PIA Weight and Balance Booklet Page 00.06]
4 passengers with baggage anywhere and 400 Kg load in any lower hold.
Only ZFW, TOGW and Total SOULS ON BOARD figures have to be revised.
b) If changes on computerized load sheet are more than those specified above, fresh load sheet is
required to be prepared.
c) If last minute changes on Manual load sheet are more than those specified above, follow the detailed
LMC procedure (page 00.06 and 00.07).
FMC figures of Total Fuel, TOGW and Stab Trim will be reconfirmed.
An average of TOCG & ZFWCG will be inserted in the CRUISE CG space on the PERF INIT
page.
If EFB performance calculating speeds are higher, they must be inserted in the FMS.
Before Start Procedure
F/O Do Items
1) Close all the doors and windows and make the departure announcement.
2) Set the CDU.
3) After ATC clearance, set the overhead panel (fuel and hydraulic) and turn on the beacon.
4) Check Recall.
** If the tow bar is connected, do not pressurize the hydraulic systems until the nose gear steering is locked out.
Unwanted tow bar movement can occur. Pressurize the right system first to prevent fluid transfer between systems.
*** Center tank pumps ON if there is more than 4,800 kilograms of fuel in the center tank.
**** For unexpected messages, check the DDG and decide if maintenance is needed.
Captain Do Items
1) Close the window.
2) Set the CDU and MCP.
3) Ground Clearance: Nose gear steering locked out + Hydraulic Pressurization.
4) Set the stabilizer trim.
V2
LNAV
Heading/Track
Altitude
Trim Set
Pushback or Towing Procedure
Captain F/O
Timer **
After Pushback
* Do not hold or turn the nose wheel tiller during pushback or towing. Do not use airplane brakes to stop the airplane
during pushback or towing.
** When commencing pushback CM1 will start the elapsed time function of the clock (Ref: FOM 16.4.3)
Captain F/O
* Auto start does not monitor oil pressure and temperature. Do the ABORTED ENGINE START checklist if there is no oil
pressure indication after the EGT increases.
Note: During or after engine start if there is an alert message then do the respective non-normal checklist and check the
DDG (on ground). After engine start, there is no need to check status messages. Any message that has an adverse affect
on safe continuation of the flight appears as an EICAS alert message.
Before Taxi Procedure
B Briefing
E EICAS and EFB
L Lights
Captain F/O
APU OFF
Transponder As needed
EFB Airport Map Set *** EFB Airport Map Set ***
Taxi Clearance
* After start, captain will ensure removal of all ground connection, display of nose wheel steering bypass pin, and hand
signal (R or L). Taxi will be commenced after announcement of Clear my side by both pilots and Hand signal / by
pass pin sighted.
** To avoid nuisance FLIGHT CONTROLS faults, a complete cycle of the control wheel during the flight control check
should be done slowly (more than approximately 6 seconds) and not combined with the check of the pitch controls.
*** Not to be used as a primary navigation reference. It is designed to aid flight crew positional awareness only.
Before Takeoff Procedure
Engine Warm Up: Engine oil temperature must be above the bottom of the temperature scale. Run
the engines for at least 3 minutes using a thrust setting normally used for taxi operations.
PF PM
Cabin Announcement
EFB Select SID
EFB Select SID
* In case of departure from an airport with surrounding high terrain PM will select TERRAIN on his ND.
Takeoff Procedure
PF PM
Strobe ON
Transponder On (TA/RA)
Announce Takeoff
N1 55% *
TOGA
Verify and Call Check Verify and Call Out FMA Changes
Timer **
VR Call Rotate
1000 Verify climb thrust set & call Check Call CLIMB / CLIMB1 / CLIMB2
3000 Verify Acceleration, Call Flaps ___ Call Speed Checked Flaps ___
By the assumed temperature method when the runway is contaminated (Max T/O, T/O 1 or T/O 2 is allowed).
Wind shear is expected along the take off path (Max T/O thrust is mandatory).
** At the initiation of takeoff roll, CM2 will start the elapsed time function of the clock (Ref: FOM 16.6.3.4)
*** Monitor engine instruments. During strong headwinds, if the thrust levers do not advance to the planned takeoff thrust,
manually advance the thrust levers by 80 knots.
**** After Take off PM will select Turnoff, Nose Landing lights and Taxi light off.
Climb Procedure
1) Transition Altitude
2) Ten Thousand Feet
3) Tilt of weather radar Auto or as required
PF PM
Transition Altitude Set and Cross Check Altimeters
* Maintain a min speed of 15 knots above the min maneuvering speed at all altitudes when airspeed is below 0.82 Mach.
Top of Climb
Effective 22 November 2008, the following provision is applicable in ICAO PANS-OPS Doc. 8168 (within or outside RVSM
airspace): Pilots should use appropriate procedures by which an airplane climbing or descending to an assigned altitude
or flight level, especially with an autopilot engaged, may do so at a rate less than 8 m/s (or 1500 ft/min) throughout the
last 300 m (or 1000 ft) of climb or descent to the assigned altitude or flight level when the pilot is made aware of
another aircraft at or approaching an adjacent altitude or flight level, unless otherwise instructed by ATC. These
procedures are intended to avoid unnecessary airborne collision avoidance system (ACAS II) resolution
advisories in aircraft at or approaching adjacent altitudes or flight levels. For commercial operations, these
procedures should be specified by the operator. Some European States have published regulations in their
Aeronautical Information Publications (AIPs) specifying vertical rates, so it is important to refer to relevant AIPs for
specific information. (Read more: http://www.theairlinepilots.com/forumarchive/quickref/acas.pdf )
PIA FOM - General Flight Rules - 6.5.1 - Level Off: With a high vertical rate, to prevent altitude divergence or
undesirable "g" forces while leveling off, rate of climb/descent to be within 500/1000 ft/min (not to exceed 1500 ft/min) in
RVSM airspace when approaching the selected altitude or when changing flight levels.
Jeppesen - Air Traffic Control - UK Rules and Procedures Maximum Rates of Climb and Descent: Aircraft when
first approaching a cleared flight level and/or when changing flight level in controlled airspace should ensure that the
vertical closure speed is not excessive. It is considered that, with about 1500ft to go to a cleared level, vertical speed
should be reduced to a maximum of 1500ft per minute and ideally to between 1000ft per minute and 500ft per minute.
Cruise Procedure
To begin with:
* For FMC recommended levels. Enter data for at least 3 flight levels:
1) Optimum level 2) One above optimum 3) One below optimum 4) Current level (if different from above)
PF PM
Weather
Review Recall and Review
Alert Messages & Operational Notes Alert Messages & Operational Notes
Verify Approach Ref Page VREF
Autobrakes ***
* The first row of keys on the CDU does it all with NAV RAD being the exception.
** F/O will check fuel predictions for the destination and alternate to estimate any extra holding time available.
*** Normal Brake level selection is level 2. Use Brake level 3 or 4 for wet/contaminated runway.
**** Through ACARS to central dispatch (KHIASPK) for onward dissemination. In case of diversion, inform central
dispatch about the diversion airfield, ETA and fuel (diversion report through ACARS).
***** Just prior to TOD, the PF shall call for the fasten seat belt sign to be cycled twice. This acts as a trigger for the cabin
crew to prepare the cabin and passengers for landing.
Approach Briefing:
2. STAR Procedures:
Transition Level
MSA
3. Approach Procedures:
Transition Level
MSA
Terrain / Obstacles
ATC Procedures
A/C Procedures
S Surface Condition
L Lighting
7. Miscellaneous:
PF PM
CDU PROG Page 1* CDU LEGS Page
Passenger Signs ON
Descent Planning
Losing airspeed can be difficult and may require a level flight segment. For planning purposes, it requires approximately
60 seconds and 6 NM to decelerate from 310 to 250 knots in level flight without speedbrakes. It requires an additional 50
seconds and 4 NM to decelerate to flaps up maneuver speed at average gross weights. Using speedbrakes to aid in
deceleration reduces these times and distances by approximately 50%.
Extend the flaps when in the terminal area and conditions require a reduction in airspeed below flaps up maneuver speed.
Normally select flaps 5 prior to the approach fix going outbound, or just before entering downwind on a visual approach.
When flaps are extended, select the next lower speed just as the additional configuration drag takes effect. Delaying the
speed selection causes an increase in thrust, while selecting the lower speed too quickly causes thrust to decrease, then
increase.
PF PM
Call for Flaps as per the schedule * Set Flaps
On intercept heading, verify:
ILS Frequency (tuned & identified)
LOC and G/S pointers
Arm APP Mode
* Start deceleration from 250 kts to Flaps 5 maneuvering speed with Flaps 5 prior to localizer capture. When Flaps are
extended, select the next lower speed just as the additional configuration drag takes effect.
** LNAV (if used to intercept the final approach course) might parallel the localizer without capturing it.
*** If not in adverse conditions (to conserve fuel or to accommodate ATC speed requests), intercept the glide slope with
gear down and flaps 20 at flaps 20 speed. Approaching 1,000 feet AFE, select landing flaps. For noise sensitive areas,
use the technique above but delay extending the landing gear until 1500 feet AFE.
**** Call if there is no auto callout. Also call 100, 50 and 30 RA in case of no auto voice callout.
Go-Around and Missed Approach Procedure
Minimums:
1. TOGA and Flaps
2. Attitude and Go-around Thrust
+ Climb:
1. Gears Up
400 Feet:
1. Roll Mode
2. Route Tracking
1000 Feet:
1. Acceleration and Flap retraction
2. Climb Mode and Thrust
3. Climb to Missed Approach Altitude
4. Checklist
PF PM
Push TOGA
Set Flaps 20
Call Flaps 20
400 feet RA Select/Verify a Roll Mode** Verify Missed Approach Altitude Set
To prevent an altitude and/or airspeed overshoot, the crew should consider doing one or more of the following:
Press TO/GA switch once to command thrust sufficient for a 2,000 fpm climb rate
If full go-around thrust is used, reduce to climb thrust earlier than normal
Disconnect the AFDS and complete the level off manually if there is a possibility of an overshoot
If autothrottle is not available, use manual thrust control to manage speed and prevent flap overspeed.
If a go-around is initiated after touchdown but before thrust reverser selection, auto speedbrakes retract and autobrakes
disarm as thrust levers are advanced. The F/D go-around mode will not be available until go-around is selected after
becoming airborne.
Once reverse thrust is initiated following touchdown, a full stop landing must be made.
Non-ILS Approaches
1. Setting up the Approach
Whenever constant angle approaches are available in the FMC data base, they will be flown using VNAV PATH. VNAV
should be used only for approaches that have one of the following features:
A published GP Angle on the LEGS page for the final approach segment
An RWxx waypoint coincident with the approach end of the runway
A missed approach waypoint before the approach end of the runway, (e.g.,MXxx).
These features permit construction of a normal glide path. VOR approaches with the missed approach point on the LEGS
page beyond the runway threshold and circling only approaches do not have these features. Do not manually build the
approach or add waypoints to the procedure (see on approach logic FCOM 11.31.30). For procedures where both the
FAF and FACF are coded with at or above altitude constraints, the crew should consider revising the FACF altitude
constraint to at (hard constraint). This enables a shallower path before the FAF, permitting a normal deceleration for
flap and gear extension. When appropriate, make cold temperature altitude corrections by applying a correction from
an approved table to the waypoint altitude constraints. If required to use MDA(H) for the approach minimum altitude, the
barometric minimums selector should be set at MDA + 50 feet to ensure that if a missed approach is initiated, descent
below the MDA(H) does not occur during the missed approach. Jeppesen will publish DA(H) instead of MDA(H) for CDFA
approaches and will not use an add-on when publishing a DA(H). To use or not use an add-on is still the operators
responsibility.
Where constant angle approaches are not available, an overlay approach procedure may be used, if available. Another
approach having the same plan view may be selected. For example, an ILS procedure might be selected if the plan view
(route) is identical to an NDB approach. In this case, waypoint altitudes must be checked and modified as required. When
an approach is flown by this overlay method, raw data should be monitored throughout the approach to assure obstacle
clearance. Note: If an NDB approach for the desired runway is in the database, an overlay approach should not be used.
When no procedure is available from the FMC arrival page, approaches may be carried out by selecting frequency &
course in the NAV radio page and utilizing HDG SEL/TRK SEL with VS/FPA.
2. RNP Requirement
Approach Type RNP
NDB, NDB/DME 0.6 NM
VOR, VOR/DME 0.5 NM
RNAV 0.5 NM
RNAV (GPS)/(GNSS) 0.3 NM
Push the POS switch on the EFIS control panel and compare the displayed raw data with the navaid symbols on the
map e.g. the VOR radials and raw DME data should overlay the VOR/DME stations shown on the MAP and the GPS
position symbol should nearly coincide with the tip of the airplane symbol (FMC position).
Display the VOR and/or ADF pointers on the map display and use them to verify your position relative to the map
display.
Compare airplane position on the map with ILS, VOR, DME, and ADF systems to detect possible map shift errors.
Instrument Approach using VNAV:
Approximately 300 feet above the MDA(H), select the missed approach altitude. This is done to use the guidance of the
altitude range arc during the approach and to prevent altitude capture and destabilizing the approach. Unlike an approach
using VNAV, the occurrence of VNAV ALT is not an issue. Since there is no below path alerting, keeping the MDA(H) set
as long as possible is recommended to help prevent inadvertent descent below MDA(H).
Leaving the MDA(H), disengage the autopilot. Turn both F/Ds OFF, then place the PMs F/D ON. This eliminates
unwanted commands for the PF and allows continued F/D guidance for the PM in the event of a go-around when pitch or
roll mode is changed.
Circling Approach:
Visual Pattern:
Landing Roll Procedure
1) Speedbrakes
2) Autobrakes
3) Reversers
4) 60 Knots
PF PM
Call 60 Knots
Reverse Idle
PF PM
APU Start
Autobrake Off
Flaps UP
Transponder As Required
Engine cool down: Run the engines for at least 3 minutes. Use a thrust setting normally used for taxi operations.
Shutdown Procedure
Capt F/O
Cabin Announcement
Seatbelts OFF
Transponder STBY
** Prior to engine shutdown ensure APU RUNNING message on EICAS or availability of Ground power.
*** Depressurize the right system last to prevent fluid transfer between systems.
**** Disregard EICAS alert and status messages displayed during the PFC self test after hydraulic shutdown. Wait
approximately 3 minutes after HYD PRESS SYS L+C+R message is shown before recording status and alert messages in
the maintenance log.
***** APU OFF if transit time is more than 1hr 30min unless there is an airport restriction.
Secure Procedure
Capt F/O
Disclaimer: "B777 Normal Procedures" are personal notes of the undersigned. These notes do not sanction any pilot to
violate his/her Company's Standard Operating Procedures, Aircraft Manuals or Manufacturer's Recommendations.
Anyone intending to use these notes should provide* an email address so that he/she can be informed about significant
changes or corrections in this article.
* www.TheAirlinePilots.com/b777articleupdatenotification.htm