Andrew Heath

Users demonstrate honesty on POSCON by maintaining their integrity and upholding a set of moral principles. Behavior that can be characterized by deceitfulness is the antithesis of honesty and will not be tolerated on POSCON venues.

Users demonstrate empathy for one another by having patience and understanding. POSCON attracts a whole spectrum of experience levels and the ability to be tolerant of someone who may not know as much as you is a core value of POSCON. Behavior that can be characterized as lacking restraint or unempathetic will not be tolerated on POSCON venues.

Users demonstrate responsibility on POSCON by behaving in a way that adheres to our policies and procedures. In addition, users who are responsible are also accountable for their actions. Failure to admit errors, concede when wrong, or refusing to comply with our policies is the antithesis of responsibility and is not tolerated on POSCON venues.

In addition to the policies outlined in 6.2, user created content must also comply with applicable policies in: User Agreement Content Creators Content Guidelines Discord

Users demonstrate respect for one another by having due regard for the feelings, wishes, rights, achievements, or traditions of others. In addition, users who are respectful are also courteous. Behavior that can be characterized as egotistical (know-it-alls), narcissistic, rude, or aggressive is the antithesis of respect and this type of behavior will not be tolerated on POSCON venues.

POSCON membership is a privilege, NOT a right. This is not a public utility and members do not have any special government-issued rights. Other than avoiding cases of discrimination, POSCON has no special responsibility when it comes to allowing members access to the network.

There are two types of Real-World Verification Badges available to users on POSCON: "RW Pilot" - This badge identifies a user who has achieved a high level of experience as a real-world pilot. Eligibility includes those users who possess an Air Transport Pilot license or equivalent. "RW ATC" - This badge identifies a user who has achieved a high level of experience as a real-world ATC. Eligibility includes those users who possess an Air Traffic Control Specialist license or equivalent. Basically, any air traffic controller that has achieved at least one real-world solo position certification is eligible. "RW ATC / Pilot" - This badge identifies a user who has achieved both of the above.

Those users who wish to apply for the Real-World Verification Badge must send an email to [email protected] and provide our team with the following details: The type of badge you are applying for (pilot or ATC) Your full name as it appears on the real-world license Real-world license number Your POSCON ID Either a picture/scan of the license (address can be redacted) OR a link to a publicly accessible website where the information can be verified by our team NOTE: If you possess both an ATP and an ATC Specialist license (or equivalent), make sure to include both so we can indicate your status.

The Real-World Verification Badge is an optional feature used to identify those individuals that have achieved a certain level of real-world status in aviation. The badge is completely optional, but POSCON encourages all users who meet the eligibility requirements to apply. Once approved, the badge will be displayed next to a user's name throughout the HQ. The purpose of the badge is to legitimize the accuracy of comments, forum posts, and other content created by those users as they discuss real-world aviation topics.

The following policies apply to all operations that are conducted at an Uncontrolled Airfield or in Uncontrolled Airspace. 3c.3.2 Early Contact Attempts. In some cases it may be operationally beneficial to establish communications early with a pilot entering Controlled Airspace from Uncontrolled Airspace. If it is deemed to be operationally beneficial, then ATC may make one early attempt to contact the pilot either via CPDLC or on Guard so long as the pilot is within 50 NM of entering the lateral boundary of Controlled Airspace. The pilot can choose to ignore the contact request without retribution; however, if the pilot does establish communication with ATC, then the pilot is responsible for maintaining two-way communication. 3c.3.3 Unresponsive Pilots. The procedure found in 3c.2.2 maybe be used. There are two exceptions to this rule: If the pilot's TOD (as calculated from published procedures using the 3 to 1 ratio) is located outside of Controlled Airspace, then these procedures may be initiated no earlier than the calculated TOD. If the pilot will enter Controlled Airspace in conflict with other traffic (e.g. dead-heat tie to the same destination airport), then these procedures may be initiated no earlier than 3 minutes prior to the ATC's boundary.

The following policies apply to all operations that are conducted at a Controlled Airfield or in Controlled Airspace. 3c.2.1 Top-Down Service Frequency Usage. Typically, one frequency shall be used for top-down controlling. In this case, role playing of lower positions is not permitted. For example, you are working New York Center on 125.325. You are not permitted to handoff to yourself on the same frequency and pretend to be New York Approach. If you desire to role play in this way, you can electively enable additional transmitters/frequencies as long as the quality of services is not degraded. As soon as you begin missing radio communications or there is a significant amount of blocked transmissions occurring, you MUST switch back to the single frequency method. 3c.2.2 Unresponsive Pilots. This procedure may only be initiated when the unresponsive pilot is within Controlled Airspace and only by the applicable ATC. There are two exceptions to this rule: ATC must attempt each step in following procedure before using self-help moderation methods (e.g. Compliance Timer or Report Issue): If the pilot is already tuned to the appropriate ATC frequency as indicated via the Live Map, then ATC must first attempt basic communication verification on the appropriate frequency using phraseology similar to: "<Pilot Callsign>, <ATC Callsign>, if you read this transmission, acknowledge with an IDENT." If the pilot does in fact acknowledge, then ATC can assume pilot is having transmission issues and no further action is necessary. If acknowledgement is not received from the pilot within a reasonable amount of time, then proceed to step 2. If the pilot is logged into CPDLC, ATC must uplink the appropriate frequency to the pilot. If the pilot does not respond within 3 minutes, then proceed to step 3. If the pilot is tuned to Guard on either radio as indicated via the Live Map, then ATC must make two attempts to contact the pilot on Guard using the following phraseology: "<Pilot Callsign>, <ATC Callsign> on Guard, contact <appropriate ATC Callsign> on frequency <appropriate ATC frequency>." If neither attempt is successful within a reasonable amount of time, move to step 4. Will ATC be required to issue a control instruction while the pilot is in Controlled Airspace? If NO, then continue to monitor pilot and attempt contact. File negative feedback for the pilot regarding the repeated attempts to contact them with no response. If YES, then move to the procedures outlined in the Self-Help Moderate Methods methods.

The following policies apply to all operations. 3c.1.1 Language Usage. All ATC must be proficient in the English language. All communication initiated in English must elicit a response in English. ATC must not assume that a POSCON Member (pilot or ATC) knows the local Division language. Local languages may be used so long as both the communicator and the receiver mutually agree to such exchanges. 3c.1.2 Working Microphone. A working microphone is required and all controllers must be prepared to talk on frequency at all times. 3c.1.3 Monitoring Guard. Controllers shall monitor Guard (121.500 MHz) at all times. If this Guard is not set up in the VSCS panel, consult with the Division Facility Data Specialist. Controllers shall only use Guard frequency to attempt to contact an unresponsive pilot and get that pilot to the correct frequency. Conversations, animal noises, or any other unrelated chatter is strictly prohibited on Guard. 3c.1.4 Unnecessary Communication. Keep unnecessary chatter on active control frequencies and landlines to a minimum. Any form of trolling on any communication method is strictly prohibited. In this context trolling is defined as screaming, intentionally blocking transmissions, playing music, pretending to be another aircraft or ATC, intentionally leaving your mic open, or anything else deemed as overly disruptive. 3c.1.5 Phraseology. Controllers must follow the phraseology standards outlined in 3g.2.2. That means controllers should make every effort to keep all communications as standard as possible. Controller should avoid "shortcutting" or being lazy with phraseology.

Controllers must use real-world weather to determine airport/airspace configuration and traffic patterns. See 3o.3.2 for exceptions to this rule.

3g.2.1 AIP Standards. Controllers are required to follow the standards published by the real-world administrative authority for the area in which they are simulating. For example, if controlling in the United States of America, that authority is the FAA and controllers are required to adhere to relevant sections from the AIP and AIM. 3g.2.2 Phraseology. Controllers are required to follow the phraseology standards published by the real-world administrative authority for the area in which they are simulating. For example, if controlling in the United States of America, that authority is the FAA and controllers are required to adhere to the JO 7110.65. 3g.2.3 Facility Specific Standards. Divisions and Sub-Divisions are required to publish ATC specific standard operating procedures (SOPs) and letters of agreement (LOAs). When published, these documents are considered policy.

This is actually an intentional feature of the voice software that was designed to prevents stuck microphones. After 30 seconds of a continuous transmission, the voice software will cut the transmission and alert the user to this automatic feature with a beep.

The navigation data used by the Radar Client updates every 28 days at 0901 UTC. The previous AIRAC cycle will be available for 24 hours after the expiration date/time providing a small buffer for pilots that departed prior to the expiration data/time. For example: A flight that departs before 0901 UTC on the expiration date will be processed using the old AIRAC cycle. A flight that departs at or after 0901 UTC on the expiration date will be processed using the new AIRAC cycle.

Garbled transmissions can occur if your CPU usage is too high (e.g. 95-100%). Attempt to reduce the load on your CPU and try again. If the problem persists, please contact POSCON Support.

Typically this error looks something like this: In order to solve this issue, open the Windows Registry Editor and create the folder and path as shown: Computer\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\FlightSimulator.exe

The following error occurs if you do not have .NET Framework 3.5 enabled in optional Windows Features: https://docs.microsoft.com/dotnet/framework/install/dotnet-35-windows#enable-the-net-framework-35-in-control-panel