LDG Perf User Guide
LDG Perf User Guide
Performance Programs 0 P1
TABLE OF CONTENTS Windows L7.3 / iPad
Manual V5.3 – PPM Issue 1
Performance Programs 0 P2
USER INTERFACE Windows L7.3 / iPad
Manual V5.3 – PPM Issue 1
MODULE PRESENTATION
The LDG PERF application is an OCTOPUS program (except for Wide Body aircraft, for which TLC
computation engine is used).
This module is an interface designed for the pilot for use in the cockpit, and for dispatch engineers for
use on ground.
The aim of the LDG PERF application is to compute the Landing performance for all Airbus aircraft
(except for Wide Body on iPad):
- A300-600
- A310
- A320 Family
- A330
- A340
- A350
- A380.
Based on the same philosophy as the other on board performance applications, the User accesses the
LDG PERF interface for a specific aircraft tail number.
- Dispatch Conditions:
It permits to check the dispatch conditions on Required Landing Distance and Go Around performance.
The module checks the Required Landing Distance against the Available Landing Distance and the
Approach Climb Gradient against the gradient defined by the User (not less than the minimum gradient
required by the regulation).
- In-Flight Conditions:
It permits to obtain the In-Flight Landing Distance and Go Around performance for an estimated Landing
Weight and a given configuration (autobrake setting, approach type…). The User can also check the
overweight performance data and the landing performance following ECAM alerts.
In addition to this, LDG PERF can be used to determine landing performance with MEL and/or CDL
items, and/or ECAM alerts (In-Flight only).
Performance Programs 0 P3
USER INTERFACE Windows L7.3 / iPad
Manual V5.3 – PPM Issue 1
APPLICATION START
Start the Airbus Landing application by tapping the AIB Landing icon in the general menu.
Start the Airbus Landing application by tapping the AIB Landing icon in My flight page.
IN FLIGHT Dispatch
LFBO/TLS BLAGNAC
RWY Airport Data
WIND °/kt (000/0)
OAT °C
QNH hPa
RWY COND Results
A-ICE
Conditions Data
LW T 182
LDG CG
LDG CONF AUTO CONF (STD)>
All fields must be completed to compute your landing
AIR COND Off (STD)> performance data
APPR TYPE Normal (STD)>
GA GRADIENT % Min (STD)
VPilot kt 0
LDG TECH MAN-A/THR on >
BRK MODE Manual >
REV Yes (STD) >
Performance Programs 0 P4
USER INTERFACE Windows L7.3 / iPad
Manual V5.3 – PPM Issue 1
4. RESULTS PANEL
This panel presents the results as soon as a computation has been run and is complete.
Performance Programs 0 P5
USER INTERFACE Windows L7.3 / iPad
Manual V5.3 – PPM Issue 1
1. AIRPORT PANEL
The User uses the airport panel to select the airport and runway(s).
The standard mode is the single runway computation.
If enabled by the Administrator, the Landing calculations can be performed for a selection of several
runways (for a given airport): this is the Multiple Runway computation mode.
It is however possible to modify the preselected airport as described in the “Aircraft” chapter of the
document “Application management”.
When the airport is defined, the runway field provides the list of the airport runways.
Choose the required runway from the list by clicking on the corresponding row. A mark is displayed on
the selected landing runway, the user shall then validate by clicking on the Close button.
RWY Close
SINGLE Multiple
LFBO/TLS BLAGNAC
RWY Select RWY from the list
RWY
14L – 3000 m
Select RWY from the list.
14R – 3500 m
32L – 3500 m
32R – 3000 m
MODIFY RWY
Once a runway is selected, the interface switches to the next parameter to set.
Performance Programs 0 P6
USER INTERFACE Windows L7.3 / iPad
Manual V5.3 – PPM Issue 1
When “None” is selected by the Administrator, the MODIFY RWY option is deactivated in the Landing
application.
When “Reduced” mode or “Full” mode is selected, the MODIFY RWY button enables to display the
Modification panel.
If enabled by the Administrator, the User is able to modify the runway characteristics in accordance
with NOTAMS.
To modify a runway:
• Click on Modify RWY button below the runway list
• In the runway list, click on the Modify RWY button associated to the runway to modify.
RWY Close
SINGLE Multiple
Cancel
When the User clicks on “Modify RWY”, the following window is then displayed:
Restore Done
Performance Programs 0 P7
USER INTERFACE Windows L7.3 / iPad
Manual V5.3 – PPM Issue 1
The User has to click on a cell of the runway characteristics list in order to modify the value.
The “GA GRADIENT AT” field is displayed only if the Administrator has activated the “Increase Go
Around Height computation” option.
Note: The modifications entered at this level are lost when the runway is changed and do not affect
the airport database as created by the Administrator.
Any change in the runway definition is notified on the Airport/Runway panel with the message “modified”
next to the runway identifier.
Restore Done
The User can click on the Restore button to reset the runway characteristics, or the Done button to
validate the changes.
RWY Close
SINGLE Multiple
14L – 3000 m
14R (MODIFIED) – 3400 m
32L – 3500 m
32R – 3000 m
MODIFY RWY
The User can then click on the runway to use in the computation.
Performance Programs 0 P8
USER INTERFACE Windows L7.3 / iPad
Manual V5.3 – PPM Issue 1
When the User clicks on the MODIFY RWY, the following window is then displayed:
ELEVATION 488 ft
LENGTH 3500 m
SLOPE 0.10 %
SURFACE SMOOTH >
GA GRADIENT AT 1988 ft
Restor Done
Any change in the runway definition is notified on the Airport/Runway panel with the message “modified”
next to the runway identifier.
Note: “Surface” is displayed only if the selected runway is defined as Grooved/PFC in the airport
manager and if the option is ticked in the “DEFINE LD RUNWAY CONDITIONS” in the PA Admin
settings. The value can be modified if the runway surface is different from Dry (at Dispatch) or is 5-
Good or 5-Wet PFC/Grooved (in flight).
Note: The Elevation and Slope parameters can be modified on Windows only.
Performance Programs 0 P9
USER INTERFACE Windows L7.3 / iPad
Manual V5.3 – PPM Issue 1
RWY Close
SINGLE Multiple
14L – 3000 m
14R – 3500 m
32L – 3500 m
32R – 3000 m
The User can create a runway only from an airport that belongs to the airport database.
To create a runway:
• Tap on CREATE RWY. A window appears in order to set runway characteristics. The default values
are displayed (except for the runway name). All values are displayed in blue.
RWY
ELEVATION 2000 ft
LENGTH 5000 m
SLOPE -1.00 %
SURFACE SMOOTH >
GA GRADIENT AT 3500 ft
Restore Done
The User has to enter all the values to define the runway characteristics. All the required data can
usually be found in the airports charts.
1.3.1. RWY
The User enters the name of the runway they want to create.
The Name has to respect the NNLL format (NN is a number from 01 to 36 and LL are two optional
letters).
1.3.2. Elevation
The User has to enter the elevation of the runway threshold.
1.3.3. Length
The User has to enter the runway length.
1.3.4. Slope
The User has to enter the runway slope. The runway slope can be positive or negative.
Note: The runway slope has to remain within the Flight Manual limitations.
1.3.5. Surface
The User has to enter the state of the runway (smooth or Grooved / PFC).
1.3.6. GA Gradient AT
The User has to enter the Go Around Altitude.
All the created runway values appear in blue in the single runway computation panel.
Once created, the new runway appears on the RWY list for the selected airport with the indication
“(Created)”.
RWY Close
SINGLE Multiple
05 (Created) – 2800 m
Select RWY from the list.
14L – 3000 m
14R – 3500 m
32L – 3500 m
32R – 3000 m
Note: The creations entered at this level do not affect the airport database created by the
Administrator.
Note: In the case of a Multiple Runway selection, make sure that the wind conditions panel is filled
with wind direction / speed (° / kt).
RWY Close
Single MULTIPLE
32R – 3000 m
Next Done
The User selects an airport in the list of available airports. All the runways defined for this airport are
then displayed. The User selects the desired runways by tapping the corresponding cells.
The Select all tick box enables the selection of all available runways.
An additional way to inform the flight crew of the NOTAM validity date is to use, in addition to the 3
characters that are used to define the runway (ex: 14R), the 10 additional characters (see box in blue
on the figure here above) to define the specificities of the runway.
For example, the administrator can enter “_A5_#DEC10” to inform the pilots that these runway data
correspond to the A5 reduced runway and that the data are valid until December 10, 2017. The way to
define the specificities of the runway with these additional 10 characters depends on the airline policy.
This airline policy shall be commonly shared between the administrators and the flight crew.
After publishing the new performance data for the EFB, both of these two elements are displayed to
the flight crew in Flysmart+, in the Runway panel when selecting the runway and after a computation
is performed in the landing comments.
In this way, the flight crew is aware of the validity of the NOTAM either with the name of the runway
and/or when reading the comments.
2. CONDITIONS PANEL
The CONDITIONS panel enables the User to define the outside conditions and the aircraft configuration
data.
When starting the application, all the fields are empty, except for some of them if the Administrator has
defined standard values.
First of all, a button located at the top of the screen field permits selecting the computation mode: IN-
FLIGHT or DISPATCH.
If the Administrator has enabled both In-Flight and Dispatch computation modes, the LDG PERF
application starts with the mode selected by the User for the default landing computation in Landing
General options of the Administration part.
In flight DISPATCH
LFBO/TLS BLAGNAC
RWY
LW T 182
LDG CG
LDG CONFAUTO CONF (STD)>
AIR COND Off (STD)>
APPR TYPE Normal (STD)>
GA GRADIENT % Min (STD)
VPilot kt 0
LDG TECH MAN-A/THR on >
MEL 0 CDL 0
CLEAR COMPUTE
2.1.1. Wind
There are two ways of defining wind values:
A wind sock indicating wind direction is displayed next to the runway. An arrow and a numeric indication
are also displayed, showing wind direction and wind speed.
The entry is projected along and perpendicularly to the runway axis, to determine respectively the
headwind (or tailwind) and the crosswind components.
If the Administrator has activated the “gust” option for crosswind limitation, the User has the possibility
to enter the value of the gust when needed.
The User has the information that the gust can be entered when the format displayed in the status bar
shows “XXX/XX/GXX”:
The Gust component is only taken into account for the check of the maximum crosswind limitation.
Others limitations such as landing distance, braking energy etc. are based on the steady wind only.
Note: The gust may be considered for some runway states only, as defined by the Administrator.
The deviation from the International Standard Atmosphere (ISA) is automatically computed and
displayed next to the OAT field.
OAT °C 15
2.1.3. QNH
The User enters the QNH (mean sea level pressure) for the airport.
QNH hPa 1010
Note: For numerical fields, the Administrator can authorize the use of alternate units. In this case, the
User can enter a value with a unit different from the default one, provided that the right abbreviation is
used (shown in the status bar if enabled).
LW T 182
LDG CG
LDG CONF AUTO CONF (STD)>
AIR COND Off (STD)>
APPR TYPE Normal (STD)>
GA GRADIENT % Min (STD)
VPilot kt 0
LDG TECH MAN-A/THR on >
Tip: The User can enter “*” in the text box to retrieve the MLW.
Note: The LW is automatically retrieved from the LOADSHEET module if a LOADSHEET calculation is
performed.
The Administrator can modify the options to be more explicit (e.g. CG > 27% instead of Standard (basic)
and CG < 27% instead of Alternate for A320 for instance).
LDG CG Close
Note: If enabled by the administrator, the LDG CG field is automatically set in accordance with the LDG
CG value from the LOADSHEET module if a LOADSHEET calculation is performed. In this case, it is
displayed in yellow.
Note: The LDG CG is customizable by the user in Admin part (refer PPM Admin – LDG STD Values).
The “AUTO CONF” option provides the results relative to the configuration that permits:
- To land at the Landing Weight in input (if one configuration leads to a landing limited by the
performance), or
- To get the shortest Runway Length (i.e. CONF FULL) if both Configurations permit to land with the
Landing Weight in input.
Note: The Approach Configuration is not accessible as it is linked to the landing configuration. Landing
configuration FULL gives approach configuration 3 and landing configuration 3 gives approach
configuration 2.
In the particular case of a high altitude airport, the Approach Configuration 1+F can be applied as well
with a Landing Configuration 3, it the “CONF 1+F go-around (High ALT ARPT)” option has been
selected by the user in Admin part (refer to PPM Admin – Engine Options). This option is only available
for A319-115, A319-133, and A350-1041 aircraft models.
For A318 aircraft fitted with steep approach option, if the Administrator has ticked the steep approach
box in the aircraft options of aircraft details, the User can select a third approach type: Steep Approach.
The User can enter the value of the flight path angle (range: -5.5° to -4.5°).
Tip: The User can enter “MIN” to insert the minimum Gradient value.
In multiple runway mode, only one value can be set for the Go Around Gradient in the user inputs.
Then, for each runway, the landing application compares the Go Around Gradient set by the User to
the one set by the Administrator in the airport manager, takes the highest Go Around Gradient and
uses it for the computation.
VPilot kt 0
This field is displayed in the conditions panel only if the autoland option is defined in the aircraft
performance database.
LDG TECHNIQUE Close
Back
Back GLIDE ANGLE Close
Close
-3.2 X
- If an glide path angle has been defined in the airport database, the glide path angle is
automatically set to this value. However, when the User selects the Autoland Technique, an
edit box appears and the User can modify the glide path angle (range: -3.5° to -2.5°).
Back
Back GLIDE ANGLE Close
Close
-3.2 X
- If an ILS glide path angle has been defined in the airport database, the User has just to select
Autoland. The glide path angle is in this case fixed and the User cannot modify it.
Note: The performance applications Administrator can define standard values for the following fields:
- LDG CONF
- AIR COND
- APPR TYPE
- GA GRADIENT
- LDG TECHNIQUE.
In this case, the default values are displayed with the indication (STD) when opening the LDG PERF
application. For example:
MEL 0 CDL 0
By clicking on the MEL or CDL button, the User can select MEL and/or CDL items.
The User selects the desired items in the following panel by clicking or tapping on the chosen row.
A scroll bar on the right can be used to navigate in the list.
Done
A panel in which the User can select the failure appears. Item selection can be done by clicking or
tapping on the chosen row, then on the Done button.
Normal
Stuck open
Done
After one MEL item has been selected, the Reset button is activated in order to reset all MEL items to
normal.
Done
Tap on the Done button of MEL items panel to validate the choices.
The number of MEL items selected is updated on the MEL button. The User can display the selected
MEL items by tapping on the MEL Button.
MEL 1 CDL 0
Done
The User can Add new MEL items by tapping on the Add button, and perform the same process as
explained here above.
The User can remove selected MEL items by tapping on the Modify button.
Delete all
The User can either tap on the Delete all button to remove all selected MEL items, or tick the MEL items
to remove, and then tap on the Delete button.
Delete (1)
Done
On Windows devices, the User can modify the MEL items selection by tapping on the Modify button:
MEL 1 CDL 0
Modify
Done
They can then select new MEL items or set one modified MEL item to another value.
In the Landing application, the User selects first the number of negligible items by tapping on the CDL
button:
Done
By tapping on the ADD button of the CDL subpanel, the User opens the CDL items panel. The CDL
items panel displays the list of structural parts that can be missing, and for which performance penalties
have to be considered for the calculation of the landing performance.
Done
On Windows device, the CDL button directly opens the CDL items subpanel, that enables the selection
of the number of negligible items and the CDL items list for which performance penalties have to be
considered for the calculation of the landing performance.
MEL 0 CDL 0
Number of negligible items: 0
The User enters a CDL item by first selecting the applicable area (air conditioning, doors …), then by
selecting the applicable item and the number missing.
The User validates the Item Number Missing by tapping on the Done button in the virtual keypad, then
on the Done button.
The User can display CDL items by tapping on the CDL button.
CDLDone
ITEMS Close
Modify
The user can modify the CDL items list by tapping on the Modify button. They can then tap on one
selected CDL items to remove it. They can also tap on a not selected CDL item to select it.
Done
The User can then remove all the CDL items by tapping on the Delete all button, or they can tick the
CDL to remove and click on the Delete button.
Delete all
In order to add a new CDL item, the User must tap on the Modify button in the CDL Items Summary
subpanel.
For dispatch purposes, the User must verify that the planned landing weight is lower than or equal to
the Maximum Landing Weight limited by performance (MLW(Perf)) according to the forecasted
conditions.
If the Administrator has disabled the “LW Input in Dispatch” option, the planned Landing Weight is
always equal to the certified Maximum Landing Weight (MLW).
If the Administrator has enabled the “In-Flight LDG distance considered at dispatch” option, the landing
calculations can be performed taking into account the Factored In-flight LDG Distance at dispatch.
14R
In flight DISPATCH
LFBO/TLS BLAGNAC
RWY 14R LDG CONF CONF 3
LIMITATION CODE LDA
WIND °/kt (110/10/G20)
OAT °C 15
VAPP --- kt 10
QNH hPa 1015
RWY COND Wet MLW(PERF) 180.5 T 9
3500 m
A-ICE Off (STD)
EO GA GRADIENT AT 1989 ft --- %
LW T 182
LDG CG CG >27% EO GA SPEED --- kt
LDG CONF CONF 3
AIR COND On (STD)
APPR TYPE Normal (STD)
GA GRADIENT % Min (STD)
VPilot kt 0
LDG TECH MAN-A/THR on
14R
|||||
MEL 0 CDL 0 ^^^
CLEAR MODIFY
When the calculated MLW(Perf) is below the LW entered by the User, red dashes “---" are displayed
instead of the output values.
The aircraft cannot be dispatched with this LW value. The actual Landing Weight must be reduced at
least to the value of MLW(Perf).
14R
In flight DISPATCH
3500 m
A-ICE Off (STD)
The results page displays the landing configuration selected by the User, or the result of the
optimization when the AUTO CONF option is selected.
When AUTO CONF is selected, the landing performance is determined for CONF 3 (Go Around
in CONF 2) and CONF FULL (Go Around in CONF 3).
If the landing is possible for both conditions, then the results for CONF FULL are displayed.
If the landing is possible only in CONF FULL (respectively CONF 3), then the results for CONF
FULL (respectively CONF 3) are displayed.
The Maximum Performance-Limited Landing Weight (MLW(Perf)) is the maximum weight that complies
with all the regulatory requirements at landing.
CAUTION
The MLW(Perf) may be higher than the certified Maximum Landing Weight (MLW), but the aircraft must
not be dispatched with an estimated Landing weight at destination higher than the certified MLW.
VAPP is the aircraft approach speed considered for the landing computation, 50 ft above the runway
surface. VAPP is defined from the Lowest Selectable Speed (VLS), with the addition of a speed
increment due to the wind correction or induced by the effect of autothrust or ice accretion. Its
computation is detailed in the Additional Results page. The administrator must enable the parameter
“Increase Vapp for dispatch” in the PA Admin, in order to display the Vapp, the Vpilot and the approach
correction value.
The Required Landing Distance is the result of the Actual Landing Distance (ALD) with the regulatory
margins, depending on the runway state.
For example, RLDdry = 1.667 * ALDdry.
This RLD must be lower than or equal to the Landing Distance Available on the runway.
The RLD is displayed on the runway graph.
1.2.1.7. Margin
The margin is the difference between the runway length and the computed Required Landing
Distance (RLD).
The margin is displayed on the runway graph.
14R
Additional information can also be displayed as shown below. To do so, the Administrator has to select
the requested information in the administrator module.
14R
LDG_CLB_GRAD LD 17.32
Several regulatory requirements can limit the landing performance. The requirements that limit
performance in specific cases are identified in the computation results via limitation codes. The
following table indicates the various codes used for the landing limitations:
1.2.2.3. Speeds
Dispatch Landing Distance (LD): most limiting among Required LD and Actual LD.
This label gives information regarding the credit of the reversers used for the calculation
To activate the In-Flight Landing Distance check at dispatch, the Administrator has to:
- Enable the “In-Flight LDG distance considered at dispatch” option in the landing preferences,
and choose one of the two possible options:
o “F-LD For Information Only”, or
o “MLW limited by MAX of (F-LD; RLD)”
- Enable the “Increase VAPP for dispatch” option. Then, the VAPP at dispatch is computed as
VAPP in-flight
- Select Reported Braking Action for In-Flight Landing Distance computation.
14R
In flight DISPATCH
LFBO/TLS BLAGNAC
RWY 14R LDG CONF CONF 3
LIMITATION CODE LDA
WIND °/kt (110/10/G20)
OAT °C 15
VAPP --- kt
QNH hPa 1015
10
RWY COND Wet MLW(PERF) 180.5 T
3500 m
CLEAR MODIFY
When the calculated MLW(PERF) is below the LW entered by the User, red dashes “---” are displayed
instead of the output values.
The aircraft cannot land at this Landing Weight. The Landing weight must be reduced at least to
the value of MLW(PERF).
When the “MLW limited by MAX of (F-LD; RLD)” is activated, three landing distance calculations are
performed:
- RLD (Required Landing Distance)
- LD (In-Flight Landing Distance)
- F-LD (Factored In-Flight Landing Distance).
The most limiting of those three landing distances is displayed as the Dispatch LD. The F-LD is
considered as a dispatch limitation.
CLEAR MODIFY
This label gives information regarding the configuration used for the calculation.
The Maximum Performance-Limited Landing Weight MLW(PERF) is the maximum weight that
permits to safely land on the destination runway.
The MLW(PERF) is associated with the Factored Landing Distance (F-LD) when the Landing
Distance Available (LDA) is not limiting. It is associated with the LD when:
The Factored Landing Distance is above the runway length
The Landing is not possible.
VAPP is the aircraft approach speed considered for the landing computation, 50 ft above the runway
surface. VAPP is defined from the Lowest Selectable Speed (VLS), with the addition of a speed
increment due to the wind correction or induced by the effect of autothrust or ice accretion. Its
computation is detailed in the Additional Results page. The administrator must enable the parameter
“Increase Vapp for dispatch” in the PA Admin, in order to display the Vapp, the Vpilot and the approach
correction value.
2.2.1.5. EO GA GRADIENT
The EO GA GRADIENT displayed corresponds to the Approach Climb Gradient, and must be higher
than or equal to the minimum climb gradient entered in the CONDITIONS panel.
The EO GA GRADIENT AT field is displayed only if the Administrator has activated the “Increase Go
Around Height computation” option.
The dispatch landing distance is the most limiting among Required LD (Landing Distance), Factored
LD and LD.
2.2.1.7. Margin
If DISPATCH LD < LDA, the displayed margin is the difference between the runway length and
the dispatch landing distance.
14R
Additional information can also be displayed as shown below. To do so, the Administrator has to select
the requested information in the administrator module.
14R
LDG_CLB_GRAD LD 17.32
Several regulatory requirements can limit the landing performance. The requirements that limit
performance in specific cases are identified in the computation results via limitation codes. The
following table indicates the various codes used for the landing limitations:
2.2.2.2. Speeds
The Required Landing Distance (RLD) is the result of the Actual Landing Distance (ALD) with the
regulatory margins depending on the runway state.
For example, RLD dry = 1.667 * ALD dry.
This RLD must be lower than or equal to the Landing Distance Available on the runway.
The RLD is displayed on the runway graph.
This label gives information regarding the credit of the reversers used for the calculation.
Whenever the ROW Landing Distance is above the Landing Distance Available (LDA) for destination
airport, the message “EXPECTED ROW ALERT” is displayed in the Results panel.
For more information, refer to the part “ROW LDG DIST > LDA” in the chapter Landing Possible in
LANDING RESULTS FOR IN-FLIGHT – OUTPUTS.
The LDG PERF application determines the landing performance for the selection of runways. The User
can access the results for each runway via a title bar displayed on top of the result panel.
It contains:
One cell named Overview: displays a summary of the results for all the runways
MEL 0 CDL 0
MODIFY CLEAR
The list is sorted by weight, from the highest to the lowest, and is color-coded:
- Green when the LW is lower or equal to the MLW(PERF)
- Red when the LW is higher than the MLW(PERF).
One cell for each selected runway: displays the results for this specific runway.
3500 m
LW T 180
EO GA GRADIENT AT 1989 ft 6.9 %
LDG CG CG >27%
LDG CONF CONF FULL
AIR COND On (STD) 10
APPR TYPE Normal (STD) 5
9
GA GRADIENT % Min (STD)
VPilot kt 0
LDG TECH MAN-A/THR on
For each runway, the results are presented in the same way as for single runway computation.
For each runway, the Maximum Performance-Limited Landing Weight (MLW(PERF)) is displayed after
the runway ID.
The list is sorted by weight, from the highest to the lowest, and is color-coded:
- Green when the LW is lower or equal to MLW(PERF)
- Red when the LW is higher than MLW(PERF).
For each runway, the results are presented in the same way as for single runway computation with in-
flight crosscheck.
2. CONDITIONS PANEL
The CONDITIONS panel enables the User to define the outside conditions and the aircraft configuration
data.
When starting the application, all the fields are empty, except those for which the Administrator has
defined standard values.
The field RWY COND provides the different runway states for which the computation is possible. Note
that the selection of some runway conditions may affect the temperature range. The temperature value
may then have to be changed to fit into the defined range.
LW T 182
LDG CG
LDG CONF AUTO CONF (STD)>
AIR COND Off (STD)>
APPR TYPE Normal (STD)>
GA GRADIENT % Min (STD)
VPilot kt 0
LDG TECH MAN-A/THR on >
BRK MODE Manual >
REV Yes (STD) >
In In-flight mode, it is possible to perform an overweight landing computation (i.e. the Landing Weight
exceeds the certified Maximum Landing Weight (MLW)).
If the LW is above the MLW, the message “overweight landing” is displayed on the interface and the
overweight landing procedure, described in the QRH-ABN-80, applies. This procedure implies a
different flare technique and a braking after the nosewheel touch. This procedure lengthens the landing
distance and has therefore been implemented in the modelling.
Tip: The User can enter “*” in the text box to retrieve the MLW.
Note: The LW is automatically retrieved from the LOADSHEET module if a LOADSHEET calculation is
performed.
The Administrator can modify the options to be more explicit (e.g. CG > 27% instead of Standard (basic)
and CG < 27% instead of Alternate for A320 for instance).
LDG CG Close
Notes:
- The LDG CG field is automatically set in accordance with the LDG CG value from the
LOADSHEET module if a LOADSHEET calculation is performed
- The LDG CG is customizable by the user in Admin part (refer to PPM Admin – LDG STD
Values)
- The LDG CG “User’s value” is only available on In-Flight part and for iPad devices from V5.0,
and for Windows devices from L7.2.
The “AUTO CONF” option provides the results relative to the Configuration that permits:
- To land at the Landing Weight in input (if one Conf leads to a landing limited by the performance),
or
- To get the shortest Runway Length (i.e. Conf FULL) if both Configurations permit to land with the
Landing Weight in input.
Note: The Approach Configuration is not accessible as it is linked to the Landing configuration. Landing
configuration FULL gives Approach Configuration 3 and Landing Configuration 3 gives Approach
Configuration 2.
In the particular case of a high altitude airport, the Approach Configuration 1+F can be applied as well
with a Landing Configuration 3, it the “CONF 1+F go-around (High ALT ARPT)” option has been
selected by the user in Admin part (refer to PPM Admin – Engine Options). This option is only available
for A319-115, A319-133, and A350-1041 aircraft models.
For A318 aircraft fitted with steep approach option, if the administrator has ticked the steep approach
box in the Aircraft options of Aircraft details, the user can select a third approach type: Steep Approach.
The User can enter the value of the flight path angle (range: -5.5° to -4.5°).
Tip: The User can enter “MIN” to insert the minimum Gradient value.
This field is displayed in the Conditions panel only if the Autoland option is defined in the aircraft
performance database.
-3.2 X
- If a glide path angle has been defined in the airport database, the User has just to select
Autoland. The glide path angle is in this case fixed and the User cannot modify it.
REV Close
Note: The performance applications Administrator can define standard values for the following fields:
- LDG CONF
- AIR COND
- APPR TYPE
- GA GRADIENT
- LDG TECHNIQUE
- BRK MODE
- REV.
In this case, the default values are displayed with the indication (STD) when opening the LDG PERF
application. For example:
REV Yes (STD) >
If the aircraft is dispatched without any MEL/CDL/ECAM alert item that affects the landing performance,
"MEL 0", “CDL 0” and “ECAM 0” appear on the corresponding buttons.
By clicking on the MEL, CDL or ECAM button, the User can select MEL / CDL and/or ECAM items.
Clicking on one cell displays all the possible ECAM alerts for the concerned system.
The User may then select one or several items, and come back to ECAM ALERTS panel to select other
items.
AIR Close
A.ICE >
AIR > AIR ABNORM BLEED CONFIG
Done
After pressing on the Done button, the ECAM button label is updated with the corresponding number
of selected items.
The selection of an ECAM alert makes the LDG CONF field disappear from the aircraft configuration
panel.
The LDG CONF authorized is then automatically managed by the application.
The User can add and/or delete ECAM ALERTS items by clicking on the ECAM button, then
on the Modify button.
Modify
Note: On A350 and A380 aircraft, the ECAM alerts are automatically sent to the EFB via avionics
synchronization.
During the flight, the User must verify that they can ensure a safe landing at destination.
Depending on the computation results, the landing will be possible, or not possible.
IN FLIGHT Dispatch
22R 14R
Modified
WARNING -570 m
LFMN/NCE NICE/COTE D’AZUR LDG REQUIREMENT NOT
RWY 22R (MODIFIED)
FULFILLED
WIND °/kt (110/15/G20) NOT-AUTHORIZED LANDING LD
2083 m
OAT °C 20
QNH hPa 970 LDG CONF CONF 3
RWY COND 3-Medium
A-ICE Off (STD)
LW 189.0 T 6
LDG CG 32.0
LDG CONF CONF 3 EO GA SPEED 136 kt
AIR COND On (STD)
APPR TYPE Normal (STD)
LD 2083 m
GA GRADIENT % Min (STD)
BRK ENERGY 27 %
VPilot kt 0
LDG TECH MAN-A/THR on
EO GA GRADIENT AT 761 ft 6.3 %
BRK MODE Med 22R
|||||
REV Yes (STD) TIRE SPEED 147 kt
^^^
MEL 0 CDL 0 ECAM 0 MLW(PERF) 179.1 T
CLEAR MODIFY
When the calculated MLW(PERF) is below the LW entered by the User, a warning message is
displayed in red to notify the user that the landing is not authorized. The outputs that are limiting for the
landing are displayed in red.
The aircraft cannot land at this Landing Weight. The Landing weight must be reduced at least to the
value of MLW(PERF).
The LDG PERF application computes the Landing Distance (LD) and Factored Landing Distance (F-
LD) associated to the LW.
Depending on the results found, and on the Landing Distance Available (LDA), the following outputs
are displayed:
- F-LD ≤ LDA
The main results page provides the following data:
IN FLIGHT Dispatch
22R
Margin
174 m
LFMN/NCE NICE/COTE D’AZUR LDG CONF CONF 3 F-LD
2396 m
RWY 22R
MLW(PERF) 207.0 T
LD
WIND °/kt (110/15/G20) 2083 m
OAT °C 20 VAPP 140 kt
QNH hPa 970
RWY COND 3-Medium
A-ICE Off (STD) EO GA SPEED 140 kt 6
2570 m
LW T 189.0 EO GA GRADIENT AT 761 ft 6.3 % 18
LDG CG 32.0
LDG CONF CONF 3
AIR COND On (STD)
APPR TYPE Normal (STD)
GA GRADIENT % Min (STD)
VPilot kt 0
LDG TECH MAN-A/THR on
BRK MODE Med 22R
REV Yes (STD) |||||
^^^
MEL 0 CDL 0 ECAM 0
CLEAR MODIFY
IN FLIGHT Dispatch
22R (MODIFIED)
Modified
-300 m
2270 m
LDG CG 32.0 FACTOR/INCREMENT 1.15
LDG CONF CONF 3
AIR COND On (STD) EO GA GRADIENT AT 761 ft 6.3 %
APPR TYPE Normal (STD)
GA GRADIENT % Min (STD) MLW(PERF) 211.2 T
VPilot kt 0
LDG TECH MAN-A/THR on
BRK MODE Med 22R
REV Yes (STD) |||||
^^^
MEL 0 CDL 0 ECAM 0
CLEAR MODIFY
A warning message is displayed in order to notify the user that the F-LD is above the runway length.
When the ROW LD is above the LDA at the arrival airport, the message “EXPECTED ROW ALERT” is
displayed in the results panel.
IN FLIGHT Dispatch
14L (MODIFIED)
Modified
-1500 m
1500 m
APPR TYPE Normal (STD)
GA GRADIENT % MIN (STD)
VPilot kt 0
LDG TECH MAN-A/THR on
BRK MODE Manual 14L
REV Yes (STD) |||||
^^^
MEL 0 CDL 0 ECAM 0
CLEAR MODIFY
The EO GA SPEED field is displayed only if the Administrator has activated the “Optimize Go Around
Speed” option.
The “EO GA GRADIENT AT” field is displayed only if the Administrator has activated the “Increase Go
Around Height computation” option.
The MLW(PERF) is associated with the Factored Landing Distance (F-LD) when the Landing Distance
Available (LDA) is not limiting.
1.2.8. Margin
If F-LD < LDA and LD < LDA, the margins are displayed in green :
The difference between the runway length and the LD
The difference between the runway length and F-LD.
14R
It contains:
One cell named Overview: displays a summary of the results for all the runways
CLEAR MODIFY
For each runway, the Maximum Performance Limited Landing Weight (MLW(PERF)) is
displayed after the runway ID.
The list is sorted by weight from the highest to the lowest and is color-coded:
- Green when the MLW(PERF) is higher than or equal to the LW
- Red when the MLW(PERF) is lower than the LW.
One cell for each selected runway: displays the results for this specific runway.
LW T 85 EO GA SPEED 140 kt
3500 m
LDG CG % CG >27%
LDG CONF CONF FULL EO GA GRADIENT AT 1989 ft 6.3 % 5
AIR COND On (STD)
9
APPR TYPE Normal (STD)
GA GRADIENT % Min (STD)
VPilot kt 0
LDG TECH MAN-A/THR on
BRK MODE Manual (STD)
REV Yes (STD)
14R
MEL 0 CDL 0 ECAM 0 |||||
^^^
CLEAR MODIFY
For each runway, the results are presented in the same way as for single runway computation.
2400 m
A-ICE Off (STD)
10
LW T 182
9
LDG CG CG >27%
AIR COND On (STD)
APPR TYPE Normal (STD)
GA GRADIENT % Min (STD)
VPilot kt 0
LDG TECH MAN-A/THR on
BRK MODE Manual
REV Yes (STD) 14R
|||||
^^^
MEL 0 CDL 0 ECAM 1
CLEAR MODIFY
For other in-flight failures (that permits a landing in Conf FULL or Conf 3), both flaps lever positions are
displayed.
The results displayed in the results panel then correspond to the flaps lever position selected by the
User with the FLAPS FULL / FLAPS 3 buttons.
The MLW(PERF) is associated with the Factored Landing Distance (F-LD) when the Landing Distance
Available (LDA) is not limiting.
3.1.6. Margin
If F-LD < LDA and LD < LDA, the margins are displayed in green :
The difference between the runway length and the LD
The difference between the runway length and F-LD.
14R
14R
Note:
APPR COR = VAPP – Vref - ∆Vref - ∆Vpilot
However LDG PERF performs the computation in CAS with 3 decimals precision, then the speeds are
converted in IAS and rounded for display.
As a consequence, due to the conversion and the rounding of the speeds, APPR COR displayed can
be 1kt above or below VAPP – Vref - ∆Vref - ∆Vpilot.
Note:
The LDG PERF application always computes MLW(PERF) limited by the Approach Climb Gradient with
One Engine Inoperative (OEI). The effect of an ECAM alert is not taken into account on Approach Climb
Gradient calculation.
For failures with a landing configuration required (e.g. FLAPS LVR POS 2), go-around performance is
always computed with flaps 3.
For failures with a landing configuration not required, go-around performance is computed with:
- Flaps 3 for landing flaps FULL, or
- Flaps 2 for landing flaps 3, in non-overweight, or
- Flaps 1+F for landing flaps 3, in overweight.