EFB Alert URGENT! PLEASE MAKE THIS INFORMATION AVAILABLE TO AFFECTED CREW MEMBERS AS SOON AS POSSIBLE

Transcription

1 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. Crossreference tables are included in this alert to provide substitute waypoint information for the mitigation.

2 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 Until then this Alert will be posted on the Jeppesen Web site: Area Map Showing Affected Waypoints NavData Cycle 1611 (Effective 13 OCT 10 NOV 2016)

3 Reference Tables of Affected Waypoints NavData Cycle 1611 (Effective 13 OCT 10 NOV 2016) Table 1 of 3: Northern Oceanic Transition Area (NOTA) Missing Means to replace missing named waypoint (bold=shortest entry) Named 1. Use Grid 2. or use 3. or use Waypoint * Waypoint Ident short-form coordinates full coordinates AGORI 5713N N57W013 N W BEGID H5614 N5630W014 N W BILTO H5615 N5630W015 N W DOGAL 5415N N54W015 N W ETARI H5515 N5530W015 N W KESIX n/a N5657W014 N W KOKIB H5414 N5430W014 N W MOGLO H5514 N5530W014 N W NETKI 5514N N55W014 N W OSBOX n/a n/a N W PIKIL 5615N N56W015 N W RESNO 5515N N55W015 N W SOVED 5614N N56W014 N W SUNOT 5715N N57W015 N W VENER H5415 N5430W015 N W * NOTE: Refer ONLY to the first column Named Waypoint when communicating with ATC Table 2 of 3: Shannon Oceanic Transition Area (SOTA) Missing Means to replace missing named waypoint (bold=shortest entry) Named 1. Use Grid 2. or use 3. or use Waypoint * Waypoint Ident short-form coordinates full coordinates ATSUR 5014N N50W014 N W BEDRA 4915N N49W015 N W BIMGO H4914 N4930W014 N W DINIM 5115N N51W015 N W ELSOX 5114N N51W014 N W EMPER 4909N N49W009 N W EPUNA H5014 N5030W014 N W GUNSO n/a n/a N W KOGAD H4915 N4930W015 N W

4 NERTU 4914N N49W014 N W RODEL H5015 N5030W015 N W SOMAX 5015N N50W015 N W * 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 Means to replace missing named waypoint (bold=shortest entry) Named 1. Use Grid 2. or use 3. or use Waypoint * Waypoint Ident short-form coordinates full coordinates BALIS n/a n/a N W BIGLI n/a n/a N W BODAM n/a n/a N W DILAX n/a n/a N W EVNAS n/a n/a N E FAMBO n/a n/a N W IZACK n/a n/a N W MADOX n/a n/a N W MIKEL n/a n/a N W NESTA n/a n/a N W NOBAL n/a n/a N W SHRUB n/a n/a N W SILOK n/a n/a N W SODKI n/a n/a N W SPIKE n/a n/a N W TIRIK n/a n/a N W TYSTI n/a n/a N W VAMLA 6004N N60W004 N W VANIN n/a n/a N W * NOTE: Refer ONLY to the first column Named Waypoint when communicating with ATC

5 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.

6 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)

7 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)

8

9 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).