Page 11 of 108

767 Pilot in Command the screen. You will have to move the overhead display down a bit to reveal the following information (this is an example of what you find):
This gives you the exact position of the aircraft according to the sim. It is important that you enter the coordinates into the FMC in the correct format. Notice the format of the lat/long listed in the REF AIRPORT data block in the previous pictures (abeam 2R LSK). You need to use this exact format for entering the coordinates manually. In our example above, we would translate the FS2000 coordinates to N3254.9W09701.8 and enter this into the scratchpad. Notice that the N coordinate was rounded off and that the W coordinate needed to be rounded and interpreted. This is necessary because FS2000 does not list lat/long in the same format as the FMC. To convert the FS2000 coordinates we did the following: - The * represents degrees and is dropped from both N and W coordinates. - The N coordinate is rounded off to give you N3254.9 - The W coordinate 97* translates to 097 - The W coordinate 1.79 translates to 01.8 and is combined with the 097 to give you the W09701.8 coordinate. This last method is the most accurate but perhaps the most difficult and confusing. We recommend this method only to those pilots that are comfortable with lat/long formats. Any of the four methods discussed above are acceptable for finding coordinates that represent current aircraft position. Once the desired coordinates are found, enter them into the FMC and the SET IRS POS boxes. Entry of the coordinates into the FMC is basically the same for all 4 methods. The general idea is to place the coordinates into the scratchpad and then transfer them into the SET IRS POS boxes. The only variable here is the method used to put the coordinates into the scratchpad. This will be made clear below. If using methods 3 or 4 to enter coordinates manually, simply use the FMC keyboard to enter the coordinates into the scratchpad. Once this is accomplished, press the 5R LSK to transfer the coordinates to the SET IRS POS boxes. This action clears the scratchpad contents and transfers the coordinates to the 5R LSK data block. After IRS alignment is complete, the SET IRS POS block disappears and the coordinates entered will be listed in the LAST POS data block abeam the 1R LSK.

Page 26 of 108

767 Pilot in Command KJFK-KSEA Route Example Here is a quick example of how to program a different type of route into the ROUTE pages. This example is offered to further solidify your understanding of ROUTE programming. DO NOT DO THIS EXAMPLE NOW! The remaining sections of this manual utilize the KDFW to KLGA route we have already programmed. For now, simply read through these steps to see if you can follow the programming logic. Then, after completing all other sections of this manual, try programming this route into the RTE 1 pages without reference to these instructions. Consider the following route from JFK to SEA: JFK.GAYEL.J95.BUF.DLH.MOT.GGW.MLP.GLASR3.SEA - Press the RTE button to display the RTE1 pages. - Start by filling in the ORIGIN and DEST data blocks. Type KJFK into the scratchpad and press the 1L LSK. Type KSEA into the scratchpad and press the 1R LSK. - Select a departure runway. In this example we use the DEP/ARR INDEX to do this. Press the DEP ARR key and select the 1L LSK for JFK DEP. Notice there are no departures in the database. Select runway 4R by pressing the 2R LSK. Return to the ROUTE page by pressing the 6R LSK. Notice that RW04R has been entered in the RUNWAY field. - Enter the optional flight number. Type AA265 into the scratchpad and press the 2R LSK. - Press the NEXT PAGE key to start entering the route. - Type GAYEL into the scratchpad and press the 1R LSK. This enters GAYEL intersection as the first waypoint of the route. - Type J95 into the scratchpad and press the 2L LSK. This puts Jet 95 in the route starting at GAYEL. - Type BUF into the scratchpad and press the 2R LSK. This completes the J95 airway entry. - Type DLH into the scratchpad and press the 3R LSK. The FMC presents a choice of waypoints. Press the 1L LSK since this is the correct waypoint. - Type MOT into the scratchpad and press the 4R LSK. The FMC presents a choice of waypoints. Press the 1L LSK to choose the correct waypoint. - Type GGW into the scratchpad and press the 5R LSK. - Press the NEXT PAGE key to move to page 3 of the route page to add more waypoints. - Type MLP into the scratchpad and press the 1R LSK. The FMC presents a choice of waypoints. Press the 1L LSK to choose the correct point. - Press the DEP ARR key and select the 2R LSK for SEA ARR. - Press the 3L LSK to select the GLASR3 arrival. - Press the 2L LSK to select the MLP TRANS procedure. - Press the 6R LSK to return to the ROUTE page. - Verify the route by using the NEXT PAGE key to view all pages of the route. - Press the 6R LSK to activate the route. Wilco Publishing Page 27 of 108
767 Pilot in Command - Press the EXEC key to execute the route. Successful programming of the route results in 4 route pages. The last waypoint in the route page should be the HETHR waypoint (from the GLASR3 arrival). Also the PERF INIT> prompt should be displayed at the 6R LSK. PERF INIT Page The Performance Initialization (PERF INIT) page is used to enter data required by the FMC to accurately calculate aircraft performance. There is only one PERF INIT page. Most of the data fields contain boxes next to the LSKs. These boxes indicate that data entry is required; otherwise the FMC will not be able to properly calculate performance numbers. The data fields in the PERF INIT page are as follows: GR WT: Aircraft gross weight (in thousands). This is automatically calculated using the FUEL and ZFW data fields. FUEL: Aircraft fuel weight (in thousands). The CALC indicates that the fuel value in the data block has been calculated by the FMC automatically. The pilot can input a fuel number manually by entering the value into the scratchpad and pressing the 2L LSK. When a manual fuel weight has been entered, MANUAL will be displayed in place of CALC next to the fuel quantity value. To return the fuel value to an FMC calculated value, press the DEL key (DELETE is displayed in the scratchpad) and press the 3L LSK. This removes the MANUAL fuel value in favor of a new CALC fuel value. ZFW: Aircraft zero fuel weight (in thousands). RESERVES: Required reserve fuel (in thousands). This value represents the minimum fuel required before an insufficient fuel warning is generated by the FMC. If the FMC predicts that you will arrive at your destination with less than the fuel quantity entered, an INSUFFICENT FUEL message is generated. CRZ ALT: Cruise altitude. Enter the desired cruise altitude. STEP SIZE: For VNAV altitude calculations, ICAO indicates standard step to altitudes. An entry of 0 inhibits automatic step altitude programming. This is discussed further in the VNAV section. COST INDEX: This value is used by the FMC to predict economy performance. A lower cost index means better economy versus a high cost index. A standard cost index for the 767 is 80.

767 Pilot in Command entered in the THRUST data block is reflected on the upper EICAS screen along with a reduction in target takeoff thrust (for more information, see the Engine section of the systems manual). The calculations involved in determining the temperature on which a reduced thrust takeoff is based are rather complicated. There are many variables taken into account including runway length, slope, altitude, and departure path obstacles just to name a few. Airlines use computer printouts generated by a load agent to determine the reduced power setting for each takeoff. For this reason it is rather impossible to supply guidance for determining reduced power temperatures for each airport in FS2000. The use of reduced power is therefore at pilot discretion. Since the Takeoff page is the final page in the pre-flight programming of the FMC, the pre-flight status is indicated at the 6R LSK. If the data required by the FMC for proper operation has been entered successfully, COMPLETED is displayed at the 6R LSK position. If the data entry required by the FMC has not been completed, INCOMPLETE is displayed at the 6R LSK position. To go back and review all preflight pages in sequence, press the <INDEX prompt (6L LSK) and then select the IDENT page using the 1L LSK. Starting with the IDENT page, cycle through the preflight pages using the 6R LSK until you find a page with missing data. Then continue through as before until COMPLETED is displayed on the TAKEOFF page at the 6R LSK position. APPROACH Page This page requires no data entry. It displays reference approach speeds calculated for the current aircraft gross weight listed in the 1L data block. Changing the weight in the 1L data block updates the reference speeds for the entered weight. However, the current gross weight of the aircraft is always restored by the FMC when the Approach page is initially displayed. Information about the runway selected for takeoff or landing can be found on the approach page. Notice here that the KDFW runway 17R information is displayed. This is the runway selected for departure. Runway length plus ILS frequency/course are shown. When the aircraft is more than halfway to the programmed destination, the runway data changes to show information about the destination runway selected on the DEP/ARR page. Now that the pre-flight preparations have been completed, lets prepare for takeoff to see how to use the FMC operationally during flight.

Page 31 of 108

FMC OPERATION
After proper programming, the FMC can be used in flight for route navigation, speed management, and altitude control. Route navigation is accomplished using the AFDS LNAV mode and the LEGS pages of the FMC. Speed and altitude control are accomplished using the AFDS VNAV mode and VNAV pages of the FMC. When the AFDS is engaged in the VNAV mode, aircraft speed and altitude can be directly controlled from the VNAV pages. More on this in the VNAV section later. For now we will concentrate on FMC route navigation and LNAV. Route Management We have already programmed a route into the FMC using the RTE pages. In our example, we used both airways and waypoints to program the route. Now, to work with the route in flight the LEGS page is utilized. Pressing the LEGS key on the FMC keyboard calls up the LEGS page for viewing. The LEGS page lists each waypoint in the route along with distance, course, speed and altitude data. If the route on the ROUTE page has Jet or Victor airways entered, each waypoint that makes up that airway is now listed in proper sequence on the LEGS page. Each waypoint listed in the LEGS page is displayed on the EHSI and connected by a pink track line. The AFDS follows the pink track line during LNAV operation and crosses each waypoint in the order listed on the LEGS page. The first waypoint on the LEGS page is known as the active waypoint and is displayed in pink on the EHSI. All other waypoints listed on the LEGS page below the active waypoint are known as inactive waypoints. These inactive points are displayed in white on the EHSI. The AFDS will navigate toward the active waypoint during LNAV operation. When the aircraft crosses the active waypoint, the next inactive waypoint moves up to become the active waypoint. Once an active waypoint becomes inactive, it is removed from the LEGS display. The important concept to remember is that the FMC always attempts to navigate toward the active (pink) waypoint via the FMC pink track line when engaged in LNAV. Waypoints can be added, modified, or remove from the route using the LEGS pages. Any time a change is made to data in the LEGS page, these changes must be executed prior to becoming active. This permits previewing of changes and allows for an opportunity to erase them if they are not correct. Lets take a look at the LEGS page for our example route and explain how it is formatted. Then we will explain how to work with your route using the LEGS page during LNAV operation.

Page 47 of 108

We see on the EHSI that a new waypoint has been created and named LIT01. This is the exact point where the LIT 150 radial crosses the SQS 270 radial. Since this is a modification to the route, the title of the LEGS page changes to MOD. The aircraft continues to navigate towards LIT until this modification is executed by pressing the EXEC key. A discontinuity is presented because the FMC wants to know where to go after the newly added waypoint. In our example, we want to go to the MEM waypoint. Do this by pressing the 4L LSK to place MEM into the scratchpad. Then press the 2L LSK to put MEM into the discontinuity boxes. This deletes the LIT waypoint and connects the LIT01 waypoint to the MEM waypoint.
After executing the route modification, the display should look like the picture above. With the AFDS is LNAV, the autopilot navigates toward the newly created place/radial/place/radial waypoint (LIT01) and then continues on to the MEM waypoint.

Page 48 of 108

767 Pilot in Command ABEAM Points Whenever making a route modification, prompts are displayed at the 4R and 5R positions on the CDU. At the 4R LSK is the ABEAM PTS> prompt. At the 5R LSK is the RTE COPY> prompt (discussed in the next section). Whenever a route modification is made, the FMC presents the opportunity to create waypoints that represent points that are abeam waypoints that may have been skipped. Abeam waypoints are useful for time and fuel calculations when flying a route. This concept is best explained using our example. To demonstrate abeam points, we must first go direct to a waypoint in our route that causes waypoints to be skipped over. On page two of our current route we find the BKW waypoint. Pressing the 6L LSK transfers BKW to the scratchpad. To go direct to this point we scroll back to page 1 of the LEGS page and press the 1L LSK to place BKW into the 1L data block. The FMC draws a dashed route modification line on the EHSI to the BKW waypoint. Also, all waypoints between aircraft present position and the BKW waypoint are removed from the LEGS page.
Notice in the above pictures that at the 4R LSK the ABEAM PTS> prompt is displayed. Pressing the 4R LSK causes the FMC to calculate waypoints along the direct routing that represent all skipped waypoints. The 4R LSK prompt also changes to SELECTED to indicate that the FMC will create these abeam points once the modification is executed. When you execute the route modification by pressing the EXEC key, the FMC updates the LEGS page with intermediate points that represent the abeam waypoints. The results are shown in the picture below.

This type of waypoint is used extensively for oceanic routings. Also, if the FMC cannot find a waypoint in the database, the lat/long coordinates can be used to represent the missing waypoint (as demonstrated in the above example). LEGS Page Summary That completes the overview of how to use the LEGS page to navigate the programmed route using LNAV. The next sections describe the remaining pages in the FMC as well as a comprehensive explanation of VNAV. The final section describes how to save FMC data for future use.

Page 52 of 108

767 Pilot in Command PROGRESS Pages Flight progress along the FMC route is summarized on the Progress pages. Pressing the PROG key on the FMC keyboard accesses the Progress pages. Page one of the Progress page display information about the first two waypoints in the route as well as your destination. Distance, crossing time, and crossing fuel is displayed for each point based on current aircraft position. Also displayed on this page is the current selected speed (abeam the 4L LSK) on which the predictions are based and some vertical navigation reference information (abeam the 4R LSK). In the example at right, SHERO is the active waypoint and the aircraft is 33 miles away from it. It is predicted that the aircraft will cross SHERO at 1820 Zulu time with 49,200 pounds of fuel on board. TXK is the next waypoint and KLGA is the destination. The same distance, time and fuel predictions are displayed for these points as well. Pressing the <POS REPORT prompt at the 6L LSK displays route information in a positionreporting format. The picture at right shows this display. The waypoint listed at the 1L data block is the last waypoint crossed. In this case we crossed the TRISS waypoint at 1814 (ATA stands for actual time of arrival) at an altitude of 20,400 feet. Fuel over TRISS was 51,600 pounds as displayed at the 5R data block. The other two waypoints are presented in the standard positionreporting format. Also listed on this page is the actual temperature and winds presently encountered by the aircraft. Pressing the 6L LSK <PROGRESS prompt restores the normal progress page display. Pressing the 6R LSK POS REF> prompt from Progress page one displays the Position Reference pages. These are the same pages discussed earlier during preflight that list current FMC position. This page is useful in verifying what coordinates the FMC is using to determine aircraft position. It also allows the pilot to compare the FMC radio position and the IRS positions to ensure that a map shift is not likely occur if the FMC reverts to IRS NAV ONLY mode.

Page 58 of 108

767 Pilot in Command DEPARTURE/ARRIVAL Page In the route programming section of this manual, the use of the DEP ARR page to expedite route programming was demonstrated. Pressing the DEP ARR key displays different DEP ARR pages depending on aircraft position. If the aircraft is on the ground, the DEP ARR INDEX page is displayed. If the aircraft is in flight and less than half way to the destination airport, the departure airport arrivals page is displayed. If the aircraft is more than half way to the destination, the destination airport arrivals page is displayed. Before we proceed, there is some important information about the SID/STAR/APP database that you must know about. The FMC comes with a limited number of standard procedures already programmed into the database. If you access the DEP/ARR INDEX pages for your favorite airports and find there is no data, this is not a bug in the program. This means that no procedures are stored in the database. Toward the end of this manual we provide information on how to program your own procedures and save them into the database. Please see the important information regarding the SID/STAR database found in the Saving FMC Data section near the end of the FMC manual. When approaching the destination airport and your routing requires the use of an arrival procedure (STAR), you can access these using the DEP ARR key. If the database finds STARs for the destination airport, they are listed on the LEFT side of the DEP ARR page. A limited number of STARs have been programmed into the database as examples (see the end of this document for custom STAR programming). Also, the approach procedure and destination runway are selected from the right side of the DEP ARR page. Approach procedures can also be custom programmed into the database (explained at the end of this document). STAR Selection In our example going to KLGA, the MINKS1 STAR with the GVE transition was selected during route programming on the ground. The FMC automatically joined the MINKS STAR to the route via the GVE waypoint. If a change in STAR procedures is required during flight, this can be accomplished by accessing the DEP ARR page by pressing the DEP ARR key on the FMC keyboard. This should display the KLGA ARRIVALS page (if not, then use the INDEX to find the KLGA ARR page prompt). The <ACT> prompt indicates that the MINKS1 arrival is the currently selected and active arrival in the route. To change the selected arrival procedure, press one of the left LSKs abeam the name of the desired arrival. The Wilco Publishing Page 59 of 108
767 Pilot in Command transition procedure for an active STAR can also be change by re-selecting the active arrival. When re-selected, the available STAR transitions are presented once again for selection. If making a change to the selected STAR, the FMC automatically removes the old STAR waypoints and adds the new waypoints to the LEGS page. The FMC also joins the arrival to the active route if a waypoint in the active route is part of the STAR. If the route contains no common points with the STAR, the FMC presents a ROUTE DISCONTINUITY that would have to be closed manually on the LEGS page. As an example, lets change the MINKS1 arrival transition into KLGA from GVE to FAK. To do this, press the DEP ARR key to display the arrival page and re-select the MINKS1 arrival by pressing the 1L LSK. All of the available transitions are presented for the STAR. Press the 2L LSK abeam FAK to make the change in transition points. When the LEGS page is displayed, a discontinuity in the route is presented because FAK is not on the original route. To close the discontinuity, line select FAK into the scratchpad (by pressing the 3L LSK) and then press the 2L LSK to join the routes. APPROACH/RUNWAY Selection Not all airports utilize a STAR for arrivals. However, all airports utilize some type of approach and runway for arrival. Selection of an arrival procedure and/or an arrival runway is also done using the DEP ARR page. Along the right side of the ARRIVAL page are available APPROACHES and RUNWAYS for the destination airport. Selection of an approach procedure automatically selects the arrival runway. If an approach procedure is not being used, selection of a runway below the RUNWAY header places a runway symbol on the EHSI for reference.

Page 63 of 108

767 Pilot in Command the aircraft is considered to be in the climb phase. After the T/C point is reached, the aircraft is considered to be in the cruise phase. The FMC also calculates a top of descent (or T/D) point based on altitude restrictions entered by the pilot for the arrival waypoints in the LEGS page. After passing the calculated T/D point, the aircraft is considered to be in the descent phase. The VNAV target altitude differs depending on if the aircraft is in the climb phase, cruise phase, or descent phase. When VNAV is engaged, the AFDS continually compares the VNAV target altitudes with the AFDS selected MCP altitude. It then commands the aircrafts vertical navigation based on that comparison. The VNAV target altitude during the climb phase is the lowest of the AFDS MCP altitude, the manually entered LEGS page altitude restrictions, or the FMC CRZ ALT. During the cruise phase, the VNAV target altitude is the manually entered FMC CRZ ALT. Altitude changes during the cruise phase are coordinated between the FMC CRZ ALT and the AFDS MCP altitude. In the descent phase, the VNAV target altitude is the highest of the AFDS MCP altitude, or the manually entered LEGS page altitude restrictions. During a VNAV climb or descent, if the AFDS MCP altitude is reached prior to the VNAV target altitude, the AFDS exits VNAV mode and enters ALT HOLD mode. If the VNAV target altitude and the MCP altitude are the same, the AFDS will remain in VNAV mode. Examples of how this works are provided later in this section. The FMC displays altitude data for each waypoint in the route on the LEGS page. The FMC displays altitudes as either the actual altitude or as a Flight Level. The VNAV CLB page (described later) has an entry for transition level. All altitudes above the transition level are displayed as flight levels. Flight level altitudes are abbreviated into 3 digits with FL prior to the altitude. For example, 33000 feet is abbreviated as FL330 in the FMC. Valid manual entries for altitudes are as follows: 33000, FL330, 330. Entry of one of these values into a data block tells the FMC that you are entering 33000 feet. For lower altitudes such as 8000 feet, valid entries are as follows: 8000, FL080, 080. During FMC pre-flight preparations, a cruise altitude is programmed into the CRZ ALT boxes of the PERF INIT page. This CRZ altitude is transferred over to the VNAV pages for altitude calculations. The picture at right shows the VNAV cruise page. Notice that the CRZ ALT (1L data block) is displayed as FL330. This indicates that the planned cruising altitude for this flight is 33000 feet.

Page 64 of 108

767 Pilot in Command The FMC has a feature called step climb. The FMC continually calculates the optimum cruise altitude based on aircraft performance data. In the picture above, the 1R data block shows a STEP TO altitude of FL370 along with a distance prediction below it. This indicates that the FMC has calculated that for optimum performance, a climb to 37000 feet approximately 738NM after departure should be executed. On the LEGS page, the manually programmed CRZ ALT should be listed as altitude predictions for all waypoints prior to the calculated step climb point. The altitude listed in the STEP TO box becomes the predicted altitudes for all waypoints after the step climb point. For example, even though the programmed CRZ ALT is 33000 feet, the LEGS pages will list 37000 feet for all waypoints after the step climb point. This is made clear in the explanation below. The size of the step climb can be adjusted on the VNAV CRZ page by using the STEP box abeam the 5L LSK. The word ICAO in this block indicates that the FMC is using standard ICAO flight levels for step climb calculations. When the word ICAO is shown in this data box, the FMC transfers to the LEGS page the FMC calculated optimum altitude regardless of CRZ ALT programmed. This means that if 33000 feet is programmed as a cruise altitude, but the FMC has calculated that 37000 is optimum, the LEGS page will list FL370 as the predicted altitude for each waypoint after the step climb point. To prevent the FMC from transferring the step climb altitudes to the LEGS pages, enter a 0 into the STEP data block. The FMC still calculates the step climb points, but they will not be transferred to the LEGS page. The picture at right shows the LEGS page for our example flight from KDFW to KLGA. Speeds and altitudes are listed abeam each waypoint on the right side of the page. The format is speed/altitude. The data is displayed in small fonts indicating that these are predicted values. The FMC is predicting that the aircraft will cross each waypoint after departure at the listed speed and altitude. The FMC predicts a top of climb (T/C) point based on aircraft performance. The top of climb is the point where the FMC predicts the aircraft will level off at the FMC programmed CRZ altitude. This T/C point is displayed on the EHSI along the route with a green circle labeled T/C. Notice that TXK is the first waypoint with FL330 as the predicted altitude. All other waypoints have a lower altitude prediction displayed because they are prior to the top of climb point.

767 Pilot in Command wanders off the path because of pilot intervention or unexpected winds, the AFDS enters VNAV SPD mode to try and catch the path again. It is possible for VNAV to get high on the descent path and unable to make a crossing restriction. If this occurs, additional drag may be required to re-capture the VNAV path. The pilot has to deploy the speed brakes in this case until catching the path. In our example, we have an additional crossing restriction at the SOMTO waypoint. The FMC has calculated a descent path between KERNO and SOMTO because these two waypoints have altitude restrictions. To enable VNAV to continue its descent on the VNAV path after KERNO, the AFDS MCP must be set to the lowest descent constraint altitude. In our example, we must cross SOMTO at 13000 feet. If we enter 13000 into the AFDS MCP, the aircraft shall descend all the way down to 13000 feet on the VNAV path to SOMTO. If no further altitudes are entered in the LEGS page, VNAV will be removed and the AFDS will enter ALT HOLD mode after crossing the SOMTO waypoint. However, if additional altitude restrictions are entered into the LEGS page the FMC will calculate a VNAV path to those points as well. The key point to remember is to match the AFDS MCP altitude to the lowest altitude restriction in the LEGS page to allow VNAV to continue its descent on the VNAV path. The aircraft always levels off at the highest of the LEGS page altitudes or the AFDS MCP altitude. When calculating the descent path, the FMC also takes into account speed restrictions in the descent. Normally, the descent path is calculated based on the speed entered in the VNAV descent page. In the absence of manually entered speed restrictions, the FMC automatically calculates a speed restriction in the descent based on the SPD TRANS listed on the descent page. In our example, the FMC plans to reduce to 240 knots below 10,000 feet. If a speed restriction is entered into the LEGS page, VNAV calculates a path that allows the aircraft to cross the restricted waypoint at the entered speed. To demonstrate this in our example, we enter a speed/altitude restriction for the last waypoint on the arrival of 210/6000. This causes VNAV to calculate a descent path from SOMTO to PROUD that takes into account the planned speed reduction to 240 knots through 10,000 feet and also the speed restriction of 210 knots at PROUD. All waypoints between SOMTO and PROUD now have prediction data displayed based on the calculated descent path. Wilco Publishing Page 75 of 108
The prediction data shows that the VNAV descent will take place at the ECON speed until reaching 10,000 feet where it transitions to 240 knots. Then sometime after the IBECU waypoint, VNAV will slow the aircraft down to cross PROUD at 210 knots. VNAV Summary We have demonstrated all of the major capabilities of the VNAV system in our example. There are numerous ways to manage the AFDS and FMC for navigation. It is best that all pilots experiment with the system and determine what methods work best for them. For more information on VNAV there are many books written on the subject that might help better understand how it works and how best to use it. Because our VNAV system is so accurate, you should be able to use any book written for a Boeing aircraft FMC and use it to help understand this FMC.

Page 77 of 108

767 Pilot in Command To save the route, enter a name in the scratchpad using the FMC keyboard. The name must be 10-characters or less for the FMC to accept it. For example, to save the example flight discussed in this manual, a name like DFWLGA01 would work well. Numbering the flight plan allows for saving additional flight plans with numbers like 02, 03, etc. Once the flight plan name is in the scratchpad, press the 5L LSK to enter the flight plan name into the FILENAME box. This transfers the scratchpad contents into the 5L data line and also causes the <SAVE TO DISK prompt to appear at the 6L LSK. To finally save the route, press the 6L LSK. The route is then saved to your hard-drive in the FS2000\fmcwp\navdata\FlightPlans folder. To recall the flight plan in the future, use the CO ROUTE data block on the route page as explained in the FMC Programming portion of this manual. To refresh, type the saved flightplan name into the scratchpad and go to the ROUTE page. Press the 3R LSK to transfer the flightplan name to the CO ROUTE data block. The saved flight plan is then loaded into the FMC. Loading a flight in this way wipes out any other route data already programmed. The following information is offered as FYI for hard-core users. The flight plan is saved as a *.rte file. You can easily view the contents of the flight plan file by using Windows Notepad to open up the file. This is not necessary, but might be handy for those who wish to manually edit the flight plan file. Each waypoint is listed with lat/long data as well as some other important FMC data. Waypoints can be removed by cutting out the entire line that has the waypoint name. Also, waypoints from other files can be added to the flight plan by cutting and pasting waypoint data from another flight plan.

Page 78 of 108

767 Pilot in Command Saving Standard Instrument Departures (SIDs) Saving a SID can be very easy or very involved. This depends on the type of SID that is being saved. Some SIDs are generic and have only one route that serves all runways. Other SIDs contain transition routes that fan out from a common waypoint after departure. And the most complicated SIDs have runway specific transition procedures that only apply when certain runways are used for departure. Lets start with the most basic SID programming. SID programming is best accomplished on the ground at the subject airport. This allows the pilot to view LEGS page entries on the EHSI to verify their accuracy. RTE1 must be utilized for SID programming because RTE2 data is not looked at by the save program. Start programming on the ROUTE page (RTE1) by entering the departure and arrival airports. Since the recall of SID data is airport specific, the FMC saves programmed SIDs using the departure airport name. Therefore, it is important that the departure airport listed on the ROUTE page be the same airport that you are programming SID data for. The arrival airport entry is of little consequence and is not saved. Programming SIDs is easiest using the LEGS page. After programming the ROUTE page with the departure and arrival airports, press the LEGS key to display the LEGS page. This page should be blank with ----- shown at the 1L data block. Start programming the SID waypoints into the LEGS page in the exact order shown in the departure procedure. When this is finished, press the EXEC key to lock in the programming (note: it may be necessary to ACTIVATE the route if this is the first route programmed for the departure airport). With all LEGS of the SID programmed into the LEGS page we can now save the route as a SID. Access the SAVE ROUTE menu using the MENU key on the FMC keyboard. On page one of the SAVE ROUTE menu the 3L LSK has a <SAVE LEGS AS SID prompt. Press the 3L LSK to open up the FILENAME data block at the 5L LSK. Type the name of the SID into the scratchpad using the FMC keyboard. Then press the 5L LSK to transfer the SID name to the FILENAME data block. This action opens up the <SAVE TO DISK prompt at the 6L LSK. Pressing the 6L LSK saves the LEGS as a SID at the departure airport. Once you have a SID saved to disk, the next time you access the DEP page for the airport, the SID programmed will be listed. Selecting this SID from the DEP page places the LEGS programmed for the SID in the appropriate place in the route. Now lets go through an example that demonstrates SID programming in action.

Page 79 of 108

767 Pilot in Command Example 1: TIFTO TWO DEPARTURE at KMCI (Kansas City, MO, USA) This SID is the most basic type found. It calls for flying ATC assigned heading for vectors to join the SID. The only waypoints required for this SID are the MCI VOR and the TIFTO intersection. To begin programming, press the RTE key on the FMC keyboard to call up the ROUTE page. Put KMCI (the identifier for the Kansas City airport) into the 1L data block for the departure airport. The arrival airport is not required when programming SIDs, so any airport identifier can be placed in the 1R data block for arrival airport. Now press the LEGS key on the FMC keyboard to display the LEGS page. Type MCI into the scratchpad and press the 1L LSK. This makes the MCI VOR the first waypoint in the route. Then type TIFTO into the scratchpad and press the 2L LSK. This makes the TIFTO intersection the second waypoint. Now ACTIVATE and EXEC the route. The LEGS page should look similar to the picture shown at right. With the SID waypoints programmed, we can now save the LEGS as a SID. Press the MENU key on the FMC keyboard and then press the 5R LSK to access the SAVE ROUTE pages. On the SAVE ROUTE pages, press the 3L LSK labeled < SAVE LEGS AS SID. Now type TIFTO2 into the scratchpad and press the 5L LSK to transfer the name of the SID to the FILENAME data block. Now press the 6L LSK to save the SID to disk. The SID is now saved in the FMC SIDS folder. Now anytime you are departing KMCI and press the DEP ARR key to access the departure page, the TIFTO2 departure procedure shall be listed as an available SID.

Page 80 of 108

767 Pilot in Command Saving SID Departure Transition Procedures The previous example showed how to program and save a basic SID procedure. Now lets look at programming a SID that contains transition procedures. SID departure transitions are routings within the same SID that use different departure fixes. Most transition procedures share at least one common fix. To program the entire procedure with all transitions we must first create and save a basic SID procedure. The basic SID procedure must contain at least the initial departure waypoint. It can also contain other waypoints common to all transition procedures. After the basic SID procedure is saved we can then create and save the transition procedures as separate files. Lets use another KMCI departure as an example of how this works. Consider the WILDCAT2 departure displayed at right. This SID contains 3 transitions shown on the diagram: KENTN, SLN and ICT. The only common point all three transitions share is the MCI VOR. Therefore, to begin programming the SID we need to create the basic SID procedure. In this case it will only contain the MCI VOR since this is the beginning point of the procedure and a common point to all three transitions. Start on the ROUTE page and enter KMCI for the departure airport (if this was not done already). Press the LEGS key to go to the LEGS page and type MCI into the scratchpad and press the 1L LSK. If there are any other waypoints listed in the LEGS page you must DELETE them prior to saving the SID. Once MCI is the only waypoint in the LEGS page, EXEC the changes and then save the LEGS as a SID just like we did in Example 1 above. The SID should be saved as WILDCAT2. With the basic SID saved, we can now create the transition procedures. Start by creating the KENTN transition. Press the LEGS key on the FMC keyboard to return to the LEGS page. Type KENTN into the scratchpad and press the 1L LSK. Delete the MCI waypoint so that KENTN is now the only waypoint listed in the LEGS page. Press the EXEC key to lock in the changes. Press the MENU key on the FMC keyboard and access the SAVE ROUTE pages. Press the NEXT PAGE key on the FMC keyboard to access page 2. On this page is a <SAVE SID TRANS prompt at the 1L LSK. Press the 1L LSK to open the FILENAME box at the 5L LSK. The box is formatted to save the LEGS as a SID transition.

Page 83 of 108

767 Pilot in Command Starting with the runway 36L procedure, enter the following waypoints into the LEGS page: PULSS, EBAWI, and GLADI. Enter the crossing restrictions as well for each waypoint. These three points should be the only waypoints in the LEGS listing. Press EXEC to execute the changes. Then press the MENU key on the FMC keyboard to access the SAVE ROUTE pages. Go to page 2 and find the <SAVE RWY/SID LEGS prompt at the 4L LSK. Pressing the 4L LSK opens up the FILENAME box in the 5L data block. The box is formatted to save the LEGS as a SID runway transition. The format for saving SID runway transitions is SID.RUNWAY. For our example we enter CHK2.36L and press the 5L LSK. Then press the 6L LSK to save the runway transition to disk. Repeat these steps for the runway 36R procedure. The name for that procedure is CHK2.36R. Programming this type of SID is the most complicated of all SIDS. The completed SID consists of a basic SID, two SID departure transitions, and two SID runway transitions. When the KCLT departure page is displayed, the only time the CHK2 SID is available is when either runway 36L or 36R is selected. Selection of the CHK2 SID automatically places the proper waypoints in sequence for the selected runway. When any other runway is selected for KCLT, the CHK2 SID will not be available. Saving SID Example (Advanced) To further solidify your understanding of the above SID programming, lets go step by step through the programming of the CHK2 SID in KCLT. Go to KCLT and position the aircraft on runway 36L to begin. (Note: During waypoint programming if you are presented with a choice of waypoints, always select the waypoint at the 1L LSK) 1. Start by creating the basic SID: Look for the common waypoint(s) in the SID that occur after runway transitions and prior to departure transitions. In this case, the JACAL waypoint is the first and only common departure waypoint. " On the ROUTE page (RTE1) put KCLT in the departure airport data box (1L). " On the LEGS page place JACAL in the 1L data block. JACAL should be the only waypoint listed on the LEGS page. " Press the 6R LSK to ACTIVATE the route (if necessary) and press EXEC to execute the changes. Wilco Publishing Page 84 of 108
767 Pilot in Command " Press the MENU key followed by the 5R LSK to access the save menu. " On page 1 of the SAVE ROUTE menu, press the 3L LSK to SAVE LEGS AS SID. " Type CHK2 into the scratchpad and press the 5L LSK to enter the SID name into the FILENAME data block. " Press the 6L LSK to save the SID to disk. 2. After programming the basic SID, program the departure transitions. In this case there are two transition points after the JACAL waypoint. " Press the LEGS key to return to the LEGS page. " Type JOTTA into the scratchpad and press the 1L LSK. " Press the DEL key on the FMC keyboard and then press the 3L LSK. This removes the JACAL waypoint from the LEGS page. " Press the EXEC key to execute the changes. JOTTA should now be the only waypoint listed on the LEGS page. " Press the MENU key followed by the 5R LSK to access the save menu. " Press the NEXT PAGE key to access page 2 of the SAVE ROUTE menu and press the 1L LSK to SAVE SID TRANS. " Type CHK2.JOTTA into the scratchpad and press the 5L LSK to enter the transition name into the FILENAME data block. " Press the 6L LSK to save the SID departure transition to disk. " Press the LEGS key to return to the LEGS page. " Type NALEY into the scratchpad and press the 2L LSK. This adds the NALEY waypoint to the LEGS listing just after the JOTTA waypoint. Since JOTTA is part of the NALEY transition we leave it in the LEGS listing. " Press the EXEC key to execute the changes. " Press the MENU key followed by the 5R LSK to access the save menu. " On page 2 of the SAVE ROUTE menu, press the 1L LSK to SAVE SID TRANS. " Type CHK2.NALEY into the scratchpad and press the 5L LSK to enter the transition name into the FILENAME data block. " Press the 6L LSK to save the SID departure transition to disk. 3. After programming the basic SID and departure transitions, program the runway specific transition procedures. In this case we have two runway transition procedures. We start by programming the 36L procedure first followed by the 36R procedure. " Press the LEGS key to return to the LEGS page. " Type PULSS into the scratchpad and press the 1L LSK. " Press the 4L LSK followed by the 2L LSK. This moves the NALEY waypoint up to the 2L position and removes the JOTTA waypoint. " Press the DEL key on the FMC keyboard and then press the 2L LSK. This removes the NALEY waypoint from the LEGS page.

Page 94 of 108

767 Pilot in Command Saving approach transitions uses the < SAVE APP TRANS prompt on page 2 of the SAVE ROUTE menu. The procedure for saving approach transitions is exactly the same as for saving previous transition procedures. The transition waypoints are placed in the LEGS page and then the SAVE APP TRANS prompt is used to call up the FILENAME data box for naming the transition. As with the other types of transitions, approach transitions must share the name given to the approach to which it serves. Lets look at a few examples to demonstrate approach programming. Example 1: ILS RWY 22 at KROC (Rochester, NY, USA) This is the simplest approach you can program. The outer marker is the only waypoint prior to the runway. Also, the missed approach procedure is a straight out procedure to an NDB. There are no transition procedures to worry about on this approach. The first step is to position your aircraft at KROC. In the FS2000 menu it is listed as the Greater Rochester Intl airport. In this example, we will program the approach on the ground to demonstrate the steps required to access the ARR page. Start programming by entering a departure airport (KROC will do for our example) and the arrival airport (in this case KROC). Make sure that you are using the RTE1 page since RTE2 cannot be used to program and save approach procedures. Press the LEGS key to display the LEGS page. Enter the first waypoint in the approach procedure. Type MAPES into the scratchpad and press the 1L LSK. Since there are no further waypoints prior to the runway, we must now place the desired runway in the LEGS page. To do this, press the DEP ARR key on the FMC keyboard. This should call up the DEP ARR INDEX page. If it does not, press the < INDEX prompt at the 6L LSK. Now press the right LSK abeam the KROC ARR > prompt. This calls up the KROC ARRIVALS page. The right side of the screen displays the RUNWAYS available at KROC. Press the 4R LSK to select runway 22. Doing this places runway 22 in the LEGS page listing below the MAPES waypoint. Press the LEGS key to return to the LEGS page. Notice now that there is an entry below MAPES called RW22. The runway entry now becomes a Wilco Publishing Page 95 of 108
767 Pilot in Command waypoint. It also causes the runway symbol for runway 22 to be drawn on the EHSI. The altitude displayed on the LEGS page abeam the RW22 waypoint is automatically added by the FMC. This should correspond to the runway touchdown zone elevation. This completes the basic approach procedure. Now you can add the missed approach waypoint to the LEGS listing. Type AVN into the scratchpad and press the 3L LSK. Once all of the waypoints have been programmed into the LEGS page, you can now enter altitude restrictions for each waypoint. On the chart, MAPES has an altitude of 2500 listed. Airspeed data for this waypoint can be entered as well. A standard FMC value of 170 for approaches should be entered. So type 170/2500 into the scratchpad and press the 1R LSK. The missed approach procedure requires a climb to 3000 feet. Enter 3000 into the scratchpad and press the 3R LSK. This adds the missed approach altitude restriction to the AVN waypoint. Now that all of the waypoints and altitude restrictions have been added to the LEGS page, ACTIVATE and EXEC the route. Then press the MENU key on the FMC keyboard followed by the 5R LSK to access the SAVE ROUTE menu. On page 1 of the SAVE ROUTE menu, press the 4L LSK labeled < SAVE LEGS AS STAR/APP. This opens up the FILENAME data box abeam the 5L LSK. Because there is a runway listed on the LEGS page, the FMC formats the FILENAME data box to save the procedure as an approach rather than a STAR. Type the name of the procedure into the scratchpad. In this case type ILS22 into the scratchpad and press the 5L LSK to put the APP name into the data box. Then press the 6L LSK to save the approach to disk. With the approach saved, the next time the KROC ARR page is accessed, the ILS 22 approach will be listed on the right side of the screen. Selection of ILS22 on the ARR page adds all of the approach waypoints to the LEGS page as well as selects runway 22 for landing.

Page 105 of 108

767 Pilot in Command We have set up the route page with KRDU as the arrival airport. We have also programmed all waypoints required for the SBV5 arrival and all of its transitions. The resulting LEGS page looks like the following.
These LEGS are saved using the SAVE LEGS AS STAR/APP prompt on the save menu using SBV5 as the name. This results in a KRDU-SBV5.wst file being placed in the \STAR folder. That file looks like the following.
We have used colors again to denote where the waypoints came from. The PINK points are the transition waypoints. The BLUE points are the basic STAR waypoints. Notice how we programmed the LEGS page logically so that all transition waypoints are grouped together for easy cutting and pasting. Once all of the transitions have been removed and saved separately, the basic STAR is left that can be re-saved to contain only the common STAR waypoints. Just as with the SID file creation, we open the KRDU-SBV5.wst file using Windows Notepad. We also open up a second instance of Notepad that is blank. Cut, paste, and save each transition file the same way we did with the SIDs. The following pictures show how this is done.

Page 106 of 108

767 Pilot in Command Cut out the first transition waypoints and place them in the blank notepad. Do not forget to COPY and paste the End of Stan line as well.
Now SAVE the new waypoints as KRDU-SBV5.PSK.tr in the STAR folder.
Then cut, paste, and save the remaining transition waypoints with their proper transition names. Do not forget to re-save the original *.wst file when finished removing all transition waypoints. This completes the STAR file creation. The KRDU arrival page shall now have the SBV5 STAR listed with all available transitions.

Page 107 of 108

767 Pilot in Command As with SID transitions, there is no limit to the number of waypoints initially stored in the *.wst STAR file. One good way to quickly program all STARs at an airport is to create and save a STAR file that contains every waypoint necessary to manually program all STAR procedures. Then use this file as a database of waypoints for the creation of all STARs and transitions manually using the above procedure. Approach Procedures Programming Programming approach procedures is exactly the same as with programming SIDs and STARs. All approaches are saved in the \Approaches folder.
Again, the file names follow a similar pattern to the SIDs and STARs files. The nomenclature for each Approach file starts with AIRPORT-APPROACHNAME. The basic approach procedure is saved with a wap extension. It has the same format and function of the basic SID (*.wsd) and basic STAR (*.wst) files. The transition files again have the tr extension and have the same format as the other transition files. The procedure to program and save approach procedures is exactly the same as we have outlined above for SIDs and STARs. Program all waypoints for an approach plus transitions into the LEGS page and then save the approach using the SAVE LEGS AS STAR/APP. Since there should be a runway selection in the LEGS listing, the FMC saves the file as a *.wap file in the \Approaches directory. Then cut, paste and save the transitions as done previously. Dont forget to resave the original *.wap file when all transitions have been removed. There is a limitation when programming approaches in bunches. It is only possible to make one runway selection on the LEGS page at any one time. It is still possible to save waypoints for all approaches in one approach file. But it would be necessary to save individual *.wap files for each runway in order to get a runway waypoint for each runway. Then you can cut and paste approach waypoints and runway waypoints into manually created *.wap files for all runways at an airport. THE END ;-)

CREDITS
PRODUCER Fred Goldman / Victor Racz LEAD PROGRAMMER Alex Koshterek LEAD ARTIST Tamas Szabo SOUND Mike Hambly REPAINTS Danny Watkins / Christophe Modave / Tamas Szabo / Sergei Shestenko / Victor Racz MANUAL Mike Ray / Fred Goldman
FLIGHT DYNAMICS Rob Young
ADVISORS Steve Weiher / Marc Brodbeck Den Okan / Pavel Lozhkin Andrew Reynolds TESTERS Les Dillon / Jan Schreiber / Piotr Nowicki / Adam WEATHER RADAR Florian Praxmarer
3D ARTISTS Tamas Szabo / Victor Racz
2D ARTISTS Tamas Szabo / Peter Balogh / Victor Racz
The material presented in this book is the sole property of Mike Ray and the University of Temecula Press, Inc. Any use of the material must be by permission. All rights are reserved. No part of this publication may be reproduced in any material form (including photocopying or storing in any medium by electronic means and whether or not transiently or incidentally to some other use of this publication) without the written permission of the copyright holder except in accordance with the provisions of the copyright. Permission has been granted to Wilco Publishing to include this publication in releases of their product known as the 737 Pilot in Command flight simulator program. The release will include both electronic as well and printed versions of the publication. The University of Temecula Press, Inc. - P.O. Box 1239 - Temecula, CA 92593 - USA The code used in Wilco Publishing products may under no circumstances be used for any other purposes without the permission of Wilco Publishing and its developers. Microsoft and Windows are trademarks or registered trademarks of Microsoft Corporation in the United States and/or other countries. Acrobat Reader is a registered trademark of Adobe.

TABLE OF CONTENTS

Welcome aboard !.6 Introduction.8 Guppy history.9 The fabulous 737 cockpit.10 How to start the Engines ?.11 How to start the APU ?.12 Setup for start.13 Engine start flow.14 After start stuff.16 Five easy pieces.18 MCP.19 EADI.20 EHSI.21 EFIS Control Unit.22 CDU.23 Simplified procedures.25 Step 1: Get information.26 Step 2: Load the CDU.30 Step 3: Configure the Flight Controls.38 Step 4: Setup EFIS and MCP.39 Takeoff V speeds.40 How to read the speed tape ?.42 Takeoff.44 The heading selector.46 Climb and descent using the MCP.47 The LNAV function.48 Approach and landing.49 Approach.52 Slow up.53 Extending the landing gear.54 Flying ILS approach with autoland.55 The Amazing Auto-Land.65 CWS.57 IRS.58
(c) 2005 Wilco Publishing www.wilcopub.com - www.FeelThere.com - All material (c) MIKERAY 2005 - www.utem.com

737 Pilot in Command

WELCOME ABOARD !

B. EXTRA

We have included a full set of files and extra on your CD-Rom. Use your Windows Explorer to locate them into the EXTRA WILCO directory.

A. INSTALLATION

Installation is automatic. Insert the CD and Autorun will take you to the start-up screen. If Autorun is disabled on your system, open Windows Explorer or My Computer, browse to your CD Rom drive and double click "737PIC_x.exe" (where x is the version).
Once setup is running, follow the on-screen prompts and ensure that the installation points directly to the Microsoft Flight Simulator 2004 folder. (Usually C:\Program Files\Microsoft Games\FlightSimulator 9)
To fully enjoy the 3D Virtual Cockpit, the Track IR lets you control your field of view in flight simulators by simply looking around by few degrees. Track IR is available from Wilco Publishing http://www.wilcopub.com.
Documentation for 737 Pilot in Command is also automatically installed and can be found from the start button on your taskbar at the following location: Start/Programs/Wilco Publishing/737 Pilot in Command. Documentation is in Adobe Acrobat (PDF) format version 5.0 or later. For the CD version, Adobe Acrobat Reader is included on the CD in the Acrobat folder.

C. QUICK START

1. To Pilot 737 Pilot in Command
1. Start Flight Simulator 2. From the menus, select AIRCRAFT 3. Choose Boeing - Feelthere 737 4. Select the Aircraft Model of your choice, according to your PC performances From upper to lower configurations, select : * Full : displays all the options * 2D Panel : displays 2D panel ONLY * VC : displays Virtual Cockpit ONLY * Wingview : displays wingview and 2D panel 5. Select the livery of your choice
The FMS database is updated monthly following real world procedure changes. This database can be obtained from feelThere's website at www.feelthere.com, Downloads page. CHECK OUT WILCO PUBLISHING WEBSITE :

2. Engines Start Up

Option 1 Use CTRL + E, the default Flight Simulator engine start up sequence. Option 2 To start up engines from a 'Cold & Dark Cockpit', please refer to the next pages for complete procedures.

http://www.wilcopub.com

YOU WILL FIND INFORMATION, NEWS, AND FREQUENTLY ASKED QUESTIONS.
For Microsoft Flight Simulator use only. Not for use in real aviation.

D. THE VIEWS

1. 2D Panel Views
The following 2D panel views are available using the following key combinations : Main Panel - Shift + 1 Overhead - Shift + 2 IRS - Shift + 3 CDU / FMS - Shift + 4 Throttle Quadrant - Shift + 5 Pedestal - Shift + 6 Flaps indicator and gear lever - Shift + 7 EADI 1 - Shift + 8 EHSI 1 - Shift + 9
While in Pan Mode (mouse wheel pressed and held down) inside the Virtual Cockpit : Moving the mouse to the left rotates the view to the left. Moving the mouse to the right rotates the view to the right. Moving the mouse forward, away from the user, rotates the view up. Moving the mouse backward, towards the user, rotates the view down. Please refer to the manual for other features list.
2. 3D Virtual Cockpit Views
Display the Virtual Cockpit using the normal FS2004 keystroke, using "S". All controls found on the main 2D panels are functional within the virtual cockpit. Mouse clicking on the FMC opens the 2D FMC in a separate window. Mouse clicking on some specific screens open a 2D window : FMS, EADI,.

E. Last Minute NOTAM

(NOTice to AirMen)
737 PILOT IN COMMAND SETUP UTILITY

3. The Cabin

To move and walk inside the cabin, we have included a utility on the CD-Rom (directory : EXTRA / F1View), also available from our website. This utility is kindly offered by Flight 1. This module requires a wheel-mouse (a center wheel that also acts as a center mouse button). Virtual Cockpit : Wheel forward moves you forward and wheel backward moves you back. CTRL+forward moves right and CTRL + back ward moves left. SHIFT+forward moves up and SHIFT + back ward moves down. CTRL+SHIFT+forward zooms out and CTRL+SHIFT+backward zooms in.
The 737 Pilot in Command Set Up utility is located into your Windows Start menu. To access it, press START button of your Windows -> All programs -> Wilco Publishing 737 PIC -> 737 PIC Utility.
GEAR CUTOFF HORN By adding flaps and pulling back the throttle to idle if you don't have the gear down a horn will sound. You can silence it by using the Gear Warning Cut OFF button.
PANEL LIGHT IN THE VIRTUAL COCKPIT The panel light in the VC can be turned ON/OFF just like the one can be found on the pedestal.

SIMICONS Press SHIFT+ 9 to display the simicons panel.
From left to right : Overhead / Throttle control FS default map / IRS + Rear overhead ATC menu / Flaps & Gear panel Pedestal / FMS First Officer side annunciator / Mode Control panel
TOGA SWITCH (Take Off Go Around)
WEATHER RADAR The weather radar included with 737 Pilot in Command is based on the real Collins WXR2100. The most important is to locate hazardous weather areas, and avoid them. This system is able to show the pilot where dense precipitation is located and turbulence is expected. In an aviation based weather radar, only water and wet hail produces reflections. Only the clouds located at the aircraft level can be displayed.
Colors code : Green Yellow Red => Light precipitations => Moderate precipitations => Severe precipitations
PEDESTAL - LATEST FEATURES
The INTENSITY OF TURBULENCE within clouds can also be displayed. The turbulence is calculated out of the velocity changes for the reflections. This turbulence can only be measured within clouds that generate normal reflections. So only precipitation based turbulence can be displayed, gusty winds and other air turbulence cannot. Colors code : dark magenta intense magenta => Moderate turbulences => Severe turbulences
The turbulence image is an overlay to the normal weather radar image so if no turbulence is measured, the normal RGB Weather Radar image is drawn. The turbulence detection is limited to a Range of 40NM. A special high sensitivity mode makes it possible to detect WINDSHEAR out of water particles. Windshear is always present at low altitudes just above ground. Additional due to the high sensitiviFor Microsoft Flight Simulator use only. Not for use in real aviation.
ty, other particles than water may produce enough reflection energy to be detected and displayed as windshear. Windshear is only working below 2500ft AGL and in ranges up to 5 NM. This mode is only intended for take off and final approach phase. Windshear areas are marked by red rings.
IMPORTANT NOTES ABOUT WEATHER RADAR : 1. The Weather Radar technology requires a lot of PC resources and therefore may result in a huge impact on the frame rate. 2. When switching ON the Weather Radar, the radar pulse generators need to warm up, which can take up to 40 seconds. 3. There is no option to tilt the radar. We have simulated the radar's Auto mode. GROUND POWER UNIT To call GPU, the plane should stay with engines OFF, parking brake ON, and click the Ground Power Available light. Then, wait a minute. Ground Power Unit is fully simulated. When you turn your engines OFF and set the parking brake ON by clicking on the Ground Power Available light you can have GPU in a minute.

APU BURNS FUEL Exclusive feature ! Just like in the real plane, the APU uses fuel. This is simulated only on feelThere aircraft. Nowhere else!
THRUST VARIES WITH OAT TEMPERATURE (drops on hot days and raises at cold ones) All temperature dependent thrust tables are rogrammed into the FMS so it detects the outside temperature and set the thrust accordingly, just like in the real life. SELECTABLE THRUST RATING Exclusive feature ! The 737 was delivered with various engine ratings in real life and we wanted to simulate them all. It is a checkbox in the setup utility and you can simulate any of these ratings customising to the airline's rating you fly. WIND REQUEST From the LEGS page of the FMS, you can request wind data to the enroute part of the flight plan and the FMS will take this information into consideration allowing an even more precise fuel prediction.
FLAP LOAD RELIEF Setting 40 degrees flaps and exceeding the flaps speed, the flap load relief system will set the flaps up to 30 degrees to avoid damage caused by the wind. AUTOMATIC NOSE STEERING LIMITER Above 40kts, the nose wheel steering is limited to 6 degrees without effecting the rudder. Very realistic but can be turned OFF in the setup utility.
PAUSE BEFORE TOP OF DESCENT (TOD) Another nice and useful feature in the setup utility. Flight Simulator can pause 20 Nm before you reach the TOD point. It's handy on long range flights.
QUALITY FIRST ! By not making illegal copies and purchasing only original WILCO PUBLISHING products, you will allow to continue developing and improving the quality of our software. THANK YOU.
(c) 2005 Wilco Publishing www.wilcopub.com - www.FeelThere.com - All material (c) MIKERAY 2005 - www.utem.com 11
(c) 2005 Wilco Publishing www.wilcopub.com - www.FeelThere.com - All material (c) MIKERAY 2005 - www.utem.com 13
(c) 2005 Wilco Publishing www.wilcopub.com - www.FeelThere.com - All material (c) MIKERAY 2005 - www.utem.com 15
(c) 2005 Wilco Publishing www.wilcopub.com - www.FeelThere.com - All material (c) MIKERAY 2005 - www.utem.com 17

(c) 2005 Wilco Publishing www.wilcopub.com - www.FeelThere.com - All material (c) MIKERAY 2005 - www.utem.com 19
(c) 2005 Wilco Publishing www.wilcopub.com - www.FeelThere.com - All material (c) MIKERAY 2005 - www.utem.com 21
(c) 2005 Wilco Publishing www.wilcopub.com - www.FeelThere.com - All material (c) MIKERAY 2005 - www.utem.com 23
(c) 2005 Wilco Publishing www.wilcopub.com - www.FeelThere.com - All material (c) MIKERAY 2005 - www.utem.com 25
(c) 2005 Wilco Publishing www.wilcopub.com - www.FeelThere.com - All material (c) MIKERAY 2005 - www.utem.com 27
(c) 2005 Wilco Publishing www.wilcopub.com - www.FeelThere.com - All material (c) MIKERAY 2005 - www.utem.com 29
(c) 2005 Wilco Publishing www.wilcopub.com - www.FeelThere.com - All material (c) MIKERAY 2005 - www.utem.com 31
(c) 2005 Wilco Publishing www.wilcopub.com - www.FeelThere.com - All material (c) MIKERAY 2005 - www.utem.com 33
(c) 2005 Wilco Publishing www.wilcopub.com - www.FeelThere.com - All material (c) MIKERAY 2005 - www.utem.com 35
(c) 2005 Wilco Publishing www.wilcopub.com - www.FeelThere.com - All material (c) MIKERAY 2005 - www.utem.com 37
(c) 2005 Wilco Publishing www.wilcopub.com - www.FeelThere.com - All material (c) MIKERAY 2005 - www.utem.com 39
(c) 2005 Wilco Publishing www.wilcopub.com - www.FeelThere.com - All material (c) MIKERAY 2005 - www.utem.com 41
(c) 2005 Wilco Publishing www.wilcopub.com - www.FeelThere.com - All material (c) MIKERAY 2005 - www.utem.com 43
(c) 2005 Wilco Publishing www.wilcopub.com - www.FeelThere.com - All material (c) MIKERAY 2005 - www.utem.com 45
(c) 2005 Wilco Publishing www.wilcopub.com - www.FeelThere.com - All material (c) MIKERAY 2005 - www.utem.com 47
(c) 2005 Wilco Publishing www.wilcopub.com - www.FeelThere.com - All material (c) MIKERAY 2005 - www.utem.com 49
(c) 2005 Wilco Publishing www.wilcopub.com - www.FeelThere.com - All material (c) MIKERAY 2005 - www.utem.com 51

(c) 2005 Wilco Publishing www.wilcopub.com - www.FeelThere.com - All material (c) MIKERAY 2005 - www.utem.com 53
(c) 2005 Wilco Publishing www.wilcopub.com - www.FeelThere.com - All material (c) MIKERAY 2005 - www.utem.com 55
(c) 2005 Wilco Publishing www.wilcopub.com - www.FeelThere.com - All material (c) MIKERAY 2005 - www.utem.com 57
Boeing 757/767 Simulator & Checkride
Simmers seldom own and fly just one airplane, but have a whole stable of fabulous airplanes. In order to enhance your flight simming experience, I recommend that you pick up Captain Mike Rays 757/767 Simulator Check-ride Survival Guide. He has written well over 300 pages of everything you need to pass a checkride at any airline in the world. The more detail the dedicated sim pilot is, the more they should get all the manuals in this series. While they are not written specifically for simming, the level of realism that they project lends itself to the phenomenal realism in the sim programs of today. Because you bought this particular add-on sim program places you in an elite group of individuals.
Boeing 747 Simulator & Checkride
Captain Mike Ray has flown the 747-400 all over the world. He has placed some of his wealth of information in a volume that takes the reader behind the scenes to reveal just how the airline pilots do it. His book has been used by thousands of airline pilot from all over the world to pass their checkrides. And if you become familiar with the information inside this entertaining 300 plus page manual, you will be able to pass the check-ride too. It covers all the necessary areas to make you a real 747-400 pro. Emergencies, SOPs, profiles, set-up and cold dark airplane material. It is all in there. Even if you dont take that check-ride, you will find the witty and sometimes humorous treatment for a really complicated and boring subject. well, entertaining. This is a real MUST HAVE for those flying the glass jumbo.
(c) 2005 Wilco Publishing www.wilcopub.com - www.FeelThere.com - All material (c) MIKERAY 2005 - www.utem.com 59
You can find all these books at : www.WILCOPUB.com & www.UTEM.com

www.wilcopub.com

www.feelthere.com