A publication of the National Air Traffic Controllers Association
Issue link: http://natca.uberflip.com/i/698751
incumbent upon them to find the funding. Additionally issues have arisen from the Office of Environmental and Energy (AEE) briefing "policy" guidelines to non - FAA entities i.e. Airports/Noise Committees and not briefing the OSG Co - leads nor have they been willing to send the guide handbook to them, because it has not been signed off by congress . Y ou can't make this stuff up. Funding has become an issue, we were briefed last week that there is a 2.2 million dollar shortfall of FE funding for this calendar year, due mostly to community outreach. There are several Metroplex teams that have not been able to move on to the evaluation phase because they have been waiting for a community outreach plan . After discussion with Josh Gustin (PBN Manager) , the belief is NextGen will provide the additional funding for this year. Submitted by Mark McKelligan (ZBW) – NATCA Article 48 National D&I Rep NATCA National Airspace Rep – June 2016 We continue to work with the agency on community outreach for all the PBN projects . F unding and a standardized process are the two major is sues we are trying to address. Community outreach was not part of the original process so the funding needed to accomplish it was not add ressed when the projects started . T his may ca use us to delay some projects. The RTCA NIWG should submit their recommendations to the FAA in June concerning community outreach . W e hope to finalize the process after that. Jeff Woods (NATCA PMO Rep) and I are still working o n the SEA Integration project. The RTCA NAC will be briefed in June along with the Western Service Area. We are hoping to put a team together this summer that will refine the details of our process and identify all the key areas to be addre ssed. Submitted by Jim Davis - NATCA Article 48 National Airspace Rep DATACOMM : Chad Geyer (ZLA) is the Article 48 Representative for DataComm. Below is his update. The Tower Data Link Services (TDLS) Version 12 has been deployed to 36 sites and only 36 remain. 29 of those sites are Controller Pilot Data Link Communication (CPDLC) capable and only 27 remain. Across the country, approximately 1000 CPDLC clearances are being sent everyday with that number increasing as more sites become operational and addi tional aircraft begin to participate. This update will discuss the different types of clearances that are sent in a CPDLC clearance. The first is a cleared as filed (CAF). A cleared as filed uplink is an initial clearance that does not include route inform ation. This means that the filing of the aircraft was such that additional route information was not sent to the aircraft and the flight strip would not have between the pluses routing. Every clearance will always include a Standard Instrument Departure (S ID), if applicable, that the pilot would have to manually enter. The SID is not sent in loadable format. To send the SID in a loadable format, the runway would have to be included in the uplink. The next message type is an Uplink Message (UM) 79. A UM79 is a loadable route message that clears the aircraft to a point to rejoin the pilot ' s filed route. The message text to the pilot would say "Clea red to XXX via route clearance." This type of message would be used if there is between the pluses routing on the flight strip. This should be an indication to the pilot that there is embedded route information that must be loaded to view. When the pilot views the last page of the uplink, they wil l see a button that says "LOAD." Once the pilot loads the route informat ion, they would be able to view the entire route from their legs page. Again, the pilot must always manually load their