航空 发表于 2011-3-22 07:21:00

320系列机组课程自动飞行飞行管理A

**** Hidden Message *****

航空 发表于 2011-3-22 07:21:11

AUTOFLIGHT MENU Flight management (A) 1/70<BR>AUTOFLIGHT MENU Flight management (A) 2/70<BR>To enable the FG part of the FMGS to guide the aircraft along<BR>a route, you must first program the flight plan into the MCDU. In<BR>this module, we will do this together and in the process learn<BR>about the organization, functions and indications of the MCDU.<BR>We will then see how the flight plan itself is displayed for you<BR>on the MCDU and compare it to what you see on the ND.<BR>PARIS<BR>(ORLY)<BR>CCAAIIRROO<BR>AUTOFLIGHT MENU Flight management (A) 3/70<BR>Before we begin to program the flight plan,<BR>lets look at the functions, controls and displays<BR>of the MCDU.<BR>AUTOFLIGHT MENU Flight management (A) 4/70<BR>AUTOFLIGHT MENU Flight management (A) 5/70<BR>First, the brightness knob. We will increase<BR>the brightness for you.<BR>Notice the knob is labeled BRT.<BR>AUTOFLIGHT Flight management (A) 6/70<BR>We will divide the MCDU into two parts:<BR>- The upper part contains the display and<BR>some keys which are oriented to specific lines on<BR>the display.<BR>MENU<BR>AUTOFLIGHT MENU Flight management (A) 7/70<BR>- The lower part contains a number key pad, a<BR>letter keyboard and some function keys.<BR>Let’s have a closer look.<BR>AUTOFLIGHT MENU Flight management (A) 8/70<BR>On the screen, the first line gives the name of the<BR>current display or page. MCDU MENU is the first page<BR>displayed at power-up. It is a menu for the various<BR>systems which can be accessed by the MCDU.<BR>Notice the first system on the list is the FMGC. MCDU<BR>1 will access FMGC 1 while MCDU 2 will access FMGC 2.<BR>All listed systems use the MCDU as a common<BR>interface.<BR>AUTOFLIGHT MENU Flight management (A) 9/70<BR>Six keys, called Line Select keys abbreviated<BR>LSK, are located on either side of the screen.<BR>AUTOFLIGHT MENU Flight management (A) 10/70<BR>The LSKs are numbered from 1 to 6 from the<BR>top to bottom. For example, the LSK used to<BR>access the FMGC is called the LSK 1 L, where L<BR>stands for left.<BR>Seelleecctt FFMGC..<BR>1<BR>2<BR>3<BR>4<BR>5<BR>6<BR>1<BR>2<BR>3<BR>4<BR>5<BR>6<BR>Left Right<BR>AUTOFLIGHT MENU Flight management (A) 11/70<BR>The LSKs are numbered from 1 to 6 from the<BR>top to bottom. For example, the LSK used to<BR>access the FMGC is called the LSK 1 L, where L<BR>stands for left.<BR>Noo,, cclliicckk oonn tthhee LLSK11 LLeefftt..<BR>1<BR>2<BR>3<BR>4<BR>5<BR>6<BR>1<BR>2<BR>3<BR>4<BR>5<BR>6<BR>Left Right<BR>AUTOFLIGHT MENU Flight management (A) 12/70<BR>The LSKs are numbered from 1 to 6 from the<BR>top to bottom. For example, the LSK used to<BR>access the FMGC is called the LSK 1 L, where L<BR>stands for left.<BR>Noo,, cclliicckk oonn tthhee LLSK11 LLeefftt..<BR>1<BR>2<BR>3<BR>4<BR>5<BR>6<BR>1<BR>2<BR>3<BR>4<BR>5<BR>6<BR>Left Right<BR>AUTOFLIGHT MENU Flight management (A) 13/70<BR>You have accessed the FMGC Status Page.<BR>Several items of information are displayed. Among them<BR>you can find the type of aircraft and the engines used.<BR>Notice the color coding used. White indicates a title or a<BR>label while blue indicates a modifiable value. Green indicates<BR>a value which cannot be modified. This color coding is used<BR>throughout all the pages of the MCDU, there are more colors<BR>which will be explained as we encounter them.<BR>AUTOFLIGHT MENU Flight management (A) 14/70<BR>Let’s talk a little more about the page layout. A page can<BR>display 14 lines of text. There is:<BR>- One title line, here “A320-200”, the aircraft type,<BR>- 6 label lines, one for each data line, our example being<BR>ENG.<BR>- 6 data lines, e.g “IAE-V2500-AX”<BR>- And a scratchpad line at the bottom of the screen.<BR>You will see how to use the scratchpad later in the module.<BR>AUTOFLIGHT MENU Flight management (A) 15/70<BR>The Flight Management system, or FM, uses<BR>two databases to perform its computations, a<BR>Navigation Data Base and a Performance Data<BR>Base.<BR>AUTOFLIGHT MENU Flight management (A) 16/70<BR>The Navigation Data Base, or Nav Data Base,<BR>contains all the necessary information for the<BR>lateral flight plan, such as routes, airways, VORs,<BR>NDBs, waypoints and airports.<BR>AUTOFLIGHT MENU Flight management (A) 17/70<BR>The navigation database is updated every 28 days<BR>and its currency and validity is checked on this page<BR>during the preflight. Notice there is an active database<BR>and a secondary or second data base.<BR>AUTOFLIGHT MENU Flight management (A) 18/70<BR>The secondary (second) data base is either<BR>the previous or the next data base.<BR>Data bases are loaded two at a time so that if<BR>the first one expires away from a maintenance<BR>base, the pilot can activate the second one before<BR>departure the next day.<BR>AUTOFLIGHT MENU Flight management (A) 19/70<BR>The Performance Data Base, or Perf Data<BR>Base, contains the aircraft performance model<BR>and is used to optimize the flight plan and to<BR>obtain predictions such as ETA’s, EFOB etc...<BR>AUTOFLIGHT MENU Flight management (A) 20/70<BR>The PERFormance FACTOR is used to modify<BR>the aircraft performance model for the individual<BR>aircraft. The value 0.0 in percentage units is in<BR>blue indicating that it can be modified.<BR>AUTOFLIGHT MENU Flight management (A) 21/70<BR>We will see now how to select the other pages<BR>of the autoflight system. Most of the pages are<BR>accessed using the function keys.<BR>AUTOFLIGHT MENU Flight management (A) 22/70<BR>In the FMGS preflight the first thing that we do is<BR>confirm the correct information on the Status Page. We<BR>are then ready to begin programming the route of flight,<BR>this is called Initializing the flight plan.<BR>Caallll IINIITT ppaaggee..<BR>AUTOFLIGHT MENU Flight management (A) 23/70<BR>In the FMGS preflight the first thing that we do is<BR>confirm the correct information on the Status Page. We<BR>are then ready to begin programming the route of flight,<BR>this is called Initializing the flight plan.<BR>Noo,, pprreessss tthhee IINIITT kkeeyy..<BR>AUTOFLIGHT MENU Flight management (A) 24/70<BR>In the FMGS preflight the first thing that we do is<BR>confirm the correct information on the Status Page. We<BR>are then ready to begin programming the route of flight,<BR>this is called Initializing the flight plan.<BR>Noo,, pprreessss tthhee IINIITT kkeeyy..<BR>AUTOFLIGHT MENU Flight management (A) 25/70<BR>The INIT page is the first<BR>page on which you input data.<BR>Notice the amber boxes; these<BR>are the fields into which data<BR>must be inserted.<BR>Notice the fields with white<BR>dashes, these fields are not yet<BR>available to fill or display<BR>information because the FMGC<BR>does not have enough<BR>information.<BR>As we proceed and provide<BR>information to compute the<BR>lateral and vertical components<BR>of the flight plan, we will see<BR>these fields become active.<BR>The field on the bottom right<BR>is the default altitude for the<BR>tropopause.<BR>The cyan color means it is<BR>modifiable, if we make no input<BR>the FMGC will use this default<BR>for its performance<BR>computations.<BR>AUTOFLIGHT MENU Flight management (A) 26/70<BR>Notice the two fields COmpany RouTE, or CO<BR>RTE, and FROM/TO on the first line. They are<BR>used to define all or some of the flight plan and<BR>associated parameters.<BR>AUTOFLIGHT MENU Flight management (A) 27/70<BR>The first step in creating<BR>the flight plan is to define the<BR>origin and destination. This<BR>can be done in two different<BR>ways:<BR>- either by inserting the four<BR>letter ICAO airport codes in the<BR>FROM/TO field,<BR>- or inserting a specific<BR>Company Route (CO RTE)<BR>which will actually insert the<BR>entire route from the Nav<BR>Database.<BR>AUTOFLIGHT MENU Flight management (A) 28/70<BR>We will use the CO RTE option to set up a flight from<BR>Paris-Orly (ORY) to Cairo (CAI). The CO RTE, ORYCAI1,<BR>is written in the scratchpad at the bottom of the screen<BR>using the keypad of the MCDU.<BR>PARIS<BR>(ORLY)<BR>CCAAIIRROO<BR>AUTOFLIGHT MENU Flight management (A) 29/70<BR>The CO RTE is inserted in the system by<BR>pressing the LSK 1L.<BR>Plleeaassee ddoo iitt nnoow..<BR>AUTOFLIGHT MENU Flight management (A) 30/70<BR>The CO RTE is inserted in the system by<BR>pressing the LSK 1L.<BR>Noo,, pprreessss tthhee LLSK 11LL..<BR>AUTOFLIGHT MENU Flight management (A) 31/70<BR>The CO RTE is inserted in the system by<BR>pressing the LSK 1L.<BR>Noo,, pprreessss tthhee LLSK 11LL..<BR>AUTOFLIGHT MENU Flight management (A) 32/70<BR>Most of the fields of the<BR>INIT page are filled using<BR>information from the Nav<BR>Data base e.g.:<BR>- LAT/LONG,<BR>- COST INDEX,<BR>- CRZ FL/ISA TEMP,<BR>- ALTN.<BR>Notice that all the fields<BR>are in cyan indicating that<BR>you can modify them.<BR>AUTOFLIGHT MENU Flight management (A) 33/70<BR>The LAT/LONG is for the departure airport<BR>Orly. The coordinates are for the airport reference<BR>as shown on your charts. You will learn to<BR>modify them in the FMGS trainer to the actual<BR>gate position.<BR>AUTOFLIGHT MENU Flight management (A) 34/70<BR>The position displayed is used as a reference<BR>for the alignment of the Inertial Reference<BR>System. It is sent to the IRSs by selecting the<BR>LSK 3R, corresponding to the ALIGN IRS prompt.<BR>AUTOFLIGHT MENU Flight management (A) 35/70<BR>You will see the full IRS alignment in detail in<BR>the Navigation modules later in the course, so we<BR>have jumped ahead to the next step after full IRS<BR>alignment.<BR>AUTOFLIGHT MENU Flight management (A) 36/70<BR>Let’s go to the flight plan page to see the flight<BR>plan itself.<BR>Caallll FF--PLLN ppaaggee..<BR>AUTOFLIGHT MENU Flight management (A) 37/70<BR>Let’s go to the flight plan page to see the flight<BR>plan itself.<BR>Noo,, pprreessss tthhee FF--PLLN kkeeyy..<BR>AUTOFLIGHT MENU Flight management (A) 38/70<BR>Let’s go to the flight plan page to see the flight<BR>plan itself.<BR>Noo,, pprreessss tthhee FF--PLLN kkeeyy..<BR>AUTOFLIGHT MENU Flight management (A) 39/70<BR>This is the F-PLN page. It can be thought of as<BR>an electronic “scroll or roll-pad” containing all<BR>the waypoints of the flight.<BR>AUTOFLIGHT MENU Flight management (A) 40/70<BR>Notice the <BR>symbols. They indicate that the<BR>“pad” can be scrolled using these two keys,<BR>called the slew keys.<BR>AUTOFLIGHT MENU Flight management (A) 41/70<BR>The F-PLAN page is capable of displaying the<BR>ETA, speed and altitude for each waypoint of the<BR>flight plan. Notice the white dashes, this is<BR>because there is insufficient information to<BR>calculate the values until we made further inputs.<BR>AUTOFLIGHT MENU Flight management (A) 42/70<BR>Notice the symbol in the upper right corner<BR>of the display, it indicates that you can access<BR>another page using the NEXT PAGE key.<BR><BR>Caallll tthhee NEXTT ppaaggee..<BR>AUTOFLIGHT MENU Flight management (A) 43/70<BR>Notice the symbol in the upper right corner<BR>of the display, it indicates that you can access<BR>another page using the NEXT PAGE key.<BR><BR>Noo,, pprreessss tthhee NEXTT PAGE kkeeyy..<BR>AUTOFLIGHT MENU Flight management (A) 44/70<BR>Notice the symbol in the upper right corner<BR>of the display, it indicates that you can access<BR>another page using the NEXT PAGE key.<BR><BR>Noo,, pprreessss tthhee NEXTT PAGE kkeeyy..<BR>AUTOFLIGHT MENU Flight management (A) 45/70<BR>NEXT PAGE key is like a toggle pb used to<BR>navigate between two pages when they are<BR>available. In this case, the pages are called FPLAN<BR>A and F- PLAN B.<BR>AUTOFLIGHT MENU Flight management (A) 46/70<BR>The two flight plan pages are the same except<BR>the TIME is replaced by EFOB and ETA is<BR>replaced by WIND.<BR>AUTOFLIGHT MENU Flight management (A) 47/70<BR>The destination information is displayed at the<BR>bottom of the flight plan page regardless of the<BR>number of waypoints.<BR>AUTOFLIGHT MENU Flight management (A) 48/70<BR>Let’s look at the color<BR>coding used for the waypoints.<BR>The white one, here D086C<BR>is the waypoint to which we will<BR>fly. Hence, it is called the TO<BR>waypoint. It is white in order to<BR>differentiate it from the other<BR>waypoints.<BR>All the other waypoints are<BR>green between the departure<BR>and destination, except the<BR>destination airport which is<BR>white.<BR>AUTOFLIGHT MENU Flight management (A) 49/70<BR>Let’s compare the flight plan on the MCDU<BR>with what is displayed on the ND. D086C is also<BR>displayed there in white as the TO waypoint.<BR>Bearing and distance to go are also displayed<BR>in both places.<BR>AUTOFLIGHT MENU Flight management (A) 50/70<BR>LFPO 08 is the takeoff runway. Notice that it is<BR>displayed in green on the MCDU but in white on the<BR>ND. The waypoint just above the TO waypoint is<BR>called the FROM waypoint. In flight we constantly<BR>travel between the FROM and TO waypoints.<BR>AUTOFLIGHT MENU Flight management (A) 51/70<BR>The waypoint following the TO waypoint is<BR>called the NEXT waypoint. Notice that you can<BR>read a bearing to the TO waypoint, and a track<BR>from the TO to the NEXT waypoints.<BR>AUTOFLIGHT MENU Flight management (A) 52/70<BR>LLeett’’ss cchhaannggee tthhee ND ttoo PLLANmooddee..<BR>Chhaannggee NDmooddee ttoo PLLAN..<BR>AUTOFLIGHT MENU Flight management (A) 53/70<BR>LLeett’’ss cchhaannggee tthhee ND ttoo PLLANmooddee..<BR>Noo,, cclliicckk oonn tthhee NDmooddee sseelleeccttoorr..<BR>AUTOFLIGHT MENU Flight management (A) 54/70<BR>LLeett’’ss cchhaannggee tthhee ND ttoo PLLANmooddee..<BR>Noo,, cclliicckk oonn tthhee NDmooddee sseelleeccttoorr..<BR>AUTOFLIGHT MENU Flight management (A) 55/70<BR>AUTOFLIGHT MENU Flight management (A) 56/70<BR>Remember, the PLAN mode is north oriented. It is<BR>always centered on the second line of the F-PLN page<BR>display. This enables you to scroll along the flight plan<BR>and see all the waypoints along the route.<BR>AUTOFLIGHT MENU Flight management (A) 57/70<BR>This mode is very convenient to check the FPLN<BR>shown on the ND against the ATC flight<BR>plans and navigation charts. Let’s scroll the<BR>MCDU F-PLN.<BR>SSccrroollll ddoownn ttoomoovvee ddoownn tthhee fflliigghhtt ppllaann..<BR>AUTOFLIGHT MENU Flight management (A) 58/70<BR>This mode is very convenient to check the FPLN<BR>shown on the ND against the ATC flight<BR>plans and navigation charts. Let’s scroll the<BR>MCDU F-PLN.<BR>Noo,, cclliicckk oonn tthhee ddoownn ssccrroollll aarrrroow..<BR>AUTOFLIGHT MENU Flight management (A) 59/70<BR>This mode is very convenient to check the F-PLN<BR>shown on the ND against the ATC flight plans and<BR>navigation charts. Let’s scroll the MCDU F-PLN.<BR>Noo,, cclliicckk oonn tthhee ddoownn ssccrroollll aarrrroow..<BR>AUTOFLIGHT MENU Flight management (A) 60/70<BR>As you can see, the waypoint centered on the ND is always<BR>the one displayed on the second line of the MCDU.<BR>Note: We can now see the track or course to the third waypoint<BR>on the MCDU. In this way we can check the course between each<BR>set of waypoints in the flight plan against the chart if we wish.<BR>AUTOFLIGHT MENU Flight management (A) 61/70<BR>As a result of the scroll, LFPO 08 is no longer<BR>displayed. It is replaced by the TO waypoint. At<BR>the same time, notice the FROM indication is<BR>removed from the MCDU.<BR>AUTOFLIGHT MENU Flight management (A) 62/70<BR>Notice the symbol displayed just after the waypoint D804. This<BR>indicates that an overfly of the waypoint. An overfly means that the aircraft<BR>will not commence the turn to the new course until directly overhead the<BR>waypoint. Without the overfly condition, the FMGC will begin the turn to<BR>the new track before the waypoint for smoothness and to stay within the<BR>lateral limits of the course.<BR>AUTOFLIGHT MENU Flight management (A) 63/70<BR>You can program the overfly of a waypoint by<BR>using this key. Then, select the waypoint to<BR>overfly using the corresponding LSK. You will<BR>see how to do this in the system trainer.<BR>AUTOFLIGHT MENU Flight management (A) 64/70<BR>Notice the amber line. It is the Engine Out<BR>Standard Instrument Departure, or EO SID. In<BR>normal operation, it is only displayed in PLAN<BR>mode for review, or in any NAV mode if an engine<BR>fails. Engine out SIDs will be discussed in more<BR>detail later on in the course.<BR>AUTOFLIGHT MENU Flight management (A) 65/70<BR>We saw earlier that we can scroll the flight plan using<BR>the arrow keys. In many cases it is important to jump<BR>ahead to the next airport to see the approach or the<BR>missed approach. To do this we press the AIRPORT<BR>KEY.<BR>Seelleecctt tthhee AIIRPORTT kkeeyy..<BR>AUTOFLIGHT MENU Flight management (A) 66/70<BR>We saw earlier that we can scroll the flight plan<BR>using the arrow keys. In many cases it is important to<BR>jump ahead to the next airport to see the approach or<BR>the missed approach. To do this we press the AIRPORT<BR>KEY.<BR>Noo,, cclliicckk oonn AIIRPORTT kkeeyy..<BR>AUTOFLIGHT MENU Flight management (A) 67/70<BR>We saw earlier that we can scroll the flight plan<BR>using the arrow keys. In many cases it is important to<BR>jump ahead to the next airport to see the approach or<BR>the missed approach. To do this we press the AIRPORT<BR>KEY.<BR>Noo,, cclliicckk oonn AIIRPORTT kkeeyy..<BR>AUTOFLIGHT MENU Flight management (A) 68/70<BR>Notice on the MCDU as well as on the ND we see the<BR>approach to the destination. If we push the key again we<BR>will cycle the MCDU and associated ND to the alternate<BR>(ALTN) airport. If we push it again we will jump to where we<BR>began, the departure airport.<BR>AUTOFLIGHT MENU Flight management (A) 69/70<BR>On the first press, the page displayed reverts to FPLN<BR>page A, with the destination airport, here HECA on<BR>the fourth line. 23R is the selected runway.<BR>AUTOFLIGHT MENU Flight management (A) 70/70<BR>In this module we have looked at the MCDU<BR>display, the LSK’s, and some of the function keys. In<BR>the next module, we will see more functions of the<BR>flight management, as accessed through the MCDU.<BR>Module completed.<BR>NEXT<BR>AUTOFLIGHT MENU Flight management (A) 71/70<BR>LLIISSTTOOFFSSUUBBJJEECCTTSS<BR>RETURN AUDIO GLOSSARY FCOM EXIT<BR>OOVVEERRFFLLYY(())<BR>AAIIRRPPOORRTTKKEEYY<BR>OOTTHHEERRPPAAGGEESSEELLEECCTTIIOONN<BR>AA//CCSSTTAATTUUSSPPAAGGEE<BR>IINNIITTPPAAGGEEAA<BR>FF--PPLLNNPPAAGGEEAA<BR>WWAAYYPPOOIINNTTSSOONNFF--PPLLNNPPAAGGEESS<BR>FF--PPLLNNPPAAGGEEBB((NNEEXXTTPPAAGGEE))<BR>PPRREESSEENNTTAATTIIOONN<BR>MMCCDDUUSSEETT--UUPP

bocome 发表于 2011-7-31 10:04:34

非正常操作

黑色曼巴_24 发表于 2014-3-8 16:28:00

320系列机




RE: 320系列机组课程自动飞行飞行管

tissle 发表于 2014-4-17 10:11:37

好资料,学习中。。。。

diguo 发表于 2017-3-13 12:15:28

恩。好东西。好好学习一下。

wz071213 发表于 2018-1-28 23:25:13

学习学习谢谢谢谢

CapJ 发表于 2021-8-23 15:13:53

哈哈哈哈哈哈哈哈哈哈哈
页: [1]
查看完整版本: 320系列机组课程自动飞行飞行管理A