Support Documents

A: Here are the steps to get connected:

1. Using a web browser, navigate to https://launcher.poscon.net/latest and download the file when prompted. This application is currently only available for Windows (Apple support will come later).
2. Install the Launcher Client by following all the on-screen instructions.
3. Once installed, navigate to "Library" within the Launcher Client and download the respective pilot clients for the simulators you use.
   
   • For FSX/P3D, you need to install a 3rd party model matching package. Previously we recommended installing the free FLAi model package, but recently FLAi was taken down permanently so it might be in your best interest to buy a payware package.
   • For X-Plane, the model set is included in the initial download.
     • NOTE: This download will take some time to complete.
   • For FS2020, there isn’t a model set yet.
4. Once the installation is completed, click the "Launch" button on the "Library" page for the software you wish to run.

NOTE: Unless you have completed the Welcome to POSCON Computer-Based Training Module, you will NOT be able to connect to POSCON in the Live mode.

A: We tried to design or clients to be intuitive enough that they would not require any documentation to operate; however, we have provided some user manuals in the Support section of our forums.

• X-Plane Pilot Client Manual
• FSX/P3D Pilot Client Manual
• Radar Client (ERAM) Manual

A: Connecting to POSCON with an ADS-B callsign via the pilot clients is required. This satisfies the real-world requirement that exists in many countries to have ADS-B operable on all aircraft. The callsign that you use for ADS-B can be the same or different than the callsign you specify in the flight plan form. The callsign you specify in your flight plan will override the ADS-B callsign once your flight plan is either activated by ATC or by you when squawking the server assigned squawk code. If ATC chooses to modify your callsign, their modifications will always take precedence over what you have specified.

While ADS-B callsigns are not required to be unique, flight plan callsigns must be unique at any given time. As such, callsigns can also be reserved up to 5 days in advance and for the entire duration of your flight. For more information on callsign reservations, see the callsign reservations topic below.

A: By default, your ADS-B callsign will appear on the map. In order to see your filed callsign on the Live Map, your flight plan must be activated. To do this:

1. If ATC is online for the area you are operating in, request clearance from ATC and squawk to code they assign to you; or
2. Log into CPDLC in the Pilot Client Web UI using the callsign associated with the flight plan on file and the FIR in which you are operating in. Once logged on to CPDLC, got to the "ATC" tab and click "CLEARANCE REQUEST" tab. Check the "REQUEST CLEARANCE" box and click "SEND". A few seconds later, the server will automatically send you a squawk code via CPDLC message. Enter the squawk code given to you and then takeoff. After liftoff, your flight plan will now show activated and you should see the correct callsign on the map.

A: It depends on if you have filed and activated a flight plan. If you have not filed and activated a flight plan, you can change your ADS-B callsign at anytime while connected by visiting the settings window located in your respective pilot client or on the Aircraft ID section of the Pilot Client Web UI (located on the Radios page under “MODE”).

If you have filed and activated a flight plan, your callsign cannot be changed unless you:

1. Are no longer under ATC coverage; and
2. You change the squawk code associated with your flight plan correlation.

Once those two requirements are met, you can change your callsign by changing your ADS-B callsign as detailed above.

NOTE: If you have filed and activated a flight plan, once you land at any airport, your flight plan will cancel and your callsign will automatically revert to your specified ADS-B callsign.

A: You can file a flight plan by clicking here.

A: Yes, we are directly integrated with SimBrief’s flight plan prefiling system. You can also import FPL files from any software that outputs these types of files (PFPX is one of the more popular ones).

A: Typically this means you have not properly activated your flight plan.

If you get disconnected, you have up to 15 minutes to reconnect without losing flight plan correlation. If you are disconnected for 15 minutes or more, your flight plan will automatically cancel and you now need to comply with the following procedure:

1. Go to the Flight Plans List page and find your previous flight plan.
2. Click on the "Copy FPL" button.
3. Fix any errors that you find. Sometimes a mid-flight refile will have errors due to previous ATC modifications.
4. Click "Import PPOS" (your sim must be connected to POSCON to see this button).
5. Click submit.
6. Logon to CPDLC using the FIR/UIR that your aircraft is currently in.
7. Request Clearance again.
8. You should now receive a new squawk code. Squawk the code and your flight plan is now reactivated.

A: For X-Plane, the traffic library is included in the initial download of the client. For FSX/P3D, you need to install a 3rd party model matching package. Previously we recommended installing the free FLAi model package, but recently FLAi was taken down permanently so it might be in your best interest to buy a payware package. For FS2020, there isn’t a model set yet.

A: There is not just one specific frequency to use while operating at uncontrolled fields or while in uncontrolled airspace. Our network attempts to model the real-world as closely as possible, which means multiple communication frequencies are used. This topic is covered in-depth on the Welcome to POSCON CBT and also in our Pilot Policies - Communications.

A: The likely reason is due to your framerates dropping below an average of 20 frames per second (FPS) over an extended period of time. POSCON requires that you maintain above 20 FPS due to rendering limitations in X-Plane. More information on this topic is covered in the X-Plane Pilot Client Manual under the “Accurate Ground Speed Simulation” and “Automatic FPS Control” sections.

A: No worries! We know the ICAO flight plan form can be complicated, so we included a built-in help tutorial. You can use the information icon located next to each field header for instructions on how to fill in that field correctly. Additional questions can be asked in the "support" section of our Public Discord or the forums.

A: POSCON does not allow you to optionally use text for communications with ATC, unless you are in the enroute phase. If you are in the enroute phase, you must be available via CPDLC. Our full communications policy is available at Pilot Policies - Communications Policies.

NOTE: As of March 17th, 2021, CPDLC is not fully implemented, which means that voice is required in all phases of flight.

A: There are a few options for casual chat. The first option is to connect with other members through our Public Discord server. This is a great place to meet other members and discuss topics such as network activity, flight simulation, and even real-world aviation.  In addition to the Public Discord, if you are connected to POSCON, casual chatter can also be initiated on Air-to-Air VHF Frequency 123.450 MHz. Just remember though that all chat is bound to Pilot Policies - Communications Policies, POSCON Content Guidelines, and POSCON User Agreement.

A: We are still developing the standards for VA registrations so we are currently not accepting any registrations at this time.

A: No, we have decided to not include any sort of pilot rating system on POSCON.

A: The flight plan system has a timeline of various triggers/events that are derived around what you 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 and not mistakenly think the flight plan system is broken. 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 be 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 you are correctly squawking the code received from the server (through CPDLC) or received from ATC.
• 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.
• Your flight plan is transferred automatically between FIRs by the server or manually by ATC, if online.
• If you disconnect and plan to reconnect while airborne, you need to reconnect in the same FIR the disconnect occurred in (with the same squawk code) to re-correlate your flight plan to your aircraft. Generally speaking, this is more “gee-whiz” knowledge and has no effect on your flight because it only applies when ATC is offline. If ATC is online, they can re-correlate the target manually.
• Upon landing, an activated flight plan will deactivate.

NOTE: In many cases, the reason why you are unable to edit your flight plan is because the current time or date falls outside of the timeline above.

A: The squawk code system has a timeline of various triggers/events that are derived around what you enter in the Date of Flight (DOF), Departure Time, and Departure Aerodrome 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 and not mistakenly think the squawk code system is broken. Here is the timeline of triggers and other important events:

• For a squawk code to be generated, a flight plan must be on file that complies with the flight plan system parameters.
• Between 35 minutes prior to filed Departure Time and 2 hours after filed Departure Time, the squawk code can be retrieved from CPDLC.
• In order to retrieve a squawk code from CPDLC, the aircraft must be in the same FIR as the filed Departure Aerodrome. You can use the "Import PPOS" button on the flight plan form to import your present position into Departure Aerodrome field if you have left the original FIR.

NOTE: In many cases, the reason you are unable to receive a squawk code from CPDLC is because the current time or date falls outside of the timeline above.

A: The callsign reservation system has a timeline of various triggers/events that are derived around what you enter in the Date of Flight (DOF), Departure Time, and Total EET 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 and not mistakenly think the callsign reservation system is broken. Here is the timeline of triggers and other important events:

• Between 1 hour prior to filed Departure Time (or the present time, whichever is later) to scheduled arrival time (Departure Time + Total EET), the callsign you enter in the Aircraft Identification field is reserved.
• The callsign associates to your aircraft when you are correctly squawking the code received from the server (through CPDLC) or received from ATC via voice or through CPDLC.
• After takeoff, the callsign reservation is extended until 2 hours after scheduled arrival time (Departure Time + Total EET) to account for airborne holding and other factors.
• 5 minutes after actual landing, the callsign is released back to the system and may be used by another flight scheduled to depart at least one hour later.

Callsign conflicts are possible within the second hour after the scheduled arrival time.

NOTE: The above process applies how to receive a callsign using the flight plan and the squawk code systems. For flights that do not have a flight plan (such as general aviation), you can put the callsign in your Mode-S transponder in the Aircraft ID section.

A: Nope! Just file a Flight Plan from the departure and destination of the Trip you want to do, connect online and activate your flight plan!

A: If you want an airport to be included in the next Trip, simply do regular flights to or from that airport. The more flights you do, the more chance that it will be included in the next Trip. To help increase your chances, the airports in the current Trip will not be included in the next Trip. Make sure when you do those flights, that you do not stay ghosted for more than 10% of the flight time!

A: Trips is an event that is enjoyed by everyone when working together. Your goal should be to work as a network of pilots to move passengers from their departure to their destination and it is fun when everyone is doing this together. With this mind, we do not allow ghosting for more than 10% of the flight time. So if your flight is estimated to be 2 hours and you were ghosted for more than 12 minutes (because 10% of 2 hours is 12 minutes), then your Trip will not count.

A: If you are disconnected, that is fine. Simply connect back on the network within 15 minutes and your flight (and Trip) will continue. If you are disconnected for more than 15 minutes then unfortunately your Trip will be cancelled and the passengers will be returned back to their departure airport.

A: Yes. Follow these steps:

1. Configure the sim to listen on a TCP port over IPv4 or IPv6 according to:
   https://docs.flightsimulator.com/html/Programming_Tools/SimConnect/SimConnect_XML_Definition.htm
2. Create a the CFG file at the following location:

   %LocalAppData%\POSCON\SimConnect Pilot Client\SimConnect.CFG

   according to https://docs.flightsimulator.com/html/Programming_Tools/SimConnect/SimConnect_CFG_Definition.htm and set the IP address to the sim machine.

NOTE: This procedure only applies for the SimConnect Pilot Client currently. X-Plane support for a remote host option will come later.

Yes, POSCON supports a basic shared cockpit experience. The way it currently works is that all ghosted pilots have a 20 meter protection zone surrounding their aircraft. Any model that is within 20 meters of any ghosted aircraft is automatically deleted until the model exits the 20 meter protection zone, then it reappears. For those familiar with MSFS multiplayer, this feature is very similar to how they handle aircraft that get too close to each other. In order to utilize this feature for shared cockpit experience on POSCON, use the following procedure:

1. The pilot who plans on being in charge of the radios on the network needs to log into POSCON using the Live Mode.
2. The other pilot needs to connect in the Ghost Mode. This pilot can listen to the radios, but cannot transmit.
3. The pilot who connects in the Live Mode should file the flight plan so that it can be activated without ATC intervention; however, if ATC is online to activate, either pilot may file the flight plan.