jeppesen mobile flitedeck user guideww1.jeppesen.com/documents/support/mobile/mobile... · resolves...

Jeppesen Mobile FliteDeck Release Notes

Jeppesen55 Inverness Drive East

Englewood, Colorado 80112-5498

This document supports version 2.7.4 of the Jeppesen Mobile FliteDeck iOS application.

The minimum operating system requirement for this release is iOS 9.0. Jeppesen Mobile FliteDeck 2.7.4 has been tested and is compatible with iOS 10.0.

September 2016

Document ID: DATD_JEPP_FDC_2.7.4_Release Notes

Copyright © 2016 Jeppesen. All rights reserved.

Contents

Jeppesen Mobile FliteDeck Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1About This Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Release Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Update and Deployment Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Initial Download and Data Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Updating from Mobile FliteDeck Version 2.6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5What is Preserved When Updating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Connectivity Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

What’s New . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Mobile FliteDeck 2.7.4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Mobile FliteDeck 2.7.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Mobile FliteDeck 2.7.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Mobile FliteDeck 2.7.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Mobile FliteDeck 2.7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Display of a VFR Enroute Theme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Filtering of Enroute Map Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Improved User Waypoint Interactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Edit a User Waypoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Enhanced Flight Plan Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Display of ATC Clearances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Load an ATC-Cleared Route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Simplified Mid-Cycle Chart Revision Interaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Enhanced Unscheduled Updates Interaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Improved Access to In-App Help Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Issues Resolved . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Mobile FliteDeck 2.7.4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Contents

Je

Enroute Theme May Not Be Retained Upon Restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Mobile FliteDeck 2.7.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Performance Issue Related to Database Query Latency Accrued Over Time . . . . . . . . 36App Could Become Unresponsive During Update from Previous Version . . . . . . . . . . . 36

Mobile FliteDeck 2.7.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Slow Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Automatic Switch to Taxi Diagram Occurred Unexpectedly . . . . . . . . . . . . . . . . . . . . . 38Object Details Popover Not Displaying All Communication Information . . . . . . . . . . . 38Highlighted Search Result Disappears from Map Under Certain Conditions . . . . . . . . 38

Mobile FliteDeck 2.7.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Terms & Conditions Popup Appears Upon Subsequent Launches . . . . . . . . . . . . . . . . . 39Selected Charts Without a Route Do Not Display After Force Close and Relaunch . . . 39Enroute Weather Display Irregularities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Certain Settings in the iPad General Settings Can Cause Unexpected Behavior . . . . . . 40Change in Time Zone Can Cause Data Update Irregularities . . . . . . . . . . . . . . . . . . . . 40The Airspace Filter Can Hide FIR and UIR Boundaries . . . . . . . . . . . . . . . . . . . . . . . . 41Battery Consumption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Latitude/Longitude User Waypoint Anomalies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Boundary Line Inaccurately Depicts Coverage Area . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Show Taxi On Landing Triggered Inaccurately . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42QNE and QNH Boundary Labels May Be Reversed . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Ownship Can Make Extreme Location Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Ownship Position Displays When There is No GPS Reception . . . . . . . . . . . . . . . . . . . 43

Mobile FliteDeck 2.7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Future Chart Title Displays During Mid-Cycle Revision in Chart List . . . . . . . . . . . . . 43Incorrect UTC Conversion in Airport Object Popover . . . . . . . . . . . . . . . . . . . . . . . . . . 44Editing Airport by Rubber-band Routing Can Cause App to Shut Down . . . . . . . . . . . . 44Route Revalidation Not Performed When Switching Between Databases . . . . . . . . . . . 44Chart Library Problem Error Occurs Under Certain Conditions . . . . . . . . . . . . . . . . . 45Site Key Generated Multiple Times . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Switching Between NEXRAD and Echo Tops Causes App to Shut Down . . . . . . . . . . . . 45Waypoint Popover Not Displaying Intersection Airways for Certain Enroute Fixes . . . 46Printing a Terminal Chart Shuts Down App Under Certain Conditions . . . . . . . . . . . . 46Enroute Theme Not Returning to Default Under Certain Circumstances . . . . . . . . . . . 46

Known Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Airport Diagram Might Not Display as Expected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Direct To Button Availability Prolonged After GPS is Disabled . . . . . . . . . . . . . . . . . . 47App Might Force Close when Viewing Keyboard and Rotating iPad . . . . . . . . . . . . . . . 47Unable to Confirm the Sharing of Flight Information Using Bluetooth . . . . . . . . . . . . . 48Enroute Map Does Not Recenter on Route When Receiving Route from Another App . 48New Waypoint Popover Display Anomaly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Removing Invalid Airports Using Keyboard Generates In-Line Message Anomaly . . . . 49Enroute Map Theme May Not Display as Expected on First Time Launch . . . . . . . . . . 49Route Information is Removed from Flight Info Drawer When Updating the App . . . . . 49Under Certain Conditions Taxi Charts are Not Displaying as Expected . . . . . . . . . . . . 50Performance Issue Related to Zooming Out with Terrain Showing . . . . . . . . . . . . . . . . 50Ownship Displaying Over Text Insets on Taxi Diagrams . . . . . . . . . . . . . . . . . . . . . . . . 50

ppesen FliteDeck Release Notes June 2016Copyright © 2016 Jeppesen. All rights reserved.

Contents

Je

Some SID and STAR Transition Points Not Depicted Accurately . . . . . . . . . . . . . . . . . 51Direct To Routing Clears Waypoints Already Flown in the Route . . . . . . . . . . . . . . . . 51Error Message on Devices with Multiple Activations and Deactivations . . . . . . . . . . . 51Flight Plans Retrieved after Clearing Call Sign . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Some iOS Multitasking Gestures Not Supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Slower Performance on Older Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

ppesen FliteDeck Release Notes June 2016Copyright © 2016 Jeppesen. All rights reserved.

Jeppesen Mobile FliteDeck Release Notes

Introduction

This document describes system requirements, updates, resolved issues, and known limitations for Jeppesen Mobile FliteDeck 2.7.4.

About This Document

The intended audiences for Mobile FliteDeck Release Notes are pilots and support specialists who currently use or support Jeppesen Mobile FliteDeck.

Additional References

In addition to these Release Notes, Jeppesen provides detailed, task-oriented training and documentation for Mobile FliteDeck on the web at Jeppesen Mobile FliteDeck Training and Documentation. Help is also available from within the app from the Settings button on the Mobile FliteDeck toolbar.

http://ww1.jeppesen.com/main/corporate/aviation/products/mobile-flitedeck/resources.jsp

IntroductionTechnical Support

Technical Support

Jeppesen provides technical support 24 hours a day, 7 days a week at:

• North America Toll Free: 800-537-7225

• United States Direct: 303-328-4170

• United Kingdom: 44-1293-842407

• Australia: 61-73105-9450

• All Other International: 49-6102-507004

• Email: [email protected]

• Web: jeppesen.com/jeppfd

Release Summary

Thank you for using Jeppesen Mobile FliteDeck. Jeppesen iOS applications are continually modified to be fully compatible with the latest Apple operating system and iOS devices.

Mobile FliteDeck 2.7.4 was released June 2016. This release resolves an issue related to the last selected enroute map theme and enroute map objects not being displayed as expected on the map upon force closing and restarting the app.

Mobile FliteDeck 2.7.3 was released May 2016. This release addressed an additional performance issue and an issue where the application might become unresponsive during an update from a previous version of the Mobile FliteDeck application.

In release 2.7.2 various updates were made to improve overall performance. As one of these updates, the View At All Scales option for enroute map filters was removed. This release also added additional communication information to controlled airspace and FIR object details popovers.

Mobile FliteDeck version 2.7 introduced an option to display a VFR enroute theme; enhanced filtering of the enroute map; an option to display and load ATC-cleared routes; improved user waypoint interaction, flight plan integration, and unscheduled

Jeppesen Mobile FliteDeck Release Notes September 2016Copyright © 2016 Jeppesen. All rights reserved.

2

mailto:[email protected]

http://ww1.jeppesen.com/support/technical-support.jsp

IntroductionRelease Summary

updates interaction; as well as improved access to in-app Help.

Release Identification Information

This document supports Mobile FliteDeck version 2.7.4.

Operating System Requirements

The minimum operating system requirement for Mobile FliteDeck 2.7.4 is iOS 9.0. Mobile FliteDeck 2.7.4 has been tested and is compatible with iOS 10.0.

Hardware Supported

Although Mobile FliteDeck is supported on all iPads except first generation iPads, older devices that run on 32-bit technology, such as 2nd, 3rd, or 4th generation iPads, might experience slower than expected performance. The iPad Air and iPad Mini 2, and later, are recommended devices.

September 2016 Jeppesen Mobile FliteDeck Release NotesCopyright © 2016 Jeppesen. All rights reserved.

3

IntroductionUpdate and Deployment Considerations

Jeppesen has tested or reviewed Mobile FliteDeck 2.7.4 for compatibility with the following operating systems and devices:

NOTE iOS 10 will is available on iPad 4, Air, Air 2, Mini 2 and Mini 3, and both iPad Pro models. Neither iPad 2 nor iPad 3 is supported with the iOS 10 update.

Update and Deployment Considerations

Initial Download and Data Updates

Mobile FliteDeck is released through available Apple distribution models. Only one version of the application can be downloaded to the iPad at a time.

The Mobile FliteDeck application and data, including subsequent data updates, requires 2 to 6 GB of available storage capacity on your iPad. The variability in the storage capacity requirement is related to the size of your Terminal Charts coverage area.

Model Operating System

iPad Pro (9.7-inch model) 9.3, 10.0

iPad Air 2 9.3, 10.0

iPad Mini 3 9.3, 10.0

iPad Mini 2 9.3, 10.0

iPad Air 9.3, 10.0

iPad 4 9.3, 10.0

iPad 3* 9.3

iPad 2* 9.3


4

IntroductionUpdate and Deployment Considerations

Updating from Mobile FliteDeck Version 2.6

There are special considerations associated with updating from Mobile FliteDeck version 2.6.

• The update process requires that you re-download enroute and cultural data, as well as any selected manuals. The time necessary to download and perform the enroute data update depends on the speed of the Internet connection and the size of your coverage area.

Ensure that you have the necessary time and bandwidth to complete the update before you begin the update procedure.

• After you download Mobile FliteDeck 2.7.4, you might need to go to Profile settings and verify that Jeppesen Sanderson, Inc. is a trusted developer on your iPad. See Verifying the App is from a Trusted Developer for instructions.

What is Preserved When Updating

When you update Mobile FliteDeck from one version of the app to another, the following information is preserved:

• Customized JeppFD global settings, including registration and account information

• Saved flights

• User waypoints

Verifying the App is from a Trusted Developer

After you download Mobile FliteDeck 2.7.4, you might be required to access iPad Profile settings and verify that Jeppesen Sanderson, Inc. is a trusted developer on your iPad. To do so:

1. Tap the iPad Settings icon.

2. Tap General.

3. Tap Profile.


5

IntroductionConnectivity Considerations

4. Tap the Jeppesen Sanderson, Inc. flyout.

5. Tap Trust Jeppesen Sanderson, Inc.

6. Tap Trust to confirm.

Automatic App Updates

Beginning with iOS 7, Apple offers an automatic update feature for apps. When your iPad is fully charged and connected to the Internet, it downloads and installs free app updates without requiring any interaction from you. This feature might not always be desirable.

Preventing Automatic App Updates

To prevent the automatic download of the Mobile FliteDeck app update so that it doesn't occur at an inopportune time, you can disable background app updates.

To disable background app updates:

1. Go to Settings > iTunes & App Store.

2. Under Automatic Downloads, switch Apps to OFF.

Connectivity Considerations

On the Ground

iPads have both Wi-Fi and Bluetooth wireless technologies built-in. Wi-Fi enables an Internet connection, and Bluetooth enables a connection to nearby devices. If an iPad is enabled for cellular service, the iPad can connect anywhere that the cellular service is available.

Mobile FliteDeck requires a reliable Wi-Fi or cellular Internet connection to download updates. To share flight information between two iPads running Mobile FliteDeck, the iPads use a


6

What’s NewMobile FliteDeck 2.7.4

Bluetooth connection.

NOTE Mobile FliteDeck displays ownship based on your GPS receiver. In Track Up orientation, the ownship symbol and enroute map might shift when your aircraft is not moving.

In the Air

All models of iPads that are 3rd generation or newer have built-in Wi-Fi and Bluetooth connectivity. The internal iPad GPS receiver uses Wi-Fi signals and nearby cellular towers to triangulate position so that your iPad can quickly find position.

Although the iPad GPS receiver works well and provides good GPS accuracy, it might not be reliable in all flight decks while airborne. You can use an external GPS device to work with your iPad as a backup.

What’s New

Mobile FliteDeck 2.7.4

Mobile FliteDeck 2.7.4 was released June 2016. This release retains the last selected enroute map theme and displays enroute map objects upon force closing and restarting the app as expected. See Issues Resolved Mobile FliteDeck 2.7.4 for more information.


Mobile FliteDeck 2.7.3 was released May 2016. This release addressed an additional performance issue and an issue where the app might become unresponsive during an update from a


7

What’s NewMobile FliteDeck 2.7.2

previous version of the Mobile FliteDeck app. See Issues Resolved Mobile FliteDeck 2.7.3 for more information.


Jeppesen Mobile FliteDeck 2.7.2 was released in May 2016 to address performance issues impacting the app. See Mobile FliteDeck 2.7.2 for a complete list.


Jeppesen Mobile FliteDeck 2.7.1 was released in January, 2016 to address issues impacting the app. See Issues Resolved Mobile FliteDeck 2.7.1 for a complete list.


8

What’s NewMobile FliteDeck 2.7

Mobile FliteDeck 2.7

In addition to being compatible with iOS 9, Jeppesen Mobile FliteDeck 2.7, released October, 2015, introduced the following new functionalities and enhancements:

• Display of a VFR Enroute Theme

• Filtering of Enroute Map Objects

• Improved User Waypoint Interactions

• Enhanced Flight Plan Integration

• Display of ATC Clearances

• Simplified Mid-Cycle Chart Revision Interaction

• Enhanced Unscheduled Updates Interaction

• Improved Access to In-App Help Information

•


9


Display of a VFR Enroute Theme

Mobile FliteDeck 2.7 introduces a VFR enroute theme. You work in the VFR theme in the same way that you are accustomed to working in the High IFR and Low IFR themes.

You create a new flight, search for, filter, view enroute objects and switch between map orientations (North Up or Track Up) in the same way.

Mobile FliteDeck enroute themes are:

• High IFR: provides aeronautical information for enroute instrument navigation facilitating operations generally above FL180.

• Low IFR: provides aeronautical information for enroute instrument navigation facilitating operations generally below FL180.

• VFR: provides aeronautical information for conducting flight under visual conditions in the United States and parts of Europe. See VFR Aeronautical Data Coverage Areas for more information.

NOTE To display the VFR enroute theme, ensure that Display VFR Theme is set to ON in JeppFD global settings.

Switch Between Enroute Themes

As in previous versions of Mobile FliteDeck, to switch between enroute themes, from the Enroute view:

1. Tap the Enroute Theme button.

2. Tap your preferred enroute theme.

When you switch between enroute themes and a route object is not included in the theme that you switch to, Mobile FliteDeck displays that object as a standard waypoint on the enroute map.


10


For example, if you add a VFR checkpoint to your route from the VFR enroute theme, and then switch to the Low IFR enroute theme, Mobile FliteDeck displays the checkpoint with a standard waypoint symbol. When you switch back to the VFR enroute theme, Mobile FliteDeck displays the VFR checkpoint symbol and label.

VFR Aeronautical Data Coverage Areas

As of this release date, the following countries include VFR aeronautical data represented in the VFR enroute theme.

VFR data coverage areas are subject to change.

NOTE You may see VFR airports outside these coverage areas.

Albania Germany Netherlands

Austria Gibraltar Norway

Belgium Greece Poland

Bosnia and Herzegovina Hungary Portugal

Canary Islands Ireland Serbia and Montenegro

Croatia Italy Slovakia

Cyprus Kosovo Slovenia

Czech Republic Latvia Spain

Denmark Lithuania Switzerland

Estonia Luxembourg Sweden

Finland Macedonia United Kingdom

France Malta United States


11


New VFR Map Objects

The VFR theme includes these new VFR objects available from the enroute object buttons while in the VFR theme:

• Airports VFR and low-use airports, balloon facilities, glider ports, hang glider facilities, heliports, private airfields, seaplane bases, and ultralight activity areas.

• Airways Advisory routes, VFR flyways, military low-flying routes, military training routes, VFR transition routes-Europe, and VFR transition routes-USA.

• Waypoints VFR checkpoints, VFR waypoints, VFR landmarks, compulsory and non-compulsory reporting points, compulsory and non-compulsory helicopter VFR reporting points, military route mileage breaks, and advisory route mileage breaks.

• Navaids Navaids relevant to the VFR enroute theme.

• Airspace Boundaries for Special Use Airspace (SUA). SUA includes flight information zones, helicopter traffic areas, helicopter traffic zones, VFR traffic areas, bird areas, and glider areas.

• Cultural Information City names, city patterns, national parks, obstacles, railroads, and roads. Obstacles include windmills, buildings, towers, plants, and suspension bridges.

NOTE To view details about an obstacle displayed with the Cultural Information button, zoom in on the obstacle, and touch, hold, and release the obstacle symbol.


12


Filtering of Enroute Map Objects

Default Filtering of Map Objects

As in previous versions of Mobile FliteDeck, depending on your zoom level and selected enroute theme, certain map objects are automatically filtered to declutter your enroute map view.

NOTE Mobile FliteDeck displays any object that is a part of your route on the map regardless of the object’s show/hide status, the enroute theme, or zoom level.

The following table defines the default settings for the display of enroute map objects at specific zoom levels and enroute themes, including the new VFR theme.

NOTE *Adjustments were made to dynamic terrain filtering at the Mobile FliteDeck 2.7.2 release that improves overall performance at strategic zoom levels. See Performance Issue Related to Zooming Out with Terrain Showing for more information.

Enroute Map Object High IFR Low IFR VFR

Airports 160 nm/in 80 nm/in 80 nm/in

Airways 80 nm/in 40 nm/in 40 nm/in

Waypoints 20 nm/in 20 nm/in 20 nm/in

Navaids 80 nm/in 40 nm/in 40 nm/in

Airspace 80 nm/in 40 nm/in 40 nm/in

Terrain* 200 nm/in 200 nm/in 200 nm/in

Cultural Never Never Always


13


Show and Hide Enroute Map Objects

As in previous versions of Mobile FliteDeck, you tap the enroute object buttons along the right side of the enroute map to show and hide specific map objects.

NOTE The Cultural Information button is available from the VFR enroute theme. To display the VFR enroute theme, ensure that Display VFR Theme is set to ON in JeppFD global settings.

CulturalInformation

Airports

Airways

Waypoints

Navaids

Airspace

Terrain


14


Customized Filtering of Enroute Objects

At Mobile FliteDeck 2.7, you can filter specific types of enroute objects for more precise control of your enroute view.

To further filter the enroute map view:

1. Tap the Filters Menu button (<) to expand the menu.

The filters menu opens to the Airports menu by default.

2. Tap the button that corresponds to the object type that you want to filter.

3. Make any changes to filter the display of that object.

NOTE If the display of the object is not showing on the map that the Filters menu is related to, tap the object button to show the filtered object on the map.

4. Tap away from the expanded menu or tap the Filters Menu button (>) to close the menu.


15


Enroute Object Button States

Mobile FliteDeck displays four different object button states:

• An amber cue indicates that a filter is applied to the object.

• Highlighted buttons indicate that the object is showing on the map.

• Gray buttons indicate that the object is available but not showing on the map.

• Dark gray buttons indicate that the object is not available at the current zoom level or from the selected enroute theme.

NOTE When you tap a map object button for an object that is not visible at the current zoom scale or enroute theme, the filters menu is still available for that object type.


16


Enroute Object Filters

The filters available for each enroute map object are as follows:

• Airports: You can set a minimum runway length for airports that appear on the map. See Filter Airports by Runway Length for more information.

In the VFR theme, you can specify whether to show or hide heliports, seaports, and private airports.

• Airways: No additional filters are available for airways in either of the IFR themes.

In the VFR theme, you can show or hide low-altitude airways and other routes. Other routes include VFR routes and military training routes.

• Waypoints: You can also specify whether to show or hide only oceanic entries or exit points in the IFR themes. See Show Only Oceanic Entry and Exit Points for more information. In the VFR theme, you can show waypoints at all zoom scales. Additionally, you can show or hide low altitude waypoints, VFR checkpoints, and VFR waypoints.

• Navaids: No additional filters are available for airways in either of the IFR themes.

• Airspace: You can customize the airspace display to show or hide controlled airspace, ATC sectors, restricted airspace, prohibited airspace, warning and danger areas, and other. The Other category includes ADIZ, alert areas, equipment boundaries, MOAs, QNE/QNH boundaries, and training areas.

• Terrain: No additional filters are available for terrain.

• Cultural Information: The cultural information button is available from the VFR theme. You can customize cultural information to show or hide city names, city patterns, high tension lines, obstacles, railroads, and roads.


17


Filter Airports by Runway Length

You can filter airports by runway length to limit airports that appear on the enroute map. To filter airports by runway length:

1. Tap the Filters Menu button (<) to expand the menu.

NOTE The filters menu opens to the Airports menu by default.

2. Tap the Minimum Rwy Length value and select the desired runway length.


Show Only Oceanic Entry and Exit Points

Displaying only oceanic entry and exit points can also be useful in certain areas of the world.

To show only oceanic entry and exit points:

1. From either the High IFR or Low IFR enroute theme, tap the Filters Menu button (<) to expand the menu.

2. Tap the Waypoints button to access the filter.

3. Switch Show Only Oceanic Entry/Exit to ON.



18


Improved User Waypoint Interactions

As with previous versions of Mobile FliteDeck, you can create and edit user waypoints from inside the Flight Info drawer or by interacting with the enroute map.

NOTE User waypoints that are a part of a route can be shared between iPads and are available in all enroute themes and zoom levels.

When you create user waypoints by interacting with the map, you can also name the waypoint and add comments to the waypoint.

Types of User Waypoints

Any user waypoint that is named, or created from the map and not added to a route, is considered permanent.

Permanent user waypoints must be individually deleted in order to eliminate them from the enroute map. Removing a permanent user waypoint from the route or clearing the route when creating a new flight does not delete a permanent user waypoint.

Any user waypoint that is part of an imported route, or created from the map without a name, is considered temporary.

Temporary user waypoints are removed when the waypoint is removed from the route or when the route is cleared when you create a new flight.


19


The following list provides some common examples of the types of user waypoints that you can create:

• Latitude/Longitude User Waypoints—You can add these waypoints to your route to view a point in space for a single instance of a route.

When you add this type of waypoint to your route, it is considered temporary and is removed when the route is cleared or when you remove it manually. For more information, see Remove a User Waypoint from Your Route .

• Radial DME User Waypoints—The location of these waypoints is based on the radial DME that you enter in the Name field.

When you add this type of waypoint to your route, it is considered temporary and is removed when the route is cleared, or you remove it manually. For more information, see Remove a User Waypoint from Your Route .

• Named User Waypoints—These user waypoints are considered permanent. You can create them to name a point in space for easier recognition and recall.

Named user waypoints may or may not be part of a route. They are not removed when a route is cleared. You must manually delete named user waypoints. For more information, see Delete a User Waypoint .


20


Create a Latitude/Longitude User Waypoint

To create a latitude/longitude user waypoint by interacting with the map:

1. Touch, hold, and release the enroute map at the location where you want to insert a waypoint.

Mobile FliteDeck displays the New Waypoint popover.

• To enter comments, tap in the Comments field.

2. Complete the action by doing one of the following:

• To add the waypoint to your current route, tap Add to Route.

• To add the waypoint to the current route and remove all points between your aircraft position and the waypoint, tap Direct To.

NOTE The Direct To option is available when the Moving Map setting in JeppFD global settings is set to ON and the minimum GPS accuracy requirement is met.

• To create the latitude/longitude waypoint without adding it to your route (in which case it would be considered a permanent waypoint), tap Done at the top of the New Waypoint popover.

Mobile FliteDeck displays the latitude and longitude coordinates for the newly created user waypoint on the map.


21


Create a Radial DME User Waypoint

Assume that air traffic control instructs you to fly: "Direct to 26 DME on 156 radial off of Falcon VOR.”

You can quickly create a radial DME user waypoint by interacting with the map. To create a temporary radial DME user waypoint:

1. Touch, hold, and release the enroute map.

FliteDeck displays the New Waypoint popover.

2. In the Name field, enter the VOR ident, radial, and DME.

Radials must be entered using three digits with a forward slash between the radial and the DME, and they must not include any spaces. Example: FQF156/26

3. To enter comments, tap in the Comments field.




Mobile FliteDeck displays the user waypoint on the map in the location based on the radial DME that you entered in the Name field.


FQF156/26

Navaid RadialDME


22


Create a Named User Waypoint

To create a named user waypoint by interacting with the map:

1. Touch, hold, and release the enroute map at the location where you want to insert a waypoint.

Mobile FliteDeck displays the New Waypoint popover.

2. In the Name field, enter a name.

You can include any characters available on the keyboard in the waypoint name, including spaces. The maximum length of a user waypoint name cannot exceed the area provided in the popover.

3. To enter comments, tap in the Comments field.





• To create a named user waypoint without adding it to your route, tap Done at the top of the New Waypoint popover.

Mobile FliteDeck displays the name for the newly created user waypoint on the map.


23


Edit a User Waypoint

To edit a user waypoint:

1. Touch, hold, and release the user waypoint.

Mobile FliteDeck displays the Waypoint popover.


• To edit the name, tap in the Name field and use the keyboard to edit the name. To complete the edit, tap Done at the top of the Waypoint popover.

• To edit comments, tap in the Comments field and use the keyboard to edit comments. To complete the edit, tap Done at the top of the Waypoint popover.

• To add the user waypoint to your current route (if it is not already added), tap Add to Route.

• To add the user waypoint to your current route and remove all points between your aircraft position and the waypoint, tap Direct To.


Remove a User Waypoint from Your Route

To remove a temporary user waypoint from your route:

1. Touch, hold, and release the user waypoint that you want to remove.

Mobile FliteDeck displays the Edit Waypoint popover.

2. Tap the Remove From Route button, and then confirm the removal.

Mobile FliteDeck removes the waypoint from your route.


24


Delete a User Waypoint

Any user waypoint that is named, or first created and not added to a route, is considered permanent. To delete a permanent user waypoint:

1. Touch, hold, and release the user waypoint that you want to delete.

Mobile FliteDeck displays the Edit Waypoint popover.

2. Tap the Delete (trashcan) button at the top of the popover, and then confirm the deletion.

Mobile FliteDeck deletes the waypoint from your route and from the enroute map.

Enhanced Flight Plan Integration

As with previous versions of Mobile FliteDeck, you can import a route from any flight-planning system that is set up to deliver flight plan routes to Mobile FliteDeck. With the 2.7 release, Jeppesen has implemented a system that communicates with Mobile FliteDeck using the aircraft call sign.

NOTE To work with flight plans, ensure that valid credentials are entered under Services > Flight Plans in JeppFD global settings and an Internet connection is established. Contact your Jeppesen account manager for more information.


25


Retrieve Flight Plans and Load a Route

Flight plans are displayed for the designated call sign that have an ETD within six hours into the future to twenty-four hours into the past.

To retrieve flight plans and load a route:

1. Open the Flight Info drawer.

2. Tap the Flight Plans button.

3. Enter the call sign for the aircraft (for example, NJ104F or CMB123).

4. Tap DONE on the keyboard.

Mobile FliteDeck displays a list of future and past flight plans for that call sign sorted by ETD from newest to oldest.

5. Tap a flight plan to select it.


26


6. Tap the Load button.

Mobile FliteDeck loads the route in the Flight Info drawer with origin, destination, alternate airports (if any), and the route description.

Flight plan routes can include the following information:

• Named user waypoints as long as they are included in the source.

• SIDs and STARs. To view SID and STAR transition points on the enroute map, ensure that the associated runway is entered in the route string.

7. Close the Flight Info drawer to view the loaded route.

Refresh the List of Flight Plans

Mobile FliteDeck displays the time and date that the list of flight plans was last updated at the bottom of the list.

As long as you are connected to the Internet, you can refresh the list to check if any updates have become available since the last time you accessed the flight plans.

To refresh the list of flight plans, tap the Refresh button at the bottom of the list.

Save a Flight Plan Route Without Loading It

When you save a flight plan route without loading it, Mobile FliteDeck adds the route to your list of saved flights. It does not change the active flight in the Flight Info drawer.

To save a flight plan route without loading it:

1. Open the Flight Info drawer.

2. Tap the Flight Plans button.

3. Enter the call sign for the aircraft (for example, NJ104F or CMB123).


27


4. Tap DONE on the keyboard.

Mobile FliteDeck displays a list of future and past flight plans for that call sign sorted by ETD newest to oldest.

5. Tap a flight plan to select it.

6. Tap the Save button next to the flight plan.

Mobile FliteDeck updates the list of saved flights with the flight plan route. Saving a flight plan route does not change the active flight.

7. Tap the Save button next to the flight plan.

Mobile FliteDeck updates the list of saved flights with the flight plan route.

Display of ATC Clearances

Mobile FliteDeck provides you with an awareness of current clearing trends with the introduction of the display of ATC clearances.

You can view cleared routes for the past 24 hours between a city pair and you can also load a cleared route into the Flight Info drawer.

Clearances are grouped by route and are available for any flight within, into, or out of the United States.

NOTE To display ATC clearances, ensure that Display ATC Clearances is set to ON in JeppFD global settings and an Internet connection is established.


28


View ATC-Cleared Routes

To display ATC clearances after you have entered origin and destination airports in the Flight Info drawer:

1. Open the Flight Info Drawer.

2. Tap the ATC Clearances button.

Mobile FliteDeck displays clearances that have occurred for that city pair in the last 24 hours.

The time and date that the list was last updated appears at the bottom of the list.

• Tap Refresh to retrieve the latest clearances.

Load an ATC-Cleared Route

To load an ATC-cleared route as the active flight:




29


3. From the list of displayed clearances tap the desired clearance to select it.

4. Tap the Load button next to the clearance.

Mobile FliteDeck loads the route as the active flight.

Save an ATC-Cleared Route Without Loading It

Saving an ATC-cleared route does not change the active flight. When you save an ATC-cleared route without loading it, Mobile FliteDeck adds the route to the list of saved flights on your iPad.

To save an ATC-cleared route without loading it as the active flight:



3. From the list of displayed clearances, tap the desired clearance to select it.

4. Tap the Save button.

Mobile FliteDeck updates the list of saved flights with the route.

Simplified Mid-Cycle Chart Revision Interaction

Mobile FliteDeck 2.7.4 simplifies chart selection during a mid-cycle chart revision.

Now, when charts with multiple revision dates are available, you can select the revision date that you want to apply for all charts at the airport, as well as selecting revision dates on a chart-by-chart basis.

A mid-cycle chart revision occurs when a chart takes effect in the middle of a scheduled chart revision time period.


30


About Mid-Cycle Chart Revisions

Usually whenever terminal charts are updated, the charts are effective upon receipt and available to you immediately in Mobile FliteDeck.

Some charts, however, take effect mid-cycle. For those charts that take effect mid-cycle, Mobile FliteDeck displays an amber badge, which indicates that a mid-cycle chart revision is available. The badge appears within 24 hours of the revised chart effectivity change.

NOTE Always brief selected terminal charts including a review of effectivity dates.

Switch Between Available Chart Versions from the Airports List

Whenever a revision exists for a chart at an airport in your route, Mobile FliteDeck displays an effectivity badge on the Airports button and in the expanded Route Airports list.

To view effective dates and access the option to switch between available chart versions for the airport:


31


1. Tap the route Airports button.

Mobile FliteDeck displays the list of airports for the active flight, and any airport effectivity text and badges.

2. Tap the Airport Effectivity badge area.

Mobile FliteDeck displays the Airport Revision Selector and prompts you to choose the effectivity date of the charts that you want to view.


• Tap the date to use charts with a different effectivity date, and then tap Done.

• Tap Cancel to dismiss the Airport Revision Selector and continue viewing the current chart version.

Switch Between Available Chart Versions on a Chart-by-Chart Basis

When you view a chart with more than one version available, Mobile FliteDeck also displays chart revision text in the chart list and a chart revision tag on the chart itself.


32


To view effective dates and access the option to switch between available chart versions while viewing the chart:

1. Tap the Chart Revision tag.

Mobile FliteDeck expands the Chart Revision tag and indicates the effective date of the chart being used.

2. Tap the Switch button.

Mobile FliteDeck displays the Airport Revision Selector and prompts you to choose the effectivity date of the chart that you want to view.

Enhanced Unscheduled Updates Interaction

At Mobile FliteDeck 2.7 usability concerns related to unscheduled updates are addressed so that you can complete an unscheduled update for any data type that is sent—that is, terminal chart, enroute, or manual updates.

An unscheduled (or off-cycle) update is an unplanned change. For example, an unscheduled update can occur due to an error on an existing chart or, in the case of company manuals, when a publication is not on an update cycle.


33


Unscheduled updates are initiated by your company or by Jeppesen on a case-by-case basis. Notification of an unscheduled update will come from an external communication.

Whenever you receive notice that there is an unscheduled update, you can go into Mobile FliteDeck to perform the update.

To perform an unscheduled update:

1. Tap the Settings button.

2. Tap Updates.

3. Mobile FliteDeck displays an alert if an unscheduled update is available.

4. To perform the unscheduled update, tap OK.

5. Tap the Update button.

6. When updates are complete, tap the X at the top of the Updates screen to dismiss it.

Improved Access to In-App Help Information

To address usability concerns related to the in-app help, Mobile FliteDeck 2.7 now includes a search capability.

To access the Mobile FliteDeck Help:


34


1. Tap the Settings button.

2. Tap Help.

3. Perform one of these actions:

• Tap in the search field and enter your search request.

• Navigate the help topics by tapping a topic.

4. Tap Done at the top of the Help window to dismiss the Help screen.


35

Issues ResolvedMobile FliteDeck 2.7.4

Issues Resolved

The following issues were resolved at the indicated release.


Enroute Theme May Not Be Retained Upon Restart

Issue: Upon force closing and restarting Mobile FliteDeck, the enroute map theme and enroute map objects may not be retained from the last viewed settings as expected.

Resolution: This issue has been resolved.


Performance Issue Related to Database Query Latency Accrued Over Time

Issue: The rendering of an active flight with a long route could lead to performance degradation over time.

Resolution: Highlighted charted elements (airport alternates) in the Enroute view were identified as causing the latency. This issue was resolved and performance improved.

App Could Become Unresponsive During Update from Previous Version

Issue: After an update from a previous version of Mobile FliteDeck, a "Syncing Downloaded Data" message related to terminal charts might be displayed in the Updates screen and the app has to be force-closed and restarted to resolve the issue.

Resolution: The update from a previous version of the Mobile FliteDeck app performs as expected.


36



Slow PerformanceIssue: Under certain circumstances, Mobile FliteDeck exhibited slower than expected performance. To help improve performance, the following modifications were made.

Resolutions:

• The Show At All Scales option was removed from the Map Object Filter menu.

Previously, you could set airports, navaids, and waypoints to appear on the map regardless of the zoom level by switching Show At All Scales to ON. Using this option, however, slowed performance.

• The display of enroute map search results was optimized.

Highlighted search results are hidden on the enroute map while panning or zooming, and enroute map search results are cleared as expected.

• The time to load operational notes in the Enroute view was improved.

• The time to launch the app and display the default Enroute view has been improved.

• The Atlas mode is no longer displayed in the Enroute view. All nations display in the same color.

• The display of terrain has been adjusted so that it appears on the enroute map only when switched on and zoomed in to a scale of 60 nm/in and below.

This is a temporary adjustment while we work to improve our rendering engine to better support terrain at different zoom levels.


37


Automatic Switch to Taxi Diagram Occurred Unexpectedly

Issue: Under certain circumstances, Mobile FliteDeck automatically switched to the taxi diagram unexpectedly.

Resolution: Additional check conditions were added to ensure that the automatic switch to a taxi diagram occurs when the speed threshold identified in Global Settings is reached. Also, an issue was corrected that prevents an unexpected switch to the taxi diagram to occur for an origin airport.

Object Details Popover Not Displaying All Communication Information

Issue: The object details popover for controlled airspace and FIRs did not display all of the necessary communication details.

Resolution: The object details popover Communications panel for controlled airspace now also displays CPDLC, INMARSAT, and SATCOM details. For FIRs, the Communications panel now also displays INMARSAT and SATCOM details.

Highlighted Search Result Disappears from Map Under Certain Conditions

Issue: This situation occurred when you performed a search from the enroute view at a zoomed-out scale and the search results returned a list of 99+ objects. When you tapped the search result from the search results list, the object popover appeared as expected. However, if you tapped away from the object popover, the highlighted search result object disappeared from view.

Resolution: This issue has been resolved.


38



In addition to various stability improvements, this release resolved the following issues:

Terms & Conditions Popup Appears Upon Subsequent Launches

Issue: The Terms and Conditions popup appeared subsequent to the initial launch, and when you tapped Agree, the active route was removed.

Resolution: The Terms and Conditions popup appears only on initial launch of the app and whenever a new version of the terms and conditions are downloaded. The active route is not removed after tapping Agree.

Selected Charts Without a Route Do Not Display After Force Close and Relaunch

Issue: If you selected an airport without entering a route and then selected terminal charts for that airport and force closed the app, when you returned the selected terminal charts did not display as expected.

Resolution: When you select an airport without entering a route and then select terminal charts for that airport and force close the app, when you return the selected terminal charts display as expected.


39


Enroute Weather Display Irregularities

Issues: Enroute weather irregularities included:

• Icing, Turbulence, and Winds Aloft forecasts did not display as expected on the enroute map.

• After installing Mobile FliteDeck, the first attempt to view enroute weather was unsuccessful. The various enroute weather types did not load or display.

• When animated enroute weather selections (NEXRAD, Echo Tops, or Lightning) were displayed, and the enroute Weather button was switched to OFF, the animation continued to play.

Resolution: Enroute weather displays as expected on the enroute map.

Certain Settings in the iPad General Settings Can Cause Unexpected Behavior

Issue: For those iPads with General Settings configured for non-USA region, language, or calendar, irregularities existed with regard to creating user waypoints and certain terminal charts with mid-cycle effectivity being unavailable.

Resolution: Mobile FliteDeck performs as expected under all iPad General Setting configurations.

Change in Time Zone Can Cause Data Update Irregularities

Issue: A change in time zones under certain conditions could cause a change in data effectivity dates displayed in the data updates screen.

Resolution: Changes in time zones do not change any dates or countdown to data effectivity in the Updates dialog.


40


The Airspace Filter Can Hide FIR and UIR Boundaries

Issue: The display of FIR and UIR boundaries on the enroute map could be disabled with the Airspace filter.

Resolution: FIR and UIR boundaries display at all times in the Enroute view, controlled only by the zoom level.

The airspace filter can be customized to show or hide controlled airspace, ATC sectors, restricted airspace, prohibited airspace, warning and danger areas, and other. The other category includes ADIZ, alert areas, equipment boundaries, MOAs, QNE/QNH boundaries, and training areas.

Battery Consumption

Issue: The network activity indicator remained active while the app was running. Battery consumption exceeded expected levels.

Resolution: The network activity indicator does not remain active while the app is running. Battery consumption is at expected levels.

Latitude/Longitude User Waypoint Anomalies

Issue: Latitude and longitude coordinates were not parsed correctly under certain conditions resulting in the inability to create and display a latitude and longitude waypoint on the enroute map.

Resolution: Mobile FliteDeck creates a latitude and longitude user waypoint and displays the latitude and longitude coordinates on the enroute map as expected.


41


Boundary Line Inaccurately Depicts Coverage Area

Issue: The boundary line depicting your data coverage area on the enroute map inaccurately displayed.

Resolution: The boundary line accurately depicts data coverage area on the enroute map displays accurately.

Show Taxi On Landing Triggered Inaccurately

Issue: The automatic switch to a taxi diagram could be erroneously triggered under certain conditions.

Resolution: The automatic switch to a taxi diagram on landing occurs as expected.

QNE and QNH Boundary Labels May Be Reversed

Issue: Under certain conditions, QNE and QNH boundary labels could be reversed resulting in the wrong value displaying on each side of the boundary.

Resolution: Mobile FliteDeck displays QNE and QNH values on the correct side of the boundary label.

Ownship Can Make Extreme Location Changes

Issue: There were situations where Mobile FliteDeck received a location update that exceeded the maximum aircraft speed that the app could handle (Mach 2). Note that if the aircraft location is


42

Issues ResolvedMobile FliteDeck 2.7

changed significantly (>15%), the speed can likely exceed the maximum aircraft speed resulting in the ownship displaying extreme location changes.

Resolution: If Mobile FliteDeck receives a location update that exceeds the maximum aircraft speed, after 10 seconds the ownship will transition to the new location.

Ownship Position Displays When There is No GPS Reception

Issue: When the ownship was displayed on taxi or approach charts, and GPS was turned off (either by switching Airplane Mode to ON or Location Services for Mobile FliteDeck to NEVER in the iPad global settings), the GPS status continued to indicate a strong signal and the ownship position continued toappear on the taxi chart.

Resolution: When ownship is set to display on terminal charts, and there is no GPS reception, the ownship position does not appear on taxi or approach charts.

Mobile FliteDeck 2.7

In addition to performance and stability improvements, this release resolved the following issues.

Future Chart Title Displays During Mid-Cycle Revision in Chart List

Issue: The future chart title during a mid-cycle revision displayed in the chart list prior to the changeover.

Resolution: During the period encompassing the mid-cycle chart revision, accurate chart titles display in the chart list.


43


Incorrect UTC Conversion in Airport Object Popover

Issue: The Airport object details popover applied an incorrect time conversion from local time to Coordinated Universal Time (UTC) at an airport.

Resolution: Corrected UTC conversion to display accurate Coordinated Universal Time (UTC) in the Airport object details popover.

Editing Airport by Rubber-band Routing Can Cause App to Shut Down

Issue: Under certain circumstances, when replacing an origin or a destination airport for an active flight using rubber-band routing, the app could shut down.

Resolution: Editing origin and destination airports using rubber-band routing works as expected.

Route Revalidation Not Performed When Switching Between Databases

Issue: The active flight route was not revalidated when switching between current and non-current enroute databases.

Resolution: The active route validates as expected when switching between enroute databases.


44


Chart Library Problem Error Occurs Under Certain Conditions

Issue: A chart library problem could occur when any of the following actions were carried out:

• When terminal chart coverages are added

• When an unscheduled update is performed

• When an update cycle is skipped

Resolution: The process for carrying out unscheduled updates has been enhanced to prevent such errors from occurring.

Site Key Generated Multiple Times

Issue: Repeatedly tapping the Activate button from the Mobile FliteDeck Activate dialog generated multiple (duplicate) activation requests consuming additional site keys.

Resolution: Site keys are not consumed by repeatedly tapping the Activate button.

Switching Between NEXRAD and Echo Tops Causes App to Shut Down

Issue: Occasionally, the application unexpectedly shut down when switching between NEXRAD and Echo Tops enroute weather types.

Resolution: The weather component framework was updated to correct the issue.


45


Waypoint Popover Not Displaying Intersection Airways for Certain Enroute Fixes

Issue: Waypoint popovers for enroute fixes in the High IFR enroute theme did not display airways in the Intersection Info flyout.

Resolution: When you tap the Intersection Info flyout from a Waypoint popover, Mobile FliteDeck displays a detailed view of the intersection formation for all applicable enroute fixes.

Printing a Terminal Chart Shuts Down App Under Certain Conditions

Issue: Occasionally, when you switched to Mobile FliteDeck after using another app on the iPad, and you tapped Settings > Print to print a terminal chart, Mobile FliteDeck unexpectedly shut down.

Resolution: Print functionality works as expected after switching between apps.

Enroute Theme Not Returning to Default Under Certain Circumstances

Issue: When exiting from the High IFR enroute theme and then switching Reset User Settings to ON in JeppFD global settings, upon relaunching the app, the High IFR enroute theme would persist instead of the default enroute theme that is indicated by the check box.

Resolution: Mobile FliteDeck displays the expected default enroute theme as indicated by the check box after resetting user settings and relaunching the app.


46

Known LimitationsMobile FliteDeck 2.7

Known Limitations

This section describes known limitations to Mobile FliteDeck 2.7.4.

Airport Diagram Might Not Display as Expected

Issue: This issue occurs when running Mobile FliteDeck 2.7.4 on iOS 10 and while viewing the enroute map, you enter a route in the Flight Info drawer. When you then navigate to the Taxi charts category, the 10-9 airport diagram might not display as expected.

Workaround: Select another chart category and then navigate back to the Taxi chart category to view the 10-9 airport diagram. The chart displays and functions as expected.

Direct To Button Availability Prolonged After GPS is Disabled

Issue: This issue occurs when running Mobile FliteDeck 2.7.4 on iOS 10 after disabling GPS in location services. When returning to FliteDeck Pro and displaying certain map object details (that is, a waypoint, navaid, or airport), the Direct To button is still available.

Workaround: After disabling GPS and returning to the FliteDeck Pro app, wait 1-2 minutes before the Direct To button is disabled.

App Might Force Close when Viewing Keyboard and Rotating iPad

Issue: This issue occurs when running Mobile FliteDeck 2.7.4 on iOS 10 and viewing FliteDeck with the iPad in portrait view. With the Flight Info drawer open and the keyboard showing,


47


when you rotate the iPad to landscape the keyboard does not rotate (although the app does), and FliteDeck Pro may force close after about 5 seconds.

Workaround: None at this time.

Unable to Confirm the Sharing of Flight Information Using Bluetooth

Issue: This issue occurs when running Mobile FliteDeck 2.7.4 on iOS 10 and both the sending and receiving iPads have Bluetooth ON (and Wi-Fi OFF). When one iPad shares flight information with the other, the flight information is successfully shared with the other iPad, but the status on the sending iPad displays, “Failed try again.” The status on the sending devices never updates.


Enroute Map Does Not Recenter on Route When Receiving Route from Another App

Issue: This issue occurs when running Mobile FliteDeck 2.7.4 on iOS 10 and you load a route from another app on your iPad. The enroute map does not recenter over the route.

Workaround: None at this time. Manually recenter route.

New Waypoint Popover Display Anomaly

Issue: This issue occurs when running Mobile FliteDeck 2.7.4 on iOS 10 and creating a user waypoint. The New Waypoint popover appears in the upper left-side of the screen instead of as expected.



48


Removing Invalid Airports Using Keyboard Generates In-Line Message Anomaly

Issue: This issue occurs when running Mobile FliteDeck 2.7.4 on iOS 10 and using the "x" delete key on the keyboard to delete an invalid origin airport. Once the invalid origin airport name is removed and the origin airport field is tapped in one more time, the exclamation point in the in-line message is multiplied. It displays correctly when using the "x" button in the origin airport field.


Enroute Map Theme May Not Display as Expected on First Time Launch

Issue: Upon force closing the app from the High IFR or VFR enroute theme and updating to a newer version of the app, the first time that you restart the app after updating, the enroute map theme may not display as expected. Specifically, the Low enroute theme is selected by default upon restarting the updated the app, but may display High IFR or VFR enroute theme objects on the map. This limitation only occurs upon first launch of the updated app.

Workaround: Select a different enroute theme, and then return to the desired enroute theme.

Route Information is Removed from Flight Info Drawer When Updating the App

Issue: All route information in the Flight Info drawer is removed when upgrading to FliteDeck 2.7.4

Workaround: Save any active flight in the Flight Info drawer prior to updating the app.


49


Under Certain Conditions Taxi Charts are Not Displaying as Expected

Issue: Taxi charts may not display as expected after updating terminal charts data.

Workaround: Select another terminal chart and then select the chart that didn’t display correctly. The chart displays and functions as expected.

Performance Issue Related to Zooming Out with Terrain Showing

Issue: At higher zoom scales, showing terrain causes a performance latency in the app.

Workaround: To support higher performance, we have adjusted the display of terrain. Terrain now shows on the enroute map only when switched on and zoomed in to a scale of 60 nm/in and below. This is a temporary adjustment while we work to improve our rendering engine to better support terrain at different zoom levels.

Ownship Displaying Over Text Insets on Taxi Diagrams

Issue: Under certain conditions, the ownship appears over a text inset on the taxi diagram.

Workaround: For an unobstructed view of the text, switch Display Ownship on Taxi Charts to OFF in JeppFD Global Settings. Alternatively, you can zoom the display so that the ownship does not cover the text.


50


Some SID and STAR Transition Points Not Depicted Accurately

Issue: Some SID and STAR transition points are not depicted accurately on the enroute map.

Workaround: Always brief the SID and STAR terminal procedure.

Direct To Routing Clears Waypoints Already Flown in the Route

Issue: When selecting the Direct To option for a waypoint in your route, waypoints already flown are removed from the route.

Workaround: None.

Error Message on Devices with Multiple Activations and Deactivations

Issue: This issue occurs on devices that have activated and deactivated the Mobile FliteDeck app using various activation serial numbers.

While the app is running, when you deactivate JeppFD in global settings and then delete the app from the iPad, upon re-installing and launching the app, the activation credentials that are retained in the device cache are used. As a result, the Updates screen displays and Mobile FliteDeck begins downloading enroute data while, at the same time, displaying a message: Server is Missing Terminal Chart Data. Try again and contact your System Administrator. (Error: 133).

Workaround: When this situation occurs, wait for Enroute data to complete the download. Then force close the app and navigate to Jepp-FD global settings. Switch Deactivate to ON and relaunch the app. Tap Proceed to confirm the deactivation.


51


Flight Plans Retrieved after Clearing Call Sign

Issue: After clearing the call sign from the Flight Plans tab in

the Flight Info drawer, flight plans for the cleared call sign are redisplayed when you tap Refresh.

Workaround: Enter a new call sign in the field and tap Done or Refresh.

Some iOS Multitasking Gestures Not Supported

Issue: Mobile FliteDeck 2.7.4 does not support the iOS 9 Split View multitasking functionality. It also does not support the five-finger pinch gesture to minimize the app.

Workaround: Mobile FliteDeck 2.7.4 supports both the iOS 9 Slide Over and Picture-in-Picture multitasking functionalities. To minimize the app, you can use the iPad Home key.

Slower Performance on Older Devices

Issue: Although Mobile FliteDeck is supported on all iPads except the first generation iPad, older devices that run on 32-bit technology, such as the 2nd, 3rd, or 4th generation iPads, might experience slower than expected performance.

Workaround: To make our app better for you, Jeppesen iOS applications are continually modified to be fully compatible with the latest Apple operating system and iOS devices. The iPad Air and iPad Mini 2, and later, are recommended devices.


52

jeppesen mobile flitedeck user guideww1.jeppesen.com/documents/support/mobile/mobile... · resolves...

Documents