Working Title CJ4 v0.12.13 | Operator’s Guide Table of Contents |
Cessna Citation CJ4 Model 525C Operator’s Guide (0.12.13)
THIS GUIDE IS INTENDED FOR USE IN FLIGHT SIMULATION ONLY.
NOT FOR USE IN REAL WORLD AVIATION.
Flight Plan Synchronization Between the Game and FMS 2
TAKEOFF AND LANDING V-SPEEDS 2
5 - FLIGHT MANAGEMENT SYSTEM 1
HOPPIE LOGON CODE - NOT IMPLEMENTED - WIP 4
6 - AUTOPILOT OPERATION LIMITATIONS 1
FLIGHT GUIDANCE SYSTEM DISPLAY (SCOREBOARD) 3
PFD - PRIMARY FLIGHT DISPLAY 1
MFD - MULTI-FUNCTION DISPLAY 11
Fig 7.14 - UPPER MFD CHECKLIST 16
MAP-SRC - Always FMS1 on the MFD. Cannot be changed. 17
▶ SYS TEST - NOT IMPLEMENTED 19
ELECTRONIC CHARTS (E-CHARTS) 22
THIS PAGE HAS BEEN INTENTIONALLY LEFT BLANK
This is a guide for the Working Title CJ4 Mod. It contains some necessary information regarding normal procedures and avionics including the Collins Pro Line 21 suite. It will be updated as necessary to include all current, working features.
The Working Title Team are strictly volunteers who all share a passion for flying. Aside from software engineers, the team is composed of real-world pilots with ratings from Private to Airline Transport, including several members with experience on the actual Cessna CJ4 and similar types.
Thank you for your support!
CURRENT VERSION: 0.12.13
You can always find your current version in the FMS by going to IDX>NEXT(PAGE 2)>ABOUT
The latest version of the CJ4 Mod can be found here: https://github.com/Working-Title-MSFS-Mods/fspackages/releases
The Working Title CJ4 is compatible with both the default NAVBLUE data or the Beta version of Navigraph for MSFS. (No special modifications are required for compatibility with Navigraph)
If you would like to contribute, or file a bug report, please do so here:
https://github.com/Working-Title-MSFS-Mods/fspackages
If you are filing a bug report, please be sure to include as much information, including pictures and video if possible, in order for us to track down and replicate the problem.
Our Discord can be found here: https://discord.gg/cmxCRJX8jG
Installation is easy, simply copy the workingtitle-aircraft-cj4 folder inside the zip file to your MSFS Community folder. Ensure you are downloading the workingtitle-aircraft-cj4-v0.X.X.zip and NOT the Source Code!
Important: We recommend that you fully delete any previous workingtitle-aircraft-cj4 folder before copying this release.
(Your installation path may differ.)
NOTE: The Installation will not add a new aircraft. This is a modification of the default Cessna CJ4. |
The alternate default liveries that now ship with MSFS are not compatible with the CJ4 yet at this time. They currently ship with panel.cfg files that do not include our FADEC module. Please use the standard livery or a known compatible 3rd party or community livery. Compatible liveries can be found in #media in our discord or here:
https://docs.google.com/spreadsheets/d/1-FZh5ZNXsSoHZFRcvkQwa-PHuBSk1QRTt7eYvx7Q4xU/edit?usp=sharing
For a more complete list of issues being tracked, please visit our GitHub page: https://github.com/Working-Title-MSFS-Mods/fspackages/issues
Configuring the FMC for Simbrief import.
THIS PAGE HAS BEEN INTENTIONALLY LEFT BLANK
The real CJ4 is only rated for operation on ‘paved surfaces’ (runways), however because of the magic of MSFS, feel free to take off and land anywhere you’d like.
Maximum Ramp Weight | 17,230lbs |
Maximum Takeoff Weight (MTOW) | 17,110lbs |
Maximum Landing Weight (MLDW) | 15,660lbs |
Zero Fuel Weight (ZFW) | 12,500lbs |
MMO (Above 27,884 feet) | Mach 0.77 (indicated) |
VMO (Between 8000 and 27,884 feet) | 305 KIAS |
VMN (Below 8000 feet) | 260 KIAS |
Maximum Flap Extended Speed - VFE
15 Degrees | 200 KIAS |
35 Degrees | 160 KIAS |
Maximum landing gear extended speed - VLE | 200 KIAS |
Minimum speed for sustained icing conditions | 160 KIAS |
Maximum landing tailwind | 10 KTS |
Maximum demonstrated crosswind | 25 KTS |
Maximum N1(%) | 104.4% |
Maximum sustained TO power | 5 minutes total per engine start/stop cycle |
The CJ4 is certified for CAT I ILS or LPV/WAAS approaches with no less than 200’ AGL minimums. BARO minimums must be used for all CAT I, LPV and other approaches. RNP AR approaches are not authorized.
THIS PAGE HAS BEEN INTENTIONALLY LEFT BLANK
Full checklists have been implemented on the MFD – you can access them from the UPR MENU or the CKLIST button on the panel below the left MFD. This SOP is not a replacement for the checklists.
A PDF Version of the checklist is available here courtesy of Discord user SeeBread: https://cdn.discordapp.com/attachments/767761280366805022/792995990659399700/WT_CJ4_Checklist.pdf
Starting the engines in the CJ4 is a very simple task. Once the BATTERY is on, it requires no other configuration other than simply pressing the L or R ENGINE STARTER button and then without delay, pressing the L or R ENGINE RUN/STOP switch. Once the ENGINE STARTER button has been pressed, the STOP indication under the button guard will disappear and once pressed, will switch to RUN indicating that the start process has been initiated.
Monitor the MFD for the following indications:
Repeat the process for the other engine.
The FMS PERF pages provide for takeoff and landing V-Speeds, and these can be pushed to the PFD from the FMS on the relevant pages. A departure and arrival runway must be selected through the DEP/ARR button on the FMS prior to attempting to use the respective PERF page in the FMS.
These V-Speeds are influenced by flap settings, weight and other parameters that can be set in the FMS. VAPP and VREF do not account for any gust or wind factor on approach. If you are landing in windy, gusty or icing conditions, you can add a safety margin to your VAPP and VREF speeds by pressing the REFS MENU above the PFD and manually adjusting any of the V- Speeds.
V-Speeds set by the FMS will be colored MAGENTA and those manually set or adjusted will be CYAN on the PFD.
A standard wind/gust factor addition of half the headwind component plus the gust value is recommended. DO NOT add more than 15 kts to the VAPP speed.
NOTE: Be sure to complete the PERF INIT page and set up the weights according to how the aircraft is loaded, otherwise your V-Speeds will be inaccurate - these do not calculate based on sim weights, but rather what the pilot inputs - just like the real aircraft! |
The recommended takeoff procedure is in addition to completing the checklists.
Takeoff can be performed from either a rolling takeoff, without stopping after entering the runway, or as a static takeoff. For a static takeoff, hold the brakes and release them as the engine begins to spool up. Performance is generally not affected whether performing a static or rolling takeoff. For shorter airstrips, a static takeoff is preferred to ensure enough runway remains within the safety margins.
NOTE: The TOGA button is normally found on the sides of the throttle but is currently INOP in the sim. The workaround is a shortcut we mapped to the FIRE BOTTLE directly under L ENG FIRE button - click to enable it. It can also be bound to a key or hardware switch.
Manage pitch angle to accelerate smoothly and when passing about 200 KIAS, you can enable the Autopilot (AP) – this is a personal choice, some will prefer to fly manually to 240 KIAS and then engage the AP to avoid having FLC pitch down for acceleration, others may wish to turn things over to the AP sooner. Anything above 200 kts should work fine for FLC, the aircraft will reduce climb to reach 240 KIAS, then pitch up to maintain that speed through the climb.
NOTE: Minimum Autopilot (AP) or Yaw Damper (YD) engagement altitude after takeoff or go around is 300’ AGL.
NOTE: Real-world procedures limit FADEC in TO Mode to 5 minutes maximum per flight.
Climb should be conducted using FLC at 240 KIAS/M0.64 - monitor Mach and IAS and after the crossover, maintain M0.64 (switched automatically). The newly implemented FADEC will manage climb power all the way to cruising altitude. You can expect climb rates in the 3,000-5,000 fpm range below 20,000’ and in the 2,000-3,000 fpm range in the 20,000s. In the FL300s, you can expect climb rate to be around 2,000 fpm decreasing with altitude.
Upon reaching cruise altitude you can use the throttle to set power to maintain your desired cruise speed, up to MMO/VMO. In the real aircraft, any throttle setting besides TO can be used during cruise. There is no detent for CRU, nor does the CJ4 have auto-throttle -- speeds are managed by the pilot. Monitor fuel flow, range and time to reserve on the FMS PERF pages.
Descent can be conducted on a 3° flight path; this rate of descent can be estimated by multiplying your ground speed by 5, so at ground speed of 450 kts, a rate of descent of 2,250 fpm would give you ~3° descent. You can elect to descend faster, rates of up to 3000 fpm can be used, especially from cruise altitude.
Top Of Descent (TOD) can be calculated roughly for a 3° flight path by taking the difference between your current altitude and landing altitude, multiplying by 3 and dividing by 1000. So, for example, if you’re cruising at 45,000’ and you’re landing in Denver at about 5,000’, then 45000-5000 = 40000; 40000 X 3 = 120000; 120000/1000 = 120. So start descent 120 NM from Denver.
You can elect to use either FLC, VS or VNAV to manage your descent; VS mode will allow you to more accurately target your descent to arrive at altitude constraints, but you need to constantly monitor your power settings and speed. Alternatively you can use FLC to descend by setting a target speed not above Vne/Mmo and then adjusting your power settings to achieve the target rate of descent. VNAV is covered at the end of this guide under AUTOPILOT OPERATION.
Allow time to slow to 250 KIAS by 10,000’ and it is not recommended to exceed a 3° descent below 250 KIAS. 3° at 250 KIAS is 1,250 fpm.
Program your approach into the FMS after checking destination weather and, when appropriate, confirming the expected approach from ATC. Attempting to change the approach after an approach has been initiated can result in FMS anomalies and will force you to return to the IAF if flying in LNAV mode.
If flying an ILS approach, use the FMS IDX -> NEXT PAGE -> ARR DATA page to check inbound ILS course and ILS frequency and then confirm the proper ILS frequency is set in the TUN page for NAV1.
Use the PERF FMS page to access the APPROACH REFS page; you will need to enter arrival weather data, such as wind, temperature (degrees C), and altimeter setting (inHG), as well as have an approach and runway selected in DEP/ARR in order for the APPROACH REFS page to work. Once page 1 is completed, hit NEXT to get page 2, where you can send your Vref and Vapp speeds to the PFD. Use the PFD REFS MENU to make any manual adjustments to the approach speeds to account for wind or gust factor.
Slow to 200 KIAS or less prior to initiating the approach and slow to no greater than 160 kts by FAF. For a precision approach it is recommended to be at Vapp by the FAF.
The Autopilot must be disengaged no lower than 200’ AGL and the yaw damper off before touchdown. When crossing the runway threshold, pull the power smoothly back to idle and initiate flare and landing. Upon landing, deploy the spoilers and use brakes as needed to slow the aircraft. The CJ4 does not have thrust reversers.
Missed approaches can now be activated in the CJ4. A missed approach will automatically be loaded in the FMS if an instrument approach procedure is also loaded. When the TOGA button is pressed, the flight director (FD) will be set and locked to fly the current heading.
The procedure is as follows:
THIS PAGE HAS BEEN INTENTIONALLY LEFT BLANK
Maximum Takeoff Weight (MTOW) | 17,110lbs / 7,761kg |
Basic Operating Weight (BOW) | 10,280lbs / 4,663kg |
Useful Load | 6,830lbs / 2,894kg |
Baggage Capacity | 1,040lbs / 472kg |
Fuel Capacity | 5,762lbs / 2,614kg |
The current, revised flight model provides seating for 7 passengers and 2 crew members. The lavatory seat is not able to be loaded at this time.
NOTE: Our current model does NOT include a pilot in the BOW (Basic Operating Weight)/Empty Weight. They must be included in the passenger total in PERF INIT to get the correct Gross Weight (GWT). |
THIS PAGE HAS BEEN INTENTIONALLY LEFT BLANK
The CJ4 features a Collins FMS-3000(v4.0) as part of the Pro Line 21 Suite of avionics. Not all functions are currently available in MSFS at the moment. Some are just not implemented and may be at a later date, and others are just not possible or relevant in some cases. They will be grayed out in the FMS if they currently have no function or the key may not be active.
These sections on the FMS will cover many of the basic operations but will not cover every detail, especially if it is not relevant to the simulation environment. It is an ongoing, work in progress.
This page on the FMS contains a number of user defined settings which will persist after each load (when the SIM is exited correctly through the menus).
The MOD SET can be accessed via IDX>NEXT>MOD SET
NOTE: THIS DOES NOT CHANGE THE PFD UNITS. That must be done through the PFD MENU (Section 7-6). |
NOTE Working Title at no time has any access to personal information in this exchange. It is an OAuth Device Authorization Flow for which the CJ4 simply asks Navigraph for an access/refresh token once they verify the account through the weblink. All of this is stored locally on the user’s machine. |
Click “Yes, Allow” to receive an access token from Navigraph servers.
Once you see the above message “Code is approved,” you can close the browser window and switch back to MSFS. NAVIGRAPH should now show LINKED in green underneath it allowing for CHART access on the MFD.
When the FMS first powers on, you will be presented with this STATUS screen. A message will appear on the message line asking to INITIALIZE POSITION so that the aircraft can determine where it is.
NOTE: Valid database dates with Navigraph updates should now show correctly. |
The POS INIT display allows you to initialize where the aircraft is currently. An INITIALIZE POSITION message will appear in the message line on first load until the position is set. To set the position, press LSK 4R to copy the GNSS (GPS) position of the aircraft into the SET POS line. The GNSS position will then automatically populate the SET POS line along with a COMPLETED message above it. The position of the aircraft should now be initialized. Many features of this page are not yet functional as the sim knows the precise position of the aircraft at all times.
PERF MENU displays all performance menu options available on the FMS-3000. A more detailed description of each page is outlined in the sections below.
PERF INIT is short for Performance Initialization. This is where initial aircraft performance is input into the FMS for calculating takeoff and landing performance data such as v-speeds and required runway lengths.
The TAKEOFF REF page is where the second part of performance calculations receives variables in order to determine v-speeds and takeoff lengths.
PAGE 1/3
PAGE 2/3
NOTE: The CJ4 does not currently model degraded engine performance when anti-ice is on. |
Once all performance data has been input, v-speeds should automatically appear in the right-hand column. To get them to display on the PFD, press the SEND button. A message IN PROGRESS will appear followed by COMPLETE once the process has finished and they will appear in MAGENTA on the PFD below the speed tape.
PAGE 3/3
Displays additional takeoff weight and limits.
The APPROACH page within the PERF MENU contains input fields for computing landing speeds (VREF, VAPP), and landing distances. The page is arranged and operates in a similar manner to the TAKEOFF page.
PAGE 1/3
PAGE 2/3
NOTE: The CJ4 does not currently model degraded engine performance when anti-ice is on. |
PAGE 3/3
Displays additional landing weight and limits.
The ACT FLPN page is where you begin when building out your flight plan. It is advisable to not program a STAR or approach until the enroute portion of the plan has been completed as this may prevent the entering of airways.
The flight plan in this example is: KCRQ/24 PADRZ2.CHKNN LAX J1 AVE.ROBIE5 KSJC and ILS30L vectors-to-final.
NOTE: An airport inserted into an origin or destination may report as NOT IN DATABASE even if it is valid. If this occurs, you can re-press the corresponding LSK where the error was reported and it should work on the second press, or you may clear the error and retry. |
RULE: VIA will not take user input on page 1 only. Airways must be entered on page 2 or higher. |
RULE: Custom Waypoints will not be accepted in the ACT FPLN page - they must be entered on the LEGS page. |
To enter departure runways, SIDs (Standard Instrument Departures)/DPs (Departure Procedures), STARs (Standard Terminal ARrivals), approaches, and arrival runways, press the DEP ARR key. When pressed, the ACT DEPART page for the airport entered in ORIG will be shown if one is selected. To access the INDEX, use LSK 6L, <DEP/ARR INDEX or the DEP ARR function key. When airborne and more than 50nm, or halfway to the destination, pressing the DEP ARR key will automatically bring you to the ACT ARRIVAL page (This is how the real FMS-3000 operates).
The DEP/ARR INDEX allows for the selection of available procedures for the ORIGIN and DEST airports as entered in the ACT FPLN, as well as the SEC (secondary) FPLN.
NOTE: SEC FPLN is currently not implemented. |
NOTE: The availability of procedures is limited by what is provided in the stock, NAVBLUE data. This can be enhanced through the addition of Navigraph’s more complete database but the stock data is generally sufficient on its own. |
Clicking on <DEP using LSK 1L, will show all available departure procedures as well as available departure runways.
Once on the ACT XXXX DEPART page, select a SID or DP, if desired - not required. The SID/DP will appear under DEPARTURES in green (PADRZ2) with the current list of available TRANS (transitions) underneath it. To select a transition, click the corresponding left LSK. It will also turn green indicating that a transition (CHKNN) has been selected. Repeat the process for the desired runway under the RUNWAYS selection (24). Additional transitions or runways (if available) can be accessed using the NEXT and PREV keys. MOD will appear in the top left corner until EXEC has been pressed.
NOTE: Not all runways are available for a selected SID. Selecting the SID first will show all available runways for that selected SID. Selecting a runway first will show all available SIDs for that selected runway. |
Selecting ARR> on the DEP/ARR INDEX will bring you to the ACT XXXX ARRIVAL page. The process for selecting a STAR/approach is very similar to the DEPART page above.
The main difference between DEPART and ARRIVAL is that on the right, instead of just RUNWAYS, you will see APPROACHES first (if an approach exists at the destination airport), and then RUNWAYS below. Use the NEXT and PREV keys to access additional pages (if applicable). A STAR can be selected without an approach or arrival runway as these are not commonly assigned by ATC until the aircraft is within the terminal range (<50nm).
NOTE: Some STARs may not populate all fixes until a runway or approach has been selected, as the final waypoints may vary depending on landing direction. |
Some approaches may also have transitions. They will appear as TRANS under APPROACHES. The process for selecting an approach transition is similar to that of a SID or STAR.
A visual approach may be used when an instrument approach is not required. To select a visual approach, use the NEXT key to scroll to the end (if necessary) where RUNWAYS are listed. These are simply displayed as RW followed by their number and possibly L, R, or C. The selected runway will be shown in green under RUNWAYS with RWY EXT appearing below it.
RWY EXT allows for the user to input an extension point heading out from the runway for enhanced situational awareness. RWY EXT will allow for values between 1 and 25nm with 5nm being default.
🛑 A visual approach must not be used in Instrument Meteorological Conditions (IMC) as a substitute for an Instrument Flight Rules (IFR) approach. |
From the LEGS page, a runway extension will appear as “RX.” You can then use this to build custom waypoints for even more situational awareness by creating “downwind,” “base,” or “final” legs. You can also choose to delete the “RX” waypoint and no extension will appear.
After entering your flight plan, check the LEGS page to verify that all waypoints and altitude constraints are correct. (LEG WIND is currently INOP and generally not used on the real CJ4)
The ACT LEGS page lists all the waypoints in a flight plan in the left column. The right column, shown as - - -/- - - - - , lists the speed and altitude constraints for the corresponding waypoint in the left column. These are DATA LINES.
- - -/ The first 3-dashes before the / are SPEED constraints. Because the CJ4 does not have an autothrottle, these are for advisory purposes only; the aircraft will not adhere to them.
/- - - - - The last 5-dashes after the / are ALTITUDE constraints and are used by VNAV if enabled.
Valid formats for constraints:
RULE: You can enter a speed constraint without a / up to 499 before it assumes it’s an altitude. Entering 500 or higher will place it after the /. If you like to add an altitude constraint below 500, you must put a / before it (/400). |
The FMS-3000 does not auto-populate cruise data into the right-hand column. The right side is used only for advisory speeds, and VNAV altitude constraints. The VNAV function will calculate the required descent based on your current altitude. Again, cruise data does NOT need to be entered into the right-hand column.
NOTE: User defined segment VPA not yet implemented. |
SEQUENCE - AUTO/INHIBIT - When in AUTO, the FMS will automatically advance to the next waypoint after passing it, and activate the next leg segment. If toggled with LSK 1R to INHIBIT, the FMS will not advance to the next waypoint in the sequence.
At the end of the flight plan, when the aircraft is direct to the runway fix (RWXX), the FMS will automatically switch to INHIBIT. Switching the sequence back to AUTO will activate the missed approach if an instrument approach was selected. (See MISSED APPROACH)
NOTE: If the autopilot remains in FMS NAV mode with INHIBIT selected, the aircraft will continuously circle back to the last waypoint it crossed in magenta. |
Page 1 of ACT LEGS depicts the departure runway and the first several waypoints of our selected SID. LSK 1L and 2L, on page 1, have special properties. Above, we see RW24, our departure runway, as the from fix. Entering any flight plan waypoint on LSK 1L, this from spot, will activate the next leg from that waypoint.
The other special spot is LSK 2L, the to fix. This always depicts which waypoint the aircraft is currently going to. In the above example, the waypoint the aircraft is going direct-to is (2299). As the aircraft passes the to fix, it becomes the from fix. When a manual direct-to is initiated, the FMS creates a new from fix called (DIR). This enables the aircraft to calculate a new course by drawing a line between the two points that the autopilot can follow or intercept. Any valid waypoint, even if it’s not part of the current flightplan, can be inserted into LSK 2L. More information on DIRECT-TO operation is listed in the section below.
To add a waypoint to the LEGS page, enter the waypoint (can be a FIX, VOR, NDB, airport or custom waypoint) into the scratchpad. Press the corresponding left LSK where you would like the waypoint to appear.
Above each waypoint are two sets of numbers. The first number is the leg track bearing and the second number is the distance between waypoints. In the last image above, GILRO is 351° from SNS and 23.0NM. Another way to understand it is that to go from GILRO to JENES, you would fly 304° for 15.0NM.
Several other special waypoints may also appear in the LEGS page.
(VECT) - A radar vector heading from the previous waypoint. The pilot is expected to switch the autopilot to HDG mode and receive radar vectors from ATC.
(2299) - An altitude constraint to cross at, at or above, or at or below. A number in (XXXX) is usually created for departures where an altitude constraint is required but not colocated with a waypoint.
ie. The SID to the right depicts “fly HDG 245 to 2300, expect vectors to GYWNN.” From RW24 to (VECT) is a 245° heading (displayed above the vector) with a (2299) altitude constraint. (The graphical SID actually depicts 2300 or above.)
▯▯▯▯▯ = Discontinuity. A discontinuity is a break in the flight plan causing separation such as from an approach or arrival. Normally, a discontinuity can be replaced or deleted however, a discontinuity cannot be deleted or replaced:
To delete a waypoint (unless specified as a discontinuity above), press the CLR DEL function key. DELETE will appear in the scratchpad. Press the LEFT LSK which corresponds to the waypoint which you would like to delete. The waypoint will now be removed. The same methodology can be used to clear the DATA LINES.
If an instrument approach is selected, MISSED APPR will appear in the data lines after the runway. All waypoints that are part of the missed approach procedure will be displayed, ending with the published hold. This segment will appear in cyan on the navigation display. Once the missed approach has been activated, it will turn white.
NOTE: Missed approach procedures/waypoints do not appear unless the missed approach is activated OR, they are selected using the display/hide function which can be found under DSPL MENU by selecting MISSEDAPPR or, from the MFD LWR MENU. |
The missed approach segment can be enabled by any of the three following methods:
The Working Title CJ4 features the ability to add custom pilot waypoints. The waypoints can be added directly on the LEGS page or can be added via the PILOT WPT interface in the DATABASE page.
To add a custom waypoint directly from the LEGS page:
RULE: Custom waypoints must be entered here on the LEGS page. They will not be accepted on the FPLN page. |
The following formats are acceptable to be entered into the scratchpad as custom waypoints. NAME at the end of a custom waypoint is always optional.
Format: N/SDDMM.MMW/EDDDMM.MM/NAME
Example: N4412.55W00405.25
Example: N44W00405
*2-Digit latitude must always come before 2-digit longitude!
FIX=Name of the FIX (IE. CHKNN, OCN, RX15)
BEARING=Bearing FROM the FIX (090)
DISTANCE=Distance FROM the FIX in NM (15)
NAME=Custom name of waypoint if desired.
Example: OCN090/15/WP1
This is useful if you need to hold a certain distance from a fix along an airway or arrival procedure, or comply with an altitude restriction.
Format: FIX/DISTANCE/NAME
ie: PADRZ/-10 Would enter a waypoint along your route 10nm BEFORE PADRZ.
ie: PADRZ/10 Would enter a waypoint along your route 10nm AFTER PADRZ.
Custom pilot waypoints added from the LEGS page are automatically stored in the PILOT WPT LIST and can be accessed by selecting IDX -> PAGE 2 -> DATABASE -> PILOT WPT LIST.
To add and manage pilot waypoints, navigate to the DATABASE page on the FMC with IDX -> PAGE 2 -> DATABASE:
On the PILOT WPT LIST page:
On the DEFINE PILOT WPT page:
RULE: A maximum of 20 pilot waypoints can be saved; upon storing the 21st pilot waypoint, the first pilot waypoint will be deleted. These are overwritten with FIFO logic (first in first out). |
RULE: Pilot waypoints may not have the same IDENT as any other pilot waypoint or waypoint in the official nav database. |
Direct To allows for the aircraft to proceed to any valid waypoint in the flight plan without going through the predefined sequence. There are two ways to initiate a direct-to a waypoint.
RULE: It is not possible to go DIRECT TO a vector (VECT). |
FROM LEGS PAGEThe first and most common method is to select the fix you wish to go direct-to from the ACT LEGS page. You can select any waypoint on any of the LEGS pages, including the one you are already going direct-to. In this case, we’ll go direct-to GYWNN on PAGE 1/4. Select GYWNN on LSK 5L. It will then copy to the scratchpad. Then, select LSK 2L, the current (2299) fix. GYWNN will now be placed into LSK 2L, removing all waypoints before it. EXEC the command and the aircraft will now go direct to GYWNN. |
FROM DIR PAGEThe second method of going direct is from DIR on the FMS function keys. Press the DIR button to bring up the ACT DIRECT-TO page. Select the fix you wish to go direct-to, cycling through pages as necessary. In this case, HUNDA on PAGE 1. Click LSK 3L to select. It will then bring you to the MOD LEGS page with the waypoint already placed in L2. Hit EXEC to confirm, MOD LEGS will become ACT LEGS, and the aircraft will now go direct to HUNDA. |
Vertical Direct-To allows the pilot to command the VNAV to go direct to an altitude constraint that already exists at a waypoint. To initiate a vertical direct-to, enable VNAV and autopilot from the FMA, and find the waypoint which corresponds to the altitude in green, on the right hand side of the FMS, in which you wish to climb or descend to. It will then place that altitude in magenta, above the VSI, as the Flight Plan Target Altitude and VNAV will now calculate and follow a path to the newly selected altitude. The altitude preselector must be at or below your new target altitude.
This page also displays the slope between waypoints and the required vertical speed based on present ground speed.
NOTE: Selecting an DIRECT TO altitude will NOT go DIRECT TO the waypoint fix it corresponds with. It is changing altitude only. |
NOTE: Going DIRECT TO an altitude will CLEAR all other altitude constraints before it. |
You can also go direct-to a nearby airport. From the DIR page, select NEAREST APTS. You will then be presented with a screen that lists your ORIGIN, your DESTINATION and the 3 nearest airports within a 200NM radius based on editable runway length. Default is 5000 but it will accept any value between 0 and 19999’. Select the airport you wish to go direct-to using the LSKs.
Another important feature of the FMS-3000 is the HOLD function. These are flown as “race-track” patterns to delay an arrival or keep an aircraft over a particular spot until ATC can provide proper sequencing.
To initiate a hold, press IDX>HOLD. You will then be taken to the ACT LEGS page. Find the page which contains the fix which you would like to hold at, or enter it manually into the scratchpad and press LSK 6L.
For this scenario, ATC requests that we “hold as published, present altitude, on the arrival at ROBIE, 1 minute legs” and an EFC time of 21:45z. The inbound course as listed on the ROBIE5 arrival chart is 308° with right-hand turns. Press LSK 4L (1) to bring ROBIE into the scratchpad. Once ROBIE is in the scratchpad, press LSK 6L (2) to initiate the HOLD set up process.
Once a hold has been entered in LSK 6L, you will be taken to a screen that says MOD FPLN HOLD. This is where the hold parameters can be entered and/or modified.
RULE: Only a 3-digit radial (001°- 360°) plus a direction will be accepted by the FMS. (ie. 308/R, 090/L, 008/R) |
RULE: You can either enter the LEG TIME or LEG DISTANCE, it is NOT possible to define both simultaneously. Defining one will define the other based on current groundspeed. ie: 1.0 MIN LEG TIME = 2.3 NM LEG DIST ie: 4.0 NM LEG DIST = 2.0 MIN LEG TIME |
When the hold is configured as required, press EXEC to insert it into the flight plan. The hold FIX will be duplicated in the LEGS page and HOLD AT will appear above it.
When more than one hold has been configured, upon accessing the HOLD page from the INDEX, you will be presented with the ACT HOLD LIST. This list contains all active holds in a flight plan. Use the Left LSK to select any active holds you wish to modify.
RULE: The maximum number of holds that can be entered at any one time is six (6). |
To delete a hold, press the CLR DEL key followed by the corresponding LSK on the left side of the FMS, followed by the EXEC key to delete.
To exit a hold, you may press LEGS>EXIT HOLD. The FMS will then note EXIT ARMED. You may also exit the hold from FPLN HOLD. If you wish to stay in the hold, you can cancel the hold exit from both LEGS and FPLN HOLD.
NOTE - Upon arming a hold exit, the plane may immediately exit if it has already passed abeam the hold fix. From elsewhere in the hold pattern, the FMS will direct the plane to turn to the inbound leg. This turn cannot be canceled. However, if CANCEL HOLD is pressed, the plane will continue to fly the holding pattern after passing the hold fix. |
The TUN (tune) page is where all aircraft radio frequencies and transponder codes are entered.
TUNE 1/2
Entering a new frequency in the COM1/2 line will “bump” the current frequency down to RECALL.
NOTE: All frequencies can be entered using shorthand by omitting the “1” or decimal point such as: 24.85 or 2485 (124.850), 8.7 (108.700), or 191 (119.100). |
RULE: Transponder code must be a 4-digit number only using numerals 0-7 |
REL/ABS - Displays current traffic altitude as either RELative or ABSolute.
TUNE 2/2
Clicking on either COM1 or COM2 without a frequency in the scratchpad, will bring up the COM CONTROL page. This page contains additional configuration options for the COM1/2 radios as well as stored presets. You can return to TUNE 1/2 by pressing on the COM1(2) frequency LSK (1L) while the scratchpad is empty or by pressing the TUN key.
NOTE: Presets cannot be deleted, they must be overwritten with a new frequency. |
Clicking on either NAV1 or NAV2 without a frequency in the scratchpad, will bring up the NAV CONTROL page. This page contains additional configuration options for the NAV1/2 radios as well as stored presets. You can return to TUNE 1/2 by pressing on the NAV1(2) frequency LSK (1L) while the scratchpad is empty or by pressing the TUN key.
NOTE: NAV CONTROL is not accessible while avionics are in DISPATCH mode. |
NOTE: The MSFS VOR search function may not always be 100% reliable. This is a limitation of the sim and something we are currently looking into. |
NOTE: Presets cannot be deleted, they must be overwritten with a new frequency. |
The ATC CONTROL page contains several options relating to the transponder. It can be accessed by pressing on the transponder code under ATC1 (LSK 5L) while the scratchpad is blank. You can exit the ATC CONTROL menu similarly by pressing ATC1 (LSK 1L), with a blank scratchpad, while in the ATC CONTROL sub-menu or by pressing the TUN function key.
The ADF CONTROL page contains several options relating to the ADF (Automatic Direction Finder) radio. It can be accessed by pressing on the frequency under ADF1 (LSK 6L) while the scratchpad is blank. You can exit the ADF CONTROL menu by pressing ADF1 (LSK 1L), with a blank scratchpad or by pressing the TUN function key.
The TCAS CONTROL page contains several options relating to the Traffic Collision Avoidance System. It can be accessed by pressing on the TCAS button (LSK 6R). The TUN button must be pressed to return to the primary radio page.
NOTE: Resolution Advisories (RAs) are currently not modeled. |
NOTE: Maximum TCAS display range is 40nm. |
When the AVIONICS switch at the electrical panel is switched to DISPATCH, the TUNE page of the FMS will revert to DISPATCH mode. This mode only powers essential systems and a single FMS for preflight planning. Only the first radios (COM1, NAV1, ATC1 and ADF) are available in this mode.
When the AVIONICS switch is moved into the ON position, the rest of the TUNE page will be activated.
NOTE: All control pages are accessible when in dispatch mode except for NAV1. |
The MFD ADV menu allows for the user to step through flight plan waypoints from the LEGS page when the MFD map is in PLAN mode (LWR MENU). The waypoints will then be centered in the PLAN map.
NOTE: Before stepping through any waypoint, the PLAN view will stay centered and follow the aircraft. Once you step through a waypoint, it cannot be re-centered on the aircraft. The real unit never centers and tracks on the aircraft. This page of the FMS is still a work-in-progress and may be updated at a later date. |
The display menu controls items to be displayed on the MFD/PFD in PPOS or PLAN view. Activated items will be highlighted in green. Items in gray are not yet available.
THIS PAGE HAS BEEN INTENTIONALLY LEFT BLANK
Minimum engage height after takeoff | 300ft AGL |
Minimum disengage height during approach | 200ft AGL |
Yaw damper | Must be engaged after liftoff, disengaged before touchdown |
Fig 6.1 - Flight Guidance Panel
The FD button on the FGP enables or disables the flight director on the PFD. The flight director will now give appropriate lateral guidance even when the autopilot is disengaged, as of 0.9.1. The co-pilot independent flight director is not currently modeled.
The VS button on the FGP enables or disables the Vertical Speed Hold mode of the Flight Guidance System. In this mode, the plane will adjust pitch to meet the desired vertical speed. The vertical speed can be selected using the vertical speed/pitch wheel, indicated by the DOWN and UP indications to the right of the wheel.
The VNAV button on the FGP enables or disables VNAV. VNAV in the climb phase is an over-the-top mode that commands altitude captures at programmed restrictions in the flight plan while still climbing using the underlying selected vertical mode (VS or FLC). VNAV in the descent phase may be used as an over-the-top mode similar to the climb phase, but also provides a calculated descent path using the defined Flight Path Angle to meet the arrival and approach restrictions if no other vertical mode is selected. The default descent flight path angle is 3°. More details are available later in this chapter in the dedicated VNAV Operations section.
The FLC button on the FGP enables or disables Flight Level Change mode of the flight guidance system. In this mode, the plane will adjust pitch to keep the selected FLC airspeed. As such, the aircraft will increase pitch to slow, and decrease pitch to gain speed. The selected speed can be changed using the knob labeled SPEED. Pressing the SPEED knob will toggle the speed hold between IAS and Mach hold modes. The selected speed bug will not be visible on the PFD unless FLC is the active vertical mode.
NOTE - The Cessna Citation CJ4 is not equipped with an autothrottle. Selecting FLC will not automatically adjust the throttle to meet the desired airspeed. Airspeed in FLC is controlled only by plane pitch angle. It is the pilot’s responsibility to select the correct throttle setting for the desired climb or descent rate. |
The NAV button on the FGP enables or disables FMS or radio LNAV. If the currently selected navigation source is the FMS, the FGS will command the aircraft to follow FMS guidance via the flight plan. However, if the currently selected navigation source is either NAV1 or NAV2, then the FGS will follow the selected nav radio. Changing the selected radial course to the nav source can be accomplished using the CRS1 (for NAV1) and CRS2 (for NAV2) knobs on the FGP. Pressing either knob will select a course that takes the aircraft directly to the tuned nav source.
If the current nav source is FMS, pressing NAV arms the LNV FGS mode. The plane will continue to fly in the current mode until within capture distance from the desired FMS course. When the course is captured, the current lateral mode will be disengaged and LNV will become the active lateral navigation mode.
The ½ BANK button will engage or disengage ½ Bank mode, which limits the maximum bank of the aircraft. Normal maximum bank is 30°, and ½ bank is 15°.
The HDG button on the FGP enables or disables the Heading Hold mode of the FGS, which commands the plane to follow the currently selected FGP heading. The selected FGP heading can be changed using the knob on the FGP labeled HDG. Pressing the HDG select knob will synchronize the selected heading to the current airplane heading.
The APPR button on the FGP enables or disables the Approach mode of the FGS. The Approach mode is a unique mode in that it controls both the APPR LNV or APPR LOC lateral modes and the GS or GP vertical modes.
Enabling approach mode during an ILS approach will arm APPR LOC and arm GS, while continuing to provide guidance in the current active mode. When the localizer is captured, APPR LOC will become the active lateral mode, and when the glideslope is captured, GS will become the active vertical mode. while enabling approach mode during a RNAV approach will activate APPR and arm GP.
Similarly, enabling approach mode during an RNAV approach will arm APPR LNV and arm GP, while continuing to provide guidance in the current active mode. When the lateral FMS course is captured, APPR LNV will become the active lateral mode, and when the vertical glidepath is captured, GP will become the active vertical mode.
The B/C button on the FGP enables or disables ILS backcourse approach mode. This mode will direct the FGS to fly the backcourse of the tuned ILS navigation source. B/C mode does not apply to RNAV approaches. - NOT IMPLEMENTED
The ALT button on the FGP enables or disables altitude hold mode on the FGS. This mode directs the aircraft to hold the selected FGP altitude. The selected altitude can be changed with the ALT knob. Pressing the ALT knob will synchronize the selected altitude with the current altitude.
The YD button on the FGP enables or disables the aircraft yaw damper. The yaw damper is always engaged if the autopilot is engaged. YD will appear in place of AP when the yaw damper is manually engaged without the autopilot.
The AP button on the FGP enables or disables the autopilot (FGS). Enabling the autopilot will immediately command the aircraft to follow the selected FGS modes.
The YD/AP DISC breaker bar forcibly disconnects the FGS from commanding the aircraft control surfaces. This bar is only used in emergency scenarios when the autopilot cannot be disengaged via normal means. Pressing the bar back in reconnects the FGS.
The Flight Guidance System display is located at the top of the pilot and co-pilot Primary Flight Displays (PFD). This display annunciates the status of the FGS and what FGS modes are armed and/or currently active, reflecting the mode selections of the pilot as pressed on the Flight Guidance Panel (FGP).
Active Lateral Mode | AP/YD Status | Active Vertical Mode | Active Vertical Mode | |
LNV1 | AP | VS 2000 | VS 2000 | |
APPR | ← | PATH | GS | |
Armed Lateral Mode | Active FGS Side | Armed Vertical Mode | VNAV Armed Mode | Armed Approach Mode |
Fig 6.2 - FGS Display Layout
Active Lateral Mode | The currently active lateral guidance mode being followed by the FGS. Valid modes are:
|
Armed Lateral Mode | The currently armed but not yet active lateral guidance mode. Valid modes are the same as the above modes. |
AP/YD Status | The current status of the autopilot and yaw damper. The yaw damper is always engaged if the autopilot is engaged.
*YD will not be annunciated when AP is engaged |
Active FGS Side | The currently active FGS side (pilot side or copilot side). If the active side points towards the pilot position, the annunciation will be green, else it will point away and be white. Currently the active side is always the pilot side. |
Active Vertical Mode | The currently active vertical guidance mode being followed by the FGS. Some vertical modes will be preceded by a V if VNAV is currently enabled. Valid modes are:
|
Armed Vertical Mode | The currently armed but not yet active vertical guidance mode. Valid modes are the same as the above modes. |
Armed VNAV Mode | The currently armed VNAV vertical mode. Valid modes are:
|
Armed Approach Mode | The current armed vertical approach mode. Valid modes are:
|
The VNAV mode of operation provides vertical navigation that respects the flight plan defined altitude restrictions during the climb, cruise, and descent phases of flight. Flight plan altitude restrictions are automatically loaded when a departure, arrival, or approach procedure are selected on the FMC DEP/ARR pages, and may also be entered by the pilot into the FMC LEGS page manually.
NOTE - The CJ4 FMC does not operate the same as an airliner style FMC for VNAV operations. The FMC will display only loaded or entered altitude restrictions and will not populate anticipated altitude crossings at each fix. This is normal operation, and VNAV will still fly the calculated path. There is no need to populate altitude restrictions for each fix. |
VNAV will automatically determine if you are in the climb or descent phase by looking at the current flight plan segment.
In VNAV climb (climbing to the selected altitude with VNAV engaged), VNAV will not calculate a climb path. The climb rate is at the pilot’s discretion, and is managed using VS (indicated by VVS while in VNAV) or FLC (indicated by VFLC while in VNAV). However, VNAV will look at the programmed climb altitude restrictions and will select an altitude to hold at to maintain those restrictions. VNAV will also arm FLC at the programmed speed entered in the VNAV SETUP page and automatically transition to make FLC active when the restriction has passed.
Because the climb rate is at the pilot’s discretion, AT OR ABOVE restrictions are up to the pilot to meet. VNAV will hold altitude for AT and AT OR BELOW restrictions.
In VNAV descent, the default vertical guidance mode (with no other vertical modes selected) is PATH. VNAV Path calculates 1 or more descent segments to fly, taking into account programmed altitude restrictions, based on the Flight Path Angle defined in FMC VNAV SETUP. VNAV Path will split the descent into multiple segments in the case where a level-off at a restriction altitude is required during a leg of the descent.
Each VNAV descent segment is preceded by a Top Of Descent (TOD) marker in green on the PPOS and PLAN PFD/MFD map displays. The TOD marker will appear on the map no later than when the aircraft is within ~20NM from the calculated top of descent for the current descent segment. It is normal to encounter multiple level-offs with TODs during a planned descent.
When the aircraft is within 1000ft of the calculated VNAV descent path, VNAV will automatically arm PATH with the FGS. This informs the pilot that when the descent path is captured, that PATH will become the active vertical guidance mode, and that the plane will follow the calculated descent path. Vertical guidance will continue to track the calculated descent path, leveling off for programmed altitude restrictions as necessary. If the pilot selected altitude is to be captured, the armed vertical mode will be ALTS. If the VNAV target altitude is to be captured, then the armed vertical mode will be ALTV.
If the aircraft is above the capture range of the path during a planned descent segment, PATH will appear in the armed VNAV mode slot. This indicates that VNAV cannot capture the path from above from the current position, and the pilot will need to descend to the path using VS or FLC modes.
VNAV does not adjust or actuate the aircraft engine throttle. It is up to the pilot to manage the aircraft horizontal speed manually with throttle control.
Vertical Deviation Indicator | The vertical deviation indicator, appearing to the left of the altitude tape, indicates the amount of deviation from the calculated VNAV descent path. The magenta snowflake indicates the aircraft’s current vertical deviation from the path. |
VNAV Target Altitude | The VNAV target altitude indication, a magenta altitude that appears above the vertical speed bar, shows the next programmed restriction in the plan. This restriction will appear if the selected altitude is under the restriction, indicating to the pilot that the restriction is taking precedence over the lower selected altitude. |
Vertical Speed Advisory Pointer | The vertical speed advisory pointer appears as a magenta donut in the vertical speed bar, and shows the minimum vertical speed required to meet the next programmed restriction, if the descent was to be immediately initiated. |
PFD TOD Alert | A TOD alert will appear on the upper left of the bottom half of the PFD display when the plane is within 1000ft vertical deviation of the next TOD. The TOD alert will flash approximately 5-10 seconds before the descent is initiated to alert the pilot to an impending vertical speed change that will require throttle management. |
THIS PAGE HAS BEEN INTENTIONALLY LEFT BLANK
The Primary Flight Display (PFD) shows basic flight information such as pitch, roll, yaw, airspeed, and altitude. In addition, it also displays many other sources of information such as those coming from the FMS and other NAV sources. PFD functions are controlled via the DCP (Display Control Panel) located above it.
Fig 7.1a - Primary Flight Display
Fig 7.1b - Primary Flight Display Top
Fig 7.1c - Primary Flight Display HSI
#1. - LNAV (FMS) accuracy. Displayed messages correspond to the accuracy of the system under various phases of flight. In the image above, APPR is depicted as corresponding to an accuracy of 0.3nm or less. Below are the normal accuracies for each phase when certain criteria are met:
Enroute - 2nm - (No display)
TERM - 1nm - Displays 31nm or less from destination.
APPR - 0.3nm - Displayed before the FAF (Final Approach Fix) when using FMS/GPS sources.
LPV APPR - 0.02nm - Displayed before the FAF when using an LPV approach.
These are not to be confused with the deviation dots of the course pointer (the magenta needle). The deviation for each NAV source is as follows when selected as the primary source. The following values are for EACH DOT.
VOR - 5 degrees of deviation.
LOC - 1 degree of deviation.
FMS - 5.0 nm Enroute.
- 1.0 nm for GPS/FMS APPR.
THIS PAGE HAS BEEN INTENTIONALLY LEFT BLANK
Fig 7.2 - Display Control Panel
The DCP (Display Control Panel) controls all the configurable options for the Primary Flight Display (PFD).
MENU ADV
Menu Advance Knob - Allows the user to scroll through PFD MENU options and data. Selected content will be outlined by a CYAN box.
DATA VALUE | |
DATA 123 | |
◯ | OPTION |
⬤ | OPTION |
▶ | SUBMENU |
Data Knob - Allows data fields selected from the MENU ADV to be changed.
PUSH SELECT
Push Select Button - Used to enable/disable items highlighted with a 𐩒 or ⃞ toggle, or enter sub-menus. Lists noted with a 𐩒 denote that only one option can be selected. Lists with a ⃞ denote that any number of items can be selected from the category. Once you scroll to the desired menu, outlined in a cyan box, press the inner-middle button labeled PUSH SELECT to enter, enable, or disable.
Navigation Source Button - Toggles between the active navigation source and the source selected under PRESET on the lower portion of the PFD. The preset source in the CYAN box can be changed by using the inner-middle selector knob labeled DATA. Any two (2) combinations of the following three (3) sources can be selected as the active source and preset:
So, if FMS1 is the active source, VOR1/LOC1 or VOR2/LOC2, can be in your preset. Or, if VOR1 is the current source, FMS1 or VOR2 can be selected in your preset.
PFD Menu Button - The PFD menu (Fig 7.3) contains many of the same controls found on the DCP. Within the PFD MENU, you can toggle formats, NAV sources, set the range, set crosshair and unit types (meters, HPA), enable overlays for traffic, terrain and weather, and configure several other options as well.
NOTE: Items with a ▶ denote accessible sub-menus. |
Fig 7.3 - PFD MENU
NOTE: Sub-menus in DARK GREY are not yet implemented. |
Bearing Source sub-menu (Fig 7.4) contains options to enable and configure BRG PTR 1 (Bearing Pointer 1) and BRG PTR 2 (Bearing Pointer 2) to display on both the PFD and MFD.
Fig 7.4 - BRG SRC
Configuration sub-menu (Fig 7.5) contains general configuration options for the PFD.
Fig 7.5 - CONFIG
NOTE: Settings in the CONFIG menu will persist through each load when MSFS is exited properly through the menus. |
Terrain/Weather Button - Terrain/Weather. Cycles through display overlay on the HSI to either show terrain heights relative to the aircraft, or weather.
▶ OVERLAYS
Overlays sub-menu (Fig 7.6) contains options for HSI overlay displays.
Fig 7.6 - OVERLAYS
References Button - Allows reference speeds, and minimums to be set or modified. V-speeds can be automatically sent to the REFS menu from the PERF page (TAKEOFF or APPROACH) in the FMS.
Speeds sent by the FMS will appear under the airspeed indicator in MAGENTA while any speed modified by the user will be CYAN.
References sub menu (Fig 7.7), also accessible from PFD MENU ↳▶ REFS.
NOTE: If a speed is modified, it must be enabled with a ✔ before it will appear on the speed tape again. Use the PUSH SELECT on the highlighted value to enable. |
Selectable from 0-14000ft.
the Radar Altimeter. Selectable from 0-2500ft.
RULE: The CJ4 is certified for ILS CAT I only! BARO minimums MUST be used for all approaches. |
Barometer Knob - Sets the altimeter display below the altitude indicator. Pressing the BARO knob will set the altimeter to 29.92 STD (or 1013 STD if using HPA).
▶ BARO SET
Barometer Set sub-menu (Fig 7.8), accessible from PFD MENU ↳▶ BARO SET contains options to set the barometric pressure or enable STD (standard) altimeter setting. This is useful for preselecting a local altimeter setting while in STD mode. Fig 7.8 - BARO SET
Escape Button - Returns from sub-menu to parent menu or exits PFD MENU.
Elapsed Time - Places a timer in the bottom-left corner of the PFD that counts up from zero seconds. Press ET once to begin. Once counting, press ET to stop. Once stopped, press ET to hide the timer.
Format Button - Cycles the PFD HSI display between ROSE, ARC, or PPOS (See PFD MENU above).
NOTE: To see traffic on the PFD when in ARC or ROSE mode, TERR or WX must be turned on. |
TILT - NOT IMPLEMENTED
Range Adjust Knob - The inner-right knob labeled RANGE controls the displayed map range for both the PFD and the MFD. They are linked together on both displays (this is how the real unit functions). Selectable range is 5NM to 600NM.
THIS PAGE HAS BEEN INTENTIONALLY LEFT BLANK
The Multi-Function Display (MFD) is capable of showing a number of parameters and is split into three (3) parts. The top window (outlined in yellow) contains engine and systems information. The UPPER window (outlined in red), displays other system information, FMS text, checklists, passenger briefings and CAS messages (WIP). The LOWER window (outlined in blue), displays maps and HSI formats. Other functions, such as charts, combine both the UPPER and LOWER windows of the MFD for better readability. All functions of the MFD are controlled via the CCP (Cursor Control Panel) below (except map range and BRG pointers which are controlled from the DCP).
Fig 7.9 - Multi-Function Display
THIS PAGE HAS BEEN INTENTIONALLY LEFT BLANK
Fig 7.10 - Cursor Control Panel
The CCP (Cursor Control Panel) controls all display functions related to the Multi-Function Display (MFD).
MENU ADV
Menu Advance Knob - Operation the same as on the DCP. Allows the user to scroll through UPPER or LOWER MFD MENU options and data. Selected content will be outlined by a CYAN box.
DATA VALUE | |
DATA 123 | |
◯ | OPTION |
⬤ | OPTION |
▶ | SUBMENU |
DATA
Data Knob - Allows data fields selected from the MENU ADV to be changed.
PUSH SELECT
Push Select Button - Used to enable/disable items highlighted with a 𐩒 or ⃞ toggle, or enter sub-menus, and make selections. Lists noted with a 𐩒 denote that only one option can be selected. Lists with a ⃞ denote that any number of items can be selected from the category. Once you scroll to the desired menu outlined in a cyan box, press the inner-middle button labeled PUSH SELECT to enter, enable, or disable.
Upper MFD Menu Controls - Controls the data field displayed in the UPPER MFD WINDOW.
to be played (Fig 7.15).
systems (Fig 7.16).
Fig 7.12 - MFD UPPER window OFF with PPOS mode selected.
Fig 7.13a - UPPER MFD FMS TEXT
NOTE: ETE format is H:MM. ETA format is HH:MM ZULU (UTC). They are calculated based on current Ground Speed. |
Fig 7.13b - FMS UPPER TEXT VNAV Window
When the FMS text window is set to VNAV (See DSPL MENU in FMS), TOD and other VNAV descent parameters will appear in the FMS text window in place of ETA, fuel at destination, and landing weight. TOD and descent information will only appear if a STAR or approach has been selected and populated with altitude restrictions, otherwise you will receive an advisory descent (see below). VNAV will follow this descent mode if the information described above is entered.
Fig 7.13c - UPPER MFD FMS TEXT VNAV ADVISORY
An Advisory Descent appears when no altitude constraints (no STAR or approach loaded) are present between the enroute portion of the flight and the destination. DES ADVISORY will provide an advisory point (DES) to begin a descent that will put you at 1500’ AFE (above field elevation), 10nm from the destination airport. CRZ ALT in PERF INIT must be filled in for the advisory descent to calculate. Advisory descents will NOT follow a VNAV path if armed. They must be manually controlled by the pilot.
Fig 7.15 - UPPER MFD PASSENGER BRIEFING
Fig 7.16 - SYSTEMS 1/2
Lower MFD Menu Controls (Fig 7.17) - Controls the data field displayed in the LOWER MFD WINDOW.
NOTE: The PLAN view will initially stay centered and follow the aircraft if waypoints have not been ‘stepped’ through (See MFD ADV). Once you step through a waypoint, it cannot be re-centered on the aircraft. The real unit does not center on the aircraft. |
Fig 7.17 - LWR MENU
Overlays sub-menu (Fig 7.18) contains options for HSI overlay displays.
Map Symbols sub-menu (Fig 7.19). Show or hide map symbols on the MFD. Symbols will be displayed when they are selected with a ✔.
NOTE: Many MAP SYMBOLS can also be displayed using the DSPL MENU key of the FMS. |
Fig 7.19 - MAP SYMBOLS
MFD with symbols.
CURSOR - NOT IMPLEMENTED
Engine Button - Show or hide the EICAS display above the UPPER MFD WINDOW.
Escape Button - Closes out the current sub-menu or parent menu on the UPPER or LOWER MFD MENU.
Terrain/Weather Button - Show or hide the weather or terrain overlays on the MFD.
DATA BASE - NOT IMPLEMENTED
NAV DATA - NOT IMPLEMENTED
Memory 1, 2, and 3 Buttons - Allows the user to save MFD configuration states into one (1) of three (3) recallable memory banks. To save MFD states to memory, set the MFD layout configuration to a state which you would like to save. Then, press and hold the corresponding memory (MEM 1, 2 or 3) key for three (3) or more seconds and then release. The configuration should now be stored and can be recalled by pressing the corresponding MEM key to which it was saved. There is no confirmation message.
NOTE: The memory store function will store parameters such as overlays (TERR/WX,TFC), and LOWER MFD window options such as displayed airports or navaids. |
NOTE: Only combinations of the UPPER and LOWER MFD windows can be stored. Full screen configurations and charts cannot be stored. |
Show or hide Electronic Charts - REQUIRES NAVIGRAPH CHART SUBSCRIPTION. Charts may be geo-referenced to the aircraft’s position where available (See E-Charts).
CHART ORIENTATION - NOT IMPLEMENTED
Chart Zoom - Zooms the selected chart in or out. The selected chart will scale automatically to fit the width of the display if it is longer than it is wide. Pressing the ZOOM button once will zoom the chart in from the center. Pressing it a second time will zoom it back out to the default level. The maximum zoom level for charts is 2x.
Chart display joystick - Slews the view around the chart when zoomed in.
Systems Button - Show or hide the systems overlay on the LOWER MFD window.
Fig 7.20a - Systems 1/2
Fig 7.20b - Systems 2/2
Crew Alert System Button - NOT IMPLEMENTED
Checklist Button - Displays the checklist menu in the UPPER MFD window. Will overwrite any current displays. To reset the checklists, hit the ESC button until you are back to the CHECKLIST INDEX, then scroll down to RESET CHECKLIST and select using the PUSH SELECT button on the CCP.
Passenger Briefing Button - Displays the passenger briefing audio menu in the UPPER MFD window. Like the CKLST button, this will overwrite any menus currently displayed.
Electronic charts (E-Charts) are displayed on the UPPER and LOWER MFD. REQUIRES NAVIGRAPH CHART SUBSCRIPTION. After a valid Navigraph account has been linked (See MOD SET in the FMS section above), the charts will be available by pressing the CHART button. Before any charts will appear, an ORIGIN and/or DEST (destination) must be filled on the FPLN page. Then, press the LWR MENU button and use the MENU ADV (outer knob) on the CCP to highlight a chart. To view, press the inner PUSH SELECT button. If a departure, arrival, or approach for the origin and/or destination airports has been selected, the corresponding charts will automatically populate into the CHART MAIN INDEX (Fig 7.25a). Press the ESC key to return to the chart on the MFD. (For night chart mode, see PANEL lighting.)
Fig 7.25a - Chart Main Index
SELECTING A NEW CHART
If a field has not been auto-populated, because a departure, arrival or approach has not been selected, highlight the blank field ([ ]) after AIRPORT, DEPARTURE, ARRIVAL, or APPROACH and press PUSH SELECT to bring up a list of all the procedures for that index. If a chart index is already populated, you can long-press the PUSH SELECT button on any populated field to view all available procedures under that index. Use the ESC key to return to the INDEX menu.
Fig 7.25b - Chart APPROACH Index
The CJ4 will geo-reference the aircraft’s position and superimpose it over the chart (if applicable). The aircraft’s present position, with north pointing up, will show as a pink aircraft symbol. To hide the charts and return to the HSI and/or UPPER window, press the CHART button while the chart is displayed. With a chart displayed (Fig 7.25c), you can scroll through all selected charts populated in the MAIN CHART INDEX by using the MFD ADV knob on the CCP.
Fig 7.25c - Geo-referenced aircraft position
THIS PAGE HAS BEEN INTENTIONALLY LEFT BLANK
The PFD and MFD have a number of map modes common to both displays such as ARC, ROSE and PPOS. PLAN mode can only be displayed on the MFD. Both the PFD and MFD are nearly identical with the exception of one feature. The MFD active waypoint data block will also include TTG (Time To Go - in minutes) below the waypoint identifier while the PFD will not include this.
Displays a 360 degree compass rose.
Fig 7.30b - MFD ROSE
Displays a 125 degree arc. TTG is also displayed on the MFD ARC.
Fig 7.31a - PFD ARC
Fig 7.31b - MFD ARC
Centers and follows the aircraft showing heading up, and displays route map with waypoints. Displaying PPOS on the PFD only will also enable a lateral deviation line to appear below the attitude indicator.
Fig 7.32b - MFD PPOS
Centers on a waypoint showing NORTH (N) up and allows for a flight plan to be previewed using the MFD ADV function (see MFD ADV above).
NOTE: The PLAN view will initially stay centered and follow the aircraft if waypoints have not been ‘stepped’ through (See MFD ADV). Once you step through a waypoint, it cannot be re-centered on the aircraft. The real unit never tracks and centers the PLAN view on the aircraft. |
Fig 7.33 - MFD PLAN
THIS PAGE HAS BEEN INTENTIONALLY LEFT BLANK
Fig 8.1 - Audio Panel
Both COM1 and COM2 are capable of transmitting and receiving. The square button above the label toggles which radio is the active transmit source. A green light above the switch indicates which source you are currently transmitting on. The round knobs below the radio label mute and unmute that radio. The buttons modeled in the MSFS CJ4 vary slightly from the real aircraft. In the MSFS version, there is no way to push the knobs in or out. Also unlike the real aircraft, in MSFS, when the knob is pointed all the way to the left (ie. COM1), the radio is set to MAX volume. When the radio knob is pointing straight up (ie. DME1), the radio is MUTED. In the image above (Fig 8.1), COM1 is set to transmit (TX) and receive (RX) while COM2 is currently set to receive (RX) only. You can only transmit on one (1) radio at a time while you can receive on both. This is useful for talking on one radio while monitoring the other for ATC or ATIS information.
NOTE: In the current configuration, you can MUTE the radio you are transmitting on. Be sure to check the position of the knob or cockpit tooltip if no audio is being received. |
All other buttons are currently inoperable with the exception of MARKER. Toggle the knob under MKR to mute or unmute ILS marker beacon tones.
NOTE: The cockpit tooltips will show the button state when TOGGLED, not the present button state. |
Fig 8.2 - Electrical Panel
Left and Right Generators - Provides power from the left and right generators to the main electrical bus. Generator switches should both be placed into the ON position as per the Cockpit Preparation checklist.
Battery Master Switch - The battery master switch supplies main electrical power to the aircraft.
Emergency Lights - The emergency lights provide power to interior lights (and wing escape lights in the event of an evacuation) when DC power fails. The switch should be in the ARMED position as per the checklist or you will receive a CAS alert displaying EMER LIGHTS NOT ARMED.
NOTE: Emergency lighting is not currently modeled in the sim but the CAS system does read the switch position. |
Standby Flight Display - Turns the standby flight display between the MFD 1 and MFD 2 on or off.
Avionics Switch - Controls power to the avionics systems. When the avionics switch is set to the ON position, all avionics systems are powered on for normal operation. When the switch is set to DISPATCH, only the left MFD and left FMS will be active. The TUNE page of the FMS will also be in a DISPATCH mode which only allows for COM1/NAV1 operation (See DISPATCH page in FMS for more information).
The lighting panel controls both the interior cockpit and exterior lighting as well as screen dimming options for the left and right PFDs and MFDs.
Fig 8.3 - Lighting Panel
PFD1/2 Dimming Knob - The outer, larger knob controls the screen brightness for the Primary Flight Displays. PFD1 is the left, pilot-side PFD. PFD2 is the right, co-pilot-side PFD. Brightness operates independently.
MFD1/2 Dimming Knob - The inner, smaller knob controls the screen brightness for the Multi Function Displays. MFD1 is the left, pilot-side MFD. MFD2 is the right, co-pilot-side MFD. Brightness operates independently.
Panel Dimming Knob - The panel dimming knob controls the backlighting for the instrument panels in the cockpit. When the switch is set all the way to the right, on DAY, panel lighting will be off and “day-mode” charts will be displayed. When the switch is moved one position to the left (when panel backlighting illuminates) charts will then be in “night-mode.” Turning the knob to the left will dim the panel backlighting while keeping the charts in “dark mode.” When the switch is moved from a “day-chart” setting to a “night chart” setting, the chart should now automatically switch to the correct mode based on the knob position.
Controls the beacon light located on the top of the vertical stabilizer. Should be in the ON position prior to engine start.
Controls the navigation lights. A red light is found on the tip of the left wing and a green light is found on the tip of the right wing. In addition, each wing-tip has a rear-facing LED position light. They are typically left on at all times.
Controls the anti-collision lights found on the wingtips between the navigation lights and the position lights. Typically turned on at all times when entering an active runway for crossing, or for takeoff. Left on until exiting the runway after landing.
Turns the forward-facing, LED lights on the underside of the aircraft to the normal illumination setting. The taxi lights and the landing lights are the same set of lights but set to different intensities.
Turns the forward-facing, LED lights on the underside of the aircraft to the highest illumination setting for greatest visibility. Most commonly used for takeoff and landing, and when below 10,000’ during day or night operations.
Turns the tail logo lights on or off. Generally used at night from engine startup to engine shutdown.
NOTE: These light switches currently have no effect on modeled interior lighting in MSFS. |
When the SAFETY switch light is activated, a safety message is played over the PA. On the real aircraft the SEAT BELT, NO SMOKING, and all emergency EXIT signs are illuminated.
When the BELT sign is activated, a seatbelt message is played over the PA. On the real aircraft, the SEAT BELT ON sign is illuminated while all emergency EXIT signs are turned off.
The pulse light system pulses the landing lights for greater visibility. When set to the ON position this will override the landing lights steady illumination. The pulse light system must be OFF for all night ground operations and night flight operations below 300ft AGL.
TCAS
NOT IMPLEMENTED
The Standby Attitude Indicator (SAI), provides an independent display for critical flight information in the event of a primary system failure.
Fig 8.5a - SAI on the ground. Fig 8.5b - SAI in flight.
NOTE: The BARO set knob on the SAI acts independently from the one on the DCP however, as a result of simulation modeling, there is currently no way to “press” the knob like in the actual unit. As a work around, the STD setting is tied to the STD “press” on the DCP. |
TC-