Andrew Heath

Data Blocks (DBs) can be displayed as: Full Data Blocks (FDB) Limited Data Blocks (LDB) Enhanced Limited Data Blocks (E-LDB)

Many commands feature an optional method to uplink the command to the pilot via DataComm (aka CPDLC). Optional syntax is indicated in GREEN. Function Key Message Type Message Purpose Message Syntax BM Add Bookmark BM {index 1-6} {custom name (can be blank)} <KBE> Delete Bookmark BM {index 1-6} DEL <KBE> CT Compliance Timer Default to sector frequency: CT <TBE on target> CT {FLID} <KBE> Add a different frequency: CT {Frequency} <TBE on target> CT {Frequency} {FLID} <KBE> Unghosting Approve unghost request after Compliance Timer: CT A <TBE on target> CT A {FLID} <KBE> Deny unghost request after Compliance Timer: CT D <TBE on target> CT D {FLID} <KBE> DATIS Request D-ATIS DATIS {station ICAO code} DEP <KBE> DATIS {station ICAO code} ARR <KBE> RNG BRG LA Range/Bearing Readout Results referencing magnetic heading: LA <TBP> <TBE on target or space> LA <TBP> <TBP> <KBE> Results referencing true heading: LA <TBP> <TBP> T {FLID} <KBE> Range/Bearing Readout w/ Speed LA <TBP on target or space> <TBP> /{speed 55-999 knots} <KBE> LB Range/Bearing/FIX Readout LB {waypoint} <TBE on target> LB {waypoint} {FLID} <KBE> LI Network Log-In LI <KBE> LO Network Log-Out LO <KBE> LOADSCT Load a Sectorfile LOADSCT <KBE> CODE (F9) QB Discrete Code Request QB {FLID} <KBE> Code Insert QB {desired squawk code} {FLID} <KBE> CRD (F2) QD Altimeter Requests QD {station ICAO code (up to 4 simultaneously)} <KBE> FR QF Request Flight Plan Data QF {FLID} <KBE> QF <TBE on target> HALO (F10) QP Distance Reference Indicator (J-Ball) QP J {FLID} <KBE> QP J <TBE on target> QP J {FLID}/{FLID}/{FLID}/{FLID}/{FLID} <KBE> QP J <TBP on up to 4 targets> <TBE on 5th> INT (F8) QQ Interim Altitude QQ {altitude 2-3 digits} /U {FLID} <KBE> QQ {altitude 2-3 digits} /U <TBE on target> 4TH LINE QS FDB Heading, Speed and Free Form Text 4th Line Headings and speeds (can be entered separately): QS {heading 0-360}/{speed 000-999 or M00-M99} {FLID} <KBE> QS {heading 0-360}/{speed 000-999 or M00-M99} <TBE on target> Free form message: QS ○{free-text up to 9 characters} {FLID} <KBE> QS ○{free-text up to 9 characters} <TBE on target> Delete/Hide 4th Line Info Delete heading 4th line data: QS */ {FLID} Delete speed 4th line data: QS /* {FLID} Delete all 4th line data: QS * {FLID} Hide all 4th line data: QS {FLID} TRK (F3) QT Track Primary QT <TBP> P {FLID} <KBE> Start Track QT <TBP> {FLID} <KBE> QT <TBP> <TBE on target> Steal Track (not tracked by you) QT /OK {FLID} <KBE> QT /OK <TBE on target> ALT (F5) QZ Assigned Altitude QZ {altitude 2-3 digits} /U {FLID} <KBE> RTE (F11) QU Route Display Time Display the next 20 minutes: QU {FLID} <KBE> QU <TBE on target> Display number of minutes requested: QU {1 to 99} {FLID} <KBE> QU {1 to 99} <TBE on target> Display entire route with waypoint names: QU 0 {FLID} <KBE> QU 0 <TBE on target> Track Reroute QU {waypoint or multiple waypoints separated by spaces} /U {FLID} <KBE> QU {waypoint or multiple waypoints separated by spaces} /U <TBE on target> Track Reroute + Change of Destination QU {waypoint or multiple waypoints separated by spaces} {new destination} ? /U {FLID} <KBE> QU {waypoint or multiple waypoints separated by spaces} {new destination} ? /U <TBE on target> DROP TRK (F4) QX Drop Track QX {FLID} <KBE> QX <TBE on target> Drop Track and Cancel FP QX FP {FLID} <KBE> QX FP <TBE on target> REFRESH Update Refresh Rate REFRESH {1 to 12} <KBE> SISO (F12) SI Position Sign-In SI <KBE> SISO (SHIFT+F12) SO Position Sign-Out SO <KBE> SR (F6) SR Request Strip SR {FLID} <KBE> SR <TBE on target> Request Strip (not tracked by you or on the ground) SR {FLID} /OK <KBE> SR /OK <TBE on target> UF Uplink Frequency UF {FLID} <KBE> UF <TBE on target> UF {Sector ID} {FLID} <KBE> UF {Sector ID} <TBE on target> UF {Sector ID} {Frequency} {FLID} <KBE> WR (F7) WR Request Weather Display WR {station ICAO code (up to 3 simultaneously)} <KBE>

To handoff an aircraft to another sector: [SCTID] [FLID] [SCTID] <TBE> Example: 56 342<KBE> This would handoff to Sector 56 from a sector within the same FIR. N56 <TBE> This would handoff the slewed to New York ARTCC Sector 56 from an adjacent FIR. To cancel a handoff: QT [FLID] QT <TBE> Example: QT 342<KBE> This would stop the handoff to the next sector.

This section will take a look at practical applications of the functions found this manual. Many ERAM instructions can be sent via CPDLC with the addition of the Uplink parameter (/U). In order for the controller to have the ability to send a message via the CPDLC Uplink the aircraft must be: CPDLC Capable and logged into the appropriate CPDLC Service area. Aircraft that meet these requirements are shown with a White Box in the CPDLC Prefix Field in line 1 of their FDB. ERAM message notation allows for many variables to optionally be used. All ERAM messages are composed in the MCA Any parameters in () are optional. The [FLID] can be either the Aircraft ID(ACID), CID, Squawk, or <TBE>. The [SCTID] is the Sector ID of the relevant sector. This is displayed in the "Active Sectors" list under the "HO" column. /OK is used to force the change on a data block not owned by the controller. This should be used only when regular commands are not sufficient. The Uplink parameter (/U) may be included in many commands to send the relevant CPDLC Message

It is highly recommended to not have multiple transmitters set to transmit on the same frequency simultaneously. The reason for this recommendation is because if an aircraft has LOS with both transmitters, they will get a blocking tone and will be unable to hear your transmission. If your transmitters are far enough apart though, this likely won't be an issue; however, please consult with your FIR's Facility Data Specialist first before deviating from this recommendation. Below is an example of generally how not to configure your VSCS panel: Reasons why the above image is wrong: You are configured to transmit on frequency 127.825 on both DTA and FFU. You are configured to transmit on frequency 133.900 on both FFU and QLC. You are configured to transmit on frequency 127.925 on both ILC and QLC. Here is the best configuration:

To enable a transmitter, TBP anywhere on the white box the then TBP on the "XMTR OFF" button. This will enable the transmitter to transmit and receive. To disable the transmit function only, but still receive, simply click the "XMTR OFF" button again. ATC have the option to route a transmitter output audio from your headset device (left image) to your speaker device (right image). To do this, TBP on the middle green box. When you activate your PTT to transmit on frequency, the XMTR OFF box will illuminate orange. When an aircraft transmits and breaks squelch on your frequency, the RCVR ON box will illuminate orange.

In the real-world, the Voice Switching & Control System (VSCS) is a hardware and application interface that allows controllers to activate VHF/UHF transmitters for associated sector frequencies and also make audio input/output selections. The VSCS is part of the controller's workstation, but is not technically part of the ERAM computer human interface. For the purposes of POSCON, however, we have combined the VSCS into the ERAM program and it can be accessed via the MASTER TOOLBAR > VIEWS menu. The VSCS requires a controller to be Signed-In to a position in order for it to populate data from the server. Once populated, it should look something like this: Each white box indicates a different air-to-ground frequency/transmitter combination. Within each white box, the top line indicates the VHF or UHF frequency while the bottom line indicates the transmitter name. The logic behind what is shown on this page is as follows: The first button located in the top left is always going to show the frequency of the sector you signed into. All other frequency/transmitter buttons are populated from the Facility + Area that you signed into. The two white boxes shown with a red line over-top of them indicate emergency transmitters. The three red PTT buttons located just below the emergency transmitters are push-to-talk buttons that activate the emergency transmitters. The logic for the emergency PTTs is as follows: PTT UHF - Is currently not operational. PTT BOTH - Will activate both the PTT UHF and PTT VHF when PTT UHF becomes operational. PTT VHF - Simultaneously activates the VHF 121.5 MHz transmitter and any other selected transmitters set to transmit. Here is how it would look if you push the PTT VHF button: On the bottom of the VSCS panel, there are various control buttons. The only button that works in this row currently is the Air-to-Ground Alternate (A/G ALT) page button. This button shows a second page of frequency/transmitter buttons if needed for overflow.

Our goal is to create the most realistic aviation radio emulation available and to that end, we have simulated some key characteristics of VHF radio such as line-of-sight (LOS), terrain occlusion, and blocking. Users need to be aware that, while these features add additional realism, they also can create real-world limitations. VHF only works when the ATC ground transmitter and the aircraft are in direct line-of-sight of each other. There are many variables that affect line-of-sight such as transmitter elevation, altitude of the aircraft, curvature of the earth, and surrounding obstructions such as terrain. All of these variables are accurately modelled on POSCON, thus if an aircraft loses line-of-sight with your transmitter, you will lose radio coverage with the aircraft. Currently, cross-coupling of frequencies is not available so we have created a few temporary workarounds to provide effective top-down service to pilots. Top-Down Transmitters - We have created a few "fake" transmitters for each FIR strategically positioned in locations where aircraft on the ground at any airport within your airspace can hear your transmissions. Your Facility Data Specialists will advise you what the names of these transmitters are. Guard Transmitters - For Guard frequency (VHF 121.5 or UHF 243.0), we have applied the same concept as the "top-down" transmitters, but on a sector-by-sector basis. Each Guard transmitter is positioned strategically within the airspace for maximum effectiveness.

This section will describe the the POSCON's voice system as well as how to utilize it's functionality as an air traffic controller.

These symbols represent how ERAM is tracking a target. They are always used in conjunction with FDBs, LDBs, and E-LDBs which are described in detail in the next section. Free Track - A target is tracked by ERAM, but is not flying along the entered route. Flight Plan Aided Track (Flat Track) - A target is tracked by ERAM and is flying along the entered route within a default tolerance of +/- 5 nm. Coast Track - No target is being tracked. The target is below radar coverage or has logged offline. ERAM will continue the track movement in the last known direction and speed before the target disappeared. This will occur for 5 minutes and then the system will automatically delete the coasting track.

These symbols represent the actual radar return of an aircraft. When separation is applied, it needs to be applied from this symbol. These are the only implemented target symbols at this time:

ERAM uses many symbols to signify different interactions with radar returns and data blocks. The following symbols should be committed to memory or else it will be hard to understand what the program is telling you.

Like everything else, the POSCON Flight Plan System is a large departure from those found on legacy networks. The flight plan system has a timeline of various triggers/events that are derived around what pilots enter in the Date of Flight (DOF) and Departure Time fields on the flight plan form. It is important to understand how and when these triggers/events occur in order to use the system properly. Here is the timeline of triggers and other important events: Flight plans can be filed as early as 5 days prior to intended DOF and Departure Time. Flight plans can filed as late as the current time. Up to 35 minutes prior to filed Departure Time, the flight plan can be edited. At 35 minutes prior to filed Departure Time or current time, whichever is later, the flight plan is sent to ATC for processing and editing is locked to the pilot user. After takeoff, the flight plan is officially activated if the pilot is squawking the code received from the server (through CPDLC) or received from ATC. In the future, ATC will need to DM (Departure Message) the flight for the flight plan to activated. If the flight plan is not activated, it can be manually deleted by the filing pilot from the time it is filed to 2 hours after filed DOF and Departure Time. If the flight plan is not activated, it will permanently time-out 2 hours after filed DOF and Departure Time. The flight plan is transferred automatically between FIRs by the server or manually by ATC, if online. If the pilot disconnects and plans to reconnect while airborne, they need to reconnect in the same FIR the disconnect occurred in (with the same squawk code) to re-correlate your flight plan to the target. If ATC is online, they can re-correlate the target manually. Upon landing, an activated flight plan will deactivate. If a flight plan needs to be deactivated while the airplane is still airborne, then the controller will be able to do this by the command QX FP {FLID} <KBE> ATC have full access to the Flight Plan List page to view and edit flight plans. There are four status icons that are used on the Flight Plan List page: - Flight Plan Active - Flight Plan Pending Activation - Flight Plan Cancelled by Landing - Flight Plan Cancelled by User

There are regions surrounding each ARTCC/FIR that define the extent of coverage of that ARTCC/FIR. These regions are defined on the server and configured by network administration at the time the ARTCC/FIR is first created. Surveillance Area of Interest (Surv AOI) This defines the area around an ARTCC/FIR where aircraft will be displayed to ATC. This area essentially filters all other network traffic and only shows relevant targets within range of that particular ARTCC/FIR. It is depicted as the gray rectangle in the image below. Aircraft Problem Detection Area (APD) This boundary defines the area within which the controller receives conflict probe alerts. It is depicted as the purple boundary in the image below. Flight Planning Area of Interest (FP AOI) This boundary is an adapted area outside the Center Boundary where Flight Plan (FP) data is available from other ERAM facilities. It is depicted as the green boundary in the image below. Area of Responsibility (AOR) This boundary is also known as the Center Boundary. It is depicted as the red boundary in the image below.

The POSCON Air Traffic Control System is a large departure what can be found on legacy networks. Over the past few years, our Facility Data Team has working hard to develop and upload airspace volumes to the server. As a result of the server now being aware of these volumes, it can effectively use them to analyze routes, sector ownership, handoffs, CPDLC, traffic management, and other complex interactions. Currently, we have the entire United States on the server and many other foreign countries as well. Why does server airspace awareness matter to the average controller? Here are a few important understandings controllers must have: The server handles the tracking of aircraft, not the client software. When you sign onto a position, you are simply letting the server know that you wish to take ownership of that sector and any other sectors that combine to it. This is hugely advantageous if you accidently get disconnected from the server. If this happens, all you have to do is sign back into the sector you were working and all of the aircraft that you had tracked prior to the disconnect will still be tracked. The server automatically combines airspace based on the configurations set by Facility Data Specialists. In the facility data, sectors can configured to pair to another sector in the event that sector is not owned or assumed by another controller. This "combined-to" logic typically starts at the Clearance Delivery being the lowest level and Center being the highest. The server evaluates aircraft positions and automatically assign squawk codes from ranges specific to the FIR/ACC/ARTCC the aircraft are in. On legacy networks, squawk code ranges are created in files and distributed to users as part of the client package or often a separate download. On POSCON, the ranges are configured by Facility Data Specialists and then are automatically invoked when flight plan is filed or when a controller requests a squawk code. The server knows where the aircraft will be in the future based on trajectory analysis. The server evaluates aircraft trajectories and can predict where a they will be in the future. While this feature is not currently being used, it will be very useful in the future when we implement auto-handoffs and traffic management software.

7g.6.1 Frequency. The following meetings should occur at the listed intervals: Network Director/Manager meeting - once per calendar month Division meeting - once per calendar month per Division 7g.6.2 Attendance. In order for a meeting to occur, at least three staff members must be in attendance. Network Director/Manager meeting attendance is restricted to Network Directors and Network Managers unless an exemption is made by the President. Division meeting attendance is restricted to the respective Division staff and any Network Director or Network Manager who wishes to attend. 7g.6.3 Notification. Notification of upcoming meetings should be made no later than 5 days prior to the meeting in the respective Discord with an @everyone mention. For Divisions, this should be in the #local-divsion-team channel, 7g.6.3 Agenda. When a meeting is held, an agenda must be created and distributed at least 24 hours prior to the meeting to all applicable staff members. 7g.6.3 Minutes. Meetings must have one person designated as the secretary to document the meeting discussion. At the conclusion of the meeting, the meeting minutes must be posted in the appropriate section within the document system.

We call "must" and "must not" words of obligation. "Must" imposes an obligation on the readers to tell them something is mandatory. "Must not" are used to say something is prohibited. While "shall" and "shall not" are not the most suitable terms for obligation, if you see the terms used in these policies, they have the same meaning as "must" and "must not". "May" means purely optional and does not imply that the writer recommends that option to the reader. "Should" also means optional but implies that the writer recommends and advises the reader to use that option. Summary: Must = mandatory Must not = prohibited May = optional Should = recommended These are the only valid word choices to convey those meanings.

Each View (i.e. window) in ERAM typically has an associated menu that can be invoked by TBEing when the cursor is within the boundary of the View OR by clicking the located in the top left corner of each View. You can see some examples of the View Menu from the sections above. The content in each View Menu usually varies, but some common options available include: O / T - This allows the user to choose between opacity or transparency. BORDER - This allows the user to choose between borders or borderless. FONT - This allows the user to choose between different font sizes. BRIGHT - This allows the user to adjust the brightness of the View. To close a View, a user simply needs to TBE/TBP on the associated Toolbar button. Associated View is CLOSED: Associated View is OPEN: Alternatively, a user can TBE/TBP on the and the View will close.

The Time View displays the current UTC time and can be customized and located anywhere on the display; but cannot be suppressed. To customize the Time View: TBE the Time View to bring up the Time View Menu. TBP/TBE desired menu item as appropriate to change Time View settings. To move the time view: TBP the Time View; a move frame (white view outline) will be displayed and the trackball cursor will be attached to the upper left hand corner of the frame. Move the frame to desired location on Situation Display. TBP/TBE to drop the frame and place the Time View.

The RA View displays the response to a flight plan readout of an active flight as well as the readout of a DATIS query. The view can be moved to any location on the Situation Display (including areas covered by a Toolbar). The RA View has a default of 4 lines but will automatically expand to as many lines as needed. Only one message at a time is displayed in the RA View. New data replaces the currently displayed data. Here is an example of when a flight plan is queried: Here is an example of when a DATIS is queried. The example also includes the RA Menu open: To access the RA View Menu, TBE when the cursor is within the boundary of the RA View when a pick area is not selected. Functions available in the MCA View Menu: WIDTH - Allows the user to set the width for the RA View (between a 25 or a 50 maximum character width) FONT - Adjusts the font size of the RA View. There are 3 sizes, TBP to decrease and TBE to increase the font size. BRIGHT - Used to change the brightness setting of the RA View. The brightness range is 0–100 in increments of 2. TBP to decrease and TBE to increase the brightness setting. CLEAR - Used to the clear the contents of the RA View. TBP/TBE the CLEAR menu item. The RA View contents are cleared and the RA View contracts to 4 lines. To move the RA View: TBP/TBE anywhere in view except scrollbars or arrows. A view outline appears. Trackball movement places outline in desired location. TBP/TBE to select the new location. RA view displays.

The MCA View is used to enter messages at the R-Position. As shown below, the MCA View contains two distinct areas: the Preview Area and the Feedback Area. The Preview Area is the upper area of the MCA View and used for message composition. The Preview Area is initially displayed as two lines and can expand as more characters are entered. The left and right arrow keys can be used to scroll through the Preview Area and the ESC key can be used to clear the entered text. When a command is ready, press the keyboard ENTER key to execute the command. The Feedback Area is the lower half of the MCA View and displays messages entered into the system from the Preview Area. The Feedback Area is initially displayed as 4 lines and can expand up to 34 lines if needed. The Feedback Area displays the following types of messages: Accept messages – preceded by a green check Reject messages – preceded by a red X Error messages – preceded by a red X When an Accept or Reject message is returned to the Feedback Area, the Preview Area is cleared and will shrink back to two lines if it was previously expanded. The Preview Area expansion capability will be allowed again when the controller clears the Preview and Feedback Area by pressing the ESC key, a hard labeled function key, or by picking a category function key. When the controller invokes the Recall function (up arrow key on keyboard), each entered command and up to 2 lines of associated feedback (accept, reject, or error) message is recalled and displayed. To access the MCA View Menu, TBE anywhere on the Preview or Feedback Areas (other than arrows and scroll bars). Functions available in the MCA View Menu: PA LINES - The number of lines displayed for the Preview Area. WIDTH - Provides the user with the option of controlling the width of the Preview Area. FONT - Adjusts the font size of the MCA View. There are 3 sizes available, TBP to decrease and TBE to increase the font size. BRIGHT - Used to change the brightness setting of the MCA View. The brightness range is 0–100 in increments of 2. TBP to decrease and TBE to increase the brightness setting. To move the MCA View: TBP/TBE anywhere in view except scrollbars or arrows. A view outline appears. Trackball movement places outline in desired location. TBP/TBE to select the new location. The MCA view displays.

The Situation Display is the area used to view traffic and sector data. The orientation of the Situation Display is always true north. The Situation Display has a dynamic projection feature which transforms the sector data as you move away from the equator. To pan around the Situation Display, hold right-click on your mouse and move your mouse to the desired location. To zoom, use your mouse scroll-wheel (forward zooms in, aft zooms out). NOTE: Users are prevented from using the scroll-wheel while the cursor is positioned over any portion of a target, position symbol, or datablock. Zooming can alternatively be accomplished by clicking TBP/TBE on the "RANGE" button on the Master Toolbar. Once open, a user can drag the range slider up or down to adjust the range using TBP. Additionally, TBP can be used to choose one of the preset values (black numbers). Positioning the cursor in the green region and then using TBP will decrease the range while TBE increases the range. The brightness of the background can be controlled by clicking TBP/TBE on the "BRIGHT" button on the Master Toolbar. Locate the "BCKGRD" button and using the TBP button, you can incrementally decrease the value. Alternatively, by using the TBE button, you can incrementally increase the value. Holding down either the TBP/TBE button will rapidly decrease or increase the value respectively.