NATCA Bookshelf

National Office Update: Dec. 9-31, 2018

A publication of the National Air Traffic Controllers Association

Issue link: http://natca.uberflip.com/i/1067228

Contents of this Issue

Navigation

Page 21 of 31

ABE, CAK, NCT, D01, D10, I90, and A80, who did a great job working with a new tool with minimal training. S6.R7 Drop 15 was tested in mid-December due to problems discovered during keysite activity. The fixes were verified and R7 will go back to keysite with a planned national release in early 2019. S6.R6a was also tested in mid-December and declared suitable for keysite. R6a is a variation of the R6 build primarily consisting of tracking enhancements originally designed to augment SCT surveillance. R6a will be released to a limited number of sites with specific tracking needs. S6.R9 OT&E is scheduled to begin Jan. 7, 2019. Program Trouble Report Working Group (PTRWG) – The December meeting continued significant cleanup efforts by going through old PTRs and closing several. NATCA elevated a PTR related to ADS-B information and a PTR that increases coordination list capacity. NATCA also elevated a PTR that improves Range Bearing Line functions and STARs playback accuracy. MSAW/CA Board – During recent R9 testing, aural alarm functionality was negatively impacted by a software change. Previous to R9, the aural alarm could be adapted to the owner of the track (tower or TRACON). In R9, the aural alarm sounded, regardless of track owner, therefore increasing nuisance alarms. The Board unanimously agreed the pre-R9 alarm behavior is preferred. TSLE will engage with Raytheon to update the software. Software Planning Board (SPB) – During the December meeting the SPB added air traffic content to S6.R8 Drop 4, and modified content to S6.R9. Keysite selection for upcoming builds was also discussed with SPB participants. The rollout of the new STARs Operating System will begin with sites in the Northeast and will continue westward. To shorten deployment times prior to the OS rollout, the R9 and R10 builds should follow a similar deployment strategy, northeast and westward. Stakeholders discussed outliers to the rollout plan such as the Academy in OKC, and sites with specific software needs such as SCT and D01. TSLE software made the following recommendations: • NEOSF solicit for an ELITE keysite for R9 (satisfies the ELITE keysite need) • DEN OSF discuss when they need R9/TSAS, consider training, and if they need to be a keysite (satisfies the consolidated TRACON keysite need) • Pacific OSF discuss keysite of R9 (and R10, R1, and R2) with SCT (satisfies the consolidated TRACON keysite need). TAMR Deployment and Common Terminal Digitizer (CTD) – We participated in the Pre- CCB meeting via telcon on Dec 6 and dialed into the CKB and HTS IOC. We are planning telcons this month to get familiar with the sites for the January 2019 IOCs. We

Articles in this issue

view archives of NATCA Bookshelf - National Office Update: Dec. 9-31, 2018