MFD 2.7.4 and Ios 10 Compatibility and KL

Home , Airport, IPad 2, IPad Mini 2, IPad Mini 3

Jeppesen Mobile FliteDeck V2.7.4 System Requirements and Compatibility Statement

Operating System Requirements The minimum operating system requirement for Mobile FliteDeck 2.7.4 is 9.0. Mobile FliteDeck 2.7.4 has been tested, and is compatible with iOS 10.

Hardware Supported Although Mobile FliteDeck 2.7.4 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.

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

Model Operating System

iPad Pro 9.3, 10.0 (9.7-inch model)

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

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

Jeppesen Mobile FliteDeck V2.7.4 - iOS 10 Known Limitations

• Airport Diagram Might Not Display as Expected o 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. o 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 o 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. o 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 o 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, 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. o Workaround: None at this time.

• Unable to Confirm the Sharing of Flight Information Using Bluetooth o 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. o Workaround: None at this time.

• Enroute Map Does Not Recenter on Route When Receiving Route from another App o 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. o Workaround: None at this time. Manually recenter route.

• New Waypoint Popover Display Anomaly o 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. o Workaround: None at this time.

• Removing Invalid Airports Using Keyboard Generates In-Line Message Anomaly o 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. o Workaround: None at this time.