Flysmart+ For Ipad Applications V4.3: Release Note - Reva

FLYSMART+ FOR
IPAD*
APPLICATIONS V4.3
RELEASE NOTE – RevA
06 JAN 2020
* iPad is a trademark of Apple Inc

2 FLYSMART+ FOR IPAD* – APPLICATIONS V4.3 - RELEASE NOTE – RevA – 06 JAN 2020
Reference RN-FSAI20200106
Confidentiality Flysmart+ Customers ONLY
Summary
The Release Note is a document designed for the Flight Operations Engineering and Training
departments of the airlines. This document gathers information on the delivered Apps version,
to be shared with the end-users (pilots, instructors, Operational Control Centre…) and people
working on the administration part (documentation, performance generation…).
The Release Note highlights the evolutions and corrections contained in the corresponding
Apps version and a selection of new and existing limitations, having an operational impact or
interest for the different users of the Apps.
This Release Note also provides operators with information regarding the compliance
documents associated to this Flysmart+ for iPad Apps version to help the operators get their
operational approval (initial or revision) from their National Aviation Authority.
©NAVBLUE SAS 2020. All rights reserved. Confidential and proprietary document.
Printed Copies are not controlled. Confirm this is the latest issue available through the Portal.
RECORD OF REVISIONS
Revision Date Chapters Description of Changes
RevA 06 JAN 2020 All Initialization of the document for Flysmart+ Apps V4.3 delivery.
TABLE OF REFERENCES
N° Title Reference Issue Date

[REF 1] Flysmart+ User and Compliance Manual X46RP1730572 2.2 26 NOV 2019
[REF 2] EASA OSL TE.GEN.00101.004 - 16 DEC 2019
[REF 3] FAA OSL - - 08 JAN 2020
Flysmart+ for iPad Apps V4.3 – Installation
[REF 4] IG-FSAI2020106 RevA 06 JAN 2020
Guide
LIST OF ACRONYMS
Acronym Definition
AC Advisory Circular
ACC ACCeleration
AECG All Engine Climb Gradient
AFM Airplane Flight Manual
ASDA Accelerate Stop Distance Available
ATA Air Transport Association
CAS Corrected Air Speed
CDL Configuration Deviation List
CG Centre of Gravity
EASA European Aviation Safety Agency
ECAM Electronic Centralized Aircraft Monitoring
EFB Electronic Flight Bag
ENG Engine
EO Engine Out
eQRH electronic Quick Reference Handbook
FAA Federal Aviation Administration
FAQ Frequently Asked Questions
FCOM Flight Crew Operating Manual
FL Flight Level
FLD Factored Landing Distance
FSTA Future Strategic Tanker Aircraft
GA Go Around
G/S Glide Slope
IFPA In-Flight Performance Application
Acronym Definition
iOS Apple Operating System
iPadOS Apple Operating System specific to iPad devices
lbs pounds
LD Landing Distance
LDPA Landing Performance Application
L/G Landing Gear
LW Landing Weight
MCT Maximum Continuous Thrust
MEL Minimum Equipment List
MLW Maximum Landing Weight
MMO Maximum Operating Mach
MRTT Multi Role Tanker Transport
MTOW Maximum TakeOff Weight
N/A Not Applicable
NAA National Aviation Authority
NM Nautical Mile
OEI One Engine Inoperative
OLB Ops Library Browser
OSL Operational Suitability Letter
P&W Pratt & Whitney
PAAdmin Performance Applications Administration Tool
PDF Portable Document Format
PEP Performance Engineer Program
PFC Porous Friction Course
QFU Magnetic Runway Heading
QNH Pressure Altitude at sea level
QRH Quick Reference Handbook
RA Radio Altitude
RED REDuction
REV REVerser
THR THRottle
TLO Takeoff and Landing Optimization
TO TakeOff
TODA TakeOff Distance Available
TOPA TakeOff Performance Application
TOW TakeOff Weight
UCM User Compliance Manual
VAPP Final Approach Speed
VMO Maximum Operating Speed
WBA Weight and Balance Application
WoB Weather on Board App
TABLE OF CONTENT
1. INTRODUCTION ......................................................................................................... 6
2. PRODUCT IDENTIFICATION ..................................................................................... 8
Name and Version .......................................................................................................... 8
Date of release ................................................................................................................ 8
3. APPLICABILITY AND COMPATIBILITY .................................................................. 10
Applicability .................................................................................................................. 10
Integrated Applications ................................................................................................ 10
Hardware and Software Requirements........................................................................ 10
4. WHAT’S NEW ........................................................................................................... 13
5. WHAT HAS BEEN CORRECTED ............................................................................. 15
Installation / Update ...................................................................................................... 15
General .......................................................................................................................... 15
Performance and Weight & Balance ............................................................................ 15
Ops Library Browser .................................................................................................... 19
6. WHAT ARE THE LIMITATIONS ............................................................................... 21
Installation / Update ...................................................................................................... 21
General .......................................................................................................................... 22
Performance and Weight & Balance ............................................................................ 22
Ops Library Browser .................................................................................................... 35
7. OPERATIONAL APPROVAL/AUTHORIZATION CONSIDERATIONS .................... 38
User and Compliance Manual ...................................................................................... 38
Operational Suitability Letters ..................................................................................... 38
Management of Changes to Flysmart+ ....................................................................... 39
From V4.2.1 to V4.3 ....................................................................................................... 39
8. CUSTOMER SUPPORT ............................................................................................ 41
1. INTRODUCTION
The Release Note is a document designed for the Flight Operations Engineering and Training
departments of the airlines. This document gathers information on the delivered Apps version,
to be shared with the end-users (pilots, instructors, Operational Control Centre…) and people
working on the administration part (documentation, performance generation…).
The Release Note highlights the evolutions and corrections contained in the corresponding
Apps version and a selection of new and existing limitations, having an operational impact or
interest for the different users of the Apps.
This Release Note also provides operators with information regarding the compliance
documents associated to this Flysmart+ for iPad Apps version to help the operators get their
operational approval (initial or revision) from their National Aviation Authority.
PRODUCT IDENTIFICATION
CHAPTER 02
2. PRODUCT IDENTIFICATION
Name and Version
Flysmart+ for iPad Apps V4.3 includes:
• FS+ Manager V4.3
• FS+ Takeoff V4.3
• FS+ Landing V4.3
• FS+ In-Flight V4.3
• FS+ Loadsheet V4.3
• FS+ OLB V4.3
The performance modules referenced above include the OCTOPUS core software V38.0.1.
Date of release
Flysmart+ for iPad Apps V4.3 have been delivered on the AppStore in January 2020.
APPLICABILITY AND
COMPATIBILITY
CHAPTER 03
3. APPLICABILITY AND COMPATIBILITY

Applicability
• A320 family including:
o A320neo P&W and CFM
o A320neo SHARP
• A330 including:
o A330 MRTT & FSTA
o A330neo -800 and -900
• A340
• A350-900 and -1000
• A380.
Integrated Applications
The following Apps have been designed and validated to be easily integrated with Flysmart+ for
iPad:
• NAVBLUE eQRH
• NAVBLUE eFF+
• Honeywell Weather on Board (WoB)
The delivery of these Apps depends on the contract of the operator.
Note 01
The eQRH and Weather on Board (WoB) integrations are exclusive. The compatibility between the
eQRH and WoB will be addressed in future versions of the Apps.
Hardware and Software Requirements

Installation procedure
Please refer to Flysmart+ for iPad Installation Guide [REF 4].
Minimum system requirements for EFB hardware & Operating System

Please refer to Flysmart+ for iPad Installation Guide [REF 4].
WARNING 01
THE NEW FLYSMART+ APPS V4.3 ARE NOT COMPATIBLE WITH EQRH V1.0.6 AND
EQRH V2.0.1.
THE CUSTOMERS THAT INTEND TO USE FLYSMART+ APPS V4.3 NEED TO INSTALL
EQRH V3.0 OR FOLLOWING VERSIONS.
WARNING 06
APPS V4.3 ARE COMPATIBLE WITH eQRH V3.0.0.
HOWEVER, CUSTOMERS OPERATING APPS V4.3 AND EFF+ V1.1.0 MUST USE eQRH
V3.1.0.
For a complete view of compatibilities, please refer to the EFB_Compatibility_Matrix.xlsx file

delivered in the Flysmart+_Apps_V4.3.zip package and also available on the NAVBLUE Support
Portal.
WHAT’S NEW
CHAPTER 04
4. WHAT’S NEW
This section describes the functional changes brought to version V4.3 in comparison to the
previous version V4.2.1.
General
• Integration with eFF+
The Flysmart+ for iPad Apps V4.3 bring communication capabilities with NAVBLUE eFF+
V1.1.0.
Performance
• Integration of Octopus V38.0.1
The Flysmart+ for iPad TakeOff and Landing Performance Apps V4.3 integrate the new
performance computation engine Octopus V38.0.1.
• Enhancement of inputs and results display when only TOGA take-off is possible
In the TakeOff Performance Application, in SINGLE RESULTS mode, when FLEX takeoff is
requested by the User but only TOGA is possible, the inputs panel and the results page are
modified to show and highlight the TOGA rating.
• Display of the TO Shift value on the runway illustration on the results page
Fixes
Refer to chapter 5 WHAT HAS BEEN CORRECTED
WHAT HAS BEEN CORRECTED
CHAPTER 05
5. WHAT HAS BEEN CORRECTED

This section describes the major corrections included in version V4.3 in comparison to the previous version V4.2.1.
Installation / Update
No limitation has been corrected in this section for this version.
General
Title Description Operational Consequences Apps Aircraft*
Native iPadOS The native iOS / iPadOS copy/paste feature is not working in the The User cannot copy the Gateway Server URL Manager All
copy/paste FS+ Manager App fields. provided in a document or email then paste it in the
FS+ Manager App Server field.
Performance and Weight & Balance

Incorrect airport in When a city pair is set up in the My Flight page, but a different The Performance Administrator analyzing the XML TakeOff All
TakeOff or Landing airport is selected and used in the TakeOff or Landing report may believe an incorrect airport is used for Landing
computation report Performance Applications, the XML report still displays the the computation.
airports selected in the My Flight page.
files
Takeoff The Airbus Standard Operational Procedure (SOP) indicates The computed vertical flight path may be higher TakeOff All
computation with that when the Air Conditioning is set to OFF at takeoff, the flight than it should be. As a result, the AECG capability
AECG enabled and crew shall set the Air Conditioning to ON when the aircraft may be slightly overestimated.
reaches the thrust reduction altitude.
Air Conditioning
OFF is not in line However, Flysmart+ considers the Air Conditioning OFF for the
complete takeoff.
with Airbus
Standard
Operational
Procedure

QNH climb speed When the climb speed limit altitude is entered in the Airport The User may not understand the reason why TakeOff All
limit altitude value Manager and expressed as a QNH altitude, it is incorrectly FL10000 is displayed instead of FL100.
displayed with FL displayed in the 3rd page of results in the TakeOff Performance
Application and in the AECG data pop-up window.
prefix
The prefix "FL" is added in front of the QNH value.
For example, when the constraint for the climb speed limit is
10000 ft in the Airport Manager, the TakeOff Performance
Application displays FL10000.
Check AFM When performing a computation on a PFC / Grooved runway, The computation will not provide results in these TakeOff A320
information the TakeOff Performance Application may abort the computation conditions. Family
message on PFC / and alert the pilot with a computation error related to the
CheckAFM module.
Grooved
computations
Dispatch - When the User performs landing computation in dispatch mode The results are slightly conservative. Landing A350
Reversers are not without in-flight crosscheck the thrust reversers are considered
operative for inoperative on wet PFC-grooved runways.
computations on
grooved - Wet
runways
Landing in-flight When an in-flight landing calculation is performed on a wet The results are slightly conservative. Landing A320Neo
performance runway, Flysmart+ always computes landing distances above A330Neo
computation may the landing distances computed by the AFM. A350
be too conservative
on wet runways

Incomplete error When an ECAM item inhibits a flight function, but the function is The error message may mislead the user on the Landing All
message in case of selected in the inputs, then an error message is displayed. reason of the computation error.
incompatibility In some cases, the content of this error message is incomplete.
For example, for A318 aircraft with ECAM NAV - RA1 FAULT
between the ECAM
that forbids to use the steep approach mode, the following
and the selected message is displayed:
inputs
The additive message, that explains why the computation cannot

be performed, is not displayed.
Altitude Rule In the PLAN module of the In-Flight Performance Application, The User may not understand the results provided In-Flight All
misbehavior in with a Flight Plan computation type and Cost Index speed type, by the PLAN module.
Flight Plan mode the current engine addressing induces that only the Flight Levels
equal to or greater than the one chosen by the User are
addressed to the computation engine.
If this altitude cannot be reached for the first cruise segment, the
latter is set at the maximum altitude that can be reached in
climb, therefore it can be a random FL not included in the
altitude rule considered.
Never ending For A319-132, when performing a computation with ENG The computation never ends, and the User can’t get In-Flight A319
computation OPERATIVE = 1 and LRC SPEED = SPD TYPE, the computation results.
computation enters an infinite loop.

PAX and CARGO In the DETAILED entry mode, when more than one configuration The results of the new computation do not match Loadsheet All
inputs not cleared is allowed for an aircraft, after performing an initial computation the inputs displayed.
when changing with one configuration, and then changing to another
configuration, the following wrong behavior is observed:
aircraft
configuration 1- The previous PAX and CARGO fields keep the previous
values when they should be cleared but the PAX and
CARGO distributions are cleared
2- The new computation is done with PAX and CARGO
values set to 0.
PAX PER TYPE In REDUCED entry mode, when using customized loadsheet The User may not understand why the value Loadsheet All
values not template to display the PAX PER TYPE, the value is not entered in the loadsheet report is not displayed.
displayed in displayed in the final loadsheet.
reduced mode
Ops Library Browser

Title Description Operational Consequence Aircraft*
No more DU when When browsing a manual applicable to ALL aircraft (example, The User may believe there is no more data to consult in the All
swiping Operating Manual part A), when the User wants to swipe from a manual.
DU to another, the message “Information, no more DU” is
displayed.
CDL items length When the User ticks a CDL item and that the value is a length The User has no information on the value to be entered. All
management (example, missing seals), the User can only enter integers.
A320 AFM OR Depending on the operator number of aircraft and aircraft The User may not be able to display the AFM or MEL LEDU. A320
MMEL LEDU configurations, the AFM or MMEL LEDU may take time to Family
display display or lead to the crash of the OLB App.
WHAT ARE THE LIMITATIONS
CHAPTER 06
6. WHAT ARE THE LIMITATIONS

Most important limitations applicable to this version are listed in the tables below. The operator should study them carefully and inform the flight crews accordingly.
Works-around or mitigations implying pilot action are highlighted in a specific column. The new limitations appearing in this Flysmart+ version (not existing in the
previous versions), are highlighted with the New! in the title column.
Installation / Update
Work-around/
Title Description Operational Impact Work-around / Mitigation Mitigation implying Apps Aircraft*
pilot awareness
New! When installing the eFF+ The User may not be able to Reinstall the FS+ Manager App. YES Manager All
FS+ Manager V1.1.0 App, then upgrading install the data in the FS+ Apps.
App crash the FS+ Apps V4.2.x to FS+
Apps V4.3, the FS+ Manager
App may crash when the
Update all button is selected.
Impossible to Sometimes at the end of None Restart the FS+ Manager App. YES Manager All
close "Update release update, the pop-up
finished" pop- “update finished” cannot be
up message closed and blocks the FS+
Manager App.
In any case the release is
successfully installed.
General
Work-around/
Title Description Operational Consequences Work-around / Mitigation Mitigation implying Apps Aircraft*
pilot awareness
Aircraft When the User selects an None In such case, the User has to YES OLB All
registration not aircraft on the My Flight page select the aircraft on the My
sent to OLB of one performance App, the Flight page of OLB.
OLB may not retrieve it when
the user displays OLB (My
Flight page of OLB is empty).
Performance and Weight & Balance

Work-around/
Title Description Operational Consequence Work-around / Mitigation Mitigation implying Apps Aircraft*
pilot awareness
New! When Flysmart+ TakeOff or The User must restart the None NO TakeOff All
Takeoff and Landing Performance performance application. Landing
Landing Applications are not used for
applications an inactivity period set in the
may crash after PAAdmin preferences, then
an automatic an automatic clear of the
clear inputs and the results is done.
The Performance Applications

may crash after the automatic
clear.
Work-around/
pilot awareness
New! For takeoff and landing The User cannot compute A330- Use the equivalence of 6 mm YES Landing A330-300
Takeoff and computations on dry snow 50 300 aircraft performance in case slush for Dry Snow 50 mm.
Landing mm & 100 mm runways, of a runway contaminated by dry For Dry Snow depth equal or
computations Octopus computation engine snow 50 mm & 100 mm. above 51 mm, no operations.
on Dry snow 50 does not provide any result
mm & 100 mm and delivers an error message
does not "No optimal weight is found".
provide results
for A330-300 The Dry Snow 50 mm &
aircraft 100 mm runway states
models was not correctly
addressed between the a/c
performance database and
the CPDF file.
Work-around/
pilot awareness
New! This limitation occurs for: The computed Required Landing None NO Landing A320
MOD 25225 is - Landing dispatch Distance may be conservative. Family
not taken into computations
account for - With FMS speeds
Landing - When the MOD
Dispatch 25225 is enabled.
computations
with FMS In this case the Approach
speeds correction is the maximum of
the following:
-5 kt (if A/THR ON) + 1/3
Headwind*
-5 kt if ice accretion in
CONF FULL
CONF 3.
The approach correction with

the MOD 25225 enabled
should have been the
maximum of the following:
-5 kt (if A/THR ON)
-1/3 Headwind*
CONF FULL
CONF 3.
New! If the PAX PER CLASS field It is not possible to export the The Pax per class field is not a YES Loadsheet All aircraft
Loadsheet contains more than two loadsheet if more than 2 classes mandatory input for the with more
cannot be classes (i.e. the format of the are set in the pax per class field. loadsheet generation. As a than 3
exported if the input is xx/xx/xx according to result, the user can leave the Pax classes
user indicates F/B/Y classes), then the per class field empty. defined in
more than 2 generate button is inactive. the W&B
classes in the data
Pax per class
field
Work-around/
pilot awareness
Transition The Airport Manager v3.7 The Flysmart+ result page Modify in Flysmart+ the related YES TakeOff All except
altitude not (Available in PEP 5.11) provides the AECG results in constraints in FL. In this case the wide body
taken into introduces the transition QNH altitude and not in Pressure computation considers the
account by altitude for the management altitude 1013 hPa. constraint as a pressure altitude
Flysmart+ of the AECG constraints for As a result, there may be a (FL).
PEP-TLO module. difference between the results
In the Airport Manager v3.7 obtained from a takeoff chart and
database, it is not possible to the ones from Flysmart+.
enter a FL as AECG target
altitude.
Flysmart+ does not take into
account the transition altitude
parameter. As a result,
previous altitudes constraints
entered in FL in the airport
manager are used as QNH
altitudes.
Number of ALL In the case of a modified The additional AECG constraints None N/A TakeOff All
ENGINE CLIMB runway, for which the User are still calculated.
GRADIENTS not added new AECG constraints,
cleared after a if the User restores the
restore runway, then the AECG
constraints that were added
are not deleted.
If other runway characteristics
were modified, the restore
function correctly resets these
data to the original values.
CDL items seen Some CDL Items selected in The performance impact is not It is necessary to select the YES TakeOff All
as negligible the OLB may be seen with no taken into account for the impacted CDL item directly in the Landing
performance impact. computation. performance applications.
Example: CDL 27-01.
Work-around/
pilot awareness
Truncated or In case the runway name The complete QFU identifier is In both cases, the runway name NO TakeOff All
removed contains more than 3 not available on the runway is correctly displayed on top of Landing
runway name characters, the runway name drawing. the runway.
on graphical is truncated on the graphical
display display of the runway.
In case the runway

intersection name contains
more than 5 characters, the
blue bullet associated to
runway intersection is
removed on the graphical
display of the runway.
CLEAR action In Takeoff or Landing The user loses the airport Set the airport in Takeoff or YES TakeOff All
resets the applications, when the change if he uses the clear Landing again after the clear. Landing
AIRPORT if AIRPORT is different from the button.
different from airport set in the "My Flight"
"My Flight" page, the use of the CLEAR
page button sets the AIRPORT to
the one defined in the "My
Flight" page.
SURFACE field In Takeoff and Landing Apps, The user cannot restore the Close Takeoff or Landing and YES TakeOff All
no longer if a runway for which the original SURFACE value. reopen the App. Landing
available in the SURFACE is defined as
runway grooved/PFC in the
modification administrator tool is modified
panel after user to Smooth, then the
change. SURFACE field disappears
from the interface and it is not
possible to switch the
SURFACE back to
Grooved/PFC.
Work-around/
pilot awareness
EO GA Gradient The EO GA Gradient value is If the EO GA Gradient value is In case of a non-authorized YES Landing All
value is rounded rounded to the closest value. just below the limit (e.g. 2.96% landing (Red case), if the GA
to the closest for a 3% requirement), then the Gradient is displayed in Red, but
value instead of landing is not authorized. still matches the minimum
the lower value. However, the EO GA gradient required value, this means that
value is rounded to the same the exact value of the GA
value as the limit and the user gradient is below the displayed
may not understand why the value (max difference is 0.05%)
landing is not authorized. and is indeed limited.
The ECAM alert The ECAM alert ENG 1(2) The user cannot select the The User must set REV input as YES Landing A320
ENG 1(2) THR THR LEVER FAULT is ECAM. As a result, the NO in the Landing App. Family
LEVR FAULT is missing in the ECAM list (not application does not consider
not provided in yet available in “landing fail” that the associated thrust
the ECAM list file). reverser is inoperative.
When this ECAM alert occurs,

the associated thrust reverser
is inoperative.
For A380 and For A380 and A340 aircraft, The performance penalty is lower In this case, the flight crew must YES Landing A380
A340 aircraft, when the MEL items that than it should be. set the number of Inoperative A340
when the MEL affect the Body or central gear Body or central Brakes, directly
items that affect brakes configuration are inside the MEL item selection
the Body or selected in OLB, the panel of the performance
central gear performance penalty sent to Application.
brakes the performance application
configuration may not be taken into account
are selected in (displayed as “No
OLB, an performance impact” in the
incorrect performance application).
performance
penalty is
applied.
Work-around/
pilot awareness
Possibility to In the Landing App, if no value An incorrect reverser setting may Fill all the inputs before launching YES Landing All
launch a has been set by default for be used for the computation. the computation.
computation REV in the administrator tool,
with no value in the User has the possibility to
REV field launch a computation with the
REV field empty. In this case,
the value used for the
computation is Yes.
Impossible to If a runway has a glide slope The user cannot perform In Airport Manager, remove all YES1 Landing All
compute (G/S) value defined in the computations with autoland on glide slope information from any
landing with airport database, the runways for which the G/S is set runway data.
autoland on a computations set with the in the airport database. As a default value, the
runway with a autoland landing technic application will consider -3°.
defined Glide cannot run. However, the User can modify it
Slope value in the landing application.
A340-300 When both in-flight failures The Landing App provides No workaround necessary, NO Landing A340-300
ENG 1 & ENG 4 ENG 1 SHUTDOWN and results on the safe side (higher results provided by the App are
SHUTDOWN ENG 4 SHUTDOWN are VAPP and longer FLD). These on the safe side.
with ICE ACC selected, and in case of ice results can be used for landing
incorrect DVref accretion, the application performance assessment. Then
returns DVref=15kt. the approach can be done with
the VAPP calculated as per QRH
As per QRH, for ENG 1+4 (using DVref=10kt).
SHUTDOWN with ice
accretion, DVref=10kt.
Dispatch - When the user performs The results are slightly N/A NO Landing All
Reversers are landing computation in conservative.
not operative for dispatch mode without in-flight
computations cross check the thrust
on grooved - reversers are considered
Wet runways inoperative on wet PFC-
grooved runways.
1 Provided that the airline administrator has applied the corresponding work-around.
Work-around/
pilot awareness
The check AFM When the administrator has The user cannot perform landing None. N/A Landing All
may reject the entered some performance computations with the
landing results degradations in the PAADMIN performance degradations that
when some tool, the Landing computation were chosen in the PAAdmin.
performance could in some cases, raise the
degradations following error message due
are set in the to an inappropriate Check
PAAdmin AFM:
Parameters The TOW and LW The user may perform a The user must perform a new YES TakeOff All
exchanged communicated from WBA to computation with an incorrect computation with the application Landing
between TOPA and LDPA are not reset weight (with TOPA and LDPA) or that was closed, in order to reset Loadsheet
Flysmart+ to the maximum structural an incorrect weight limitation the values in the other
applications not weight when WBA is closed (with WBA). applications.
reset when an and reopened, although WBA The user can also manually set
application is is cleared. the correct weight in TOPA and
closed and The same behavior occurs for LDPA, or the weight limitation in
reopened TOPA and LDPA: when the WBA.
application is closed and
reopened, the MTOWperf and
MLWperf communicated to
WBA are not reset although
the results and the inputs are
cleared in TOPA and LDPA.
Work-around/
pilot awareness
Parameters The TOW and LW The user may perform a The user must perform a new YES TakeOff All
exchanged communicated from WBA to computation with an incorrect computation with the application Landing
between TOPA and LDPA are not reset weight (with TOPA and LDPA) or that was closed or cleared, in Loadsheet
Flysmart+ to the maximum structural an incorrect weight limitation order to reset the values in the
applications not weight when WBA is closed, (with WBA). other applications.
reset when an or the clear button is used in The user can also manually set
application is the WBA application. the correct weight in TOPA and
closed, or when The same behavior occurs for LDPA, or the weight limitation in
the clear button TOPA and LDPA: when the WBA.
is used application is closed, or the
clear button is used, the
MTOWperf and MLWperf
communicated to WBA are
not reset.
Weight and CG In Takeoff and Landing, when The user may compute the In the takeoff/landing YES TakeOff All
in takeoff and the AIRPORT is different from performance with the default applications, set the airport to the Landing
landing the airport in the My flight weight and CG values instead of same value as the My Flight Loadsheet
applications is page, the synchronization of the values computed by the Page. Then switch from the
not weight and CG between Loadsheet application. Takeoff or Landing application to
synchronized Loadsheet and the Loadsheet and switch back to
with Loadsheet Takeoff/Landing is stopped. the Takeoff or Landing
values after the If the User sets back the application.
airport is airport in Takeoff/Landing with The link between the loadsheet
modified and set the same value as in the My and the takeoff/landing
back to the "My flight page, the TOW/LW and applications will be re-
Flight" page the TO CG / LD CG are filled established and the TOW/LW
value with the default admin values and TO CG/LD CG computed by
instead of the values Loadsheet will be set in the
computed by Loadsheet. inputs of the takeoff/landing
applications.
Work-around/
pilot awareness
Removal of the If the User selects or deselect All the MEL/CDL items that were The User must select once again YES TakeOff All
MEL/CDL items MEL/CDL items via the OLB, selected via the performance the MEL/CDL items via the Landing
selected via the then all the MEL/CDL items applications are deselected. performance applications. Loadsheet
performance that were previously selected
applications via the performance
when MEL/CDL applications are deleted.
are selected via
the OLB
No Pax In REDUCED entry mode, the The User may not understand Use the loadsheet in DETAILED YES Loadsheet All
distribution in PAX distribution per cabin why the value entered in the mode.
the loadsheet zone is not displayed in the loadsheet report is not displayed.
report final loadsheet.
Error message if When no cargo type is defined The User cannot set any cargo It is mandatory to define at least NO Loadsheet All
no cargo in PAAdmin, the cargo input is for the loadsheet computation. one cargo type for any loadsheet
defined not possible in the Loadsheet customization on the PAAdmin
App. tool.
Customized When using a customized The User cannot perform the Use default Airbus template. NO Loadsheet All
Loadsheet Issue Loadsheet (detailed), the loadsheet computation.
Loadsheet App crashes upon
generation.
Discrepancy of If the user performs a PLAN The flight level at top of climb If the provided flight level at top YES In-Flight All
the initial Flight computation and sets a cruise may not correspond to the of climb does not correspond to
Level for a altitude above the aircraft’s selected altitude rule. the altitude selected in the input,
PLAN capacity at top of climb, IFPA reduce the cruise altitude in the
computation should display an error inputs to a Flight Level that:
message. - Is below the provided
However, IFPA provides a flight level at top of climb,
flight profile and sets the initial - Corresponds to the
Flight Level to the maximum chosen altitude rule.
achievable altitude.
Work-around/
pilot awareness
Limited CAS When a new aircraft is added Impossible to compute when the In PA ADMIN, enter VMO & YES In-Flight All
and MACH in the PA ADMIN tool, the speed is higher than the max MMO in the Max speed for L/G
range for new range of CAS and MACH (at speed defined for the L/G Doors Doors Open.
A/C least for the climb) checked in Open. Be careful, with this mitigation
Flysmart+ is limited by the the computation becomes
max speed defined for the L/G possible up to VMO & MMO in
Doors Open. case of L/G Doors Open.
The export In the PLAN module, if the The User cannot export the result Select another in-flight YES In-Flight All
button User performs a computation, of another PLAN computation. computation module and perform
disappears after then exports the report, then a calculation, then select the
a PLAN the export button disappears. PLAN module. The export button
computation is available again.
report is sent
Incorrect When the alternative units for The results are not provided When the User uses the YES In-Flight All
behavior of the the aircraft weight (e.g. weight directly, the User must apply the alternative units, the value is
in-flight entered in kLbs when the workaround described here after. converted to the default unit and
application default unit is tons) or for the both values are displayed in the
when the altitude (e.g. altitude entered input field.
alternative units in meters when the default The User can then replace the
are used unit is feet), the application value in alternative unit by the
may not provide results. converted value and relaunch the
computation. The results will then
be provided.
Discrepancy of If the user performs a PLAN The flight level at top of climb If the provided flight level at top YES In-Flight All
the initial Flight computation and sets a cruise may not correspond to the of climb does not correspond to
Level for a altitude above the aircraft’s selected altitude rule. the altitude selected in the input,
PLAN capacity at top of climb, IFPA reduce the cruise altitude in the
computation should display an error inputs to a Flight Level that:
message. - is below the provided
However, IFPA provides a flight level at top of climb
flight profile and sets the initial - corresponds to the
Flight Level to the maximum chosen altitude rule.
achievable altitude.
Work-around/
pilot awareness
Computation of For the A350 aircraft, the The User cannot determine the None N/A In-Flight A350
Descent with Descent OEI computation will in-flight performance with these
One Engine fail if the A-ICE and AIR anti-ice and air conditioning
Inoperative is COND input are set as systems settings.
not possible for follows:
some • A-ICE = TOTAL AND
combinations of AIR COND =
Anti-ice and air o LO
conditioning o NORM
o HI
• A-ICE = Severe icing
(and any AIR COND
setting)
PLAN For A320 family aircraft, the The User cannot determine the None N/A In-Flight A320
computation not In-flight computation PLAN in-flight performance with this air family
possible with fails if the User sets the AIR conditioning system setting.
Air Conditioning COND input to High.
High for A320
family aircraft
Fuel allowance For PLAN ALTERNATE or The results do not take into None N/A In-Flight All
not correct for FLIGHT PLAN computation account the fuel that was used
PLAN types, if the User sets the for the taxi.
computation aircraft weight in kLbs, (with
with the weight kLbs set as main unit in the
set in kLbs PAAdmin, or by using the
alternative units) then the fuel
allowance for the taxi that is
set in the PAAdmin may not
be taken into account.
Incorrect Thrust In the DESCENT OEI module, The Thrust set to MCT may None N/A In-Flight All
value for DES if the user sets the number of mislead the User.
OEI with all operative engines to 0, the
engines Thrust is set to MCT, instead
inoperative of idle.
Work-around/
pilot awareness
Incorrect unit The unit label for the specific The incorrect unit label may None N/A In-Flight All
label for the range result in the Cruise mislead the User.
Specific range module is always
value for NM/1000Lbs, even when the
CRUISE default unit for aircraft weight
computations is Tons.
performed in However, the value is always
tons correct and corresponds to
the unit selected in the
PAAdmin.
Ops Library Browser

Work-around/
Title Description Operational Consequence Work-around / Mitigation Mitigation implying Aircraft*
awareness
The CDL pop-up In the CDL manual, for several The flight crew may be disturbed by In the CDL manual the Yes All
(message + CDL items (aircraft seals) the user the CDL pop-up wording and wonder “Performance Impact” section of
keyboard) to must enter in the application a what is the expected value to be CDL items specifies when the
select the length missing. Therefore, for inserted. performance degradation needs to
number of these specific CDL items, the be considered per length missing.
items, does not performance degradations are For such items, the user needs to
consider calculated with regards to the enter in the application a length
measured CDL CDL length missing. The pop-up missing (integer value in meter)
items. currently requests the user to without considering the pop-up
enter a number of items missing. wording requesting for a number of
units missing.
A MEL item In the OLB, if the following occurs: The user may not realize that the MEL Always select one MSN in the OLB YES All
selected in the - ALL is selected instead of item is not selected in the application. initialization page.
OLB may not be one MSN in the OLB
transferred to initialization page
the performance - the user selects only one
application if MEL item
ALL is selected - The performance
instead of one application is OFF
MSN Then the MEL item is not
transferred when the performance
application is launched.
Content width When scrolling or zooming in a All the content is not visible after the Do not rotate the iPad during YES All
display after content displayed in portrait rotation of the iPad. current content display.
rotating the iPad mode, and after rotating the iPad
to landscape mode, the procedure
does not display in full width.
Some result not Searches using “OR” operators The User may not find all the desired None YES All
found when use do not always display all the searched information.
the search expected results.
operator “OR”
Work-around/
Title Description Operational Consequence Work-around / Mitigation Mitigation implying Aircraft*
awareness
CDL - 57-01 The "ATA 57 01 - Wing tip fence" The CDL item may be seen as a Select the CDL item directly in the YES A320 family
Complete Wing CDL item may be considered as “negligible item” in the Performance performance application to take into
Tip Fence "negligible item" when selected Apps and no performance penalty is account the performance penalty.
missing/A from OLB and "performance added for calculation.
impacting" when selected from
TOPA or LDPA applications.
CDL - 52-12 The "ATA 52-12 - Forward Cargo The CDL item is seen as a “negligible Select the CDL item directly in the YES A330/A340
Forward Cargo Door " CDL item is considered as item” in the Performance Apps and no performance application to take into
Door "negligible item" when selected performance penalty is added for account the performance penalty.
from OLB and "performance calculation.
impacting" when selected from
TOPA or LDPA applications.
Search issue Searches using non-latin The User may lose the context of the Do not use space with non-latin YES All
with non-latin characters and a space App. characters for the search.
characters characters takes the OLB App
down.
Deletion then In OLB, when the user deletes the The User may consider the selected To activate again an MEL item that YES All
tick of MEL list of inoperative MEL items, he item as not activatable. has been deleted, tick twice on the
items into OLB has to tick twice to reactivate the item reference number.
items that have been deleted.
No ECAM In OLB, ECAM search for A320 None Use the word search. YES All
search Family and A330/340 does not
work.
The Airbus manuals do not

contain associated contextual
data.
OPERATIONAL
APPROVAL/AUTHORIZATION
CONSIDERATIONS
CHAPTER 07
7. OPERATIONAL APPROVAL/AUTHORIZATION
CONSIDERATIONS
User and Compliance Manual
The User and Compliance manual [REF 1] provides considerations for the operations and the
administration of the Flysmart+ for iPad Apps. It also provides elements that may be used by the
Flysmart+ Operators for the compliance demonstration with the applicable EFB regulation from the
competent National Aviation Authority (NAA).
Operational Suitability Letters

Upon NAVBLUE request, EASA and FAA perform operational evaluation of the Flysmart+ for iPad
Apps in order to check the compliance against the applicable EASA & FAA regulatory materials. It
includes the evaluation of the software and the review of the associated User and Compliance
Manual.
EASA and FAA evaluation results regarding the Flysmart+ for iPad Apps version V4.1 are provided
in the Operational Suitability Letters (OSL) for the Flysmart+ for iPad software published by EASA
[REF 2] and FAA [REF 3]. These OSLs are applicable to later versions like V4.3.
EASA OSLs can be retrieved on the following link (select Airbus as Manufacturer in the Search
filter): https://www.easa.europa.eu/document-library/operational-suitability-data
The Operators who wish to operate Flysmart+ V4.3 need to apply the change management
process from their competent NAA based on:
• The EASA OSL [REF 2] and FAA OSL [REF 3] published for V4.1,
• The stacking of major changes listed in Section 7.4 of the release notes of all Flysmart+
versions released since the latest NAA approval received,
• The latest UCM update ([REF 1])
Note 03
Please note that these letters do not constitute Operational Approval or Operational Authorization.
Operators remain responsible for demonstrating compliance with the EFB requirements and
guidance of their National Aviation Authority.
Management of Changes to Flysmart+

This section provides the list of changes introduced by new versions of Flysmart+ for iPad Apps
and their associated classification (Minor or Major) as described in Flysmart+ User and
Compliance Manual section 10 ([REF 1]).
The classification of the changes is a recommendation provided by Airbus to support the
determination by the Operator to apply the change management procedure approved by the
competent authority.
The correspondence of this Airbus criterion MINOR/MAJOR with EASA and FAA criteria for EFB
changes is shown below:
Flysmart+ change Regulation (EU) 995/2012 FAA AC120-76D

on Air Operations
MAJOR The Operator should apply Operator’s responsibility
the change management Minor or Significant
procedure approved by the
(to be determined in accordance
competent authority
with AC 120-76D 13.1)
MINOR The Operator does not need Minor, without FAA review or
to apply the change assessment
management procedure
approved by the competent
authority
Refer to the following tables to see the minor/major changes recommendations from Airbus for
each new change of the present Flysmart+ for iPad Apps version.
From V4.2.1 to V4.3

Change title Major Minor
General
Integration with eFF+ X
Performance
Integration of Octopus V38.0.1 X
Enhancement of inputs and results display when only TOGA take-off X
is possible
Display of the TO Shift value on the runway illustration on the results X
page
CUSTOMER SUPPORT
CHAPTER 08
8. CUSTOMER SUPPORT
For any information about our Flysmart+ products, please consult our Support Web Portal
(https://www.navblue.aero/support) where you can find:
• The latest roadmaps
• The Operational Documentation
• The Announcements
• The FAQs.
For any support need, please feel free to:

• Use our search engine
• Open a support ticket

Flysmart+ For Ipad Applications V4.3: Release Note - Reva

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Flysmart+ For Ipad Applications V4.3: Release Note - Reva

Hochgeladen von

Copyright:

Verfügbare Formate

FLYSMART+ FOR

RELEASE NOTE – RevA

* iPad is a trademark of Apple Inc

Revision Date Chapters Description of Changes

N° Title Reference Issue Date

3. APPLICABILITY AND COMPATIBILITY

The delivery of these Apps depends on the contract of the operator.

Hardware and Software Requirements

Minimum system requirements for EFB hardware & Operating System

For a complete view of compatibilities, please refer to the EFB_Compatibility_Matrix.xlsx file

5. WHAT HAS BEEN CORRECTED

Performance and Weight & Balance

Title Description Operational Consequences Apps Aircraft*

Title Description Operational Consequences Apps Aircraft*

The additive message, that explains why the computation cannot

Title Description Operational Consequences Apps Aircraft*

Ops Library Browser

6. WHAT ARE THE LIMITATIONS

Performance and Weight & Balance

The Performance Applications

The approach correction with

In case the runway

When this ECAM alert occurs,

Ops Library Browser

The Airbus manuals do not

Operational Suitability Letters

Management of Changes to Flysmart+

Flysmart+ change Regulation (EU) 995/2012 FAA AC120-76D

From V4.2.1 to V4.3

For any support need, please feel free to:

• Open a support ticket

Das könnte Ihnen auch gefallen