FS2Crew MSFS PMDG 737 SOP1 Main Ops
FS2Crew MSFS PMDG 737 SOP1 Main Ops
FS2Crew MSFS PMDG 737 SOP1 Main Ops
MSFS
QUICK LINKS:
FS2Crew Website
FS2Crew Forum
FS2Crew Facebook
FS2Crew Instagram
INTRODUCTION:
SOP 1 follows, in general, stock OEM Boeing procedures, and the goal of this product is to allow you to
fly your MSFS PMDG 737 in a much more realistic way using actual airline procedures with respects to
flows, checklists, and general crew interaction.
Two main interface modes are available: Voice Control and Button Control. An additional “Auto
Respond” mode is available for Button Control users.
If you are new to FS2Crew, we STRONGLY suggest starting in Button Control mode until you understand
the rhythm of the program.
DISCLAIMER: This tutorial is made for flight simulation purposes only and does not necessarily reflect
real world procedures to their fullest. FS2Crew is an entertainment product. It is not meant for real
world flying or training. It is not affiliated or associated with any specific airline or company.
• Download FS2Crew for the PMDG 737 via the Product Manager.
• Open the MSFS Toolbar and open the FS2Crew Command Center by clicking the FS2Crew icon
(the airplane nose) as shown below.
• Select PMDG 737 SOP 1 in the drop-down menu and click LAUNCH APPLICATION.
• You may need to scroll down the product list to see FS2Crew for the PMDG 737.
• The FS2Crew panels should appear. If you have not yet activated FS2Crew for the PMDG 737, you
will be prompted to enter your serial code.
• Your serial code is viewable in your on-line FS2Crew account, or from wherever you purchased
FS2Crew.
• The FS2Crew panel viewable via the Command Center performs many of the same functions
found on the main stand-alone panel. If you are using a VR headset, you would typically use this
panel since it is embedded into the Tool Bar and therefore visible in your VR headset.
Note, however, that the FS2Crew Config Panel is not viewable in the Command Center / MSFS
Tool Bar.
• It is possible to network the FS2Crew Panel to your mobile device. Click here to learn how.
• Tool tips are associated with each button in either panel. Mouse over each button to learn more
about each button. An option is available on the Config Panel to disable/enable tool tips. Again,
if you have any doubts, please post your question in our Support Forum or on our Discord
Channel (Discord is the best way to communicate).
IMPORTANT! IF THE PANEL IS BLANK...
• If the panel on the left in the Tool Bar is blank, please ensure you have ENABLE HTTP SERVER
checked on the FS2Crew Config Panel (GEAR ICON).
• You will then be prompted to give the NETWORK COMMAND SHELL permissions to access your
device. Please select YES. This panel may be hidden ‘behind’ the FS2Crew panel, so if you do not
see it, minimize the FS2Crew panel so you can see it.
https://fs2crew.com/fs2crew-command-center-troubleshooting/
If your EXE.xml file is corrupt (and it is easy for it to become corrupt since multiple developers
write to it now), the COMMAND CENTER will not auto start when MSFS loads. In fact, if the
EXE.XML is sufficiently corrupt, it can cause MSFS to crash on startup.
The general solution is to delete your EXE.xml (make a backup first), then re-install FS2Crew.
FS2Crew will rebuild a fresh new EXE.xml that will clear of any corruption (usually invalid
characters).
However, a better option is also available on the CONFIG PANEL to make the Command Center
auto start when Windows starts, thus bypassing the EXE.xml altogether.
• You can select your desired interface mode on the FS2Crew CONFIG PANEL, which is accessible
by clicking the Gear Icon on the Main Panel (2D Panel only).
Auto Respond = Button Control but you do not need to manually press the Main Button to
respond to each checklist item. The checklist will run through itself automatically.
• If using Voice Control, you can check your speech recognition status by pressing SPEECH STS in
the INFO CENTER.
• The ASSIST panel is intended to help users operate the software without referencing a manual all
the time.
• The critical information needed to fly is displayed directly in the ASSIST panel.
The ASSIST panel can be toggled by pressing the YELLOW CHECKMARK icon located to the left of
the Info Center icon.
Voice Command Assist = Displays available suggested Voice Commands. Note that these
are “suggested” voice commands. Just because the voice command is there, it does not
mean you need to call for it immediately. Use your own judgement.
Capt / PF Flows Assist = Displays suggested actions for the Captain / Pilot Flying. These
actions are typically referred to as “flows.”
Note: Running the Pre-Flight Events is OPTIONAL. You can start the Pre-Flight events routine by clicking
the blue Clock icon, or, if using Voice Control, you may Command: “LET’S START SETTING UP.”
• We recommend that the F/O's altimeter and Standby altimeter syncs to the Captain's altimeter
as shown below.
SYNC CAPT AND F/O EFIS TO: BARO AND MINIMUMS. SYNC
CAPT AND STBY BARO TO 'YES'.
• We recommend using EGPWS auto-callouts for the “MINIMUMS” and “PLUS HUNDRED” calls
during approach. Please ensure your PMDG Options are set accordingly as shown below:
• Open the PMDG’s FMC and select a stock PANEL STATE file. It is your choice. You do not need to
do this for every flight. In fact, you can start with the engines running. But for the sake of this
tutorial, we are going to start with the engines off, so select your desired stock PMDG panel
state.
VERY IMPORTANT: ONLY USE STOCK PMDG PANEL STATE FILES. IF YOU USE YOUR OWN CUSTOM
PANEL STATE FILE AND YOU EXPERIENCE ODD ISSUES, REVERT TO THE PMDG PANEL STATE FILES.
Button Control is also easier than Voice Control, since in Button you are just following a linear path.
Via the Button Control drop down menu, you can jump to any point in flight and start from there.
If you start from the beginning of the flight, the button control action list will auto advance as you
progress.
Note that some commands described in the tutorial flight are not available in Button Control.
As always, if you have any doubts, please ask our Discord Channel.
GSX INTEGRATION
To enable the GSX integration you need to check the following option in Config panel:
Once enabled, F2Crew will be able to request different GSX services during the FS2Crew Pre-Flight phase.
The following services are called automatically by FS2Crew: Catering, Fuel, Boarding, Jetway, Pushback
and Stairs. The only service that will be triggered or called outside the Pre-Flight phase is Stand/Remote
Deicing. Under Voice Control mode, there are additional commands, which are designed to be used when
you are not using the FS2Crew Pre-Flight phase, so you can verbally (manually) request any of the
previously mentioned GSX services. These are the commands:
Additionally, there are these voice commands you can use at any time to control GSX menu via voice
commands:
To resume the timer, just right-clicking with the mouse on it again. If you are under Voice Control mode,
you can use the following voice commands to achieve the same:
To start the Pre-Flight events, be at a parking spot with the engines off, then click the CLOCK icon.
Note: The aircraft BEACON must be OFF for the clock icon to be visible.
Special Note: To FAST FORWARD the PRE FLIGHT EVENTS TIME, left click the time remaining value
directly. The time remaining value will appear where the clock icon is located!
+25 Minutes: Pre-Flight Events start. Jetway connects if available. Door 1L and cargo doors open.
GSX integration: It will automatically request the fuel truck. If for any reason, it couldn’t
request the fuel truck, it will request the catering service. After that, it will connect the
Jetway, if available, otherwise, it will request the stairs.
+24 Minutes: If the aircraft has no electrical power, the FO starts the ELECTRICAL POWER UP
SUPPLEMENTRY PROCEDURE unless you have selected otherwise in the FS2Crew Flight Options
menu (FO POWER UP PROC).
BATTERY ON
GROUND POWER SWITCH ON (IF GROUND POWER AVAILABLE)
FIRE TESTS (FAULT/INOP, OVHT FIRE, EXTINGUISHER)
START APU IF GROUND POWER NOT AVAILABLE
CONFIGURE FUEL PUMPS
WHEEL WELL FIRE TEST
+23 Minutes: You as the Captain should perform the PRELIMINARY PREFLIGHT PROCEDURE. By
convention, the Captain usually performs this procedure if the FO is doing the walk around. If
you want the FO to perform this procedure instead of you, select the associated FS2Crew option.
+22 Minutes: FO starts walk around if they have not already left. If it is night, the FO will turn on
the wheel well light. Captain performs the CDU pre-flight using the estimated ZFW.
GSX integration: If catering service could not be requested, it will request catering now.
+19 Minutes: FA asks if she can start the boarding. Respond: “YES PLEASE/ GO FOR IT/ OKAY.”
Actual boarding will commence approximately two minutes later.
GSX integration: If you reply with a “YES” to the FA question, it will request boarding.
+15 Minutes: FO returns from walk around and starts his PREFLIGHT and CDU PREFLIGHT
PROCEDURE. Capt starts his PRE FLIGHT PROCEDURE.
PREFLIGHT PROCEDURE
-CAPTAIN
PREFLIGHT PROCEDURE
-FIRST OFFICER. TUTORIAL ASSUMES FO WILL DO IT BASED ON DEFAULT CONFIG OPTION. A
CONFIG OPTION IS AVAILABLE TO DISABLE THIS FEATURE (“FO PREFLIGHT PROC” IN FLIGHT
OPTIONS)
NOTE: The various tests (CVR, WX RADAR, TCAS, GPWS) are not part of the normal Preflight
Procedure and are not usually run in during everyday operations. They are ‘Supplementary
Procedures.’ However, if you want the FO to run the Supplementary Procedures during his
Preflight flow, check the “PREFLIGHT SUP PROC” option in the FS2Crew Settings menu.
YAW DAMPER ON
NAVIGATION AND DISPLAYS PANEL SET
FUEL PANEL SET
ELECTRICAL PANEL SET
FIRE DETECTION TESTS IF NOT COMPLETED DURING ELECTRICAL POWER UP
EMERGENCY EXIT LIGHTS ARMED
WINDOWS HEAT ON
PROBE HEAT OFF (ON IF COLD WX OPS)
HYDRAULIC PANEL SET
AIR CONDITIONING PANEL SET
CABIN PRESSURIZATION PANEL SET
IGNITION SWITCH RIGHT
LIGHTING PANEL SET
OXYGEN TEST AND SET
DISENGAGE LIGHTS TEST
FLIGHT INSTRUMENTS CHECK
AUTOBRAKE RTO
CARGO FIRE TEST
AUDIO CONTROL PANEL SET
At the end of the pre-flight procedure, and if “FUEL UPLIFT REQUIRED” selected to “YES” on the
FS2CREW SETUP page, the ground crew will hand the FO the fuel receipt.
+12 Minutes or when desired. As the FO to obtain the ATC Clearance: “REQUEST ATC
CLEARANCE”. This is optional. You can do it at any time.
+11 Minutes or later: Run the Pre Flight Checklist. Command: “PRE FLIGHT CHECKLIST.”
Checklist Notes:
Items in RED TEXT are to be spoken by you, the Captain. If using Voice Control, this is what you
would speak into your microphone.
If using Button or Auto Respond control, actioning the Main Button is equivalent to ‘speaking’ or
‘commanding.’
The FO will respond to many of his own challenges if the item falls within his area of
responsibility.
In voice control, if you ever get stuck on a checklist item due to a speech recognition issue, speak
“SET AND CHECKED.”
• Trigger key phrase is “ALTIMETER XXXX.” Example: “ALTIMETER TWO NINE NINE TWO.”
Ensure this phrase is said clearly and distinctly from the previously spoken Heading value.
Pause a second after saying ‘Heading XXX.’
+9 Minutes: Run the Departure Brief. There are two options: You can open the FS2Crew
BRIEFING PANEL.
Or, if using voice control, you can announce: “ARE YOU READY FOR THE DEPARTURE BRIEF?”
Close the brief by asking: “ANY QUESTIONS?”
+7 Minutes: Load sheet arrives. If load sheet arrives in person and not via ACARS (as defined in
the Config Options), respond: “THANK YOU/ OKAY THANKS/ THANKS.”
+6 Minutes: The FO will ask you if you want to start the APU if the Air Start Cart is not connected
and the APU is off. Note that the PMDG LONG PANEL STATE uses the Air Start Cart. Reply “YES
PLEASE / GO FOR IT/ OKAY / NO.”
ARM AUTOTHROTTLE
SET V2 IN MCP
ARM LNAV/VNAV AS REQUIRED. DO NOT ARM LNAV IF EXPECTING VECTORS OR NOT
DEPARTING ON A SID
+2 Minute: If desired, request permission from the Ground Crew to pressurize the hydraulics.
Command: “COCKPIT TO GROUND”…. “CAN WE PRESSURIZE THE HYDRAULICS?”
If using Button Control, press the GND CALL button on the overhead panel.
ENSURE YOUR AUDIO PANEL IS SETUP LIKE THIS WHEN CONTACTING THE GROUND CREW:
NOTE: Making this request will override your FS2Crew CFG Option to have HYD SYSTEM A
depressurized. The FO will turn on HYD A PUMPS during his Before Start Flow regardless of your
CFG setting. Unless the Air Start Cart is required for engine start, ask the Ground Crew to
disconnect the ground equipment. Ensure you have a power source on-line first, such as the APU!
+1 Minute: Boarding is complete. The FA will notify you that the cabin is ready and if she can close
the door. Respond: “THANKS / THANKS IT WILL BE A SHORT TAXI / THANKS IT WILL BE A LONG
TAXI / CLEARED TO CLOSE SHORT TAXI / CLEARED TO CLOSE LONG TAXI.”
GSX integration: Before FA asks for close doors, it will check GSX status, if it still doing
anything (like for example boarding or if there is any pending ground service to finish), it
will reset the Pre-Flight timer to +7 minutes, to give time GSX to finish. It’s IMPORTANT to
have in mind that this will be kept in a loop when it reaches +1 minute, and if GSX didn’t
finish its pending requests and/or services, it will keep resetting to +7 minutes in the
FS2Crew Pre-Flight timer, to allow GSX to complete all its pending operations prior to
pushback. If FS2Crew doesn’t detects GSX is doing anything when it comes back to +1
minute, the FA will ask for close doors, and if you say “YES” she will close the door. If icing
GSX integration: Automatically it will disconnect jetway or stairs, depending on if you are
at a terminal gate parking spot or a remote parking area. At this moment, it may display
voice commands, or the secondary button, for allow you to request GSX pushback.
In Voice control, you have the option to respond “NO” if you are not ready to close the door. If
you respond “NO”, the pre-flight event timer will reset to plus 6 minutes. If using Button Control,
you can press the Secondary Button to say “NO”. You have 3 seconds to say “NO”, otherwise the
Captain will automatically respond with “YES”.
Closing the door is the trigger for the crew to perform the BEFORE START PROCEDURE:
+1 Minute: If the Air Start Cart is not connected and the APU is running and on the busses, the
wheel chocks will be automatically removed. The Air Conditioning Cart will also be removed if it
is connected.
• Trigger key phrase is “ALTITUDE.” Example: “ALTITUDE SEVEN THOUSAND / ALTITUDE FLIGHT
LEVEL NINE ZERO.” Ensure this phrase is said clearly and distinctly from the previously
spoken heading value.
• Trigger key phrase is “VEE TWO.” Example: “VEE TWO IS ONE FOUR SIX.” Ensure this phrase
is said clearly and distinctly from the previously spoken VR value.
Click here to learn about PUSHBACK EXPRESS. It is the only MSFS Pushback Program that offers
VOICE CONTROL.
• Announce: “START SEQUENCE IS TWO THEN ONE” unless doing a cross bleed start. If doing a
crossbleed start, see the section further down.
• After you’ve announced the start sequence, use one of the following voice commands to start
engine two:
• At around 25 percent N2, manually move the right fuel control lever to IDLE CUTOFF.
• The FO will call “STARTER CUTOUT” when the START VALVE LIGHT extinguishes.
• Tip: If it is a hot day and you delayed the APU start (if using the APU at all), command the FO to
isolate a pack after engine two stabilizes. This will help get cool air to the passengers since the
engines can cool the plane faster than APU bleed air. Command: “ISOLATE A PACK.”
• Start Engine 1 using the same procedure.
• Note: If doing a cross bleed start, the start sequence would be one then two.
TRANSPONDER AS REQUIRED
RECALL
• After you have called for the Takeoff Flaps, it is time to run the flight controls check. The flight
control check is optional since some airlines do it silently. A config option is available.
• Announce: “CONTROL CHECK” or “FLIGHT CONTROLS CHECK.”
• Move the control column fully left and announce, “FULL LEFT… CENTER.”
• Move the control column fully right and announce, “FULL RIGHT… CENTER.”
• The FO will respond “CHECKED.”
• Perform the same check with the elevators: “FULL UP… FULL DOWN… CENTER.”
• Then rudders: “FULL LEFT… CENTER… FULL RIGHT… CENTER.”
• When done, command “FLIGHT CONTROLS CHECK COMPLETE.” That phrase is the trigger for the FO
to complete the remaining two items in his procedure. DO NOT FORGET TO SPEAK THIS PHRASE OR
THE FO WILL NOT COMPLETE HIS FLOW.
• Now it is time to run the Before Taxi Checklist. Command: “BEFORE TAXI CHECKLIST (PLEASE).” ▪ If
it is night, the FO will turn off the Dome Light at the end of the checklist.
• The FO will turn on the TAXI LIGHT, and, if it is night, the RUNWAY TURN OFF LIGHTS after the
GROUND EQUIPMENT CHALLENGE.
TAXI:
• Announce: “CLEAR LEFT / CLEAR ON THE LEFT.” ▪ The FO will blank the lower screen.
• Taxi to runway.
APPROACHING RUNWAY:
• The FA will notify the cockpit that the cabin is secure. The FO will answer the service interphone
and notify you that the cabin is secure. Note: You cannot take off until the cabin is secure. You may
line up and wait on the runway while waiting for the cabin secure call.
• After the cabin is secure, run the BEFORE TAKEOFF CHECKLIST. Command: “BEFORE TAKEOFF
CHECKLIST (PLEASE).”
If you need to cross any runways, command: “CONFIRM CLEARED TO CROSS RUNWAY XXX /
CONFIRM CLEARED TO ENTER RUNWAY XXX”
• Command “TAKEOFF” after cleared by ATC for takeoff. After takeoff clearance received, set landing
lights to ON.
• Advance the thrust levers to 40%, wait for the engines to stabilize, then press TOGA.
• At this point, the FMAs should be called out. Announce: “N1 TO GA”. Pronounce TOGA as “Tow Ga.”
The PM will reply “CHECKED.” Do not make any more FMA callouts until four hundred feet.
• PM will call “THRUST SET” and “80 KNOTS”.
• When the PM calls 80 Knots, speak “CHECKED” to confirm you are not incapacitated and that the
ASI’s agree.
REJECTED TAKEOFFS
• Command: “REJECT REJECT.”
• If you want to return to the runway, command: “LETS TAXI BACK TO THE RUNWAY.”
• If desired, you make the following voice commands should an evacuation be required: “THIS IS THE
CAPTAIN EVACUATE EVACUATE EVACUATE” or simply “EVACUATE EVACUATE EVACUATE.”
If an autopilot value does not stop when it should, speak “CANCEL LAST COMMAND.”
CLIMB:
• If LNAV was not armed on the ground, engage a lateral mode at four hundred feet. If the autopilot is
on, press LNAV yourself since the MCP is the Pilot Flying’s area of responsibility with the autopilot
on. If the autopilot is off, command: “ENGAGE LNAV / SELECT LNAV / ENAGE HEADING SELECT /
SELECT HEADING SELECT.”
• If not using VNAV and the autopilot is off, command: “SET FLAPS UP SPEED” passing the acceleration
altitude. The PM will then set the Flaps Up Speed in the airspeed window. However, if the autopilot
is on, then you control the autopilot panel and you would set the Flaps Up Speed manually.
• Retract the flaps on schedule using the following commands (assuming takeoff was done at Flaps 5):
“FLAPS 1”, “FLAPS UP / FLAPS ZERO”.
• The PM will start his AFTER TAKEOFF PROCEDURE automatically when the flaps are up and when the
aircraft is above the clean speed.
CRUISE
• If you wish to communicate with the FA, press the CALL ATTD button on the overhead. If you press
the CALL ATTD button, you will hear a chime a few seconds later when the Cabin contacts you.
Speak: “HELLO FLIGHT DECK” to answer the FA. Use the available responses from the bottom of this
manual.
• In cruise, there is not much to do other than monitor the instruments.
DESCENT PROCEDURE
• As you near the Top of Descent, start setting up for the approach.
• Pass control to the PM (“YOU HAVE CONTROL”) and open the APPROACH BRIEF PAGE and make your
selections based on the approach you will fly. If you have any questions about the options on the
Briefing panel, please ask our Discord Channel.
• Playing the approach brief is optional.
• Note: If using Voice Control, you can announce: “ARE YOU READY FOR THE APPROACH BRIEF?” You
must then close the brief by speaking: “ANY QUESTIONS?” If you want to hear a full brief with both
crew members talking, you must use the BRIEF PANEL and press the RUN BRIEF button.
• As the Captain / Pilot Flying, you would typically perform your DESCENT PROCEDURE before or while
doing the brief. It is, however, recommended you do the descent procedure prior to doing the brief
just because it makes things easier.
• Completing the approach brief is the trigger for the First Officer / Pilot Monitoring to perform their
DESCENT PROCEDURE:
DESCENT PROCEDURE
-PILOT FLYING
SET MINS SELECTOR (RADIO IF CATII or III OTHERWISE SELECT BARO)
SET DECISION ALTITUDE/HEIGHT AND SELECT APP/BCRS ON STANDBY/IFSD.
DESCENT PROCEDURE
-PILOT MONITORING
RECALL
SELECT VREF
SET DA/DH ON EFIS PANEL (NOT SIMULATED DUE TO SDK LIMITS)
SET AUTOBRAKE
IF RNAV APPROACH, SET VOR UPDATING OFF
• At the end of the procedure, retake control from the PM: “I HAVE CONTROL”.
DESCENT CHECKLIST
• The Descent checklist should be completed before the airplane descends below 10,000 MSL for
arrival. Generally, though, you would run it prior to the Top of Descent.
• Command: “DESCENT CHECKLIST (PLEASE).”
APPROACH
• After passing the Transition Level, Command: “APPROACH CHECKLIST (PLEASE).”
Example response. 2992 SET. 1013 SET. You must say “SET” at the end or the FS2Crew Mode will not
change to the next mode.
• Passing 10,000 feet (unless otherwise selected on the FS2Crew CFG Options page), the PM will turn
on the fixed landing lights, the logo lights as required and set the seatbelts signs to on.
• If AUTOLAND was selected in the APPROACH BRIEF for the APPROACH TYPE, the PM will turn on the
APU for electrical redundancy.
• At approximately ten thousand feet above the arrival airport elevation, the PM will make a PA:
“CABIN CREW PREPARE FOR LANDING.”
• At approximately five thousand feet above the arrival airport, the FA will notify the cockpit that
the cabin is secure.
If you can see the runway and you wish to continue visually, announce: “VISUAL.” That will change
the Approach Type to Visual. Then command: “CANCEL THE BAROS/ RESET THE BAROS.” You should
then press the RST button on your MINS selector. The PM will stop making callouts relevant to the
instrument approach. Note: On a Visual and sometimes on a VNAV/IAN approach (especially in hot
conditions), you should call “CYCLE FLIGHT DIRECTORS” or “RECYCLE THE FLIGHT DIRECTORS” after the
autopilot is disengaged.
• When the Glideslope comes alive, command: “GEAR DOWN FLAPS 15”. Arm the speed brake.
• The PF will warn you if the speed brakes are still up with Flaps 15 set.
• When the Radar Altimeter comes alive, the PM will make a PA: “CABIN CREW TAKE YOUR SEATS.” ▪
At Glideslope capture, command: “FLAPS 30” or “FLAP 40” as desired.
• Assuming the autopilot is on, manually set the Missed Approach Altitude in the MCP at Glideslope
Capture. If the autopilot is off, command the PM to set the Missed Approach Altitude. Command:
“SET MISSED APPROACH ALTITUDE.”
• If autopilot not engaged, command: “SET VREF PLUS ___”
• If autopilot engaged, manually set VREF plus additive in the MCP speed window.
• Passing the Outer Marker or FAF/FAP, the PM will call “OUTER MARKER / FINAL APPROACH FIX,
HEIGHT CHECKED, MISSED APPROACH ALTITUDE SET.” Reply: “CHECKED.”
• After the final landing flap has been selected, command: “LANDING CHECKLIST.”
GO AROUND PROCEDURES
• Push the TO/GA switch
• Command: “GO AROUND.” After thrust confirmed increasing, call “FLAPS 15”. ▪ After the PM
announces, “POSITIVE RATE,” Command: “GEAR UP.” ▪ The PM will select landing gear up.
• At or above four hundred, select or call for a lateral roll mode.
• At the acceleration altitude, Command: “SET FLAPS UP SPEED” if VNAV is not engaged.
• Retract the flaps on schedule and call for the “AFTER TAKEOFF CHECKLIST.”
ROLLOUT
• The PM will announce the status of the speed brakes and reverses. “SPEED BRAKE UP/ NOT UP/
REVERSES NORMAL.”
• The PM will call “60 KNOTS”. Command: “CHECKED.”
• The PM will call auto brakes disarmed. Command: “CHECKED.”
AFTER LANDING
To trigger the FO’s after landing flow, position the speed brake down or speak “OKAY TO CLEAN UP”.
Note: If, in the APPROACH BRIEF, you selected POWER/AIR: APU (DELAYED START), the FO will NOT
start the APU on his own. You will need to tell him when to start the APU. Command: “START THE
APU.”
If, in the APPROACH BRIEF, you selected POWER/AIR: APU (A.LDG PROC), the FO will start the APU
on his own during his After Landing flow.
TAXI IN
• If you require APU power, and if you did not select the FO to automatically turn on the APU during
the AFTER LANDING PROCEDURE in the APPROACH BRIEF, command “TURN ON THE APU / START
THE APU” when desired. Turn it on as late as possible to save fuel.
• If desired, shut down engine number two to save fuel. See the Engine Shutdown procedure
described after the SINGLE ENGINE TAXI section in this tutorial found further down.
• Just prior to turning into the gate or stand, command: “LIGHTS AND DOORS.” The FO will turn off
the taxi and runway turnoff lights and make the following PA: “CABIN CREW DISARM DOORS AND
CROSSCHECK.”
IF AIRCRAFT MOVING:
IF AIRCRAFT STATIONARY:
• Put your mouse on the number two start lever and announce: “ENGINE START LEVER
NUMBER TWO CONFIRM.”
• The FO will respond “CONFIRMED.” • Manually set FUEL LEVER #2 to CUTOFF.
GATE/STAND ARRIVAL
• When you park at the gate or stand, set the parking brake, and ensure the taxi light is off.
• THE TAXI LIGHT MUST BE OFF as it is a necessary condition for the FO’s shutdown flow to initiate.
• If the three minute engine cool down time has not been reached, the FO will announce that
three minutes have not been reached. If the APU is not on the bus or no Ground Power is
available, the FO will announce that no power is available.
• Visibly check that you have a power source before turning off the engines, either APU or GPU!
When the shutdown procedure is complete, call for the SHUTDOWN CHECKLIST. Command:
“SHUTDOWN CHECKLIST.”
Note: If you want to make a second flight, you do NOT need to reload the aircraft. Instead, press the PRE
FLIGHT EVENTS button again.
GSX integration: After completing the Shutdown checklist, FS2Crew will automatically call for De-
boarding process.
SECURE PROCEDURE
-FIRST OFFICER
IRS’S OFF
EMERGENCY EXIT LIGHTS OFF
WINDOW HEAT OFF
PACKS OFF
SUPPLEMENTARY VOICE
COMMANDS
GENERAL COMMANDS:
If the autopilot is engaged, as the Pilot Flying only you should touch the MCP panel. If you update an
autopilot value, you should announce your selection as part of good CRM.
• HEADING ___
• SPEED ___
• ALTITUDE ___
• FLIGHT LEVEL ___
• VERTICAL SPEED DOWN / UP ____
• SPEED INTERVENE
• ALTITUDE INTERVENE
• BUG UP/ 1 / 5/ 10/ 15 / 25 (Autopilot must be on)
GPWS INHIBIT:
FMC:
• SET WIPERS ON
• SET WIPERS OFF
Note: There is an Approach Brief option to have the GPU and AC Unit connect automatically during Gate
Arrival.
Note: To communicate with the Ground Crew, your audio panel must be set up properly.
CAPTAIN'S AUDIO CONTROL PANEL - ENSURE 'SVC' IS PRESSED IN AND THE VOLUME
IS UP
Note: If using Button Control, press the Ground Call button on the overhead to call the FA.
FA IN FLIGHT CONVERSATIONS
• HELLO FLIGHT DECK (ONLY AFTER CHIME IS HEARD WHEN FA CALLS YOU)
• ONE COFFEE PLEASE
• ONE TEA PLEASE
• SOME LUNCH PLEASE
• SOME DINNER PLEASE
• SOME BREAKFAST PLEASE
• ONE JUICE PLEASE
• ONE WATER PLEASE
• I WILL KEEP YOU UPDATED
• I WILL KEEP YOU IN THE LOOP
• I WILL KEEP YOU INFORMED
FMA CALLOUTS:
• N1
• MCP SPEED
• THROTTLE HOLD
• VOR ARMED
• LOCALIZER ARMED
• LOCALIZER
• VOR
• LNAV
• ROLLOUT
• ARM
• ROLLOUT ARMED
• FLARE ARMED
FA IN FLIGHT CONVERSATIONS
• HELLO FLIGHT DECK (ONLY AFTER CHIME IS HEARD WHEN FA CALLS YOU)
• ONE COFFEE PLEASE
• ONE TEA PLEASE
• SOME LUNCH PLEASE
• SOME DINNER PLEASE
• SOME BREAKFAST PLEASE
• ONE JUICE PLEASE
SUPPLEMENTARY INFO/
PROCEDURES
CABIN PA TRIGGERS:
WELCOME PA: Triggered during Pre Flight events at plus 5 minutes remaining.
TAXI PA: Triggered when both engines have been started and both are stable.
MEALS PA: Triggered 400 feet below cruise altitude as entered in FMC.
NOTE: You can swap the Cabin PAs with your own audio files so long as the format and file name remain
the same.
Notes:
Switch off the FD and auto throttles for takeoff. Use flap 5 for convenience. Aim for climb speed 180
knots and leave flap at 5. At 1000 AGL start turn at 30 degrees angle of bank - maintaining bank angle
until arriving at downwind heading and hauling back throttles to maintain 180 knots while levelling at
1500 feet AGL.
Up to you whether you set MCP cursor at 180 knots or set Vref+5 now. You are not using the auto
throttle, so the MCP speed is purely a reminder figure rather than an A/T setting. Ensure A/T is switched
off and not just ARM (see FCTM cautionary paragraphs on auto throttle use in ARM mode - Boeing do
not recommend it.)
45 seconds after passing end of runway, turn base 25-30 degrees angle of bank and square off the circuit
because of slower speed of 150 knots. Avoid flying a 5 degree bank angle turn as this is sloppy flying. If
an ILS is available ensure the standby ADI ILS is selected because it gives you earlier glide slope indication
than primary ADI/HSI glide slope.
Flap as required on base and final. Cross the fence at VREF if no wind and use reverse and manual
braking. This gives you the practice at modulating the brakes as a skill rather than always carrying out
autobrake use which can lead to loss of braking technique skills.
For touch and go don't arm the speed brake and don’t use reverse. On touch-down open up to 50-60%
N1. The FO will set the stab trim to 5 units and set Flaps 15. When ready, set take-off thrust and rotate
at VREF which has already been set. Around 1000 feet AGL select flap 5 and aim for 180 knots and
repeat the circuit. Note at no stage was FD, AP or AT used. Minimum talk in the cockpit.
For asymmetric circuit practice simply maintain flap 5 downwind and 180 knots, pull back one throttle to
idle early downwind, set flap 15 VREF and you are on your way again.
-MANUAL END-