Beruflich Dokumente
Kultur Dokumente
For The
Version 2.0
2 November 2015
http://www.iflysimsoft.com/
Contents
Introduction
Preparation
Instrument Panels
16
22
25
26
Preflight Procedure
36
44
Pushback Procedure
46
47
48
50
Takeoff Procedure
51
Climb Procedure
55
Cruise Procedure
62
Descent Procedure
69
77
87
Shutdown Procedure
88
Secure Procedure
90
Introduction
This flight tutorial is only for the iFly Jets: The 747-400. The purpose of the tutorial is to help users
familiarize themselves with the iFly Jets: The 747-400 aircraft simulation by leading them through the
steps required to simulate a scheduled airline flight. The separate Aircraft Operating Manual (AOM)
covers all onboard systems in great detail and should be studied to gain a complete understanding of
the simulation. This tutorial is suitable for those who can already successfully operate the default
aircraft provided by Microsoft Flight Simulator, but are unfamiliar with complex simulations. Even if you
are a Flight Simulator veteran, it is recommended that you take the time to read through this tutorial as
the iFly simulation closely models the real Boeing 747-400. Basic aviation knowledge is presumed.
Users should read through this tutorial prior to flight and keep it close at hand during the flight.
Never hesitate to pause Flight Simulator in order to understand the procedures described in this
tutorial.
After completing this tutorial and studying the AOM, users should be able to operate all systems of the
iFly Jets: The 747-400 much like the real aircraft is operated.
THIS TUTORIAL IS ONLY FOR THE IFLY JETS: THE 747-400, AN ADD-ON FOR MICROSOFT
FLIGHT SIMULATOR. IT IS STRICTLY FORBIDDEN TO APPLY ANY INSTRUCTIONS CONTAINED
IN THIS TUTORIAL TO ANY SITUATION WHICH INVOLVES REAL AVIATION.
The flight used as the example in this tutorial is from London Heathrow Airport (EGLL) to San Francisco
International Airport (KSFO). The situation starts with a cold and dark cockpit. All screenshots are from
the FS9 version of the aircraft.
The tutorial consists of aircraft set up, flight plan and the take off, climb, cruise, descent, approach and
landing phases of a simulated airline flight. Many aspects of the separate AOM are not part of the
tutorial. However, the information may be applied in any simulated flight.
The following sceneries are used for this tutorial:
London Heathrow: Aerosoft
San Francisco International: Fly Tampa
Freeware files for both airports may be available from various community websites and there are
several commercial sceneries which could increase your enjoyment of the simulation.
Special thanks to Steve Hall for serving as check pilot and freely contributing his professional expertise,
which kept this tutorial on course. Thanks to the entire iFly 747-400 Team for reviewing this document.
Note: The screenshots in this tutorial were gathered over several months and show software
under test. There may be slight differences, including airspeed, between the tutorial
screenshots and what you see during your tutorial flight. These differences are not significant.
IMPORTANT: Please see the Tutorial Addendum for additional information concerning proper
procedure for operating the simulation.
Preparation
In order to verify that the status of Flight Simulator is the same as its status in this tutorial, some
configuration by you is necessary. Prior to running FS, you must configure the aircrafts weight and other
parameters.
The Configuration Tool utility is used to change multiple items involved in aircraft setup. For this tutorial,
the default weights must be changed. Start the Configuration Tool for the 747-400 and, as shown below:
-
NOTE: All iFly 747 models MUST be configured with this tool. Do not use third party tools for
configuration.
See the next page for the aft part of the passenger cabin.
Do not forget to click Update after entering the passenger and cargo load.
Fuel Configuration page:
Enter 129,514 kgs in the Set desired total fuel field. The Configuration Tool will automatically distribute
the fuel load among the tanks as required by the fuel logic.
10
Click DONE then OK on the popup and you will return to the MyFleet page with a configured aircraft.
Click Exit on that page.
Styles may also be set from the FS menu bar. Choose iFlyiFly Jets: The 747-400Styles. Set
the Unit to Metric System and the remainder of the styles as shown above.
11
If the metric unit is not selected the input of data when configuring the CDU will trigger errors.
Configure FS and then select the iFly 747-400
Now start Flight Simulator with the default flight with the engine running and go to the Settings International page and set Metric (altimeter in feet) as Units of measure:
International, Unit of Measure, MUST be set to Metric (altimeter in feet) for this tutorial.
NOTE: FSX and P3D users need to select Hybrid (feet, milibars) on the SETTINGS
GENERAL page.
Next select Create A Flight then click Change Location. Then on the Go To Airport page, set
London Heathrow (EGLL) as the location and Gate 340 as the position. If you are using default FS2004
scenery, select any Heavy gate.
12
Then click OK to go back to the Create a Flight page then click Select Aircraft. Select iFly Developer
Team as the Aircraft manufacturer and the iFly 747-400 GE with the monitor you are using as the
Aircraft model. Normal screen is suitable for 1280x1024 or similar displays, and Wide screen is for
1680x1050 or similar displays.
13
Click OK and you will back to the Create A Flight page. Then click Selected Weather and on the
WEATHER tab select Clear Skies as the Weather theme. This will clear the weather and set the
atmospheric pressure to 1013Hpa/29.92mb.
14
Click Fly Now and you are at the gate with a Cold and Dark aircraft:
NOTE: The tutorial flight is 4,779NM, a trip which takes around ten hours at normal FS speed. You
may want to depart EGLL at about 1300 hours local time in order to arrive at KSFO while it is
still daylight on the West coast of the U.S.
15
Instrument Panels
Now is the time to become familiar with our office, the 747-400 flight deck. For easier explanation,
each panel is identified and that information will be used during explanations in later sections of this
tutorial.
Each of the 2D panels may be selected using the Panel Selector positioned at the upper left corner of
the monitor.
OVERHEAD
GLARESHIELD
CENTER FORWARD
LEFT FORWARD
RIGHT FORWARD
CONTROL STAND
FORWARD AISLE
STAND
NOTE: The OVERHEAD MAINTENANCE Panel (iFly AFT OVHD) is not shown above, but is included
in the close up panel screenshots which follow.
16
LEFT
CENTER
RIGHT
17
18
GLARESHIELD PANEL
First Officer
Captain
19
20
21
Now the cockpit has electric power supplied by the batteries only. Needless to say, the batteries can
support the system only for a short time. Before connecting to any exterior power or APU power, we
should check the status of the hydraulic system, windshield wipers, flaps and the landing gear, making
sure that all controls and switches are in the correct position. Now close the FWD OVHD panel using
the Panel Selector and then select the main panel.
6. Now close the FWD OVHD panel and come back to the
main panel. On the Center Instrument panel check the
landing gear lever and verify that it is positioned at DN.
7. Verify that the green DOWN indicator is displayed on
the upper EICAS. The green indicator means that the
landing gear is down and locked. If the landing gear is
not down and locked, or is in disagreement with the
landing gear levers position, a red indicator will
illuminate.
22
Now we have finished the checks before applying external or APU power. Either can provide sufficient
electric power to the aircraft. In order to explain how to apply these two electric power sources, we will
first connect external power, then APU power, and then disconnect external power.
Connecting external power:
8. In FS, no ground crew will bring power to the aircraft, so
we can only simulate this process. First, verify that the
aircraft is not moving in the parking area. Open the THR
panel using the Panel Selector and confirm that the Park
Brake lever is pulled up. Then close the throttle panel.
We have now successfully connected external power to the aircraft. Next we will start the APU. It is OK
to have only the exterior power supply connected and carry out the procedures explained later in this
tutorial without starting the APU. However, in order to explain in detail the functionality of every device,
we will start APU. If you do not want to start APU, the following steps can be skipped and you can go
directly to the Preliminary Preflight Procedure section.
23
All following procedures assume completion of the Electrical Power Up Supplementary Procedure.
24
C.
25
1L
1R
2L
2R
3L
3R
4L
4R
5L
5R
6L
6R
26
27
28
29
7. We will enter the KSFO arrival procedure and runway later while in flight. Flight crews are
seldom certain of this information until close to starting the descent and the arrival runway is
known.
30
31
32
33
34
NOTE: All aircraft performance data must be Entered and Executed in order for
the system to correctly draw the route on the ND.
NOTE: See the iFly Aircraft Operating Manual (AOM) for much more detail on the FMS/CDU.
35
Preflight Procedure
IMPORTANT NOTE: This procedure presumes that the Supplementary Electrical Power Up Procedure
was accomplished.
36
37
38
39
40
34.
THR PANEL
36.
41
THR PANEL
42
43
THR PANEL
44
10.
11.
BEFORE START
Flight Deck Door.Closed and Locked
Passenger Signs....AUTO
MCP.V2,HDG,ALT SET
Takeoff speeds...SET
CDU Preflight..Completed
Trim..SET
Taxi and takeoff briefings..Completed
Beacon.BOTH
45
Pushback Procedure
The PUSHBACK function is embedded in the CDU. Click MENU SIMU PUSHBACK to
access the PUSHBACK configuration page.
At 1L, the straight line distance for PUSHBACK should be entered. At 2L, you can choose to have the
Nose Gear turn right or left. And at 3L, enter the turning angle. After entering the data as shown above,
press 4R to start the PUSHBACK. In the example above, the aircraft first moves backwards for 60m,
then heads left (front wheel turning right) to turn 90 degrees to complete the PUSHBACK. To stop the
PUSHBACK process, press 4R again.
Memory Items:
-
The aircraft turns opposite from the nose gear turn direction.
PARK BRAKE ON after pushback.
46
Note: This tutorial demonstrates single engine autostart. Normally, two engines are autostarted
together, 3 and 4 then 1 and 2.
The engine start procedure can be carried out during the PUSHBACK process or after the PUSHBACK
process completes. In this tutorial, we start the engines after the PUSHBACK process is completed.
1. On the lower EICAS, select the secondary
engine indications. The screenshot to the
right shows No. 4 engine being started.
THR PANEL
After the Number 4 engine is stable at idle, repeat steps 3-4 to start engines 1,2 and 3, in that order.
47
THR PANEL
THR PANEL
48
BEFORE TAXI
Anti-iceAs Needed
Recall.Checked
Autobrake...RTO
Flight ControlsChecked
Ground equipmentClear
49
BEFORE TAKEOFF
Flaps..SET
50
Takeoff Procedure
After receiving takeoff clearance, confirm that the parking brake is released and the aircraft is aligned with
the runway centerline. A standing takeoff will be used for this tutorial.
1. With the brakes engaged, advance the thrust levers to
approximately 70% N1 and check that the engines are
stable and normal readings are displayed.
MCP
See the following screenshots. The three columns inside the FMA (Flight Mode Annunciation) on the
PFD, from left to right, are Auto Throttle Mode, Roll Mode, and Pitch Mode
Now check the FMA. The autothrottle mode should be THR REF with a green box around it
(adds emphasis when the mode first appears), and pitch and roll modes should be TO/GA. The
two pictures below show the differences on the FMA before pressing TO/GA and after TO/GA is
pressed. Also note that LNAV and VNAV are displayed in white, indicating they are armed.
TO/GA means that the current pitch mode is TAKE OFF/GO AROUND. Takeoff is a flight director only
function of the TO/GA mode. Flight director pitch and roll commands are displayed and the autothrottle
maintains takeoff N1 thrust limit as selected from the FMC until HOLD appears on the FMA. That is to
say, under TO/GA, the autopilot system does not control the aircraft, so the pilot controls the
aircraft manually by following FD cues.
51
After pressing the TO/GA switch, THR REF continues to display until speed reaches about 65
knots. As shown in the screenshot below, the auto throttle mode becomes HOLD with a green
box around it and then becomes HOLD without the box. HOLD means power is removed from
the autothrottles and the thrust levers remain stationary. At that point in the real world, the pilot
flying must maintain the required N1 value and the thrust levers can be move manually; however,
due to the limitations in Flight Simulator we suggest firewalling (push fully forward) hardware
thrust levers for the remainder of the flight to prevent conflicts with the autothrottles. Look at the
screenshot in paragraph 1 of this section: the green 104.4 is the value at which thrust should be
kept. Generally, once the throttles are set leave them alone unless there is a gross error.
When Airspeed is at V1, the panel system automatically calls out V1 then at VR, ROTATE. At
VR, rotate at 2.5 degree/second (2 degrees for an engine failure) towards 15 degrees pitch
attitude. The Flight Director is not used during rotation. During the entire takeoff process, the pilot
must monitor the engine instruments, the vertical speed, and the airspeed indicator.
3. When the aircraft lifts-off, the pitch command target speed is V2+ 10 to 25 knots (the MCP speed
we set was V2), and the roll command remains wings level.
4.
After seeing a positive rate of climb displayed on the altimeter, select the landing gear lever to
UP.
If an engine fails during the takeoff, the target speed of pitch command is:
V2, if the speed is less than V2;
the current speed, if the speed is between V2 and V2+10;
V2+10, if the speed is higher than V2+10
5. At 50 ft AGL (ABOVE GROUND LEVEL) LNAV activates (if armed) and replaces TOGA as the
roll mode. The pilot flying should now be following the lateral guidance on the PFD.
52
6.
At 400 ft AGL, VNAV activates (if armed) and become the pitch mode. Pitch commands the
current airspeed and the autothrottle sets the selected reference thrust and annunciates THR
REF.
7. When the aircraft reaches the thrust reduction altitude (which can be set in the TAKEOFF 2/2
page of CDU, the allowable input range is 800ft~9999ft, and in our example, is 1500ft), the flight
phase changes from the takeoff phase to the climb phase. The FMC changes the reference
thrust limit to the armed climb limit: CLB (in our case) or CLB1 or CLB 2.
8. Now Press CMD A to engage the autopilot, and the flight director status shows that CMD has
replaced FD. The pitch mode of the FMA is VNAV SPD. VNAV SPD pitch mode means that the
aircraft is using speed specified in the CDU to maintain pitch. In summary, now the aircraft is
tracking the current FMC route under the control of AFDS roll and pitch commands and using the
FMC calculated N1 value for speed.
MCP
LEFT FORWARD INSTRUMENT PANEL
9.
Retract the flaps on the schedule annunciated on the PFD speed tape and watch to see
that the indicated flap and slat positions are the same as those of the flap lever. On some
departures, it may be necessary to remain at Flaps 5/Flaps 1 to control airspeed in turns,
and it may be necessary to SPEED INTERVENE. See the AOM for details.
10. When the flaps and slats are completely retracted, if not previously armed, press the VNAV
switch to select the VNAV mode, or select normal climb speed. After VNAV mode is
engaged, the MCP speed window will blank.
When VNAV mode is engaged, the AFDS pitch and A/T mode will be commanded by the
FMC, and the aircraft automatically flies the vertical profile.
There are three VNAV modes:
VNAV SPD: The AFDS maintains the speed displayed by the airspeed indicator and/or on
the CDU CLIMB or DESCENT page.
VNAV PTH: The AFDS maintains the FMC altitude and path or flies the descent path
indicated by the pitch command.
VNAV ALT: When a conflict occurs between the VNAV profile and the MCP altitude, the
airplane levels at the MCP altitude and the pitch flight mode annunciation becomes VNAV
ALT. VNAV ALT maintains altitude.
53
VNAV can be armed on the MCP before takeoff if the following conditions are satisfied:
An active route has been entered.
The performance data have all been entered.
The flight director switches are both positioned to the ON position.
Now lets have a look at the current status of the aircraft. The current FMA status is given below.
MCP
LEFT FORWARD INSTRUMENT PANEL
Under the following situations, the MCP speed window will be blank:
VNAV mode is engaged
A/T engaged in the FMC SPD mode
During two engine AFDS go-around
11. After the landing gear is completely retracted, move the landing gear
lever to the OFF position by clicking OFF or assign a key
combination such as SHIFT+O in the iFly Key Assignments
dropdown and use that to position the lever to OFF.
54
Climb Procedure
Now the aircraft is flying along the FMC route under the control of the AFDS. There are some operational
principles that should be followed during the climb phase.
1. When the flight altitude is above 10000ft, position the landing light switches to OFF.
2. Set the passenger signs according to needs.
3. At transition altitude, 6000ft in our case, set the altimeters to standard.
Now have a look at the target speed, target altitude, and the heading of the aircraft. Press LEGS located on
CDU to access the LEGS page, as shown below:
CDU
On the CDU, the active airspeed, altitude, and waypoint name are displayed in magenta, while other
waypoints and the altitude data are displayed in white. On the ND, the active data, including the route,
waypoints, speed, and altitude, are displayed in magenta; inactive data, cyan; modified data, white; and
offset data, magenta.
On the PFD photo below, the active speed and altitude are displayed above the speed indications and the
altitude indications respectively. From the above LEGS page and the ND snapshot figure, we can see that
we are now flying toward CPT waypoint.
55
Next we check the active speed, which involves the CDU LEGS page and the CDU CLB page.
Target Speed
Speed Restriction
Selected Speed
Speed Bug
On the CDU and PFD, the active speed is displayed in magenta. On the PFD, the Speed Bug and Selected
Speed are both displayed in magenta. They point to the airspeed:
manually selected in the IAS/MACH window
airspeed computed by the FMC when the MCP IAS/MACH window is blank.
Now the IAS/MACH window on MCP is blank, so the FMC computed airspeed is displayed on the PFD.
From the picture, we can see that the current active speed is 344 knots.
56
Next we check the active altitude, which involves the LEGS page and the CLB page.
Cruise Altitude
Selected Altitude
Selected Altitude Bug
The Selected Altitude Bug and Selected Altitude located above the PFD altitude indications both display the
MCP ALTITUDE setting. Rotate the Altitude Selector to adjust the MCP ALTITUDE in 100ft increments. The
Calculated Waypoint Altitude or the Specified Waypoint Altitude is displayed on the LEGS page. At or above
altitude restrictions are entered with a suffix letter A (example: 6890A). At or below altitude restrictions are
entered with a suffix letter B (example: 13770B). Mandatory altitude restrictions are entered without any
suffix letter (example: 20000). During the CLIMB, altitude restrictions that are between two altitudes are
displayed with the lower limit first, followed by a suffix letter A, then the upper limit, followed by a suffix letter
B (example: 6890A13770B). The reverse (B first) is entered for the DESCENT. Altitude entry is not allowed
on the LEGS page for CRUISE phase waypoints. The cruise altitude is displayed on the CDU CLB page.
During the TAKEOFF and CLIMB phases, the AFDS uses the lowest altitude among the three as the active
altitude. During the DESCENT phase, the highest altitude setting is the active altitude. On the PFD just
above, we can see that the altitude is set to 30,000ft and that the aircraft is in the climb. We set the MCP to
the CRUISE phase altitude before the aircraft passed waypoint WOBUN. Otherwise, the aircraft would
remain at 6,000ft.
57
We would like to emphasize again that when the aircraft passes waypoint WOBUN, you must adjust the
MCP altitude to a higher altitude or the cruising altitude, otherwise the aircraft will remain at the current MCP
altitude.
Tip: Changing the Altitude
So the aircraft is at the programmed 6,000ft prior to WOBUN and ATC
states climb and maintain FL180 (18,000ft). There are a couple of
ways to satisfy this requirement:
1. Set the cleared altitude in the MCP ALTITUDE WINDOW and
press the ALTITUDE SELECTOR knob. This clears the next
waypoint altitude (in this case 6000 at WOBUN) and the
aircraft will start to climb to the MCP altitude immediately.
2. While still on the ground, on the CDU Legs page delete the
WOBUN altitude restriction. Then manage the altitude
clearances by setting them on the MCP.
3. Push 6R on the VNAV CLB page, CLB DIR(ect). ALL
waypoint altitude restrictions between the current aircraft
altitude and the MCP ALT or the FMC cruise altitude are
deleted. The FMC cruise altitude is not affected. Be careful
with this.
Now look at the ND. As expected, WELIN waypoint has been passed and is now displayed in white, and
now the aircraft is flying towards waypoint AKUPA. This is because we have armed the LNAV mode before
takeoff and have been flying according to FD commands after takeoff. Therefore, after the aircraft passes a
waypoint, the FMC will automatically switch to the next waypoint.
58
This page provides quite a lot of flight data. The first line displays the last waypoint we passed and the
altitude, time, and fuel quantity which remained when passing that waypoint. The second line displays the
waypoint we are now approaching, and the distance-to-go (DTG) from present aircraft position to the
waypoint, predicted arrival time, and the predicted fuel quantity when reaching that waypoint. The third line
displays the next following waypoint and its corresponding data. The fourth line displays the corresponding
data when reaching the destination airport. The data of this line is very important, and should be
checked often during the flight. Confirm there is sufficient fuel to reach the destination airport. If the
fuel quantity displayed at 4R is less than the RESERVES value on the CDU PERF INIT page, the CDU will
display an INSUFFICIENT FUEL warning message. 5R displays the time and flight distance to T/C (top
ofclimb), T/D (topofdescent), S/C (step climb), and E/D (end of descent) according to the current flight
phase. 5L displays the active speed.
After the aircraft climbs above the transition altitude, the barometric setting display located below the PFD
altitude indication will turn amber with a square box around it, indicating that we need to set the Barometric
Standard Switch located on the EFIS Control Panel to STD. Press the STD switch, and then the system
will use the standard barometric setting (29.92 inches Hg/1013 HPA) as the barometric altitude reference
and STD will display on the PFD. The following show inches actions are the same for HPA.
STD
CAPTAIN GLARESHIELD
59
Continuing the climb we see a green circle on the ND, marked T/C. This is the top-of-climb point. After
passing this point, the aircraft reaches the cruise altitude and begins the cruise phase of our flight. The green
arc in the figure is the altitude range arc, showing that according to the current vertical speed and ground
speed, the aircraft will reach the MCP altitude when it reaches the arc on the map. The altitude range arc
position on the ND is calculated according to the current vertical speed and ground speed, and the higher the
aircraft climbs the lower the vertical speed will be, so, usually, the altitude range arc displays before the T/C
point. As altitude increases, the deviation between these two points becomes less.
Now look at the CDU CLB page. In the following two figures, the left one shows the situation when the
aircraft is climbing using IAS, and the one on the right after the change to MACH. The changeover occurs
when the MACH speed indicated on the PDF matches the MACH set by the FMS, which is shown on the
CDU ACT ECON CLB page, in this case .836. The changeover altitude will vary depending on aircraft
60
loading and the selected cruise altitude. Lower cruise altitudes may not produce a changeover to MACH.
If the MCP IAS/MACH display is not blank, it will automatically changeover between IAS and MACH.
The aircraft is now past the T/C and in the Cruise phase of the flight.
61
Cruise Procedure
Aside from checking the navigation, responding to ATC, keeping up with aircraft system status, with
particular emphasis on the fuel system and step climbs, and planning ahead, there is not that much to
do during the cruise phase. Press VNAV on CDU to access the cruise page. The CLB page is displayed
on the CDU before reaching the T/C point, then after passing the T/C, the CRZ page will automatically
display. Through the CRZ page, we can select various modes, just as on the CLB page. These modes are
described in the AOM
The most often used pitch and roll modes for the cruise phase are VNAV+LNAV. The roll mode of HDG SEL
and the pitch modes of ALT HOLD or V/S may also be used during the cruise phase. Those modes and
FLCH pitch mode are described in the AOM.
During the remaining time of the cruise phase, we will use a VNAV + LNAV mode, which ensures the most
economical operation of the aircraft.
The iFly 747-400 is designed for use under time acceleration, which may be set to automatically activate on
the Configuration Tool Miscellaneous page. The automatic time acceleration function is limited to 8X.
In the interests of good airmanship, the following should be accomplished at each waypoint or every hour:
-
Check that the track and distance to the next waypoint and the flight plan agree. Ensure that
the aircraft turns properly toward the next waypoint.
Using the CDU PROGRESS page, compare the fuel totalizer reading and flight plan required
fuel at each waypoint to ensure arrival at the destination with the correct amount of fuel.
Check the EICAS synoptic pages at TOC and every hour thereafter for normal systems
operation.
NOTE: The TERRAIN DISPLAY may be ON during the CRUISE as desired or required.
62
STEP CLIMBS
From the upper right corner of the CDU ECON
CRZ page shown on page 60 above, we know
that we can perform a step climb (S/C) to a more
economical altitude of 34,000ft in 767 nautical
miles. The S/C point will be shown on the ND well
before executing the climb. Per the ND
screenshot at the right, we need to be ready to
execute the first step climb of our flight. The
primary method of performing step climbs is by
setting the new altitude on the MCP and, upon
reaching the S/C point on the ND, pressing the
ALTITUDE SELECTOR button. This enters the
MCP altitude as the active cruise altitude, without
creating a modification. Step climbs may also be
performed by entering the desired altitude at 1L
on the CDU CRZ page. The step climb will then
start automatically when the aircraft reaches the
S/C point shown on the ND. In either method, the
CRZ page title changes to CRZ CLB.
See the screenshots at the right for the set up for
our step climb to 34,000ft using the MCP method
discussed above. The CDU ACT CRZ CLIMB
pages displayed when the step climb was
executed and the screenshot shows that FL340
will be reached in 34NM at 0930Z.
MCP
CDU
64
Before reaching the Top of Descent (T/D), check the active route for the correct arrival and approach
procedures. Make modifications as necessary, which well do next.
Recall that we configured the aircraft to pause FS 10NM from the top of descent. FS is now paused, and its
now time to enter the KSFO arrival procedure and runway as we discussed back on page 30.
ENTERING AND MODIFYING THE ARRIVAL ROUTE
65
66
The active arrival procedure takes us over the SFO VOR then direct to CEPIN INTERSECTION on the
ILS28R approach. In order to slow things down a bit and make the arrival more realistic, we need to make
more changes to the route.
67
CAPTAIN GLARESHIELD
68
Descent Procedure
The DESCENT phase begins before the aircraft descends below cruise altitude. The Descent Procedure
should be completed by the time the aircraft is at 10,000ft.
The following should be accomplished as the aircraft approaches the T/D:
CDU
Press the CDU INIT REF button and well see the APPROACH REF page. APROACH REF shows the
approach planning information and the approach speed reference (VREF). This page is also reachable
from the CDU INDEX page.
On this page, 1L displays the aircraft weight, which, if in small font, means that the data was calculated by
the FMC automatically. This data is the same as that on the PERF INIT page. It can also be entered
manually, which will be displayed in large font. After exiting this page, the FMC automatically calculated
weight data will replace the manually entered data.
3L and 4L show the flight plan landing runway and its length.
1R~2R are the landing reference speed for two landing flap settings.
4R displays selected approach reference flap and speed setting. Pressing the LSK corresponding to
1R~2R will transfer the flap and speed setting to the scratchpad, after which you can press 4R to enter
the speed into FMC. 5R shows the wind correction for approach, which is +05 knots by default. It can be
entered manually, the maximum being +20 knots.
In this flight, we will use Flap30 as the landing flap setting. So press 2R and 30/147 is displayed in the
scratchpad, indicating that the flap setting is 30 degrees and that the landing speed is 147kts. Then press
4R to complete the entering of approach reference flap and speed. Dont forget the wind correction of +5
kts when you set MCP speed.
69
MINS
CAPTAIN GLARESHIELD
Recall..Checked
AutobrakeSet
Landing dataVREF ___ Minimums ___
Approach briefingCompleted
1.
2.
When cleared to descend, set the clearance limit altitude on the MCP.
3.
Set VREF.
4.
5.
6.
Set or verify that the navigation radios and course are correct for the selected approach.
7.
Familiarize yourself (brief) with the approach to be flown and double check the nav/radio setup.
70
Now lets have a look at ND to focus on the current aircraft position. We are still in the CRUISE, but
approaching the location where we need to start the descent into the San Francisco area.
We can see there is a green circle about 21NM ahead of the aircraft beside which T/D is marked. This is
the top of descent point. The methods of starting the descent include:
The descent phase starts automatically if the aircraft passes the T/D point under the VNAV cruise mode.
Start the descent phase by pressing 6R on the CDU DES page when a T/D is set and the descent phase
is not active. This starts a descent at approximately 1,250 feet per minute using the active descent speed
schedule. Upon intercepting the planned descent path, the aircraft transitions to the planned descent path.
Start the descent phase by pressing ALTITUDE SELECTOR if the MCP altitude is lower than the cruise
altitude and the aircraft is within 50NM from the T/D point under the VNAV cruise mode.
No matter how the descent phase is started, you MUST set the MCP altitude to be lower than the cruise
altitude. Otherwise, the aircraft will stay at the MCP altitude even if it has started the descent phase. This
concept is similar to the climb phase, during which the MCP altitude provides altitude intervention.
If the aircraft starts the descent phase by the last two methods outlined above, it actually starts the early
descent mode, instead of a normal descent phase. VNAV starts the early descent with a reduced descent
rate until the aircraft intercepts the idle descent path. VNAV uses FMC SPD as the autothrottle mode; and
VNAV PTH, as the pitch mode. The dashes in the following figure represent the flight path of an early
descent. After intercepting the idle descent path, the aircraft will descend along the idle descent path.
T/D
When the MCP altitude is lower than the cruise altitude, the early descent mode will be started if the
ALTITUDE SELECTOR is pressed when the aircraft is within 50NM of the T/D.
71
But if the ALTITUDE SELECTOR is pressed when the aircraft is more than 50NM from the T/D, it only sets
a new cruise altitude.
50NM
50NM
T/D
In this tutorial, we will use the first method to start the descent phase. Before reaching the T/D, set the MCP
altitude to an altitude constraint lower than the cruise altitude, or set it to be the landing airports altitude.
Here we set the MCP to 11,000, the altitude constraint at the LOZIT waypoint show on the CDU LEGS page.
Note that this altitude must be reset in order to meet follow on constraints.
MCP
CDU
The aircraft will start to descend automatically as it passes the T/D. If we do not set the MCP to a lower
altitude, the FMC will display a warning message RESET MCP ALT on the CDU when the aircraft is about
2NM from the T/D.
As the aircraft reaches the T/D point, the autothrottle (A/T) may stay in SPD mode, as that is what is being
regulated, or you may see IDLE display as the A/T mode. These two modes appear as follows:
72
Recall the discussion on page 50 concerning autothrottle HOLD and what it means to the flight crew. In the
real world, the pilot flying can tweak the thrust above idle if required to maintain speed on path.
The roll mode continues to be LNAV. There is not much to explain about this, because it is the same as the
climb phase and the cruise phase. But we should explain in detail about the pitch mode. VNAV can perform
the descent in two modes: Path Descent (displayed as VNAV PTH) and Speed Descent (displayed as VNAV
SPD).
Path Descent (VNAV PTH)
During the path descent process idle thrust and pitch control maintain the vertical path calculated by the
FMC. The descent path starts from the T/D point, and the following factors are also taken into account when
performing the path calculation:
Applicable target altitude
Applicable target speed
Idle thrust
Speedbrakes retracted
Target speed on the DES page
Entered descent winds
ANTIICE ON altitude
The target speed can be changed via LEGS or DES page. You can also enter the wind data on the Descent
Forecast page. It should be emphasized that the path descent uses the target speed for planning purposes
only. The descent path is calculated for an idle thrust descent but the FMC will apply thurst to maintain
speed on the path if required by, for example, unforecast headwind in the descent.
If the aircraft does not have all necessary information to path descent, FMC will revert to speed descent
mode. If the airspeed increases significantly due to unexpected tailwind, the CDU will display the message
DRAG REQUIRED in order to keep along the path. If the speed limit is exceeded the FMC will revert to
VNAV SPD and descend at the programmed descent speed.
73
As shown in the CDU screenshot below, the aircraft is now in the descent, heading for an altitude restriction
of 11,000 at waypoint LOZIT.
From the FMA snapshot on page 70 above, we know that the aircraft is using the path descent mode. Look
at the ND, and you will see that a scale is displayed at the lower right corner of the screen, as shown in the
following screenshot:
The magenta symbol is the VNAV path pointer; and the white scale is the deviation scale. Their function is
similar to the ILS glide slope indicator, i.e., to indicate the deviation between the aircraft and the FMC
planned descent path. The scale can show a deviation of 400ft. If the deviation is more than 400ft, the
deviation figure will be displayed above or below the scale. Now the aircraft is descending automatically
under autopilot control.
The descent may also be monitored on the CDU PROGRESS page 2 by observing VTK ERROR at 2R.
CDU
Recall that the transition altitude in the U.S is 18000ft, so if not already done reset the CDU DES
FORECAST page accordingly:
CDU
74
Lets have a look at our current status. The aircraft is in the descent flying towards waypoint LOZIT, having
just made the turn at PYE:
Before the aircraft passes LOZIT set the KSFO ILS 28R G/S intercept altitude of 1800ft in the MCP
ALTITUDE WINDOW.
ATC may ask you to fly a holding pattern at a certain point. The busier an airport is, the more often you are
asked to fly a holding pattern. Holds are discussed in the AOM.
During the descent phase ATC may ask for a change of arrival procedure due to weather, other traffic, etc.
In such cases, we can access the ARR page of CDU to re-select the directed procedure. Pay attention after
changing the current procedure: go back to the LEGS page to remove the Discontinuities which have
appeared in the CDU and confirm that the route is correct. After repeated modifications, the route in the
CDU may become unusable. In such case, we recommend the use of other autopilot modes, which are
covered in the AOM.
75
Now we are still in the descent and getting much closer to our destination, KSFO. Lets have a look at what
we can expect to be displayed on the ND as we approach the SFO VOR. Recall that we previously
modified the arrival route to make things a bit more realistic and easier for the flight crew to manage.
There are two things to notice on the above screenshot snip from the ND: the green circle, or donut,
just prior to DUXBY waypoint and the green E/D just below 28R.
The green donut is a deceleration point computed by the FMC. Deceleration points do not have an
identifier and represent when the FMC will slow the aircraft speed to conform to what is programmed.
The first donut is where airspeed reduces to 240kts (the system uses 240kts to account for winds
which could cause the aircraft to exceed the 250kt limit).
The green E/D represents the end of the descent. When an arrival or approach procedure is selected
on the CDU ARRIVALS page and incorporated into the flight plan, the FMC creates an E/D. The E/D
is located 50 feet above the runway threshold (RW waypoint) for all approaches except VOR
approaches. The E/D for VOR approaches is the missed approach point; which may be the VOR,
runway waypoint (RWXXX), or a named waypoint.
76
BARO
ST D
CAPTAIN GLARESHIELD
CAPTAIN GLARESHIELD
Altimeters...Set
77
Now the aircraft is just past the SFO VOR and continuing the descent. It is time to focus on the approach
and landing.
The FMC has slowed the aircraft to the 10000ft altitude speed limit. Remaining under LNAV and VNAV
control, the aircraft is on course to OSI and the start of the base leg of the approach. Note the green donut
on the ND between OSI and MENLO intersection, which signifies additional speed reduction. Also note that
CEPIN is the first waypoint on the APPROACH.
IMPORTANT NOW PAUSE FLIGHT SIMULATOR IMPORTANT
We need to discuss the unique aspects of the 747-400 APPROACH phase of flight. These matters
necessitate prior planning by the crew as the flight deck workload increases due to procedural requirements.
There is a mode used by the FMC which is not annunciated: On Approach mode. The aircraft is in
On Approach mode when one of the following conditions is met:
1. A VFR approach is created and,
a. the aircraft has sequenced the FAXXX, or
b. the aircraft is enroute to a direct-to or intercept-to the RWYYY waypoint and is within 25 nm of
the runway threshold
2. A published instrument approach is selected and incorporated in the active flight plan and the
aircraft is two (2) nautical miles from the first waypoint on the APPROACH. That waypoint will be
shown at LSK 6R on the CDU when the APPROACH is selected. In our case, the waypoint is
CEPIN. IMPORTANT: If there is disagreement with a chart, be certain to use the airac defined
waypoint given by the CDU.
3. Air traffic control redirects the aircraft to a course direct to the Final Approach Fix (FAF) and the
aircraft is on that course and is two (2) nautical miles from the FAF.
78
The FMC transitions out of On Approach mode when any of the following occurs:
1. TOGA is selected
2. the aircraft lands
3. the aircraft flies beyond the last waypoint in the approach (missed approach waypoint or
runway) and the VNAV page title changes from "ACT xxxxxx DES" to "ACT END OF DES"
See page 279 of the iFly 747-400 AOM and the Tutorial Addendum for additional information about
On Approach.
When the aircraft reaches the deceleration point signified by the green donut on the ND, if the FMA Mode is
VNAV PATH the FMC will reduce the airspeed to around 173KTS. This speed is well into the amber band
and just above the Red Bricks. It is also below FLAP UP maneuver speed. The next screenshot shows
this:
This is not a situation crews want to encounter in the high workload environment of an approach.
So, in an approach with the deceleration point is before the first waypoint on the approach, we must select
speed intervention (press the SPD BUTTON) on the MCP just prior, about one (1) NM, before
arriving at the green donut on the ND. Then immediately set the PFD Command Airspeed Bug (CBE) to the
FLAP UP or FLAP1 SPD shown on the PFD speed tape. Set FLAP as necessary.
79
Here is how the MCP, PFD and ND should look at this point:
Note that the MCP SPD Window is open. The crew is now managing airspeed and must also be aware of
the descent as VNAV SPD is now the FMA Mode. In VNAV SPD the elevators are controlling the aircraft
speed and the computer is not really interested in the path at all unless there is a FMC altitude constraint.
Then the pitch mode will change to VNAV PTH, the speed window will close and airspeed will revert to
whatever the FMC has programmed at that point. Or if the aircraft encounters an altitude set in the MCP
window (such as the 1800FT in our case) the FMA Mode will change to VNAV ALT and the speed window
will stay open. The path is still generated and, as shown above, appears graphically on the PFD. There is
also a plus or minus VTK ERROR readout on the CDU PROGRESS page 2.
How did that green circle appear on the ND? Press the CDU FIX button and you will see:
80
In an approach where the green decel donut is NOT before the first waypoint on the approach, draw a two
(2) NM circle around the first approach waypoint. That is where the FMC will enter On Approach mode and
the crew must open the SPD WINDOW and set then manage the airspeed just before the aircraft arrives at
the two (2) NM circle. If on your tutorial approach the decel point is not prior to CEPIN, draw the circle
around CEPIN and SPD INT just before the aircraft reaches the circle. In this case, the MCP, PFD and ND
will look like the following:
Note that while the SPD WINDOW is open and the crew is managing airspeed, VNAV PTH remains as the
pitch mode. The FMC is controlling the descent. This is due to the FMC being in On Approach mode, as
discussed above.
IMPORTANT UNPAUSE FLIGHT SIMULATOR - IMPORTANT
81
At MENLO intersection the aircraft will turn toward the final approach course, and there are important
actions the flight crew must take: on the MCP, press LOC to arm the localizer and confirm the ALT is set to
1800ft for G/S intercept. When the localizer is intercepted, the system will automatically set the inbound
final approach course.
Looking at the above screenshot, we see that the aircraft remains in VNAV SPD mode, with the crew
controlling speed and the FMC calculating the vertical profile. Also, LOC is armed but not yet captured, and
the aircraft is still left of the final approach course. The G/S is alive, speed is reducing toward 203kts,
82
FLAPs are being extended on schedule, and the aircraft is turning left to establish on the final approach
course. The MCP ALTITUDE remains set to 1800 feet in anticipation of G/S intercept at the Final Approach
Fix (FAF). The FMC will set MCP COURSE to the final approach course when established on the LOC.
Then arm APP. This tutorial executes an autoland, so the other autopilots will engage automatically at
1500ft AGL.
1500ft AGL on an autoland is also the point when the autopilots control the rudder, so applying trim to the
rudder will have no effect. Thats important to know for an engine out event! The rudder remains under
autopilot control until (1) the autopilot is disengaged after the landing or (2) after the first roll mode is
selected on a go around, usually at 400ft AGL.
Do not be late arming the LOC or the APP modes as things happen in a hurry at this point. Extend FLAPS
according the flap extension scheduled display on the Speed Tape.
Set the Decision Height (DH) in the MCP ALT Window just prior to reaching the FAF altitude. This allows
the FMC to continue the descent rather than leveling off at the FAF altitude. Reset the MCP ALT to the
missed approach altitude when the aircraft is more than 300FT below the missed approach altitude to avoid
a level off during the final approach descent. In this tutorial flight use 200FT as the DH and 3000FT as the
missed approach altitude.
Continue to set the FMC determined airspeed on the MCP at each of the remaining waypoints and extend
FLAPS as required until the aircraft captures the G/S.
Do not hesitate to pause Flight Simulator in order to stay ahead of the aircraft!
NOTE: For more information about refinements to the iFly 747-400, please see the Tutorial Addendum.
83
4.
At glide slope intercept, lower the landing gear, verify that the
gear is shown as down on the ND and continue to extend the
flaps on schedule. Set MCP speed to VRef + 5 after selecting
Flaps30. Set the MCP to the missed approach altitude of
3000ft.
CENTER FORWARD INSTRUMENT PANEL
5. Click the input box area beside the spoiler lever to arm
the spoilers, and verify that the SPEEDBRAKE ARMED
is annunciated on the UPPER EICAS.
THR PANEL
Speedbrake. ARMED
Landing gearDown
Flaps.___, Green light
84
TIP: Energy Management (Recovery from a high and/or fast condition) and Approach Types
Using the speedbrake is the first thing which may come to mind, and in fact that is preferable to extending
flaps at or close to the maximum placarded speeds due to the high flap mechanism wear factor. Use of
the speedbrake is less effective at slower speeds and is not recommended beyond FLAP20. At slower
speeds (under the 270kt extend limitation) the landing gear provides a tremendous amount of drag and will
effectively slow the aircraft.
So if you are a little too high or fast, extend the speed brake fully, reduce pitch and slow up. Then,
following the PFD speed tape cues, extend flaps. If quite high or fast then extend the gear. Be advised
there will be unexpected, perhaps never-before-experienced, noise in the passenger cabin if the gear is
extended at 270 kts! If the aircraft is not stable (on speed and descent profile and with the engines
spooled up by 1000ft AGL) then go-around.
There are two types of approaches:
1. Full drag: Have the gear down and landing flaps selected by G/S intercept. (used in this
tutorial)
2. Low drag: Start the approach at Flap5 with the gear up. (If the aircraft is heavy, Flap10 may
be required to stop acceleration down the G/S.) At 2000ft AGL select Gear down, Flap20
and arm the spoilers (do not arm the spoilers until the gear is down any fault in the spoiler
mechanism may trigger the spoilers to deploy to the GRD position, which you do not want to
experience!) By 1500ft AGL select landing flaps. Be stable with the landing checklist
complete by 1000ft AGL
5. Glide slope capture is show below. Study the photo to ensure you understand what is depicted:
the PFD FMA shows SPD, LOC and G/S in green (active modes) and LAND 3 is show in green on
the PFD, indicating the all three autopilots are coupled with the flight controls. Speed is steady at
VREF + 5 and the aircraft is centered on the LOC and flying down the glide slope. ROLLOUT
and FLARE are armed (shown in white).
85
And here is the full view on the final approach. The Gear is down, Flap30 is set, Autobrakes are set to 2,
the Speedbrake is armed and the missed approach altitude is set on the MCP.
7. Exit the runway and taxi to the KSFO International Terminal, remembering the taxi
speeds we discussed on departure from EGLL.
86
87
Shutdown Procedure
After stopping in the parking area or at the gate, we can start the shutdown procedure.
1. Set the parking brake and confirm that the
PARK BRAKE SET message is shown on the
EICAS.
CENTER FORWARD INSTRUMENT PANEL
THR PANEL
88
Hydraulic panel..Set
Fuel pumps.OFF
Flaps..UP
Parking brake...___
Fuel control switches CUTOFF
We a t h e r r a d a r . . . OF F
89
Secure Procedure
The secure procedure is started after completing the Shutdown Procedure.
1. Set the IRS mode selectors to OFF.
LEFT FWD OVHD PANEL
IRSs.....OFF
Emergency exit lights.OFF
Packs...OFF
Now you have completed the entire flight process. Well done, captain!
The tutorial ends here, but please do not forget to read the iFly 747-400 AOM and the Tutorial Addendum for
much more detail.
90