- Dashboard
- Dispatch
- Ground
- Performance
- Navigation & Charts
- Online ATC
- Failures
- Settings
- Click on the menu icons in this image to see other flyPad pages.
-
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- TODO: adapt this to also work for the A380X
+ # Nose Wheel and Tiller Operation We have introduced a feature for using the tiller to steer the nose wheel independently of the rudder. As Microsoft Flight Simulator does not natively support this feature yet, we had to become creative to build a solution for this. @@ -115,7 +118,7 @@ The MSFS Controller Option we are using is `TOGGLE WATER RUDDER` and your mappin To activate the tiller feature, you need to go to the flyPad Settings page and navigate to the `Realism` tab. From there, enable the `Separate Tiller from Rudder` feature. -![flyPad Settings Sim Options Tiller](../assets/flypados3/flypad-settings-realism.png "flyPad Settings Sim Options +{loading=lazy} ## Using the Tiller and Rudder diff --git a/docs/fbw-a32nx/feature-guides/simbrief.md b/docs/aircraft/a32nx/feature-guides/simbrief.md similarity index 88% rename from docs/fbw-a32nx/feature-guides/simbrief.md rename to docs/aircraft/a32nx/feature-guides/simbrief.md index 3612f336b..e81a0d5af 100644 --- a/docs/fbw-a32nx/feature-guides/simbrief.md +++ b/docs/aircraft/a32nx/feature-guides/simbrief.md @@ -56,17 +56,17 @@ You can do this by navigating to the following page on the flyPad (EFB): - 3rd Party Options - Select the "Link Account" button next to Navigraph Account Link -{loading=lazy} +{loading=lazy} You will be presented with the following screen: -{loading=lazy} +{loading=lazy} Follow the instructions above to link your account. If successful, you should see your account name followed by your Navigraph account subscription status (not required) and an option to Unlink Account. As seen below: -{loading=lazy} +{loading=lazy} !!! note "Overriding SimBrief User ID" There may be situations where you would like to import data from SimBrief not specifically linked to your account, i.e., copying a streamer's or friend's flight plan to your @@ -75,17 +75,17 @@ If successful, you should see your account name followed by your Navigraph accou In this case you can override the SimBrief User ID by entering it in the SimBrief User ID field. This will override the linked Navigraph account temporarily until it is removed. You will be notified when the override is successful with a pop up message. Example below: - {loading=lazy} + {loading=lazy} -If you are still unsure of where the Settings page on the EFB is, please see [flyPad Settings](flypados3/settings.md). +If you are still unsure of where the Settings page on the EFB is, please see [flyPad Settings](../../common/flypados3/settings.md). ## Using the flyPad SimBrief Integration ### Importing the SimBrief OFP to the flyPad -See [flyPad Guide - Load from SimBrief](flypados3/dashboard.md#load-from-simbrief) +See [flyPad Guide - Load from SimBrief](../../common/flypados3/dashboard.md#load-from-simbrief) -See [flyPad Guide - OFP](flypados3/dispatch.md#ofp-page) on how to view the SimBrief Operational Flight Plan. +See [flyPad Guide - OFP](../../common/flypados3/dispatch.md#ofp-page) on how to view the SimBrief Operational Flight Plan. See [Fuel and Weight](loading-fuel-weight.md) on how to load fuel and payload. @@ -119,7 +119,7 @@ Otherwise, read the [SimBrief User Guide](https://www.simbrief.com/system/guide. - Click on `INIT/PRESS` - Click on `INIT DATA REQ` -{loading=lazy} +{loading=lazy} This will prepare the MCDU to input the flight plan. @@ -134,11 +134,11 @@ Head over to the `INIT A` page. This will load your flight plan from SimBrief directly into the MCDU -{loading=lazy} +{loading=lazy} !!! note #### RWY, SID, STAR, and APPR - The SimBrief import will **not** load RWY, SID, STAR, or APPR. You will need to manually add these into the flight plan. To learn how to set up the MCDU, you can read the [**^^F^^**LIGHT PLAN](../../pilots-corner/beginner-guide/preparing-mcdu.md#--f---light-plan) section in our beginner's guide. + The SimBrief import will **not** load RWY, SID, STAR, or APPR. You will need to manually add these into the flight plan. To learn how to set up the MCDU, you can read the [**^^F^^**LIGHT PLAN](../../../pilots-corner/a32nx/a32nx-beginner-guide/preparing-mcdu.md#--f---light-plan) section in our beginner's guide. This is because RWY, SID, STAR and APPR are dependent on factors like active runways, traffic, weather, etc. and are determined by ATC and not the pilot's flight plan. They can be changed by ATC any time before takeoff or during flight and are therefore not imported in real life aircraft either. diff --git a/docs/fbw-a32nx/feature-guides/wheel-chocks-cones.md b/docs/aircraft/a32nx/feature-guides/wheel-chocks-cones.md similarity index 93% rename from docs/fbw-a32nx/feature-guides/wheel-chocks-cones.md rename to docs/aircraft/a32nx/feature-guides/wheel-chocks-cones.md index 56aee2cb5..1933e6cf0 100644 --- a/docs/fbw-a32nx/feature-guides/wheel-chocks-cones.md +++ b/docs/aircraft/a32nx/feature-guides/wheel-chocks-cones.md @@ -10,7 +10,7 @@ description: Ensure safe ground operations with wheel chocks and GSE Safety Cone This page details the safety equipment available when parked with the A32NX. Other than just looking gorgeous, the wheel chocks even apply some braking force to hold the aircraft in place. The flight crew activates the Wheel Chocks and Safety Cones through the -[flyPad EFB Sim Option Settings](flypados3/settings.md#sim-options). +[flyPad EFB Sim Option Settings](../../common/flypados3/settings.md#sim-options). This simulates the ground crew automatically placing or removing the chocks or cones. The ground crew will determine if chocks and cones should be placed or removed based on specific criteria, which are described in the [next section](#usage). !!! block "" @@ -24,7 +24,7 @@ This simulates the ground crew automatically placing or removing the chocks or c The Wheel Chocks and Safety Cones appear when the following conditions are given: -- Chocks and/or Safety Cones are enabled in the [flyPad EFB Sim Options Settings Page](flypados3/settings.md#sim-options) +- Chocks and/or Safety Cones are enabled in the [flyPad EFB Sim Options Settings Page](../../common/flypados3/settings.md#sim-options) - Engines are off (`ENG1+2 N1` < 3.5 %) - Beacon lights are off - Airplane is on ground diff --git a/docs/aircraft/a32nx/index.md b/docs/aircraft/a32nx/index.md new file mode 100644 index 000000000..f6e733da8 --- /dev/null +++ b/docs/aircraft/a32nx/index.md @@ -0,0 +1,95 @@ +--- +title: FlyByWire A32NX - Overview +description: Documentation and resources for the FlyByWire A32NX add-on for Microsoft Flight Simulator 2020. +--- + + + +# FlyByWire A32NX Overview + +This section of the FlyByWire Documentation is dedicated to the A32NX add-on itself. It covers the software and more technical aspects of the FlyByWire add-on. + +The A32NX Project is a community-driven open-source project to create a free Airbus A320neo in Microsoft Flight Simulator that is as close to reality as possible. It started out as an enhancement project to the default A320neo and is now proceeding as an independent add-on project aiming to bring the FlyByWire A32NX up to payware-level systems depth and functionality, all for free. + +### **Aircraft Configuration(s)** + +The following aircraft configurations are currently simulated: + +```title="Simulated Hardware" +Model A320-251N +Engine CFM LEAP 1A-26 +APU APS3200 +FMS Honeywell Release H3 +FWC Std. H2F13 +RA Honeywell ALA-52B +TAWS Honeywell EGPWS +ACAS Honeywell TPA-100B +ATC Honeywell TRA-100B +MMR Honeywell iMMR +WXR Honeywell RDR-4000 +ACSC S1803A0001 +``` + +## Quick Links + +
+ 
)
+[//]: # ( 
)
[//]: # ( 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
[FAQ](./faq)
+ + --- + + The FAQ section provides answers to frequently asked questions regarding the FlyByWire aircraft add-ons. + +-[Installation Guide](./install/installation.md)
+ + --- + + The Installation Guide section provides information on how to install the FlyByWire aircraft add-ons. + +-[Support Resources](./support)
+ + --- + + The Support Resources section provides information on how to get support for the FlyByWire aircraft add-ons. + +-[A32NX](./a32nx)
+ + --- + + The A32NX is a community-driven open-source project to create a free Airbus A320neo in Microsoft Flight Simulator 2020. + It aims to provide an Airbus A320neo that is as close to reality as possible. + +-[A380X](./a380x)
+ + --- + + The A380X is a community-driven open-source project to create a free Airbus A380 in Microsoft Flight Simulator 2020. + It aims to provide an Airbus A380 that is as close to reality as possible. + +-[Common Features](./common)
+ + --- + + The Common Features section covers features that are shared between the A32NX and A380X aircraft add-ons. + It provides information on features like the EFB, Tiller, and more. \ No newline at end of file diff --git a/docs/aircraft/install/.pages b/docs/aircraft/install/.pages new file mode 100644 index 000000000..f4972013e --- /dev/null +++ b/docs/aircraft/install/.pages @@ -0,0 +1,6 @@ +title: Installation +nav: + - Overview: installation.md + - Versions: fbw-versions.md + - Settings: settings.md + - Liveries: liveries.md diff --git a/docs/aircraft/install/fbw-versions.md b/docs/aircraft/install/fbw-versions.md new file mode 100644 index 000000000..dd0a68f6e --- /dev/null +++ b/docs/aircraft/install/fbw-versions.md @@ -0,0 +1,97 @@ +--- +title: Versions and Features +description: Differences and release notes about the Development, Stable, and Experimental versions of the FlyByWire A32NX. +--- + +# Versions and Features + +## Version Overview + +### Development Edition (recommended) + +The Development Edition will have the latest features that will eventually end up in the next Stable release. + +In general, this version has the latest fixes and newest features but also a slightly higher risk of containing bugs as +features had less time to be used and tested by users. + +This version updates often, and occasionally several times a day. We recommend updating this version via our installer +before every start of the simulator. + +Every addition to the development version is code-reviewed and tested by several people, our QA Team and also interested +users. In general, it tends to be very stable and robust. + +You can view the latest changes to our aircraft via the commits to the master branch of the project: +[GitHub Commits to Master](https://github.com/flybywiresim/aircraft/commits/master){target=new}. + +#### Development Version Changelogs + +
+
+- **A380X - Current Stable Version**
+
+ ---
+
+ *Pending Release*
+
+
@@ -77,7 +62,43 @@ You can send us logs to our [Discord](https://discord.gg/flybywire){target=new}
[Download Development](https://github.com/flybywiresim/aircraft/releases/download/assets/master/A32NX-master.7z){.md-button target=new}
- [**IMPORTANT:** View information on Autopilot / Fly-By-Wire here](feature-guides/autopilot-fbw.md)
+ **IMPORTANT:**
+
+ View information on Autopilot / Fly-By-Wire [here](../a32nx/feature-guides/autopilot-fbw.md)
+
+- **Download A380X**
+
+ ---
+
+ Download via our Installer.
+
+ [Download Installer](https://api.flybywiresim.com/installer){ .md-button target=new}
+
+ ---
+
+ === "4K Texture Option"
+
+ [System Requirements](../../aircraft/install/installation.md#estimated-system-requirements-for-a380x)
+
+ Includes our 4K downscaled cabin, cockpit and exterior textures. Choose this option for reduced stutters, better performance, with HIGH or lower texture resolution setting.
+
+ Additionally, if you intend to use the following:
+
+ - Use frame generation
+ - Virtual Reality (VR)
+ - DX12 beta
+ - or are otherwise limited by your graphics card VRAM amount.
+
+ === "8K Texture Option"
+
+ [System Requirements](../../aircraft/install/installation.md#estimated-system-requirements-for-a380x)
+
+ Includes our 8K full resolution cabin, cockpit and exterior textures. This is the full fidelity experience and our recommendation if your system is powerful enough to support it. Realistic and in high detail.
+
+ - DX11 recommended
+ - HIGH or lower texture resolution setting recommended
+
+ 
+
+ FBW Installer - [Download Here](https://api.flybywiresim.com/installer){target=new}
+
+!!! warning "Read our Support Guides"
+
+ 1. [Learn How to Fly the Aircraft](../index.md#1-learn-how-to-fly-the-aircraft)
+ 2. [Troubleshoot](../index.md#2-how-to-troubleshoot)
+ 3. [Research Known Issues](../index.md#3-research-known-issues)
+ 4. [Report Issue on Discord](../index.md#4-report-issue-on-discord)
+ 5. [Report Issue on the FBW Aircraft GitHub](../index.md#5-report-issue-on-the-a32nx-github)
+ 6. [Collecting Support Information](../index.md#collecting-support-information)
+
+ === "Custom Autopilot"
+
+ Due to the complex nature of our custom autopilot, please visit the dedicated ^^Custom Autopilot / Fly-By-Wire^^ page for more information:
+
+ - [**Main Page**](../../a32nx/feature-guides/autopilot-fbw.md)
+ - [**Typical Issues + Solutions**](../../a32nx/feature-guides/autopilot-fbw.md#typical-issues-and-how-to-solve-them)
+ - [**Known Issues**](../../a32nx/feature-guides/autopilot-fbw.md#known-issues)
+
+ === "Custom FMS"
+
+ Please visit the ^^Dedicated Custom Flight Management System^^ page for more information on our latest implementation:
+
+ - [**Features + Issues**](../../a32nx/feature-guides/cFMS.md)
+ - [**Special Notes**](../../a32nx/feature-guides/cFMS.md#special-notes)
+ - [**Known Issues**](../../a32nx/feature-guides/cFMS.md#known-issues)
+
+ === "SimBridge"
+
+ If you're having issues with ^^SimBridge^^, please follow our dedicated guide for it:
+
+ - [**SimBridge Troubleshooting Guide**](../../../tools/simbridge/troubleshooting.md)
+
+ ---
+
+ Do this before reporting bugs.
+
+---
+
+## FlyByWire Aircraft
+
-
-Stable is our version which contains features that are the most mature and most tested. This should be a reliable version for those users preferring stability over the newest features.
-
-This version will not always be up-to-date, but we work hard at ensuring its compatibility with the current version of Microsoft Flight Simulator.
-
-### Experimental Version
-
-We have discontinued our Experimental Version. Latest features and testing will be on the Development Version of the aircraft.
-
-## Version Comparison
-
-See [Latest Release Notes for Stable](/latest-release/)
-
-For all changes made to the Development version since the last major release of the Stable version, refer to:
-
-- Official [CHANGELOG](https://github.com/flybywiresim/aircraft/blob/master/.github/CHANGELOG.md#080){target=new}
-- Commits on the [:fontawesome-brands-github:{: .github } - **GitHub FBW Aircraft Repository Master Branch**](https://github.com/flybywiresim/aircraft/commits/master){target=new}.
diff --git a/docs/fbw-a32nx/feature-guides/flypados3/throttle-calibration.md b/docs/fbw-a32nx/feature-guides/flypados3/throttle-calibration.md
deleted file mode 100644
index 47d7f30c3..000000000
--- a/docs/fbw-a32nx/feature-guides/flypados3/throttle-calibration.md
+++ /dev/null
@@ -1,735 +0,0 @@
----
-title: flyPadOS 3 EFB - Throttle Calibration
-description: Important information regarding throttle calibration for use with the FlyByWire A32NX, with step-by-step guide for each controller.
----
-
-# Throttle Calibration
-
-!!! warning "Please Note"
- Throttle Calibration is required for all versions of the FlyByWire A32NX.
-
-## Introduction
-
-This guide will help you set up your throttles for use with the FlyByWire A32NX.
-
-There are many controllers available to use in Microsoft Flight Simulator. Many have dedicated throttle levers/sliders, and some have sliders which can be used as throttle levers/sliders.
-
-Although configuration and calibration is similar for most controllers, there are subtle differences between different brands and models.
-
-The major differences between different throttle controllers are:
-
-- Number of axis (levers/sliders).
-- Having detents or not.
-- Having a reverser range on the throttle axis or not.
-- Button on the lever/slider to engage reverser or not.
-
-!!! warning "Please read this guide carefully and follow it step-by-step. Do not just skim over and skip steps, as the calibration might then fail."
-
-??? note "Collection of Controllers and their Features"
-
- | Controller | Reverser | # of axis | Detents |
- |:------------------------------------------|:---------------:|:---------:|:--------:|
- | Thrustmaster TCA | On Axis | 2 | 3 |
- | Thrustmaster TWCS | Any Button | 1 | 0 |
- | Honeycomb Bravo Throttle Quadrant | Reverser Button | 2 | ? |
- | Thrustmaster T.16000M FCS (Flight Stick) | Any Button | 1 | 0 |
- | Thrustmaster TCA Sidestick Airbus edition | Reverser Button | 1 | 1 (Idle) |
-
- Use this table to identify how to configure and calibrate your controller with the steps described below.
-
----
-
-
-
-!!! tip "Resetting to Defaults"
- Before you start with calibration, consider resetting your settings to default values as described here: [Resetting To Defaults](#resetting-to-defaults)
-
-## Microsoft Flight Simulator Control Options
-
-!!! danger "PLEASE DO NOT SKIP THIS SECTION!"
-
-### 1. Create a Separate Controller Profile in Microsoft Flight Simulator
-
-Before you change anything in the controller profile, make sure to create a dedicated controller profile for the FlyByWire A32NX in Microsoft Flight Simulator so that any changes to the throttle configuration does not impact any other aircraft.
-
-??? note "How to Create a New Controller Profile"
- Microsoft Flight Simulator allows you to create separate profiles for different controllers. To make that change to the `DEFAULT` profile of your controller and create a copy of it (`DUPLICATE`).
-
- {loading=lazy}
-
-### 2. Set Sensitivity to Linear
-
-Set all sensitivity settings to 0 %. This includes Sensitivity + and -, Dead Zone, Neutral, and Extremity Dead Zone. Leave Reactivity at 100 %.
-
-??? note "How to Set Sensitivity to Linear"
- Set your Sensitivity settings exactly like this:
-
- {loading=lazy}
-
-### 3. Axis Mapping
-
-Check that the axis mappings are correct.
-
-??? note "How to Set Axis Mapping"
-
- Your controller needs to have an axis which can be used as a throttle lever. This axis needs to be mapped to the throttle input of Microsoft Flight Simulator. Most controllers will be mapped automatically by Microsoft Flight Simulator in the default profile.
-
- If this is not the case, you can find out which controller axis is used by your controller by using the Sensitivity dialog and moving the lever to see which axis is moving.
-
- You can use ^^either^^ of these MSFS inputs:
-
- - `THROTTLE 1 AXIS (0 TO 100 %)` and `THROTTLE 2 AXIS (0 TO 100 %)`
-
- FBW Installer - [Download Here](https://api.flybywiresim.com/installer){target=new} / *Latest Sim Version: 1.37.19.0*
-
-!!! warning "Read our Support Guides"
-
- 1. [Learn how to fly an A32NX](index.md#1-learn-how-to-fly-the-a32nx)
- 2. [Troubleshoot](index.md#2-how-to-troubleshoot)
- 3. [Research Known Issues](index.md#3-research-known-issues)
- 4. [Report Issue on Discord](index.md#4-report-issue-on-discord)
- 5. [Report Issue on the FBW Aircraft GitHub](index.md#5-report-issue-on-the-a32nx-github)
- 6. [Collecting Support Information](index.md#collecting-support-information)
-
- === "Custom Autopilot"
-
- Due to the complex nature of our custom autopilot, please visit the dedicated ^^Custom Autopilot / Fly-By-Wire^^ page for more information:
-
- - [**Main Page**](../feature-guides/autopilot-fbw.md)
- - [**Typical Issues + Solutions**](../feature-guides/autopilot-fbw.md#typical-issues-and-how-to-solve-them)
- - [**Known Issues**](../feature-guides/autopilot-fbw.md#known-issues)
-
- === "Custom FMS"
-
- Please visit the ^^Dedicated Custom Flight Management System^^ page for more information on our latest implementation:
-
- - [**Features + Issues**](../feature-guides/cFMS.md)
- - [**Special Notes**](../feature-guides/cFMS.md#special-notes)
- - [**Known Issues**](../feature-guides/cFMS.md#known-issues)
-
- === "SimBridge"
-
- If you're having issues with ^^SimBridge^^, please follow our dedicated guide for it:
-
- - [**SimBridge Troubleshooting Guide**](../../simbridge/troubleshooting.md)
-
- ---
-
- Do this before reporting bugs.
-
----
-
-
-
-## Quick Links
-
-
-
- 
-
- 
-
-
-
-
-
-
-
- 
-
-
-
-
-
- This is for simulation purposes only.
The level of detail in this guide is meant to get a FlyByWire A320neo beginner from the runway to the designated destination gate. A *beginner* is defined as someone familiar with flying a GA aircraft or different types of airliners. Aviation terminology and know-how is a requirement to fly any airliner, even in Microsoft Flight Simulator. diff --git a/docs/pilots-corner/beginner-guide/descent.md b/docs/pilots-corner/a32nx/a32nx-beginner-guide/descent.md similarity index 94% rename from docs/pilots-corner/beginner-guide/descent.md rename to docs/pilots-corner/a32nx/a32nx-beginner-guide/descent.md index abd15e4a6..e7991489d 100644 --- a/docs/pilots-corner/beginner-guide/descent.md +++ b/docs/pilots-corner/a32nx/a32nx-beginner-guide/descent.md @@ -6,6 +6,7 @@ from cruise altitude through STAR and Instrument Approach up to the final approa The actual final approach (ILS approach) will be covered by a separate chapter. !!! warning "Disclaimer" +This is for simulation purposes only.
The level of detail in this guide is meant to get a FlyByWire A320neo beginner safely from cruise level down to the ILS glideslope. A *beginner* is defined as someone familiar with flying a GA aircraft or different types of airliners. Aviation terminology and know-how is a requirement to fly any airliner even, in Microsoft Flight Simulator. @@ -44,9 +45,9 @@ This guide will cover these phases: Often a STAR contains a clearance point which mustn't be passed without explicit clearance by ATC. If clearance is not given, then a holding must be flown as described in the charts. - Please also have a look at our airliner guide's SIDs and STAR section [SIDs and STARS](../airliner-flying-guide/navigation.md#sids-and-stars) + Please also have a look at our airliner guide's SIDs and STAR section [SIDs and STARS](../../airliner/airliner-flying-guide/navigation.md#sids-and-stars) - Find a good overview over charts in our airliner guide: [Reading a Chart](../airliner-flying-guide/navigation.md#reading-a-chart) + Find a good overview over charts in our airliner guide: [Reading a Chart](../../airliner/airliner-flying-guide/navigation.md#reading-a-chart) - __Approach__This is for simulation purposes only.
The level of detail in this guide is meant to get a FlyByWire A320neo beginner safely from the terminal to the runway hold short point. A *beginner* is defined as someone familiar with flying a GA aircraft or different types of airliners. Aviation terminology and know-how is a requirement to fly any airliner, even in Microsoft Flight Simulator. @@ -79,10 +80,10 @@ The FlyByWire A32NX has a ground operations page on its built-in flyPad EFB (Ele Although Microsoft Flight Simulator also has some pushback functionality built into the default ATC service, this guide will only cover the A32NX pushback functionality. -{loading=lazy} +{loading=lazy} !!! block "" - {loading=lazy align=left width=30%} + {loading=lazy align=left width=30%} After we received clearance to pushback, we will call the pushback tug by pressing the `Call Tug` button on the flyPad. @@ -93,7 +94,7 @@ Although Microsoft Flight Simulator also has some pushback functionality built i After the tug is attached to the nose wheel, we can start pushing back by using the control buttons or the rudder and elevator controls. -See the flyPad documentation for more details: [flyPad Pushback](../../fbw-a32nx/feature-guides/flypados3/ground.md#pushback) +See the flyPad documentation for more details: [flyPad Pushback](../../../aircraft/common/flypados3/ground.md#pushback) --- @@ -292,7 +293,7 @@ If it is required to perform a sharp turn immediately, we may need more than ~ While underway to the runway, perform the following as part of the taxi flow: - Use the tiller or rudder pedals to steer the aircraft. - - See [Nose Wheel and Tiller Operation](../../fbw-a32nx/feature-guides/nw-tiller.md) + - See [Nose Wheel and Tiller Operation](../../../aircraft/a32nx/feature-guides/nw-tiller.md) - Perform a [flight controls check](#flight-controls-check) (if you haven't already). - Verify the ATC clearance for departure. @@ -392,87 +393,12 @@ When approved to cross a runway (active or not) perform the following actions: !!! warning Never cross a runway without express permission from ATC and providing a read back of said instructions. Always ensure maximum safety when crossing. ---- - -## General Resources - -This section provides you with information on understanding the different signs and markings you may see while taxiing at the airport. - -### Airport Signage and Markings - -!!! info "Scenery / Accuracy Issues" - Please be aware that the default scenery or 3rd party sceneries may not be entirely accurate with the posted signage on the ground. However, this guide will explain how to read and understand them. +#### Airport Signage and Markings -#### FAA Quick Reference Guide - -The FAA has a handy guide available for download that contains images of all the pertinent signs you may encounter, their purpose, and location at the airport. - -[Download FAA Guide](https://www.faa.gov/sites/faa.gov/files/airports/runway_safety/publications/QuickReferenceGuideProof8.pdf){ .md-button } +Please see [Airport Signage and Markings](../../airliner/airliner-flying-guide/airport-signage.md). --- -There are two types of signage at airports - operational guidance signs and mandatory instruction signs. - -#### Operational Guidance Signs - -^^Location Signs^^ - -- These signs are yellow text on a black background. Typically, indicates a specific taxiway or runway your aircraft is on or entering. - -^^Direction/Runway Exit Signs^^ - -- Black text on a yellow background. These will have an arrow indicating the direction to turn, which helps pilots identify what taxiways they are approaching or runway exits towards a specified runway. - - {loading=lazy} - -^^Stop Bar Signs^^ - -- White text on a blue background. These are non-standard signs that may appear at some airports, usually indicating which taxiway a stop bar is positioned. Airports usually use more conventional traffic signs you may see on the road, such a regular stop sign. See the [FAA Guide](#faa-quick-reference-guide) for samples. - - {loading=lazy} - -#### Mandatory Instruction Signs - -^^Runway Signs^^ - -- White text on a red background. These signs inform pilots that a runway intersection is ahead. - -^^Holding Position Signs / Markings^^ - -There are typically three very important holding position signs / markings that appear on the ground at airports. At various airports that operate with low visibility, these positions are also paired with a line of red lights across a taxiway to help visually indicate the holding positions. - -1. Runway Holding Position - - Two sets of solid yellow lines and two sets of dashed yellow lines indicate a holding position for a runway ahead. These **must never be crossed** without express permission from ATC. - - {loading=lazy} - - "Holding position markings pattern A ahead of a crossing runway" by Claudius Henrichs [CC BY-SA 2.0](https://creativecommons.org/licenses/by-sa/2.0) - -2. Taxiway Holding Position - - Single dashed yellow line. If this is present along your taxi route, it will indicate a position that ground control may request you stop and hold short before another taxiway. - - { loading=lazy style="width:320px;height:79px" } - -3. ILS Critical Area - - Solid yellow lines that look like a railroad or ladder. These are another form of hold short point but indicate a critical area where your aircraft would violate the ILS approach airspace while on the ground. - - {loading=lazy} - ---- - -### Taxiway Lighting - -Taxiway lighting helps the flight crew and ground crew navigate the airport at night or in low visibility and stop at the appropriate locations as given by ATC. - -There are usually two types of lighting on taxiways - centerline and edge. Depending on the airport operator, the lightning may differ if the airport operates in low visibility conditions. - -- Centerline lighting is green on the principal taxiways located along the taxiway centerline. These lights can alternate between green and yellow when a taxiway crosses a runway, or highlight a "lead-off" taxiway from a runway to join a taxiway. -- Edge lighting is typically blue and characteristically appears at the edges of a taxiway. Spacing can range from 50 - 200 ft apart, usually condensing in distance when approaching an intersection. - -{loading=lazy} - -John Murphy, [CC BY-SA 2.0](https://creativecommons.org/licenses/by-sa/2.0) - This concludes the *Taxi*. Continue with [Takeoff, climb and cruise](takeoff-climb-cruise.md) diff --git a/docs/pilots-corner/beginner-guide/landing.md b/docs/pilots-corner/a32nx/a32nx-beginner-guide/landing.md similarity index 99% rename from docs/pilots-corner/beginner-guide/landing.md rename to docs/pilots-corner/a32nx/a32nx-beginner-guide/landing.md index 22564eccd..cf963d382 100644 --- a/docs/pilots-corner/beginner-guide/landing.md +++ b/docs/pilots-corner/a32nx/a32nx-beginner-guide/landing.md @@ -4,6 +4,7 @@ This guide will explain the correct procedures to fly a final approach and condu !!! warning "Disclaimer" +This is for simulation purposes only.
The level of detail in this guide is meant to get a FlyByWire A320neo beginner currently on approach to intercept the ILS and land the aircraft safely on the runway. A *beginner* is defined as someone familiar with flying a GA aircraft or different types of airliners. Aviation terminology and know-how is a requirement to fly any airliner, even in Microsoft Flight Simulator. @@ -200,7 +201,7 @@ This concludes *Preparation and Checklist for Landing* Although the A320 can do an automatic landing (**Autoland**) we will do a manual landing as this is more common and also more fun. -For an advanced guide on Autoland, see [here](../advanced-guides/flight-guidance/autoland.md). +For an advanced guide on Autoland, see [here](../a32nx-advanced-guides/flight-guidance/autoland.md). We MUST get landing clearance from ATC before we actually are allowed to land. Without landing clearance, we must do a go-around (not part of this beginner guide) before touching the runway. Usually, ATC will have given us clearance at this point. Late clearance is rare and communicated to us beforehand. diff --git a/docs/pilots-corner/beginner-guide/overview.md b/docs/pilots-corner/a32nx/a32nx-beginner-guide/overview.md similarity index 69% rename from docs/pilots-corner/beginner-guide/overview.md rename to docs/pilots-corner/a32nx/a32nx-beginner-guide/overview.md index b5955fda1..5e8c94c56 100644 --- a/docs/pilots-corner/beginner-guide/overview.md +++ b/docs/pilots-corner/a32nx/a32nx-beginner-guide/overview.md @@ -24,18 +24,18 @@ The [Preflight](preflight.md) page contains guides on how to set up relevant dat --- -| Topics | -|:-----------------------------------------------------| -| [Preflight](preflight.md) | -| [Starting the Aircraft](starting-the-aircraft.md) | -| [Preparing the MCDU](preparing-mcdu.md) | -| [Engine Start and Taxi](engine-start-taxi.md) | +| Topics | +|:------------------------------------------------------| +| [Preflight](preflight.md) | +| [Starting the Aircraft](starting-the-aircraft.md) | +| [Preparing the MCDU](preparing-mcdu.md) | +| [Engine Start and Taxi](engine-start-taxi.md) | | [Takeoff, Climb, and Cruise](takeoff-climb-cruise.md) | -| [Descent Planning and Descent](descent.md) | -| [Approach and ILS Landing](landing.md) | -| [After Landing and Taxi to Gate](after-landing.md) | -| [Powering Down](powering-down.md) | -| [Abbreviations](../abbreviations.md) | +| [Descent Planning and Descent](descent.md) | +| [Approach and ILS Landing](landing.md) | +| [After Landing and Taxi to Gate](after-landing.md) | +| [Powering Down](powering-down.md) | +| [Abbreviations](../../airliner/abbreviations.md) | --- diff --git a/docs/pilots-corner/beginner-guide/powering-down.md b/docs/pilots-corner/a32nx/a32nx-beginner-guide/powering-down.md similarity index 97% rename from docs/pilots-corner/beginner-guide/powering-down.md rename to docs/pilots-corner/a32nx/a32nx-beginner-guide/powering-down.md index fb7b1d872..cd47530da 100644 --- a/docs/pilots-corner/beginner-guide/powering-down.md +++ b/docs/pilots-corner/a32nx/a32nx-beginner-guide/powering-down.md @@ -5,6 +5,7 @@ This guide will explain the correct procedures to power down the aircraft when a Obviously, this is not strictly required in a simulator, but for interested sim pilots this might be an interesting process for a more realistic experience. !!! warning "Disclaimer" +This is for simulation purposes only.
The level of detail in this guide is meant to help a FlyByWire A320neo beginner to correctly shut down the aircraft. A *beginner* is defined as someone familiar with flying a GA aircraft or different types of airliners. Aviation terminology and know-how is a requirement to fly any airliner, even in Microsoft Flight Simulator. @@ -106,7 +107,7 @@ Taking care of passengers and luggage with the FlyByWire flyPad: - Connect the Jetway (PAX). - Call cargo/baggage (Baggage). -{loading=lazy} +{loading=lazy} Obviously, this would take a while in real life, and we would not be able to shut down the aircraft before everybody is disembarked. diff --git a/docs/pilots-corner/beginner-guide/preflight.md b/docs/pilots-corner/a32nx/a32nx-beginner-guide/preflight.md similarity index 88% rename from docs/pilots-corner/beginner-guide/preflight.md rename to docs/pilots-corner/a32nx/a32nx-beginner-guide/preflight.md index 86d620c62..5195e2dd6 100644 --- a/docs/pilots-corner/beginner-guide/preflight.md +++ b/docs/pilots-corner/a32nx/a32nx-beginner-guide/preflight.md @@ -23,7 +23,7 @@ You can choose to use other software/websites to plan your route, but when using - [Little Nav Map](https://albar965.github.io/littlenavmap.html){target=new} (Flight Planning and Charts) - [ChartFox](https://chartfox.org/){target=new} (Charts) - [Navigraph](https://navigraph.com/){target=new} (Flight Planning and Charts) **Requires Subscription** - - See our [Custom Flight Management System](../../fbw-a32nx/feature-guides/cFMS.md) page and the [special notes section](../../fbw-a32nx/feature-guides/cFMS.md#special-notes) section. + - See our [Custom Flight Management System](../../../aircraft/a32nx/feature-guides/cFMS.md) page and the [special notes section](../../../aircraft/a32nx/feature-guides/cFMS.md#special-notes) section. ## Flight Plan Import @@ -32,7 +32,7 @@ If you wish to expedite the process of inputting your flight plan on the MCDU, w !!! warning "IMPORTANT" If you plan to import the flight plan from SimBrief, do not select an arrival airport on the MSFS world menu or flight planner. Doing this "initializes" the `FROM/TO` field when loading into your flight, removing the `INIT REQ.` option from the `INIT A` page. -[SimBrief A32NX Features](../../fbw-a32nx/feature-guides/simbrief.md){.md-button} +[SimBrief A32NX Features](../../../aircraft/a32nx/feature-guides/simbrief.md){.md-button} ### Manual Flight Planning @@ -48,13 +48,13 @@ When inputting your flight plan into the MCDU, discontinuities appearing is an i To configure your aircraft, we have provided options onboard the aircraft to load fuel and passengers / baggage. See the following page and note any advisories. -[Fuel and Weights](../../fbw-a32nx/feature-guides/loading-fuel-weight.md){.md-button} +[Fuel and Weights](../../../aircraft/a32nx/feature-guides/loading-fuel-weight.md){.md-button} ## EFB Navigraph Charts To help with navigation during your flight, our flyPad EFB can connect to your Navigraph account to provide access to all the en route charts for your flight! -[EFB Navigraph](../../fbw-a32nx/feature-guides/flypados3/charts.md){.md-button} +[EFB Navigraph](../../../aircraft/common/flypados3/charts.md){.md-button} This concludes the *Preflight* guide. diff --git a/docs/pilots-corner/beginner-guide/preparing-mcdu.md b/docs/pilots-corner/a32nx/a32nx-beginner-guide/preparing-mcdu.md similarity index 93% rename from docs/pilots-corner/beginner-guide/preparing-mcdu.md rename to docs/pilots-corner/a32nx/a32nx-beginner-guide/preparing-mcdu.md index 135bf668e..b5999eaec 100644 --- a/docs/pilots-corner/beginner-guide/preparing-mcdu.md +++ b/docs/pilots-corner/a32nx/a32nx-beginner-guide/preparing-mcdu.md @@ -3,6 +3,7 @@ This guide will help you prepare the MCDU in the A32NX for your departure. It includes a simple route that you can use to follow along easily and replicate in the simulator. !!! warning "Disclaimer" +This is for simulation purposes only.
The level of detail in this guide is meant to provide a FlyByWire A320neo beginner the ability to adequately program the MCDU to conduct and complete a flight. A *beginner* is defined as someone familiar with flying a GA aircraft or different types of airliners. Aviation terminology and know-how is a requirement to fly any airliner, even in Microsoft Flight Simulator. @@ -140,7 +141,7 @@ DATA includes the pages below: For more information and a guide to our simBrief A32NX features, visit the page below: - [FMS (MCDU) and simBrief Integration](../../fbw-a32nx/feature-guides/simbrief.md#using-the-fms-mcdu-and-simbrief-integration){ .md-button } + [FMS (MCDU) and simBrief Integration](../../../aircraft/a32nx/feature-guides/simbrief.md#using-the-fms-mcdu-and-simbrief-integration){ .md-button } ^^FROM/TO Field^^ @@ -167,7 +168,7 @@ The cost index can be found in the image above. !!! tip "Wind Requests" Pilots can choose to import your wind data at this stage through the `WIND/TEMP` option by pressing LSK 4R. For more information on using this feature, please see the guide below. - [Wind Request Guide](../../fbw-a32nx/feature-guides/simbrief.md#wind-request){.md-button} + [Wind Request Guide](../../../aircraft/a32nx/feature-guides/simbrief.md#wind-request){.md-button} !!! warning "" Please also note the following: @@ -208,7 +209,7 @@ Our route for this flight can be found on the 2nd page of the OFP These are procedures that are defined and published that take a flight from the take-off phase to the en route phase. - Also see: [SIDS and STARS](../airliner-flying-guide/navigation.md#sids-and-stars) + Also see: [SIDS and STARS](../../airliner/airliner-flying-guide/navigation.md#sids-and-stars) To program the Standard Instrument Departure (SID): @@ -286,7 +287,7 @@ For the purposes of this guide, we will pre-plan our arrival into EDDF via the ` 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) + Also see: [SIDS and STARS](../../airliner/airliner-flying-guide/navigation.md#sids-and-stars) Find `EDDF` in green in the flight plan OR select `EDDF` in white under `DEST` using the corresponding LSK. @@ -317,10 +318,11 @@ Verify the flight plan by using the vertical slew keys to scroll through it. {loading=lazy} - See our detailed documentation for [Discontinuities](../advanced-guides/flight-planning/disco.md){target=new} to understand how to appropriately handle these when encountered on your F-PLN page. + See our detailed documentation for [Discontinuities](../a32nx-advanced-guides/flight-planning/disco.md){target=new} to understand how to appropriately handle these when +encountered on your F-PLN page. !!! warning "" - Additionally, make note of this [Special Case](../advanced-guides/flight-planning/disco.md#special-case) on the discontinuity page. + Additionally, make note of this [Special Case](../a32nx-advanced-guides/flight-planning/disco.md#special-case) on the discontinuity page. !!! info "Viewing Flight Plan on ND" We can also verify the route looks correct by selecting `Plan` on the EFIS control panel and watching the ND as we scroll through. @@ -383,7 +385,7 @@ On this page, we can input our zero fuel weight (ZFW) and zero fuel weight cente - This page (INIT FUEL PRED) has a ZFW/ZFWCG value. **Reminder:** After engines are started, INIT FUEL PRED changes to the FUEL PRED page. - At least one engine is running. - Please see our [Fuel and Weights Guide](../../fbw-a32nx/feature-guides/loading-fuel-weight.md) for more detailed information. + Please see our [Fuel and Weights Guide](../../../aircraft/a32nx/feature-guides/loading-fuel-weight.md) for more detailed information. The A32NX can autopopulate this information. @@ -398,7 +400,7 @@ Now we can add our fuel on board (FOB). The amount we input in this field can be !!! info "Loading Fuel" - Via the EFB - [Learn How](../../fbw-a32nx/feature-guides/flypados3/dispatch.md#fuel-page) + Via the EFB - [Learn How](../../../aircraft/common/flypados3/dispatch.md#fuel-page) ^^ECAM FOB^^ @@ -440,7 +442,7 @@ The performance page changes based on the relative stages of flight until we lan The flyPad onboard the aircraft is capable of calculating your required takeoff performance for your flight. Visit our flyPad Performance Page guide for more information. -[flyPad Performance Page](../../fbw-a32nx/feature-guides/flypados3/performance.md){target=new .md-button} +[flyPad Performance Page](../../../aircraft/common/flypados3/performance.md){target=new .md-button} For this flight, we will be taking off with a `1+F` flaps configuration. @@ -474,12 +476,12 @@ For this flight, we will be taking off with a `1+F` flaps configuration. GW CG Values can be found: - - On the [Payload Tab on the Grounds Services Page](../../fbw-a32nx/feature-guides/loading-fuel-weight.md#finding-the-payload-screen) in the flyPad EFB. + - On the [Payload Tab on the Grounds Services Page](../../../aircraft/a32nx/feature-guides/loading-fuel-weight.md#finding-the-payload-screen) in the flyPad EFB. - On the [Fuel Prediction](../a32nx-briefing/mcdu/fuel-pred.md) page in the MCDU. CG to THS calculation: - - CG to THS can be found in the downloable FBW checklist in our [Standard Operating Procedures](../SOP.md#normal-procedures) resources page. + - CG to THS can be found in the downloable FBW checklist in our [Standard Operating Procedures](../a32nx-sop.md#normal-procedures) resources page. - The CG/THS markings on the trim wheel can be used to validate this. Make sure to update this value or set the correct trim once your engines have started. @@ -504,7 +506,7 @@ Read the following tip for more information on FLEX temp. Pilots can use the flyPad Performance Page to calculate Flex Temp for takeoff. The flyPad will also calculate if TOGA is the preferred thrust setting for takeoff and notify the pilot through the EFB. -[flyPad Performance Page](../../fbw-a32nx/feature-guides/flypados3/performance.md){target=new .md-button} +[flyPad Performance Page](../../../aircraft/common/flypados3/performance.md){target=new .md-button} !!! tip "What is Flex Temp?" Flex temp is entered into the MCDU, enabling the computer to use the pilot-specified air temperature to allow for take-off thrust that is less than TOGA but not less than CLB. This is a method of creating cost savings by increasing engine life, resulting in reduced overhaul and fuel costs. This value is normally calculated via a pilot's company EFB or other tools. @@ -530,7 +532,7 @@ Our SID chart mentions that the TRANS ALT for this departure is 5000 ft. Pilots can use the flyPad Performance Page to calculate V-Speeds for takeoff. -[flyPad Performance Page](../../fbw-a32nx/feature-guides/flypados3/performance.md){target=new .md-button} +[flyPad Performance Page](../../../aircraft/common/flypados3/performance.md){target=new .md-button} ??? warning "Stable Version Only" V-Speeds are normally calculated by a company EFB or other tools. This feature is not yet available in the stable version. @@ -564,7 +566,7 @@ To enter your assigned code find the ATC/TCAS Panel on the bottom right portion ## A32NX simBrief Integration -This section has been moved to our dedicated [simBrief Integration](../../fbw-a32nx/feature-guides/simbrief.md#importing-the-simbrief-ofp-to-the-fms-mcdu) feature guide. +This section has been moved to our dedicated [simBrief Integration](../../../aircraft/a32nx/feature-guides/simbrief.md#importing-the-simbrief-ofp-to-the-fms-mcdu) feature guide. --- diff --git a/docs/pilots-corner/beginner-guide/starting-the-aircraft.md b/docs/pilots-corner/a32nx/a32nx-beginner-guide/starting-the-aircraft.md similarity index 98% rename from docs/pilots-corner/beginner-guide/starting-the-aircraft.md rename to docs/pilots-corner/a32nx/a32nx-beginner-guide/starting-the-aircraft.md index 973947998..fbab4069d 100644 --- a/docs/pilots-corner/beginner-guide/starting-the-aircraft.md +++ b/docs/pilots-corner/a32nx/a32nx-beginner-guide/starting-the-aircraft.md @@ -3,6 +3,7 @@ This guide will assist you with starting your aircraft. It includes images to assist you with understanding the locations of all buttons and switches. !!! warning "Disclaimer" +This is for simulation purposes only.
The level of detail in this guide is meant to teach a FlyByWire A320neo beginner to start the aircraft correctly. A *beginner* is defined as someone familiar with flying a GA aircraft or different types of airliners. Aviation terminology and know-how is a requirement to fly any airliner, even in Microsoft Flight Simulator. @@ -256,7 +257,7 @@ Verify on the Upper ECAM that your aircraft has enough fuel for the flight.  -If we do not have enough fuel for the flight, we can refuel via the [flyPad EFB Fuel Page](../../fbw-a32nx/feature-guides/flypados3/ground.md#fuel-page) . +If we do not have enough fuel for the flight, we can refuel via the [flyPad EFB Fuel Page](../../../aircraft/common/flypados3/ground.md#fuel-page) . --- diff --git a/docs/pilots-corner/beginner-guide/takeoff-climb-cruise.md b/docs/pilots-corner/a32nx/a32nx-beginner-guide/takeoff-climb-cruise.md similarity index 99% rename from docs/pilots-corner/beginner-guide/takeoff-climb-cruise.md rename to docs/pilots-corner/a32nx/a32nx-beginner-guide/takeoff-climb-cruise.md index 58fe99f9f..13b0ebd46 100644 --- a/docs/pilots-corner/beginner-guide/takeoff-climb-cruise.md +++ b/docs/pilots-corner/a32nx/a32nx-beginner-guide/takeoff-climb-cruise.md @@ -3,6 +3,7 @@ This guide will explain the correct procedures to accomplish takeoff, climb and establish cruise altitude. !!! warning "Disclaimer" +This is for simulation purposes only.
The level of detail in this guide is meant to get a FlyByWire A320neo beginner safely up in the air and to cruise level under normal conditions, while simplifying details which are not (yet) important for a beginner. A *beginner* is defined as someone familiar with flying a GA aircraft or different types of airliners. Aviation terminology and know-how is a requirement to fly any airliner, even in Microsoft Flight Simulator. @@ -386,7 +387,7 @@ Typically, the climb to the flight plan's cruise level (e.g., FL210) happens in If the selected target V/S is too high (relative to the current thrust condition and speed), the FMGC will steer the aircraft to the target V/S, but the aircraft will also accelerate or decelerate. When the speed reaches its authorized limit, V/S automatically decreases to maintain the minimum or maximum speed limit. - See also [Protections](../advanced-guides/protections/overview.md). + See also [Protections](../a32nx-advanced-guides/protections/overview.md). **Passing 10,000ft**
+
+ This is for simulation purposes only.
+ --- ## Quick Links @@ -27,7 +27,7 @@ but are omitted in this briefing. | Quick Links | |:--------------------------------------| | [Flight-Deck](flight-deck/index.md) | -| [Flight-Deck A32NX API](../../fbw-a32nx/a32nx-api/a32nx-flightdeck-api.md) | +| [Flight-Deck A32NX API](../../../aircraft/a32nx/a32nx-api/a32nx-flightdeck-api.md) | | [ECAM](ecam/index.md) | | [PFD](pfd/index.md) | | [MCDU](mcdu/index.md) | diff --git a/docs/pilots-corner/a32nx-briefing/limitations.md b/docs/pilots-corner/a32nx/a32nx-briefing/limitations.md similarity index 99% rename from docs/pilots-corner/a32nx-briefing/limitations.md rename to docs/pilots-corner/a32nx/a32nx-briefing/limitations.md index 253849cd3..a82f5ebd1 100644 --- a/docs/pilots-corner/a32nx-briefing/limitations.md +++ b/docs/pilots-corner/a32nx/a32nx-briefing/limitations.md @@ -144,7 +144,7 @@ This list is incomplete, but should mention the most important operational limit !!! note The AP or FD in OP DES or DES mode can be used in approach. However, its use is only permitted if the FCU selected altitude is set to, or above, the higher of the two: MDA/MDH or 500 ft AGL. -See also [Autoland](../advanced-guides/flight-guidance/autoland.md#aircraft-limitations) +See also [Autoland](../a32nx-advanced-guides/flight-guidance/autoland.md#aircraft-limitations) ## Engines diff --git a/docs/pilots-corner/a32nx-briefing/mcdu/.pages b/docs/pilots-corner/a32nx/a32nx-briefing/mcdu/.pages similarity index 100% rename from docs/pilots-corner/a32nx-briefing/mcdu/.pages rename to docs/pilots-corner/a32nx/a32nx-briefing/mcdu/.pages diff --git a/docs/pilots-corner/a32nx-briefing/mcdu/atc-comm.md b/docs/pilots-corner/a32nx/a32nx-briefing/mcdu/atc-comm.md similarity index 64% rename from docs/pilots-corner/a32nx-briefing/mcdu/atc-comm.md rename to docs/pilots-corner/a32nx/a32nx-briefing/mcdu/atc-comm.md index 45223c2fc..15cda628d 100644 --- a/docs/pilots-corner/a32nx-briefing/mcdu/atc-comm.md +++ b/docs/pilots-corner/a32nx/a32nx-briefing/mcdu/atc-comm.md @@ -4,4 +4,4 @@ This page will not be documented in this guide. -Use our [Hoppie ACARS Guide](../../../fbw-a32nx/feature-guides/hoppie.md) instead. +Use our [Hoppie ACARS Guide](../../../../aircraft/a32nx/feature-guides/hoppie.md) instead. diff --git a/docs/pilots-corner/a32nx-briefing/mcdu/data.md b/docs/pilots-corner/a32nx/a32nx-briefing/mcdu/data.md similarity index 98% rename from docs/pilots-corner/a32nx-briefing/mcdu/data.md rename to docs/pilots-corner/a32nx/a32nx-briefing/mcdu/data.md index 42972e50e..836f51bb4 100644 --- a/docs/pilots-corner/a32nx-briefing/mcdu/data.md +++ b/docs/pilots-corner/a32nx/a32nx-briefing/mcdu/data.md @@ -230,7 +230,7 @@ stored in the database. Currently, not all of these are available in the FBW A32NX for Microsoft Flight Simulator. - STORED WAYPOINTS (1R) - - See [Stored Waypoints Guide](../../advanced-guides/data-management.md#stored-waypoints). + - See [Stored Waypoints Guide](../../a32nx-advanced-guides/data-management.md#stored-waypoints). - STORED NAVAIDS (2R) - STORED RUNWAYS (3R) diff --git a/docs/pilots-corner/a32nx-briefing/mcdu/dir.md b/docs/pilots-corner/a32nx/a32nx-briefing/mcdu/dir.md similarity index 96% rename from docs/pilots-corner/a32nx-briefing/mcdu/dir.md rename to docs/pilots-corner/a32nx/a32nx-briefing/mcdu/dir.md index b58c1070d..58a0139ea 100644 --- a/docs/pilots-corner/a32nx-briefing/mcdu/dir.md +++ b/docs/pilots-corner/a32nx/a32nx-briefing/mcdu/dir.md @@ -8,7 +8,7 @@ The DIR TO page is used by the flight crew to select waypoints from the flight p When in NAV mode, this changes the currently active leg and waypoint. In HDG mode, activation of a DIR TO will switch to NAV mode for a direct course to the new waypoint. -See our [DIRECT-TO page](../../advanced-guides/flight-planning/direct.md) on how to use this page. +See our [DIRECT-TO page](../../a32nx-advanced-guides/flight-planning/direct.md) on how to use this page. ## Usage diff --git a/docs/pilots-corner/a32nx-briefing/mcdu/f-pln.md b/docs/pilots-corner/a32nx/a32nx-briefing/mcdu/f-pln.md similarity index 96% rename from docs/pilots-corner/a32nx-briefing/mcdu/f-pln.md rename to docs/pilots-corner/a32nx/a32nx-briefing/mcdu/f-pln.md index ea15509b4..8762aec37 100644 --- a/docs/pilots-corner/a32nx-briefing/mcdu/f-pln.md +++ b/docs/pilots-corner/a32nx/a32nx-briefing/mcdu/f-pln.md @@ -11,13 +11,13 @@ Revisions to the lateral and vertical flight plans can be made from these pages. !!! tip "Additional Resources" Also see the following resources for further feature information when utilizing the F-PLN page: - - [MCDU Setup Procedure](../../beginner-guide/preparing-mcdu.md) in our [Beginner Guide](../../beginner-guide/overview.md). + - [MCDU Setup Procedure](../../a32nx-beginner-guide/preparing-mcdu.md) in our [Beginner Guide](../../a32nx-beginner-guide/overview.md). - Advance Flight Planning Guides - - [Direct To (DIR TO)](../../advanced-guides/flight-planning/direct.md) - - [Discontinuities](../../advanced-guides/flight-planning/disco.md) - - [Fix Info](../../advanced-guides/flight-planning/fixinfo.md) - - [Holds](../../advanced-guides/flight-planning/holds.md) - - [Leg Types](../../advanced-guides/flight-planning/leg-types.md) + - [Direct To (DIR TO)](../../a32nx-advanced-guides/flight-planning/direct.md) + - [Discontinuities](../../a32nx-advanced-guides/flight-planning/disco.md) + - [Fix Info](../../a32nx-advanced-guides/flight-planning/fixinfo.md) + - [Holds](../../a32nx-advanced-guides/flight-planning/holds.md) + - [Leg Types](../../a32nx-advanced-guides/flight-planning/leg-types.md) {loading=lazy} @@ -145,7 +145,7 @@ STAR revisions are done only at a destination airport (Destination page). - FIX INFO (1R) - Used for entering radial, radius and abeam intercept points. - Only available on the current FROM waypoint (first waypoint when opening the F-PLN page). - - See the [FIX INFO Guide](../../advanced-guides/flight-planning/fixinfo.md) for more information. + - See the [FIX INFO Guide](../../a32nx-advanced-guides/flight-planning/fixinfo.md) for more information. - ARRIVAL (1R) - Used for selecting the arrival runway and procedures (STAR, APPR, TRANS, etc.) @@ -174,7 +174,7 @@ STAR revisions are done only at a destination airport (Destination page). - NEXT WPT (3R) - A new waypoint after the selected one can be entered into this field. - If it is a waypoint already in the flight plan after the current waypoint, then all intermediate waypoints are removed. - - If it is a new waypoint, a [discontinuity](../../advanced-guides/flight-planning/disco.md) is created. + - If it is a new waypoint, a [discontinuity](../../a32nx-advanced-guides/flight-planning/disco.md) is created. - Only available on departure, waypoint, and destination. - ENABLE ALTN (4L) @@ -186,7 +186,7 @@ STAR revisions are done only at a destination airport (Destination page). - Used to change the destination airport. - Will create a temporary flight plan direct to the new destination. - Clears all waypoints between the current waypoint and the new destination. - - Creates a [discontinuity](../../advanced-guides/flight-planning/disco.md). + - Creates a [discontinuity](../../a32nx-advanced-guides/flight-planning/disco.md). - Only available on departure, waypoint. - ALTN (5L) @@ -368,7 +368,7 @@ The FIX INFO pages are used to create waypoint intersections of the flight plan !!! info "" Currently, only partly implemented in the FBW A32NX for Microsoft Flight Simulator. -See [Feature Guide: Fix Info](../../../pilots-corner/advanced-guides/flight-planning/fixinfo.md) +See [Feature Guide: Fix Info](../../a32nx-advanced-guides/flight-planning/fixinfo.md) The FIX INFO pages can be accessed from the LAT REV page of the FROM waypoint. @@ -390,7 +390,7 @@ Visual example for intersections: The HOLD page is used to enter a holding pattern for a waypoint. The HOLD page can be accessed from the LAT REV page of the FROM waypoint. -See or guide for [HOLDS](../../advanced-guides/flight-planning/holds.md#programming-holds). +See or guide for [HOLDS](../../a32nx-advanced-guides/flight-planning/holds.md#programming-holds). ## AIRWAYS Page diff --git a/docs/pilots-corner/a32nx-briefing/mcdu/fuel-pred.md b/docs/pilots-corner/a32nx/a32nx-briefing/mcdu/fuel-pred.md similarity index 100% rename from docs/pilots-corner/a32nx-briefing/mcdu/fuel-pred.md rename to docs/pilots-corner/a32nx/a32nx-briefing/mcdu/fuel-pred.md diff --git a/docs/pilots-corner/a32nx-briefing/mcdu/index.md b/docs/pilots-corner/a32nx/a32nx-briefing/mcdu/index.md similarity index 79% rename from docs/pilots-corner/a32nx-briefing/mcdu/index.md rename to docs/pilots-corner/a32nx/a32nx-briefing/mcdu/index.md index dde821bed..ac2345a31 100644 --- a/docs/pilots-corner/a32nx-briefing/mcdu/index.md +++ b/docs/pilots-corner/a32nx/a32nx-briefing/mcdu/index.md @@ -44,11 +44,11 @@ This section describes the MCDU in detail, covering each page and also the stand !!! tip "Additional Resources" Also see the following resources for further feature information: - - [MCDU Setup Procedure](../../beginner-guide/preparing-mcdu.md) in our [Beginner Guide](../../beginner-guide/overview.md). + - [MCDU Setup Procedure](../../a32nx-beginner-guide/preparing-mcdu.md) in our [Beginner Guide](../../a32nx-beginner-guide/overview.md). - Advance Flight Planning Guides - - [Direct To (DIR TO)](../../advanced-guides/flight-planning/direct.md) - - [Discontinuities](../../advanced-guides/flight-planning/disco.md) - - [Fix Info](../../advanced-guides/flight-planning/fixinfo.md) - - [Holds](../../advanced-guides/flight-planning/holds.md) - - [Leg Types](../../advanced-guides/flight-planning/leg-types.md) + - [Direct To (DIR TO)](../../a32nx-advanced-guides/flight-planning/direct.md) + - [Discontinuities](../../a32nx-advanced-guides/flight-planning/disco.md) + - [Fix Info](../../a32nx-advanced-guides/flight-planning/fixinfo.md) + - [Holds](../../a32nx-advanced-guides/flight-planning/holds.md) + - [Leg Types](../../a32nx-advanced-guides/flight-planning/leg-types.md) diff --git a/docs/pilots-corner/a32nx-briefing/mcdu/init.md b/docs/pilots-corner/a32nx/a32nx-briefing/mcdu/init.md similarity index 100% rename from docs/pilots-corner/a32nx-briefing/mcdu/init.md rename to docs/pilots-corner/a32nx/a32nx-briefing/mcdu/init.md diff --git a/docs/pilots-corner/a32nx-briefing/mcdu/interface.md b/docs/pilots-corner/a32nx/a32nx-briefing/mcdu/interface.md similarity index 100% rename from docs/pilots-corner/a32nx-briefing/mcdu/interface.md rename to docs/pilots-corner/a32nx/a32nx-briefing/mcdu/interface.md diff --git a/docs/pilots-corner/a32nx-briefing/mcdu/mcdu-menu.md b/docs/pilots-corner/a32nx/a32nx-briefing/mcdu/mcdu-menu.md similarity index 91% rename from docs/pilots-corner/a32nx-briefing/mcdu/mcdu-menu.md rename to docs/pilots-corner/a32nx/a32nx-briefing/mcdu/mcdu-menu.md index 6c93e82cc..24e51b366 100644 --- a/docs/pilots-corner/a32nx-briefing/mcdu/mcdu-menu.md +++ b/docs/pilots-corner/a32nx/a32nx-briefing/mcdu/mcdu-menu.md @@ -53,7 +53,7 @@ This page lists the various systems which are accessible via the MCDU. The syste - INIT/PRES (1L) --> See [INIT/PRES](#initpres-page) - WX REQUEST (2L) --> See [WX REQUEST](#wx-request-page) - ATIS (3L) --> See [ATIS](#atis-page) -- FREE TEXT (1R) --> See [Free Text Guide](../../../fbw-a32nx/feature-guides/freetext.md) +- FREE TEXT (1R) --> See [Free Text Guide](../../../../aircraft/a32nx/feature-guides/freetext.md) - RECEIVED MESSAGES (3R) - Shows list of received messages (WX, ATIS, Free Text). - Press the LSK left of the `<` to read the full message @@ -79,7 +79,7 @@ This page is used to initialize the FMS with the flight plan from SimBrief. Press `INIT DATA REQ*` to start the SimBrief import. -Also see [SimBrief Integration](../../../fbw-a32nx/feature-guides/simbrief.md) for more details. +Also see [SimBrief Integration](../../../../aircraft/a32nx/feature-guides/simbrief.md) for more details. The rest of these two pages is for reviewing the imported data. The second page also provides some information about various times for events like doors closed, takeoff, etc. Some of these are only available after the flight. @@ -88,7 +88,7 @@ The rest of these two pages is for reviewing the imported data. The second page  This page is used to request weather data from the -[configured data source](../../../fbw-a32nx/feature-guides/flypados3/settings.md#atsuaoc). +[configured data source](../../../../aircraft/common/flypados3/settings.md#atsuaoc). - WX TYPE (1L) - Change the requested data between METAR and TAF. @@ -103,7 +103,7 @@ This page is used to request weather data from the  This page is used to request ATIS data from the -[configured data source](../../../fbw-a32nx/feature-guides/flypados3/settings.md#atsuaoc). +[configured data source](../../../../aircraft/common/flypados3/settings.md#atsuaoc). - AIRPORT ICAO (1L) - Enter the ICAO code of the airport for which the ATIS is requested. diff --git a/docs/pilots-corner/a32nx-briefing/mcdu/messages.md b/docs/pilots-corner/a32nx/a32nx-briefing/mcdu/messages.md similarity index 100% rename from docs/pilots-corner/a32nx-briefing/mcdu/messages.md rename to docs/pilots-corner/a32nx/a32nx-briefing/mcdu/messages.md diff --git a/docs/pilots-corner/a32nx-briefing/mcdu/perf.md b/docs/pilots-corner/a32nx/a32nx-briefing/mcdu/perf.md similarity index 97% rename from docs/pilots-corner/a32nx-briefing/mcdu/perf.md rename to docs/pilots-corner/a32nx/a32nx-briefing/mcdu/perf.md index 19efa52e9..dbdda7381 100644 --- a/docs/pilots-corner/a32nx-briefing/mcdu/perf.md +++ b/docs/pilots-corner/a32nx/a32nx-briefing/mcdu/perf.md @@ -42,7 +42,7 @@ Prompts on each PERF page: !!! tip In the FlyByWire A32NX, pilots can calculate takeoff performance data via the flyPad. Visit our flyPad Performance Page guide for more information. - [flyPad Performance Page](../../../fbw-a32nx/feature-guides/flypados3/performance.md){target=new .md-button} + [flyPad Performance Page](../../../../aircraft/common/flypados3/performance.md){target=new .md-button} !!! warning "Not Available in the Stable Version; you can instead click on the LSK next to V1, VR and V2 to let the aircraft calculate the V-Speeds for you." @@ -88,11 +88,11 @@ Prompts on each PERF page: - FLAPS/THS (3R) - Positions of the flaps and the trimmable horizontal stabilizer (THS) at takeoff to be entered by the crew. - Can be edited until takeoff, by entering “UP X.X” or “X.X UP”, or “DN X.X” or “X.X DN” for the THS. - - See also the [Beginner Guide PERF TAKEOFF THS](../../beginner-guide/preparing-mcdu.md#perf) + - See also the [Beginner Guide PERF TAKEOFF THS](../../a32nx-beginner-guide/preparing-mcdu.md#perf) - FLX TO TEMP (4R) - Flight crew inserts the FLX TO temperature in Celsius for FLX takeoff setting purposes. It can only be entered during preflight. This value will be sent to the FADEC and displayed on the upper ECAM display. - - See also the [Beginner Guide PERF TAKEOFF Flex Temp](../../beginner-guide/preparing-mcdu.md#flex-temp) + - See also the [Beginner Guide PERF TAKEOFF Flex Temp](../../a32nx-beginner-guide/preparing-mcdu.md#flex-temp) - ENG OUT ACC (5R) - Engine-out acceleration altitude, as defined in the database, or manually entered by the flight crew. @@ -343,7 +343,7 @@ Prompts on each PERF page: - Can't be modified here. - O, S, F, V~LS~ Speeds (2M, 3M, 4M) - - See [Speeds](../../abbreviations.md#additional-speeds) and [V-Speeds](../../abbreviations.md#v-speeds) for more information. + - See [Speeds](../../../airliner/abbreviations.md#additional-speeds) and [V-Speeds](../../../airliner/abbreviations.md#v-speeds) for more information. - BARO (2R): - The Minimum Descent/Decision Altitude (MDA) with associated brackets, or diff --git a/docs/pilots-corner/a32nx-briefing/mcdu/prog.md b/docs/pilots-corner/a32nx/a32nx-briefing/mcdu/prog.md similarity index 100% rename from docs/pilots-corner/a32nx-briefing/mcdu/prog.md rename to docs/pilots-corner/a32nx/a32nx-briefing/mcdu/prog.md diff --git a/docs/pilots-corner/a32nx-briefing/mcdu/rad-nav.md b/docs/pilots-corner/a32nx/a32nx-briefing/mcdu/rad-nav.md similarity index 100% rename from docs/pilots-corner/a32nx-briefing/mcdu/rad-nav.md rename to docs/pilots-corner/a32nx/a32nx-briefing/mcdu/rad-nav.md diff --git a/docs/pilots-corner/a32nx-briefing/mcdu/sec-f-plan.md b/docs/pilots-corner/a32nx/a32nx-briefing/mcdu/sec-f-plan.md similarity index 100% rename from docs/pilots-corner/a32nx-briefing/mcdu/sec-f-plan.md rename to docs/pilots-corner/a32nx/a32nx-briefing/mcdu/sec-f-plan.md diff --git a/docs/pilots-corner/a32nx-briefing/pfd/.pages b/docs/pilots-corner/a32nx/a32nx-briefing/pfd/.pages similarity index 100% rename from docs/pilots-corner/a32nx-briefing/pfd/.pages rename to docs/pilots-corner/a32nx/a32nx-briefing/pfd/.pages diff --git a/docs/pilots-corner/a32nx-briefing/pfd/altitude-indicator.md b/docs/pilots-corner/a32nx/a32nx-briefing/pfd/altitude-indicator.md similarity index 56% rename from docs/pilots-corner/a32nx-briefing/pfd/altitude-indicator.md rename to docs/pilots-corner/a32nx/a32nx-briefing/pfd/altitude-indicator.md index 348dcb115..6c9de0583 100644 --- a/docs/pilots-corner/a32nx-briefing/pfd/altitude-indicator.md +++ b/docs/pilots-corner/a32nx/a32nx-briefing/pfd/altitude-indicator.md @@ -1,19 +1,19 @@ - + # Altitude Indicator
- 
+
-
+
+
+ 
+
+
+
-
+
+
+
+
+
+
-
+
+
-
+
-
+
+
+
-
+
+
+
+ This is for simulation purposes only.
+ +## Quick Links + +[Beginner Guide](a32nx-beginner-guide/overview.md){ .md-button } +[Advanced Guides](a32nx-advanced-guides/overview.md){ .md-button }x§ +[A320neo Pilot Briefing](a32nx-briefing/index.md){ .md-button } + +## Topics + +| Featured List | +|:-----------------------------------------------------------------------| +| [Beginner Guide](a32nx-beginner-guide/overview.md) | +| [Advanced Guides](a32nx-advanced-guides/overview.md) | +| [A320neo Pilot Briefing](a32nx-briefing/index.md) | +| [Standard Operating Procedures](a32nx-sop.md) | +| [Airliner Flying Guide](../airliner/airliner-flying-guide/overview.md) | diff --git a/docs/pilots-corner/a380x/.pages b/docs/pilots-corner/a380x/.pages new file mode 100644 index 000000000..6dc052d47 --- /dev/null +++ b/docs/pilots-corner/a380x/.pages @@ -0,0 +1,9 @@ +title: A380X Corner +nav: + - Overview: index.md + - Beginner Guide: a380x-beginner-guide + - Advanced Guides: a380x-advanced-guides + - A380 Pilot Briefing: a380x-briefing + - Standard Operating Procedures: a380x-sop.md + - ... + diff --git a/docs/fbw-a32nx/support/.pages b/docs/pilots-corner/a380x/a380x-advanced-guides/.pages similarity index 60% rename from docs/fbw-a32nx/support/.pages rename to docs/pilots-corner/a380x/a380x-advanced-guides/.pages index 3a13d259a..2138657df 100644 --- a/docs/fbw-a32nx/support/.pages +++ b/docs/pilots-corner/a380x/a380x-advanced-guides/.pages @@ -3,9 +3,7 @@ # - Titles for specific pages or subdirectories # - Order of pages (otherwise alphabetical order) -title: Support +title: Advanced Guides nav: - - Support Guide: index.md - - reported-issues.md - - performance-tips.md - - ... + - Overview: overview.md + - OANS / BTV: oans-btv.md diff --git a/docs/pilots-corner/a380x/a380x-advanced-guides/oans-btv.md b/docs/pilots-corner/a380x/a380x-advanced-guides/oans-btv.md new file mode 100644 index 000000000..dc69d6857 --- /dev/null +++ b/docs/pilots-corner/a380x/a380x-advanced-guides/oans-btv.md @@ -0,0 +1,111 @@ +# Onboard Airport Navigation System (OANS) & Brake To Vacate (BTV) + +Both the OANS (also known as Airport Navigation Function on the A350) and BTV add a high operational benefit to the A380, +simplyfing navigation on complex airports and allowing optimal turnaround times. + +This advanced guide introduces the basic operation of the airport navigation function, the approaching runway advisory as +well as setup and operation of BTV. + +!!! warning "Disclaimer" +Navigraph Unlimited subscription required
+ The OANS function currently relies on data provided by Navigraph, which can only be accessed with a Navigraph Unlimited + subscription. + + We're working on enabling OANS using the MSFS scenery data, however this is work-in-progress. + + BTV can be set up manually without the OANS airport map through the OANS control panel, for details see [Without Navigraph Unlimited](#without-navigraph-unlimited) + +This is for simulation purposes only.
+ +--- + +## Airport navigation + +The OANS features a moving airport map on the flight crew's navigation display (ND). Any airport contained in the Navigraph +AMDB database can be selected for display. + +On the ground at the departure airport, the airport map should be loaded automatically. +Airports can be selected manually through the OANS control panel, which can be opened via the arrow button on the lower +right of the ND. After selection of an airport, a click on "DISPLAY AIRPORT" loads the airport map. + + + +The OANS airport map is active in ROSE NAV, ARC and PLAN EFIS modes. In PLAN mode, any airport of the database can be displayed. +In all modes, the center of the map can be moved using the mouse (click and drag in the navigation display). + +If you want to center the map on the aircraft again, double click on the map to open the context menu and select "CENTER ON ACFT". + + + +## Approaching Runway Advisory + +If the aircraft is on the ground and ground speed is below 40 knots, OANS continuously checks the aircraft protection area +in front of the aircraft (as wide as the wingspan, projected 7 seconds ahead) for runways. When detecting a runway inside this +area, an advisory is triggered on the PFD and ND. The advisory disappears when the above conditions aren't met anymore, or +the aircraft has entered the runway. + +There is no aural warning (as RAAS). + + + +## BTV setup + +### With Navigraph Unlimited + +As part of the descent preparations, BTV is usually set up. After having selected the landing runway in the FMS, switch +the EFIS mode selector to PLAN, turn the range selector to ZOOM and load the destination airport using the OANS control panel. +The airport map now shows your destination airport, with the FMS landing runway marked with a green arrow in front of the +runway identifier (QFU). Clicking on the runway identifier selects this runway for BTV. + +After selecting a runway, OANS displays two magenta lines projecting the required minimal stopping distance for DRY and WET +conditions. The targeted exit should be chosen after the WET line only, this provides a safety margin. To finalize the +selection, the runway exit is selected by clicking on the corresponding label. +The upper left of the ND now shows: + +- The runway identifier, length and bearing +- The exit identifier, and requested stopping distance +- The runway occupancy time (ROT) in seconds +- The turnaround time in minutes, with full reverse and idle reverse during rollout + + + + +??? info "Without Navigraph Unlimited" + ### Without Navigraph Unlimited + + Provided the landing runway is set in the FMS, BTV can also be set up without the airport map from the OANS. Turn the EFIS range + selector to ZOOM, and open the OANS control panel by clicking on the arrow symbol on the lower right of the ND. + + Change to the "MAP DATA" tab, check that the selected landing runway is correct and enter the desired stopping distance in the input + field next to "BTV STOP DISTANCE" (don't forget to finish by pressing the enter key). + +  + +### Finalize BTV Setup + +To finalize the setup, the auto brake mode selector knob is turned to the "BTV" option, which arms BTV (this should be +checked in the PFD FMA). + + + + +## BTV operation after touchdown + +After touchdown of the main and nose wheels, BTV will become active and annunciated in the FMA. BTV monitors the deceleration of the aircraft with respect to the aircraft position and the exit selected and calculates when to start apply braking. + +Braking with BTV is quite different to standard autobrake modes, with BTV most of the braking happens very late in the landing roll and can be a bit disconcerting initially. + +This is done to minimise the energy absorbed by the brakes, lowering the brake temperatures and enabling a quicker turnaround. + +A green bar indicates the predicted stopping distance. + + + +BTV disarms, when one of these conditions apply: + +- The aircraft reaches the runway exit at the release speed of 10 knots +- Flight crew applies a larger braking force through the pedals than BTV +- Auto brake mode selector is turned to the DISARM position +- A/THR instinctive disconnect push buttons (on the outside of the thrust levers) is pushed (This is the normal method of disarming, at 70kts groundspeed) + +For the last three conditions, the "AUTO BRK OFF" memo and aural callout will be triggered. diff --git a/docs/pilots-corner/a380x/a380x-advanced-guides/overview.md b/docs/pilots-corner/a380x/a380x-advanced-guides/overview.md new file mode 100644 index 000000000..58021ab8d --- /dev/null +++ b/docs/pilots-corner/a380x/a380x-advanced-guides/overview.md @@ -0,0 +1,38 @@ +--- +title: A380X Advanced Guides - Overview +description: The A380X Advanced Guides provide additional information on how to operate the FlyByWire A380X aircraft beyond the Beginner Guide. +--- + + + +# Overview + +Welcome to the A380X Advanced Guides. + +This is a collection of guides and tutorials for real A380 features which go beyond the scope of our beginner guide. This collection will grow over time as we add topics and also add features to the A380X add-on. + +Each page was reviewed by an A380 type rated pilot and provides accurate information for aircraft operation. + +!!! info "Airline SOP" + Please be aware that different airlines may have slightly different procedures at different stages of flight. + +This is for simulation purposes only.
+ +--- + +## Topics + +| Quick Links | +|:-----------------------------------------------| +| [Onboard Airport Navigation System (OANS) & Brake To Vacate (BTV)](oans-btv.md) | + +--- + +If you have any issues or feedback with this guide, please file an issue here: + +[:fontawesome-brands-github:{: .github } - **FBW Docs Issues**](https://github.com/flybywiresim/docs/issues){target=new} + +For general questions, please visit our Discord: + +[:fontawesome-brands-discord:{: .discord } - **Discord Link**](https://discord.gg/flybywire){target=new} + diff --git a/docs/pilots-corner/a380x/a380x-beginner-guide/.pages b/docs/pilots-corner/a380x/a380x-beginner-guide/.pages new file mode 100644 index 000000000..55ef8acb1 --- /dev/null +++ b/docs/pilots-corner/a380x/a380x-beginner-guide/.pages @@ -0,0 +1,17 @@ +# Edit this page to get: +# - Title for the whole directory +# - Titles for specific pages or subdirectories +# - Order of pages (otherwise alphabetical order) + +title: Beginner Guide +nav: + - Overview: overview.md + - Preflight: 01_preflight.md + - Cockpit Preparation: 02_cockpit-preparation.md + - Preparing the FMS: 03_preparing-fms.md + - Engine Start and Taxi: 04_engine-start-taxi.md + - Takeoff, Climb & Cruise: 05_takeoff-climb-cruise.md + - Descent Planning and Descent: 06_descent.md + - Landing: 07_landing.md + - After Landing: 08_after-landing.md + - Powering Down: 09_powering-down.md diff --git a/docs/pilots-corner/a380x/a380x-beginner-guide/01_preflight.md b/docs/pilots-corner/a380x/a380x-beginner-guide/01_preflight.md new file mode 100644 index 000000000..6a9374e4a --- /dev/null +++ b/docs/pilots-corner/a380x/a380x-beginner-guide/01_preflight.md @@ -0,0 +1,74 @@ +# Preflight + +Before you start your flight in earnest, we have included various features in the A380X that assist in configuring the +aircraft and in-flight support. Some of these features require the aircraft to be powered on. Additionally, these guides +will be linked to the appropriate locations throughout the beginner guide. + +--- + +## Nav Data + +The AIRAC cycle (nav data version) of MSFS's nav data is updated during MSFS's regular sim updates. It's important to +take stock of what AIRAC cycle you are currently using for your flight planning and if it matches the current AIRAC +cycle in MSFS. When using simBrief or other planning tools with older AIRAC cycles, you may +encounter errors during the flight plan import (`NOT IN DATABASE`, `AWY/WPT Mismatch`) OR the +[flight plan import](#flight-plan-import) may fail due to outdated/incorrect AIRAC cycle. + +Owning a Navigraph subscription gives you access to their standalone nav data add-on for MSFS that pairs with their +simBrief flight planning. It will provide you with an up-to-date AIRAC alongside any revisions, and ensure compatibility +when importing from simBrief or planning your flight manually. + +## Flight Planning + +We highly recommend **not** using the built-in MSFS flight planner (World Map). We recommend +using [SimBrief](https://www.simbrief.com/){target=new} as it is a great resource that provides routing and other +information to successfully plan your flight. + +You can choose to use other software/websites to plan your route, but when using simBrief we have a handy import feature +as seen in the next section. Additionally, other tools often don't have the most current nav data AIRAC cycle available. + +!!! tip "Important Links for Flight Planning" +- [SimBrief Website](https://www.simbrief.com/){target=new} (Flight Planning) +- [Little Nav Map](https://albar965.github.io/littlenavmap.html){target=new} (Flight Planning and Charts) +- [ChartFox](https://chartfox.org/){target=new} (Charts) +- [Navigraph](https://navigraph.com/){target=new} (Flight Planning and Charts) **Requires +Subscription** + +## Flight Plan Import + +If you wish to expedite the process of inputting your flight plan into the FMS, we have incorporated a simBrief import +function for the FMS similar to the real aircraft. + +Also, the EFB can import and use your SimBrief flight plan to display the OFP, import fuel and payload data automatically. + +[SimBrief A380X Features](../../../aircraft/a380x/feature-guides/simbrief.md){.md-button} + +### Manual Flight Planning + +The [Flight Plan Section](03_preparing-fms.md#flight-plan) in the "Preparing the FMS" guide contains a sample routing to +showcase how to input your waypoints, departure SID, and arrival STAR / procedure. + +### Flight Plan Discontinuities + +When inputting your flight plan, discontinuities appearing is an intended feature. The page below +describes how to handle these when encountered during your preflight preparations. + +[Flight Plan Discontinuities](03_preparing-fms.md#discontinuity){.md-button} + +## Payload Management + +To configure your aircraft, we have provided options onboard the aircraft to load fuel and passengers / baggage. See the +following page and note any advisories. + +[Fuel and Weights](../../../aircraft/a380x/feature-guides/loading-fuel-weight.md){.md-button} + +## EFB Navigraph Charts + +To help with navigation during your flight, our flyPad EFB can connect to your Navigraph account to provide access to +all the en route charts for your flight! + +[EFB Navigraph](../../../aircraft/common/flypados3/charts.md){.md-button} + +This concludes the *Preflight* guide. + +Continue with [Cockpit Preparation](02_cockpit-preparation.md). diff --git a/docs/pilots-corner/a380x/a380x-beginner-guide/02_cockpit-preparation.md b/docs/pilots-corner/a380x/a380x-beginner-guide/02_cockpit-preparation.md new file mode 100644 index 000000000..4bd749716 --- /dev/null +++ b/docs/pilots-corner/a380x/a380x-beginner-guide/02_cockpit-preparation.md @@ -0,0 +1,422 @@ + + +# Cockpit Preparation + +This guide will help you with preparing and powering up the Airbus A380. +It includes images to help you understand the locations of all buttons and switches. + +!!! warning "Disclaimer" +This is for simulation purposes only.
+ + The level of detail in this guide is meant to teach an Airbus A380 beginner to start the aircraft correctly. + + A *beginner* is defined as someone familiar with flying a GA aircraft or different types of airliners. Aviation + terminology and know-how is a requirement to fly any airliner, even in Microsoft Flight Simulator. + + This guide simplifies the process of starting the aircraft to accomodate beginners and the fact that this is a + simulation. More advanced sim pilots can use the [A380X SOP](../a380x-sop.md) directly. + + When this guide refers to ATC it is referring to any Online ATC network but **NOT** the built-in ATC in the + simulator as this is very unrealistic and unreliable. + +--- + +## Prerequisites + +This guide assumes that your aircraft is in a cold and dark state at a gate. + +[Download FlyByWire Checklist](../assets/sop/FBW_A380X_Checklist.pdf){ .md-button target=new } + +## Pre-checks + +??? tip "What and Why" + Before starting the aircraft, we need to ensure that all switches are in the correct position. + This is to prevent any damage to the aircraft systems and to ensure that the aircraft is ready for flight. + + (Of course, this is not an issue in the sim, but in real life it is crucial to check this!) + +`ENGINE MASTER SWITCHES (1, 2, 3, 4) .................................. OFF`This is for simulation purposes only.
+ + The level of detail in this guide is meant to teach an Airbus A380 beginner to start the aircraft correctly. + + A *beginner* is defined as someone familiar with flying a GA aircraft or different types of airliners. Aviation + terminology and know-how is a requirement to fly any airliner, even in Microsoft Flight Simulator. + + This guide simplifies the process of starting the aircraft to accommodate beginners and the fact that this is a + simulation. More advanced sim pilots can use the [A380X SOP](../a380x-sop.md) directly. + + When this guide refers to ATC it is referring to any Online ATC network but **NOT** the built-in ATC in the + simulator as this is very unrealistic and unreliable. + +The simBrief route used in this guide: + +[Download simBrief OFP](../assets/beginner-guide/03_preparing-fms/sample-ofp.pdf){ .md-button } + +!!! tip "AIRAC Updates" + Please note, we may update this OFP and guide occasionally to ensure it is current with the latest AIRAC + provided by the simulator or external nav-data. + +--- + +## Prerequisites + +Below are a few Prerequisites before starting programming the FMS. + +Visit [Cockpit Preparation](02_cockpit-preparation.md) to learn more. + +* Make sure the aircraft is powered up. + * External Power OR APU +* Make sure the ADIRS are set to NAV. +* Have a valid flight plan. +* Ensure IFR clearance has been obtained. + +--- + +## Chapters / Phases + +This guide will cover the following topics in helping you set up the FMS: + +* [Understanding the FMS](#understanding-the-fms) + * [Using Keyboard and Mouse](#using-keyboard-and-mouse) +* [FMS Initialization](#fms-initialization) + * [Data & Status](#data-status) + * [Init & Flight Plan Initialization](#init-flight-plan-initialization) + * [Navaids](#navaids) + * [Fuel & Payload](#fuel-payload) + * [Performance](#performance) +* [A380X simBrief Integration](#a380x-simbrief-integration) + +## Understanding the FMS + +During this guide we will be referring to a few key terms which are defined below. + +### Using Keyboard and Mouse + +The FMS can be managed entirely using your mouse and keyboard, allowing for a greater freedom and efficiency when +selecting items and entering information. + +Below is a screenshot of the FMS as you would find it after the initial start up of the aircraft. Two items are +highlighted in the image below: + +* Buttons show up as grey boxes. + * If a button has a downwards pointing triangle, it indicates a dropdown menu. + * If a button has greyed out text, it is disabled. + * Tabs also show as buttons. +* The mouse pointer is identified as a yellow `X` with a dot in the middle. + +Highlighted and selected buttons and fields will have a blue border around them. + +{loading=lazy} + +By using the mouse and using the different dropdown menus and buttons, it is easy to navigate through the entire FMS and +quickly find the page or information you are looking for. + +When you select an input field, you will be able to use your regular keyboard to type in the expected data. By pressing +`ENTER`, you will confirm the entry in the field. + +## FMS Initialization + +### Data & Status + +When the FMS first starts, it will show a screen showing the current status of the aircraft. This information includes: + +* Aircraft type +* Engine type +* Navigation Database serial number and dates +* Pilot stored Waypoints, Routes, Navaids and Runways + + + +### Init & Flight Plan Initialization + +??? tip "What and Why?" + The FMS contains information about the flight that needs to be set up by the pilots. This includes: + + * Flight Number + * From, To and possible Alternate airports + * Cruise level + * Cost Index + * Flight Plan Route + + These form the basis of the FMS Initialization and help the FMS manage the flight. It helps program the different + systems in the aircraft to optimally fly the flightplan. + +`FLIGHT PLAN INITIALIZATION........................................COMPLETE`This is for simulation purposes only.
+ + The level of detail in this guide is meant to get an Airbus A380 beginner safely from the terminal to the runway + hold short point. + + A *beginner* is defined as someone familiar with flying a GA aircraft or different types of airliners. Aviation + terminology and know-how is a requirement to fly any airliner, even in Microsoft Flight Simulator. + +--- + +## Prerequisites + +- IFR clearance obtained +- The aircraft is secure +- APU MASTER SW - `Set to ON` and the APU is available + +At this time, we may request for clearance to push and start from ATC. + +[Download FlyByWire Checklist](../assets/sop/FBW_A380X_Checklist.pdf){ .md-button } + +--- + +## Chapters / Phases + +This guide will cover these chapters: + +1. [Before Pushback and Start](#before-pushback-and-start) +2. [Pushback Clearance and Preparation](#pushback-clearance-and-preparation) +2. [Pushback](#pushback) +2. [Engine Start](#engine-start) +3. [After Engine Start](#after-engine-start) +4. [Flight Controls Check](#flight-controls-check) +5. [Taxi](#taxi) +6. [General Resources](#general-resources) + +--- + +### Before Pushback and Start + +Once all passengers have boarded and secured, we are ready to begin pushback. + +??? tip "What and Why" + Before pushback the flight crew need to ensure the external power is not used any more so the ground crew can + safely disconnect the aircraft from the ground power. The same goes for the low-pressure ground carts as keeping + them connected during engine start could cause faulty triggers. + +`EXTERNAL POWER (1, 2, 3, 4).....................DISCONNECT and CHECK AVAIL`This is for simulation purposes only.
+ + The level of detail in this guide is meant to get an Airbus A380 beginner safely up in the air and to cruise level + under normal conditions, while simplifying details which are not (yet) important for a beginner. + + A *beginner* is defined as someone familiar with flying a GA aircraft or different types of airliners. Aviation + terminology and know-how is a requirement to fly any airliner, even in Microsoft Flight Simulator. + +--- + +## MSFS Start from Gate or Runways + +Microsoft Flight Simulator allows you to start your flight from cold & dark at a gate or directly from the runway with +the aircraft ready for takeoff. + +For this guide, we assume you started cold & dark at the gate and taxied to the runway holding point as per the previous +chapters of this beginner guide. + +If you did start on the runway, you have to make sure to set up the FMS and APS correctly anyway as otherwise the aircraft +won't work as expected. You can't fly an airliner without a proper setup. + +You can then skip the first part (Lineup) and directly continue reading [Takeoff](#2-takeoff). + +## Prerequisites + +Aircraft is in `TAXI` state as per previous chapters. + +[Download FlyByWire Checklist](../assets/sop/FBW_A380X_Checklist.pdf){ .md-button } + +## Chapters / Phases + +This guide will cover these phases: + +[Base Knowledge About the Airbus A380 for Flight](#base-knowledge-about-the-airbus-a380-for-flight) + +1. [Lineup](#1-lineup) +2. [Takeoff](#2-takeoff) +3. [Initial climb](#3-initial-climb) +4. [Climb](#4-climb) +5. [Cruise](#5-cruise) + +--- + +## Base Knowledge About the Airbus A380 for Flight + +This section is focused on differences to other non-Airbus airliners a user might be used to. + +??? tip "What is a Fly-by-Wire System?" + Traditional mechanical and hydro-mechanical flight control systems use a series of levers, rods, cables, pulleys and + more, which pilots move to adjust control surfaces to aerodynamic conditions. Their "hands on" design gives pilots a + direct, tactile feel for how the aircraft is handling aerodynamic forces as they fly. On the other hand, mechanical + systems are also complicated to operate, need constant monitoring, are heavy and bulky, and require frequent + maintenance. + + In fly-by-wire systems, when the pilot moves flight controls, those movements are converted into electronic signals, + which are then interpreted by the aircraft's Electrical Flight Control System (EFCS) to adjust actuators that move + flight control surfaces. Computers also monitor sensors throughout the aircraft to make automatic adjustments that + enhance the flight. + + Because fly-by-wire is electronic, it is much lighter and less bulky than mechanical controls, allowing increases in + fuel efficiency and aircraft design flexibility, even in legacy aircraft. And to prevent flight critical failure, most + fly-by-wire systems also have triple or quadruple redundancy back-ups built into + them. [source: BAE Systems](https://www.baesystems.com/en-us/definition/what-are-fly-by-wire-systems){target=new} + + See also: [Fly-by-wire Wikipedia](https://en.wikipedia.org/wiki/Fly-by-wire){target=new} + +??? tip "What is Autotrim?" + The A380 has a feature called "Autotrim", which makes it unnecessary to hold the sidestick or use the trim wheel for + holding the current pitch. This system is always active, even when the __Autopilot__ is off (in Normal Law, which means + under normal circumstances with a fully functional aircraft). + +??? tip "What is Autothrust?" + The A380 has __Autothrust__ which is similar to Autothrottle (e.g., in a Boeing), but it does not move the thrust + levers. Basically, the thrust levers are only moved by the pilot and never move on their own. The thrust levers act as a + maximum allowed power setting for the Autothrust system. During normal flight (after takeoff) the levers stay in the CL + climb detent, and the Autothrust system will set engine power accordingly. + +??? tip "What is Autopilot?" + The A380's __Autopilot__ system works a bit differently from other manufacturer's systems. The A380 FCU controls allow + setting certain values and then push or pull the knobs. Pushing usually means automatic control (Managed Mode) and + pulling will use the manually selected value (Selected Mode). + + {loading=lazy} + + The FCU (Flight Control Unit) shows three important values: + + - SPD "---":This is for simulation purposes only.
+ + The level of detail in this guide is meant to get an Airbus A380 beginner safely from cruise + level down to the ILS glideslope. + + A *beginner* is defined as someone familiar with flying a GA aircraft or different types of + airliners. Aviation terminology and know-how is a requirement to fly any airliner even, in + Microsoft Flight Simulator. + +--- + +## Prerequisites + +Aircraft is in `CRUISE` state and phase as per previous chapters + +[Download FlyByWire Checklist](../assets/sop/FBW_A380X_Checklist.pdf){ .md-button } + +## Chapters / Phases + +This guide will cover these phases: + +1. [Descent and Approach Planning](#1-descent-and-approach-planning) +2. [Starting the Descent](#2-starting-the-descent) +3. [Flying the STAR and Approach](#3-flying-the-star-and-approach) +4. [Intercepting ILS](#4-intercepting-ils) + +--- + +## Base Knowledge: Route, Star, Approach and ILS + +### Basics Information + +As we have learned in previous chapters, a flight route begins with an origin airport and a SID to safely guide the +aircraft away from the airport to the first waypoint on their actual route. Similar to a **SID**, the arrival to an +airport is done via a **STAR** (Standard Terminal Arrival Route) and an **IAP** (Instrument Approach, often APPR) to safely +bring the aircraft into a position to land on the destination airport safely and with as little ATC communication as +possible. + +??? tip "Standard Terminal Arrival Route (STAR)" + #### STAR + + A Standard Terminal Arrival Route (STAR) ensures safe and efficient traffic from the last en-route waypoint to the + initial approach fix (IAF) of the Instrument Approach (IAP). It separates aircraft, avoids conflicts and helps with + noise abatement through specific routing, levels/altitudes, speed restrictions and checkpoints often with holding + areas. + + One main objective is, to do this with a minimum of communication between the ATC controller and the pilot. As the + STAR is part of the flight plan, a pilot can simply continue from the normal route into the STAR if ATC has not + given any other instructions. Sometimes ATC might give an explicit clearance for the STAR or change the STAR to + manage traffic and landing situation (different runways, etc.). + + Often a STAR contains a clearance point which mustn't be passed without explicit clearance by ATC. If clearance is + not given, then a holding must be flown as described in the charts. + + Please also have a look at our airliner guide's SIDs and STAR section + [SIDs and STARS](../../airliner/airliner-flying-guide/navigation.md#sids-and-stars) + + Find a good overview over charts in our airliner guide: + [Reading a Chart](../../airliner/airliner-flying-guide/navigation.md#reading-a-chart) + +??? tip "Instrument Approach (IAP)" + #### Instrument Approach + + The Instrument Approach (IAP or APPR) has similar goals as a SID or STAR - safely bring an aircraft into a + position to land while ensuring separation between multiple aircraft, avoiding terrain, support with noise + abatement, etc. + + IAP are often designed for handling maximum traffic in even bad weather conditions. With only little traffic and + good weather, it is quite common that ATC instructs the pilot to leave the approach route by giving the pilot + heading vectors for a more direct route to the Final Approach Fix (FAF, also called final approach point). + + When flying with Online ATC (VATSIM, IVAO, PilotEdge, ...) expect being vectored to the FAF quite often. + + Understand important ILS approach chart features here: + [Approach Chart](../../airliner/airliner-flying-guide/navigation.md#chart-sample-1) + +??? tip "Instrument Landing System (ILS)" + #### Instrument Landing System (ILS) + + The Instrument Landing System (ILS) is one of several modern forms of helping an aircraft during its final approach + to land even in non-optimal weather situations. ILS uses a localizer for lateral guidance and a glideslope for + vertical guidance from the Final Approach Fix down to a minimum at which the pilot needs to perform the final + landing sequence visually. + + Modern airliner like the A380 are even able to use the ILS to land fully automatically as long as the runway's ILS + supports it. + + Understand important ILS approach chart features here: + [Approach Chart](../../airliner/airliner-flying-guide/navigation.md#chart-sample-1) + +!!! info "Microsoft Flight Simulator and navigation charts" + Although Microsoft Flight Simulator allows some flight planning through the user interface, it is highly recommended + to use navigational charts when flying airliners. MSFS' flight planning does not provide sufficient information to + correctly fly a STAR or an approach. + + There are several good sources for charts - free or subscription based. A good free solution is + [ChartFox](https://chartfox.org/), which only requires a free VATSIM account. One of the most known + subscription-based sources for charts is [Navigraph](https://navigraph.com/home). Navigraph has been integrated into + the FlyByWire A380X flyPad, whereas Chartfox is TBD. + + Also, often a simple internet search will do the trick: Search for "<airport icao code> charts": + E.g., "EDDM charts" + +--- + +## 1. Planning the Descent and Approach + +**Situation:** + +- Aircraft is in `CRUISE` state and phase as per previous chapters. +- Distance to destination is ~200NM (on a short flight, start as early as possible and maybe even before the flight).
+
+!!! warning "Pilot's responsibility"
+ #### Pilot's responsibility
+
+ It is the sole responsibility of the pilot to conduct proper flight planning, and especially proper descent
+ planning.
+
+ It is not at all ATC's task to do descent planning for pilots by giving descent instructions. On the other
+ hand, ATC often actually gives descent instructions, especially on common routes, as they want the aircraft in their
+ responsibility to be at certain altitudes when approaching the destination airport. Nevertheless, pilots must know
+ when approaching their top of descent and if necessary need to proactively request clearance to descend from ATC.
+
+ Good descent and approach planning is the foundation for a successful landing. It has to be done early during the
+ flight or even before the flight.
+
+??? tip "Important Data Points for Descent Planning:"
+ - **Cruise Flight Level:** The higher we fly, the earlier we need to start descending. Also for short flights, too
+ high a cruising altitude can make it impossible to actually descend to the destination airport in time. Therefore,
+ verify your flight plan if overall distance and flight level make sense.
+ - **Flight Plan Constraints:** STARs often have flight level (FL) or altitude constraints which we must adhere to.
+ We must plan our descent, so we can meet these altitude constraints, even when they themselves are still far away
+ from the destination airport.
+ - **Speed**: STARs also regularly have speed constraints which we need to take into consideration as slowing down
+ will cost time and is hard to do while descending. If we start our descent too late, we might not be able to slow
+ down in time as required by a constraint.
+ - **Aircraft capability and passenger comfort:** Although not a big concern in the A380, general aircraft
+ capabilities and passenger comfort also come into play.
+
+### Step-by-step Guide for Descent Planning
+1. Read the STAR chart and determine if there are altitude and/or speed constraints which we need to consider.
+2. Consider the STAR and APPR route as optional and do not count on them to be flown and available for descending. ATC
+ might want to vector us to a different runway or at least shortcut our approach. But they won't be able to if we are
+ still too high for the final approach.
+3. Determine the first constraint you need to meet. This could be a STAR waypoint with an altitude constraint, the Final
+ Approach Fix altitude or even the airport (or runway) elevation itself.
+4. Calculate the required distance needed to descend to that waypoint with a standard descent angle of 3°. We can use
+ the FlyByWire flyPad in the cockpit or a simple rule of thumb calculation (details below).
+5. Use the DIR TO function of the F-PLN page to determine the distance to the waypoint (see details below).
+
+??? tip "How to Calculate the Required Distance for Descent"
+ #### Calculate the Required Distance for Descent
+ **Example data:**
+
+ - Flight to EGKK via STAR TEBRA 2G.
+ - Flight level FL320.
+ - STAR constraint at waypoint ABTUM "at FL140".
+
+ **Example chart:**
+
+ {loading=lazy} TODO: update screenshot for A380X This is for simulation purposes only. TODO: link to advanced guide This is for simulation purposes only. This is for simulation purposes only. This is for simulation purposes only. This is for simulation purposes only. TODO: update the linked page to reflect both aircraft TODO: Update this table for A380X This is for simulation purposes only. TODO: FIX online preview links once merged. This is for simulation purposes only. This is for simulation purposes only. This is for simulation purposes only. [A32NX Corner](./a32nx) [A380X Corner](./a380x) [Airliner Corner](./airliner) Requires Navigraph Unlimited Subscription Cargo Door requires manual opening as of this version A32NX Release Notes A380X Release Notes [Installer Release Notes](installer/v330.md) [SimBridge](./simbridge) [Installer](./installer) Encountering issues flying the A32NX? This section lists our most commonly reported issues, workarounds, and status of any fixes available. Encountering issues flying a FlyByWire aircraft? This section lists our most commonly reported issues, workarounds, and status of any fixes available. Our beginner guide is a comprehensive gate-to-gate flight tutorial for the A32NX. Each guide was verified by an A320neo pilot. Click here to start learning!
+ Our beginner guides are comprehensive gate-to-gate flight tutorial for our aircraft.
+ Interactive A320neo systems overview for use with Microsoft Flight Simulator and the FlyByWire A32NX aircraft add-on.
+ Interactive systems overview for the FlyByWire A32NX and A380X aircraft.
+
+ *Copyright © 2021 Navigraph / Jeppesen
+ "Navigraph Charts are intended for flight simulation use only, not for navigational use."*
+
+ **Using the flyPad:**
+
+ Standard calculation with 3° descent path:
+ {loading=lazy}
+
+ Calculation with a specific distance to calculate the required descent velocity (V/S):
+ 
+
+??? tip "Rule of Thumb"
+ #### Rule of Thumb
+
+ ```
+ Distance = "Altitude difference"*3/1000+margin**
+
+ Altitude difference: 32000-14000=18000
+ Times 3: 18000*3=54000
+ Divided by 1000: 54000/1000=54
+ Plus margin (~10%): 59NM
+ ```
+
+ The margin can be lower for headwind and larger for tailwind. Some pilots also change the margin to compensate for
+ slowing down while descending.
+
+ As can be seen on the chart, there will be a further descent to TIMBA at FL70 and after that (not visible on the
+ chart above), there will be a descent to the final approach which will be at 2000ft at the Final Approach Fix FF26L.
+
+ The same methodology/calculation as our initial descent can be applied to these descents as well, but they require
+ less planning as they are usually designed in a way that an aircraft with a 3° descent angle can make these descents
+ with ease.
+
+ ATC will quite often instruct certain altitudes within the STAR and APPR which deviate from the STAR and APPR
+ charts. Please expect such instructions at any time.
+
+
+??? tip "Distance to Waypoint"
+ #### Distance to Waypoint
+
+ The F-PLN page of the MFD has the DIR TO function which can be used to determine the distance to a waypoint. This is
+ currently the only way to get this information without having to calculate it manually by adding up all distances
+ between waypoints as displayed on the F-PLN page.
+
+ Unfortunately, the A380X does not yet have [FIX INFO](../../../a32nx/a32nx-advanced-guides/flight-planning/fixinfo)
+ implemented, so we can't use it to determine when to start descent at a certain distance.
+
+ To use the DIR TO function, go to the F-PLN page and select the waypoint you want to know the distance to. Then press
+ on the waypoint and select the DIR TO option in the popup menu.
+
+ {loading=lazy}
+
+ **ND distance rings:**
+
+ The ND distance rings can also be used to determine the distance to a waypoint or fix. The distance rings can be set to a
+ specific distance and will show the distance to the waypoint or fix. The distance rings can be set by pressing the
+ ND button on the lower ECAM display and then selecting the distance rings option.
+
+ {loading=lazy}
+
+ *Copyright © 2021 Navigraph / Jeppesen*
+
+??? tip "ILS in the A380"
+ ##### ILS in the A380
+
+ Although the A380 is capable of a CAT IIIB ILS approach (with Autoland) and has an approach category of "C" we will
+ do a manual landing for the purpose of this guide.
+ (see [Wikipedia Aircraft approach category](https://en.wikipedia.org/wiki/Aircraft_approach_category){target=new})
+
+ So for the minimums we need to find the `DA` or `MDA` for CAT I ILS for the destination airport. In this chart for
+ EDDF 07C ILS there is a `DA` of 528ft defined - so we can enter "528" into the `BARO` field.
+
+ If we are using Microsoft Flight Simulator without any Online ATC services (VATSIM, IVAO, PilotEdge, ...), and using
+ the MSFS built-in ATC, you usually can't request ATIS information for the destination airport at this point. MSFS
+ ATC makes ATIS only available once close to the destination airport.
+
+ If we are flying with Online ATC, you can request ATIS via the network.
+
+??? tip "METAR Information"
+ ##### METAR Information
+
+ We can in any case request the METAR weather information the flyPad EFB.
+
+ {loading=lazy}
+
+`WEATHER AND LANDING INFORMATION ................................... OBTAIN`
+`LANDING ELEVATION .................................................. CHECK`
+`BAROMETRIC REFERENCE .............................................. PRESET`
+`LANDING PERFORMANCE ................................................ CHECK`
+??? note "Landing Performance"
+ Unfortunately, there is no landing performance calculator for the A380X yet. This will be added in the future.
+
+#### Flight Management System (FMS) Checks
+If not already inserted, insert the applicable APPR, STAR, TRANS and APPR VIA in the active flight plan arrival page
+of the flight management system.
+
+`FMS ACTIVE/F-PLN/ARRIVAL PAGE ............................... INSERT/CHECK`
+`DES PANEL OF THE FMS ACTIVE/PERF PAGE ....................... INSERT/CHECK`
+`APPR PANEL OF THE FMS ACTIVE/PERF PAGE ...................... INSERT/CHECK`
+`GA PANEL OF THE FMS ACTIVE/PERF PAGE ............................... CHECK`
+`FMS POSITIONAL/NAVAIDS PAGE ........................................ CHECK`
+`FMS ........................................................... CROSSCHECK`
+
+#### OANS (Onboard Airport Navigation System) and BTV (Brake to Vacate)
+If available, you can also set up the [OANS and BTV](../../a380x-advanced-guides/oans-btv) for the destination airport.
+
+??? tip "OANS"
+ The Onboard Airport Navigation System (OANS), developed jointly by Thales and Airbus, is a groundbreaking technology
+ designed to enhance pilot navigation during airport operations.
+
+ Key features of OANS include:
+
+ **Overview Map Display:** OANS provides pilots with an overview map display of the airport apron and taxiways. This
+ display indicates the precise location of the aircraft on the map, aiding pilots during taxiing and ground movements.
+
+ **Geo-Referenced Map Integration:** The system integrates the plane’s position on a high-resolution, geo-referenced map
+ using a standardized Airport Mapping Database. This ensures accurate and clear navigation guidance for pilots,
+ especially when they find themselves in unfamiliar airports after landing.
+
+ **Efficiency Benefits:** By helping pilots navigate airports more efficiently, OANS aims to:
+ - Reduce taxi time.
+ - Streamline airport handling operations.
+ - Maximize turnaround times
+
+ **Adaptation to Multiple Platforms:** Initially certified for the A380, OANS has been adapted to other Airbus platforms,
+ including the A320, A330, A340, and A350 XWB. Thales’s expertise allows effective adaptation of systems designed for
+ newer platforms into earlier ones3.
+
+ In summary, OANS bridges the technological gap between the air and the ground, providing pilots with clear and
+ concise directions from landing through arrival at the gate, and vice versa3.
+
+??? tip "BTV"
+ Brake to Vacate (BTV) is a system that helps pilots to select the most appropriate runway exit for their aircraft
+ based on the aircraft’s current position, speed, and weight. The system calculates the optimal exit based on the
+ aircraft’s deceleration capabilities and the distance to the exit.
+
+ By selecting the most appropriate exit, pilots can reduce taxi times and improve airport efficiency. This is
+ especially important for busy airports with high traffic volumes, where every minute saved can help to reduce
+ congestion and improve overall airport operations.
+
+ BTV is a valuable tool for pilots, providing them with the information they need to make informed decisions about
+ runway exits. By selecting the most appropriate exit, pilots can help to reduce taxi times, improve airport
+ efficiency, and enhance the overall passenger experience.
+
+
+`RUNWAY SHIFT ................................................. AS REQUIRED`
+`ND MODE ............................................................. PLAN`
+`ND RANGE ............................................................ ZOOM`
+`RUNWAY ............................................................ SELECT`
+`RUNWAY EXIT ....................................................... SELECT`
+??? note "Exit Selection"
+ It is recommended to select the exit in accordance with the runway conditions. It is recommended to select an exit
+ after the wet line to anticipate any changes of runway condition, as well as a smoother deceleration for passenger
+ comfort. It is also recommended to take into account arrival gate, the ground circulation, the runway exit
+ configuration, and the predicted turn around time, which is displayed on the navigation display
+`AUTO BRAKE/BTV ....................................... SELECT, AS REQUIRED`
+??? note "Brake / BTV"
+ It is recommended to use of the autobrake system to have equal brake pressure and prevent brake overheat. Select the
+ appropriate autobrake mode, depending on the weight, the runway length, the conditions and the winds. However, if
+ the pilot selects the BTV system, set the BTV mode before removing the onboard airport navigation display from the
+ navigation display. It is recommended on contaminated runway to use the autobrake mode 3. It is recommended to use
+ of the HI mode if the BTV mode is not available or on short runway conditions
+`OANS RUNWAY LENGTH VS CHARTS RUNWAY LENGTH .................... CROSSCHECK`
+
+See our [OANS Guide](../../a380x-advanced-guides/oans-btv) for more information on the system.
+
+`LANDING BRIEFING ................................................. PERFORM`
+
+This concludes *Descent and Approach Planning*.
+
+---
+
+## 2. Descent
+
+**Situation:**
+
+- Aircraft is in `CRUISE` phase as per previous chapters.
+- Descent and approach planning is done.
+- The first descent point (altitude at certain waypoint) is identified.
+- Distance-to-descent point is calculated, which is called TOD (top of descent).
+
+??? tip "Descent Clearance from ATC & TOD"
+ A few minutes before we reach our calculated descent point (TOD) we request clearance for descent from ATC if not
+ already given a descent instruction before.
+
+ **Do NOT start the descent without clearance from ATC.**
+
+ The A380 has a downward pointing arrow at the TOD to support the pilot with the decision of when to descend.
+
+ **Ultimately, it is still the pilot's responsibility to calculate and validate the TOD.**
+
+ When clearance is given, we can start our descent to the flight level or altitude ATC has given us.
+
+`DESCENT CLEARANCE ................................................. OBTAIN`
+`CLEARED ALTITUDE ON AUTO FLIGHT SYSTEM CONTROL PANEL ................. SET`
+`ANIT-ICE ..................................................... AS REQUIRED`
+
+### Starting the Descent
+
+`DESCENT ......................................................... INITIATE`
+`ALTITUDE ..................................................... QNH/HPA SET`
+`CABIN CREW ........................................................ ADVISE`
+
+??? tip "How to initiate the descent"
+ For descending, we set the new flight level or altitude in the `FCU` with the `altitude selector`. We can then
+ either PUSH the selector for `Managed Altitude Mode` (constraints are respected, also known as
+ [DES](../../a32nx/a32nx-advanced-guides/flight-guidance/vertical-guidance/managed-modes.md#des-descent)) or PULL the
+ selector for `Selected Altitude Mode` (constraints are ignored, also known as
+ [OP DES](../../a32nx/a32nx-advanced-guides/flight-guidance/vertical-guidance/selected-modes.md#op-des-open-descent)).
+
+
+ {loading=lazy}
+
+??? info "What is DES mode"
+ Managed Descent (DES) Mode will follow a calculated vertical profile, this may lead to unexpected occurrences of
+ very high and very low V/S. Users not familiar with Airbus Managed Descent should use OP DES instead as it provides
+ a linear descent most users would expect.
+
+ See the [Vertical Guidance Guide](../../a32nx/a32nx-advanced-guides/flight-guidance/vertical-guidance/overview.md)
+ for more information on using managed vertical modes.
+
+ When either of these altitude modes are engaged, the relevant mode will appear in the Second Column of the `FMA`,
+ and will be displayed in green.
+ (See [A32NX Vertical Mode Annunciations](../../a32nx/a32nx-briefing/pfd/second-column.md) as the A380 FMA is very similar).
+
+??? warning "Using V/S not recommended for beginners"
+ It is not recommended to use V/S for climbing or descending in the A380 (at least not for beginners) as the V/S
+ guidance has priority over the speed guidance, and speed needs to be watched very closely when using V/S.
+
+ If the selected target V/S is too high (relative to the current thrust condition and speed), the FMGC will steer the
+ aircraft to the target V/S, but the aircraft will also accelerate or decelerate. When the speed reaches its
+ authorized limit, V/S automatically decreases to maintain the minimum or maximum speed limit.
+
+ See also [A32NX Protections](../../a32nx/a32nx-advanced-guides/protections/overview.md) as the A380 systems are very
+ similar.
+
+??? tip "VNAV and ATC in the FlyByWire A380X"
+ In case we are cleared to a lower altitude or flight level with altitude constraints above the clearance
+ is an ideal scenario for the called so `VNAV` autopilot mode, which would be activated by using
+ "`Managed Altitude Mode`" (pushing the `ALT selector`).
+
+ The autopilot will automatically level off at the constraint and continue descending when the constraint is no
+ longer valid. ATC typically will not clear us to our final target altitude directly, but will give us several step
+ descents down to our required altitude.
+
+ ATC will often still expect us to respect the STAR's constraints, although they might have given us a lower
+ clearance. We should then only descent to the constraint's altitude. We repeat the process until we have reached our
+ desired final approach altitude.
+
+`DESCENT .......................................................... MONITOR`
+`RATE OF DESCENT ....................................... ADJUST AS REQUIRED`
+`SPEEDBRAKES .................................................. AS REQUIRED`
+
+!!! info "Airline SOPs"
+ Some airline's SOPs (standard operating procedures) might have a different order for the following steps.
+
+### At 20,000 feet
+
+`CABIN CREW ........................................................ ADVICE`
+`TERRAIN RADAR ................................................ AS REQUIRED`
+`WEATHER RADAR ................................................ AS REQUIRED`
+??? note "Weather Radar"
+ The Weather Radar is currently not available in the A380X. It is planned to be implemented in the future if and when
+ the simulator provides the required weather data.
+
+### At 10,000 feet
+
+??? tip "What and Why?"
+ As we reach the 10,000 foot mark in our descent, we have to take a few more steps to prepare the aircraft to land.
+ We make sure the seatbelt sign is on so passengers are secure and not moving around during descent. We also make sure
+ the landing lights are on so we are visible to other aircraft on approach.
+
+ The `LS` buttons are turned on so we have the landing system active for when we intercept the ILS.
+
+`LANDING LIGHTS ........................................................ ON`
+`LANDING DATA ......................................................... SET`
+`SEAT BELTS SIGN ....................................................... ON`
+`CSTR BUTTON ........................................................... ON`
+`LS BUTTON .................................................... AS REQUIRED`
+`NAVAIDS ................................................ AS REQUIRED/CHECK`
+
+??? tip "How and Where?"
+ [Flight Deck Overview](../../a380x-briefing/flight-deck){ .md-button }
+
+ Use the Flight Deck Overview to locate the items mentioned above. The Flight Deck Overview is a
+ clickable cockpit that will show you where each item is located.
+
+ * [External Lights](../../a380x-briefing/flight-deck/ovhd/ext-lt)
+ * [MFD](../../a380x-briefing/flight-deck/main-panel/mfd)
+ * [SIGNS Panel](../../a380x-briefing/flight-deck/ovhd/signs)
+ * [EFIS Panel](../../a380x-briefing/flight-deck/glareshield/efis)
+
+`APPROACH CHECKLIST .............................................. COMPLETE`
+??? note "Approach Checklist"
+ The Airbus A380 has a built-in checklist system that can be accessed via the
+ [Engine Warning Display (EWD)](../../a380x-briefing/flight-deck/main-panel/ewd).
+
+ To activate it you need to press the `C/L` button on the
+ [ECAM Control Panel (ECP)](../../a380x-briefing/flight-deck/pedestal/ecam).
+
+ You can navigate through the checklist by using the `UP` and `DOWN` buttons on the ECP. You can check/uncheck items
+ by pressing the buttons with the check mark on the ECP.
+
+ Some items are autosensed by the aircraft and will be checked automatically (e.g. Beacon).
+
+ {loading=lazy}
+
+??? tip "Cabin Crew in real life"
+ In real life, the cabin crew will be asked to prepare the cabin for landing at some point during the descent. The
+ exact moment and process might differ between airlines, but most seem to do this when the Seatbelt Signs are turned
+ on (typically at the latest at 10,000ft).
+
+ The Cabin Crew will notify the pilots either by a "Cabin Ready" button (A380) or by a call to the cockpit once
+ they are ready and strapped in themselves. Typically, we will be in final approach by that time.
+
+This concludes *Starting the Descent*.
+
+---
+
+## 3. Flying the STAR and Approach
+
+**Situation:**
+
+- Aircraft is in `DES` phase.
+- Descent has started (we are after TOD).
+- We have not yet reached the first waypoint of the STAR.
+- `FMS PERF APPR` page is filled - see [Arrival Planning](#arrival-planning)).
+
+Flying the STAR and Approach is very similar to any other part of the route within the flight plan. Apart from
+descending and adhering to constraints, the lateral flight path just follows the programmed route.
+
+Let the __Autopilot__ do this for you, and just adjust altitude and speed according to the charts or ATC instructions.
+
+??? tip "ATC Instructions During STAR and Approach"
+ At some point during the descent and when close enough to the airport, we will be instructed by ATC to contact ATC
+ Approach for the airport we are flying into.
+
+ Be prepared for ATC instructions to deviate from the STAR or Approach route to separate from other aircraft
+ or to shortcut the approach when there is little traffic. ATC will then typically give you new heading instructions
+ (heading vectors) and will guide you the rest of the STAR and Approach with additional heading instructions until
+ intercepting the ILS localizer.
+
+ **Example for shortcuts:**
+
+ DEBHI1D STAR EDDF (Frankfurt) 07C - it is only in times with a lot of traffic that we would have to fly the whole
+ downwind part of this transition.
+
+  1C](../assets/beginner-guide/06_descent/eddf-star-debhi1c-manual.png){loading=lazy}
+ *Copyright © 2024 Navigraph / Jeppesen
+ "Navigraph Charts are intended for flight simulation use only, not for navigational use."*
+
+ Note: If you do fly without Online ATC use DIR TO to the IAF waypoint DF554 after DF644 to start the final approach and
+ intercept the ILS localizer.
+
+---
+
+## 4. Intercepting ILS
+
+**Situation:**
+
+- Aircraft is in `DES` phase.
+- Aircraft is set up for flight <10,000ft (`seat belt signs` on, `landing lights` on, etc.).
+- We are either within the IAP (Instrument Approach) and at the correct altitude and speed or at a heading vector,
+ altitude, and speed instructed by ATC.
+
+??? tip "Reaching the beginning of the ILS Approach"
+ At the start of the Instrument Approach (or by ATC vectoring) we will be on a path to the Final Approach Fix and/or
+ intercepting the ILS localizer and eventually the ILS glideslope.
+
+ To intercept the ILS, we need to be at the correct altitude and should not have an approach angle larger than 30°.
+ The `LS` button should also be `ON`on both the captain and first officer's sides of the FCU.
+
+ 
+ 
+ *Copyright © 2024 Navigraph / Jeppesen
+ "Navigraph Charts are intended for flight simulation use only, not for navigational use."*
+
+`APPROACH PHASE ............................................ CHECK/ACTIVATE`
+??? note "Approach Phase"
+ The FMS approach phase activates:
+
+ - Manually, when the flight crew clicks on the ACTIVATE APPR on the FMS PERF page, or
+ - Automatically, when NAV is engaged, and the aircraft flies the DECEL pseudo waypoint.
+
+`MANAGED SPEED ...................................................... CHECK`
+??? note "Managed Speed"
+ It is recommended to regularly verify the managed speed and to monitor the target speed.
+
+ When in NAV, LOC*, or LOC mode is engaged, the aircraft will automatically decelerate at the DECEL waypoint.
+
+`SPEEDBRAKES .................................................. AS REQUIRED`
+
+More details regarding the ILS approach and landing in the next chapter.
+
+This concludes *Intercepting ILS*.
+
+Continue with [Final Approach and Landing](../07_landing)
diff --git a/docs/pilots-corner/a380x/a380x-beginner-guide/07_landing.md b/docs/pilots-corner/a380x/a380x-beginner-guide/07_landing.md
new file mode 100644
index 000000000..846cb32b8
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-beginner-guide/07_landing.md
@@ -0,0 +1,468 @@
+
+
+# Approach and ILS Landing
+
+This guide will explain the correct procedures to fly a final approach and conduct an ILS landing.
+
+
+!!! warning "Disclaimer"
+
+??? note "ILS Frequency"
+ Verify that the correct ILS frequency is tuned in the `MFD-RNAV` page. We find the correct frequency on the
+ pproach chart.
+
+ "Check ILS frequency"
+
+ {loading=lazy}
+
+ {loading=lazy}
+
+`LS (Landing System) ............................................. CHECK ON`
+??? note "LS Button on Glare Shield"
+ Turn on the `ILS localizer and glideslope scales` with the `LS` button on the glareshield if not already done
+ before. There is an `LS` button on both the captain and F.Os side of the FCU.
+
+ {loading=lazy width=40%}
+
+`ALTITUDE .......................................................... VERIFY`
+??? note "Verify Altitude"
+ Make sure we are on the correct altitude (4000 ft in this example) and we should not have an approach angle larger
+ than 30°.
+
+ 
+ 
+ *Copyright © 2024 Navigraph / Jeppesen
+ "Navigraph Charts are intended for flight simulation use only, not for navigational use."*
+
+### After ATC Clearance
+Once ATC has cleared us for the approach, we will fo the following:
+
+`ATC CLEARANCE FOR APPROACH ...................................... OBTAINED`
+??? note "APPR Phase and Speed"
+ When passing the pseudo waypoint `D` (DECEL) the aircraft will automatically switch to the `APPR` phase.
+
+ Check if the `APPR` phase is activated by going to the `PERF` page on the `MFD` and verify that the `APPR` mode is
+ active (green tab). If it is not active, you can activate it by pressing the `ACTIVATE APPR *` button at the bottom
+ of the `PERF` page.
+
+ When in the APPR phase, the `Autopilot` together with "Managed Speed Mode" relieves the pilot of a lot of stress
+ by managing the speed according to flaps setting automatically (S-Speed after `FLAPS 1`, F-Speed after `FLAPS 2`,
+ V~app~ after landing flap selection).
+
+`SPEED MODE ....................................................... MANAGED`
+??? note "Managed Speed Mode"
+ Set `SPEED` to `Managed Speed Mode` (push the `Speed Selector`). The aircraft should now decelerate to `green dot`
+ speed.
+`APPR MODE .......................................................... PRESS`
+??? note "Activate APPR mode"
+ Turn on `APPR` in the `FCU` to command the aircraft to intercept the ILS localizer. The aircraft will keep the
+ current heading until the localizer is captured and guides the aircraft towards the runway. The `lateral ILS
+ localizer scale` shows the `deviation marker` moving towards the middle of the `lateral deviation scale`. Also, the
+ lateral `FMA` shows `LOC` in blue (armed).
+
+ {loading=lazy}
+
+ {loading=lazy}
+
+!!! warning "Arming APPR"
+ Using `APPR` also arms the glideslope descent (G/S) and the aircraft will descend as soon as it captures the ILS
+ glideslope signal.
+
+ Do not descend without ATC clearance and only when directly on the ILS localizer path as only as obstacle clearance
+ is guaranteed.
+
+ To help with this you can use the `LOC` button first (only localizer capture) and when cleared for approach press
+ `APPR`
+`AUTOPILOT 1+2.......................................................... ON`
+??? note "Autopilot 1+2"
+ Turn on `AUTOPILOT 1+2` to have same additional redundancy in case of a failure.
+`FLIGHT MODE ANNUNCIATOR (FMA) ...................................... CHECK`
+??? tip "FMA"
+ The pilot can verify on the flight mode annunciator the approach capability (CAT2, CAT3 SINGLE, CAT3 DUAL, or
+ AUTOLAND) for the selected approach.
+
+ Also the `lateral FMA` should show `LOC` in blue (armed) or green (active) and the `vertical FMA` should show `G/S`
+ in blue (armed) or green (active).
+`FLAPS 1 (at V~FE~ -15)................................................ SET`
+??? note "Flaps 1"
+ Set `FLAPS` to 1 at about V~FE~ -15 knots (but never before speed is below V~FE~) for the first slat/flap
+ configuration (`CONF1`). The aircraft will then decelerate further to prepare for the next flaps configuration. Our
+ target is to be in CONF 1 and at S-speed by the time you need to set flaps 2 (CONFIG 2) before the glideslope
+ intercept (S-speed will be slow enough to set flaps 2).
+
+ {loading=lazy}
+`TCAS MODE .......................................................... TA/RA`
+`LOC CAPTURE ...................................................... MONITOR`
+??? note "Capturing the Localizer"
+ It is recommended to pay close attention to the LOC beam capture. Verify that during the capture phase, the LOC
+ deviation is within the LOC scale. The deviation should be displayed on the primary flight display and on the
+ navigation display.
+
+ The aircraft will turn towards the localizer and the deviation marker will move towards the center of the lateral
+ deviation scale. The lateral `FMA` will show `LOC` in green when the localizer is captured.
+
+ {loading=lazy}
+`ATC CONTACT ........................................................ TOWER`
+??? note "Contact Tower"
+ When we are established on the ILS localizer (the lateral `FMA` shows `LOC` in green) we will contact Tower ATC and
+ report that we are established on the ILS localizer (including call sign and runway).
+
+ Tower ATC will then give us clearance for the ILS approach to the target runway. This clears us to descend on the
+ ILS glideslope.
+
+ **Do not descent without explicit clearance from ATC.**
+
+This concludes *Intercepting the ILS Localizer*
+
+---
+
+## 2. Intercepting the ILS Glideslope
+
+**Situation:**
+
+Verify these items:
+
+`APPR MODE ......................................................... ACTIVE`
+`AUTOPILOT 1+2 ......................................................... ON`
+`LOC CAPTURE ...................................................... MONITOR`
+`ILS LOCALIZER ................................................ ESTABLISHED`
+`FLAPS 1 .............................................................. SET`
+`ECAM STS .......................................................... NORMAL`
+`ALTIMETER .................................................... QNH/HPA SET`
+`MINIMA ............................................................... SET`
+`SIGNS ................................................................. ON`
+
+After ATC has given us clearance for the ILS approach, we can also start descending using the ILS glideslope.
+
+### ILS Glideslope
+Check that the `APPR` button is activated on the `FCU` to arm the ILS glideslope descent mode.
+
+The vertical `FMA` now shows `G/S` (glideslope) in blue.
+
+`G/S CAPTURE ...................................................... MONITOR`
+??? note "Capturing the Glideslope"
+ The aircraft will start descending when the deviation marker is in the middle (we have captured the ILS glideslope).
+ The vertical `FMA` will now display `G/S` in green.
+
+ {loading=lazy}
+
+ We are now descending along the glideslope. The radio altimeter comes alive at 2,500ft above the ground to display
+ the actual precise height above ground.
+
+??? tip "ATC instructed approach speed"
+ The A380 `Autothrust` will manage speed during approach automatically and will reduce speed further with each flap
+ setting. In real life and also when flying with Online ATC like VATSIM, we need to expect that ATC instructs us to
+ stay at a certain speed (e.g., 160knots until 5NM to the runway).
+
+ In this case, we would use `Selected Speed Mode` (select a speed in the `FCU` and pull the knob) until the
+ instructed distance to the runway where we would then go back to `Managed Speed Mode` and drop the gear then as well
+ as setting flaps to 3 and flaps to full - see below.
+
+`GO AROUND ALTITUDE ................................................... SET`
+??? note "Go Around Altitude"
+ Set the `Go Around Altitude` in the `FCU` to the altitude where we would go around if we don't see the runway or
+ are not stable for landing. This is usually the `Missed Approach Altitude` from the approach chart.
+
+`FLAPS 2 (~2.500ft and below V~FE~).................................... SET`
+??? Note "Flaps 2"
+ Verify that the aircraft is decelerating toward the F speed. If the aircraft interception of the ILS/GLS glideslope
+ is below 2 000 feet above ground level, It is recommended setting flaps 2 at one dot below the glideslope. If
+ the aircraft is above the glideslope, or the aircraft does not decelerate, it is recommended to extend the landing
+ gear. It is not recommended to use the speed brakes due to limited effect at low speed.
+
+This concludes *Intercepting the ILS Glideslope*
+
+---
+
+## 3. Preparation and Checklist for Landing
+
+**Situation:**
+
+Verify these items:
+
+`ILS LOCALIZER & GLIDESLOPE.................................... ESTABLISHED`
+`FLAPS 2 .............................................................. SET`
+
+### 2000 feet and below
+
+`LANDING GEAR ........................................................ DOWN`
+`AUTOBRAKE ........................................................ CONFIRM`
+`GROUND SPOILERS ...................................................... ARM`
+`EXTERIOR LIGHTS ...................................................... SET`
+
+`FLAPS 3 (after L/G down and below V~FE~).............................. SET`
+`WHEEL SYSTEM DISPLAY PAGE .......................................... CHECK`
+??? note "SD WHEEL Page"
+ Verify the wheel system display page appears below 800 feet above ground level or at the extension of the landing
+ gear. It is recommended to verify the five landing gear green indication, as well as at least one green triangle on
+ each landing gear. This indicates the landing gear strut is locked at the down position.
+
+`FLAPS (below V~FE~).................................................. FULL`
+`AUTOTHRUST .................................... CHECK IN SPEED MODE OR OFF`
+
+??? tip "Ready at <=1000 feet"
+ **We need to be fully set up and stable at 1,000ft above the ground.**
+
+ What does that mean? Flaps fully extended, Autothrottle in speed mode or off completely, and the landing checklist
+ is complete.
+
+ PFD at ~1000ft above the ground:
+ {loading=lazy}
+
+ EWD at ~1000ft above the ground:
+ {loading=lazy}
+
+`LANDING MEMO ................................................ NO BLUE LINE`
+`CABIN .............................................................. READY`
+
+`LANDING CHECKLIST ............................................... COMPLETE`
+??? note "Landing Checklist"
+ The Airbus A380 has a built-in checklist system that can be accessed via the
+ [Engine Warning Display (EWD)](../../a380x-briefing/flight-deck/main-panel/ewd).
+
+ To activate it you need to press the `C/L` button on the
+ [ECAM Control Panel (ECP)](../../a380x-briefing/flight-deck/pedestal/ecam).
+
+ You can navigate through the checklist by using the `UP` and `DOWN` buttons on the ECP. You can check/uncheck items
+ by pressing the buttons with the check mark on the ECP.
+
+ Some items are autosensed by the aircraft and will be checked automatically.
+
+ {loading=lazy}
+
+!!! warning "Thrust levers during landing"
+ For the landing, we have our hand on the thrust levers for a potential go-around, so we can quickly push the levers
+ forward into `TO GA`.
+
+ **We do not move the levers until the last seconds before landing.**
+
+This concludes *Preparation and Checklist for Landing*
+
+---
+
+## 4. Landing
+
+**Situation:**
+
+- Aircraft is fully set up for landing as per previous chapters.
+- Configuration is `FLAPS FULL`.
+- Aircraft is at about 1000ft above the ground.
+- Wind is calm (no crosswind for this beginner guide).
+
+Verify these items:
+
+`LANDING GEAR ........................................................ DOWN`
+`NOSE LIGHT ........................................................... T.O`
+`RWY TURN OFF LIGHT .................................................... ON`
+`AUTOBRAKE ........................................................ CONFIRM`
+`GROUND SPOILERS ...................................................... ARM`
+`EXTERIOR LIGHTS ...................................................... SET`
+`FLAPS ............................................................... FULL`
+`AUTOTHROTTLE .................................. CHECK IN SPEED MODE OR OFF`
+
+??? tip "Autoland"
+ Although the A380 can do an automatic landing (**Autoland**) we will do a manual landing as this is more common and
+ also more fun.
+
+ For an advanced guide on Autoland, see [here](../../a32nx/a32nx-advanced-guides/flight-guidance/autoland.md).
+
+!!! warning "Clearance"
+ We MUST get landing clearance from ATC before we actually are allowed to land. Without landing clearance, we must do
+ a go-around (not part of this beginner guide) before touching the runway. Usually, ATC will have given us clearance
+ at this point. Late clearance is rare and communicated to us beforehand.
+
+`AUTOPILOT ............................................................ OFF`
+??? note "Autopilot OFF"
+ Next, we turn the **Autopilot** `OFF` at about 500ft above the ground by pressing the green lit `AP1+2` buttons on
+ the `FCU`.
+
+ We leave the **Autothrust** on, so we don't have to worry about thrust and speed at all (Leaving **Autothrust** on
+ for landing is common for the Airbus).
+
+??? tip "PAPI lights"
+ At the beginning of the runway you will notice an array of lights to the runway side. These are called PAPI lights
+ and act as a visual indicator as to whether or not the airplane is on the correct glideslope. The lights also
+ indicate whether the plane is too high or too low off glideslope. For example, if you see 4 white lights, that means
+ the plane is too high. If you see 4 red lights, that means the plane is too low. We want two white lights and 2 red
+ lights.
+
+ {loading=lazy}
+
+ See also [Wikipedia:PAPI](https://en.wikipedia.org/wiki/Precision_approach_path_indicator)
+
+ We correct our pitch only very carefully when too high (3-4 white) or too low (3-4 red). We don't need a lot of
+ input to the sidestick to correct.
+
+??? tip "Touchdown zone and center line"
+ We aim for the middle of the touchdown zone, which is marked by the touchdown zone markers.
+
+ {loading=lazy}
+
+ Also, we try to aim for the center line of the runway in a way that it points directly under us.
+
+ Correct your final heading and bank very carefully. We should not need to correct much at this point.
+
+`LAND ON FMA (at 350ft agl) ......................................... CHECK`
+`ILS COURSE ......................................................... CHECK`
+
+`ONE HUNDRED ABOVE ................................................ MONITOR`
+
+`MINIMUM .......................................................... MONITOR`
+`LANDING or GO-AROUND............................................. MONITOR`
+??? note "Go-Around"
+ If you are not stable for landing at 100ft above the ground, you should do a go-around. This is a common procedure
+ and not a failure.
+
+ Thie beginner guide does not cover a go-around - see the advanced guide for this.
+
+??? note "Flaring"
+ Once over the runway threshold, we look towards the end of the runway to better judge our pitch, especially for the
+ so-called **Flare**.
+
+ The flare follows the final approach phase and precedes the touchdown and roll-out phases of landing. In the flare,
+ the nose of the plane is raised, slowing the descent rate and therefore, creating a softer touchdown, and the proper
+ attitude is set for touchdown.
+
+ At the runway threshold we should be about 50ft above ground and prepare to set the thrust levers to idle and flare.
+
+ {loading=lazy}
+
+ At about 40ft, we start our flare by pulling back on the sidestick carefully. We only need a few degrees in positive
+ pitch and hold the aircraft there. Too much flare will cause the aircraft to float down the runway, too little will
+ cause a harder landing.
+`ATTITUDE ......................................................... MONITOR`
+??? note "Attitude"
+ We hold the attitude of the aircraft until it settles on the ground.
+
+ **Do not push the sidestick forward (nose down) once flared.**
+
+ We let the aircraft settle to the runway while holding the pitch.
+`THRUST LEVERS ....................................................... IDLE`
+`DEROTATION ...................................................... INITIATE`
+??? note "Derotation"
+ We let the front gear settle gently on the runway (don't slam it down) and hold the center line of the runway while
+ we are reducing speed. The speed reduction should be monitored on the `PFD` speed band and the speed trend arrow.
+
+`REVERSER LEVERS ..................................................... PULL`
+??? note "Reverser Levers"
+ It is recommended to select MAX REV as soon as the landing gear touches down. If for operational reason the use of
+ the thrust reversers are limited, it is recommended to maintain IDLE REV until the aircraft reaches the taxi speed.
+`GROUND SPOILERS EXTENDED................................. CHECK / ANNOUNCE`
+??? note "Ground Spoilers"
+ Verify the slats/flaps display on the lower part of the primary flight display. Ensure that the ground spoilers are
+ deployed. In the event of no deployment, check that all thrust levers are positioned at the IDLE detent. If no
+ ground spoilers extended, set both thrust reversers to MAX REV, and press the brake pedals.
+`REVERSERS ............................................... CHECK / ANNOUNCE`
+??? note "Reversers"
+ You can verify the reversers on the Engine Warning Display. It should display the reverser deployment.
+`AUTO BRAKE ................................................ CHECK/ANNOUNCE`
+??? note "Auto Brake"
+ The `Autobrakes` should now have activated and started to further decelerate the aircraft. This can be checked by
+ the `Autobrake` annunciators.
+
+ If you have configured BTV (Brake to Vacate) the FMA should now show `BTV` in green.
+
+`REVERSE LEVERS (at <80knots) ........................................ IDLE`
+
+This concludes *Landing*
+
+---
+
+## 5. Vacate Runway
+
+**Situation:**
+
+- Aircraft has landed and is moving along the center line of the runway.
+- Speed is <40knots.
+
+### At Taxi Speed
+
+`REVERSE LEVERS ...................................................... STOW`
+`AUTOBRAKE ......................................................... DISARM`
+??? note "Auto Brake Disarm"
+ The autobrake can be disarmed at the pilot’s discretion. It is recommended to use one of the autothrottle
+ instinctive disconnect pushbuttons to disarm the autobrake. If BTV mode was used, the autobrake will disarm
+ automatically at 10 knots.
+
+### Vacate the runway
+We look for the next runway exit and slow down to about 10knots before we start turning off the runway.
+
+We continue rolling forward until we passed the runway entry marker with the **full length** of our aircraft.
+
+![Aircraft stopped after runway is vacated](../assets/beginner-guide/07_landing/runway-vacated.png
+"Aircraft stopped after runway is vacated"){loading=lazy}
+
+We can now safely stop the aircraft and do our "After Landing" checklist - see next chapter.
+
+If ATC did not already contact us on the ground, we would contact them now to let them know we have vacated the runway.
+
+They will give us taxi instructions, so we can continue taxiing to our gate once we have completed the after landing
+tasks.
+
+!!!info "After landing tasks in simulation"
+ In real life, the A380 will have two pilots which can actually do things in parallel, such as talking to ATC,
+ taxiing the aircraft and doing the after landing tasks. In the simulation we are typically alone, so it is perfectly
+ fine to stop once we have fully vacated the runway and do these things one after the other.
+
+This concludes *Vacate Runway*
+
+Continue with [After Landing Steps](../08_after-landing)
diff --git a/docs/pilots-corner/a380x/a380x-beginner-guide/08_after-landing.md b/docs/pilots-corner/a380x/a380x-beginner-guide/08_after-landing.md
new file mode 100644
index 000000000..49989e991
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-beginner-guide/08_after-landing.md
@@ -0,0 +1,176 @@
+
+# After Landing and Taxi to Gate
+
+This guide will explain the correct procedures after we have landed and vacated the runway, and will also cover taxiing to the designated gate.
+
+!!! warning "Disclaimer"
+
+??? note "Radio Frequency"
+ ATC Tower will usually hand us off to ATC Ground, and they will give us taxi instructions for our destination gate.
+ Write them down and read them back as usual, but you don't have to move immediately unless ATC explicitly tells you
+ to. Online ATC controllers understand that the after-landing-tasks do take some time.
+
+ If you did not get any frequencies from ATC, you can use the airport charts to find the correct frequencies for EDDM.
+`AUXILLIARY POWER UNIT MASTER SWITCH ................................... ON`
+`GROUND SPOILERS ................................................... DISARM`
+`FLAPS ............................................................ RETRACT`
+`APU MASTER ............................................................ ON`
+`APU START ............................................................. ON`
+??? note "Starting the APU"
+ Once we are safely off the runway and on to our assigned taxiway, we need to start the APU. We are doing this to
+ ensure the aircraft will still have electrical power and air conditioning and circulation once we complete our
+ taxi to our assigned gate. Upon reaching the gate, our engines will need to be shut down, and we are still
+ going to need power for a little bit while we focus on shutting the airplane down.
+`ENGINE START SELECTOR ......................................... CHECK NORM`
+`ANTI-ICE ..................................................... AS REQUIRED`
+
+??? tip "How and Where"
+ [Flight Deck Overview](../../a380x-briefing/flight-deck){ .md-button }
+
+ Use the Flight Deck Overview to locate the items mentioned above. The Flight Deck Overview is a
+ clickable cockpit that will show you where each item is located.
+
+ * [RMP Panel](../../a380x-briefing/flight-deck/pedestal/rmp)
+ * [Spoiler Lever](../../a380x-briefing/flight-deck/pedestal/speed-brake)
+ * [Flaps Lever](../../a380x-briefing/flight-deck/pedestal/flaps-lever)
+ * [APU Master Switch](../../a380x-briefing/flight-deck/ovhd/apu)
+ * [Engine Start Selector](../../a380x-briefing/flight-deck/ovhd/eng-start)
+ * [Anti-Ice](../../a380x-briefing/flight-deck/ovhd/anti-ice)
+
+### Exterior Lights
+??? tip "What and Why"
+ The exterior lights are used to make the aircraft more visible to other traffic and ground personnel. The lights
+ are used to signal the aircraft's intentions and to make the aircraft more visible in low light conditions.
+
+`LANDING LIGHTS ....................................................... OFF`
+`STROBE .............................................................. AUTO`
+`OTHER EXTERIOR LIGHTS ........................................ AS REQUIRED`
+`NOSE ................................................................ TAXI`
+`RUNWAY TURN OFF LIGHTS & CAMERA............................... AS REQUIRED`
+
+### Prepare for Taxi
+
+??? tip "What and Why"
+ The aircraft needs to be prepared for taxiing to the gate. This includes setting up the aircraft systems for
+ taxiing and ensuring that the aircraft is ready to taxi to the gate.
+
+`AIRPORT NAVIGATION DISPLAY RANGE..................... ZOOM, AS APPROPRIATE`
+`EFIS TAXI..................................................... AS REQUIRED`
+`WEATHER RADAR ...................................................CHECK OFF`
+??? note "Weather Radar"
+ The A380X does not have a weather radar system implemented yet as the simulator does not allow access to the weather
+ data to implement a proper weather radar system. This is a feature planned for the future when the simulator
+ allows for it.
+`BRAKE TEMPERATURE ................................................ MONITOR`
+??? note "Brake Temperature"
+ You can monitor the brake temperature on the SD WHEEL page. Verify the temperatures for discrepancies and high
+ temperature (higher than 500°C).
+
+This concludes *After Landing*
+
+## 2. Taxi to Gate
+
+### Situation
+
+- Aircraft on taxiway directly after runway.
+- **After Landing** checklist is completed.
+- ATC Ground has given taxi instructions.
+
+### Taxiing
+
+Make sure to also read the Taxi section of the [Engine Start and Taxi](04_engine-start-taxi#taxi) chapter.
+Use your charts to follow the ATC taxi instructions to the designated gate.
+
+!!! warning "Only use taxiways approved for the A380"
+ The A380 is a large aircraft and not all taxiways are approved for the A380. Make sure to follow the taxi instructions
+ and only use taxiways that are approved for the A380.
+
+ A380 Airport Taxi Chart for EDDF:
+ {loading=lazy}
+ *Copyright © 2024 Navigraph / Jeppesen
+ "Navigraph Charts are intended for flight simulation use only, not for navigational use."*
+
+??? tip "How to Cross a Runway"
+ When approaching a runway, always ensure you have ATC permission to cross it. Ask ATC for
+ permission to cross the runway and read back the instructions. Always ensure maximum safety
+ when crossing.
+ When approved to cross a runway (active or not) perform the following actions:
+ - Look out the windows and visually ensure that there are no visible aircraft to your left and right.
+ - Turn on extra lights to ensure your aircraft is visible when crossing:
+ - Strobe lights - `Set to ON`
+ - Inform ATC you have vacated the runway if required.
+
+ !!! warning
+ NEVER cross a runway without express permission from ATC and providing a read back of said
+ instructions. Always ensure maximum safety when crossing.
+
+ `ATC CLEARANCE .................................................. OBTAIN`
+ `LANDING LIGHTS ..................................................... On`
+ `STROBE LIGHTS ...................................................... ON`
+
+ After you have crossed the runway and are on the adjacent taxiway, turn the strobe lights back
+ off, and notify ATC you are clear of that runway.
+
+ `STROBE LIGHTS ..................................................... OFF`
+ `LANDING LIGHTS .................................................... OFF`
+
+### Turning into the Gate
+`NOSE LIGHTS .................................................. AS REQUIRED`
+`RWY TURN OFF LIGHTS ...........................................AS REQUIRED`
+??? tip "Turning into the Gate"
+ When turning into the gate, turn off your `NOSE` light and your `RWY TURN OFF` lights to not
+ blind the ground personnel. This of course is only done if enough lighting is available to safely
+ navigate and park into the gate.
+
+
+
+This concludes *Taxi to Gate*
+
+Continue with [Powering Down](../09_powering-down)
diff --git a/docs/pilots-corner/a380x/a380x-beginner-guide/09_powering-down.md b/docs/pilots-corner/a380x/a380x-beginner-guide/09_powering-down.md
new file mode 100644
index 000000000..c25c38199
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-beginner-guide/09_powering-down.md
@@ -0,0 +1,198 @@
+
+
+# Powering Down
+
+This guide will explain the correct procedures to power down the aircraft when at the gate after arriving at the
+destination and taxiing to the designated gate.
+
+!!! warning "Disclaimer"
+
+`APU BLEED ............................................................. ON`
+`PARKING BRAKE ......................................................... ON`
+`ENGINE MASTER SWITCHES (1, 2, 3, 4) .................................. OFF`
+`SEAT BELTS ........................................................... OFF`
+`SLIDES DISARMED .................................................... CHECK`
+`ENGINE ALL N1 < 5% ..................................................AWAIT`
+`BEACON ............................................................... OFF`
+`EXTERIOR LIGHTS ...............................................AS REQUIRED`
+`GROUND CONTACT ............................................... ESTABLISHED`
+`FUEL PUMPS ........................................................... OFF`
+`FUEL QUANTITY .................................................... CHECKED`
+??? note "Fuel Quantity"
+ Verify the amount of fuel left on board is consistent with the predicted fuel remaining.
+
+??? tip "How and Where?"
+ [Flight Deck Overview](../../a380x-briefing/flight-deck){ .md-button }
+
+ Use the Flight Deck Overview to locate the items mentioned above. The Flight Deck Overview is a
+ clickable cockpit that will show you where each item is located.
+
+ * [Anti-Ice](../../a380x-briefing/flight-deck/ovhd/anti-ice)
+ * [APU Bleed](../../a380x-briefing/flight-deck/ovhd/apu)
+ * [Parking Brake](../../a380x-briefing/flight-deck/pedestal/parking-brake)
+ * [Engine Master Switches](../../a380x-briefing/flight-deck/pedestal/engine-master)
+ * [Seat Belts](../../a380x-briefing/flight-deck/ovhd/int-lt)
+ * [Beacon](../../a380x-briefing/flight-deck/ovhd/ext-lt)
+ * [Exterior Lights](../../a380x-briefing/flight-deck/ovhd/ext-lt)
+ * [Fuel Pumps](../../a380x-briefing/flight-deck/ovhd/fuel)
+
+`PARKING CHECKLIST ............................................... COMPLETE`
+??? note "Parking Checklist"
+ The Airbus A380 has a built-in checklist system that can be accessed via the
+ [Engine Warning Display (EWD)](../../a380x-briefing/flight-deck/main-panel/ewd).
+
+ To activate it you need to press the `C/L` button on the
+ [ECAM Control Panel (ECP)](../../a380x-briefing/flight-deck/pedestal/ecam).
+
+ You can navigate through the checklist by using the `UP` and `DOWN` buttons on the ECP. You can check/uncheck items
+ by pressing the buttons with the check mark on the ECP.
+
+ Some items are autosensed by the aircraft and will be checked automatically.
+
+ {loading=lazy}
+
+This concludes *Parking at the Gate*.
+
+## 2. Disembarking Passengers and Baggage
+
+**Situation**
+
+- **Parking** checklist is completed.
+
+In real life, there are many things that begin automatically after parking at the gate. The Jetway is connected to the
+aircraft, doors are opened, passengers disembark, cargo is unloaded, etc. The pilots don't have to do much to trigger
+these steps.
+
+In the simulator, though, we would have to trigger these events by ourselves. For this, we use the FlyByWire flyPad's
+ground functionality or the Microsoft Flight Simulator's built-in ATC to start these procedures. There are also some
+nice add-on tools out there which help with this.
+
+Taking care of passengers and luggage with the FlyByWire flyPad:
+
+- Go to the flyPad (view can be activated by `Ctrl+0`).
+- Connect the Jetway (PAX).
+- Call cargo/baggage (Baggage).
+
+This would take a while in real life, and we would not be able to shut down the aircraft before all
+passengers and crew have disembarked.
+
+For a turnaround, we would start preparing the aircraft for the next flight, and the cabin crew would coordinate
+everything from disembarking the passengers to cleaning and resetting the cabin.
+
+After refueling, the pilot would signal to the cabin crew that they could let the new passengers board the aircraft once
+the cabin is ready.
+
+This concludes *Disembarking Passengers and Baggage*.
+
+## 3. Securing the Aircraft
+
+**Situation**
+
+- **Parking** checklist is completed.
+- Aircraft is empty (no passengers or cargo).
+- Cabin is cleaned and ready for shutdown.
+
+??? tip "What and Why?"
+ In the event that there is no other crew that will use this aircraft for a flight immediately following ours, we are
+ going to secure the aircraft. Doing this will put the aircraft into a `Cold and Dark` state, meaning whoever flies the
+ aircraft next will have to do a complete power up. To do this, we will need to shut off all lighting, power and fuel
+ pumps. We are essentially doing the opposite of what we did when we powered the plane up from a `Cold and Dark` state.
+
+`PARKING BRAKE ......................................................... ON`
+`OXYGEN CREW SUPPLY ................................................... OFF`
+`ADIRS (1+2+3) ........................................................ OFF`
+`EXTERIOR LIGHTS ...................................................... OFF`
+`APU BLEED ............................................................ OFF`
+`EXTERNAL POWER ....................................................... OFF`
+`AUXILIARY POWER UNIT MASTER SWITCH ................................... OFF`
+`EMERGENCY EXIT LIGHTS ................................................ OFF`
+`NO SMOKING ........................................................... OFF`
+
+??? tip "How and Where?"
+ [Flight Deck Overview](../../a380x-briefing/flight-deck){ .md-button }
+
+ Use the Flight Deck Overview to locate the items mentioned above. The Flight Deck Overview is a
+ clickable cockpit that will show you where each item is located.
+
+ * [Parking Brake](../../a380x-briefing/flight-deck/pedestal/parking-brake)
+ * [Oxygen Crew Supply](../../a380x-briefing/flight-deck/ovhd/oxygen)
+ * [ADIRS](../../a380x-briefing/flight-deck/ovhd/adirs)
+ * [Exterior Lights](../../a380x-briefing/flight-deck/ovhd/ext-lt)
+ * [APU Bleed](../../a380x-briefing/flight-deck/ovhd/apu)
+ * [External Power](../../a380x-briefing/flight-deck/ovhd/elec)
+ * [APU Master Switch](../../a380x-briefing/flight-deck/ovhd/apu)
+ * [Emergency Exit Lights](../../a380x-briefing/flight-deck/ovhd/signs)
+
+`SECURING THE AIRCRAFT CHECKLIST ................................. COMPLETE`
+??? note "Securing the Aircraft Checklist"
+ The Airbus A380 has a built-in checklist system that can be accessed via the
+ [Engine Warning Display (EWD)](../../a380x-briefing/flight-deck/main-panel/ewd).
+
+ To activate it you need to press the `C/L` button on the
+ [ECAM Control Panel (ECP)](../../a380x-briefing/flight-deck/pedestal/ecam).
+
+ You can navigate through the checklist by using the `UP` and `DOWN` buttons on the ECP. You can check/uncheck items
+ by pressing the buttons with the check mark on the ECP.
+
+ Some items are autosensed by the aircraft and will be checked automatically.
+
+ {loading=lazy}
+
+`ALL BATT (Battery 1, Essential, Battery 2, APU Battery) .............. OFF`
+
+Now the aircraft is back in a cold and dark state.
+
+This concludes *Securing the Aircraft*
+
diff --git a/docs/pilots-corner/a380x/a380x-beginner-guide/overview.md b/docs/pilots-corner/a380x/a380x-beginner-guide/overview.md
new file mode 100644
index 000000000..bfb1c4d3a
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-beginner-guide/overview.md
@@ -0,0 +1,75 @@
+---
+title: A380X Beginner Guide - Overview
+description: The A380X Beginner Guide teaches users how to operate and fly the FlyByWire A380X aircraft.
+---
+
+
+
+# Overview
+
+Welcome to the A380X Beginner's Guide. Although this guide is tailored towards beginners, each topic below may even
+serve as reminders of proper procedure at different stages of flight for veteran sim pilots.
+
+Each page was reviewed by an A380 type rated pilot and provides accurate information to aircraft operation.
+
+!!! warning "Disclaimer"
+
+ The FG gives guidance based on flight targets picked by the flight crew, or managed by the Flight Management System.
+- The Flight Management System (FMS)
+ The FMS handles the flight plan, set by the flight crew, and gives flight parameters to the FG accordingly.
+
+### Flight Guidance (FG)
+
+The FG's job is to give lateral and vertical guidance, including speed or Mach control, based on set targets.
+These targets can be either selected or managed.
+
+#### Selected Targets
+
+The flight crew picks the targets via the short-term interface: The AFS Control Panel (CP). Then the FG uses these
+targets to give selected guidance.
+
+#### Managed Targets
+
+The flight crew uses the long-term interface, the Multi Function Display (MFD), to set up the flight plan. The FMS
+calculates managed targets accordingly. Then the FG uses these targets to give managed guidance.
+
+### AFS CP Philosophy
+
+On the AFS CP, the SPD/MACH, HDG/TRK, V/S / FPA knobs can be turned, pulled, and pushed. This lets the flight crew:
+
+- Preselect a target: Turn
+- Use a mode that will guide the aircraft to a **selected** target: Pull
+- Arm or use a mode that will guide the aircraft to a **managed** target: Push.
+
+Here is an example with the ALT (altitude) knob:
+
+Pull = Selected / Push = Managed
+
+### FG FUNCTIONS: AP, FD AND A/THR
+
+To do its job (lateral guidance, vertical guidance, including speed or Mach control), the FG uses:
+
+- The Autopilot 1 and/or 2 (AP1 and/or AP2)
+ The AP gives flight guidance by calculating pitch, roll, yaw and nosewheel steering orders.
+- The Flight Directors 1 and 2 (FD1 and FD2)
+ The FDs show guidance orders on the PFDs to help the flight crew fly the aircraft manually. When the AP is on, the
+ flight crew can use the FD orders to monitor the guidance.
+- The Autothrust (A/THR)
+ A/THR controls the thrust by sending commands to the engines.
+
+### FLIGHT MANAGEMENT SYSTEM (FMS)
+
+The Flight Management System (FMS) gives **long-term guidance** along the set flight plan.
+
+To do these long-term tasks, the FMS calculates managed targets, that are then sent to the FG.
+
+Besides long-term guidance, the FMS:
+
+- Gives flight planning and navigation info
+- Calculates and optimizes performance data
+- Shows info on the MFD, ND and PFD.
+
+### FLIGHT MANAGEMENT COMPUTER (FMC)
+
+There are two FMSs (FMS1 and FMS2), that use three FMCs: FMC-A, FMC-B and FMC-C.
+
+In normal operation:
+
+- FMC-A runs FMS1
+- FMC-B runs FMS2
+- FMC-C is on standby, ready to run FMS1 or FMS2.
+ Each FMC can run all the flight management functions.
+
+### Flight Director (FD)
+
+The Flight Director (FD) shows guidance orders on the Primary Flight Displays (PFDs):
+
+- If no AP is on, the flight crew can manually fly the aircraft by following FD orders
+- If at least one AP is on, the flight crew can use the FD to monitor the flight guidance.
+
+When the FDs are on, the PFDs can show the roll, pitch and yaw bars.
+
+When the FDs are on:
+
+- The FD pb on the AFS CP lights up
+- 1FD2 shows up on both FMAs
+- When a mode is active, the PFDs show the FD orders.
+
+### Autopilot (AP)
+
+The Autopilot (AP):
+
+- Stabilizes the aircraft around its center of gravity
+- Controls the lateral path
+- Controls the vertical path, or speed/Mach
+- Works with the A/THR
+- Does the automatic landing, or the go-around.
+
+The AP generates:
+
+- Pitch, roll, and yaw orders
+- The nosewheel angle.
+
+There are two APs: AP1 and AP2. Only one works at a time. AP1 uses ADIRS1, and AP2 uses ADIRS2.
+
+AP1 and AP2 usually work separately. In some conditions (e.g. APPR mode), the flight crew can use both at the same time.
+
+One AP works when the flight crew presses the AP1 pb or the AP2 pb on the AFS CP, and:
+
+- The aircraft is in flight for more than 5 s
+- The aircraft pitch, bank angle, and speed are not too much.
+ - The pitch is between -11 ° and 22.5 °
+ - The bank angle is less than 40 °
+ - The speed is between VLS and VMAX.
+
+When AP1(2) works:
+
+- The AP1(2) pb lights up
+- Both FMAs show:
+ - AP1 (AP2)
+ - AP1+2, if both APs are on.
+
+The status of the AP shows in the AP, FD, A/THR status column of FMAs.
+
+The standard way to manually turn off the AP is to press two times the sidestick pb on either sidestick.
+
+The AP also turns off when the flight crew:
+
+- Press the AP1(2) pb, while AP1(2) is already on, or
+- Move a sidestick, or the sidestick deflection goes beyond 5° on pitch axis, or 6° on roll axis.
+- Moves the rudder pedals. The rudder pedal deflection goes beyond 10°.
+
+The AP automatically turns off, if one of the following happens:
+
+- The aircraft pitch, bank angle, speed/Mach, or Angle Of Attack (AOA) becomes too much:
+ - The pitch is below -13 °, or above 25 °
+ - The bank angle is above 45 °
+ - The speed is below VLS, or above VMO + 15 kt
+ - The Mach is above MMO + 0.04
+ - The AOA is above αprot + 1 ° (above 100 ft RA).
+ - This does not apply in LAND below 200 ft RA.
+- A failure happens in approach
+
+Different warnings will trigger, depending on how it disconnects.
+
+As the AP system is a complex system, a full description of the AP system goes beyond this briefing. It is planned to
+provide a dedicated advanced guide on the Auto Flight System (AFS) in the future.
+
+### Autothrust (A/THR)
+
+The A/THR is either armed, active, or off.
+
+When active, the A/THR can work in two different types of mode:
+
+- SPEED/MACH mode: The A/THR continuously adjusts the thrust to keep a speed/Mach target, e.g. during cruise, and approach
+- THRUST modes: The A/THR controls a fixed thrust, based on the active THRUST mode.
+
+The A/THR modes are automatically linked to the AP/FD vertical modes:
+
+- When an AP/FD vertical mode controls the path (e.g. altitude acquire modes, altitude hold modes, V/S / FPA, G/S,
+ F-G/S), the A/THR is in SPEED/MACH mode
+- When an AP/FD vertical mode adjusts the aircraft pitch to keep a speed/Mach target (e.g. climb, descent), the A/THR is
+ in THRUST mode.
+
+The flight crew uses the thrust levers to:
+
+- Arm, activate, and turn off the A/THR
+- Use the takeoff and go-around modes
+- Manually control the thrust of each engine, when the A/THR is off
+- Use reverse thrust on engine 2 and 3.
+- The thrust levers have:
+ - Four detents: 0 (idle), CL, FLX-MCT, TOGA.
+ - Two instinctive disconnect pushbuttons.
+
+When the A/THR is active:
+
+- The FMA shows:
+ - The A/THR message on the third line of the fifth column
+ - The A/THR mode in green on the first line of the first column.
+- The A/THR pb light is on the AFS CP.
+
+As the A/THR system is a complex system, a full description of the A/THR system goes beyond this briefing. It is planned
+to provide a dedicated advanced guide on the Auto Flight System (AFS) in the future.
+
+## Usage
+
+### SPD/MACH pb
+
+If the speed (Mach) target is selected pressing the SPD/MACH pb changes the speed target to the corresponding Mach
+target, and vice versa.
+
+### SPD/MACH Display
+
+- Shows `SPD` and the selected speed in selected target mode.
+- Shows `MACH` and the selected mach speed in selected target mode.
+- Shows `SPD` and `---` in managed target mode.
+- Shows `MACH` and `---` in managed target mode.
+
+Note: At the speed/Mach crossover altitude, the managed speed target automatically changes to a managed Mach target. The
+display on the SPD/MACH window changes from SPD to MACH (and vice versa in descent).
+
+### SPD/MACH Knob
+
+- When turned, preselects a speed or Mach target
+- Note:
+ - When the SPD/MACH window is dashed, and if the flight crew begins to turn the knob without pulling it, the window
+ displays:
+ - The current aircraft speed, if SRS TO, or SRS GA is on, or
+ - The managed speed/Mach target, in all other cases.
+ - Then, turning the knob would change the value. If there is no action on the knob for 45 s, the dashes reappear.
+- When pulled, activates the selected speed or Mach target
+- When pushed, the speed or Mach becomes managed.
+
+One entire rotation of the knob equals 32 kt (1 kt per click), or 0.32 Mach (0.01 Mach per click).
+
+The selection has a range of:
+
+- 100 kt to 399 kt for the speed
+- M 0.01 to M 0.99 for the Mach.
+
+### TRUE/MAG pb
+
+When pressed, changes the TRUE North reference to Magnetic (MAG) North reference, and vice versa.
+
+The North reference is magnetic, unless the aircraft is in the polar zone.
+
+When the aircraft reaches the polar zone:
+
+- The North reference automatically changes from MAG to TRUE in the ADIRSs
+- The following messages ask the flight crew to change from MAG to TRUE North reference:
+ - The SELECT TRUE NORTH REF memo shows up on the ND
+ - The NAV EXTREME LATITUDE triggers.
+
+### HDG/TRK pb
+
+When pressed, selects either:
+
+- HDG-V/S: Heading (HDG) is linked with Vertical Speed (V/S)
+ If the VV pb is pressed on the EFIS CP, the linked PFD shows the Velocity Vector (VV) in black.
+- TRK-FPA: Track (TRK) is linked with Flight Path Angle (FPA)
+ The PFDs show the Flight Path Vector (FPV) in green.
+
+### HDG/TRK Display
+
+- Shows `HDG` and the selected heading in selected target mode
+- Shows `TRK` and the selected track in selected target mode
+- Shows `HDG` and `---` in managed target mode
+- Shows `TRK` and `---` in managed target mode
+
+Note: The HDG/TRK window shows TRUE, at the top left corner of the HDG/TRK window, if TRUE is selected with the
+TRUE/MAG pb.
+
+### HDG/TRK Knob
+
+- When turned, preselects a heading or track target
+- Note: When the HDG/TRK window is dashed, and if the flight crew begins to turn the knob without pulling it, the window
+ shows the current aircraft heading/track. Then, turning the knob would change the value. If there is no action on the
+ knob for 45 s, the dashes reappear. However, if a HDG/TRK preset is set, the value stays permanently.
+- When pulled, activates the selected heading or track target
+- When pushed, a managed lateral mode arms or works.
+
+One entire rotation of the knob equals 32 ° (1 ° per click).
+
+The selection has a range of 0° to 359°.
+
+### LOC pb
+
+When pressed, arms/works or disarms/stops the LOC, LOC B/C, or F-LOC mode.
+
+### FD pb
+
+When pressed, works/stops the FDs.
+
+### AP1/2 pb
+
+When pressed, works/stops the AP1 or AP2.
+
+### A/THR pb
+
+When pressed, arms/works or disarms/stops the A/THR.
+
+### METER pb
+
+When pressed, shows the current and target altitudes in meters (in addition to feet) on the PFDs. When pressed again,
+clears the meter display from the PFDs.
+
+### ALT Display
+
+Shows the altitude set by the flight crew with the ALT knob.
+
+Note: The window never shows dashes.
+
+### ALT Knob
+
+When turned, sets the target altitude on the AFS CP.
+
+The outer knob has two positions: 100 and 1000, to set the target altitude in increments of 100 ft or 1 000 ft.
+
+- When pulled, activates the selected target altitude on the AFS CP. The FMS vertical profile is ignored.
+- When pushed, the altitude target becomes managed. The FMS vertical profile is followed, or the AFS CP target altitude
+ is followed, if applicable.
+
+### ALT pb
+
+When pressed, the aircraft immediately starts to level-off.
+
+Note: The ALT pb also lights up, when the aircraft keeps a selected or managed altitude.
+
+### V/S / FPA Display
+
+- Shows `V/S` and the selected vertical speed in selected target mode
+- Shows `FPA` and the selected flight path angle in selected target mode
+- Shows `V/S` and `---` in managed target mode
+- Shows `FPA` and `---` in managed target mode
+
+### V/S / FPA Knob
+
+When turned, preselects a vertical speed or flight path angle target
+
+Note: When the V/S / FPA window is dashed, and if the flight crew turns the knob without pulling it, the window shows
+the current V/S / FPA aircraft. Then, turning the knob would change the value. If there is no action for 45 s, the
+dashes reappear.
+
+- When pulled, activates the selected vertical speed or flight path angle target.
+- When pushed: There is no effect.
+
+One entire rotation equals 1 600 ft/min in vertical speed (100 ft/min per 2 clicks), or 3.2 ° in flight path
+angle (0.1 ° per click).
+
+The selection has a range of:
+
+- –6 000 ft/min to +6 000 ft/min for the vertical speed
+- –9.9 ° to + 9.9 ° for the flight path angle.
+
+### APPR pb
+
+When pressed, arms or disarms/stops the APPR modes.
+
+---
+
+[Back to Main Instrument Panel and Glareshield](../overviews/main-glare.md){ .md-button }
+
+---
\ No newline at end of file
diff --git a/docs/pilots-corner/a380x/a380x-briefing/flight-deck/glareshield/efis.md b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/glareshield/efis.md
new file mode 100644
index 000000000..ec58441ef
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/glareshield/efis.md
@@ -0,0 +1,135 @@
+---
+title: Electronic Flight Instrument System (EFIS) Panel
+description: The A380 Flight Deck Electronic Flight Instrument System (EFIS) Panel description.
+---
+
+# Electronic Flight Instrument System (EFIS) Panel
+
+---
+
+[Back to Main Instrument Panel and Glareshield](../overviews/main-glare.md){ .md-button }
+
+---
+
+
+
+## Description
+
+The Electronic Flight Instrument System (EFIS) lets you control what flight info shows up on the Primary Flight Displays
+(PFDs) and the Navigation Displays (NDs).
+
+The EFIS Control Panel helps the flight crew pick and set up the info they want to see on the PFDs and NDs.
+
+## Usage
+
+### TAXI pb
+
+Press this to turn the ETACS (Enhanced Taxi Aid and Crew Awareness System) video on or off on the PFD.
+
+!!! warning "ETACS"
+ The ETACS system isn't simulated in the A380X because of simulator limitations.
+
+### ND Data Display pushbuttons
+
+These buttons let the flight crew choose what info to show on the NDs.
+
+| Button | Function |
+|---------|-------------------------------------------------------------------------------------------------|
+| CSTR pb | Toggles showing flight plan constraints on the ND. |
+| WPT pb | Toggles showing waypoints on the ND. |
+| VORD pb | Toggles showing VOR/DME stations on the ND. |
+| NDB pb | Toggles showing NDB stations on the ND. |
+| ARPT pb | Toggles showing airports on the ND. |
+| VOR1 pb | Toggles showing the selected VOR1 information on the ND. |
+| WX pb | Toggles showing weather radar information on the ND. (INOP) |
+| TERR pb | Toggles showing terrain information on the ND. |
+| TRAF pb | Toggles showing traffic information on the ND. |
+| VOR2 pb | Toggles showing the selected VOR2 information on the ND. |
+
+### Barometric Reference Window
+
+- If `QNH` is in the upper left corner:
+ - The barometric reference is set to the number shown.
+ - The QNH range is from 745 hPa (22.00 inHg) to 1 100 hPa (32.48 inHg).
+- If `QNH` isn't in the upper left corner and `STD` is shown:
+ - The barometric reference is STD.
+ - Turning the inner knob presets a QNH (upper right corner) and sets it when the knob is pushed.
+
+### Barometric Reference Controls
+The barometric reference controls have an outer selector and an inner knob.
+
+The flight crew uses the selector to pick the barometric unit (hectoPascal or mercury inches) for the values shown in
+the barometric reference window.
+
+Note: The PFDs don't show the selected barometric unit.
+
+The flight crew uses the knob to set the barometric reference value. When the EFIS CP powers up, the barometric
+reference value starts at 1 013 hPa or 29.92 inHg, depending on the selected unit.
+
+When the flight crew:
+
+- **pushes** the knob, the barometric reference is set to STD.
+ They can turn the knob to preset a QNH value. When they switch back to the QNH barometric reference, it automatically
+ shows this preset value.
+- **pulls** the knob, the barometric reference is set to QNH, and the preset value is selected.
+ Note: The selected value appears in the barometric reference window and under the altitude scale on the PFD.
+
+### LS pb
+
+The Captain's (First Officer's) PFD shows landing system data based on the approach selected on the FMS ARRIVAL page:
+Deviation scales, deviation signals, course pointer, and info.
+
+Note:
+
+1. If the destination airport is more than 300 NM away, only the deviation scales appear.
+2. The LS light automatically comes on when LOC, LOC B/C, or F-LOC arms.
+
+The Captain's (First Officer's) PFD doesn't show the landing system data.
+
+### VV pb
+
+Press this to show or hide the Velocity Vector (VV) on the PFD.
+
+### ND Mode Selector
+
+This selector lets the flight crew pick the ND mode they want.
+
+The flight crew can choose from these modes:
+
+- PLAN mode:
+ - Shows the flight plan on a map with North/South and West/East references.
+ - Lets the flight crew scroll through and display the entire flight plan.
+- ARC mode:
+ - Shows a 100° sector in front of the aircraft.
+- ROSE-NAV mode:
+ - Shows the same info as ARC mode but in a 360° sector.
+ - Displays the ROSE-NAV in relation to the aircraft heading.
+ - Defaults to ROSE-NAV mode with an 80 NM range if the ND mode or range isn't valid.
+- ROSE-VOR mode:
+ - Shows the aircraft's position relative to the tuned VOR.
+ - Displays the ROSE-VOR in relation to the aircraft heading.
+- ROSE-LS mode:
+ - Shows the aircraft's position relative to the LOC, F-LOC, G/S, and F-G/S indications.
+ - Displays the ROSE-LS in relation to the aircraft heading.
+
+### ND Range Selector
+
+The flight crew sets the range for the ND (Navigation Display) and the VD (Vertical Display) in nautical miles.
+
+When set to ZOOM, the ND shows the moving airport map.
+
+Note: The VD range is limited to 160 NM.
+
+If set to ZOOM, the VD display isn't available.
+
+If the flight crew changes ND mode from ARC to one of the ROSE or PLAN modes, the ND range automatically increases to
+the next value to keep the same distance in front of the aircraft mock-up.
+
+If the flight crew changes ND mode to ARC mode, the ND range automatically decreases to the previous value.
+
+---
+
+[Back to Main Instrument Panel and Glareshield](../overviews/main-glare.md){ .md-button }
+
+---
+
diff --git a/docs/pilots-corner/a380x/a380x-briefing/flight-deck/glareshield/glare-side.md b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/glareshield/glare-side.md
new file mode 100644
index 000000000..cc1878054
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/glareshield/glare-side.md
@@ -0,0 +1,97 @@
+---
+title: Glareshield Side Panels
+description: The A380 Flight Deck Glareshield Side Panels description.
+---
+
+# Glareshield Side Panels
+
+---
+
+[Back to Main Instrument Panel and Glareshield](../overviews/main-glare.md){ .md-button }
+
+---
+
+
+
+## Usage
+
+### CHRONO pb
+
+- When pressed one time, the ND displays and starts the chronometer.
+- When pressed two times, the ND freezes the time that appears on the ND.
+- When pressed three times, the ND resets the chronometer, and the ND no longer displays the time.
+
+### SIDESTICK PRIORITY pb
+
+- Red arrow light:
+ - Illuminates in front of the pilot who is losing authority.
+ - Light extinguishes if the pilot has recovered authority.
+ - If the pilot either:
+ - Releases his TAKEOVER pb before the priority condition is set
+ - Used the TAKEOVER pb to cancel a set priority situation.
+ **Sidestick priority audio**: The audio voice message "PRIORITY LEFT" or "PRIORITY RIGHT" is played each
+ time priority is taken.
+
+- Green CAPT and F/O lights:
+ - Both lights will flash if the pilots are attempting to move both sidesticks at the same time and neither pilot
+ takes priority.
+ - If a pilot who has taken priority by using the TAKEOVER pb and the other pilot's sidestick is in motion or not
+ neutral, the light of the pilot who has taken priority illuminates. It will extinguish when the opposing sidestick
+ returns to the neutral position.
+
+### Attention Getters
+
+There are two attention-getters on the glareshield of each flight crew member\`s station:
+
+One MASTER WARN light, and one MASTER CAUT light,
+depending on the severity of the failure. These attention-getters inform the flight crew of an alert.
+
+When pressed, the lights go off and the associated aural warnings stop.
+
+MASTER WARN flashes in the case of emergency situations (e.g. emergency procedure
+displayed on the EWD).
+
+MASTER CAUT lights up in the case of abnormal situations (e.g. abnormal procedure
+displayed on the EWD).
+
+Note: In the case of multiple failures, both MASTER WARN lights and
+MASTER CAUT lights may come on at the same time.
+
+### AUTOLAND WARNING LIGHT
+
+The events below trigger a flashing AUTOLAND red warning accompanied by a triple click audio warning when the aircraft
+is below 200 ft RA and the aircraft is in LAND mode:
+
+- AP1 and AP2 OFF below 200 ft RA.
+- LOC deviation (1/4 dot above 15 ft RA) or GLIDE deviation (1 dot above 100 ft RA). Both LOC and GLIDE scales will
+ flash on the PFD.
+- LOC signal lost above 15 ft or loss of GLIDE signal when above 100 ft. The flight director bars flash on the PFD and
+ LAND mode remains engaged.
+- Difference of radio altimeter indications is more than 15 ft.
+
+### ATC MSG
+
+If flashing: A message from the ATC has been received.
+
+Associated with a RING aural alert that sounds:
+
+- 10 s after the reception of a normal message
+- Immediately after the reception of an urgent message.
+ When the flight crew presses one of the two pushbuttons, the ATC MSG lights go off and the aural alert is canceled.
+ The RING aural alert also stops if the flight crew reads the message.
+
+The ATC MSG pb lighting and the aural alert are inhibited during takeoff and landing.
+
+### LOUDSPEAKER
+
+Volume control for the loudspeaker.
+
+### RADIO PTT
+
+Push-to-talk button for the radio.
+
+---
+
+[Back to Main Instrument Panel and Glareshield](../overviews/main-glare.md){ .md-button }
+
+---
diff --git a/docs/pilots-corner/a380x/a380x-briefing/flight-deck/glareshield/glare-underside.md b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/glareshield/glare-underside.md
new file mode 100644
index 000000000..8366c84fd
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/glareshield/glare-underside.md
@@ -0,0 +1,37 @@
+---
+title: Glareshield Underside
+description: The A380 Flight Deck Glareshield Underside description.
+---
+
+# Glareshield Underside
+
+---
+
+[Back to Main Instrument Panel and Glareshield](../overviews/main-glare.md){ .md-button }
+
+---
+
+
+
+
+## Description
+
+The Glareshield Underside has 4 knobs to control the brightness of the instrument panel flodd lights and the
+brightness of the glareshield integral lights and LCD brightness.
+
+## Usage
+
+From left to right:
+
+- Brightness for the instrument panel flood lights on the Captain side.
+- Brightness for the glareshield integral lights.
+- Brightness for the LCD displays.
+- Brightness for the instrument panel flood lights on the First Officer side.
+
+
+---
+
+[Back to Main Instrument Panel and Glareshield](../overviews/main-glare.md){ .md-button }
+
+---
+
diff --git a/docs/pilots-corner/a380x/a380x-briefing/flight-deck/index.md b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/index.md
new file mode 100644
index 000000000..05b62e06d
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/index.md
@@ -0,0 +1,49 @@
+---
+hide:
+ - toc
+ - navigation
+title: A380 Flight Deck Overview
+description: The A380 Flight Deck Overview is providing an interactive graphical overview of the A380 flight deck and its systems.
+---
+
+# Flight Deck Overview
+
+[Back to A380 Pilot Briefing Overview](../index.md){ .md-button }
+
+!!! note "Clickable Cockpit"
+ - Clickable overview of the A380 flight deck.
+ - Move the mouse over the panels to get the name of the panel.
+ - Click on the panels to get a more detailed description of that panel.
+
+
+
+
+
+
+---
+
+[Back to A380 Pilot Briefing Overview](../index.md){ .md-button }
+
+
+
diff --git a/docs/pilots-corner/a380x/a380x-briefing/flight-deck/main-panel/center-right.md b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/main-panel/center-right.md
new file mode 100644
index 000000000..e59c54fd0
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/main-panel/center-right.md
@@ -0,0 +1,178 @@
+---
+title: Center Right Panel
+description: The A380 Flight Deck Center Right Panel description. The Center Right Panel is holding
+ the landing gear indicator, the brake accumulator pressure gauge, the autobrake
+ selector, the RTO (Rejected Takeoff) button, the anti skid switch, the gear lever, the
+ clock.
+
+---
+
+# Center Right Panel
+
+---
+
+[Back to Main Instrument Panel and Glareshield](../overviews/main-glare.md){ .md-button }
+
+---
+
+{loading=lazy width=50%}
+
+## Description
+
+We have consolidated the Center Right Panel into a single page. The Center Right Panel is holding the following
+controls and instruments:
+
+- Landing Gear Indicator
+- Brake Accumulator Pressure Gauge
+- Autobrake Selector
+- RTO (Rejected Takeoff) Button
+- Anti Skid Switch
+- Gear Lever
+- Clock
+
+## Usage
+
+### Landing Gear Indicator
+
+The landing gear indicator is located on the center right panel. It displays the status of the nose landing gear (NLG),
+the left wing landing gear (WLG), and the body landing gear (BLG).
+
+The NLG, the WLG and the BLG indicator lights have the same logic.
+
+- Unlit:
+ - The associated landing gear is uplocked and the landing gear lever is in the UP position.
+- Green:
+ - The associated landing gear is downlocked and the landing gear lever is in the DOWN position.
+- Red UNLK
+ - The associated landing gear is:
+ - In transit, or
+ - Not locked in the selected position, after the normal extension/retraction delay.
+ In this case, the L/G GEAR NOT LOCKED DOWN or L/G GEAR NOT LOCKED UP alerts are displayed.
+
+### Body Accumulator Pressure Gauge
+
+The BODY ACCU pressure indication shows the lowest BLG brake accumulator pressure.
+
+- GREEN ARC:
+ - The green arc represents the normal pressure zone.
+ - The green arc ranges from 4872 to 5000 PSI.
+- AMBER ARC:
+ - The amber arc represents the low pressure zone.
+ - The amber arc ranges from 0 to 3840 PSI.
+
+When the indication is in the amber arc, the flight crew should press the ACCUS REINFLATE pb to
+reinflate the BLG brake accumulators before towing/push-back and before engine start.
+
+### Autobrake Selector
+
+The flight crew arms/disarms a landing AUTO BRK mode, by rotating the AUTO BRK mode selector to the appropriate position.
+
+Each mode corresponds to a deceleration target.
+
+If all the AUTO BRK arming conditions are satisfied, the selector is electrically maintained in the selected position.
+
+If an arming condition is lost or the RTO mode is armed, the selector automatically returns to the DISARM position. For
+BTV, in the case of a reversion to BRK HI, the selector stays on BTV position even if the FMA displays BRK HI.
+Simultaneously, the light of the RTO pb or ACTIV light go off.
+
+Note: A landing AUTO BRK mode can be armed in flight, and on ground.
+
+### RTO (Rejected Takeoff) Button
+
+When the RTO pb is pressed, the RTO mode arms and the RTO ARM light goes on provided all the arming conditions are
+satisfied. In addition, RTO in blue is displayed on PFD FMA left column.
+
+When the RTO pb is pressed again, the RTO mode disarms.
+
+Note: The RTO mode can be armed only on ground.
+
+### Anti Skid Switch
+
+- ON:
+ - The A-SKID is available if normal braking or alternate braking with A-SKID are available.
+- OFF:
+ - The A-SKID is off. As a consequence, emergency braking is active.
+ - A-SKID sw OFF is to be used only in case of total brake efficiency loss.
+ - Note: A-SKID sw OFF does not cut off NWS
+
+### Gear Lever
+
+In UP position, the landing gear retraction is selected.
+
+In DOWN position, the landing gear extension is selected.
+
+The red arrow goes on and flash when the aircraft is in a landing configuration below 750 ft radio altimeter and one or
+more landing gears are not downlocked.
+
+The red arrow logic is independent from the position of the landing gear lever.
+
+The L/G GEAR NOT DOWN alert displays simultaneously.
+
+
+### Clock
+
+The A380X has a built-in independent clock which sends time data to several systems. It has redundant electrical
+supply and is also directly connected to the aircraft's Hot Battery Bus.
+
+Functions:
+
+- "UTC" (GMT) time in hours, minutes, and seconds on the center counter.
+- Elapsed time (ET) (from engine startup) in hours and minutes on the lower counter.
+- Chronometer (CHR), which measures a time interval (from the pushing of the CHRONO button) in minutes and seconds.
+- Date display.
+
+#### UTC (GMT) counter
+
+24-hour format clock.
+
+#### Elapsed Time (ET) counter
+
+Tracks flight time
+
+#### Chrono (CHR) counter
+
+Tracks elapsed time. Controlled by the CHR pushbutton.
+
+The first push starts the CHR counter and the second push stops the CHR counter but keeps the display at its last indication.
+
+#### Reset (RST)
+
+Resets the chrono counter when the counter is running.
+
+#### ET selector
+
+- RUN:
+ - ET counter starts
+- STP:
+ - ET counter stops
+- RST:
+ - ET counter is blanked. The selector returns to its STP position when the selector is released.
+
+Note: When alternating between "RUN" and "STP" a cumulative elapsed time can be measured.
+
+#### DATE/SET button
+
+- Not pushed:
+ - Time mode. The date display disappears.
+- Pushed:
+ - Date mode. The UTC time display is replaced by the date (day month year).
+
+#### Operating Mode Selector
+
+The operating mode selector has three positions.
+Two of these positions correspond to operating modes
+
+GPS mode: The time and date synchronize with the GPS.
+INT mode: The clock internally computes the time and date.
+SET: The flight crew manually sets the time and date.
+
+!!! warning ""
+ The operating mode selector is currently not functional in the A380X.
+
+---
+
+[Back to Main Instrument Panel and Glareshield](../overviews/main-glare.md){ .md-button }
+
+---
+
+
diff --git a/docs/pilots-corner/a380x/a380x-briefing/flight-deck/main-panel/efis-reconf.md b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/main-panel/efis-reconf.md
new file mode 100644
index 000000000..daf1ca405
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/main-panel/efis-reconf.md
@@ -0,0 +1,95 @@
+---
+title: Display Unit Control Panel
+description: The A380 Flight Deck Display Unit Control Panel
+ description.
+---
+
+# Display Unit Control Panel
+
+---
+
+[Back to Main Instrument Panel and Glareshield](../overviews/main-glare.md){ .md-button }
+
+---
+
+{loading=lazy width=50%}
+
+## Description
+
+The Display Unit Control Panel (DU CP) is located on the main instrument panel on each side for the Captain and the
+First Officer. The DU CP is used to configure the displays for the Primary Flight Display (PFD), the Navigation Display
+(ND), the Onboard Information Terminal (OIT), and the Multi-Function Display (MFD).
+
+## Usage
+
+### PFD DU KNOB
+When turned, turns on or off the PFD screen, and adjusts the brightness of
+the PFD display unit.
+
+### ND DU KNOB
+
+- Inner knob:
+ - Turns on or off the ND
+ - Adjusts the brightness of the ND.
+- Outer knob:
+ - controls the brightness of both the weather radar image and the terrain display.
+
+### PFD/ND pb
+
+When pressed, exchanges the onside PFD and the ND, regardless of their default position.
+
+!!! warning ""
+ The PFD/ND pb is not functional in the A380X.
+
+### OIT knob
+
+When turned, turns on or off the OIT screen, and adjusts the brightness of the OIT display unit.
+
+!!! warning ""
+ The OIT knob is not functional in the A380X.
+
+### RECONF pb
+
+!!! warning ""
+ The RECONF pb is not functional in the A380X.
+
+In case of a display unit failure, the flight crew can manually reconfigure one of the remaining display units to
+recover the lost display.
+
+This manual reconfiguration is done using:
+
+- either the reconfiguration pushbutton (DU RECONF pb)
+- or, the KCCU function keys.
+
+This DU RECONF pb is active only if there is a failed on-side display unit. The EWD DU and SD DU can be reconfigured
+from both sides.
+
+The push-button acts on the following display unit, in the given order.
+
+For the CPT side:
+
+1. The MFD DU
+2. The ND DU, if the MFD DU is failed
+3. The PFD DU, if both the ND DU and MFD DU are failed.
+
+For the F/O side:
+
+1. The ND DU, if the PFD DU and ND DU are both operative
+2. The MFD DU, if either the PFD DU or the ND DU is failed
+
+
+ Overhead Panel
+
+
+ Glareshield and Main Panel
+
+
+ Stdby Compass and Eye Reference
+
+
+ Pedestal
+
+
+ Lateral Console
+ Lateral Console
+
+
+ Seats
+ Seats
+
+ Note: This is to favor the display of the PFD on either the PFD or ND DU.
+3. The PFD DU, if both the ND DU and MFD DU are failed.
+
+Note:
+
+- If the EWD DU, and/or SD DU fails, the EWD and/or the SD can be displayed on either side
+- The EWD (SD) cannot be displayed on both sides at the same time
+
+### MFD knob
+
+When turned, turns on or off the MFD screen, and adjusts the brightness of the MFD display unit.
+
+---
+
+[Back to Main Instrument Panel and Glareshield](../overviews/main-glare.md){ .md-button }
+
+---
diff --git a/docs/pilots-corner/a380x/a380x-briefing/flight-deck/main-panel/ewd.md b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/main-panel/ewd.md
new file mode 100644
index 000000000..7ab638343
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/main-panel/ewd.md
@@ -0,0 +1,37 @@
+---
+title: Engine Warning Display (EWD)
+description: The A380 Flight Deck Engine Warning Display (EWD) description.
+---
+
+# Engine Warning Display (EWD)
+
+---
+
+[Back to Main Instrument Panel and Glareshield](../overviews/main-glare.md){ .md-button }
+
+---
+
+{loading=lazy width=50%}
+
+## Description
+
+The Engine Warning Display (EWD) is located on the main instrument panel in the center.
+
+It consists of two parts:
+
+- The upper part displays the status of the engines.
+- The lower part displays the status of the Electronic Centralized Aircraft Monitoring (ECAM)
+
+!!! note ""
+ We will provide a detailed description of the EWD in the future.
+
+
+
+
+
+---
+
+[Back to Main Instrument Panel and Glareshield](../overviews/main-glare.md){ .md-button }
+
+---
+
diff --git a/docs/pilots-corner/a380x/a380x-briefing/flight-deck/main-panel/gravity-gear.md b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/main-panel/gravity-gear.md
new file mode 100644
index 000000000..a5cff1527
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/main-panel/gravity-gear.md
@@ -0,0 +1,59 @@
+---
+title: Gravity Gear Panel
+description: The A380 Flight Deck Gravity Gear Panel description.
+---
+
+# Gravity Gear Panel
+
+---
+
+[Back to Main Instrument Panel and Glareshield](../overviews/main-glare.md){ .md-button }
+
+---
+
+{loading=lazy width=50%}
+
+## Description
+
+
+
+## Usage
+
+### L/G GRVTY sw
+
+The L/G GRVTY panel has two switches that are linked together for simultaneous operation, and protected by a cover.
+However, if the link is removed, the switches can be used separately, for maintenance purposes only.
+Each switch controls one FFCM.
+
+- OFF POSITION:
+ - When the L/G GRVTY sw is in the OFF position (normal position), the landing gear lever can be used for the normal
+ extension/retraction of the L/G.
+- DOWN POSITION:
+ - The extension of the landing gear by gravity is selected.
+ - The L/G GRVTY sw remains in the DOWN position until the flight crew selects another position.
+ - Note: Both switch-guards should be removed before the DOWN position is selected.
+- RESET POSITION:
+ - After a gravity landing gear extension, the RESET position is selected to restore the LGERS in the normal
+ configuration.
+ - When the L/G GRVTY sw is in the RESET position:
+ - The cut-out valves open
+ - The retraction actuators switch from the gravity mode to the normal mode.
+ - The L/G GRVTY sw should be back in the OFF position before the L/G lever can be used again to extend/retract
+ the L/G.
+
+ !!! warning ""
+ The L/G GRVTY sw can be reset either in flight or on ground.
+
+ However:
+
+ - A reset on ground of the L/G GRVTY sw must be performed only by maintenance as BLG doors will collide with
+ forward BLG wheels when closing (a specific prior maintenance action is needed before reset)
+ - A reset in flight must be restricted to training in absence of any gear system failure.
+
+---
+
+[Back to Main Instrument Panel and Glareshield](../overviews/main-glare.md){ .md-button }
+
+---
+
+
diff --git a/docs/pilots-corner/a380x/a380x-briefing/flight-deck/main-panel/isis.md b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/main-panel/isis.md
new file mode 100644
index 000000000..e2a22688f
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/main-panel/isis.md
@@ -0,0 +1,80 @@
+---
+title: Integrated Standby Instrument System (ISIS)
+description: The A380 Flight Deck Integrated Standby Instrument System (ISIS) description.
+---
+
+# Integrated Standby Instrument System (ISIS)
+
+---
+
+[Back to Main Instrument Panel and Glareshield](../overviews/main-glare.md){ .md-button }
+
+---
+
+{loading=lazy width=50%}
+
+
+# Description
+
+In addition to the PFD and ND, the standby instruments provide an independent source of information for:
+
+- Air data and inertial reference parameters
+- Navigation information.
+
+The standby instruments consist of:
+
+- Two Integrated Standby Instruments Systems (ISIS), located at the center of the instrument panel:
+ - One ISIS is used as the Standby Flight Display (SFD)
+ - The other ISIS is used as the Standby Navigation Display (SND).
+- One standby compass.
+
+Each ISIS can be either SFD, or SND. It is not possible to display two SFDs, or two SNDs at the same time. One SFD is
+always displayed.
+
+Both ISIS are connected to fully independent probes:
+
+- One standby pitot probe
+- Two standby static probes.
+
+!!! warning ""
+ Only one ISIS is available in the A380X at this time.
+ Also the ISIS is not fully functional at this time.
+
+## Usage
+
+### LS/DIR TO pb
+
+When pressed, the SFD displays the following LS indications:
+
+- Localizer scale and index
+- Glideslope scale and index
+- LS course.
+
+### MENU pb
+
+The content of the SFD menu is:
+
+- SET SPD BUG 1 and SET SPD BUG 2 to adjust and display the speed bugs,
+- SET ALT BUG to adjust and display an altimeter bug,
+- DISPLAY METERS to display aircraft altitude in meter, in addition to the altitude in ft,
+- SET BARO UNIT to switch from hPa to inHg,
+- DISPLAY NAV to display the aircraft position, heading and track,
+- DISPLAY FIX to modify and display a FIX.
+
+### SET/SEL KNOB
+
+- When pressed the displayed item is selected.
+- When turned the displayed selection is modified
+
+### Brightness pb
+
++/- to adjust the brightness of the display.
+
+
+
+---
+
+[Back to Main Instrument Panel and Glareshield](../overviews/main-glare.md){ .md-button }
+
+---
+
diff --git a/docs/pilots-corner/a380x/a380x-briefing/flight-deck/main-panel/mfd.md b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/main-panel/mfd.md
new file mode 100644
index 000000000..19e35c7de
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/main-panel/mfd.md
@@ -0,0 +1,44 @@
+---
+title: Multi-Function Display (MFD)
+description: The A380 Flight Deck Multi-Function Display (MFD) description.
+---
+
+# Multi-Function Display (MFD)
+
+---
+
+[Back to Main Instrument Panel and Glareshield](../overviews/main-glare.md){ .md-button }
+
+---
+
+{laoding=lazy width=50%}
+
+## Description
+
+There are two Multi Function Displays (MFDs). There is one for the Captain and one for the First Officer.
+
+The MFD displays:
+
+- The FMS pages (FMS)
+- The ATC Communication pages (ATCCOM)
+- The surveillance pages (SURV)
+- The FCU backup (FCU BKUP)
+
+The MFD is interactive: The flight crew can navigate through the pages, and can consult, enter or modify the data via
+the KCCU.
+
+!!! tip "MFD Interaction"
+ On the A380X users can use their normal mouse and keyboard to interact with the MFD.
+
+!!! note ""
+ We will provide a detailed description of the EWD in the future.
+
+
+---
+
+[Back to Main Instrument Panel and Glareshield](../overviews/main-glare.md){ .md-button }
+
+---
+
+
+
diff --git a/docs/pilots-corner/a380x/a380x-briefing/flight-deck/main-panel/nd.md b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/main-panel/nd.md
new file mode 100644
index 000000000..5449424cc
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/main-panel/nd.md
@@ -0,0 +1,73 @@
+---
+title: Navigation Display (ND)
+description: The A380 Flight Deck Navigation Display (ND) description.
+---
+
+# Navigation Display (ND)
+
+---
+
+[Back to Main Instrument Panel and Glareshield](../overviews/main-glare.md){ .md-button }
+
+---
+
+{loading=lazy width=50%}
+
+
+## Description
+
+The Navigation Display (ND) provides the flight crew with mid-term information of the status of the
+lateral navigation of the aircraft, according to:
+
+- The flight plan
+- The navigation database data (waypoints, NAVAIDS, airports).
+
+The flight crew can change some items of the flight plan directly from the ND. For more information,
+
+The ND also displays:
+
+- The weather radar, the terrain, or information about traffic collision avoidance
+- The airport navigation function. For more information, Refer to Airport Navigation.
+
+For navigation, the flight crew can select one of the following ND modes:
+
+- ARC
+- PLAN
+- ROSE-NAV
+- ROSE-VOR
+- ROSE-LS.
+
+In PLAN mode, it is not possible to display additional information about the weather radar, the terrain,
+or traffic collision avoidance.
+
+The lower part of the ND display unit also provides the Vertical Display (VD) information.
+
+The Vertical Display (VD) provides the flight crew with an overview of the vertical position of the
+aircraft. The VD is a secondary means of navigation, that helps increase the flight crew's awareness of
+the aircraft vertical location.
+
+The VD is only available in ARC and ROSE-NAV modes.
+
+When the flight crew sets the EFIS CP RANGE selector to ZOOM, the airport navigation function
+appears instead of the vertical display.
+
+The VD provides the current aircraft position, in relation to the:
+
+- Safety altitudes
+- Predicted trajectory
+- Weather information
+- Terrain information.
+
+The VD is below the Navigation Display (ND).
+
+Note: The VD update occurs after the computations of the FMS, and may last a few seconds longer than the ND update.
+
+!!! note ""
+ We will provide a detailed description of the ND in the future.
+
+---
+
+[Back to Main Instrument Panel and Glareshield](../overviews/main-glare.md){ .md-button }
+
+---
+
diff --git a/docs/pilots-corner/a380x/a380x-briefing/flight-deck/main-panel/oit.md b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/main-panel/oit.md
new file mode 100644
index 000000000..51b3094d0
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/main-panel/oit.md
@@ -0,0 +1,27 @@
+---
+title: Onboard Information Terminal (OIT)
+description: The A380 Flight Deck Onboard Information Terminal (OIT) description.
+---
+
+# Onboard Information Terminal (OIT)
+
+---
+
+[Back to Main Instrument Panel and Glareshield](../overviews/main-glare.md){ .md-button }
+
+---
+
+
+
+
+## Description
+
+!!! warning "OIS and OIT"
+ THe OIS/OIT is not yet implemented in the A380X. We will provide a detailed description in the future.
+
+
+---
+
+[Back to Main Instrument Panel and Glareshield](../overviews/main-glare.md){ .md-button }
+
+---
\ No newline at end of file
diff --git a/docs/pilots-corner/a380x/a380x-briefing/flight-deck/main-panel/pfd.md b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/main-panel/pfd.md
new file mode 100644
index 000000000..6acde4c45
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/main-panel/pfd.md
@@ -0,0 +1,36 @@
+---
+title: Primary Flight Display (PFD)
+description: The A380 Flight Deck Primary Flight Display (PFD) description.
+---
+
+# Primary Flight Display (PFD)
+
+---
+
+[Back to Main Instrument Panel and Glareshield](../overviews/main-glare.md){ .md-button }
+
+---
+
+{loading=lazy width=50%}
+
+## Description
+
+The PFD mainly displays:
+
+- Primary flight parameters (bank angle, pitch angle, speed, Mach, heading, track, altitude, vertical speed, flight
+ path vector, velocity vector)
+- Selected and managed guidance targets (e.g. speed and altitude targets)
+- Armed and engaged modes, landing capability, AP, FD and A/THR engagement status on the Flight Mode Annunciator (FMA)
+- Flight Director guidance orders
+- Instrument approach information.
+
+!!! note ""
+ We will provide a detailed description of the PFD in the future.
+
+---
+
+[Back to Main Instrument Panel and Glareshield](../overviews/main-glare.md){ .md-button }
+
+---
+
+
diff --git a/docs/pilots-corner/a380x/a380x-briefing/flight-deck/main-panel/sd.md b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/main-panel/sd.md
new file mode 100644
index 000000000..3c583a609
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/main-panel/sd.md
@@ -0,0 +1,73 @@
+---
+title: System Display (SD)
+description: The A380 Flight Deck System Display (SD) description.
+---
+
+# System Display (SD)
+
+---
+
+[Back to Main Instrument Panel and Glareshield](../overviews/main-glare.md){ .md-button }
+
+---
+
+{loading=lazy width=50%}
+
+## Description
+
+The SD screen has three horizontal sections:
+
+- The top section provides the system display page, the STATUS page, or the STATUS MORE page. In normal operation, the
+ SD provides system display pages. The system display pages appear:
+ - Automatically, depending on the flight phase. For more details Refer to Normal Operation, or
+ - When manually-selected by the flight crew. For more details refer to [ECP](../pedestal/ecam-cp.md).
+- The middle section displays permanently-displayed data such as: External temperature, time,
+ aircraft weight, CG, and Fuel On Board (FOB).
+- The bottom section displays the mailbox (Refer to ECP).
+
+In addition, after an alert due to a system failure, the SD displays:
+
+- The applicable system display page, if any.
+- The aircraft STATUS page after the flight crew clears the alert from the EWD, if the STATUS page
+ is not empty.
+
+The System Display (SD) pages appear on the SD in the following decreasing order of priority:
+
+- SD page that the flight crew manually selects.
+- SD page that appears after an alert.
+- SD page that automatically appears when there is an advisory.
+- SD page that automatically appears depending on the flight phases.
+
+Available SD pages are:
+
+- ENG (Engine)
+- APU (Auxiliary Power Unit)
+- Bleed (Bleed Air
+- Cond (Air Conditioning)
+- Press (Cabin Pressure)
+- Door (Doors, Windows, Slides)
+- ElecAc (Electrical AC)
+- ElecDc (Electrical DC)
+- Fuel (Fuelsystem and Fuel Quantity)
+- Wheel (Wheels and Brakes)
+- Hyd (Hydraulic)
+- Fctl (Flight Controls)
+- Cb (Circuit Breakers)
+- Crz (Cruise)
+- Status (Status)
+- Video (Video)
+
+!!! note ""
+ We will provide a detailed description of the SD in the future.
+
+
+
+
+---
+
+[Back to Main Instrument Panel and Glareshield](../overviews/main-glare.md){ .md-button }
+
+---
+
+
+
diff --git a/docs/pilots-corner/a380x/a380x-briefing/flight-deck/main-panel/switching.md b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/main-panel/switching.md
new file mode 100644
index 000000000..ab6803485
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/main-panel/switching.md
@@ -0,0 +1,46 @@
+---
+title: Switching Panel
+description: The A380 Flight Deck Switching Panel description.
+---
+
+# Switching Panel
+
+---
+
+[Back to Main Instrument Panel and Glareshield](../overviews/main-glare.md){ .md-button }
+
+---
+
+{loading=lazy width=20%}
+
+## Description
+
+## Usage
+
+### ATT HDG SELECTOR
+
+* IR1 supplies data to captain PFD and captain ND.
+* IR2 supplies data to first officer PFD and first officer ND.
+* IR3 supplies data to captain PFD and captain ND.
+* IR3 supplies data to first officer PFD and first officer ND.
+
+### AIR DATA SELECTOR
+
+* ADR1 supplies data to captain PFD and captain ND.
+* ADR2 supplies data to first officer PFD and first officer ND.
+* ADR3 supplies data to captain PFD and captain ND.
+* ADR3 supplies data to first officer PFD and first officer ND.
+
+### FMS SELECTOR
+
+The FMS selector allows the flight crew to link all flight management interfaces on both sides with the
+FMC on Captain's side (when selecting BOTH ON 1), or the FMC on First Officer's side (when
+selecting BOTH ON 2).
+
+---
+
+[Back to Main Instrument Panel and Glareshield](../overviews/main-glare.md){ .md-button }
+
+---
+
+
diff --git a/docs/pilots-corner/a380x/a380x-briefing/flight-deck/main-panel/table-keyboard.md b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/main-panel/table-keyboard.md
new file mode 100644
index 000000000..488b617cb
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/main-panel/table-keyboard.md
@@ -0,0 +1,34 @@
+---
+title: Table and Keyboard
+description: The A380 Flight Deck Table and Keyboard description.
+---
+
+# Table and Keyboard
+
+---
+
+[Back to Main Instrument Panel and Glareshield](../overviews/main-glare.md){ .md-button }
+
+---
+
+{loading=lazy width=50%}
+{loading=lazy width=50%}
+
+## Description
+
+Captain and First Officer have a table and keyboard in front of them. The keyboard is used to interact with the OIS
+which is not yet implemented in the A380X.
+
+You can extend the table by clicking the click spot on the stowed table.
+You can then also fold back the table cover to access the keyboard.
+
+
+
+---
+
+[Back to Main Instrument Panel and Glareshield](../overviews/main-glare.md){ .md-button }
+
+---
+
+
+
diff --git a/docs/pilots-corner/a380x/a380x-briefing/flight-deck/overviews/compass.md b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/overviews/compass.md
new file mode 100644
index 000000000..0c309e661
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/overviews/compass.md
@@ -0,0 +1,41 @@
+---
+title: Compass and Eye Reference
+description: The A380 Flight Deck Compass and Eye Reference description.
+---
+
+# Compass and Eye Reference
+
+[Back to A380 Flight Deck Overview](../index.md){ .md-button }
+
+---
+
+## Overview
+
+
+
+## Standby Compass
+
+At the top, the standby compass provides magnetic heading information, allowing the pilots to navigate the aircraft
+manually in case the main electronic navigation systems fail. It is a traditional, analog compass, a reliable fallback
+that isn’t dependent on the aircraft’s electrical systems.
+
+## Eye Reference Indicator
+
+Below the compass, there’s the eye reference indicator, commonly referred to as the "ball."
+In the Airbus A380, the eye reference indicator consists of two red balls and one white ball in the middle. The pilot
+adjusts their seat so the white ball is hidden behind a red ball from their viewpoint. When properly aligned, this
+ensures that the pilot's eyes are at the correct height and position for an optimal view of both the outside environment
+and the cockpit instruments. This is especially critical for accurate visual reference during critical flight phases
+like takeoff and landing.
+
+## Visual Ice Indicator
+
+There are two visual ice indicators outside the aircraft, between the two windshields. They provide
+the flight crew with a visual backup to the ice detection system.
+
+The visual ice indicators can be illuminated by the flight crew using the "ICE IND & STBY COMPASS" switch on the
+overhead panel to check for ice accumulation on the windshield.
+
+---
+
+[Back to A380 Flight Deck Overview](../index.md){ .md-button }
diff --git a/docs/pilots-corner/a380x/a380x-briefing/flight-deck/overviews/lateral-console.md b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/overviews/lateral-console.md
new file mode 100644
index 000000000..dc47699c0
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/overviews/lateral-console.md
@@ -0,0 +1,118 @@
+---
+title: Lateral Consoles
+description: The A380 Flight Deck Lateral Consoles description.
+---
+
+# Lateral Consoles
+
+[Back to A380 Flight Deck Overview](../index.md){ .md-button }
+
+---
+
+## Overview
+
+
+
+## 1. OIT Domain Switch and Console & Floor Light Switch
+
+The OIT Domain switch is used to select the OIT domain for the OIT display (3).
+The avionics domain includes the applications that exchange data with the aircraft avionics:
+The flight operations domain includes the applications that support the flight crew on ground and in flight.
+These applications are part of the Airbus Electronic Flight Bag (EFB)
+
+!!! note "OIT in the A380X"
+At the time of writing this document, the OIT is not yet implemented in the A380X.
+Many of its features can be found in the flyPad EFB next to it.
+
+## 2. Electronic Flight Bag (EFB) - flyPad
+
+The flyPad is FlyByWire's version of an EFB which allows the user to manage the aircraft and the flight by providing
+access to aircraft settings, flight plans, ground services, performance calculations, navigational charts, online ATC
+frequencies and more.
+
+[flyPadOS 3 Documentation](/aircraft/common/flypados3/)
+
+## 3. OIT Display
+
+The Onboard Information System (OIS) provides tools for the flight crew to operate the aircraft.
+The OIS includes aircraft technical information, operating manuals, performance computation tools and mission management
+information. The main goal of the electronic documentation is to provide the flight crew with attractive documentation,
+that enables easy access to the necessary information related to operational needs.
+It replaces all the previously used paper documentation and charts.
+
+The OIS applications can be divided into:
+
+- Tools for flight operations support
+- Tools for cabin operations support
+- Tools for maintenance operations support
+- Services to the passengers, flight crew and cabin crew.
+
+The applications are hosted on two sub-networks or domains of the Network Server System (NSS):
+
+- The avionics domain (NSS AVNCS)
+- The flight operations domain (FLT OPS)
+
+!!! note "OIT in the A380X"
+At the time of writing this document, the OIT is not yet implemented in the A380X.
+Many of its features can be found in the flyPad EFB next to it.
+
+## 4. Sidestick
+
+The sidesticks are the pilots' primary control for manual flight.
+
+They are spring-loaded and automatically return to the neutral position. They do not receive any feedback from the
+control surfaces, as Airbus uses the fly-by-wire system without force feedback.
+
+When the autopilot is engaged, the sidsticks are locked in neutral position.
+
+If the pilot applies a force above a given threshold:
+
+- The sidesticks unlock
+- The autopilot disengages
+- The AUTO FLT AP OFF alert triggers
+
+Each sidestick has two controls:
+
+- The Radio Push To Talk switch
+- The sidestick pb, for autopilot disengagement, or sidestick priority
+
+At all times, only one flight crew member should fly the aircraft. However, if both flight crew members use their
+sidesticks simultaneously, their orders are algebraically added. The flight control laws limit the combined order to the
+equivalent of the full deflection of one sidestick. In this case, the two green SIDE STICK PRIORITY lights on the
+glareshield come on and "DUAL INPUT" voice message is activated.
+
+The sidestick pushbutton is used as priority takeover pushbutton:
+
+- The pilot can deactivate the other sidestick and take full control by pressing and keeping pressed his sidestick
+ pushbutton.
+- If the sidestick pushbutton is pressed for more than 30 seconds, the priority is latched and the other sidestick is
+ maintained deactivated.
+- At any time, a deactivated sidestick can be reactivated by momentarily pressing the sidestick pushbutton.
+
+## 5. Steering Handwheels (Tiller)
+
+The steering handwheels, also called tillers, which are interconnected, can steer the nose wheel up to 70° in either
+direction.
+
+After takeoff, the steering system centers the nose wheel automatically.
+
+The center button on either handwheel removes control of nose-wheel steering from the rudder pedals until the button is
+released.
+
+[//]: # (TODO)
+
+
+
+---
+
+[Back to A380 Pilot Briefing Overview](../index.md){ .md-button }
+
+
+
diff --git a/docs/pilots-corner/a380x/a380x-briefing/flight-deck/overviews/ovhd.md b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/overviews/ovhd.md
new file mode 100644
index 000000000..64ba327ec
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/overviews/ovhd.md
@@ -0,0 +1,140 @@
+---
+hide:
+ - toc
+ - navigation
+title: Overhead Panel
+description: The A380 Flight Deck Overhead Panel is providing an interactive graphical overview of the A380 flight deck
+ overhead panel and its systems.
+---
+
+# Overhead Panel
+
+[Back to A380 Flight Deck Overview](../index.md){ .md-button }
+
+
+
+
+
+
+
+
+ AFS
+
+
+ EFIS Captain
+
+
+ EFIS First Officer
+
+
+ Glareshield Side
+
+
+ Glareshield Side
+
+
+ Glareshield Underside
+
+
+
+
+
+ OIT Capt
+ OIT FO
+
+
+ Display Unit Control Panel Capt
+ Display Unit Control Panel FO
+
+
+ PFD Capt
+ PFD FO
+
+
+ ND Capt
+ ND FO
+
+
+ EWD
+
+
+ SD
+
+
+ MFD Capt
+ MFD FO
+
+
+ ISIS
+
+
+ Switching
+
+
+ L/G Gravity Gear Extention
+
+
+ Gear, Brake, Clock
+
+
+ Table and Keyboard Capt
+ Table and Keyboard FO
+
+
+
+
+---
+
+[Back to A380 Pilot Briefing Overview](../index.md){ .md-button }
+
+
diff --git a/docs/pilots-corner/a380x/a380x-briefing/flight-deck/overviews/pedestal.md b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/overviews/pedestal.md
new file mode 100644
index 000000000..7757e49f6
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/overviews/pedestal.md
@@ -0,0 +1,73 @@
+---
+hide:
+- toc
+- navigation
+title: Pedestal
+description: The A380 Flight Deck Pedestal page is providing an interactive graphical overview of the A380 flight deck
+ pedestal and its systems.
+
+---
+
+# Pedestal
+
+[Back to A380 Flight Deck Overview](../index.md){ .md-button }
+
+
+
+
+
+
+
+
+ Computer Resets
+
+
+ ELT
+
+
+ APU Fire
+
+
+ ADIRS
+
+
+ Flight Control
+
+
+ Fuel Jettison
+
+
+ Recorder & Evacuation
+
+
+ Emergency Electrical Power
+
+
+ Entertainment
+
+
+ Oxygen
+
+
+ Calls
+
+
+ Wiper
+
+
+
+
+ Maintenance Panel
+
+
+ Engine Fire
+
+
+ Hydraulic
+
+
+ Fuel
+
+
+ Electrical
+
+
+ Air
+
+
+ Anti Ice
+
+
+ Engine Start
+
+
+ Pressurization
+ Ditching
+
+
+ Exterior Lights
+
+
+ APU
+
+
+ Interior Lights
+
+
+
+ Signs
+
+
+
+
+ Resets
+
+
+ CVR
+
+
+ RMP
+
+
+ Flight Control
+
+
+ Cargo Air Conditioning
+
+
+ Cargo Smoke Detection
+
+
+ Ventilation
+
+
+ Engine Manual
+
+
+ Wiper
+
+
+ Reading Lights
+ Reading Lights
+
+
+
+
+
+---
+
+[Back to A380 Pilot Briefing Overview](../index.md){ .md-button }
+
+
+
diff --git a/docs/pilots-corner/a380x/a380x-briefing/flight-deck/overviews/seats.md b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/overviews/seats.md
new file mode 100644
index 000000000..df846b44c
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/overviews/seats.md
@@ -0,0 +1,58 @@
+---
+title: Seats
+description: The A380 Flight Deck Seats page is providing an interactive graphical overview of the A380 flight deck
+ seats and its features.
+---
+
+
+
+# Seats
+
+[Back to A380 Flight Deck Overview](../index.md){ .md-button }
+
+---
+
+## Overview
+
+The seats in the A380X are fully animated and can be moved forward and backward as well as sideways to allow for easy
+access to the cockpit.
+
+Also, the arm rests are moveable as can be seen in the animation below.
+
+## Seat Movement
+
+
+
+
+ Thrust Controls
+
+
+ KCCU Capt
+ KCCU FO
+
+
+ RMP Capt
+ RMP FO
+
+
+ Engine Master
+
+
+ ECAM Control
+
+
+ Speed Brake
+
+
+ Flap Lever
+
+
+ Surveillance Control
+
+
+ Cockpit Lighting
+ Cockpit Lighting
+
+
+ Parking Brake
+
+
+ Trim Panel
+
+
+ FDRS
+
+
+ Cockpit Door Panel
+
+
+ Printer
+
+
+
+_Click image to play animation._
+
+## Outer Arm Rest
+
+
+_Click image to play animation._
+
+## Inner Arm Rest
+
+
+_Click image to play animation._
+
+[Back to A380 Pilot Briefing Overview](../index.md){ .md-button }
diff --git a/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/adirs.md b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/adirs.md
new file mode 100644
index 000000000..624e888de
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/adirs.md
@@ -0,0 +1,55 @@
+---
+title: ADIRS Panel
+description: The A380 Flight Deck Air Data Inertial Reference System (ADIRS) Panel description.
+---
+
+# ADIRS Panel
+
+---
+
+[Back to Overhead](../overviews/ovhd.md){ .md-button }
+
+---
+
+{loading=lazy width=50%}
+
+[//]: # (TODO API Doc Link)
+
+## Description
+
+- The Air Data Inertial Reference System (ADIRS) computes the aircraft's position, speed, altitude, attitude, and air data for the displays, flight management guidance system, flight controls, engine controls, and other systems.
+
+- There are three identical air data/inertial reference units (ADIRUs) installed in the aircraft. Each ADIRU combines an air data reference (ADR) system with a laser gyro inertial reference (IR) system in a single unit. The ADR and IR systems in each ADIRU operate independently, meaning failure of one system will not cause a failure of the other.
+
+- The ADR provides barometric altitude, airspeed, Mach number, angle of attack, temperature, and overspeed warnings. If either ADR 1 or 2 fails, ADR 3 can be manually selected.
+
+- The IR provides attitude, flight path vector, heading, track, acceleration (speed trend), VSI, groundspeed, and aircraft position. The IR provides an inertial position input to the FMGCs for navigation computations. If either IR 1 or 2 fails, IR 3 can be manually selected.
+
+- ADIRU 1 and 2 supply their on side systems. ADIRU 3 is a hot spare.
+
+## Operation
+
+Normal operation:
+
+- The IR mode selector should be turned to NAV in the order of 1, 2, then 3.
+
+- ON BATT will then illuminate as a self-test at the start of alignment for a few seconds. If one or more of the ADIRU's are running on battery power, ON BATT will display constantly.
+
+- IR 1, 2 and 3, as well as ADR 1, 2 and 3 can be turned off using the corresponding push button.
+
+- If a fault develops with any of the IR's or ADR's a FAULT light will show on its corresponding push button.
+
+Abnormal operation:
+
+- The IR mode selector can be turned ATT. However, this only provides attitude and heading data, when entered by the flight crew. The navigation data is not available.
+
+- The heading data must be entered using the MCDU. This must be updated frequently, roughly every 10 minutes.
+
+- If the IR mode selector is set from NAV to ATT, or NAV to OFF during flight, NAV mode will be inoperable for the remainder of the flight.
+
+
+---
+
+[Back to Overhead](../overviews/ovhd.md){ .md-button }
+
+---
diff --git a/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/air.md b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/air.md
new file mode 100644
index 000000000..5fde09ffb
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/air.md
@@ -0,0 +1,152 @@
+---
+title: Air Panel
+description: The A380 Flight Deck Air Panel description.
+---
+
+# Air Panel
+
+---
+
+[Back to Overhead](../overviews/ovhd.md){ .md-button }
+
+---
+
+{loading=lazy}
+
+[//]: # (TODO API Doc Link)
+
+## Usage
+
+### AIR FLOW selector
+
+- NORM
+ - The airflow in the cabin/cockpit is automatically controlled.
+- HI
+ - The airflow in the cabin/cockpit is in manual mode.
+ - The pack airflow is 120% of the MAN default value.
+- LO
+ - The airflow in the cabin/cockpit is in manual mode.
+ - The pack airflow is 80% of the MAN default value.
+- MAN
+ - The airflow in the cabin/cockpit is in manual mode.
+ - The pack airflow is a default value.
+
+### PACK 1+2 pb
+
+- AUTO
+ - The pack is on and automatically controlled.
+- OFF
+ - The pack is off.
+- FAULT:
+ - When any pack valve position disagrees with the requested position.
+ - Associated with the following ECAM alert:
+ - AIR PACK 1(2) VLV 1(2) FAULT
+ - Or when the pack overheats.
+ - Associated with the following ECAM alert:
+ - AIR PACK 1(2) OVHT
+ - The FAULT light goes off when the overheat disappears.
+ - Or when the pack has failed.
+ - Associated with one of the following ECAM alerts:
+ - AIR PACK 1(2) FAULT
+ - AIR PACK 1+2 FAULT
+ - Or when there is a bleed leak on one pack.
+ - Associated with the following ECAM alert:
+ - AIR PACK 1(2) LEAK.
+
+### HOT AIR 1+2 pb
+
+- AUTO
+ - The hot air valve operates automatically.
+- OFF
+ - The hot air valve is closed.
+ - Associated with the following ECAM alert:
+ - COND HOT AIR 1(2) OFF
+- FAULT
+ - An overheat is detected in the applicable duct.
+ - Associated with the following ECAM alerts:
+ - COND DUCT OVHT
+ - AIR HOT AIR 1(2) LEAK
+ - The FAULT light goes off when the temperature decreases below 70°C, and the HOT AIR 1(2) pb is set to OFF.
+
+### RAM AIR pb
+
+- OFF
+ - Both RAM air inlets are closed.
+ - During a descent required by a loss of cabin pressurization, the RAM air inlets may
+ automatically open by system logic, even if the RAM AIR pb is not set to ON. In this
+ case, the outflow valves stay closed.
+- ON
+ - The RAM air inlets will open provided that the DITCHING pb on the CAB PRESS panel is not set to ON.
+ - When the differential pressure is lower than 1 PSI: Each outflow valve will open to approximately 20%.
+ - When the differential pressure is higher than 1 PSI: Each outflow valve will continue to operate normally.
+
+### CKPI selector
+
+- COLD...HOT
+ - The cockpit temperature is 24°C.
+ - Each gradation corresponds to 2°C.
+
+### CABIN selector
+
+- COLD...HOT
+ - The cabin temperature is 24°C.
+ - Each gradation corresponds to 2°C.
+
+- PURS SEL:
+ - Cabin temperature regulation is only controlled from the Flight Attendant Panel (FAP).
+
+### CABIN AIR EXTRACT pb-sw
+
+- Closed and dark:
+ - The cabin overboard valves are closed.
+- OVRD (Open and illuminated):
+ - The cabin overboard valves are open.
+
+### ENG 1+2+3+4 BLEED pb-sw
+
+- AUTO
+ - The engine bleed valve is automatically controlled.
+- OFF
+ - The engine bleed valve is closed.
+- FAULT
+ - The engine bleed position disagrees with the requested position, or
+ - An overpressure is detected, or
+ - An engine bleed overheat is detected.
+ - Associated with the following ECAM alerts:
+ - AIR ENG 1(2)(3)(4) BLEED FAULT
+ - A leak is detected in the applicable engine or inner (outer) wing.
+ - Associated with the following ECAM alerts:
+ - AIR L(R) INR WING LEAK
+ - AIR L(R) OUTR WING LEAK
+ - AIR ENG 1(4) BLEED LEAK
+ - AIR ENG 2(3) BLEED LEAK
+ - The FAULT light goes off when the flight crew selects OFF, and the applicable failure disappears.
+
+### APU BLEED pb-sw
+
+- OFF (dark)
+ - The APU bleed valve is closed.
+- ON (illuminated)
+ - The APU bleed valve is open when:
+ - The APU is running
+ - The aircraft altitude is below 22500 ft
+ - No APU leak is detected.
+- FAULT
+ - The ECAM detects an APU bleed leak
+ - Associated with the following ECAM alerts:
+ - AIR APU BLEED LEAK
+
+### X BLEED selector
+
+- AUTO
+ - The cross bleed valves are automatically controlled.
+- CLOSE
+ - The cross bleed valves are closed.
+- OPEN
+ - The cross bleed valves are open.
+
+---
+
+[Back to Overhead](../overviews/ovhd.md){ .md-button }
+
+---
\ No newline at end of file
diff --git a/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/anti-ice.md b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/anti-ice.md
new file mode 100644
index 000000000..713173da8
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/anti-ice.md
@@ -0,0 +1,76 @@
+---
+title: Anti Ice Panel
+description: The A380 Flight Deck Anti Ice Panel description.
+---
+
+# Anti Ice Panel
+
+---
+
+[Back to Overhead](../overviews/ovhd.md){ .md-button }
+
+---
+
+{loading=lazy}
+
+[//]: # (TODO)
+
+
+## Description
+
+The ice protection system allows unrestricted operation of the aircraft in icing conditions.
+
+This system protects the critical areas of the aircraft against ice, by using:
+
+- Hot bleed air for:
+ - Engine anti-ice
+ - Wing anti-ice
+- Electrical power for:
+ - Window heating
+ - Water/Waste drain masts heating
+ - Probe heating
+
+An ice detection system measures ice accretion via the anti-ice control system and provides this
+information to the flight crew.
+
+## Usage
+
+### WING anti-ice
+
+- OFF:
+ - Wing anti-ice is off.
+- ON:
+ - Wing anti-ice is on.
+ - The ECAM displays the WING A-ICE memo.
+ - On ground, the wing anti-ice valves will open for 30s. Wing anti-ice will then be
+ inhibited for 10 min, provided the aircraft is not in flight. If the flight crew does not
+ switch off the wing anti-ice, the ON light will remain on, even though the wing anti-ice
+ valves are closed. The wing anti-ice valves will then reopen after takeoff thrust
+ reduction.
+- FAULT:
+ - The wing anti-ice valve position disagrees with the requested position
+ - Or, the wing anti-ice valve is open, but a low pressure is detected.
+ - Amber light and ECAM caution message.
+ - The FAULT light goes off, when the affected wing anti-ice system is recovered, after
+ applying the appropriate procedure.
+ - If the system cannot be recovered, the FAULT light will
+ remain on for the remainder of the flight.
+
+### ENG 1+2+3+4
+
+- OFF:
+ - The anti-ice of the applicable engine is off.
+- ON:
+ - The anti-ice of the applicable engine is on.
+ - The ECAM displays the ENG A-ICE memo.
+- FAULT:
+ - Amber light and ECAM caution message, if the position of the anti-icing valve disagrees with
+ the corresponding pushbutton selection.
+
+---
+
+[Back to Overhead](../overviews/ovhd.md){ .md-button }
+
+---
diff --git a/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/apu-fire.md b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/apu-fire.md
new file mode 100644
index 000000000..62e2ca69b
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/apu-fire.md
@@ -0,0 +1,56 @@
+---
+title: APU Fire Panel
+description: The A380 Flight Deck APU Fire Panel description.
+---
+
+# APU Fire
+
+---
+
+[Back to Overhead](../overviews/ovhd.md){ .md-button }
+
+---
+
+{loading=lazy}
+
+## Description
+
+The APU compartment has a fire protection system, with:
+
+- A fire detection system
+- One extinguisher bottle that discharges extinguisher agent
+- An APU Fire panel, with assigned pushbuttons.
+ These pushbuttons can be used to isolate the APU from the other aircraft systems, and control fire extinguishing.
+- Visual and aural alerts.
+
+## Usage
+
+### APU FIRE pb
+
+- Nominal position: Dark
+ - No fire is detected.
+- Normal position: Illuminated
+ - Fire is detected in the APU compartment.
+ - Associated with the following ECAM warning: APU FIRE (Refer to Procedure)
+ - The light remains on, until the fire is extinguished, regardless of the position of the APU FIRE pb.
+- Guard open, Pushed out
+ - All associated systems are isolated from the APU
+ - The aural fire warning stops
+ - The fire extinguishing system is armed, the bottle is ready to discharge.
+
+### AGENT pb
+
+- OFF
+ - The fire extinguisher bottle is not armed.
+- SQUID
+ - The squibs of the fire extinguisher bottle are armed. The fire extinguisher bottle is ready to discharge
+ extinguisher agent.
+ - When pressed, the extinguisher bottle discharges and the SQUIB light goes off.
+- DISCH
+ - The fire extinguisher bottle discharges or is empty.
+
+---
+
+[Back to Overhead](../overviews/ovhd.md){ .md-button }
+
+---
diff --git a/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/apu.md b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/apu.md
new file mode 100644
index 000000000..f135bd7a3
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/apu.md
@@ -0,0 +1,59 @@
+---
+title: Auxiliary Power Unit (APU)
+description: The A380 Flight Deck Auxiliary Power Unit (APU) description.
+---
+
+# Auxiliary Power Unit
+
+---
+
+[Back to Overhead](../overviews/ovhd.md){ .md-button }
+
+---
+
+{loading=lazy width=20%}
+
+[//]: # (TODO)
+
+
+## Description
+
+The Auxiliary Power Unit (APU) is a small jet engine in the back of the aircraft which supplies the
+aircraft with pneumatic and electrical power.
+
+## Usage
+
+### MASTER SW
+
+Controls the APU operation and its start- and shutdown sequence.
+
+- OFF:
+ - The APU is off.
+ - When pressed, the APU system is powered and the air-intake flap opens.
+- ON:
+ - The APU is in operation.
+ - When pressed, the APU shutdown sequence begins.
+- FAULT Lt:
+ - The APU is failed, or
+ - An automatic shutdown has occurred, or
+ - An emergency shutdown has occurred.
+ - Associated with an ECAM alert.
+
+### START
+
+- OFF:
+ - The APU is not running.
+- ON:
+ - The APU is starting.
+ - When the APU reaches 95 % speed, the ON light goes off and the AVAIL light
+ comes on.
+- AVAIL Lt:
+ - The APU is started, and can provide electrical power, and/or bleed air.
+
+---
+
+[Back to Overhead](../overviews/ovhd.md){ .md-button }
+
+---
diff --git a/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/calls.md b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/calls.md
new file mode 100644
index 000000000..ba963ae51
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/calls.md
@@ -0,0 +1,77 @@
+---
+title: Calls Panel
+description: The A380 Flight Deck Calls Panel description.
+---
+
+# Calls Panel
+
+---
+
+[Back to Overhead](../index.md){ .md-button }
+
+---
+
+{loading=lazy width=70%}
+
+[//]: # (TODO API Doc Link)
+
+## Description
+
+The Calls Panel is used to alert the cabin crew of a call from the flight deck.
+
+!!! warning ""
+ The Calls Panel buttons are not yet functional in the A380X.
+
+## Usage
+
+### PURS pb
+When pressed:
+
+- A pink light, on the Purser Area Call Panel (ACP), comes on
+- The CAPTAIN CALL message appears on the Purser Attendant Indication Panel (AIP)
+- A high/low chime sounds through the associated cabin loudspeakers.
+
+### PILOT REST pb
+When pressed, a high/low chime sounds in the forward and the main crew rest.
+
+### DECK pb
+When pressed:
+
+- A pink light, on the upper/lower deck Area Call Panels (ACP), comes on
+- The CAPTAIN CALL message appears on the upper/lower deck Attendant Indication Panels (AIP)
+- A high/low chime sounds through the upper/lower deck cabin loudspeakers.
+
+### ALL pb
+When pressed:
+
+- A pink light, on all the ACP s in the cabin, comes on.
+- The CALL ALL CAPT message appears on all AIP s in the cabin.
+- A high/low chime sounds through the cabin loudspeakers.
+
+### MECH pb
+When pressed:
+
+- The COCKPIT CALL light on the maintenance nose gear panel comes on
+- An external horn sounds as long as the ground crew maintains the MECH pb pressed.
+
+### EMER pb-sw
+
+- Closed and dark:
+ - Neither the flight crew nor the cabin crew has made an EMER call.
+- Closed and illuminated (amber CALL):
+ - The cabin crew has made an EMER call.
+ - The CALL light flashes
+ - A buzzer sounds three times through the cockpit loudspeakers.
+ - The ATT transmission key flashes on all RMPs.
+- Open and illuminated (amber CALL, white ON):
+ - The ON and the CALL lights come on
+ - A pink light, on all the area call panels in the cabin, comes on
+ - The CALL PRIO CAPT message appears on all AIPs in the cabin
+ - Three successive high/low chimes sound through the cabin loudspeakers.
+
+---
+
+[Back to Overhead](../index.md){ .md-button }
+
+---
+
diff --git a/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/cargo-air.md b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/cargo-air.md
new file mode 100644
index 000000000..23851e0b1
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/cargo-air.md
@@ -0,0 +1,62 @@
+---
+title: Cargo Air Conditioning Panel
+description: The A380 Flight Deck Cargo Air Conditioning Panel description.
+---
+
+# Cargo Air Conditioning Panel
+
+---
+
+[Back to Overhead](../overviews/ovhd.md){ .md-button }
+
+---
+
+![Cargo Air Conditioning Panel](../../../assets/a380x-briefing/flight-deck/ovhd/cargo-air-cond-panel.png
+"Cargo Air Conditioning Panel"){loading=lazy width=70%}
+
+[//]: # (TODO API Doc Link)
+
+## Description
+
+The Cargo Air Conditioning Panel is used to control the air conditioning in the cargo compartments.
+
+## Usage
+
+### BULK(AFT)(FWD) ISOL VALVES PB-SW
+
+- AUTO
+ - The bulk (forward) cargo isolation valves are open.
+- OFF
+ - The bulk (forward) cargo isolation valves are closed, and the bulk (forward) cargo extraction fan stops.
+- FAULT
+ - The bulk (forward) cargo isolation valves are failed.
+ - Associated with the following ECAM alerts:
+ - BULK CARGO ISOL FAULT
+ - BULK CARGO VENT FAULT
+ - FWD CARGO ISOL FAULT
+ - FWD CARGO VENT FAULT
+ - AFT CARGO ISOL FAULT
+ - AFT CARGO VENT FAULT
+
+### TEMP REGUL SELECTOR
+
+- Used to select the desired temperature in the bulk cargo compartment.
+- The selected bulk cargo temperature is 15 °C.
+
+### HEATER pb-sw
+
+- AUTO
+ - Normal position: The bulk cargo heater automatically operates.
+- OFF
+ - The bulk cargo heater is off.
+- FAULT
+ - The bulk cargo heater is failed.
+ - Associated with the following ECAM cautions:
+ - COND BULK CARGO DUCT OVHT
+ - COND BULK CARGO HEAT FAULT
+
+---
+
+[Back to Overhead](../overviews/ovhd.md){ .md-button }
+
+---
diff --git a/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/cargo-smoke.md b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/cargo-smoke.md
new file mode 100644
index 000000000..6d50c3c32
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/cargo-smoke.md
@@ -0,0 +1,69 @@
+---
+title: Cargo Smoke Panel
+description: The A380 Flight Deck Cargo Smoke Panel description.
+---
+
+# Cargo Smoke Panel
+
+---
+
+[Back to Overhead](../overviews/ovhd.md){ .md-button }
+
+---
+
+{loading=lazy}
+
+[//]: # (TODO API Doc Link)
+
+## Description
+
+The Cargo Smoke Panel is used to detect smoke in the cargo compartments.
+
+## Usage
+
+### AGENT TO FWD/AFT pb
+
+- Guarded and dark:
+ - No smke is detected.
+- Smoke:
+ - Smoke is detected in the associated cargo compartment.
+ - Associated with the following ECAM warning:
+ - SMOKE FWD (AFT/BULK) CARGO SMOKE
+ - The SMOKE light remains on as long as smoke is detected.
+- Open and illuminated (red SMOKE):
+ - When pressed, the bottles discharge extinguisher agent in the associated cargo compartment.
+- Open and illuminated (amber DISCH):
+ - The fire extinguisher bottles discharge:
+- Open and illuminated (red SMOKE and amber DISCH):
+ - Smoke is detected in the associated cargo compartment, and the fire extinguisher bottles discharge, or
+ - The flight crew is pressing the CARGO SMOKE Panel Test pb.
+
+### BTL LIGHTS
+
+- OFF
+ - No bottle has discharged.
+- BTL1 or BTL2 lights on
+ - The fire extinguisher bottle has discharged.
+- BTL1 and BTL2 lights on
+ - The two fire extinguisher bottles have discharged, or
+ - The flight crew is pressing the CARGO SMOKE panel Test pb.
+
+### Test pb
+
+When pressed for at least three seconds, and until released, tests the operation of the cargo compartments fire
+detection and extinguishing system:
+
+- The continuous repetitive chime sounds
+- The MASTER WARN lights flash
+- The ECAM displays the cargo compartments SMOKE and AVNCS SMOKE warnings
+- The isolation valve of the ventilation system closes
+- All BTL lights come on
+- All DISCH lights AGENT pb come on
+- All SMOKE lights AGENT pb come on
+- The AVNCS SMOKE light on the VENT panel comes on.
+
+---
+
+[Back to Overhead](../overviews/ovhd.md){ .md-button }
+
+---
diff --git a/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/cvr.md b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/cvr.md
new file mode 100644
index 000000000..747ad2f88
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/cvr.md
@@ -0,0 +1,43 @@
+---
+title: Cockpit Voice Recorder (CVR) Panel
+description: The A380 Flight Deck Cockpit Voice Recorder (CVR) Panel description.
+---
+
+# Cockpit Voice Recorder (CVR) Panel
+
+---
+
+[Back to Overhead](../overviews/ovhd.md){ .md-button }
+
+---
+
+{loading=lazy}
+
+[//]: # (TODO API Doc Link)
+
+## Description
+
+The Cockpit Voice Recorder (CVR) Panel is used to control the cockpit voice recorder system.
+
+## Usage
+
+### Test pb
+
+- When pressed, tests the CVR.
+- If a boomset is connected to the BOOMSET jack, the flight crew will hear a low frequency signal.
+- If the test is not successful, the ECAM triggers a RECORDER CVR FAULT alert 5 s after the pushbutton is pressed.
+- To perform this test, the recorder must be on.
+
+### ERASE pb
+
+- When pressed for 2 seconds, the audio recording is erased, if the aircraft is on ground, and the parking brake is on.
+- Note: Data recording cannot be erased.
+- If a boomset is connected into the BOOMSET jack, the flight crew will hear a low frequency signal.
+- To erase audio recording, the recorder must be in use.
+
+---
+
+[Back to Overhead](../overviews/ovhd.md){ .md-button }
+
+---
+
diff --git a/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/elec.md b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/elec.md
new file mode 100644
index 000000000..231708668
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/elec.md
@@ -0,0 +1,152 @@
+---
+title: Electrical Panel
+description: The A380 Flight Deck Electrical Panel description.
+---
+
+# Electrical Panel
+
+---
+
+[Back to Overhead](../overviews/ovhd.md){ .md-button }
+
+---
+
+{loading=lazy}
+
+[//]: # (TODO API Doc Link)
+
+## Description
+
+The Electrical Panel is used to control the electrical systems of the aircraft.
+
+## Usage
+
+### BAT1(2)(APU)(ESS) pb-sw
+
+- AUTO:
+ - Normal position. Each TR automatically controls the charging of its associated Battery.
+- OFF:
+ - The battery is disconnected from the network.
+- FAULT:
+ - The charging or discharging current of the battery is abnormal.
+ - The battery automatically disconnects from its associated DC busbar.
+ - Associated with one of the following ECAM cautions:
+ - ELEC APU BAT FAULT
+ - ELEC BAT 1 (2)(ESS) FAULT .
+
+### BUS TIE pb-sw
+
+- AUTO:
+ - Normal position. The BUS TIE contactors automatically open or close, to reconfigure the electrical network, as necessary.
+- OFF:
+ - Some BUS TIE contactors open to segregate:
+ - The AC 1 and AC 2 busbars from the AC 3 and AC 4 busbars, and
+ - The DC 1 busbar from the DC 2 busbar.
+
+### PAX SYS pb-sw
+
+- ON:
+ - Normal Operation
+ - The IFE system, the passenger communication means and the passenger seats are electrically-supplied.
+- OFF:
+ - The IFE system, the passenger communication means and the seat power supply are manually shed.
+
+### ELMU pb-sw
+
+- AUTO:
+ - The automatic shedding function for high and low commercial loads is available.
+- OFF:
+ - The ELMU is off: The automatic shedding function for low commercial loads is not available. ENMU 1 and 2 can shed high loads, if necessary.
+- FAULT:
+ - The ELMU is failed: The automatic shedding function for low commercial loads is not available. ENMU 1 and 2 can shed high loads, if necessary.
+ - Associated with the following ECAM caution: ELEC LOAD MANAGT FAULT
+
+### AC ESS Feed pb-sw
+
+- AUTO and closed:
+ - Normal position:
+ - The AC 1 busbar supplies the AC ESS busbar.
+ - If the AC 1 busbar is lost, the AC 4 busbar will automatically supply the AC ESS busbar.
+- ALTN and open:
+ - The AC ESS FEED pb-sw is manually set to ALTN.
+ - The AC 4 busbar supplies the AC ESS busbar.
+- FAULT and closed:
+ - The AC ESS busbar is not supplied.
+ - Associated with the following ECAM caution: ELEC AC ESS BUS FAULT .
+
+### GALLEY pb-sw
+
+- AUTO:
+ - The galleys are supplied. Some galleys may be automatically shed, if necessary.
+- OFF:
+ - All galleys are manually shed.
+
+### COMMERCIAL 1(2) pb-sw
+
+- AUTO:
+ - All commercial loads of the main and upper left (right) cabin supply centers, are supplied.
+ - Some commercial loads may be automatically shed, if necessary.
+- OFF:
+ - All commercial loads of the main and upper left (right) cabin supply centers, are manually shed.
+ - The commercial loads are:
+ - All galleys
+ - The In-Flight Entertainment (IFE) system
+ - Ground servicing
+ - The cargo loading system
+ - Water and waste ice protection
+ - Lavatory and cabin lights
+ - The water heater
+ - The heated floor panels
+ - The trolley lift system.
+
+### EXT 1(2)(3)(4) pb
+
+- OFF:
+ - The external power unit is not connected to the aircraft.
+- AVAIL:
+ - The external power unit is connected to the aircraft, and is available to supply the electrical network.
+- ON:
+ - The external power unit supplies the electrical network.
+
+### APU GEN A(B) pb-sw
+
+- AUTO:
+ - The APU generator is available to supply the electrical network.
+- OFF:
+ - The APU GEN A(B) pb-sw is set to OFF with the APU running.
+- FAULT:
+ - The APU generator is disconnected from the electrical network.
+ - The applicable GGPCU disconnects the APU generator from the electrical network.
+ - Associated with the following ECAM alert: ELEC APU GEN A(B) FAULT
+
+### GEN 1(2)(3)(4) pb-sw
+
+- AUTO:
+ - The engine generator is connected to the electrical network.
+- OFF:
+ - The GEN 1(2)(3)(4) pb-sw is set to OFF with the engine running.
+- FAULT:
+ - The engine generator is disconnected from the electrical network.
+ - The applicable GGPCU disconnects the engine generator from the electrical network.
+ - Associated with the following ECAM alerts:ELEC GEN 1(2)(3)(4) FAULT.
+ - If the DRIVE pb-sw is set to DISC, the engine is disconnected from the engine generator, and the ENG pb-sw
+ automatically sets to FAULT.
+
+### DRIVE 1(2)(3)(4) pb
+
+- AUTO:
+ - The engine generator is driven by the engine.
+- DISC:
+ - The engine generator is disconnected from the engine. It can only be reconnected by maintenance action on ground. The reconnection requires the removal of the engine generator from the aircraft, and refurbishment of the engine generator in workshop.
+- FAULT:
+ - The engine generator must be disconnected from the engine.
+ - Associated with the following ECAM alerts:
+ - ELEC DRIVE 1(2)(3)(4) OIL OVHT
+ - ELEC DRIVE 1(2)(3)(4) OIL PRESS LO
+
+---
+
+[Back to Overhead](../overviews/ovhd.md){ .md-button }
+
+---
+
diff --git a/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/elt.md b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/elt.md
new file mode 100644
index 000000000..9182a7bdb
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/elt.md
@@ -0,0 +1,42 @@
+---
+title: Emergency Locator Transmitter (ELT) Panel
+description: The A380 Flight Deck Emergency Locator Transmitter (ELT) Panel description.
+---
+
+# Emergency Locator Transmitter (ELT) Panel
+
+---
+
+[Back to Overhead](../overviews/ovhd.md){ .md-button }
+
+---
+
+{loading=lazy}
+
+!!! warning ""
+ Currently not available or INOP in the FBW A380X for Microsoft Flight Simulator.
+
+## ELT light
+
+- OFF:
+ - The ELT is not transmitting.
+- ON:
+ - The ELT is either transmitting, or running a self-test.
+ - Note: If the ELT is transmitting when the aircraft is on the ground, the external horn sounds.
+
+## ELT selector
+- ARMED
+ - The Emergency Locator Transmitter (ELT) is armed, and automatically transmits the emergency
+ radio signal (i.e. 121.5 MHz, 243 MHz and 406 MHz), when the aircraft sustains an abnormal load factor.
+- ON
+ - The ELT is on, and transmits the emergency radio signal.
+- TEST/RESET
+ - The ELT stops transmitting, or
+ - An ELT self-test starts.
+
+---
+
+[Back to Overhead](../overviews/ovhd.md){ .md-button }
+
+---
+
diff --git a/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/emer-elec.md b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/emer-elec.md
new file mode 100644
index 000000000..0c2635b69
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/emer-elec.md
@@ -0,0 +1,47 @@
+---
+title: Emergency Electrical Panel
+description: The A380 Flight Deck Emergency Electrical Panel description.
+---
+
+# Emergency Electrical Panel
+
+---
+
+[Back to Overhead](../overviews/ovhd.md){ .md-button }
+
+---
+
+{loading=lazy}
+
+[//]: # (TODO API Doc Link)
+
+## Description
+
+The Emergency Electrical Panel is used to control the emergency electrical systems of the aircraft.
+
+## Usage
+
+### RAT MAN ON pb
+
+- CLOSED:
+ - Normal position
+ - The RAT is stowed, and the emergency generator does not supply the emergency network.
+ - In the event that all AC busbars are lost, the RAT automatically extends, and the emergency generator electrically-supplies the emergency network.
+- GUARD OPEN:
+ - When the pushbutton is pressed, the RAT extends, and the emergency generator connects to the emergency network.
+
+### EMER GEN FAULT LIGHT
+
+- OFF:
+ - The emergency generator is available, if necessary.
+- FAULT:
+ - The RAT is extending, or
+ - The RAT is extended, and the emergency generator does not supply the emergency network.
+
+
+---
+
+[Back to Overhead](../overviews/ovhd.md){ .md-button }
+
+---
+
diff --git a/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/eng-fire.md b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/eng-fire.md
new file mode 100644
index 000000000..fba0f2803
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/eng-fire.md
@@ -0,0 +1,72 @@
+---
+title: Engine Fire Panel
+description: The A380 Flight Deck Engine Fire Panel description.
+---
+
+# Engine Fire Panel
+
+---
+
+[Back to Overhead](../overviews/ovhd.md){ .md-button }
+
+---
+
+{loading=lazy}
+
+[//]: # (TODO API Doc Link)
+
+## Description
+
+The Engine Fire Panel is used to control the engine fire detection and extinguishing systems.
+
+## Usage
+
+### ENG 1(2)(3)(4) FIRE pb
+
+- IN, dark and closed:
+ - Normal position.
+ - No fire is detected.
+- IN, illuminated and closed:
+ - Fire is detected. The FIRE light of the ENG MASTER panel comes on, and also indicates the affected engine.
+ - Associated with the following ECAM warning: ENG 1(2)(3)(4) FIRE
+ - The light remains on, until the fire is extinguished, regardless of the position of the ENG FIRE pb.
+ - The flight crew is pressing the ENG FIRE Panel Test pb (Refer to Test pb).
+- OUT, illuminated and open (pressed):
+ - All associated systems are isolated from the engine.
+ - The aural fire warning stops.
+ - The fire extinguishing system is armed, the bottles are ready to discharge.
+
+### AGENT 1(2) pb
+
+- AUTO:
+ - Normal position.
+- SQUID:
+ - The squibs of the fire extinguisher bottles are armed.
+ - The fire extinguisher bottles are ready to discharge extinguisher agent.
+ - When pressed, the extinguisher bottles discharge and the SQUIB light goes off.
+- DISCH:
+ - The fire extinguisher bottle discharges or is empty.
+- SQUID & DISCH:
+ - The flight crew is pressing the ENG FIRE panel TEST pb (Refer to [TEST pb](#test-pb)).
+
+### TEST pb
+
+- Tests the engines, the APU and the main landing gear bay fire warnings.
+- When pressed for at least three seconds, and until released, tests the operation of the engine fire detection and
+ extinguishing system:
+ - The continuous repetitive chime sounds.
+ - The MASTER WARN lights flash.
+ - The ECAM displays ENG FIRE, APU FIRE and MLG FIRE warnings titles.
+ - All ENG FIRE pb come on red.
+ - The APU FIRE pb comes on red.
+ - All SQUIB lights of the AGENT pb come on.
+ - All DISCH lights of the AGENT pb come on.
+ - All FIRE lights on the ENG MASTER panel come on.
+
+
+---
+
+[Back to Overhead](../overviews/ovhd.md){ .md-button }
+
+---
+
diff --git a/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/eng-man.md b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/eng-man.md
new file mode 100644
index 000000000..215617254
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/eng-man.md
@@ -0,0 +1,61 @@
+---
+title: Engine Manual Start Panel
+description: The A380 Flight Deck Engine Manual Start Panel description.
+---
+
+# Engine Manual Start Panel
+
+---
+
+[Back to Overhead](../overviews/ovhd.md){ .md-button }
+
+---
+
+{loading=lazy}
+
+## Description
+
+The Engine Manual Start Panel is used to manually start the engines.
+
+## Usage
+
+### ENG MAN START pb-sw
+
+- ON:
+ - During a manual engine start, the start valve opens, provided ENG START selector is set to IGN/START or CRANK.
+ - *Note*: The start valve automatically closes when N2 reaches 58.4%.
+
+- OFF:
+ - The start valve closes, provided the ENG MASTER lever is set to OFF.
+ - This stops the engine start sequence.
+
+### ALTN MODE
+
+In ALTN mode, the N1 parameter is the primary engine parameter. However, the THR parameter remains displayed on the EWD.
+
+In ALTN mode, the TPR control loop is lost. The FADEC reverts to N1 control and uses the current N1 to control the
+engine thrust.
+
+The FADEC computes the N1 command as a function of the thrust levers position, speed/mach, altitude, and temperature.
+
+An automatic reversion to ALTN mode occurs when some engine parameters are not available. Automatic reversion to ALTN
+mode occurs when the P30 or the EGT engine parameter is failed.
+
+When the FADEC operates in ALTN mode:
+
+- The A/THR remains available
+- The thrust rating modes and the corresponding thrust rating limit are available, except flexible and derated takeoff
+ modes
+- The maximum available thrust at takeoff and go-around is reduced. The maximum available thrust is reduced by 4\%.
+- The soft go-around function is available.
+
+---
+
+[Back to Overhead](../overviews/ovhd.md){ .md-button }
+
+---
+
+
+
+
+
diff --git a/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/eng-start.md b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/eng-start.md
new file mode 100644
index 000000000..fc89d1ea6
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/eng-start.md
@@ -0,0 +1,35 @@
+---
+title: Engine Start Panel
+description: The A380 Flight Deck Engine Start Panel description.
+---
+
+# Engine Start Panel
+
+---
+
+[Back to Overhead](../overviews/ovhd.md){ .md-button }
+
+---
+
+![Engine Start Panel](../../../assets/a380x-briefing/flight-deck/ovhd/eng-start-panel.png
+"Engine Start Panel"){loading=lazy width=50%}
+
+[//]: # (TODO API Doc Link)
+
+## Usage
+
+### ENG MODE selector
+
+- NORM:
+ - Normal operation mode.
+- IGN START:
+ - Starts the automatic or manual start sequences when on ground.
+ - When engine is running, it initiates continues ignition.
+- CRANK:
+ - Used for a dry or a wet engine cranking.
+ !!! info ""
+ Currently not available or INOP in the FBW A380X for Microsoft Flight Simulator.
+
+
+
+
diff --git a/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/entertainment.md b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/entertainment.md
new file mode 100644
index 000000000..8ec00f6fc
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/entertainment.md
@@ -0,0 +1,73 @@
+---
+title: Entertainment Panel
+description: The A380 Flight Deck Entertainment Panel description.
+---
+
+# Entertainment Panel
+
+---
+
+[Back to Overhead](../overviews/ovhd.md){ .md-button }
+
+---
+
+{loading=lazy}
+
+[//]: # (TODO API Doc Link)
+
+## Description
+
+The Entertainment Panel is used to control the entertainment system on the A380.
+It also detects and alerts the crew of smoke in the entertainment system.
+
+## Usage
+
+### CWS pb-sw
+
+CWS stands for Cabin Work Station. The CWS pb-sw is used to control the power to the Cabin Work Station.
+
+- AUTO:
+ - Normal operation. No smoke is detected.
+- SMOKE:
+ - Smoke is detected in the Cabin Work Station (CWS).
+ - The SMOKE light remains on, as long as smoke is detected.
+- OFF:
+ - The CWS is electrically shutoff.
+- OFF and SMOKE:
+ - The CWS is electrically shutoff, and smoke is detected.
+
+### IFEC pb-sw
+
+IFEC stands for In-Flight Entertainment Center (IFEC). The IFEC pb-sw is used to control the power to the IFEC.
+
+- AUTO:
+ - Normal operation. No smoke is detected.
+- SMOKE:
+ - Smoke is detected in the IFEC.
+ - The ventilation extraction fan automatically stops, and electrical power to the IFE
+ System is cut off.
+ - The SMOKE light remains on, as long as smoke is detected.
+- OFF:
+ - The IFEC is electrically shutoff.
+- OFF and SMOKE:
+ - The IFEC is electrically shutoff, and smoke is detected.
+
+### NSS MASTER pb-sw
+
+NSS stands for Network Server System. The NSS MASTER pb-sw is used to control the power to the Network Server System.
+
+- AUTO:
+ - Normal operation. No smoke is detected.
+- SMOKE:
+ - Smoke is detected in the Network Server System (NSS).
+ - The SMOKE light remains on, as long as smoke is detected.
+- OFF:
+ - The NSS is electrically shutoff.
+- OFF and SMOKE:
+ - The NSS is electrically shutoff, and smoke is detected.
+
+---
+
+[Back to Overhead](../overviews/ovhd.md){ .md-button }
+
+---
diff --git a/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/ext-lt.md b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/ext-lt.md
new file mode 100644
index 000000000..c8bdd14f8
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/ext-lt.md
@@ -0,0 +1,167 @@
+---
+title: Exterior Lights Panel
+description: The A380 Flight Deck Exterior Lights Panel description.
+---
+
+# Exterior Lights Panel
+
+---
+
+[Back to Overhead](../overviews/ovhd.md){ .md-button }
+
+---
+
+{loading=lazy}
+
+[//]: # (TODO)
+
+
+## Description
+
+The Exterior Lighting of an Airbus A380 includes these lights:
+
+- The navigation lights
+- The landing lights
+- The runway turn off lights
+- The TO and TAXI lights
+- The logo lights
+- The anti collision lights
+- The wing and engine scan lights.
+
+### External lighting configuration:
+
+[//]: # (TODO)
+
+ The surfaces are actuated by one of the two hydraulic systems, or by an independent hydraulic
+ source (EHA/EBHA).
+ Note: The slats also have an electrical motor.
+
+The flight crew uses sidesticks and rudder pedals to fly the aircraft. The flight control computers
+interpret the pilot's inputs, and order flight control surface movement, as necessary.
+Additionally, a pitch trim switch and a rudder trim selector (with a rudder trim reset p/b) allow to trim the
+airplane when needed.
+
+## Usage
+
+### PRIM pb-sw
+
+- ON (not illuminated):
+ - The corresponding PRIM is on.
+- OFF:
+ - The corresponding PRIM is off.
+ - Switching it OFF then on resets it.
+- FAULT:
+ - The corresponding PRIM is failed.
+ - Associated with the following ECAM alert:F/CTL PRIM 1(2)(3) FAULT:
+ - The FAULT light goes off when the flight crew selects OFF.
+ - The FAULT light flashes during the PRIM safety test.
+
+### SEC pb-sw
+
+- ON (not illuminated):
+ - The corresponding SEC is on.
+- OFF:
+ - The corresponding SEC is off.
+ - Switching it OFF then on resets it.
+- FAULT:
+ - The corresponding SEC is failed.
+ - Associated with the following ECAM alert: F/CTL SEC 1(2)(3) FAULT.
+ - The FAULT light goes off when the flight crew selects OFF.
+ - The FAULT light flashes during the SEC safety test.
+
+
+
+---
+
+[Back to Overhead](../overviews/ovhd.md){ .md-button }
+
+---
diff --git a/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/fuel-jettision.md b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/fuel-jettision.md
new file mode 100644
index 000000000..17ee0276d
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/fuel-jettision.md
@@ -0,0 +1,71 @@
+---
+title: Fuel Jettison Panel
+description: The A380 Flight Deck Fuel Jettison Panel description.
+---
+
+# Fuel Jettison Panel
+
+---
+
+[Back to Overhead](../overviews/ovhd.md){ .md-button }
+
+---
+
+{loading=lazy}
+
+[//]: # (TODO API Doc Link)
+
+## Description
+
+The A380's fuel jettison system is designed to quickly reduce the aircraft's weight in emergency situations, allowing it
+to safely return to land. It enables the controlled discharge of fuel from specific tanks through nozzles located on the
+wings. This process helps achieve the aircraft's maximum landing weight when required, enhancing safety during emergency
+landings. The system is carefully monitored and controlled to ensure efficient and safe operation during use.
+
+!!! warning ""
+ This is not available in the A380X yet.
+
+## Usage
+
+### JETTISON ARM pb-sw
+
+- OFF (not illuminated):
+ - Jettison is not armed.
+- ON:
+ - Jettison is armed, and can be activated using the JETTISON ACTIVE pb-sw.
+
+### JETTISON ACTIVE pb-sw
+
+- OFF (not illuminated):
+ - Jettison is not active.
+- ON:
+ - Jettison is selected active. The jettison valves open, if the JETTISON ARM pb-sw is also ON.
+- ON and OPEN:
+ - The jettison valves are fully open.
+ - The ON and OPEN lights go off, when the FQMS automatically stops the jettison, or when the flight crew presses
+ the JETTISON ACTIVE pb-sw or JETTISON ARM pb-sw again.
+
+### EMER OUTR TK XFR pb-sw
+
+- OFF (not illuminated):
+ - The emergency outer tank transfer valves are closed.
+- ON:
+ - The emergency outer tank transfer valves are commanded open.
+ - Fuel transfers from the outer tanks into the outer feed tanks (FEED TK 1 or 4).
+ - The EMER OUTR TK XFR pb-sw is used in the case of:
+ - ENG 1(2)(3)(4) FAIL with damage
+ - FUEL NORM XFR FAULT
+ - FUEL NORM + ALTN XFR FAULT
+ - ELEC EMER CONFIG
+ - ELEC AC BUS 2 FAULT
+ - ELEC AC BUS 4 FAULT
+ - ELEC AC ESS BUS FAULT
+ - ELEC DC BUS 1 FAULT
+ - ELEC DC BUS 2 FAULT
+ - ELEC DC ESS BUS FAULT
+
+---
+
+[Back to Overhead](../overviews/ovhd.md){ .md-button }
+
+---
diff --git a/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/fuel.md b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/fuel.md
new file mode 100644
index 000000000..4534ee220
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/fuel.md
@@ -0,0 +1,215 @@
+---
+title: Fuel Panel
+description: The A380 Flight Deck Fuel Panel description.
+---
+
+# Fuel Panel
+
+---
+
+[Back to Overhead](../overviews/ovhd.md){ .md-button }
+
+---
+
+{loading=lazy}
+
+[//]: # (TODO API Doc Link)
+
+## Description
+
+The fuel system stores fuel, monitors the quantity and temperature of fuel in each tank, and controls
+fuel transfers to:
+
+- Supply fuel to the engines and to the Auxiliary Power Unit (APU)
+- Maintain the Center of Gravity (CG) within limits
+- Reduce structural loads
+- Control refueling and defueling
+- Enable fuel jettison, if necessary.
+
+## Usage
+
+### FEED TK 1(2)(3)(4) MAIN pb-sw
+
+- AUTO:
+ - The main pump is running.
+- OFF:
+ - The main pump is off.
+- FAULT:
+ - The main pump is running at low pressure or is failed.
+ - Associated with one of the following ECAM cautions:
+ - FUEL FEED TK 1(2)(3)(4) MAIN PMP FAULT
+ - FUEL FEED TK 1(2)(3)(4) MAIN + STBY PMP FAULT
+ - FUEL L(R) WING FEED PMPs FAULT.
+ - The FAULT light goes off, when the flight crew sets the FEED TK 1(2)(3)(4) MAIN pb-sw to OFF.
+
+### FEED TK 1(2)(3)(4) STBY pb-sw
+
+- AUTO:
+ - The standby pump runs automatically, when the associated main pump is failed, or is off.
+- OFF:
+ - The standby pump is off.
+- FAULT:
+ - The standby pump is running at low pressure or is failed.
+ - Associated with one of the following ECAM alerts:
+ - FUEL FEED TK 1(2)(3)(4) STBY PMP FAULT
+ - FUEL FEED TK 1(2)(3)(4) MAIN + STBY PMP FAULT
+ - FUEL L(R) WING FEED PMPs FAULT.
+ - The FAULT light goes off, when the flight crew sets the FEED TK 1(2)(3)(4) STBY pb-sw to OFF.
+
+### L(R) INR(MID)(OUTR) TK FWD pb-sw
+
+- AUTO:
+ - The transfer pump runs, if necessary:
+ - For an automatic fuel transfer from the inner, mid, or outer tanks, via the forward gallery, or
+ - For a manual transfer from the outer tanks, via the forward gallery (except if any outer tank pump has been switched off), or
+ - During jettison.
+- OFF:
+ - The transfer pump is off.
+- FAULT:
+ - Comes on:
+ - When the transfer pump is failed, or is abnormally on
+ - Associated with one of the following ECAM alerts:
+ - FUEL L(R) INR FWD PMP FAULT
+ - FUEL L(R) INR FWD+AFT PMPs FAULT
+ - FUEL L(R) MID FWD PMP FAULT
+ - FUEL L(R) MID FWD+AFT PMPs FAULT
+ - FUEL L(R) OUTR PMP FAULT.
+ - Or, when the transfer pump must be turned off to allow a manual gravity transfer:
+ - Associated with the following ECAM alert:
+ - FUEL OUTR TK XFR FAULT
+ - The FAULT light goes off, when the flight crew sets the L(R) INR(MID)(OUTR) TK FWD pb-sw to OFF.
+
+### L(R) MID(INR) TK AFT pb-sw
+
+- ON:
+ - The transfer pump runs, if necessary:
+ - For an automatic or manual fuel transfer from the inner, or mid tanks, via the aft gallery, or
+ - During jettison.
+- OFF:
+ - The transfer pump is off.
+- FAULT:
+ - The transfer pump is failed, or is abnormally on, or a low pressure is detected during a manual transfer.
+ - Associated with one of the following ECAM alerts:
+ - FUEL L(R) INR AFT PMP FAULT (Refer to procedure)
+ - FUEL L(R) INR FWD+AFT PMPs FAULT (Refer to procedure)
+ - FUEL L(R) MID AFT PMP FAULT (Refer to procedure)
+ - FUEL L(R) MID FWD+AFT PMPs FAULT (Refer to procedure)
+ - The FAULT light goes off, when the flight crew sets the L(R) MID(INR) TK AFT pb-sw to OFF.
+
+### TRIM TK L(R) pb-sw
+
+- ON:
+ - The transfer pump runs, if necessary:
+ - For an automatic or manual fuel transfer, or
+ - During jettison.
+- OFF:
+ - The transfer pump is off.
+- FAULT:
+ - Comes on:
+ - When the transfer pump is failed, or is abnormally on, or a low pressure is detected during a manual transfer
+ - Associated with one of the following ECAM alerts:
+ - FUEL TRIM TK L(R) PMP FAULT (Refer to procedure)
+ - FUEL TRIM TK L+R PMPs FAULT (Refer to procedure)
+ - FUEL TRIM TK XFR FAULT (Refer to procedure)
+ - Or, when the trim line is damaged and all trim tank transfers must be inhibited.
+ - Associated with the following ECAM alert:
+ - FUEL TRIM & APU LINES FAULT (Refer to procedure)
+ - The FAULT light goes off, when the flight crew sets the TRIM TK L(R) pb-sw to OFF.
+
+### INR(MID)(OUTR) TK XFR pb-sw
+
+- AUTO:
+ - Automatic fuel transfers from the inner (mid)(outer) tanks are available.
+ - For more information: Refer to Fuel Transfer Sequence
+- MAN:
+ - Fuel manually transfers from the inner (mid)(outer) tanks to the feed tanks.
+- FAULT:
+ - Comes on:
+ - When automatic fuel transfers from the affected tanks are no longer possible.
+ - Associated with one of the following ECAM alerts:
+ - FUEL MAN XFR PROCEDURE
+ - FUEL OUTR TK XFR FAULT
+ - Or, when a low level is detected in one or more of the feed tanks.
+ - Associated with the following ECAM alerts:
+ - FUEL FEED TK 1(2)(3)(4) LEVEL LO
+ - FUEL FEED TKs 1+2(3+4) LEVEL LO
+ - FUEL ALL FEED TKs LEVEL LO
+ - Or, (for the OUTR TK XFR pb-sw only) when a low fuel temperature is detected in the outer tanks.
+ - Associated with the following ECAM alert:
+ - FUEL TEMP LO
+ - The FAULT light goes off, when the flight crew sets the INR(MID)(OUTR) TK XFR pb-sw to MAN.
+
+### TRIM TK XFR pb-sw
+
+- AUTO:
+ - Automatic fuel transfers from the trim tank are available.
+ - For more information: Refer to Fuel Transfer Sequence
+- MAN:
+ - Fuel manually transfers from the trim tank to the inner tanks.
+- FAULT:
+ - Comes on:
+ - When an excessive aft CG is detected
+ - The Weight and Balance Backup Computer (WBBC) monitors the CG.
+ - Associated with the following ECAM alert:
+ - FUEL EXCESS AFT CG
+ - Or, when the CG has been previously detected at the forward limit, and the trim tank transfer can resume
+ - Associated with the following ECAM alert:
+ - FUEL CG AT FWD LIMIT
+ - Or, when a manual trim tank transfer is required
+ - Associated with the following ECAM alert:
+ - FUEL TRIM XFR FAULT
+ - FUEL MAN XFR PROCEDURE
+ - Or, when a low fuel temperature is detected in the trim tank
+ - Associated with the following ECAM alert:
+ - FUEL TEMP LO
+ - Or, when there is a low level of fuel in any feed tank, and there is still some fuel in the trim tank
+ - Associated with one of the following ECAM alerts:
+ - FUEL FEED TK 1(2)(3)(4) LEVEL LO
+ - FUEL FEED TKs 1+2 (3+4) LEVEL LO
+ - FUEL ALL FEED TKs LEVEL LO
+ - Or, when an overflow of the trim tank is detected.
+ - Associated with the following ECAM alert:
+ - FUEL TRIM TK OVERFLOW
+ - The FAULT light goes off, when the flight crew sets the TRIM TK XFR pb-sw to MAN.
+
+### TRIM TK FEED SELECTOR
+
+- AUTO:
+ - The trim tank transfers are automatic.
+- ISOL:
+ - The trim tank forward transfer stops and the trim tank transfer line is isolated.
+ - The following valves close to isolate the transfer line:
+ - The trim tank isolation valve
+ - The trim tank inlet valves
+ - The trim pipe isolation valves.
+- OPEN:
+ - The following valves open, to allow gravity transfer from the trim tank to the inner tanks:
+ - Trim tank inlet valves
+ - Trim pipe isolation valve connected to the aft gallery
+ - Inner tank aft inlet valves.
+
+### CROSSFEED 1(2)(3)(4) pb-sw
+
+- AUTO:
+ - All crossfeed valves automatically open:
+ - In electrical emergency configuration, while the slats are retracted, or
+ - If required for an automatic ground transfer.
+- ON and OPEN:
+ - The CROSSFEED 1(2)(3)(4) pb-sw is set to ON and the crossfeed valve is open.
+- ON:
+ - The CROSSFEED 1(2)(3)(4) pb-sw is set to ON and the crossfeed valve remains closed.
+ - Associated with the following ECAM alert:
+ - FUEL CROSSFEED VLV 1(2)(3)(4) FAULT (Refer to procedure).
+ - The OPEN/ON lights go off, when the flight crew deselects the CROSSFEED 1(2)(3)(4) pb-sw.
+- OPEN:
+ - The CROSSFEED 1(2)(3)(4) pb-sw is deselected and the crossfeed valve is open.
+ - If the crossfeed valve is abnormally open, this is associated with the following ECAM alert:
+ - FUEL CROSSFEED VLV 1(2)(3)(4) FAULT (Refer to procedure).
+ - If the crossfeed valve is automatically commanded open (automatic ground transfer or electrical emergency configuration), there is no associated alert.
+
+
+---
+
+[Back to Overhead](../overviews/ovhd.md){ .md-button }
+
+---
diff --git a/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/hyd.md b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/hyd.md
new file mode 100644
index 000000000..7c6ceb644
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/hyd.md
@@ -0,0 +1,120 @@
+---
+title: Hydraulic Panel
+description: The A380 Flight Deck Hydraulic Panel description.
+---
+
+# Hydraulic Panel
+
+---
+
+[Back to Overhead](../overviews/ovhd.md){ .md-button }
+
+---
+
+{loading=lazy}
+
+
+[//]: # (TODO API Doc Link)
+
+## Description
+
+The aircraft has two identical and independent hydraulic systems, referred to as GREEN
+and YELLOW. These two systems operate continuously, and power the flight controls, the
+landing gear systems, and the cargo doors. Hydraulic fluid cannot be transferred from one system to the other.
+
+In case one or both hydraulic systems fail, the following hydro-electrical backups are available:
+
+- For flight controls: The Electro-Hydrostatic Actuators (EHAs) and the Electrical Backup Hydraulic
+ Actuator (EBHA). For information on EHAs and EBHAs: Refer to EHA/EBHA description.
+- For braking and nose wheel steering: The Local Electro-Hydraulic Generation System (LEHGS).
+ For more information on the LEHGS: Refer to Braking System Architecture and Refer to Nose
+ Wheel Steering System.
+
+The normal operating pressure of each hydraulic system is 5 000 PSI.
+Each hydraulic system is monitored and controlled by its assigned Hydraulic System Monitoring Unit (HSMU).
+
+The hydraulic systems ensure:
+
+- Hydraulic generation
+- Hydraulic distribution.
+
+## Usage HYD Panel
+
+### ENG PMP pb-sw
+
+- AUTO:
+ - The pump pressurizes its hydraulic system, when the engine is running.
+- OFF:
+ The pump is depressurized.
+- FAULT:
+ - The pump is failed, or the pump must be depressurized because of a hydraulic system failure.
+ - Associated with one of the following ECAM alerts:
+ - HYD G(Y) ENG 1 or 2 (3 or 4) PMP A or B PRESS LO
+ - HYD G(Y) SYS TEMP HI
+ - HYD G(Y) SYS OVHT
+ - HYD G(Y) RSVR LEVEL LO
+ - HYD G(Y) RSVR AIR PRESS LO.
+ - The FAULT light goes off, when the flight crew selects OFF. However, in case of an overheat, the FAULT light
+ will remain on, until the overheat disappears.
+
+### ENG PMP A+B DISC pb
+
+- ON
+ - Pumps A and B are connected to the engine accessory gearbox.
+- DISC
+ - Pumps A and B are disconnected from the engine accessory gearbox.
+ - Note: When disconnected, they cannot be reconnected by the flight crew. Maintenance action is required.
+- FAULT:
+ - The hydraulic system is failed, and cannot be recovered before the end of the flight.
+ - Therefore, the pumps must be disconnected from the engine accessory gearbox.
+ - Associated with one of the following ECAM alerts:
+ - HYD G(Y) RSVR LEVEL LO
+ - HYD G(Y) SYS TEMP HI (If pump depressurization failed)
+ - HYD G(Y) SYS OVHT.
+ - The FAULT light goes off, when the crew selects DISC.
+
+## Usage GND HYD Panel
+
+### ELEC PMP ON pb
+- OFF:
+ - The electric pump is not running.
+- ON:
+ The electric pump is running.
+ - Electric pumps may run:
+ - In automatic mode, or
+ - In manual mode, by pressing the ELEC PMP ON pb (for maintenance purpose only).
+ - Note:
+ - When the electric pump is already running in automatic mode, action on the ELEC PMP ON pb has no effect.
+ - When the electric pump is already running in manual mode, the automatic mode is disregarded (e.g. cargo door
+ actuation).
+
+!!! warning ""
+ When an electric pump is running in manual mode, the corresponding hydraulic system is fully pressurized.
+ Do not select manually any electric pump without clearance from the ground crew.ELEC PMP ON pb
+
+
+## ELEC PMP pb-sw
+The electric pumps are fully automatic and do not require any crew action, unless requested by the ECAM.
+
+- AUTO:
+ - The HSMU automatically controls the pump.
+- OFF:
+ - The pump is OFF and can neither be started by the HSMU, nor by the flight crew.
+- FAULT:
+ - The pump is failed, or the pump must be stopped because of a hydraulic system failure.
+ - Associated with one of the following ECAM alerts:
+ - HYD G(Y) ELEC PMP A (B) FAULT
+ - HYD G(Y) SYS TEMP HI (on ground, with engines OFF)
+ - HYD G(Y) SYS OVHT (on ground, with engines OFF)
+ - HYD G(Y) RSVR LEVEL LO (on ground, with engines OFF)
+ - HYD G(Y) RSVR AIR PRESS LO (on ground, with engines OFF) (Refer to procedure).
+ - The FAULT light goes off, when the flight crew selects OFF. However, in case of an overheat, the FAULT light will
+ remain on, until the overheat disappears.
+
+
+---
+
+[Back to Overhead](../overviews/ovhd.md){ .md-button }
+
+---
+
diff --git a/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/int-lt.md b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/int-lt.md
new file mode 100644
index 000000000..a0b342b55
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/int-lt.md
@@ -0,0 +1,59 @@
+---
+title: Internal Lights Panel
+description: The A380 Flight Deck Internal Lights Panel description.
+---
+
+# Internal Lights Panel
+
+---
+
+[Back to Overhead](../overviews/ovhd.md){ .md-button }
+
+---
+
+{loading=lazy}
+
+[//]: # (TODO)
+
+
+## Usage
+
+### STBY COMPASS
+
+- ICE IND & STBY COMPASS:
+ - The standby compass light and the eye reference light are on.
+- OFF:
+ - The standby compass light and the eye reference light are off.
+
+### STORM
+
+The storm function enables the flight crew to obtain maximum lighting in the cockpit, via the ambient
+lights and the main instrument panel lights.
+
+Ambient lights on the ceiling, and main instrument panel lights are at their
+maximum brightness.
+
+Overrides all the other lighting selections, regardless of the position of the
+AMBIENT LIGHT knob or the MAIN PNL FLOOD LT knob.
+
+!!! warning ""
+ Currently not available or INOP in the FBW A380X for Microsoft Flight Simulator.
+
+### ANN LT
+
+Brightness of cockpit annunciator lights. Either "bright" or "dim", or test.
+
+- TEST:
+ - Turns on all annunciator lights in the cockpit and LCDs in the FCU for the test.
+- DIM:
+ - Dims all annunciator lights.
+- BRT:
+ - Normal brightness for all annunciator lights.
+
+---
+
+[Back to Overhead](../overviews/ovhd.md){ .md-button }
+
+---
\ No newline at end of file
diff --git a/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/maintenance.md b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/maintenance.md
new file mode 100644
index 000000000..e02736180
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/maintenance.md
@@ -0,0 +1,199 @@
+---
+title: Maintenance Panel
+description: The A380 Flight Deck Maintenance Panel description.
+---
+
+# Maintenance Panel
+
+---
+
+[Back to Overhead](../overviews/ovhd.md){ .md-button }
+
+---
+
+![Maintenance Panel](../../../assets/a380x-briefing/flight-deck/ovhd/maintenance-panel.png
+"Maintenance Panel"){loading=lazy}
+
+[//]: # (TODO API Doc Link)
+
+## Description
+The Airbus A380 overhead maintenance panel provides a central interface for accessing various aircraft systems and
+performing maintenance checks. The panel is divided into sections, each dedicated to specific systems or functions.
+
+Here's a breakdown of the major systems covered on the overhead maintenance panel:
+
+### OXYGEN
+
+#### RESET pb
+Maintenance personnel uses this pushbutton to reset the control circuit, after the oxygen system has
+been used.
+
+- When pressed:
+ - Resets the oxygen system: The PAX SYS ON light (on the OXYGEN panel) goes off.
+ - When the reset is completed, ON goes off.
+ - The reset lasts approximately three seconds.
+- FAULT:
+ - The reset has failed.
+
+### GND HYD
+
+See [Hydraulic Panel](./hyd.md) for more information.
+
+### FUEL
+
+#### REFUEL pb-sw
+Refueling is usually initiated from the external REFUEL panel, that is under the aircraft belly fairing.
+However, refueling can also be initiated from the cockpit, via the REFUEL pb-sw. Cockpit refueling
+takes a priority over a refueling initiated from the external REFUEL panel.
+
+- OFF:
+ - Refueling from the cockpit is not activated.
+- ON:
+ - When pressed, refueling from the cockpit is enabled.
+- END/ON:
+ - Refueling was initiated from the cockpit and has completed, or has aborted.
+ - If the FQMS aborts refueling, the light flashes.
+ - This is associated with the following ECAM alert: FUEL REFUEL FAULT
+
+#### AUTO GND XFR pb-sw
+
+- OFF:
+ - Automatic ground transfer is not active.
+ - Note: Only manual transfers can be initiated from the external REFUEL panel.
+- ON:
+ - When pressed, automatic ground transfer is activated to automatically obtain the ground CG target.
+ - Note: All transfer pumps must selected ON to perform an automatic ground transfer.
+- END/ON:
+ - Automatic ground transfer is completed, or is aborted by the FQMS.
+ - If the FQMS aborts the automatic ground transfer, the light flashes.
+ - This is associated with the following ECAM alert: FUEL AUTO GND XFR FAULT
+
+### BAT
+
+#### BAT 1/2/APU/ESS selector
+Selects the battery in order to display the voltage.
+
+#### BAT Display
+Displays the voltage of the selected battery.
+
+### ENG
+
+#### FADEC GND PWR pb
+
+- AUTO:
+ - The aircraft electrical network or the FADEC alternator automatically supplies the FADEC.
+- ON:
+ - On ground, the aircraft electrical network supplies the FADEC for 10 min, provided that:
+ - The ENG FIRE pb-sw is not pressed
+ - The FADEC is not self-powered.
+ - The FADEC is self-powered when N2 is above 12.5 %.
+
+### MAINT
+
+#### GND CONNECTION pb (INOP)
+
+- OFF:
+ - The maintenance personnel cannot connect a PMAT to the NSS AVNCS side via the plugs distributed throughout the
+ aircraft.
+- ON:
+ - The maintenance personnel pressed the MAINT GRND CONNECTION pb-sw .
+ - For maintenance purposes on ground, the maintenance personnel can connect a PMAT to the NSS AVNCS side via the
+ plugs distributed throughout the aircraft.
+
+### ELEC
+
+#### REMOTE C/B CTL pb
+
+- OFF:
+ - Normal operation.
+- ON:
+ - The remote C/B controller is ON, and can be displayed on the OIT.
+ - This controller is for maintenance purposes only.
+
+### NSS
+Network Server System (NSS) communication between the NSS CAB side and the FLT OPS side.
+
+#### NSS GATELINK pb-sw
+
+- ON:
+ - The Terminal Area Wireless LAN Unit (TWLU) is on.
+ - Communication between NSS and ground via gatelink is possible.
+- OFF:
+ - The Terminal Area Wireless LAN Unit (TWLU) is off.
+ - Communication between NSS and ground via gatelink is not possible.
+
+#### NSS CAB DATA TO NSS pb-sw
+
+- ON:
+ - Communication between NSS CAB side and FLT OPS is enabled.
+- OFF:
+ - Communication between NSS CAB side and FLT OPS is disabled.
+
+### AIR
+
+#### OVHT COND AIR FANS RESET pb
+
+In the case of overheat of a ventilation system fan, the affected fan automatically stops. The
+Maintenance personnel uses this pushbutton to restart the fan.
+
+- Not illuminated:
+ - No overheat is detected.
+- FAULT illuminated:
+ - One or several fans of the ventilation system failed due to overheat.
+ - The FAULT light is not always associated with an ECAM alert, depending on the location and the number of the
+ affected fan(s). For example:
+ - If one primary cabin fan fails, the ECAM alert COND ONE PRIMARY CABIN FAN FAULT triggers
+ - If one cabin air extraction fan fails, no ECAM alert triggers. There is no operational impact.
+ - When pressed, resets the affected fan(s). When the reset is completed and successful, the FAULT light goes off.
+
+### VENT
+
+#### AVNCS GND COOLG pb
+
+- AUTO:
+ - Normal operation of the supplemental cooling system.
+- OFF:
+ - The supplemental cooling system is off.
+- FAULT:
+ - The supplemental cooling system is failed.
+ - Associated with the following ECAM alerts:
+ - VENT COOLG SYS 1(2) OVHT
+ - VENT COOLG SYS PROT FAULT
+
+### Miscellaneous
+
+#### SVCE INT OVRD pb
+
+- AUTO:
+ - The service interphone is automatically inhibited in flight.
+ - ON:
+ - If the service interphone remains abnormally inhibited on ground, the ground crew can manually activate it, by
+ pressing the SVCE INT OVRD pb.
+
+#### GND HF DATA LINK
+
+- AUTO:
+ - HF data communication is automatically inhibited on ground.
+- OVRD:
+ - For maintenance purposes, the ground crew can press the GND HF DATALINK pb-sw to activate HF data communication on
+ ground.
+
+#### CKPT DOOR LCKG SYS
+
+Maintenance personnel uses this pushbutton-switch to turn off the Cockpit Door Locking System
+(CDLS), in order to ease ground operations (e.g. servicing, cleaning, maintenance, etc).
+
+- AUTO:
+ - The CDLS is operative.
+ - When pressed, turns off the CDLS.
+- OFF:
+ - The CDLS is off, and the door is free to open from the cockpit or from the cabin.
+ - When pressed, turns on the CDLS.
+
+---
+
+[Back to Overhead](../overviews/ovhd.md){ .md-button }
+
+---
+
+
diff --git a/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/oxygen.md b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/oxygen.md
new file mode 100644
index 000000000..bbf4c3947
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/oxygen.md
@@ -0,0 +1,49 @@
+---
+title: Oxygen Panel
+description: The A380 Flight Deck Oxygen Panel description.
+---
+
+# Oxygen Panel
+
+---
+
+[Back to Overhead](../overviews/ovhd.md){ .md-button }
+
+---
+
+{loading=lazy}
+
+[//]: # (TODO API Doc Link)
+
+## Usage
+
+### CREW SUPPLY pb-sw
+The CREW SUPPLY pb-sw controls oxygen supply to the masks in the cockpit.
+
+- ON:
+ - The supply valve is open, and supplies oxygen to the masks.
+- OFF:
+ - The supply valve is closed.
+
+### MASK MAN ON pb
+The MASK MAN ON pb is a guarded pushbutton.
+
+- GUARD CLOSED:
+ - Normal position.
+ - If the cabin altitude is above 13 800 ft, the masks drop automatically.
+- GUARD OPEN:
+ - When pushbutton is pressed the masks will drop.
+
+### PAX SYS ON LIGHT
+
+- SYS ON:
+ - Oxygen flows toward the passenger masks.
+ - The light remains on, until the RESET pb on the [OXYGEN maintenance panel](./maintenance.md#reset-pb) is pressed.
+
+---
+
+[Back to Overhead](../overviews/ovhd.md){ .md-button }
+
+---
+
+
diff --git a/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/press.md b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/press.md
new file mode 100644
index 000000000..e86065ae0
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/press.md
@@ -0,0 +1,89 @@
+---
+title: Pressurization Panel
+description: The A380 Flight Deck Pressurization Panel description.
+---
+
+# Pressurization Panel
+
+---
+
+[Back to Overhead](../overviews/ovhd.md){ .md-button }
+
+---
+{loading=lazy}
+{loading=lazy width=20% align=right}
+
+[//]: # (TODO API Doc Link)
+
+## Description
+
+The cabin pressurization system controls the pressurization of the cabin to allow crew and passengers
+to fly comfortably without the use of oxygen masks and the negative impact of too low pressure at high altitude.
+
+In normal operation, the pressurization system does not require any action by the flight crew.
+Cabin air pressure is automatically regulated to provide maximum passenger comfort.
+
+The cabin pressure regulation is performed via the automatic control of the outflow valves during all
+flight phases, from takeoff to landing.
+
+During cruise, the cabin altitude is regulated not to exceed 7500 ft.
+
+If necessary, the flight crew can manually operate the cabin air pressurization system by selecting
+the cabin altitude target and/or the cabin vertical speed.
+
+The CABIN PRESS panel is only used when pressurization has to be controlled in manual mode
+or in the event of a ditching.
+
+## Usage
+
+### CABIN ALT MODE pb-sw
+
+- AUTO:
+ - Cabin altitude is automatically regulated.
+- MAN:
+ - Cabin altitude is manually controlled.
+ - The cabin altitude target must be manually selected via the CABIN ALT TRGT selector.
+ - The cabin altitude target remains steady at the current value until the flight
+ crew manually selects a new cabin altitude target.
+
+### CABIN ALT TRGT selector
+
+When the CABIN ALT MODE pb-sw is set to MAN, the flight crew uses the selector to manually select
+the cabin altitude target.
+
+The selected cabin altitude target is displayed on the CAB PRESS and on the CRUISE page of the SD.
+
+The cabin altitude selection has a range of –2000 ft to 15000 ft.
+
+### CABIN V/S MODE pb-sw
+
+- AUTO:
+ - Cabin vertical speed is automatically regulated according to the flight profile and the cabin
+ altitude target.
+- MAN:
+ - Cabin pressure vertical speed is manually controlled.
+ - The vertical speed must be manually selected via the CABIN V/S TRGT selector.
+
+### CABIN V/S TRGT selector
+
+When the CABIN V/S MODE pb-sw is set to MAN, the flight crew uses the selector to manually select
+the cabin pressure vertical speed.
+
+The selected cabin pressure vertical speed is displayed on the CAB PRESS and on the CRUISE page of the
+system display.
+
+The cabin vertical speed selection has a range of –1500 ft/min to +2500 ft/min.
+
+### DITCHING guarded
+
+- Normal:
+ - The system functions normally.
+- ON:
+ - To prepare for ditching, the flight crew sets the DITCHING pb-sw on the CAB PRESS control panel
+ to ON. This closes all the valves located below the flotation line.
+
+---
+
+[Back to Overhead](../overviews/ovhd.md){ .md-button }
+
+---
\ No newline at end of file
diff --git a/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/rcdr-evac.md b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/rcdr-evac.md
new file mode 100644
index 000000000..f5cb6b75d
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/rcdr-evac.md
@@ -0,0 +1,70 @@
+---
+title: Recording and Evacuation Panel
+description: The A380 Flight Deck Recording and Evacuation Panel description.
+---
+
+# Recording and Evacuation Panel
+
+---
+
+[Back to Overhead](../overviews/ovhd.md){ .md-button }
+
+---
+
+{loading=lazy}
+
+[//]: # (TODO API Doc Link)
+
+## Usage RCDR
+
+### RCDR GND CTL PB
+
+-AUTO:
+ - All recorders operate automatically.
+- ON:
+ - The flight crew has manually started the recorders.
+ - The system automatically switches from ON to AUTO when the first engine is started.
+
+## Usage EVAC
+
+### COMMAND PB-SW
+
+- OFF and guarded:
+ - Normal Operation.
+ - Neither the Captain nor the Chief Purser order an evacuation.
+- EVAC (red) :
+ - The Chief Purser requests or orders an evacuation.
+ - If the CAPT and PURS sw is set to CAPT position, when the Chief Purser requests an evacuation:
+ - The EVAC light comes on
+ - A horn sounds in the cockpit during 3 s.
+ - If the CAPT and PURS sw is set to CAPT & PURS position, when the Chief Purser orders an evacuation:
+ - The EVAC light flashes
+ - A horn sounds in the cockpit
+ - The EVACUATION ALERT message appears on all Attendant Indication Panels (AIP) in the cabin
+ - EVAC CMD pb on FAPs, MINI FAPs and AAPs will be lit in the cabin
+ - The evacuation horn sounds in the cabin.
+- EVAC and ON:
+ - The Flight Crew orders an evacuation, regardless of the CAPT and PURS sw position (CAPT or CAPT & PURS).
+ - When pressed:
+ - The ON light and the EVAC light flashes
+ - The EVACUATION ALERT message appears on all Attendant Indication
+ Panels (AIP) in the cabin
+ - EVAC CMD pb on FAPs, MINI FAPs and AAPs will be lit in the cabin
+ - The evacuation horn sounds in the cabin.
+
+### HORN OFF pb
+When pressed, silences the evacuation horn in the cockpit.
+
+### CAPT AND PURS sw
+
+- CAPT:
+ - The Captain is the only person who can order an evacuation.
+- CAPT & PURS:
+ - The Captain and the Chief Purser can order an evacuation.
+
+---
+
+[Back to Overhead](../overviews/ovhd.md){ .md-button }
+
+---
+
diff --git a/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/reading.md b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/reading.md
new file mode 100644
index 000000000..514433e49
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/reading.md
@@ -0,0 +1,26 @@
+---
+title: Reading Lights Panels
+description: The A380 Flight Deck Reading Lights Panels description.
+---
+
+# Reading Lights Panels
+
+---
+
+[Back to Overhead](../overviews/ovhd.md){ .md-button }
+
+---
+{loading=lazy width=20%}
+
+[//]: # (TODO API Doc Link)
+
+## Description
+
+Each flight crew member has a reading light.
+
+---
+
+[Back to Overhead](../overviews/ovhd.md){ .md-button }
+
+---
+
diff --git a/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/resets.md b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/resets.md
new file mode 100644
index 000000000..d6a6a7075
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/resets.md
@@ -0,0 +1,62 @@
+---
+title: Reset Panels
+description: The A380 Flight Deck Reset Panels description.
+---
+
+# Reset Panels
+
+---
+
+[Back to Overhead](../overviews/ovhd.md){ .md-button }
+
+---
+
+=== block ""
+ {loading=lazy width=45% align=left}
+ {loading=lazy width=45% align=right}
+
+# Description
+
+!!! warning "Reset Panels"
+ The Reset Panels are currently not functional in the A380X.
+
+Some systems that operate abnormally, or that are detected failed by the ECAM, can be recovered by
+a computer reset.
+The flight crew can perform a computer reset by using the cockpit controls (e.g. pushbuttons), or the
+reset buttons.
+
+!!! warning ""
+ The flight crew can attempt a computer reset only when:
+
+ - An ECAM/OEB/TDU procedure requests to reset the system, or
+ - The List of Computer Reset Procedures permits to reset the system (Refer to List of
+ Computer Reset Procedures), or
+ - When approved by MCC in the case of specific TR failures in flight, which are
+ confirmed by the Airbus Real Time Health Monitoring system.
+
+The reset procedures give the conditions to perform a reset and also describes the precautions to take and the effects
+of the reset.
+
+Unless indicated differently in the reset procedure, to perform a system reset:
+
+- Set the normal control to OFF, or pull the reset button
+- Wait three seconds if a normal cockpit control is used, or one second if a reset button was pulled
+- Set the normal control to ON, or push the reset button.
+
+!!! warning ""
+ Several resets must not be performed at the same time, unless indicated in the applicable reset procedure.
+
+Note:
+
+1. In flight, before taking any action on the reset buttons, the PF and PM must crosscheck and verify that the
+reset button corresponds to the affected system
+2. The flight crew should report any in-flight reset to the maintenance.
+
+
+
+---
+
+[Back to Overhead](../overviews/ovhd.md){ .md-button }
+
+---
+
diff --git a/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/rmp.md b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/rmp.md
new file mode 100644
index 000000000..7551334c1
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/rmp.md
@@ -0,0 +1,27 @@
+---
+title: Radio Management Panel (RMP)
+description: The A380 Flight Deck Radio Management Panel (RMP) description.
+---
+
+# Radio Management Panel (RMP)
+
+---
+
+[Back to Overhead](../overviews/ovhd.md){ .md-button }
+
+---
+
+{loading=lazy}
+
+## Description
+The Radio Management Panels (RMP) are powerful systems managing the aircraft's communication and std-by navigation
+systems.
+
+Please refer to the [pedestal RMP](../pedestal/rmp.md) for more information.
+
+---
+
+[Back to Overhead](../overviews/ovhd.md){ .md-button }
+
+---
+
diff --git a/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/signs.md b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/signs.md
new file mode 100644
index 000000000..c24d99de4
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/signs.md
@@ -0,0 +1,80 @@
+---
+title: Signs Panel
+description: The A380 Flight Deck Signs Panel description.
+---
+
+# Signs Panel
+
+---
+
+[Back to Overhead](../overviews/ovhd.md){ .md-button }
+
+---
+
+
+
+[//]: # (TODO)
+
+
+## Usage
+
+### EMER EXIT LT
+
+- ON:
+ - Turn on Overhead Emergency Lights, EXIT signs and proximity marking system (floor light band).
+- OFF:
+ - Turn off Overhead Emergency Lights, EXIT signs and proximity marking (floor light band) system.
+- ARM:
+ - Emergency lighting and proximity marking turn on, when normal aircraft electrical power system fails or DC SHED ESS BUS fails or AC BUS 1 fails.
+ - Exit signs turn on when normal aircraft electrical power system fails or DC SHED ESS BUS fails.
+
+### EMER EXIT LT
+
+- OFF Lt:
+ - Amber light when the EMER EXIT LT selector is selected OFF.
+
+### SEAT BELTS
+
+- ON:
+ - Turn on FASTEN SEAT BELT and RETURN TO SEAT signs. A low tone chime is played in the passenger compartment.
+- AUTO:
+ - The FASTEN SEAT BELT signs and the RETURN TO SEAT signs come
+ on automatically in the cabin when engines are ON (depending on CIDS
+ programming), and:
+ - The slats are extended, or
+ - The main landing gear is extended.
+ An associated low tone chime sounds in the cabin.
+- OFF:
+ - Turn off FASTEN SEAT BELT and RETURN TO SEAT signs.
+
+!!! note ""
+ Chime is barely audible in the cockpit with the cockpit door closed.
+
+### NO MOBILE
+
+- ON:
+ - NO MOBILE and EXIT signs come on together with a low tone chime.
+- AUTO:
+ - The NO MOBILE signs come on automatically in the cabin, when:
+ - The aircraft is flying over a country where the use of mobile phone is not
+ authorized, or
+ - The aircraft altitude is approximately below 13 000 ft AGL.
+ - Depending on CIDS programming, an associated low tone chime
+ sounds in the cabin.
+ - The EXIT signs come on automatically in the cabin, when
+ - The slats are extended, or
+ - The landing gear is extended.
+- OFF:
+ - The NO MOBILE signs, and the EXIT signs go off in the cabin. Depending on the CIDS programming,
+ an associated low tone chime sounds in the cabin.
+
+!!! note ""
+ Chime is barely audible in the cockpit with the cockpit door closed.
+
+---
+
+[Back to Overhead](../overviews/ovhd.md){ .md-button }
+
+---
\ No newline at end of file
diff --git a/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/vent.md b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/vent.md
new file mode 100644
index 000000000..109d57f70
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/vent.md
@@ -0,0 +1,72 @@
+---
+title: Ventilation Panel
+description: The A380 Flight Deck Ventilation Panel description.
+---
+
+# Ventilation Panel
+
+---
+
+[Back to Overhead](../overviews/ovhd.md){ .md-button }
+
+---
+
+{loading=lazy}
+
+## Usage
+
+### AVNCS LIGHT
+
+- OFF:
+ - No smoke detected.
+- SMOKE (red):
+ - Smoke is detected in the ventilation duct of the main, upper, or aft avionics bay.
+ - Associated with the following ECAM warning:
+ - SMOKE L(R) MAIN AVNCS SMOKE (Refer to Procedure)
+ - SMOKE L(R) UPPER AVNCS SMOKE (Refer to Procedure)
+ - SMOKE AFT AVNCS SMOKE (Refer to Procedure)
+ - The flight crew is pressing the CARGO SMOKE Panel Test pb (Refer to Test pb)
+
+### AVNCS EXTRACT pb-sw
+
+- AUTO:
+ - The overboard and extract valves operate automatically, to ensure ventilation
+ of the avionic bays and the cockpit panels.
+- OVRD:
+ - The overboard and extract valves are in override configuration, provided that
+ the DITCHING pb-sw is not set to ON.
+- FAULT:
+ - A low ventilation flow is detected in any avionics compartment.
+ - Associated with the following ECAM alerts:
+ - VENT AVNCS EXTRACT FAULT
+ - SMOKE / FUMES.
+ - The FAULT light goes off, when the flight crew sets the AVNCS
+ EXTRACT pb-sw to OVRD.
+
+### CAB FANS pb-sw
+
+- ON:
+ - The cabin fans are on.
+- OFF:
+ - The cabin fans are off.
+
+### COOLG pb-sw
+
+- AUTO:
+ - The supplemental cooling system operates automatically.
+- OFF:
+ - The supplemental cooling system is off.
+- FAULT:
+ - The supplemental cooling system is failed.
+ - Associated with the following ECAM alerts:
+ - VENT COOLG SYS 1(2) OVHT (with protection).
+ - VENT COOLG SYS 1(2) OVHT (without protection).
+ - VENT COOLG SYS PROT FAULT.
+
+---
+
+[Back to Overhead](../overviews/ovhd.md){ .md-button }
+
+---
+
+
diff --git a/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/wiper.md b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/wiper.md
new file mode 100644
index 000000000..e895553a8
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/ovhd/wiper.md
@@ -0,0 +1,39 @@
+---
+title: Wiper Panel
+description: The A380 Flight Deck Wiper Panel description.
+---
+
+# Wiper Panel
+
+---
+
+[Back to Overhead](../overviews/ovhd.md){ .md-button }
+
+---
+
+{loading=lazy width=50%}
+
+[//]: # (TODO API Doc Link)
+
+## DESCRIPTION
+
+Each windshield is provided with two-speed electric wipers that are controlled by individual WIPER selectors.
+
+## Usage
+
+### WIPER SELECTOR:
+
+- OFF:
+ - Wiper is stowed out of view at the base of the window.
+- SLOW:
+ - Wiper operates at low speed.
+- FAST:
+ - Wiper operates at high speed.
+
+
+---
+
+[Back to Overhead](../overviews/ovhd.md){ .md-button }
+
+---
+
diff --git a/docs/pilots-corner/a380x/a380x-briefing/flight-deck/pedestal/cockpit-door.md b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/pedestal/cockpit-door.md
new file mode 100644
index 000000000..985352bfd
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/pedestal/cockpit-door.md
@@ -0,0 +1,52 @@
+---
+title: Cockpit Door Panel
+description: The A380 Flight Deck Cockpit Door Panel description.
+---
+
+# Cockpit Door Panel
+
+---
+
+[Back to Pedestal](../overviews/pedestal.md){ .md-button }
+
+---
+
+{loading=lazy width=50%}
+
+## Description
+
+The cockpit door automatically locks, as soon as it closes, when the Cockpit Door Locking System
+(CDLS) is powered.
+
+A Cockpit Door Lock Control Unit (CDLCU) electrically locks and unlocks the cockpit door.
+If the CDLS fails, the door unlocks but remains closed. The flight crew can lock the door by using the
+dead bolt.
+
+The flight crew uses the CKPT DOOR sw to either open the cockpit door, or to refuse access to the
+cockpit.
+
+At any time, the flight crew can use the door handle to manually open the cockpit door.
+
+## Usage
+
+- UNLOCK
+ - Unlocks the door, as long as the flight crew maintains the UNLOCK position.
+ - Note: When the flight crew releases the switch, it goes back to the NORM position.
+- NORM:
+ - The door is locked. If a crewmember enters a routine access code on the keypad, the door remains locked.
+ - Note: If a crewmember enters the emergency access code on the keypad, the door automatically unlocks for 5 s,
+ after a defined period of time.
+ - The Operator defines this period of time.
+- LOCK:
+ - Locks the door, and inhibits the keypad and the buzzer for a defined period of time.
+ - The Operator defines this period of time (between 5 min and 20 min).
+ - Note: When the flight crew releases the switch, it goes back to the NORM position.
+
+---
+
+[Back to Pedestal](../overviews/pedestal.md){ .md-button }
+
+---
+
+
+
diff --git a/docs/pilots-corner/a380x/a380x-briefing/flight-deck/pedestal/cockpit-lighting.md b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/pedestal/cockpit-lighting.md
new file mode 100644
index 000000000..bb71f8c40
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/pedestal/cockpit-lighting.md
@@ -0,0 +1,48 @@
+---
+title: Cockpit Lighting Panel
+description: The A380 Flight Deck Cockpit Lighting Panel description.
+---
+
+# Cockpit Lighting Panel
+
+[Back to Pedestal](../overviews/pedestal.md){ .md-button }
+
+---
+
+## Overview
+
+
+
+The Cockpit Lighting Panel has knobs to control various cockpit lights.
+The knob settings range from "OFF" to "BRT" (Bright), allowing pilots to set the lighting levels to their
+preference and the needs of the flight environment.
+
+## INTEG LT (Integral Lighting):
+
+This knob adjusts the backlighting intensity of the integrated instruments on the main instrument panel. This
+illumination helps pilots find and read switches, knobs, buttons, etc. during low-light conditions, such as night flying
+or when flying through clouds.
+
+## MAIN PNL FLOOD LT (Main Panel Flood Light):
+
+This control adjusts the flood lighting for the main panel, which provides a wash of light over the entire instrument
+panel. This general lighting is useful when the pilots need to see the entire panel without the need for backlighting on
+individual instruments.
+
+## PEDESTAL FLOOD LT (Pedestal Flood Light):
+
+This knob controls the flood lighting over the pedestal area, where the throttle and other control systems like the
+radio and flight management systems are located. This light allows for better visibility of the pedestal controls,
+especially important during critical flight operations.
+
+## AMBIENT LT (Ambient Light):
+
+The ambient light control adjusts the cabin's general lighting, usually providing a soft, indirect light to help the
+pilots adjust their eyes between looking at brightly lit instruments and the darker outside conditions. This helps to
+reduce eye strain and maintain night vision.
+
+
+---
+
+[Back to Pedestal](../overviews/pedestal.md){ .md-button }
+
diff --git a/docs/pilots-corner/a380x/a380x-briefing/flight-deck/pedestal/ecam-cp.md b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/pedestal/ecam-cp.md
new file mode 100644
index 000000000..9c8476063
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/pedestal/ecam-cp.md
@@ -0,0 +1,182 @@
+---
+title: ECAM Control Panel (ECP)
+description: The A380 Flight Deck ECAM Control Panel description.
+---
+
+# ECAM Control Panel (ECP)
+
+---
+
+[Back to Pedestal](../overviews/pedestal.md){ .md-button }
+
+---
+
+
+
+## Description
+
+The flight crew uses the ECAM Control Panel (ECP) to interface with the ECAM system. There is one
+ECP, and it is located on the central pedestal.
+
+The ECP provides keys that enables the flight crew to:
+
+- Navigate in a menu list, checklist, and/or procedure
+- Select an item in a menu list
+- Activate an item in a checklist and/or procedure
+- Activate the takeoff configuration test
+- Clear or cancel alerts
+- Access some system pages
+- Access normal checklists
+- Access not-sensed ABN PROC
+- Access STATUS page
+- Access STATUS MORE page
+- Access additional information system pages.
+ In addition, the ECP provides:
+- Rotary selectors to turn the EWD and SD on and off, and to adjust their brightness
+- Video display selection and control.
+
+!!! note ""
+ We will provide a detailed description of the SD in the future.
+
+## Usage
+
+### T.O CONFIG
+
+Simulates the application of takeoff power, by initiating a takeoff configuration
+test. A warning triggers, if any monitored system is not in the correct takeoff
+configuration.
+
+If the test is successful, the EWD displays a T.O CONFIG NORMAL message in
+the takeoff memo section.
+
+### C/L
+
+The EWD displays the normal checklist menu.
+
+### ✓
+
+When pressed, validates/devalidates the item that is surrounded by a blue box
+on the EWD.
+
+- Validates/devalidates a checklist item or procedure item, that is not detected
+ by the ECAM.
+- Selects one item of a checklist menu or procedure menu.
+
+### UP-ARROW
+
+The blue box moves up to the previous selectable item on the EWD screen.
+
+If pressed and held, the blue box moves up to the previous selectable item on the
+EWD screen, until released. The blue box cannot surround a grey line (except on
+the checklist menu).
+
+### DOWN-ARROW
+
+The blue box moves down to the next selectable item on the EWD screen.If
+pressed and held, the blue box moves down to the next selectable item on the
+EWD screen, until released.
+
+The blue box cannot surround a grey line (except on the checklist menu).
+
+### ABN PROC (INOP)
+
+The EWD displays the menu of not—sensed emergency or abnormal
+procedures. The ECAM cannot detect these procedures. Therefore, the flight
+crew manually requests their display, when necessary.
+
+### EMER CANC (INOP)
+
+The EMER CANC pb is a guarded pushbutton.
+
+- Cancels the audio indicator and turns off the MASTER WARN light
+ associated with an ECAM warning.
+ However, the associated procedure remains displayed on the EWD.
+ The audio indicator and MASTER WARN light are not canceled for the
+ remainder of the flight. If the ECAM warning is triggered a second time, the
+ audio indicator and MASTER WARN light appear again
+- Cancels the SC, the procedure on the EWD, and turns off the MASTER CAUT light, associated with an ECAM caution.
+ The ECAM caution is canceled for the remainder of the flight, even if the triggering conditions occur again
+- Cancels all the audio indicators and aural alerts. If the triggering conditions occur again, the audio indicators and
+ the aural alerts sound again
+- Deactivates any activated not-sensed procedure.
+- Note:
+ - All the alerts that are still active and canceled via the EMER CANC pb appear again on the EWD when the flight
+ crew presses the RCL pb on the ECP for more than three seconds.
+ - When pressed and if there is no alert that the flight crew can cancel, the EWD displays the EMERGENCY CANCEL ON
+ message.
+
+### System Pages Buttons
+
+- ENG (Engine)
+- APU (Auxiliary Power Unit)
+- Bleed (Bleed Air
+- Cond (Air Conditioning)
+- Press (Cabin Pressure)
+- Door (Doors, Windows, Slides)
+- ElecAc (Electrical AC)
+- ElecDc (Electrical DC)
+- Fuel (Fuelsystem and Fuel Quantity)
+- Wheel (Wheels and Brakes)
+- Hyd (Hydraulic)
+- Fctl (Flight Controls)
+- C/B (Circuit Breakers)
+- Crz (Cruise)
+- Status (Status)
+- Video (Video)
+
+### ALL
+
+When pressed and maintained, each system display page consecutively appears
+on the SD, for three seconds.
+
+When released, the last system display page remains, until a new display is either
+requested by the flight crew, or prompted by the ECAM.
+
+### CLEAR
+
+* On EWD or SD clears the lines indicated by the displayed vertical bar.
+* The CLEAR pb light comes on, when there is an alert to clear on EWD.
+* Note: The CLEAR pb does not cancel any aural alerts associated witha caution/warning, and does not deactivate a
+ Not-Sensed ABN PROC.
+
+### RCL LAST
+
+Cancels the last CLEAR pb action on an alert.
+
+### STS
+
+- The SD displays the STATUS page, if applicable.
+- The SD displays NORMAL, if the STATUS page is empty.
+- If the SD displays a STATUS page, the STS pb comes on.
+- If pressed again, when the SD displays the STATUS page, the page is cleared.
+
+### MORE
+
+The SD displays the MORE information page that is available when MORE
+appears on the system display pages and STATUS page.
+
+When the SD already displays the MORE information page, pressing again this
+pushbutton clears the MORE information page.
+
+### VIDEO knob (INOP))
+
+Displays the selected video on the applicable display unit.
+
+### EWD DU knob
+
+Turns the EWD on/off and adjusts its brightness.
+
+### SD DU knob
+
+Turns the SD on/off and adjusts its brightness.
+
+
+
+---
+
+[Back to Pedestal](../overviews/pedestal.md){ .md-button }
+
+---
+
+
+
diff --git a/docs/pilots-corner/a380x/a380x-briefing/flight-deck/pedestal/engine-master.md b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/pedestal/engine-master.md
new file mode 100644
index 000000000..c9fa82a89
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/pedestal/engine-master.md
@@ -0,0 +1,50 @@
+---
+title: Thrust and Thrust Reverser Control Levers
+description: The A380 Flight Deck Thrust and Thrust Reverser Control Levers description.
+---
+
+# Thrust and Thrust Reverser Control Levers
+
+---
+
+[Back to Pedestal](../overviews/pedestal.md){ .md-button }
+
+---
+
+
+
+## Usage
+
+### ENGINE 1(2)(3)(4) MASTER LEVER
+
+- When put to ON:
+ - The FADEC initiates an automatic engine start sequence, provided the ENG START selector is set to IGN START position,
+ or for more information, Refer to DSC-70-30 Automatic start sequence.
+ - Turns on the igniters and the fuel, if the ENG MAN START pb-sw is set to ON.
+
+- When put to OFF:
+ - Shutdowns the engine or aborts the start sequence. The FADEC resets.
+
+### ENGINE MASTER 1(2)(3)(4) LIGHT
+
+- FIRE (red):
+ - A fire is detected on the corresponding engine.
+ - Associated with the following ECAM alerts:
+ - ENG 1(2)(3)(4) FIRE (IN FLIGHT).
+ - ENG 1(2)(3)(4) FIRE (ON GROUND).
+
+- FAULT (amber):
+ - An automatic start sequence aborts, or
+ - The HP fuel valve position is abnormal.
+ - Associated with the ECAM alert ENG 1(2)(3)(4) HP FUEL VLV FAULT
+ - The overthrust protection is active and the FADEC automatically shut downs the engine.
+ - Associated with the ECAM alert ENG 1(2)(3)(4) CTL SYS FAULT
+
+---
+
+[Back to Pedestal](../overviews/pedestal.md){ .md-button }
+
+---
+
+
+
diff --git a/docs/pilots-corner/a380x/a380x-briefing/flight-deck/pedestal/fdrs.md b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/pedestal/fdrs.md
new file mode 100644
index 000000000..99b5ff511
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/pedestal/fdrs.md
@@ -0,0 +1,57 @@
+---
+title: Flight Data Recording System (FDRS)
+description: The A380 Flight Deck Flight Data Recording System (FDRS) description.
+---
+
+# Flight Data Recording System (FDRS)
+
+---
+
+[Back to Pedestal](../overviews/pedestal.md){ .md-button }
+
+---
+
+{loading=lazy width=100%}
+
+## Aircraft Conditioning Monitoring System (ACMS)
+
+The ACMS function provides a real-time monitoring of the aircraft parameters.
+
+The ACMS can generate system reports, that can be:
+
+- Printed: Automatically or via the ACMS TRIGGER pb on the pedestal (Refer to ACMS TRIGGER pb), and/or
+- Sent via ACARS or Gatelink, and/or
+- Stored on the Network Server System (NSS).
+
+Default ACMS reports and triggering conditions are available at aircraft delivery. The Operator can customize the
+content and the triggering conditions of the reports.
+
+### ACMS TRIGGER PB
+
+When pressed, prints a specific ACMS report and/or triggers the recording of some specific parameters.
+The Operator can customize the content and the triggering conditions of the ACMS reports.
+
+## Digital Flight Data Recorder (DFDR)
+
+The DFDR records flight parameters and data from various aircraft systems.
+
+The DFDR stores the data in a memory, that keeps all the recorded data for at least the last 25 h of operation.
+The recorder data remains protected, in the event of high G-loads, fire, water, or other damage. An underwater locator
+beacon is attached to the DFDR.
+
+### DFDR Location
+
+The flight crew uses the DFDR EVENT pb to point an event in the recorded data.
+
+### DFDR EVENT PB
+
+When pressed, it points an event in the recorded DFDR data.
+
+---
+
+[Back to Pedestal](../overviews/pedestal.md){ .md-button }
+
+---
+
+
+
diff --git a/docs/pilots-corner/a380x/a380x-briefing/flight-deck/pedestal/flap-lever.md b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/pedestal/flap-lever.md
new file mode 100644
index 000000000..2acea335d
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/pedestal/flap-lever.md
@@ -0,0 +1,42 @@
+---
+title: Flaps Lever Panel
+description: The A380 Flight Deck Flaps Lever Panel description.
+---
+
+# Flaps Lever Panel
+
+---
+
+[Back to Pedestal](../overviews/pedestal.md){ .md-button }
+
+---
+
+{loading=lazy width=50%}
+
+## Description
+
+The FLAPS lever controls the operation of the slats and flaps.
+
+The five lever positions correspond to the following surface positions :
+
+| Position | ECAM | Max Speed | Phase |
+|:--------:|:-----:|:----------:|:----------------------|
+| 0 | | | CRUISE |
+| 1 | 1/1+F | 263/222 kt | HOLD / TAKE OFF |
+| 2 | 2 | 220 kt | TAKE OFF / APPR |
+| 3 | 3 | 196 kt | TAKE OFF / LDG / APPR |
+| FULL | FULL | 182 kt | LDG |
+
+Before selecting any position, the pilot must pull the lever out of the detent. Stops at positions 1 and 3 prevent the
+pilot from calling for excessive flap/slat travel with a single action.
+
+Note: The pilot cannot select an intermediate lever position.
+
+---
+
+[Back to Pedestal](../overviews/pedestal.md){ .md-button }
+
+---
+
+
+
diff --git a/docs/pilots-corner/a380x/a380x-briefing/flight-deck/pedestal/kccu.md b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/pedestal/kccu.md
new file mode 100644
index 000000000..101fc5947
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/pedestal/kccu.md
@@ -0,0 +1,102 @@
+---
+title: Keyboard Cursor Control Unit (KCCU)
+description: The A380 Flight Deck Keyboard Cursor Control Unit (KCCU) description.
+---
+
+# Keyboard Cursor Control Unit (KCCU)
+
+---
+
+[Back to Pedestal](../overviews/pedestal.md){ .md-button }
+
+---
+
+{loading=lazy width=70%}
+
+
+## Description
+
+There are two Keyboard and Cursor Control Units (KCCUs) on the center pedestal. There is one for
+the Captain and one for the First Officer.
+
+The flight crew uses the KCCU to:
+
+- Navigate through the FMS pages on the MFD
+- Enter and modify data on the MFD FMS pages
+- Perform some flight plan revisions on the ND.
+
+The FMS dedicated KCCU controls are:
+
+- The FMS shortcut keys
+- The CLR INFO key
+- The ND key
+- The Navigation keys
+
+### FMS Shortcut Keys
+
+The FMS shortcut keys are used to access the FMS pages directly. The keys are labeled with the
+corresponding FMS page name.
+
+### DIR KEY
+When pressed:
+
+- Displays the DIRECT TO page on the MFD (Refer to Page)
+- Moves the cursor back to the MFD, if it was previously on another display.
+
+### PERF KEY
+When pressed:
+
+- Displays the ACTIVE/PERF page (on the panel that corresponds to the active flight phase) on the MFD (Refer to Page)
+- Moves the cursor back to the MFD, if it was previously on another display.
+
+### INIT KEY
+When pressed:
+
+- Displays the ACTIVE/INIT page on the MFD (Refer to Page)
+- Moves the cursor back to the MFD, if it was previously on another display.
+
+### NAVAID KEY
+When pressed:
+
+- Displays the POSITION/NAVAIDS page on the MFD (Refer to Page)
+- Moves the cursor back to the MFD, if it was previously on another display.
+
+### F-PLN KEY
+When pressed:
+
+- Displays the top of the flight plan on the ACTIVE/F-PLN page on the MFD (Refer to Page)
+- Moves the cursor back to the MFD, if it was previously on another display.
+
+### DEST KEY
+When pressed:
+
+- Displays the bottom of the primary flight plan on the ACTIVE/F-PLN page on the MFD (Refer to Page)
+- Moves the cursor back to the MFD, if it was previously on another display.
+
+### SEC INDEX KEY
+When pressed:
+
+- Displays the FMS SEC INDEX page on the MFD (Refer to Page)
+- Moves the cursor back to the MFD, if it was previously on another display.
+
+### CLR INFO KEY
+When pressed, clears the message that is currently displayed in the FMS Message Area.
+
+!!! info ""
+ Note: The CLR INFO key is also used to clear the ATCCOM, and SURV messages.
+
+### ND KEY (INOP)
+When pressed, moves the cursor to the ND.
+
+### Navigation Keys
+Moves the cursor to the display unit that is to the right, or to the left, of the one that is currently selected
+(if applicable).
+
+---
+
+[Back to Pedestal](../overviews/pedestal.md){ .md-button }
+
+---
+
+
+
diff --git a/docs/pilots-corner/a380x/a380x-briefing/flight-deck/pedestal/parking-brake.md b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/pedestal/parking-brake.md
new file mode 100644
index 000000000..364064b96
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/pedestal/parking-brake.md
@@ -0,0 +1,35 @@
+---
+title: Parking Brake Panel
+description: The A380 Flight Deck Parking Brake Panel description.
+---
+
+# Parking Brake Panel
+
+[Back to Pedestal](../overviews/pedestal.md){ .md-button }
+
+---
+
+## Overview
+
+
+
+## Parking Brake Handle
+
+To apply the Parking Brake, the flight crew pulls this handle and turns it clockwise.
+
+The message "PARK BRK" appears on the ECAM.
+
+To release the Parking Brake, the handle is turned counterclockwise.
+
+## Accus Reinflate
+
+If the parking brake hydraulic pressure is low and all the engines are shut down, the ACCUS
+REINFLATE pb can be used to activate the BLG LEHGS (Body L/G Local Electro-Hydraulic Generation Systems) and reinflate
+the BLG accumulators.
+
+With initial nominal BLG ACCUS filling, the parking brake is efficient for 12 h.
+
+---
+
+[Back to Pedestal](../overviews/pedestal.md){ .md-button }
+
diff --git a/docs/pilots-corner/a380x/a380x-briefing/flight-deck/pedestal/printer.md b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/pedestal/printer.md
new file mode 100644
index 000000000..314103801
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/pedestal/printer.md
@@ -0,0 +1,29 @@
+---
+title: Printer Panel
+description: The A380 Flight Deck Trim Panel page description.
+---
+
+# Printer Panel
+
+[Back to Pedestal](../overviews/pedestal.md){ .md-button }
+
+---
+
+## Overview
+
+{loading=lazy width=70%}
+
+## Description
+
+The following systems (if installed) can print reports on paper: ACARS, AIDS, FMGC, CFDIU and EVMU.
+
+After loading a new paper roll, the SLEW switch can be used to feed the paper forward.
+
+New paper can be added by opening the printer panel using the latch, which locks the door.
+
+!!! warning "Printer"
+ The printer is not yet implemented in the A380X.
+
+---
+
+[Back to Pedestal](../overviews/pedestal.md){ .md-button }
diff --git a/docs/pilots-corner/a380x/a380x-briefing/flight-deck/pedestal/rmp.md b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/pedestal/rmp.md
new file mode 100644
index 000000000..5fe596492
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/pedestal/rmp.md
@@ -0,0 +1,181 @@
+---
+title: Radio Management Panel (RMP)
+description: The A380 Flight Deck Radio Management (RMP) Panel description.
+---
+
+# Radio Management Panel (RMP)
+
+---
+
+[Back to Pedestal](../overviews/pedestal.md){ .md-button }
+
+---
+
+{loading=lazy width=70%}
+
+## Description
+
+The Radio Management Panels (RMP) are powerful systems managing the aircraft's communication and std-by navigation
+systems.
+
+We are planning a separate more in-depth guide for the RMPs, but here is a brief overview:
+
+There are three Radio Management Panels (RMPs) in the cockpit. The flight crew uses these RMPs to control the
+communication system.
+
+On each RMP, the flight crew can:
+
+- Select the communication mean(s) in transmission and/or reception mode(s)
+- Tune HF and VHF frequencies
+- Dial SATCOM Telephone (TEL) numbers
+- Select voice or data mode
+- Monitor and change data mode parameters
+- Enter the Squawk (SQWK) code
+- Select Standby Radio Navigation (STBY RAD NAV) and tune the NAVAIDs (only via RMP 1 and RMP 2).
+- Adjust the volume for voice communication and for NAVAID identification.
+
+The RMPs share selections and inputs to enable the flight crew to control all radio communication via any RMP.
+
+The RMPs share mainly the following data:
+
+- Active and standby frequencies
+- SATCOM channels and their status (e.g. logged on/off, connected)
+- Active function displays (e.g. Amplitude Modulation (AM))
+ However, it is possible to display a different page on each RMP.
+
+In normal operation:
+
+- The Captain controls communication via RMP 1
+- The First Officer controls communication via RMP 2
+- The third and the fourth occupants control communication via RMP 3.
+- RMPs 1 and 2 are directly connected to the VHF and HF transceivers.
+- RMP 1 transmits all commands to VHF 1, VHF 3 and HF 1.
+- RMP 2 transmits all commands to VHF 2 and HF 2.
+- RMP 3 transmits commands to RMP 1 or RMP 2, via the appropriate control connection.
+- RMP 1 and/or RMP 2 then send these commands to the appropriate transceivers.
+- All three RMPs are directly connected to the SATCOM system.
+
+## Usage
+
+!!! warning "RMP in the A380X"
+ The RMPs are not yet fully implemented in the A380X.
+
+ They can be used for the pilot <-> ATC communication with VHF and squawk code entry.
+ Currently no other features are available.
+
+ The RMPs are planned to be fully implemented in the future.
+
+ Below we will only describe the features that are currently available in the A380X.
+
+!!! warning "VATSIM vPilot"
+ Unfortunately, the VATSIM vPilot plugin does not support a correct usage of the RMPs yet.
+
+ Current known limitations when using vPilot:
+
+ - vPilot doest not support 3 RMPs, only 2.
+ - vPilot does not support the volume contol of the RMP's reception knobs.
+ - VHF1/COM1 works well, but VHF2/COM2 only works if you turn VHF3/COM3 receive on.
+
+### BRT/OFF KNOB
+
+!!! block ""
+ {loading=lazy align=right}
+
+ The flight crew uses the BRT/OFF knob to turn the RMP on or off, and to adjust the brightness of the
+ RMP screen.
+
+ The status indicator changes color to indicate the status of the RMP:
+
+ - Green: The RMP is off and in standby mode.
+ - Red:
+ - if the knob is pointing to OFF then the RMP is off and failed.
+ - if the knob is not pointing to OFF then the RMP is on and failed.
+ - no light: The RMP is on.
+
+### LINE SELECTION KEYS (LSK 1-3)
+
+!!! block ""
+ {loading=lazy align=right}
+
+ When pressed, select, validate, or activate the corresponding displays (e.g.
+ frequencies, functions, page titles).
+
+### ACTIVATION/DIALING KEYS (ADK 1-3)
+
+!!! block ""
+ {loading=lazy align=right}
+
+ When pressed, dial, select, validate, activate the corresponding displays (e.g.
+ frequencies, functions).
+
+### NUMERIC KEYS
+
+!!! block ""
+ {loading=lazy align=right}
+
+ When pressed, enter numeric values (e.g. frequencies, squawk codes).
+
+ CLR KEY:
+
+ - When pressed, clears the last digit entered.
+ - When pressed and held, clears all digits entered.
+
+### VHF TRANSMISSION KEYS (VHF 1(2)(3))
+
+!!! block ""
+ {loading=lazy align=right}
+
+ - Not illuminated:
+ - The associated communication mean (i.e. VHF 1(2)(3)) is not in transmission mode.
+ - When pressed, the transmission key turns on the transmission mode.
+ - Note: Only one communication mean at a time (internal and external communication) can be in transmission mode
+ on each RMP.
+ - Illuminated green:
+ - The associated communication mean (i.e. VHF 1(2)(3)) is in transmission mode.
+ - When pressed, the transmission key turns off the transmission mode.
+
+### VHF RECEPTION KNOBS (VHF 1(2)(3))
+
+!!! block ""
+ {loading=lazy align=right}
+
+ - Dark and in:
+ - The associated communication mean (i.e. VHF 1(2)(3)) is in reception mode.
+ - When pressed and released in the out position, the reception knob turns off the reception mode.
+ - Illuminated and out:
+ - The associated communication mean (i.e. VHF 1(2)(3)) is in reception mode.
+ - When pressed and released in the in position, the reception knob turns off the reception mode.
+ - When turned, the reception knob adjusts the volume of the headset.
+
+### RMP Page Access Keys
+
+!!! block ""
+ {loading=lazy align=right}
+
+ - The RMPs have multiple pages that can be selected by pressing the LSK 1-3 keys.
+
+### VHF Page
+
+{loading=lazy}
+
+1. Active frequency
+2. Loadspeaker symbol (indicating if reception is on or not)
+3. Transceiver Indicator (indicating if transmission is on or not)
+4. Standby frequency
+5. Clear the RMP message line
+6. RMP message line
+
+### Squawk Page
+
+The Squawk page is used to quickly enter a squawk code.
+
+The transponder system (XPDR) is otherwise managed in the [MFD](../main-panel/mfd.md) and not on the RMP.
+
+---
+
+[Back to Pedestal](../overviews/pedestal.md){ .md-button }
+
+---
+
+
+
diff --git a/docs/pilots-corner/a380x/a380x-briefing/flight-deck/pedestal/speed-brake.md b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/pedestal/speed-brake.md
new file mode 100644
index 000000000..bd0518b91
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/pedestal/speed-brake.md
@@ -0,0 +1,35 @@
+---
+title: Speed Brake Panel
+description: The A380 Flight Deck Speed Brake Panel description.
+---
+
+# Speed Brake Panel
+
+---
+
+[Back to Pedestal](../overviews/pedestal.md){ .md-button }
+
+---
+
+{loading=lazy width=70%}
+
+## Description
+
+- The speed brake surfaces can be controlled with the SPEED BRAKE lever.
+- To set speedbrake surfaces to a required position, the lever has to be pushed down and set to the required position.
+- A detent is provided at "½" SPEED BRAKE position.
+- The ground spoilers can be armed via the SPEED BRAKE lever. The lever must be pulled up when in the RET position to
+ achieve this.
+- When the lever is armed (or reverse thrust is selected), all spoiler's surfaces will automatically extend at landing,
+ or in case of a rejected takeoff.
+
+
+
+---
+
+[Back to Pedestal](../overviews/pedestal.md){ .md-button }
+
+---
+
+
+
diff --git a/docs/pilots-corner/a380x/a380x-briefing/flight-deck/pedestal/surveillance.md b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/pedestal/surveillance.md
new file mode 100644
index 000000000..c6bef2ed2
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/pedestal/surveillance.md
@@ -0,0 +1,82 @@
+---
+title: Surveillance Panel
+description: The A380 Flight Deck Surveillance Panel description.
+---
+
+# Surveillance Panel
+
+---
+
+[Back to Pedestal](../overviews/pedestal.md){ .md-button }
+
+---
+
+{loading=lazy width=70%}
+
+
+## Description
+
+The Surveillance (SURV) system includes the following systems that perform aircraft surveillance
+functions:
+
+- Terrain Awareness and Warning System (TAWS)
+- Weather Radar (WXR) system, including the predictive windshear detection
+- Traffic Collision Avoidance System (TCAS)
+- Transponder (XPDR).
+
+!!! warning ""
+ The Surveillance Panel is not yet fully implemented in the A380X.
+
+## Usage
+
+### WXR Controls (INOP)
+
+!!! warning "WXR in the A380X"
+ The Weather Radar (WXR) is inoperative in the A380X.
+
+### TA pb
+
+- Not illuminated:
+ - The TCAS is in TA/RA mode.
+- TA ONLY illuminated:
+ - The TCAS is in TA ONLY mode.
+ - Associated with the TA ONLY message on the ND.
+
+### ABV and BLW pb
+
+- Not illuminated:
+ - The TCAS display is in NORM mode.
+- ABV illuminated:
+ - The TCAS display is in ABV mode.
+- BLW illuminated:
+ - The TCAS display is in BLW mode.
+
+### G/S MODE pb
+
+- AUTO:
+ - The G/S mode (mode 5) is active.
+ - This is the default position.
+ - On the SURV/CONTROLS page of the MFD, the G/S MODE button is automatically set to ON.
+- OFF:
+ - The flight crew turns off the G/S mode (mode 5).
+ - Associated with the TAWS G/S MODE OFF MEMO.
+ - On the SURV/CONTROLS page of the MFD, the G/S MODE button is automatically set to OFF.
+
+### WXR/TAWS SYS 1(2) pb
+SYS 1 or 2 provides the WXR/TAWS functions.
+
+Note: On the SURV/STATUS & SWITCHING page of the MFD, the WXR/TAWS SYS 1(2) buttons are automatically updated.
+
+### XPDR/TCAS SYS 1(2) pb
+SYS 1 provides the XPDR/TCAS functions.
+
+Note: On the SURV/STATUS & SWITCHING page of the MFD, the XPDR/TCAS SYS 1(2) buttons are automatically updated.
+
+---
+
+[Back to Pedestal](../overviews/pedestal.md){ .md-button }
+
+---
+
+
+
diff --git a/docs/pilots-corner/a380x/a380x-briefing/flight-deck/pedestal/throttle.md b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/pedestal/throttle.md
new file mode 100644
index 000000000..7dfaf93ec
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/pedestal/throttle.md
@@ -0,0 +1,110 @@
+---
+title: Thrust and Thrust Reverser Control Levers
+description: The A380 Flight Deck Thrust and Thrust Reverser Control Levers description.
+---
+
+# Thrust and Thrust Reverser Control Levers
+
+---
+
+[Back to Pedestal](../overviews/pedestal.md){ .md-button }
+
+---
+
+{width=50%}
+
+[//]: # (TODO: This needs polishing)
+
+## Description
+
+The A380 has so called FADECs which stands for Full Authority Digital Engine Control and is responsible to ensure the
+engine to perform at maximum efficiency for the given condition.
+
+As one FADEC dedicated to each engine controls the engines' operation, the pilots or the FMGS can set the thrust. The
+pilot uses the thrust levers when in manual mode and the FMGS sets the thrust in automatic mode (A/THR aka Autothrust).
+
+The thrust levers in the A380 can only be moved manually and are not moved by an autothrottle system as it does in
+Boeing aircraft.
+
+The FADEC controls and limits thrust not to exceed the limit set via the thrust lever position in both manual and
+automatic modes.
+
+The FADEC receives the current thrust lever position and computes the thrust rating limit and the N1 for that Thrust
+Lever Angle (TLA).
+
+If the thrust lever is between two detents, the FADEC will select the rating limit of the higher detent.
+
+### Thrust Levers
+
+The thrust levers are used to manually adjust the engine thrust.
+
+Each thrust lever can be moved individually.
+
+The thrust lever position appears on the EWD via a blue circle on the thrust gauge.
+
+### Thrust Detents
+
+The flight crew can set each thrust lever in one of the following detents:
+
+- Idle (0) detent
+- Climb (CLB) detent
+- Flexible takeoff thrust (FLX) and Maximum Continuous Thrust (MCT) detent
+- Takeoff and Go-Around (TOGA) detent.
+
+Each detent has one or several thrust rating limits.
+
+### Thrust Reverser 2(3) Lever
+
+The thrust reversers levers are used to control the deployment and the stowing of the reversers, and to
+adjust the reverse thrust.
+
+Each thrust reverser lever can be moved individually from IDLE REV detent to MAX REV detent, when
+the associated thrust lever is in the IDLE detent.
+
+The flight crew can monitor the position of the thrust reverser lever on the EWD, via the blue circle on
+the reverse thrust gauge.
+
+### Automatic Thrust Control
+
+In autothrust mode (A/THR function active), the FMGC computes the thrust. Thrust is limited by the thrust lever position
+(except when in alpha-floor mode).
+
+#### A/THR Instinctive Disconnect Push Button
+
+Each thrust lever has a so-called "A/THR Instinctive Disconnect" push button in red. Pressing it disconnects the A/THR.
+
+!!! warning ""
+ If the flight crew pushes and holds one instinctive disconnect pb for more than 15 s, the A/THR system
+ is disconnected for the remainder of the flight. All A/THR functions including ALPHA FLOOR are lost, and they can be
+ recovered only at the next FMGC power-up (on ground).
+
+### Manual Thrust Control
+
+When the auto-thrust (A/THR) mode is not armed or not active (levers in wrong position) the engines are in manual mode.
+
+The thrust lever position controls thrust for the corresponding engine in this case.
+
+By moving the thrust lever, the pilot can set the thrust level, which corresponds to a N1 between the IDLE and TOGA
+positions.
+
+FLX/MCT detent:
+
+- On the ground, the engine will produce the Maximum Continuous Thrust (MCT) if the crew did not set a valid FLEX take
+ off temperature. It needs to be higher than the current Total Air Temperature (TAT) to have any effect.
+- After takeoff with FLEX thrust, the pilot can, by moving the thrust lever to TOGA or CL, chose MCT thrust. It is not
+ possible to go back to FLEX thrust.
+
+!!! info ""
+ Note: Setting the thrust lever out of FLX/MCT detent without reaching TOGA or CL detent has no effect.
+
+MAX TO thrust can always be achieved by pushing the thrust lever all the way forward.
+
+!!! warning "FLEX TO thrust is not yet available on the A380."
+
+---
+
+[Back to Pedestal](../overviews/pedestal.md){ .md-button }
+
+---
+
+
diff --git a/docs/pilots-corner/a380x/a380x-briefing/flight-deck/pedestal/trim-panel.md b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/pedestal/trim-panel.md
new file mode 100644
index 000000000..75cab84c4
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-briefing/flight-deck/pedestal/trim-panel.md
@@ -0,0 +1,41 @@
+---
+title: Trim Panel
+description: The A380 Flight Deck Trim Panel page description.
+---
+
+# Trim Panel
+
+[Back to Pedestal](../overviews/pedestal.md){ .md-button }
+
+---
+
+## Overview
+
+
+
+## Pitch Trim
+
+This control is used to adjust the aircraft's nose attitude up or down. It changes the angle of the
+horizontal stabilizer on the tail to reduce control forces on the stick or yoke for the pilot. The actual adjustment is
+made by moving the switch up to trim the nose down or down to trim the nose up.
+
+On ground, or in direct law, the THS is directly controlled via the pitch trim switch.
+In flight, in normal and alternate law, the THS is controlled by the flight control computers.
+
+## Rudder Trim
+
+This is used to adjust the aircraft's yaw to keep it flying straight with minimal control input,
+especially useful when the aircraft experiences asymmetrical forces like engine failure or crosswinds. The rudder
+trim is controlled by moving the knob left to turn the nose left (L) or right to turn the nose right (R).
+
+## Rudder Trim Display
+
+This display shows the current rudder trim setting in degrees.
+
+## Reset Button
+
+Typically, this button is used to reset the rudder trim settings to a neutral position.
+
+---
+
+[Back to Pedestal](../overviews/pedestal.md){ .md-button }
diff --git a/docs/pilots-corner/a380x/a380x-briefing/index.md b/docs/pilots-corner/a380x/a380x-briefing/index.md
new file mode 100644
index 000000000..08819a234
--- /dev/null
+++ b/docs/pilots-corner/a380x/a380x-briefing/index.md
@@ -0,0 +1,33 @@
+---
+title: A380 Pilot Briefing - Overview
+description: The A380X Pilot Briefing provides Flight Crew Operations Manuals (FCOM) styled documentation for the
+ FlyByWire A380X aircraft.
+---
+
+
+
+# A380 Pilot Briefing
+
+This A380 Pilot Briefing shall give a good overview of most A380
+systems for personal flight simulation with focus on Microsoft Flight
+Simulator and the FlyByWire A380X aircraft add-on.
+
+
-## Topics
+-
\ No newline at end of file
diff --git a/docs/release-notes/.pages b/docs/release-notes/.pages
index 139c3417d..c123b9bd4 100644
--- a/docs/release-notes/.pages
+++ b/docs/release-notes/.pages
@@ -1,23 +1,6 @@
-# Edit this page to get:
-# - Title for the whole directory
-# - Titles for specific pages or subdirectories
-# - Order of pages (otherwise alphabetical order)
-
title: Release Notes
nav:
- - ...
- - Stable Release v0.11.0: v0110.md
- - Stable Release v0.10.1: v0101.md
- - Stable Release v0.10.0: v0100.md
- - Stable Release v0.9.1: v091.md
- - Stable Release v0.9.0: v090.md
- - Stable Release v0.8.2: v082.md
- - Stable Release v0.8.1: v081.md
- - Stable Release v0.8.0: v080.md
- - Stable Release v0.7.5: v075.md
- - Stable Release v0.7.4: v074.md
- - Stable Release v0.7.3: v073.md
- - Stable Release v0.7.2: v072.md
- - Stable Release v0.7.1: v071.md
- - Stable Release v0.7.0: v070.md
- - FBW Installer: installer
+ - Overview: index.md
+ - A32NX: a32nx
+ - A380X: a380x
+ - Installer: installer
diff --git a/docs/release-notes/a32nx/.pages b/docs/release-notes/a32nx/.pages
new file mode 100644
index 000000000..7f9882755
--- /dev/null
+++ b/docs/release-notes/a32nx/.pages
@@ -0,0 +1,19 @@
+
+title: A32NX Release Notes
+nav:
+ - Stable Release v0.12.0: v0120.md
+ - Stable Release v0.11.1: v0111.md
+ - Stable Release v0.11.0: v0110.md
+ - Stable Release v0.10.1: v0101.md
+ - Stable Release v0.10.0: v0100.md
+ - Stable Release v0.9.1: v091.md
+ - Stable Release v0.9.0: v090.md
+ - Stable Release v0.8.2: v082.md
+ - Stable Release v0.8.1: v081.md
+ - Stable Release v0.8.0: v080.md
+ - Stable Release v0.7.5: v075.md
+ - Stable Release v0.7.4: v074.md
+ - Stable Release v0.7.3: v073.md
+ - Stable Release v0.7.2: v072.md
+ - Stable Release v0.7.1: v071.md
+ - Stable Release v0.7.0: v070.md
diff --git a/docs/release-notes/v0100.md b/docs/release-notes/a32nx/v0100.md
similarity index 93%
rename from docs/release-notes/v0100.md
rename to docs/release-notes/a32nx/v0100.md
index 0a0968882..c5b07fdca 100644
--- a/docs/release-notes/v0100.md
+++ b/docs/release-notes/a32nx/v0100.md
@@ -1,8 +1,8 @@
-# Stable Release v0.10.0
+# A32NX Stable Release v0.10.0
-
+
We're excited to bring a slew of new features and various improvements to the A32NX. Terrain on ND is now available through our SimBridge, which allows sim pilots to have access to our external
terrain database. We've got some improved visuals by way of interior and exterior lighting, as well as new UI elements in the flyPadOS. In the
@@ -28,14 +28,14 @@ This release now includes these major features:
For a full release changelog - [see here](#changelog)
!!! tip "Recommended Settings"
- Before your first flight, please make sure to read our [Recommended Settings](../fbw-a32nx/settings.md) guide.
+ Before your first flight, please make sure to read our [Recommended Settings](../../aircraft/install/settings.md) guide.
**Navigraph Airframe**
The team at Navigraph have been kind enough to include our airframe as a selectable option on SimBrief. You no longer have to save our custom airframe to your account to use it. If we decide
to make any changes, it will be automatically updated in their system.
- [Guide Here](../fbw-a32nx/feature-guides/simbrief.md#simbrief-airframe){.md-button}
+ [Guide Here](../../aircraft/a32nx/feature-guides/simbrief.md#simbrief-airframe){.md-button}
!!! warning "Important User Experience Changes"
@@ -49,19 +49,19 @@ For a full release changelog - [see here](#changelog)
- Local Files feature
- Company Routes
- [SimBridge Guides Here](../simbridge/index.md){.md-button}
+ [SimBridge Guides Here](../../tools/simbridge/index.md){.md-button}
- Custom Flight Management System.
- - See the [Special Notes Section](../fbw-a32nx/feature-guides/cFMS.md#special-notes) on our custom FMS page for more details.
+ - See the [Special Notes Section](../../aircraft/a32nx/feature-guides/cFMS.md#special-notes) on our custom FMS page for more details.
- Weather is inoperable as we wait for Asobo implementations.
- MSFS Built-in ATC and VFR maps are on limited support. [Guides Here](#)
- - [Discontinuities](../pilots-corner/advanced-guides/flight-planning/disco.md) may now appear in your flight plan — they are a feature and not a bug.
- - [Throttle calibration](../fbw-a32nx/feature-guides/flypados3/throttle-calibration.md) is **mandatory**.
+ - [Discontinuities](../../pilots-corner/a32nx/a32nx-advanced-guides/flight-planning/disco.md) may now appear in your flight plan — they are a feature and not a bug.
+ - [Throttle calibration](../../aircraft/common/flypados3/throttle-calibration.md) is **mandatory**.
!!! info ""
- Downloads available through our [installer](../fbw-a32nx/installation.md).
+ Downloads available through our [installer](../../aircraft/install/installation.md).
- Please see our [Support Guide](../fbw-a32nx/support/index.md) and [Reported Issues](../fbw-a32nx/support/reported-issues.md).
+ Please see our [Support Guide](../../aircraft/support/index.md) and [Reported Issues](../../aircraft/support/known-issues/index.md).
---
@@ -93,7 +93,7 @@ The ND and PFD indicate the tuning mode of the navaids displayed by way of an un
Overall, navaid selection and automatic tuning simplifies the navigation process for pilots and allows them to focus on other critical aspects of the flight. It is a valuable feature that improves the safety and efficiency of the aircraft.
-{loading=lazy}
+{loading=lazy}
### Air Conditioning Simulation
@@ -147,21 +147,21 @@ layouts.
GSX integration features supported include refueling, boarding, and cargo. While we have some limitations in place due to Asobo's model and animations, we have done our best to make the experience
to sync GSX features through the EFB as seamless as possible. These limitations are most notable with utilizing the rear cargo door or passenger doors and require special toggles on our EFB.
-You can read more about our GSX integration [here](../fbw-a32nx/feature-guides/gsxintegration/index.md).
+You can read more about our GSX integration [here](../../aircraft/a32nx/feature-guides/gsxintegration/index.md).
QuickControls have been added to the EFB to allow for quick access to important features like EFB brightness, or controlling the SimBridge connection, instant boarding. or instant ADIRS alignment.
-See our documentation for more information: [Quick Controls Documentation](../fbw-a32nx/feature-guides/flypados3/index.md#quick-controls)
+See our documentation for more information: [Quick Controls Documentation](../../aircraft/common/flypados3/index.md#quick-controls)
The EFB Pushback System can now be fully controlled via API and therefore mapped to hardware buttons or controllers. See our
-documentation for more information: [Pushback API](../fbw-a32nx/a32nx-api/a32nx-flightdeck-api.md#pushback-api)
+documentation for more information: [Pushback API](../../aircraft/a32nx/a32nx-api/a32nx-flightdeck-api.md#pushback-api)
We also continue to improve and perfect on our translations for the EFB, which would not be possible without the amazing support from our community. It also would not be possible without our great partners at Localazy who have provided us with a great platform to manage our translations.
!!! note ""
- We are always looking for more help with translations. You can find more information on how to do so through our documentation [here](../dev-corner/dev-guide/specific/flypad-translations.md).
+ We are always looking for more help with translations. You can find more information on how to do so through our documentation [here](../../dev-corner/dev-guide/specific/flypad-translations.md).
+
+- 4K Texture Option
+
+ ---
+
+ [System Requirements](../../aircraft/install/installation.md#estimated-system-requirements-for-a380x){.md-button}
+
+ Includes our 4K downscaled cabin, cockpit and exterior textures. Choose this option for reduced stutters, better performance, with HIGH or lower texture resolution setting.
+
+ Additionally, if you intend to use the following:
+
+ - Use frame generation
+ - Virtual Reality (VR)
+ - DX12 beta
+ - or are otherwise limited by your graphics card VRAM amount.
+
+- 8K Textures Option
+
+ ---
+
+ [System Requirements](../../aircraft/install/installation.md#estimated-system-requirements-for-a380x){.md-button}
+
+ Includes our 8K full resolution cabin, cockpit and exterior textures. This is the full fidelity experience and our recommendation if your system is powerful enough to support it. Realistic and in high detail.
+
+ - DX11 recommended
+ - HIGH or lower texture resolution setting recommended
+
+
+
+## Release Feature List
+
+### Flight Management
+
+- [x] Working flight management system (FMS) -> based on the novel FBW **fms-v2**
+- [x] Vertical guidance (VNAV) to accurately follow altitude and speed constraints
+- [x] Support for all ARINC424 leg types, holdings, missed approaches and diversions
+- [x] Separate operation of CAPT and F/O MFD
+- [x] Flight management via 17 interactive pages in the MFD
+
+### ECAM / Flight Warning
+
+- [x] Accurate MEMOs for a multitude of systems
+- [x] Electronic checklists for normal procedures (checklists) and abnormal sensed procedures (faults)
+- [x] Audible callouts such as radio altitude, EGPWS, AUTO BRK OFF, AP disconnection
+
+### Navigation
+
+- [x] Onboard Airport Navigation (OANS) display, including RWY AHEAD advisory
+ -
+
+-
+
+-
\ No newline at end of file
diff --git a/docs/tools/installer/index.md b/docs/tools/installer/index.md
new file mode 100644
index 000000000..25c64a799
--- /dev/null
+++ b/docs/tools/installer/index.md
@@ -0,0 +1,3 @@
+# Installer Guide
+
+[//]: # (TODO: Write this Installation Guide)
\ No newline at end of file
diff --git a/docs/simbridge/.pages b/docs/tools/simbridge/.pages
similarity index 100%
rename from docs/simbridge/.pages
rename to docs/tools/simbridge/.pages
diff --git a/docs/simbridge/assets/autostart_prompt.png b/docs/tools/simbridge/assets/autostart_prompt.png
similarity index 100%
rename from docs/simbridge/assets/autostart_prompt.png
rename to docs/tools/simbridge/assets/autostart_prompt.png
diff --git a/docs/simbridge/assets/efb-setting-simoptions.png b/docs/tools/simbridge/assets/efb-setting-simoptions.png
similarity index 100%
rename from docs/simbridge/assets/efb-setting-simoptions.png
rename to docs/tools/simbridge/assets/efb-setting-simoptions.png
diff --git a/docs/simbridge/assets/exec_location.png b/docs/tools/simbridge/assets/exec_location.png
similarity index 100%
rename from docs/simbridge/assets/exec_location.png
rename to docs/tools/simbridge/assets/exec_location.png
diff --git a/docs/simbridge/assets/firewall_rules.png b/docs/tools/simbridge/assets/firewall_rules.png
similarity index 100%
rename from docs/simbridge/assets/firewall_rules.png
rename to docs/tools/simbridge/assets/firewall_rules.png
diff --git a/docs/simbridge/assets/fwrules-dialog.png b/docs/tools/simbridge/assets/fwrules-dialog.png
similarity index 100%
rename from docs/simbridge/assets/fwrules-dialog.png
rename to docs/tools/simbridge/assets/fwrules-dialog.png
diff --git a/docs/simbridge/assets/installer_prompt.png b/docs/tools/simbridge/assets/installer_prompt.png
similarity index 100%
rename from docs/simbridge/assets/installer_prompt.png
rename to docs/tools/simbridge/assets/installer_prompt.png
diff --git a/docs/simbridge/assets/ipad-network-info.png b/docs/tools/simbridge/assets/ipad-network-info.png
similarity index 100%
rename from docs/simbridge/assets/ipad-network-info.png
rename to docs/tools/simbridge/assets/ipad-network-info.png
diff --git a/docs/simbridge/assets/manual_start_running.png b/docs/tools/simbridge/assets/manual_start_running.png
similarity index 100%
rename from docs/simbridge/assets/manual_start_running.png
rename to docs/tools/simbridge/assets/manual_start_running.png
diff --git a/docs/simbridge/assets/mcdu-coroute-selection-page.png b/docs/tools/simbridge/assets/mcdu-coroute-selection-page.png
similarity index 100%
rename from docs/simbridge/assets/mcdu-coroute-selection-page.png
rename to docs/tools/simbridge/assets/mcdu-coroute-selection-page.png
diff --git a/docs/simbridge/assets/mcdu-init-a-load.png b/docs/tools/simbridge/assets/mcdu-init-a-load.png
similarity index 100%
rename from docs/simbridge/assets/mcdu-init-a-load.png
rename to docs/tools/simbridge/assets/mcdu-init-a-load.png
diff --git a/docs/simbridge/assets/samsung-network-info.png b/docs/tools/simbridge/assets/samsung-network-info.png
similarity index 100%
rename from docs/simbridge/assets/samsung-network-info.png
rename to docs/tools/simbridge/assets/samsung-network-info.png
diff --git a/docs/simbridge/assets/simbridge-context-menu.png b/docs/tools/simbridge/assets/simbridge-context-menu.png
similarity index 100%
rename from docs/simbridge/assets/simbridge-context-menu.png
rename to docs/tools/simbridge/assets/simbridge-context-menu.png
diff --git a/docs/simbridge/assets/simbridge-header.png b/docs/tools/simbridge/assets/simbridge-header.png
similarity index 100%
rename from docs/simbridge/assets/simbridge-header.png
rename to docs/tools/simbridge/assets/simbridge-header.png
diff --git a/docs/simbridge/assets/simbridge-location.png b/docs/tools/simbridge/assets/simbridge-location.png
similarity index 100%
rename from docs/simbridge/assets/simbridge-location.png
rename to docs/tools/simbridge/assets/simbridge-location.png
diff --git a/docs/simbridge/assets/simbridge.png b/docs/tools/simbridge/assets/simbridge.png
similarity index 100%
rename from docs/simbridge/assets/simbridge.png
rename to docs/tools/simbridge/assets/simbridge.png
diff --git a/docs/simbridge/assets/simbridge_config.png b/docs/tools/simbridge/assets/simbridge_config.png
similarity index 100%
rename from docs/simbridge/assets/simbridge_config.png
rename to docs/tools/simbridge/assets/simbridge_config.png
diff --git a/docs/simbridge/assets/simbridge_installing.png b/docs/tools/simbridge/assets/simbridge_installing.png
similarity index 100%
rename from docs/simbridge/assets/simbridge_installing.png
rename to docs/tools/simbridge/assets/simbridge_installing.png
diff --git a/docs/simbridge/assets/simbridge_resourcefolder.jpg b/docs/tools/simbridge/assets/simbridge_resourcefolder.jpg
similarity index 100%
rename from docs/simbridge/assets/simbridge_resourcefolder.jpg
rename to docs/tools/simbridge/assets/simbridge_resourcefolder.jpg
diff --git a/docs/simbridge/assets/simbridge_stop_tm.png b/docs/tools/simbridge/assets/simbridge_stop_tm.png
similarity index 100%
rename from docs/simbridge/assets/simbridge_stop_tm.png
rename to docs/tools/simbridge/assets/simbridge_stop_tm.png
diff --git a/docs/simbridge/assets/simbridge_window.png b/docs/tools/simbridge/assets/simbridge_window.png
similarity index 100%
rename from docs/simbridge/assets/simbridge_window.png
rename to docs/tools/simbridge/assets/simbridge_window.png
diff --git a/docs/simbridge/assets/simbrief-datafile-download.png b/docs/tools/simbridge/assets/simbrief-datafile-download.png
similarity index 100%
rename from docs/simbridge/assets/simbrief-datafile-download.png
rename to docs/tools/simbridge/assets/simbrief-datafile-download.png
diff --git a/docs/simbridge/assets/taws_color_coding.png b/docs/tools/simbridge/assets/taws_color_coding.png
similarity index 100%
rename from docs/simbridge/assets/taws_color_coding.png
rename to docs/tools/simbridge/assets/taws_color_coding.png
diff --git a/docs/simbridge/assets/temp_folder.png b/docs/tools/simbridge/assets/temp_folder.png
similarity index 100%
rename from docs/simbridge/assets/temp_folder.png
rename to docs/tools/simbridge/assets/temp_folder.png
diff --git a/docs/simbridge/assets/terr-nd1.png b/docs/tools/simbridge/assets/terr-nd1.png
similarity index 100%
rename from docs/simbridge/assets/terr-nd1.png
rename to docs/tools/simbridge/assets/terr-nd1.png
diff --git a/docs/simbridge/assets/terr-nd2.png b/docs/tools/simbridge/assets/terr-nd2.png
similarity index 100%
rename from docs/simbridge/assets/terr-nd2.png
rename to docs/tools/simbridge/assets/terr-nd2.png
diff --git a/docs/simbridge/assets/tray_stop.png b/docs/tools/simbridge/assets/tray_stop.png
similarity index 100%
rename from docs/simbridge/assets/tray_stop.png
rename to docs/tools/simbridge/assets/tray_stop.png
diff --git a/docs/simbridge/assets/trayicon-remote-mcdu.png b/docs/tools/simbridge/assets/trayicon-remote-mcdu.png
similarity index 100%
rename from docs/simbridge/assets/trayicon-remote-mcdu.png
rename to docs/tools/simbridge/assets/trayicon-remote-mcdu.png
diff --git a/docs/simbridge/assets/trayicon-resource.png b/docs/tools/simbridge/assets/trayicon-resource.png
similarity index 100%
rename from docs/simbridge/assets/trayicon-resource.png
rename to docs/tools/simbridge/assets/trayicon-resource.png
diff --git a/docs/simbridge/assets/w11ch1.png b/docs/tools/simbridge/assets/w11ch1.png
similarity index 100%
rename from docs/simbridge/assets/w11ch1.png
rename to docs/tools/simbridge/assets/w11ch1.png
diff --git a/docs/simbridge/assets/w11ch2.png b/docs/tools/simbridge/assets/w11ch2.png
similarity index 100%
rename from docs/simbridge/assets/w11ch2.png
rename to docs/tools/simbridge/assets/w11ch2.png
diff --git a/docs/simbridge/assets/w11ch3.png b/docs/tools/simbridge/assets/w11ch3.png
similarity index 100%
rename from docs/simbridge/assets/w11ch3.png
rename to docs/tools/simbridge/assets/w11ch3.png
diff --git a/docs/simbridge/assets/web-mcdu-ipad.webp b/docs/tools/simbridge/assets/web-mcdu-ipad.webp
similarity index 100%
rename from docs/simbridge/assets/web-mcdu-ipad.webp
rename to docs/tools/simbridge/assets/web-mcdu-ipad.webp
diff --git a/docs/simbridge/index.md b/docs/tools/simbridge/index.md
similarity index 79%
rename from docs/simbridge/index.md
rename to docs/tools/simbridge/index.md
index 15d633c94..fc57c3e19 100644
--- a/docs/simbridge/index.md
+++ b/docs/tools/simbridge/index.md
@@ -24,10 +24,10 @@ SimBridge is our custom-built solution to connect our aircraft to various extern
| Feature | Status |
|:-----------------------------------------------------------------------------------:|:-----------------------------------------------------------:|
-| [Terrain Display](simbridge-feature-guides/terrain.md) | Available in [All Versions](../fbw-a32nx/fbw-versions.md) |
-| [MCDU Remote Display](simbridge-feature-guides/remote-displays/remote-mcdu.md) | Available in [All Versions](../fbw-a32nx/fbw-versions.md) |
-| [Company Routes Support](simbridge-feature-guides/coroute.md) | Available in [All Versions](../fbw-a32nx/fbw-versions.md) |
-| [flyPad Local Charts](../fbw-a32nx/feature-guides/flypados3/charts.md#local-files) | Available in [All Versions](../fbw-a32nx/fbw-versions.md) |
+| [Terrain Display](simbridge-feature-guides/terrain.md) | Available in [All Versions](../../aircraft/install/fbw-versions.md) |
+| [MCDU Remote Display](simbridge-feature-guides/remote-displays/remote-mcdu.md) | Available in [All Versions](../../aircraft/install/fbw-versions.md) |
+| [Company Routes Support](simbridge-feature-guides/coroute.md) | Available in [All Versions](../../aircraft/install/fbw-versions.md) |
+| [flyPad Local Charts](../../aircraft/common/flypados3/charts.md#local-files) | Available in [All Versions](../../aircraft/install/fbw-versions.md) |
| Remote Displays | Work in Progress |
!!! warning "Important Notes"
diff --git a/docs/simbridge/install-configure/.pages b/docs/tools/simbridge/install-configure/.pages
similarity index 100%
rename from docs/simbridge/install-configure/.pages
rename to docs/tools/simbridge/install-configure/.pages
diff --git a/docs/simbridge/install-configure/configuration.md b/docs/tools/simbridge/install-configure/configuration.md
similarity index 97%
rename from docs/simbridge/install-configure/configuration.md
rename to docs/tools/simbridge/install-configure/configuration.md
index e3e1aa738..02b936aad 100644
--- a/docs/simbridge/install-configure/configuration.md
+++ b/docs/tools/simbridge/install-configure/configuration.md
@@ -18,7 +18,7 @@ This tab is dedicated to settings regarding the SimBridge server itself.
- You can modify SimBridge's hosted port.
- Default: `8380`
!!! warning "Notice"
- If this is changed, make sure to reflect the same port in the [EFB](../../fbw-a32nx/feature-guides/flypados3/settings.md#sim-options).
+ If this is changed, make sure to reflect the same port in the [EFB](../../../aircraft/common/flypados3/settings.md#sim-options).
## Printer Settings
This tab is for modifying settings regarding printing data from the MCDU to your physical printer.
diff --git a/docs/simbridge/install-configure/installation.md b/docs/tools/simbridge/install-configure/installation.md
similarity index 98%
rename from docs/simbridge/install-configure/installation.md
rename to docs/tools/simbridge/install-configure/installation.md
index 6a9b4daa1..18f385fc1 100644
--- a/docs/simbridge/install-configure/installation.md
+++ b/docs/tools/simbridge/install-configure/installation.md
@@ -80,7 +80,7 @@ It is located in:
### Troubleshooting
-See [find the community folder](../../fbw-a32nx/installation.md#Troubleshooting)
+See [find the community folder](../../../aircraft/install/installation.md#Troubleshooting)
## Resources Folder
The resources folder is used for storing various files required by SimBridge to provide its functionality.
diff --git a/docs/simbridge/install-configure/start-simbridge.md b/docs/tools/simbridge/install-configure/start-simbridge.md
similarity index 96%
rename from docs/simbridge/install-configure/start-simbridge.md
rename to docs/tools/simbridge/install-configure/start-simbridge.md
index 1fcac10e8..0bc60b817 100644
--- a/docs/simbridge/install-configure/start-simbridge.md
+++ b/docs/tools/simbridge/install-configure/start-simbridge.md
@@ -17,7 +17,7 @@ Upon installation of SimBridge you will be prompted to enable autostart, You can
If you choose not to enable autostart, you can open SimBridge via the installer. Just select the `Start` button.
-If this is not your preference, or it fails to start, you can also open the tool by opening the `fbw-simbridge.exe` found in the folder, `flybywire-externaltools-simbridge`, in the [community folder](../../fbw-a32nx/installation.md#Troubleshooting).
+If this is not your preference, or it fails to start, you can also open the tool by opening the `fbw-simbridge.exe` found in the folder, `flybywire-externaltools-simbridge`, in the [community folder](../../../aircraft/install/installation.md#Troubleshooting).
## Stopping SimBridge
diff --git a/docs/simbridge/simbridge-feature-guides/.pages b/docs/tools/simbridge/simbridge-feature-guides/.pages
similarity index 100%
rename from docs/simbridge/simbridge-feature-guides/.pages
rename to docs/tools/simbridge/simbridge-feature-guides/.pages
diff --git a/docs/simbridge/simbridge-feature-guides/coroute.md b/docs/tools/simbridge/simbridge-feature-guides/coroute.md
similarity index 100%
rename from docs/simbridge/simbridge-feature-guides/coroute.md
rename to docs/tools/simbridge/simbridge-feature-guides/coroute.md
diff --git a/docs/simbridge/simbridge-feature-guides/local-files.md b/docs/tools/simbridge/simbridge-feature-guides/local-files.md
similarity index 59%
rename from docs/simbridge/simbridge-feature-guides/local-files.md
rename to docs/tools/simbridge/simbridge-feature-guides/local-files.md
index 1396b2c5d..f2f30e910 100644
--- a/docs/simbridge/simbridge-feature-guides/local-files.md
+++ b/docs/tools/simbridge/simbridge-feature-guides/local-files.md
@@ -2,4 +2,4 @@
Local Files is a feature that allows you to use local files for charts and maps in the flyPad's Charts section.
-See [flyPadOS 3 Charts](../../fbw-a32nx/feature-guides/flypados3/charts.md#local-files)
\ No newline at end of file
+See [flyPadOS 3 Charts](../../../aircraft/common/flypados3/charts.md#local-files)
\ No newline at end of file
diff --git a/docs/simbridge/simbridge-feature-guides/remote-displays/.pages b/docs/tools/simbridge/simbridge-feature-guides/remote-displays/.pages
similarity index 100%
rename from docs/simbridge/simbridge-feature-guides/remote-displays/.pages
rename to docs/tools/simbridge/simbridge-feature-guides/remote-displays/.pages
diff --git a/docs/simbridge/simbridge-feature-guides/remote-displays/architecture.md b/docs/tools/simbridge/simbridge-feature-guides/remote-displays/architecture.md
similarity index 100%
rename from docs/simbridge/simbridge-feature-guides/remote-displays/architecture.md
rename to docs/tools/simbridge/simbridge-feature-guides/remote-displays/architecture.md
diff --git a/docs/simbridge/simbridge-feature-guides/remote-displays/remote-mcdu.md b/docs/tools/simbridge/simbridge-feature-guides/remote-displays/remote-mcdu.md
similarity index 100%
rename from docs/simbridge/simbridge-feature-guides/remote-displays/remote-mcdu.md
rename to docs/tools/simbridge/simbridge-feature-guides/remote-displays/remote-mcdu.md
diff --git a/docs/simbridge/simbridge-feature-guides/terrain.md b/docs/tools/simbridge/simbridge-feature-guides/terrain.md
similarity index 82%
rename from docs/simbridge/simbridge-feature-guides/terrain.md
rename to docs/tools/simbridge/simbridge-feature-guides/terrain.md
index c497276db..600845f13 100644
--- a/docs/simbridge/simbridge-feature-guides/terrain.md
+++ b/docs/tools/simbridge/simbridge-feature-guides/terrain.md
@@ -3,7 +3,7 @@
Sicily, Italy
-The Terrain Awareness and Warning Systems (TAWS) is a system used to alert the flight crew in a timely manner of hazardous situations ahead of the airport to avoid Controlled Flight Into Terrain (CFIT). A part of TAWS is to overlay the approach terrain on the [ND](../../pilots-corner/a32nx-briefing/flight-deck/front/nd.md), referred to as Terrain Awareness and Display (TAD), for the awareness of the crew. This display is derived from a database and subsequently can be out of date, which can lead to TAWS making false positives and general nuisances to the crew.
+The Terrain Awareness and Warning Systems (TAWS) is a system used to alert the flight crew in a timely manner of hazardous situations ahead of the airport to avoid Controlled Flight Into Terrain (CFIT). A part of TAWS is to overlay the approach terrain on the [ND](../../../pilots-corner/a32nx/a32nx-briefing/flight-deck/front/nd.md), referred to as Terrain Awareness and Display (TAD), for the awareness of the crew. This display is derived from a database and subsequently can be out of date, which can lead to TAWS making false positives and general nuisances to the crew.
!!! warning "Note"
Please be aware that we are still continuously optimizing the performance of the TERR ON ND feature.
@@ -30,7 +30,7 @@ The aforementioned database has worldwide coverage and is defined according to a
## Enabling the Terrain Display
-The Terrain Display can be enabled on either the `left` or `right` [Navigation Display](../../pilots-corner/a32nx-briefing/flight-deck/front/nd.md). To enable the display, push the `TERR ON ND` [pushbutton](../../pilots-corner/a32nx-briefing/flight-deck/front/nd.md#terr-on-nd-pushbutton) and the display will begin to overlay the terrain ahead of the aircraft in a sweeping motion.
+The Terrain Display can be enabled on either the `left` or `right` [Navigation Display](../../../pilots-corner/a32nx/a32nx-briefing/flight-deck/front/nd.md). To enable the display, push the `TERR ON ND` [pushbutton](../../../pilots-corner/a32nx/a32nx-briefing/flight-deck/front/nd.md#terr-on-nd-pushbutton) and the display will begin to overlay the terrain ahead of the aircraft in a sweeping motion.
## Usage
The display contains many details, and understanding these details will allow you to effectively use the display as well as understand its faults. If the aircraft is descending more than 1 000 ft/min, then the display provides a 30-second advance display for better projection.
diff --git a/docs/simbridge/troubleshooting.md b/docs/tools/simbridge/troubleshooting.md
similarity index 95%
rename from docs/simbridge/troubleshooting.md
rename to docs/tools/simbridge/troubleshooting.md
index 868881892..b4bc3d97c 100644
--- a/docs/simbridge/troubleshooting.md
+++ b/docs/tools/simbridge/troubleshooting.md
@@ -64,17 +64,17 @@ SimBridge should now be able to be minimized to the tray appropriately.
The EFB will stop trying to connect to SimBridge after a 5-minute timer.
Check the connectivity status on the EFB by checking if the Wi-Fi icon on the top is crossed.
-{loading=lazy}
+{loading=lazy}
Icon Crossed | Icon Normal
:-------------------------:|:-------------------------:
-{loading=lazy} | {loading=lazy}
+{loading=lazy} | {loading=lazy}
- If the Wi-Fi / connectivity icon is crossed, head to the flyPad Settings --> Sim Options
FlyPad Settings | Sim Options
:-------------------------:|:-------------------------:
-{loading=lazy} | {loading=lazy}
+{loading=lazy} | {loading=lazy}
To attempt connection:
@@ -185,7 +185,7 @@ Error: listen EADDRINUSE: address already in use :::8380
If the port is indeed already occupied, then you need to change the default port in [SimBridge Configuration](install-configure/configuration.md#server-settings).
-You also need to change the port in the [flyPad EFB Sim options page](../fbw-a32nx/feature-guides/flypados3/settings.md#sim-options).
+You also need to change the port in the [flyPad EFB Sim options page](../../aircraft/common/flypados3/settings.md#sim-options).
Of course, now the firewall might have to be opened for this new port.
diff --git a/includes/abbreviations.md b/includes/abbreviations.md
index bb8a20923..950d0a062 100644
--- a/includes/abbreviations.md
+++ b/includes/abbreviations.md
@@ -1,6 +1,10 @@
*[AP]: AutoPilot
+*[A/THR]: AutoTHRust
*[APU]: Auxiliary Power Unit
+*[BTV]: Brake To Vacate
*[ECAM]: Electronic Centralized Aircraft Monitoring
+*[EFB]: Electronic Flight Bag
+*[EFIS]: Electronic Flight Instrument System
*[F-PLN]: Flight PLan
*[F/O]: First Officer
*[FBW]: Fly-By-Wire
@@ -14,5 +18,6 @@
*[FPL]: Flight Plan
*[ILS]: Instrument Landing System (LOC and G/S)
*[MCDU]: Multipurpose Control & Display Unit
+*[OANS]: Onboard Airport Navigation System
*[ND]: Navigation Display
*[PFD]: Primary Flight Display
\ No newline at end of file
diff --git a/mkdocs.yml b/mkdocs.yml
index 69ad36949..98e1aa0b1 100644
--- a/mkdocs.yml
+++ b/mkdocs.yml
@@ -26,7 +26,7 @@ theme:
- navigation.prune
- navigation.tabs
- navigation.tabs.sticky
- # Removed this feature again as it's breaking TOC navigation on reported-issues.md
+ # Removed this feature again as it's breaking TOC navigation on known-issues.md
- navigation.instant
- navigation.instant.progress
- navigation.top
@@ -50,18 +50,10 @@ plugins:
mark: "video-embed"
redirects:
redirect_maps:
- # Folder: /start/
- 'start/fbw-versions.md': 'fbw-a32nx/fbw-versions.md'
- 'start/installation.md': 'fbw-a32nx/installation.md'
- 'start/support.md': 'fbw-a32nx/support/index.md'
- 'start/reported-issues.md': 'fbw-a32nx/support/reported-issues.md'
- 'start/autopilot-fbw.md': 'fbw-a32nx/feature-guides/autopilot-fbw.md'
- # Commented out in case we want to use this in the future
-# 'start/exp.md': 'fbw-a32nx/support/exp.md'
# Folder: /beginner-guide/
- 'beginner-guide/overview.md': 'pilots-corner/beginner-guide/overview.md'
+ 'beginner-guide/overview.md': 'pilots-corner/a32nx/a32nx-beginner-guide/overview.md'
# Folder: /airliner-flying-guide/
- 'airliner-flying-guide/overview.md': 'pilots-corner/airliner-flying-guide/overview.md'
+ 'airliner-flying-guide/overview.md': 'pilots-corner/airliner/airliner-flying-guide/overview.md'
# Folder: /development-projects/
'development-projects/overview.md': 'dev-corner/dev-guide/index.md'
'development-projects/website.md': 'dev-corner/development-projects/website.md'
@@ -70,29 +62,30 @@ plugins:
'a32nx-dev/texture-changes.md': 'dev-corner/texture-changes.md'
# TEMP redirects
# A.FLOOR
- 'fbw-a32nx/feature-guides/afloor.md': 'pilots-corner/advanced-guides/protections/afloor.md'
+ 'fbw-a32nx/feature-guides/afloor.md': 'pilots-corner/a32nx/a32nx-advanced-guides/protections/afloor.md'
# Fix Info
- 'fbw-a32nx/feature-guides/fixinfo.md': 'pilots-corner/advanced-guides/flight-planning/fixinfo.md'
+ 'fbw-a32nx/feature-guides/fixinfo.md': 'pilots-corner/a32nx/a32nx-advanced-guides/flight-planning/fixinfo.md'
# A32NX API
- 'pilots-corner/a32nx-briefing/a32nx_api.md': 'fbw-a32nx/a32nx-api/a32nx-flightdeck-api.md'
+ 'pilots-corner/a32nx-briefing/a32nx_api.md': 'aircraft/a32nx/a32nx-api/a32nx-flightdeck-api.md'
# additional redirects:
- 'fbw-a32nx/feature-guides/throttle-calibration.md': 'fbw-a32nx/feature-guides/flypados3/throttle-calibration.md'
+ 'fbw-a32nx/feature-guides/throttle-calibration.md': 'aircraft/common/flypados3/throttle-calibration.md'
# Convenience redirects:
- 'beginner-guide.md': 'pilots-corner/beginner-guide/overview.md'
- 'installation.md': 'fbw-a32nx/installation.md'
- 'throttle.md': 'fbw-a32nx/feature-guides/flypados3/throttle-calibration.md'
- 'reported-issues.md': 'fbw-a32nx/support/reported-issues.md'
- 'support.md': 'fbw-a32nx/support/index.md'
+ 'beginner-guide.md': 'pilots-corner/a32nx/a32nx-beginner-guide/overview.md'
+ 'installation.md': 'aircraft/install/installation.md'
+ 'throttle.md': 'aircraft/common/flypados3/throttle-calibration.md'
+ 'reported-issues.md': 'aircraft/support/known-issues/index.md'
+ 'support.md': 'aircraft/support/index.md'
'discord-bot.md': 'dev-corner/development-projects/discord-bot.md'
'airframe.md': 'https://docs.flybywiresim.com/fbw-a32nx/installation/#simbrief-airframe'
'fdr.md': 'https://docs.flybywiresim.com/fbw-a32nx/support/#fdr-files'
- 'flypad-performance.md': 'fbw-a32nx/feature-guides/flypados3/performance.md'
+ 'flypad-performance.md': 'aircraft/common/flypados3/performance.md'
+ 'faq.md': 'aircraft/faq.md'
# Commented out in case we want to use this in the future
# 'exp.md': 'fbw-a32nx/support/exp.md'
- 'vnav.md': 'pilots-corner/advanced-guides/flight-guidance/vertical-guidance/overview.md'
+ 'vnav.md': 'pilots-corner/a32nx/a32nx-advanced-guides/flight-guidance/vertical-guidance/overview.md'
# Release Notes Permalink
- 'latest-release.md': 'release-notes/v0111.md'
+ 'latest-release.md': 'release-notes/index.md'
'latest-installer-release.md': 'release-notes/installer/v330.md'
# ########################################
# Needed for URL within the A32NX aircraft
diff --git a/overrides/assets/stylesheets/home.css b/overrides/assets/stylesheets/home.css
index b94ff1941..3e94a6707 100644
--- a/overrides/assets/stylesheets/home.css
+++ b/overrides/assets/stylesheets/home.css
@@ -11,7 +11,7 @@
.container {
padding-top: 1.5rem;
padding-bottom: 1.5rem;
- background: url("../../assets/hero-image.jpg") #1d1e26;
+ background: url("../../assets/hero-image.png") #424a65;
background-repeat: no-repeat;
background-size: cover;
background-blend-mode: overlay;
diff --git a/overrides/home.html b/overrides/home.html
index 54fa36675..875d71bb3 100644
--- a/overrides/home.html
+++ b/overrides/home.html
@@ -24,7 +24,7 @@ FlyByWire Documentation
-
+
Reported Issues
-
-
- Beginner Guide
+ Beginner Guides
-
+ → A32NX
+ → A380X
+
-
-
- Pilot's Briefing
-
-
-
+ Pilot's Briefings
+
+
+
+ → A32NX
+ → A380X
+