Cessna Citation X Honeywell FMZ Flight Management System

tasks, previously performed by navigators and flight engineers. The presence of an FMS reduces the workload in the cockpit, allowing the aircraft to be operated by (usually) just two crew members. To accomplish its assigned tasks, an FMS will interface with many aircraft systems, including engine, fuel, hydraulic, electrical, and navigation devices such as GPS, the on-board Inertial Navigation System, and the “Nav” radios. A Flight Management System is an integration of several components, including: ✓ Multipurpose Control & Display Unit (MCDU) A small screen and touch-keypad that provides the interface through which the pilot operates the FMS. ✓ Flight Management Computer The computer hardware and software that runs the system. This is not visible to the pilot in the cockpit and is usually located elsewhere in the aircraft. ✓ Primary Flight Display (PFD) / Navigation Display (ND) / Engine Indication / Crew Alerting System (EICAS) One or more electronic displays (usually CRT or LCD) that provide the pilot with navigation direction and information, engine performance, and aircraft system information (depending on the mode selected). 5 The X-Plane Citation X Flight Management System The Laminar Research / X-Plane Citation X flight management system resembles the Honeywell FMZ system, which is used in many business jets, including those manufactured by Cessna, Gulfstream, Bombardier, Dassault, and Hawker. Rival systems are built by Thales and Collins. Despite differences, these systems perform many of the same functions. Due to the immense complexity of a real-life flight management system, the version modelled in X-Plane is simplified and does not support every capability. However, the functions necessary to program and execute a flight plan are present, including the use of published arrival and departure procedures (SIDs and STARs) and instrument approaches. The “Pop-Up” MCDU and Radio Panel For convenience, a pop-up MCDU and radio panel is provided in the X-Plane Cessna Citation X. These 2D panels can be moved and sized per the needs of the pilot. For the purposes of this guide, we will present the pop-up MCDU and radio panels only. However, commands may also be input using the same panels built into the 3D cockpit. Invoking, moving, sizing, and closing the “Pop- Up” panels Invoking the pop-up MCDU and radio panels To invoke the pop-up MCDU and radio panels, position and click the mouse-pointer anywhere inside the DISPLAY area of either panel in the 3D cockpit. See highlighted areas in image to left. 6 Moving a pop-up panel To move a pop-up panel to the desired location on your computer screen, first place the mouse-pointer on the outer- frame, as indicated by the arrows. Now click and drag the pop-up panel to the desired location on your computer screen. Re-sizing and closing a pop-up panel Place the mouse-pointer at the top-center of the CDU frame. Two click-spots will appear. The click-spot in the UPPER-LEFT closes the pop-up. The click-spot in the UPPER-RIGHT of the frame invokes “Window” mode. In “Window” mode, the CDU panel can be re-sized by dragging the window frame - in the same manner as any other window supported by your operating system. Clicking the top-center resizes all pop-up panels to their default aspect ratio. 7 Components of the MCDU The Control Display Unit (CDU) provides the interface between the pilot and the flight management computer (FMC). It consists of a display panel, and a series of keys that are grouped together according to their function. Display This panel provides a simple output display to the pilot, allowing him to program the unit, make commands, and select available options. Scratch Pad This area of the MCDU Display is used for keypad input. Inputs made by the pilot are initially displayed here, before a Line Select Key is chosen, to move this text to the appropriate line of the MCDU display (above the scratch pad). Line Select Keys These keys are used to make selections from the options provided alongside them, in the MCDU Display. The keys on the left- side of the unit align with the options on the left-side of the display, and vice- versa. Keypad Used to input text into the scratch pad area on the MCDU display. 8 Page Keys These keys are used to select the page presented in the Display Area. The primary functions of the CDU are grouped by “Page”. This simplifies the presentation and provides a logical workflow to the pilot. Clear Key These key clears text currently displayed in the “Scratch Pad” 9 Programming the CDU In this section of the guide, the pilot will program the CDU with initialization data, followed by a manually input flight plan. The flight plan used in this example originates at EDDS (Stuttgart) and terminates at EDDF (Frankfurt). We will depart runway 25 at EDDS and use the ETAS4B Standard Instrument Departure (SID). The route-segment of the flight plan will be via the “Z12” AIRWAY to TOSTU. We will arrive EDDF via the CHA transition waypoint and the SPES3B Standard Instrument Arrival (STAR), followed by the ILS approach to runway 25. The full route is as follows: EDDS25 ETAS4B KETEG Z12 TOSTU CHA SPES3B ILS25L Important Flight plan waypoints and procedures change over time. The sample flight plan used here may no longer be current, and some of these waypoints may not be available for selection during your flight. Therefore, it is not recommended you attempt to duplicate these steps in X-Plane - but instead use the examples below as guidelines for inputting and managing your own flight plan. Loading a previously saved flight-plan is discussed later in this guide, in the section Loading a (saved) Flight Plan. 10 Flight Plan (FPL) Page The “FPLN” button is used to invoke the FLIGHT PLAN (FPL) page, for inputting and displaying the route and procedures for the upcoming flight. Click the FPL button to invoke the FLIGHT PLAN page. This page is used to input and display the: ✓ Departure procedure ✓ Arrival procedure ✓ En-route flight plan 11 Origin Airport Input the origin airport code into the scratch pad. Click the line-select key adjacent to ORIGIN to populate this. Destination Airport Input the destination airport code into the scratch pad. Click the line-select key adjacent to DEST to populate this. 12 Programming the Departure Hint: Click the FPL Page Key to invoke the Flight Plan page if the ‘Departure’ option is not already presented. Click the line-select key adjacent to ‘DEPARTURE’. Click the line select key adjacent to the desired runway. In this example, we are departing on runway 25. Hint: Use the PREV and NEXT Page Keys to scroll the desired runway into view if needed. 13 Selecting a Standard Instrument Departure (SID) Standard instrument departure (SID) routes, also known as departure procedures (DP), are published flight procedures followed by aircraft on an IFR flight plan immediately after takeoff from an airport [Source Wikipedia] Select the desired Standard Instrument Departure (SID) for the chosen runway. In this example, we will be following the ETAS4B procedure. Hint: Use the PREV and NEXT Page Keys to scroll the desired runway into view if needed. Selecting a Standard Instrument Departure (SID) Transition Note: None of the departure procedures at EDDS have transitions, so the example below is fictional. The transition waypoints shown in the example below are (in reality) for a different airport. FICTIONAL Standard instrument departure (SID) routes often feature en-route transition waypoints. When these are present, the flight crew will be presented with multiple options and should select the transition waypoint that is in the direction of the intended flight plan. This joins the departure procedure to the first waypoint of the en- route portion of the flight plan. Click the line-select key adjacent to the desired transition waypoint. In this example, the transition waypoint is PHASE. The chosen runway, procedure and transition will be displayed as confirmation. 14 Committing the Flight Plan The REVIEW option is displayed alongside a line-select key. You may use this function to review the departure procedure, without committing. Click the line-select key adjacent to REVIEW. The waypoints comprising the procedure are displayed. Hint: Use the PREV and NEXT Page Keys to scroll waypoints into view if needed. Click the ACTIVATE line select key to commit the procedure. Click the CLEAR line select key to back out without committing. 15 Inputting en-route waypoints Note: The use of waypoint KETEG is for convenience and would normally be useful only for a different flight plan. When the en-route segment of your flight plan consists of one or more waypoints, these may be input individually. [STEP 1] Click the FPL button to invoke the flight plan page. [STEP 2] Scroll the display until the next unused waypoint in the flight plan is visible. Hint: Use the up-arrow, or down-arrow buttons to scroll the additional content into view. [STEP 3] Input the waypoint identifier into the scratch pad. [STEP 4] Click the line-select key adjacent to VIA.TO to insert the waypoint into the flight plan. Repeat STEP 2 thru STEP 4 for each additional waypoint. 16 Inputting en-route airways When the en-route segment of your flight plan consists of one or more airway segments, these may be input individually. [STEP 1] Click the FPL button to invoke the flight plan page. [STEP 2] Scroll the display until the next unused waypoint in the flight plan is visible. Hint: Use the up-arrow, or down-arrow buttons to scroll the additional content into view. [STEP 3] Input the airway identifier and destination waypoint (on that airway) into the scratch pad in the format: Airway.Waypoint (or Airway.Waypoint.Airway – unique to the Honeywell FMZ) [STEP 4] Click the line-select key adjacent to VIA.TO to insert the airway segment into the flight plan. Every waypoint along the specified airway will be automatically inserted into the flight plan, up to and including the final waypoint specified in STEP 3. 17 Inputting Pilot Waypoints Note: The waypoint included in this example is not part of the intended flight plan and is used for demonstration purposes only. Pilot defined waypoints may be included in your flight plan where needed. These are waypoints that do not have official identifiers, and are created by the flight crew by inputting the specific latitude and longitude in the format: N / S Degrees, Decimal Minutes E / W Degrees, Decimal Minutes Example: N 1 ° 1.1 E 150 ° 59.9 would be input as… N0101.1E15059.9 [STEP 1] Click the FPL button to invoke the flight plan page. [STEP 2] Scroll the display until the next unused waypoint in the flight plan is visible. Hint: Use the up-arrow, or down-arrow buttons to scroll the additional content into view. [STEP 3] Input a fictional pilot waypoint identifier into the scratch pad [STEP 4] Click the line-select key adjacent to VIA.TO [STEP 5] Input the latitude and longitude of the chosen waypoint into the scratch pad. 18 [STEP 6] Click the line select key adjacent to LAT LON to add the waypoint to the en-route waypoints database. [STEP 7] Follow the steps for Inputting en-route waypoints to insert the waypoint into your flight plan. 19 Saving a Flight Plan Saved flight plans are stored in the Output/FMS Plans folder. Flight plans may be saved for use again later. A saved flight plan in X-Plane uses a. fms extension. Important: A feature of the Honeywell FMZ system is that flight plans may not be saved once they have been closed (see: Closing the Flight Plan). This is how the real device operates, and therefore this restriction applies in X-Plane. [STEP 1] Click the FPL button to invoke the flight plan page. [STEP 2] Scroll to the end of the flight plan. The SAVE ACTIVE FLT prompt is now visible. Hint: Use the up-arrow, or down-arrow buttons to scroll the additional content into view. [STEP 3] Input the flight plan file name into the scratch pad (without any pathname, as shown in this example). [STEP 4] Click the line-select key adjacent to PLAN TO. This will save the flight plan using the filename specified in the Output/FMS Plans folder. 20 Closing the Flight Plan The Honeywell FMZ system requires that you ‘close’ the flight plan before programming the arrival. This is accomplished by selecting the destination airport code as the final waypoint in the flight plan. [STEP 1] Click the FPL button to invoke the flight plan page. [STEP 2] Scroll the display until the next unused waypoint in the flight plan is visible. Hint: Use the up-arrow, or down-arrow buttons to scroll the additional content into view. [STEP 3] Click the line-select key adjacent to DEST to populate the scratch pad with the destination airport code. [STEP 4] Click the line-select key adjacent to VIA.TO to insert the destination airport code as a waypoint in your flight plan. 21 Performance Initialization (PERF) Page Group The “PERF” (Performance) key is used to initialize the performance parameters used by the flight management system for the duration of the flight. Hint: The flight plan must be closed for these entries to have any effect. Note: Failure to input performance data may lead to unpopulated data in other FMS pages. Click the PERF button followed by the PERF INIT button to invoke the first of five PERFORMANCE INIT pages. These are used to change the default computation parameters used by the FMS. PERFORMANCE INIT Page 1 / 5 ✓ Information only Hint: Use the NEXT and PREV buttons to cycle through the pages. PERFORMANCE INIT Page 2 / 5 This page supports the option to change: ✓ Climb speed and Mach number ✓ Cruise speed and Mach number ✓ Descent speed, Mach number and default vertical path angle The FMS will pass these values to the flight director (for display) when the autopilot is engaged in VNAV mode. Note: The Citation X doesn’t have an auto-throttle, so thrust must always be set by the crew. Hint: Input the new data (into the scratch pad) in the same format as currently populated, and then click the adjacent line-select key. PERFORMANCE INIT Page 3 / 5 This page supports the option to change: ✓ Step Climb Increment (thousands of feet) A step-climb is a series of incremental altitude changes that occur when the aircraft performance allows (due to fuel burn). This parameter defines the increment that will be used by the FMS to compute when the next step climb is feasible. Hint: Input the new data (into the scratch pad) in the same format as currently populated, and then click the adjacent line-select key. 22 Programming the Arrival Note: The Honeywell FMZ system requires that you ‘close’ the flight plan before programming the arrival. This is accomplished by inputting the destination airport code as the final waypoint in the flight plan. See: Closing the Flight Plan [STEP 1] Click the NAV button to invoke the NAV INDEX page. [STEP 2] Click the line-select key adjacent to ARRIVAL. [STEP 3] Click the line-select key adjacent to RUNWAY. [STEP 4] Select the desired arrival runway. In this example we will be using runway 25L. Hint: Use the up-arrow, or down-arrow buttons to scroll the additional content into view. 23 [STEP 5] Select the desired approach type. In this example we will be using the ILS to runway 25L. Hint: Use the up-arrow, or down-arrow buttons to scroll the additional content into view. [STEP 6] Select the desired transition waypoint. In this example we will be using CHA. Hint: Use the up-arrow, or down-arrow buttons to scroll the additional content into view. Note: Transition waypoint CHA is for non-RNAV aircraft and is used here for convenience. A more likely transition waypoint for this aircraft and flight plan would be DF626, followed by a short-cut from ATC. Continued in next chapter: Selecting a Standard Instrument Arrival (STAR) 24 Selecting a Standard Instrument Arrival (STAR) Continued from previous chapter: Programming the Arrival [STEP 7] Select the STAR (Standard Arrival) procedure. In this example we will be using SPES3B. Hint: Use the up-arrow, or down-arrow buttons to scroll the additional content into view. [STEP 8] The runway, transition, approach type and arrival procedure (STAR) are displayed for confirmation. Hint: Use the PREV and NEXT Page Keys to scroll waypoints into view if needed. Click the ACTIVATE line select key to commit the procedure. 25 Clearing Discontinuity Messages Use the up-arrow, or down-arrow buttons to scroll the >>DISCONTINUITY<< message into view. Click the DEL button to enable the DELETE function. Click the line-select key adjacent to the waypoint immediately above the >>DISCONTINUITY<< message to remove this and stitch together the flight plan waypoints immediately above and below. The two waypoints either side of the >>DISCONTINUITY<< are now joined together. 26 Altitude Constraints When altitude constraints are in effect, these are displayed adjacent to relevant waypoints of the flight plan. Altitudes displayed in small font are computed by the FMS using performance data. Constraints displayed in large font (shown here) are sourced from the specific departure or arrival procedure to which that waypoint belongs. These always take precedent over computed constraints. When the autopilot is in VNAV mode, and during a climb phase of the flight, the crew may set a top of climb altitude using the Altitude Select Rotary, and the FMS will command climbs to each of the altitude constraints in the flight plan, as the associated waypoint is reached. Note that the FMS will never command a climb beyond the altitude set by the Altitude Select rotary. When the autopilot is in VNAV mode, and during a descent phase of the flight, the crew may set a bottom of descent altitude using the Altitude Select Rotary, and the FMS will command descents to each of the altitude constraints in the flight plan, as the associated waypoint is reached. Note that the FMS will never command a descent below the altitude set by the Altitude Select rotary. Note: The Citation X has no auto-throttle. During climb the crew must advance the throttle to the CLB (Climb) position and retard it to the CRZ (cruise) position for level flight or retard the throttle further to comply with any speed restriction in level flight. During descent, the crew must manually adjust the throttle to maintain the desired airspeed. 27 Manual Input of Altitude Constraints Altitude constraints may be manually input by the crew for a given waypoint, or waypoints. [STEP 1] Click the FPL button to invoke the flight plan page. [STEP 2] Scroll the display until the next unused waypoint in the flight plan is visible. Hint: Use the up-arrow or down-arrow buttons to scroll the additional content into view. [STEP 3] Input the desired altitude constraint expressed as thousands of feet or a flight level (e.g. FL180) [STEP 4] Click the line-select key adjacent to the waypoint to which the altitude constraint applies. 28 Speed Constraints Note: The speed constraint included in this example is fictional and is used for demonstration purposes only. When speed constraints are in effect, these are displayed adjacent to relevant waypoints of the flight plan. Constraints displayed in small font (shown here) are computed by the FMS using performance data. Constraints displayed in large font are sourced from the specific departure or arrival procedure to which that waypoint belongs. These always take precedent over computed constraints. The Citation X does not feature an auto-throttle, and therefore speed constraints during descent are for information only and must be managed by the crew. 29 Manual Input of Speed Constraints Speed constraints may be manually input by the crew for a given waypoint, or waypoints. [STEP 1] Click the FPL button to invoke the flight plan page. [STEP 2] Scroll the display until the next unused waypoint in the flight plan is visible. Hint: Use the up-arrow or down-arrow buttons to scroll the additional content into view. [STEP 3] Input the desired speed constraint in the format shown in the example. [STEP 4] Click the line-select key adjacent to the waypoint to which the speed constraint applies. 30 Reviewing the completed Flight Plan MCDU Review Click the FPL button to invoke the ACTIVE FLT PLAN page. Use the NEXT button to scroll through each waypoint in the plan 31 Note the location of any speed and altitude constraints in the flight plan. Note also the missed-approach waypoints at the end of the flight plan - should the landing be aborted. 32 MFD Review Examine the shape of the flight plan on the Multi-Function Display (MFD) to ensure it corresponds with your Electronic Flight Bag (EFB) or other documentation. For instructions using the MFD, see: https://x-plane.com/manuals/Citation_X_Pilot_Operating_Manual.pdf 33 Direct to a waypoint Sometimes during the flight, the need will arise to proceed directly to a waypoint, thus skipping those that preceded it. [STEP 1] Click the DIR ( Direct To ) button. [STEP 2] Scroll the display until the relevant segment of the flight plan is visible. Hint: Use the up-arrow, or down-arrow buttons to scroll the additional content into view. [STEP 3] Click the line-select key adjacent to the desired waypoint. This will become the next (and de facto first) waypoint in your flight plan. Hint: You may need to scroll the waypoint back into view using the up-arrow, or down-arrow buttons. 34 Inserting a waypoint into an existing flight plan Sometimes during the flight, the need will arise to insert an additional waypoint (or waypoints) into the flight plan. This can happen following an instruction from ATC, or a request by the flight crew. Manually input waypoints may be added to the flight plan as follows: [STEP 1] Click the FPL button to invoke the flight plan page. [STEP 2] Scroll the display until the relevant segment of the flight plan is visible. Hint: Use the up-arrow, or down-arrow buttons to scroll the additional content into view. [STEP 3] Input the new waypoint identifier into the scratch pad. [STEP 4] Click the line-select key adjacent to the waypoint immediately prior to the new waypoint. The new waypoint is added to the flight plan, as shown in the example here. 35 Deleting a waypoint from an existing flight plan Individual waypoints may be deleted from the flight plan as follows: [STEP 1] Click the FPL button to invoke the flight plan page. [STEP 2] Scroll the display until the relevant segment of the flight plan is visible. Hint: Use the up-arrow, or down-arrow buttons to scroll the additional content into view. [STEP 3] Click the DEL (Delete) button. [STEP 4] Click the line-select key adjacent to the waypoint to be deleted. The waypoint is removed from the flight plan, as shown in the example here. 36 PROGRESS Page Group Click the PROG button to invoke the first of three PROGRESS pages. These provide real-time data as the progress of the flight unfolds. PROGRESS Page 1 / 3 ✓ Next Waypoint Identifier ✓ Distance to next waypoint ✓ Estimated time to next waypoint ✓ Fuel remaining at next waypoint ( x 1000 lbs. ) Hint: Use the NEXT and PREV buttons to cycle through the pages. PROGRESS Page 2 / 3 ✓ Distance to Top of Climb (TOC) if specified in flight plan ✓ Distance to Top of Descent (TOD) if specified in flight plan ✓ Remaining Fuel Quantity ✓ Gross Weight ( lbs.) Hint: Use the NEXT and PREV buttons to cycle through the pages. PROGRESS Page 3 / 3 ✓ Cross Track (XTK) Error The deviation distance ( nautical miles ) from the desired course track ✓ Current Ground Track ( degrees ) ✓ Current Heading ( degrees ) ✓ Drift ( difference between heading and track in degrees ) ✓ Computed wind direction ( degrees ) and speed ( knots ) ✓ Ground Speed ( knots ) Hint: Use the NEXT and PREV buttons to cycle through the pages. 37 Resetting the Flight Plan [STEP 1] Click the FPL button to invoke the flight plan page. [STEP 2] Scroll the display until the relevant segment of the flight plan is visible. Hint: Use the up-arrow, or down-arrow buttons to scroll the additional content into view. [STEP 3] Input a new origin into the scratch pad. [STEP 4] Click the line-select key adjacent to ORIGIN. 38 Loading a (saved) Flight Plan Saved flight plans are stored in the Output/FMS Plans folder. Flight plans that have been generated previously (and saved in the appropriate format for X-Plane) may be loaded into the Flight Management System. The following file (extension) types are acceptable: ✓ FLP (compatible with aircraft for both X-Plane and other simulators, supports airways) ✓ FMS (compatible with X-Plane, with support for airways and procedures) [STEP 1] Click the FPL button to invoke the flight plan page. [STEP 2] Click the line-select key adjacent to FPL LIST. [STEP 3] Click the line-select key adjacent to the file name of the desired flight plan. 39 [STEP 4] Click the line-select key adjacent to ACTIVATE.