EFB Alert - Jeppesenww1.jeppesen.com/documents/aviation/notices-alerts/chart-alert/... · If you have any questions concerning this EFB Alert, ... NESTA n/a n/a N60 00.0 W004 10.0

If you have any questions concerning this EFB Alert, please contact the Global Support and Control Center at: 1-800-537-7225 (Americas)

+49 61025 07004 (Europe, Middle East & Africa) +44 12938 42407 (United Kingdom)

+61 73105 9450 (Asia, Pacific Basin) E-mail: [email protected] E-mail: [email protected]

EFB Alerts - Enroute Application are published to advise users of significant issues with the EFB Enroute Application which may affect aircraft operations. These Notices are distributed to affected EFB users.

United Kingdom Waypoints - 1611

EFB Alert

URGENT! PLEASE MAKE THIS INFORMATION AVAILABLE

TO AFFECTED CREW MEMBERS AS SOON AS POSSIBLE Date: 14 October 2016

Subject: Waypoints removed or renamed to Grid Waypoint Idents, Cycle 1611

APPLICATIONS: The following EFB applications are affected:

Jeppesen FliteDeck Pro (iOS and Windows)

Jeppesen Mobile FliteDeck

Boeing EFB with Enroute application

Jeppesen Trip Kit on Demand

eLink for Windows

ALERT SUMMARY: 46 waypoints in Jeppesen NavData Cycle 1611 (EFF 13 OCT – 10 NOV 2016)

are missing or were incorrectly renamed to Grid Waypoints. Affected waypoints are in these FIRs:

Shanwick Oceanic FIR (EGGX)

London FIR (EGTT)

Scottish FIR ( EGPX) All missing or incorrectly named waypoints are listed in this alert, and corrective information is provided. CONSIDER THIS ALERT AND USE CAUTION WHEN REFERENCING WAYPOINTS WITHIN THE UNITED KINGDOM FOR CYCLE 1611 NAVDATA WITHIN YOUR EFB ENROUTE APPLICATION.

EFFECT AND MITIGATION: During use of EFB in Cycle 1611, users will encounter an “Unable

to Find (waypoint)” or “Nothing found for (waypoint)” error message in their applications if any of the missing or renamed waypoints are part of a route string or search. For route strings, the user can replace the waypoint name not found with a corresponding Grid Waypoint Identifier or raw coordinates if no Grid Waypoint Identifier is available. When this is done, the proper routing will be shown in the application. Pilots need to remember to use the correct (actual) waypoint name in conversations with ATC. Cross-reference tables are included in this alert to provide substitute waypoint information for the mitigation.






RESOURCES: The following items are included in this alert to assist you:

Map showing location and names of missing and incorrectly renamed waypoints

Tables of affected waypoints with information needed to mitigate the issue

Screen captures showing error message example and mitigation steps

FINAL RESOLUTION: The affected Waypoints will be corrected for EFB in the next Jeppesen

NavData cycle 1612, effective 10 NOV 2016. Until then this Alert will be posted on the Jeppesen Web site: http://www.jeppesen.com/company/alerts/alerts.jsp

Area Map Showing Affected Waypoints NavData Cycle 1611 (Effective 13 OCT – 10 NOV 2016)

http://www.jeppesen.com/company/alerts/alerts.jsp






Reference Tables of Affected Waypoints NavData Cycle 1611 (Effective 13 OCT – 10 NOV 2016)

Table 1 of 3: Northern Oceanic Transition Area (NOTA)

Missing Named

Waypoint *

Means to replace missing named waypoint (bold=shortest entry)

1. Use Grid Waypoint Ident

2. or use short-form coordinates

3. or use full coordinates

AGORI 5713N N57W013 N57 00.0 W013 00.0

BEGID H5614 N5630W014 N56 30.0 W014 00.0

BILTO H5615 N5630W015 N56 30.0 W015 00.0

DOGAL 5415N N54W015 N54 00.0 W015 00.0

ETARI H5515 N5530W015 N55 30.0 W015 00.0

KESIX n/a N5657W014 N56 57.0 W014 00.0

KOKIB H5414 N5430W014 N54 30.0 W014 00.0

MOGLO H5514 N5530W014 N55 30.0 W014 00.0

NETKI 5514N N55W014 N55 00.0 W014 00.0

OSBOX n/a n/a N56 48.4 W012 48.1

PIKIL 5615N N56W015 N56 00.0 W015 00.0

RESNO 5515N N55W015 N55 00.0 W015 00.0

SOVED 5614N N56W014 N56 00.0 W014 00.0

SUNOT 5715N N57W015 N57 00.0 W015 00.0

VENER H5415 N5430W015 N54 30.0 W015 00.0

* NOTE: Refer ONLY to the first column Named Waypoint when communicating with ATC

Table 2 of 3: Shannon Oceanic Transition Area (SOTA)

Missing Named

Waypoint *





ATSUR 5014N N50W014 N50 00.0 W014 00.0

BEDRA 4915N N49W015 N49 00.0 W015 00.0

BIMGO H4914 N4930W014 N49 30.0 W014 00.0

DINIM 5115N N51W015 N51 00.0 W015 00.0

ELSOX 5114N N51W014 N51 00.0 W014 00.0

EMPER 4909N N49W009 N49 00.0 W009 00.0

EPUNA H5014 N5030W014 N50 30.0 W014 00.0

GUNSO n/a n/a N49 03.2 W011 46.1

KOGAD H4915 N4930W015 N49 30.0 W015 00.0






NERTU 4914N N49W014 N49 00.0 W014 00.0

RODEL H5015 N5030W015 N50 30.0 W015 00.0

SOMAX 5015N N50W015 N50 00.0 W015 00.0

* NOTE: Use ONLY to the first column Named Waypoint when communicating with ATC

Reference Tables of Affected Waypoints NavData Cycle 1611 (Effective 13 OCT – 10 NOV 2016)

Table 3 of 3: Other Affected Enroute Waypoints

Missing Named

Waypoint *





BALIS n/a n/a N57 14.1 W002 03.9

BIGLI n/a n/a N52 07.8 W000 14.5

BODAM n/a n/a N59 55.1 W001 16.1

DILAX n/a n/a N51 45.3 W001 40.7

EVNAS n/a n/a N51 40.1 E000 26.6

FAMBO n/a n/a N54 30.0 W000 27.9

IZACK n/a n/a N59 53.5 W001 01.2

MADOX n/a n/a N58 43.7 W003 46.7

MIKEL n/a n/a N54 16.5 W004 51.8

NESTA n/a n/a N60 00.0 W004 10.0

NOBAL n/a n/a N57 15.3 W002 03.6

SHRUB n/a n/a N57 18.0 W001 48.9

SILOK n/a n/a N59 46.2 W001 29.0

SODKI n/a n/a N58 47.9 W003 37.9

SPIKE n/a n/a N57 32.4 W001 39.9

TIRIK n/a n/a N59 32.3 W001 12.2

TYSTI n/a n/a N59 22.4 W001 14.7

VAMLA 6004N N60W004 N60 00.0 W004 00.0

VANIN n/a n/a N53 59.1 W004 02.4

* NOTE: Refer ONLY to the first column Named Waypoint when communicating with ATC






Screen Captures for Affected Apps For any affected application when a waypoint cannot be found it can be replaced with either a Grid Waypoint Ident or Latitude/Longitude Coordinates, referring to the tables above. The following screen captures show a before-and-after example of a waypoint “not found” in a route drawer that has been corrected using the reference tables, above.

BEFORE

Example error message for named waypoint not found in database:

AFTER

Waypoint replaced with a Grid Waypoint Ident “5415N” (Entering coordinates from the table works in similar way)

Additional screen captures for each app are included in the following pages.






FliteDeck Pro iOS and Windows / Mobile FliteDeck iOS

1. A route is input that contains a missing Named Waypoint. FliteDeck reports that the waypoint cannot be found (top example: iOS, bottom example: Windows)






2. Edit the route to replace the missing Named Waypoint with the corresponding Grid

Waypoint Ident (or Coordinates) listed in the tables in this Alert.

3. The corrected route is shown on the map (top example: iOS, bottom example: Windows)











Boeing Enroute Application (Class 3 EFB) / FliteDeck Pro 7 for Windows

1. A route is input that contains a missing Named Waypoint. The application reports that the waypoint cannot be found (see left image, below).

2. Edit the route to replace the missing Named Waypoint with the corresponding Grid

Waypoint Ident (or Coordinates) listed in the tables in this Alert.

3. The corrected route is shown on map (see right image, below).

Documents

EFB Alert - Jeppesenww1.jeppesen.com/documents/aviation/notices-alerts/chart-alert/... · If you have any questions concerning this EFB Alert, ... NESTA n/a n/a N60 00.0 W004 10.0