Lido mBriefing

2 New features, enhancements and fixed issues 2.1 Application 2.1.1 Enroute Others - NOTAM's by FIR/UIR 2.1.2 SIGWX Bulletin section - Volcanic Ash Advisory/Tropical Cyclone Advisory 2.1.3 Navlog - "Planned/Minimum" Fuel on-board values 2.1.4 Fuel Summary - Improvements 2.1.5 RCF Indicator - Status bar 2.1.6 NOTES Synchronization 2.1.7 Archiving improvements - GDPR compliance 3 Bug fixes: 3.1 Bug - Final Reserve label and value mismatch on the Navlog's Fuel Bar. 4 Known Limitations: 4.1 Topic: Tankering fuel field is not included in the optional fuel group outside the Minimum take-off fuel section 4.2 Topic: Unread indicators (Blue dots) for the categories having "No data available" 4.3 Topic: Tankering fuel is not included in the optional fuel group outside the Minimum take-off fuel section

3.7.0 Scope 2.1 Application 2.1.1 Aircraft/Fuel weights - Improvements 2.1.2 Optional - Aerodata Takeoff and Landing Performance Report ("TLR") 2.1.3 Navlog Page - Improvements 2.1.4 Fuel Summary - Improvements 2.1.5 RCF indicator - Dashboard Flight Card 2.1.6 New NOTES section 2.1.7 Real-time sync - Improvements in the User workflow and robustness : 2.1.8 Improved Chart access from the Dashboard 2.1.9 NOTAM related Improvements 2.1.10 Flight times and Fuel screen - Usability improvement 2.1.11 ETOPS - "two engines out" condition 2.1.12 Enroute Others - "WX" section removed 2.1.13 Fuel Summary - Display of Statistical Contingency Fuel 2.1.14 Airport Briefing - Airport Codes are established as main identifiers in the Fuel Summary/ETOPS screen 2.1.15 Archive - Timestamps in Navlog.json and Joruneylog.json are changed from Unix Epoch timestamp to human readable date & time. 3 Bug fixes: 3.1 Bug - Lido mBriefing application holding onto the old flight information 3.2 Bug - Pilots are unable to flag/search NOTAMs from the Classic OFP 3.3 Bug - Partial sharing of "Additional Briefing Documents" also results in the sharing of the Journey log section data

2 New features, enhancements and fixed issues 2.1 Application 2.1.1 Additional Briefing Documents - Annotations 2.1.2 Sharing functionality - Conflict Handling Improvements 2.1.3 Fuel summary - Improvements 3 Bug fixes: 3.1 Bug - Delete data from the device value set to "Disabled" from the LCB admin portal caused problems in the Lido mBriefing application 4 Known Limitations: 4.1 Topic: Mismatch between the delta figure in the Planned column and the value in the adjustment factor

Summary: 2 New features, enhancements and fixed issues 2.1 Application 2.1.1 Fuel summary - Improvements 2.1.2 New "Re-acceptance" feature 2.1.3 Navlog improvements 2.1.4 Improved workflow - Informing Users about Push Notification Service unavailability 3 Bug fixes: 3.1 Bug - Flight Acceptance: Loader issue 3.2 Bug - Significant number of attempts to confirm old flights 3.3 Bug - ETOPS: Weight units should be presented correctly 4 Known Limitations: 4.1 Topic: Discrepancy between T/O fuel figure and Navlog’s first waypoint EFOB value 4.2 Topic: Mismatch between the delta figure in the Planned column and the value in the adjustment factor 4.3 Topic: App Data Settings - "Disabled" and "Max" configuration values are not supported by the Application

Bug - Fuel Page - Statistical Contingency Fuel numbers presented in Statistical Extra Fuel section External Ticket ID: Observed Behaviour: The Statistical Contingency Fuel information was presented in the Statistical Extra/DISCF section on the Fuel page. Fix: The logic to select and present the numbers was corrected so that only the analyzed (statistical) extra/discretionary fuel values are presented. For airlines not leveraging that functionality of Lido Flight and in case the data is not present in the OFP and OFP data (OFP.xml), the Statistical Extra/Discretionary Fuel section is invisible. Limitation: None.

Improvements: - Manual BP update shall lead to update of Briefing status (e.g. to confirmed) - Maps Component - Geocultural Data pack update Bugfixes: - User account gets locked if user changes password from LCB web - Estimated Landing Fuel - Not adjusted with Alternate change - Flights are not getting deleted even after submitting the flights - App Crash - Unlocking the screen after some time when user is on the dashboard screen - App Crash - User accepts the BP in offline mode via biometric - Compatibility with iPhone and iOS 17.1

2 New features, enhancements and fixed issues 2.1 Application 2.1.1 Briefing package - "Accept"/Confirmation status synchronization 2.1.2 Briefing package - "Accept"/Confirmation status sharing 2.1.3 Flight acceptance - Workflow change 2.1.4 Introduction of optional pre-flight archive submission 2.1.5 Briefing Package sharing - Conflict handling for annotated OFP 2.1.6 OFP Annotations - Tool improvement 2.1.7 Fuel summary - FAA rules 2.1.8 Fuel summary - Display of Statistical Discretionary(Extra) Fuel 2.1.9 Airport Briefing - Airport Codes are established as main identifiers 2.1.10 Status Bar improvements 2.1.11 Navlog - Read/Write mode changes 2.1.12 NOTAMs - missing NOTAMs 2.1.13 New weight unit presentation - "lb" 3 Bug fixes: 3.1 Bug - Fuel screen: Tankering fuel is not updated when changing the Block fuel value 3.2 Bug - Fuel screen: The statistical Discretionary Fuel section is getting populated with the figures from the Statistical Contingency fuel 4 Known Limitations: 4.1 Topic: Pre-flight archive unavailable / not created 4.2 Topic: Briefing Status not updated 4.3 Topic: Flight plans containing weights in lb will not be handled in Lido mBriefing versions before 3.6.3

Bug fixes: Bug - Estimated landing fuel External Ticket ID: T2321196 Observed Behaviour: The estimated Landing Fuel is not getting updated when Discretionary Fuel is updated via updating the block fuel and on certain other scenarios. Fix: The estimated Landing Fuel is re-estimated/recalculated upon change of the Discretionary Fuel. Limitation: The estimated landing fuel might not be updated correctly in case of Tankering and the User modifying the Block Fuel directly.

Lido mBriefing iOS 3.6.1 2 New features, enhancements and fixed issues 2.1 Application 2.1.1 Changes in the third party shortcuts display in Quick Access 2.1.2 Annotation tool improvements: 2.1.3 Improved Notification Workflow: 2.1.4 Estimated Landing Fuel 2.1.5 Manual switch of Dark/Light mode in Quick Access 2.1.6 Flight List - Share feedback from flight cards context menu 2.1.7 Sharing of full briefing pdf from Flight list 2.1.8 Airport Codes are established as Main identifiers in briefing menu/maps 2.1.9 Chart Notam improvements: 2.2 Bug fixes: 2.3 Bug - GDPR: Crew member names are displayed as blurred for their own assigned flights 2.4 Bug - Dashboard : Commercial flight number mismatch between Status Info bar and Flight card 2.5 Bug - Performance: Lido mBriefing takes longer loading time in Dashboard screen when there are large number of Notams 2.6 Bug - Scrolling and Zooming does not work properly for the pdf annotations 2.7 Bug - Dashboard : Overlapping labels seen in the Flight card 2.8 Bug - Missing Chart Notams for Enroute Others

2 New features, enhancements and fixed issues 2.1 Application 2.1.1 Easy access menu on Flight List 2.1.2 MEL/CDL information 2.1.3 Flight Information status bar 2.1.4 WX/NOTAM/RAIM – NOTAM Notes 2.1.5 Dashboard - NOTAM card 2.1.6 Export to mPilot 2.1.7 mPilot - AFC 2.1.8 Add Flight via Departure & Destination airport parameter 2.1.9 Briefing Efficiency - Continuous Improvements 2.1.10 GDPR (Global Data Protection Regulation) 2.1.11 Improved notification workflow 2.1.12 OFP PDF Annotations 16 2.1.13 "Feedback" - enhanced Error reporting 2.1.14 ETOPS Summary - display of planned runway 2.2 Bug Fixes: 2.3 Bug - Submission: Flights are not submitted and showing as pending for submission 2.4 Bug - Some waypoints are entirely composed of null values in navlog.json. No waypoint name, no waypoint ID and no coordinates are displaying 2.5 Bug - Sharing: iPad/iPhone full name doesn't display on 'Device found' screen while sharing BP. 3 Known Limitations: 3.1 Topic : Fuel order may fail in case of Discretionary tankering flight 3.2 Topic : Application launch in offline mode after successful update to 3.6.0