Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs(bg): update sample flight in preparing-mcdu.md #939

Merged
merged 14 commits into from
Feb 17, 2024
Merged

docs(bg): update sample flight in preparing-mcdu.md #939

Changes from 6 commits
Commits
Show all changes
14 commits
Select commit Hold shift + click to select a range
a60b6d0
docs(bg): update sample flight in preparing-mcdu.md
Valastiri Feb 5, 2024
0338aac
update pdf
Valastiri Feb 5, 2024
621b82f
update images
Valastiri Feb 5, 2024
c43a14a
update images + ofp to EU route
Valastiri Feb 10, 2024
b295c96
add loading lazy
Valastiri Feb 10, 2024
8b106d5
initial text changes to preparing-mcdu.md
Valastiri Feb 10, 2024
021cf3c
update ofp photos
Valastiri Feb 10, 2024
cbc69a7
Apply suggestions from frankkopp code review
Valastiri Feb 11, 2024
50ebbca
Further fixes of setup mcdu page
frankkopp Feb 11, 2024
efd3f9a
Update docs/pilots-corner/beginner-guide/preparing-mcdu.md
frankkopp Feb 11, 2024
199a7e3
Apply suggestions from code review
frankkopp Feb 11, 2024
eecbdad
Update docs/pilots-corner/beginner-guide/preparing-mcdu.md
frankkopp Feb 11, 2024
9192ce0
Clarification for Discos
frankkopp Feb 11, 2024
d1b4db8
Apply suggestions from code review
frankkopp Feb 14, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
76 changes: 44 additions & 32 deletions docs/pilots-corner/beginner-guide/preparing-mcdu.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -180,7 +180,7 @@ The cost index can be found in the image above.

![ofp2](../assets/beginner-guide/mcdu/ofp2.jpg){loading=lazy}

Input the desired cruise flight level in this field. On our OFP, this is listed as `0190` or `FL190`.
Input the desired cruise flight level in this field. On our OFP, this is listed as `0240` or `FL240`.

* Using the keypad, type in `240`
* Press LSK6L
Expand All @@ -190,7 +190,7 @@ This will input FL240 and the temperature as well.

### **^^F^^**LIGHT PLAN

Upon loading the flight plan page, there will be three entries. Departure airport, `(DECEL)`, and arrival airport.
Upon loading the flight plan page, there will be three entries. Departure airport, a discontinuity and arrival airport.

Our route for this flight can be found on the 2nd page of the OFP

Expand All @@ -199,7 +199,7 @@ Our route for this flight can be found on the 2nd page of the OFP

![ofp3](../assets/beginner-guide/mcdu/ofp3.jpg){loading=lazy}

`EGFF/30 BCN1A BCN P69 DIZIM N864 MONTY AXCIS1M EGCC/23R`
`EDDM/08L GIVMI6Q GIVMI Y101 ERNAS T161 DEBHI DEBHI1C EDDF/07L`

^^Inputting a SID^^

Expand All @@ -214,14 +214,14 @@ To program the Standard Instrument Departure (SID):

* Press LSK1L or EDDM (the departure airport)
* Select `DEPARTURE` shown next to LSK1L
* Select the runway we are departing from. In this case `30` using LSK3L
* Select the runway we are departing from. In this case `08L` using LSK2L
* On the list of SIDs select the `GIVMI6Q` departure

The MCDU should now show at the top of the screen in yellow what is selected for our departure from EDDM.

![mcdu8](../assets/beginner-guide/mcdu/mcdu8.png){loading=lazy}

* Press `INSERT` using LSK6R to program this into the flight plan.
* Press `INSERT*` using LSK6R to program this into the flight plan.

Our flight plan should now have the associated waypoints for the `GIVMI6Q` SID. We can scroll through the flight plan using the vertical slew keys. The SID terminates at `GIVMI`
and this is where we can begin to fill out the rest of the flight plan.
Expand All @@ -240,6 +240,8 @@ and this is where we can begin to fill out the rest of the flight plan.

![mcdu10](../assets/beginner-guide/mcdu/mcdu10.png){loading=lazy}

* Press `INSERT*` using LSK6R to program this into the flight plan.

#### DCT Before a Waypoint

!!! warning ""
Expand All @@ -253,14 +255,14 @@ and this is where we can begin to fill out the rest of the flight plan.
EDDM/08L GIVMI6Q GIVMI Y101 ERNAS T161 DEBHI EDDF/07L
```

Let's imagine for this example that there was no airway between `BCN` and `OKTEM`. The flight plan would look like the following:
Let's imagine for this example that there was no airway between `GIVMI` and `ERNAS`, as well as between `ERNAS` and `DEBHI`. The flight plan would look like the following:

```title="Example NO AIRWAY Flight Plan"
EDDM/08L GIVMI6Q GIVMI DCT ERNAS DCT DEBHI EDDF/07L
```

!!! note ""
The airwayS `Y101` and `T161` was replaced with `DCT` indicating from waypoint `GIVMI` proceed direct to `ERNAS` and after that proceed direct to `DEBHI`.
The airways `Y101` and `T161` were replaced with `DCT` indicating from waypoint `GIVMI` proceed direct to `ERNAS` and after that proceed direct to `DEBHI`.

When you encounter this type of routing, there are a couple of ways to input this leg without the use of the airways page on the MCDU.

Expand All @@ -281,20 +283,21 @@ For the purposes of this guide, we will pre-plan our arrival into EDDF via the `
!!! info "STAR"
Standard Terminal Arrival Route

Similar to the SID, these are procedures that are defined and published that take a flight from the last point in a route *(in our case `DEBHI`)* to the first point in the approach or the initial approach fix (IAF).
Similar to the SID, these are procedures that are defined and published that take a flight from
the last point in a route *(in our case `DEBHI`)* to the first point in the approach or the initial approach fix (IAF).

Also see: [SIDS and STARS](../airliner-flying-guide/navigation.md#sids-and-stars)

Find `EDDF` in green in the flight plan OR select `EDFF` in white under `DEST` using the corresponding LSK.
Find `EDDF` in green in the flight plan OR select `EDDF` in white under `DEST` using the corresponding LSK.

* Select `ARRIVAL` using LSK1R
* We will be shown the approaches available, designated by `Type` `Rwy`.
* For this guide, we will shoot for an ILS to keep it simple.
* Use the vertical slew keys to find `ILS07LY` and select it using the corresponding LSK.
* A designator such as Y or Z may be present. This suffix is to distinguish in the navigation database a difference between approaches to the same runway. While similar in nature they may have different minimums, allowed equipment, or other differences.
* A designator such as Y or Z may be present. This suffix is to distinguish in the navigation database a difference between approaches to the same runway. While similar in nature, they may have different minimums, allowed equipment, or other differences.
* Again, use the vertical slew keys to find the STAR for this flight `DEBHI1C` and select it using the corresponding LSK.
* For the approach VIA Select `DF454` using the appropriate LSK. On the following page we can choose transitions if available, but for this flight we don't.
* Insert this STAR into the flight plan using LSK6R.
* For the approach VIA, select `DF454`, using the appropriate LSK. On the following page, we can choose transitions, if available, but for this flight, we don't.
* Press `INSERT*` using LSK6R to program this into the flight plan.

![mcdu12](../assets/beginner-guide/mcdu/mcdu12.png){loading=lazy}

Expand All @@ -305,7 +308,13 @@ Verify the flight plan by using the vertical slew keys to scroll through it.

The flight plan might contain so-called discontinuities. These are breaks in the flight plan and often separate two flight plan sections, like the SID and first in-route waypoint or the STAR and the APPR. They are also often inserted when the flight plan is modified.

Sometimes discontinuities are also part of a procedure to indicate that manual input is required (mostly clearance by ATC). The preceding legs are called MANUAL legs.In this flight plan we have a discontinuity between the STAR and approach procedure as shown below.
Sometimes discontinuities are also part of a procedure to indicate that manual input is required
(mostly clearance by ATC). The preceding legs are called MANUAL legs.

**Discontinuities after a MANUAL leg cannot and should not be deleted. See below link on how to
handle discontinuities.**

In this flight plan we have a discontinuity between the STAR and approach procedure as shown below.

![mcdu-discontinuity.png](../assets/beginner-guide/mcdu/mcdu-discontinuity.png){loading=lazy}

Expand Down Expand Up @@ -334,24 +343,22 @@ If we would like to have additional navaids for the departure, we can input the

The A32NX supports VOR autotuning when in range of a VOR before departure. You can verify this by checking the RADNAV page and seeing if the VOR frequency is already populated. You should verify the relevance of this VOR to your departure procedure and flight plan before takeoff.

On this departure SID, we have routing instructions that rely on the Munich VOR `DMN` with a frequency of `116.0`
On this departure SID, we have routing instructions that rely on the Munich VOR `DMN` with a frequency of `116.0`.

* Using the keypad, type in `116.0` and press LSK1L. This will autopopulate the identifier of the VOR when within range.
* We can also set the desired course to track `080` and press LSK2L to input it. (This is for a departure on runway 08L)

^^Departure ILS^^

When selecting the SID earlier in the flight plan section, the A32NX should have autopopulated the ILS/LOC frequency. If it hasn't, we can manually insert it for centerline guidance on take off.

Our departure runway is EDDM/08l (runway 08 left) which has a frequency of `109.50`. When inputting a frequency, and we are in range of the ILS, it will autopopulate the identifier and course. There is no need to fill these fields.
Our departure runway is EDDM/08L (runway 08 left), which has a frequency of `109.50`. When inputting a frequency, and we are in range of the ILS, it will autopopulate the identifier and course. You could also enter the identifier `IMNE` and it would automatically fill in the frequency. You cannot enter both at the same time, as this would result in a `FORMAT ERROR`.

* Using the keypad, type in `109.50` and press LSK3L to input it.

^^Arrival ILS^^

With an ILS or LOC approach selected, the arrival ILS frequency should be automatically tuned correctly whenever the aircraft is at climb phase or greater and within 250 NM of the destination. **Ensure** that we verify the ILS frequency when we reach the arrival phase of the flight - see [Approach and Landing (ILS)](landing.md).

Remember, our arrival airport/rwy is `EDDF/07l` with ILS07l having a frequency of `110.30`. When inputting a frequency, and we are in range of the ILS, it will autopopulate the identifier and course. There is no need to fill these fields.
Remember, our arrival airport/rwy is `EDDF/07L` with ILS07L having a frequency of `110.30`. When inputting a frequency, and we are in range of the ILS, it will autopopulate the identifier and course. There is no need to fill these fields. You could also enter the identifier `IFEL` and it would automatically fill in the frequency. You cannot enter both at the same time, as this would result in a `FORMAT ERROR`.

* Using the keypad, type in `110.30` and press LSK3L to input it.

Expand All @@ -371,8 +378,6 @@ On this page, we can input our zero fuel weight (ZFW) and zero fuel weight cente
Fuel and payload have to be set in the aircraft (see link below) and passenger boarding has to be **complete or in progress** for the ZFW/ZFWCG values to be correct. The
"planned" payload values are used for the calculation if boarding has not been completed.

*Ideally you no longer have to wait for boarding to be completed to finalize preparations on the INIT FUEL PRED page.*

Gross Weight (GW) value on the ECAM will appear only when certain conditions are satisfied:

- This page (INIT FUEL PRED) has a ZFW/ZFWCG value. **Reminder:** After engines are started, INIT FUEL PRED changes to the FUEL PRED page.
Expand All @@ -382,7 +387,7 @@ On this page, we can input our zero fuel weight (ZFW) and zero fuel weight cente

The A32NX can autopopulate this information.

* Press LSK1R to load in the calculated ZFW/ZFWCG into the scratch pad at the bottom of the MCDU.
* Press LSK1R to load in the calculated ZFW/ZFWCG into the scratch pad at the bottom of the MCDU (after boarding has been started in the flyPad).
* Press LSK1R a second time to input the above calculation into the MCDU. (The empty orange boxes should now be filled in by the scratch pad entry).

Now we can add our fuel on board (FOB). The amount we input in this field can be done in one of three ways:
Expand All @@ -397,7 +402,7 @@ Now we can add our fuel on board (FOB). The amount we input in this field can be

^^ECAM FOB^^

Look at the upper ECAM and note the FOB indicated. Let's say that amount is `4631 kg`. When inputting the block fuel into the MCDU, it is referenced in "Tons" and we should round to the closest decimal point.
Look at the upper ECAM and note the FOB indicated. Let's say that amount is `4631 kg`. When inputting the block fuel into the MCDU, it is referenced in "tons", and we should round to the closest decimal point.

* Using the keypad, type in `4.7` and press LSK2R.

Expand Down Expand Up @@ -471,8 +476,6 @@ For this flight, we will be taking off with a `1+F` flaps configuration.
- CG to THS can be found in the downloable FBW checklist in our [Standard Operating Procedures](../SOP.md#normal-procedures) resources page.
- The CG/THS markings on the trim wheel can be used to validate this.

!!! warning "GW CG in the flyPad payload page and correct CG trim values on the trim wheel in the cockpit are not yet implemented in the stable release version"

Make sure to update this value or set the correct trim once your engines have started.

---
Expand All @@ -483,7 +486,10 @@ For this flight, we will be taking off with a `1+F` flaps configuration.

--}

We can also choose to set a `FLEX TO TEMP` for the flight. The example we are using today is 60 degrees. (This will normally be calculated via a pilot's company EFB or other tools).
We can also choose to set a `FLEX TO TEMP` for the flight. The example we are using today is 60 degrees.
This will normally be calculated via a pilot's company EFB or other tools, but for the sake of this guide, we will use the value of 60.

Read the following tip for more information on FLEX temp.

* Using the keypad, type in `60` and press LSK4R

Expand All @@ -496,39 +502,45 @@ We can also choose to set a `FLEX TO TEMP` for the flight. The example we are us

{==

Flex temps are above ISA+29 °C (44 °C at sea level) and above current temp, but no higher than ISA+59 °C (74 °C at sea level). Usable Flex temps at sea level are from 45 °C (or current OAT if it is higher) to 74 °C.
Flex temps are above ISA+29°C (44°C at sea level) and above current temp, but no higher than ISA+59°C (74°C at sea level). Usable Flex temps at sea level are from 45 °C (or current OAT if it is higher) to 74 °C.

Additionally, a decent rule of thumb for simulation purposes is to use a lower number if heavy or on a short runway and higher for the opposite.

==}

Our SID chart mentions that the TRANS ALT for this departure is 5000ft.
Our SID chart mentions that the TRANS ALT for this departure is 5000 ft.

* Using the keypad, type in `5000` and press LSK4L

The A32NX can calculate the V-Speeds automatically. To do this simply:
#### V-Speeds

V-Speeds are normally calculated by a company EFB or other tools. Unfortunately, A320neo performance
data for V-Speeds alongside other various tools are not publicly available and are guarded by Airbus.
Therefore, the A32NX has a built-in simplified V-Speed calculator, which can be used by simply
clicking the LSK next to the V-Speed you want to calculate.

* Press LSK1L to have the calculated V1 speed appear in the scratchpad.

![mcdu19](../assets/beginner-guide/mcdu/mcdu19.png){loading=lazy}

* Press LSK1L again to have 132 inputted into the V1 speed.
* Press LSK1L again to have the value inputted into the V1 speed. The value you get can be different
from the one in the image as it depends on the weight of the aircraft.
* Repeat this procedure for VR and V2.

The performance page should now look like this:
The performance page should now look similar to this:

![mcdu20](../assets/beginner-guide/mcdu/mcdu20.png){loading=lazy}

## Entering Squawk Code

During your MCDU preparation or before departing from the stand you should have obtained your IFR clearance. As part of this action you will be given a transponder/squawk code
During your MCDU preparation or before departing from the stand, you should have obtained your IFR clearance. As part of this action, you will be given a transponder/squawk code
for your flight. This allows ATC to identify your aircraft on their radar.

To enter your assigned code find the ATC/TCAS Panel on the bottom right portion of the lower pedestal. It will look like this:

![ATC-TCAS.png](../assets/beginner-guide/takeoff-climb-cruise/ATC-TCAS.png){loading=lazy}

- Ensure that the `XPDR` switch is in the `AUTO` or `ON` position.
- Ensure that the `XPDR` switch is on STDBY for now (will be set to `AUTO` or `ON` shortly before take-off)
- To clear the current code, **double press** the `CLR` button.
- Enter your assigned code using the keypad.

Expand Down
Loading