flyPad Performance
Top of Descent Calculator
This calculator helps the pilot to calculate when to start descending (aka the Top of Descent) based on various variables so that different scenarios can be calculated (e.g., descending with 3° descent rate, descending with a given vertical speed, etc.).
For more information about descent and approach planning, see our guide: Descent and Approach Planning
Usage
There are several scenarios for the TOD Calculation:
 Fixed Angle of Descent:
 Descending from altitude X to altitude Y with a fixed descent angle (commonly 3°)
 Fixed Distance to Navigation Fix:
 Descending from altitude X to altitude Y within a fixed distance (e.g., 90 NM)
 Fixed Rate of Descent:
 Descending from altitude X to altitude Y within a fixed vertical speed (e.g.,  2000 ft/min)
Depending on the scenario, ground speeds are included in the calculation to take into account that we usually also slow down at some point during descent.
The flyPad TOD calculator can be used for all of these scenarios.
Angle of Descent
To calculate the TOD with a fixed angle of descent, we simply have to enter the starting altitude and the desired target altitude. We can also enter a certain angle besides 3°. But 3° is a common standard descent angle in aviation and rarely needs to be changed.
Example:
 Cruising altitude: 39 000 ft
 Target altitude: 11 000 ft
 Descent angle: 3°
 Ground Speed: has no impact on the calculation because of the fixed angle.
Result: We need to start our descent 88 NM before the target fix, at which we want to reach 11 000 ft.
Distance to Fix
To calculate the TOD with a fixed distance to a specific fix, we have to enter the starting altitude, the desired target altitude, and the distance to the target fix.
Example:
 Cruising altitude: 39 000 ft
 Target altitude: 11 000 ft
 Distance to fix: 90 NM
 Ground Speed: 450 kt (constant)
Result: We need to start our descent 90 NM before the target fix with either an average vertical speed of  2333 ft/min or an average descent angle of  3.0° during the descent distance.
The above result is averaged over the descent distance, and the values are approximations. For more precision, use one of the other two methods.
Rate of Descent
To calculate the TOD with a fixed vertical speed (rate of descent) we have to enter the starting altitude, the desired target altitude, and the desired vertical speed.
Example:
 Cruising altitude: 39 000 ft
 Target altitude: 11 000 ft
 Vertical Speed:  2000 ft/min
 Ground Speed: 450 kt (constant)
Result: We need to start our descent 105 NM before the target fix with a vertical speed of  2000 ft/min
Ground Speed and Wind
To allow for different ground speeds during descent, the calculator allows entering several altitude levels with the corresponding ground speed. This will be included in the calculations.
Example:
 Cruising altitude: 39 000 ft
 Target altitude: 11 000 ft
 Vertical Speed:  2 000 ft/min
 Ground Speed: 420 kt at or above 10 000 ft, 250 kt below 10 000 ft
Result: We need to start our descent 98 NM before the target fix with a vertical speed of 2 000 ft/min
Wind
Wind is not a factor and can be ignored as these calculations are done based on ground speed which includes any wind impacting an aircraft in the air.
Landing Performance Calculator
The primary purpose of this calculator is to aid the flight crew in assessing whether a landing can be safely made within the given runway length in existing conditions. The pilot can also use this tool to determine the appropriate level of braking and whether reverse thrust is needed to stop within the available runway distance.
The calculator results are shown both numerically and graphically. Variations in airplane configuration, approach speed, runway surface condition, and other parameters can also be investigated to see their effect on the airplane's landing distance. The landing distance results include a safety margin of 15 % added to the calculated distance.
Usage
Enter the required data into the calculator fields. The initial state of the calculator will have all input fields blank except for runway condition (Dry), flap setting (Full), overweight procedure (No), and reverse thrust (No). It is important to note that all fields must be filled to activate the "Calculate" button. The "Clear" button will return input fields to the initial state.
Weather data can be automatically filled by entering an airport ICAO and pressing "Get METAR". How to get the information for all the fields is described in the following section.

Wind, Temperature, QNH:
 This information can be obtained from the METAR or ATIS.

Rwy Altitude:
 This information can be obtained from the airport chart (see example below).

Rwy Heading:
 This information can be obtained from the airport chart (see example below).

Rwy Condition:
 This information can be obtained from the METAR or ATIS and from NOTAMs on the OFP (Operational Flight Plan).
 SimBrief provides field condition reports (FICONs) which helps populate appropriate data for this field.
 For detailed information see the RWY Conditions section on the landing calculator additional info page.

Rwy Slope:
 This information can be obtained from the airport chart (see example in Landing Calculator Additional Info) but requires a little calculation.
 Formula: (((Runway elevation on touchdown side)  (Runway elevation on far side)) / Runway length) * 100.
 E.g., EDDM 26R: 1449 ft  1467 ft =  18 ft.
 Then  18 ft / 13 123 ft =  0.001 37.
 Then  0.00137 * 100 =  0.137 % slope.

Rwy LDA (Landing Distance Available):
 This information can be obtained from the airport chart (see example below).

Approach Speed: MCDU PERF APPR
 This is part of the MCDU PERF APPR page and can be taken from there (V_{APP}).

Weight:
 This information can be obtained from the ECAM SD bottomright corner (GW 59 600 kg in the example below).

Flaps:
 Planned landing flap setting (CONF FULL or CONF 3).

Overweight Procedure:
 Will the landing weight be greater than the maximum landing weight (Yes or No).
 Reminder: maximum landing weight is 67 400 kg.

Reverse Thrust:
 Will reverse thrust be used (Yes or No)?
 Use of reverse thrust on a wet or contaminated runway would be considered necessary for safety reasons.
 May be subject to airport requirements. If there are airport requirements regarding the use of reverse thrust, these can be found on the airport chart (see example below).

Autoland:
 If an Autoland is planned, then set this to Yes.
Example Data
Below you can find an example of runway details and how to identify it to input data into the respective fields.
Example Chart:
_{Copyright © 2021 Navigraph / Jeppesen "Navigraph Charts are intended for flight simulation use only, not for navigational use."}
Example 1
This runway can be used for landing in the given circumstances and full flaps in all braking configurations (low, medium, max manual).
Example 2
This runway's landing distance available is long enough to be used for landing with full flaps only and with max manual braking. Be aware that there might be other restrictions that prohibit landing of an A320neo on this airport/runway.
Example 3
This runway can't be used for landing in the given circumstances. It is similar to Example 2 but has a higher weight and therefore higher approach speed.