A publication of the National Air Traffic Controllers Association
Issue link: http://natca.uberflip.com/i/698751
SID and Transition, if applicable. One of the issues that we are seeing in the field is that some of the pilots are not loading the rout e and just accepting the clearance. This is a pilot training issue and Harris C orporation is working with the airlines to improve their training. The local 48 teams at the participating airports have been briefed on this issue and are working with their co ntrollers to understand what to look for when a pilot calls confused on their routing. As more and more sites become CPDLC enabled and pilots get to use the system more, instances of this confusion on the pilot site should diminish. Another message type i s an Uplink Message 80. A UM80 is a message that embeds the entire route from departure airport to the destination airport. This message will contain a text that includes the ver biage "Cleared Route Clearance." When the pilot sees this text, they should ag ain look for a load prompt on the last page of the message. The pilot will have to load the message and then view the legs page to see the entire routing. Again, the pilot must always manually load the SID and transition, if applicable. The final message t ype is a Non - Route Revision. This message is sent to the flight deck when local information is changed and does not require routing. Such messages would be Request Altitude changes, EDCT s, Departure Frequencies, and other local information that would be se lected on the Editor Window of the Departure Clearance application. ENROUTE AUTOMATION MODERNIZATION (ERAM): Julio Henriques (ZNY) lea ds the ERAM efforts for NATCA. This week's update is provided by Dan Mullen (ZID). Keysite Testing of EAD500 was complet ed at ZNY and ZDC on June 9. The remaining ARTCCs will install this new release over the next few weeks. This release contains the new Unconditional Track Control function (The Hammer), a Vertical Rate Indicator, and Pending Notification for SAAs, al ong wi th other changes. The next release, EAD510, is expected in early September. The National User Team (NUT) held its quarterl y meeting the week of June 13. Some of the issues worked on by the team include: Approval of the Corrective Action Request (CAR) addre ssing the lack of destination in some Terminal flight plans. The addition of the "P" altitude in the data block for Procedure Altitude clearances. Correction of ERAM behavior regarding Conflict Probe for aircraft in Hold. Discussion of the Contingency Flig ht Data Management (CFDM) failure tool. ARTCC Radar positi on monitor replacement options. How Airborne Re - route (ABRR) will be integrated into ERAM. The automatic addition of flights to the Continuous Range Readout view. Additionally, the team was briefed on several future enhancements being planned, and completed work on engineering documents. The Data Comm Program Office briefed the NUT on the progress of the program and the work required to integrate Data Comm into ERAM. A combined ERAM/OAPM task team ha s been working to try to solve some of the problems with Conflict Alert and Probe that have developed since the introducti on of the new OAPM procedures. There is currently no way to adapt these procedures so that ERAM won't show alerts, even though flights are separated by the procedures. AJV - 7 (Requirements) has continued to brief us regularly about enhancements planned for the NAS, so the ERAM team can help with the design fro m the earliest possible point. These enhancements are still several years away, but the tech design needs to st art very early in the process. Some examples are: Handoff to Non - U.S. Facilities, Conflict Probe in 3 - mile A irspace, and Path Stretch.