flybywiresim · frankkopp · Nov 29, 2021 · Nov 24, 2021 · Nov 24, 2021 · Nov 25, 2021
diff --git a/docs/fbw-a32nx/assets/flypad/Pulling-knob.png b/docs/fbw-a32nx/assets/flypad/Pulling-knob.png
diff --git a/docs/fbw-a32nx/assets/flypad/flight-phases.png b/docs/fbw-a32nx/assets/flypad/flight-phases.png
diff --git a/docs/fbw-a32nx/feature-guides/cFMS.md b/docs/fbw-a32nx/feature-guides/cFMS.md
@@ -34,7 +34,7 @@ For guides on utilizing features included with our custom FMS see the [Guides an
 
 ## Guides and Information
 
-- [MCDU Fix Info](./fixinfo.md)
+- [MCDU Fix Info](../../pilots-corner/advanced-guides/flight-planning/fixinfo.md)
 - [Flight Plan Discontinuities](../../pilots-corner/beginner-guide/preparing-mcdu.md#discontinuity)
 
 ## Known Issues

diff --git a/docs/fbw-a32nx/feature-guides/index.md b/docs/fbw-a32nx/feature-guides/index.md
@@ -6,12 +6,10 @@ It is not a complete collection of all features but a growing list which is exte
 
 Topics:
 
-- [Alpha Floor Protection](afloor.md)
 - [Autopilot and fly-by-wire](autopilot-fbw.md)
 - [Flight Management System](cFMS.md)
-- [Fix Info](fixinfo.md)
 - [Fuel and Weight](loading-fuel-weight.md)
 - [MCDU Keyboard Support](mcdu-keyboard.md)
 - [SimBrief Integration](simbrief.md)
 - [Throttle Calibration](flyPad/throttle-calibration.md)
-- [flyPad EFB](flyPad/index.md)
+- [flyPad EFB](flyPad/index.md)
diff --git a/docs/fbw-a32nx/feature-guides/loading-fuel-weight.md b/docs/fbw-a32nx/feature-guides/loading-fuel-weight.md
@@ -72,8 +72,6 @@ Please select the correct version below.
 
     Trimming the aircraft for takeoff is usually optional and technically not required. Please reference our the [FBW Checklist](../../pilots-corner/SOP.md) to set the appropriate trim should you wish to.
 
-    !!! bug "TODO where to get CG?"
-
     Ideally, anything less than 25% CG is considered FWD load, and anything more than 25% is considered an AFT load. While opting to choose between either CG configuration (aft/fwd) please consider the information below.
 
     !!! info "Notes on Differing CG Configurations"

diff --git a/docs/pilots-corner/.pages b/docs/pilots-corner/.pages
@@ -2,6 +2,7 @@ title: Pilot's Corner
 nav:
     - Overview: index.md
     - Beginner Guide: beginner-guide
+    - Advanced Guides: advanced-guides
     - Airliner Flying Guide: airliner-flying-guide
     - A320neo Pilot Briefing: a32nx-briefing
     - Standard Operating Procedures: SOP.md

diff --git a/docs/pilots-corner/advanced-guides/.pages b/docs/pilots-corner/advanced-guides/.pages
@@ -0,0 +1,13 @@
+# Edit this page to get:
+# - Title for the whole directory
+# - Titles for specific pages or subdirectories
+# - Order of pages (otherwise alphabetical order)
+
+title: Advanced Guides
+nav:
+    - Overview: overview.md
+    - flight-phases.md
+    - flight-planning
+    - flight-guidance
+    - protections
+#    - ...
diff --git a/docs/pilots-corner/advanced-guides/data-management.md b/docs/pilots-corner/advanced-guides/data-management.md
@@ -0,0 +1,3 @@
+# Data Management
+
+## Stored Waypoints
diff --git a/docs/pilots-corner/advanced-guides/flight-guidance/.pages b/docs/pilots-corner/advanced-guides/flight-guidance/.pages
@@ -0,0 +1,9 @@
+# Edit this page to get:
+# - Title for the whole directory
+# - Titles for specific pages or subdirectories
+# - Order of pages (otherwise alphabetical order)
+
+title: Flight Guidance
+nav:
+    - Overview: overview.md
+#    - ...
diff --git a/docs/pilots-corner/advanced-guides/flight-guidance/approaches.md b/docs/pilots-corner/advanced-guides/flight-guidance/approaches.md
@@ -0,0 +1,11 @@
+# Approaches
+
+## ILS
+
+## RNAV
+
+## VOR, VOR/DME, NDB
+
+## Other Approaches
+
+### MLS
diff --git a/docs/pilots-corner/advanced-guides/flight-guidance/autopilot.md b/docs/pilots-corner/advanced-guides/flight-guidance/autopilot.md
@@ -0,0 +1,9 @@
+# Autopilot
+
+<!--
+
+Page 1131 FCOM - DSC-22-30-30
+
+- [Speed Protection Excessive V/S]
+
+-->
diff --git a/docs/pilots-corner/advanced-guides/flight-guidance/lnav.md b/docs/pilots-corner/advanced-guides/flight-guidance/lnav.md
@@ -0,0 +1 @@
+# Lateral Guidance
diff --git a/docs/pilots-corner/advanced-guides/flight-guidance/overview.md b/docs/pilots-corner/advanced-guides/flight-guidance/overview.md
@@ -0,0 +1,62 @@
+# Flight Guidance in the A320
+
+The flight management and guidance system (FMGS) performs navigation functions and lateral and vertical flight planning functions. It also computes performance parameters and guides the aircraft along a pre-planned route.
+
+It generates and sends commands to the FADECs, autothrust system, autopilot, and flight director to control aircraft roll, pitch, speed, and thrust. This gives three-dimensional flight management with fully automatic, optimized flight performance and guidance.
+
+## Lateral Guidance
+
+The primary flight plan is used for lateral guidance and automatically sequences route legs. The current aircraft position is used to determine the required steering commands (AP and FD) to achieve the desired flight plan path.
+
+## Vertical Guidance
+
+Vertical guidance is available for TAKEOFF, CLIMB, CRUISE, DESCENT, and APPROACH phases of the flight plan. The flight planning capability lets the pilot enter published departure, arrival, and approach segments with individual pseudo waypoints that include speed/altitude constraints. These constraints, as well as the entered cruise altitude and cost index,
+define the vertical profile.
+
+## Autopilot and Flight Director Modes
+
+Two types of autopilot and flight director modes are available to guide the aircraft:
+
+### Managed modes
+
+When the aircraft is using managed targets, the Flight Management and Guidance System (FMGS) guides it along lateral and vertical flight paths and speed profiles computed by the Flight Management function (FM) from data in the MCDU. FM manages the guidance targets.
+
+Managed Modes are activated when the corresponding knob on the FCU is pushed in provided that the aircraft meets the necessary engagement conditions. E.g. Managed Heading (NAV) requires a valid flight plan defined in the MCDU.
+
+### Selected modes
+
+When the flight crew is using selected targets, the FMGS guides the aircraft along lateral and vertical flight paths and speed profiles to meet targets that the flight crew has selected manually on the FCU. The flight crew selects the guidance targets.
+
+Selected Modes are activated by pulling the corresponding knob in the FCU.
+
+### Pulling and Pushing Knobs in Microsoft Flight Simulator
+
+Using the legacy [Cockpit Interaction System](../../../fbw-a32nx/support/reported-issues.md#cockpit-interaction-system) you can push and pull knobs on the FCU like this:
+
+![Pulling-knob](../../../fbw-a32nx/assets/flypad/Pulling-knob.png){loading=lazy width=30%}
+
+## Available Guidance Modes
+
+The following guidancve modes are available and displayed in the PFD's FMA as either active or armed. See our [PFD FMA](../../a32nx-briefing//pfd/fma.md) documentation.
+
+| Guidance | MANAGED                   | SELECTED       |
+|:---------|:--------------------------|:---------------|
+| LATERAL  | NAV, APP NAV              | HDG-TRK        |
+|          | LOC*, LOC                 |                |
+|          | RWY                       |                |
+|          | RWY TRK                   |                |
+|          | LAND                      |                |
+|          | GA TRK                    |                |
+|          | ROLL OUT                  |                |
+|          |                           |                |
+| VERTICAL | SRS (TO and GA)           |                |
+|          | CLB, DES                  | OP CLB, OP DES |
+|          | ALT CST*, ALT CST         | ALT*, ALT      |
+|          | ALT CRZ                   | EXPEDITE       |
+|          | G/S*, G/S                 |                |
+|          | FINAL, FINAL APP          |                |
+|          | FLARE                     |                |
+|          | TCAS                      |                |
+| SPEED    | FMGC REFERENCE            | FCU REFERENCE  |
+|          | (ECON, Auto SPD, SPD LIM) |                |
+|          | EXPEDITE                  |                |
diff --git a/docs/pilots-corner/advanced-guides/flight-guidance/vnav.md b/docs/pilots-corner/advanced-guides/flight-guidance/vnav.md
@@ -0,0 +1 @@
+# Vertical Guidance
diff --git a/docs/pilots-corner/advanced-guides/flight-phases.md b/docs/pilots-corner/advanced-guides/flight-phases.md
@@ -0,0 +1,65 @@
+# Flight Phases
+
+The A320 flight management system defines a set of flight phases each flight will sequence through.
+
+It is important to understand these flight phases as they have an impact on planning a flight as well as on the lateral and vertical guidance of the aircraft.
+
+![FLight Phases](../../fbw-a32nx/assets/flypad/flight-phases.png "FLight Phases")
+
+The most prominent place where these phases become visible are the MCDU PERF pages where all phases, apart from PREFLIGHT and DONE, have their own page.
+
+## PREFLIGHT Phase
+
+During the PREFLIGHT phase the pilot initializes the Flight Management Guidance Computer (FMGC) and sets up various systems in the aircraft.
+
+Flight planning and performance planning happen during this phase.
+
+## TAKEOFF Phase
+
+The TAKEOFF phase starts when applying take off thrust (FLX or TOGA) and extends until reaching the acceleration altitude.
+
+Autopilot can be engaged at 100ft above ground or 5 seconds ofter takeoff, whichever is later.
+
+At thrust reduction altitude the thrust levers are normally set in the climb thurst detent (CL detent). The FMGC is in managed mode at this point guiding the aircraft vertically and laterally along the flight plan.
+
+## CLIMB Phase
+
+The CLIMB phase extends from the acceleration altitude to the top of climb (ToC) cruise flight level (displayed and modifiable on the MCDU PROG page).
+
+The FMS guides the aircraft and commands acceleration when above the terminal area speed restriction altitude.
+
+The system observes speed/altitude constraints that have been entered in the flight plan.
+
+When all managed modes have been selected and confirmed, the FMS gives speed, altitude, and lateral guidance during climb.
+
+## CRUISE Phase
+
+The CRUISE phase extends from the top of climb (ToC) point to
+the top of descent (ToD) point.
+
+It may also includes intermediate climbs as well as en route descents. At anytime, the pilot can define a step climb to determine the cost and time savings of flying at a different flight level. Step climbs and descents are entered on the MCDU STEP ALTS page which is accessed from a VERT REV page or from the MCDU F-PLN page A.
+
+The FMS transitions to the descent phase when a subsequent descent is initiated within 200 NM of the destination and no preplanned step descent exists in front of the aircraft.
+
+## DESCENT Phase
+
+The DESCENT phase starts at the top--of--descent point (which is less than 200 NM from destination) by pushing the ALT knob for a managed descent or pulling the ALT knob for an open or selected descent from the cruise altitude.
+
+The pilot is required to confirm and initiate all descents from cruise altitude by pushing or pulling the ALT knob on the FCU. The managed descent does not occur until the pilot initiates the descent following clearance from ATC.
+
+## APPROACH Phase
+
+The APPROACH phase starts when the pilot activates and confirms the approach on the PERF descent page, or when the approach deceleration pseudo waypoint (DECEL) is passed and the aircraft is below 9500 ft AGL in managed flight.
+
+## GO-AROUND Phase
+
+The GO-AROUND phase is activated when the thrust levers are moved to the TOGA position while in the APPROACH phase. The FMS then guides the aircraft through the missed approach procedure.
+
+To return to the APPROACH flight phase, activate and confirm the APPROACH phase on the PERF GO-AROUND page.
+
+## DONE Phase
+
+The DONE phase is activated after the aircraft has been on the ground for at least 30 seconds and all engines are shut down.
+
+During the done phase, the FMS clears the active flight plan in
+preparation for reinitialization.
diff --git a/docs/pilots-corner/advanced-guides/flight-planning/.pages b/docs/pilots-corner/advanced-guides/flight-planning/.pages
@@ -0,0 +1,11 @@
+# Edit this page to get:
+# - Title for the whole directory
+# - Titles for specific pages or subdirectories
+# - Order of pages (otherwise alphabetical order)
+
+title: Flight Planning
+nav:
+#    - Overview: overview.md
+    - fixinfo.md
+#    - Flight Plan: fplan.md
+#    - ...
diff --git a/docs/fbw-a32nx/feature-guides/fixinfo.md → ...dvanced-guides/flight-planning/fixinfo.md b/docs/fbw-a32nx/feature-guides/fixinfo.md → ...dvanced-guides/flight-planning/fixinfo.md
@@ -5,15 +5,15 @@
 ## Overview
 
 The MCDU FIX INFO pages are used to create waypoint intersections of the
-flight plan with radials, radiuses, and abeam intercept points associated
+flight plan with radial, radius, and abeam intercept points associated
 with a waypoint.
 
 These lines or circles are displayed on the ND and also used to compute intercept waypoints which are then added to the active flight plan.
 
 The A32NX has implemented the display of these lines and circles on the ND.
 
 !!! warning ""
-    The computed intercept waypoints and ABEAM functionality are not yet implemented.
+    The computed intercept waypoints and ABEAM functionality are not yet implemented. This page will be updated as soon as these features are implemented.
 
 ## Use Cases
 
@@ -39,7 +39,7 @@ A reference fix (REF FIX) named EGKK is used to show the three different methods
 - Abeam:
     - An Abeam is a line from the REF FIX onto the flight path meeting the flight path at a 90° angle.
 
-![Fix Info Examples](../assets/fixinfo/fixinfo-example.png "Fix Info Examples")
+![Fix Info Examples](../../assets/advanced-guides/fixinfo/fixinfo-example.png "Fix Info Examples")
 
 After entering a radial, radius or abeam the FMS calculates if an intersection with the flight path is possible and provides the option to create a waypoint into the flight plan.
 
@@ -65,29 +65,29 @@ You will find the option to select the FIX INFO page on the top most waypoint of
 
 For this go to the MCDU F-PLN page and select the top most waypoint with the left LSK (line select key).
 
-![Top most waypoint in F-PLN](../assets/fixinfo/mcdu-top-wp.png "Top most waypoint in F-PLN"){loading=lazy}
+![Top most waypoint in F-PLN](../../assets/advanced-guides/fixinfo/mcdu-top-wp.png "Top most waypoint in F-PLN"){loading=lazy}
 
 This brings up the lateral revision page for this waypoint and also displays the FIX INFO page option. Press the right LSK next to `FIX INFO`
 
-![Lateral Revision page](../assets/fixinfo/mcdu-lat-rev.png "Lateral Revision page"){loading=lazy}
+![Lateral Revision page](../../assets/advanced-guides/fixinfo/mcdu-lat-rev.png "Lateral Revision page"){loading=lazy}
 
 ### 2) Enter a Navigation Fix
 
-![Enter a navigation fix](../assets/fixinfo/mcdu-fixinfo-enterfix.png "Enter a navigation fix"){loading=lazy}
+![Enter a navigation fix](../../assets/advanced-guides/fixinfo/mcdu-fixinfo-enterfix.png "Enter a navigation fix"){loading=lazy}
 
 ### 3) Enter Radial or Radius
 
-![Fix Info page](../assets/fixinfo/mcdu-fixinfo.png "Fix Info page"){loading=lazy}
+![Fix Info page](../../assets/advanced-guides/fixinfo/mcdu-fixinfo.png "Fix Info page"){loading=lazy}
 
 With radius 63NM around the waypoint ABTUM:
 
-![Fix Info with radius set](../assets/fixinfo/mcdu-fixinfo-radius.png "Fix Info with radius set"){loading=lazy}
+![Fix Info with radius set](../../assets/advanced-guides/fixinfo/mcdu-fixinfo-radius.png "Fix Info with radius set"){loading=lazy}
 
 ### 4) Additional Fix Info Pages
 
 You can define up to 4 different fixes by selecting the horizontal skew navigation button to go to the next page.
 
-![Go to previous or next page](../assets/fixinfo/mcdu-fixinfo-pages.png "Go to previous or next page"){loading=lazy}
+![Go to previous or next page](../../assets/advanced-guides/fixinfo/mcdu-fixinfo-pages.png "Go to previous or next page"){loading=lazy}
 
 ## Examples
 
@@ -97,7 +97,7 @@ FL340 with arrival TEBRA2G into Gatwick EGKK.
 
 A descent is required at 63NM before ABTUM as calculated by the flyPad Top of Descent calculator.
 
-![EGKK STAR TEBRA2G](../assets/fixinfo/navigraph-egkk-tebra2g.png "EGKK STAR TEBRA2G"){loading=lazy}
+![EGKK STAR TEBRA2G](../../assets/advanced-guides/fixinfo/navigraph-egkk-tebra2g.png "EGKK STAR TEBRA2G"){loading=lazy}
 <br/><sub>*Copyright © 2021 Navigraph / Jeppesen<br/>
 "Navigraph Charts are intended for flight simulation use only, not for navigational use."*</sub>
 
@@ -108,22 +108,22 @@ A descent is required at 63NM before ABTUM as calculated by the flyPad Top of De
 </style>
 
 !!! block ""
-    ![Fix Info with radius set](../assets/fixinfo/mcdu-fixinfo-radius.png "Fix Info with radius set"){loading=lazy width=48%}
-    ![ABTUM 63NM circle](../assets/fixinfo/nd-abtum-circle.png "ABTUM 63NM circle"){loading=lazy width=48%}
+    ![Fix Info with radius set](../../assets/advanced-guides/fixinfo/mcdu-fixinfo-radius.png "Fix Info with radius set"){loading=lazy width=48%}
+    ![ABTUM 63NM circle](../../assets/advanced-guides/fixinfo/nd-abtum-circle.png "ABTUM 63NM circle"){loading=lazy width=48%}
 
 ### ILS Localizer Extension Line
 
 To visualize the ILS localizer for the approach the runway fix can be used to display a radial line corresponding to the ILS track course.
 
 !!! block ""
-    ![Fix Info Page EGKK26L](../assets/fixinfo/mcdu-fixinfo-egkk26l.png "Fix Info Page EGKK26L"){loading=lazy width=48%}
-    ![Localizer Line for EGKK 26L](../assets/fixinfo/nd-egkk26l-locline.png "Localizer Line for EGKK 26L"){loading=lazy width=48%}
+    ![Fix Info Page EGKK26L](../../assets/advanced-guides/fixinfo/mcdu-fixinfo-egkk26l.png "Fix Info Page EGKK26L"){loading=lazy width=48%}
+    ![Localizer Line for EGKK 26L](../../assets/advanced-guides/fixinfo/nd-egkk26l-locline.png "Localizer Line for EGKK 26L"){loading=lazy width=48%}
 
 ### VOR Intercept in SID
 
 In this scenario we have a departure on 36R in KMCO (Orlando) with the ORLANDO 4 DEPARTURE SID (ORLA4). This departure expects ATC to assign headings after departure to intercept the filed/assigned route.
 
-![KMCO OLRA4 SID](../assets/fixinfo/navigraph-kmco-orla4.png "KMCO OLRA4 SID")
+![KMCO OLRA4 SID](../../assets/advanced-guides/fixinfo/navigraph-kmco-orla4.png "KMCO OLRA4 SID")
 <br/><sub>*Copyright © 2021 Navigraph / Jeppesen<br/>
 "Navigraph Charts are intended for flight simulation use only, not for navigational use."*</sub>
 
@@ -136,11 +136,11 @@ As you can read in the Initial Climb description for 36R we need to meet certain
 To visualize these points we can use the fix info page to define a 2NM distance circle and 2 lines for R155 and R090/270 on the ND.
 
 !!! block ""
-![Fix Info ORL](../assets/fixinfo/mcdu-orl-fixinfo1.png "Fix Info ORL"){loading=lazy width=48%}
-![Fix Info ORL](../assets/fixinfo/mcdu-orl-fixinfo2.png "Fix Info ORL"){loading=lazy width=48%}
+![Fix Info ORL](../../assets/advanced-guides/fixinfo/mcdu-orl-fixinfo1.png "Fix Info ORL"){loading=lazy width=48%}
+![Fix Info ORL](../../assets/advanced-guides/fixinfo/mcdu-orl-fixinfo2.png "Fix Info ORL"){loading=lazy width=48%}
 
 !!! block ""
-![Fix Info ORL](../assets/fixinfo/nd-orl-fixinfo1.png "Fix Info ORL"){loading=lazy width=48%}
-![Fix Info ORL](../assets/fixinfo/nd-orl-fixinfo2.png "Fix Info ORL"){loading=lazy width=48%}
+![Fix Info ORL](../../assets/advanced-guides/fixinfo/nd-orl-fixinfo1.png "Fix Info ORL"){loading=lazy width=48%}
+![Fix Info ORL](../../assets/advanced-guides/fixinfo/nd-orl-fixinfo2.png "Fix Info ORL"){loading=lazy width=48%}
 
 
diff --git a/docs/pilots-corner/advanced-guides/flight-planning/fplan.md b/docs/pilots-corner/advanced-guides/flight-planning/fplan.md
@@ -0,0 +1,2 @@
+# Flight Planning using the MCDU
+
diff --git a/docs/pilots-corner/advanced-guides/flight-planning/holds.md b/docs/pilots-corner/advanced-guides/flight-planning/holds.md
@@ -0,0 +1 @@
+# Holds
diff --git a/docs/pilots-corner/advanced-guides/flight-planning/offset.md b/docs/pilots-corner/advanced-guides/flight-planning/offset.md
@@ -0,0 +1 @@
+# Offset
diff --git a/docs/pilots-corner/advanced-guides/flight-planning/overview.md b/docs/pilots-corner/advanced-guides/flight-planning/overview.md
@@ -0,0 +1 @@
+# Flight Planning Using the MCDU