To prepare for the transition to the new vNAS system and future release of CRC, automatic beacon code allocation will be enabled on the live and sweatbox servers on 12/19/2022. This means that all flight plans departing NAS airports will automatically receive a beacon code according to National Beacon Code Allocation Plan (
https://www.faa.gov/documentLibrary/media/Order/FAA_Order_JO_7110.66G_NBCAP.pdf). This has all been configured for you, so no action is required on your part.
We'd like you to note that this change does have the potential to alter controller workflow, as some controllers rely on the presence of a beacon code in a flight plan to signify that an aircraft has received a clearance. This process will no longer work, and we encourage you to use other means such as flight strip annotations, scratchpad entries, and/or data block positioning to signify that a clearance has been issued. Since every flight plan originating in the US will be assigned a squawk code automatically, it is no longer necessary to assign new squawk codes as a method of radar identification (such as an uncontrolled field departure or an aircraft entering the airspace) if no existing code duplication errors exist.
We appreciate your continued support through this transition and are excited about the opportunity to provide next-generation software for VATUSA controllers!
