VX Flight Network Code of Conduct

Introduction

VX Flight is an online network where Ro-Aviation enthusiasts can further their passion in aviation to the extent that PTFS allows the user to. One of our goals here at VX is to provide everyone with a safe and welcoming experience for all members. Whether an experienced veteran of aviation, or a brand new member to the hobby, this network is here to provide everyone with the same experience.

To further these goals, the VX Staff Team has outlined certain rules and regulations that all users, regardless of class, must follow at all times on and off the network in order to participate in our server.

The VX Flight Network Code of Conduct is heavily inspired by the VATSIM Code of Conduct.

Note: The VX Staff Team reserves the right to punish people as they deem fit, even when the punishment given does not directly follow the global strike system.

A. General Code of Conduct

• A1. Everyone, regardless of race, ethnicity, sexuality, or gender is welcome on the VX network. Everyone shall be valued equally and no person shall be degraded for any reason regardless of identity, knowledge, or personal being.

• A2. English is the official language of the VX Flight Network. VX Senior Staff are unable to moderate and control in other languages. Users shall refrain from speaking other languages in VX.

• A3. All members on VX are required to have simple common sense. There is no reason to purposely find loopholes in the strike system, or the Code of Conduct to potentially make the experience of VX unenjoyable for others.

• A4. All members on VX are required to be respectful to one another at all times. Toxicity within our server, either on the Discord or ROBLOX server, will be tolerated.

• A5. Purposefully arguing or ignoring requests by VX Senior Staff will not be tolerated. All members are required to follow all instructions given by Senior Staff. If a staff members seems unreasonable or out of place, please notify a higher staff member of the issue politely.

• A6. All members are required to have a sense of class. NSFW, Adult Content, or just a simple lack of maturity will not be tolerated on the VX Flight Network.

• A7(a). Discussing or conversing in highly controversial topics, which include, but are not limited to politics and religion are prohibited. Conversing in this topics in the Discord or anywhere on VX may make other members feel unwelcome in the server.

• A7(b). To avoid making other members feel unwelcome too, using discriminatory language and/or slurs are prohibited. This includes any media that is posted that may make a member feel unwelcome, too.

• A8. Unless given explicit permission from VX Senior Staff, using alternate accounts for any reason, such as bypassing a modlog, or simply having an alternate account in the server, is strictly prohibited. This includes any alternate accounts that are used for channel observation.

• A9. Do not harass other members. Impersonation of a member or role falls under this category.

• A10. Using any sort of Discord client (such as BetterDiscord) is strictly prohibited and will result in an immediate permanent ban from the VX Flight Network if caught using one.

• A11. Self promotion and/or advertisements in VX are not allowed. This includes invites to other Discord communities, or links to social media accounts.

• A12. Members of VX must, at all times, follow ROBLOX and Discord Terms of Service. All rules in VX are on top of the terms outlined by ROBLOX and Discord in their respective Code of Conduct and Terms of Service.

• A13. Only members of VX Senior Staff, including ARTCC ATMs and DATMs, are allowed to advertise the VX Flight Network in PTC, MJ's Charts or any other PTFS related servers.

• A14. The VX Flight Network Suggestion Forum posted in the VX Discord Server shall only be used for future suggestions for the ROBLOX and/or Discord Server. Using the forum for general discussion, or irrelevant topics is not allowed.

• A15. Using VX resources (including TRACON RVM's, SOPs, LOAs, Documents, etc.) for your own server will result in a permanent blacklist from your server.

B. General In-Game Code of Conduct
All rules listed pertain to general play time in the VX ROBLOX PTFS Private Server.

• B1. All users must have at least 100 minutes of in-game flight time prior to obtaining the VX P0 Rating

• B2. Pilots are not permitted to share the ROBLOX Game Link to any member without the Pilot or ATC role, or anyone who is not a current member of the VX Flight Network

• B3. All pilots participating on VX must have a headset/speakers. A microphone is not required, and if a user does not currently have a microphone, they are required to utilize the ROBLOX chat for flying.

• B4. While on the server, all pilots AND controllers must have the ROBLOX chat open at all times.

• B5. When flying and controlling on the network, you must have the "Push To Talk" feature enabled on Discord.

• B6. All users must remain in the appropriate VC for the airspace they're in.

• B7. Voice changers/soundboards are not allowed in VX. This includes Discord Lounge Channels, and ATC frequencies.

• B8. Use of VX approved charts, resources SOPs, documents, etc. for other PTFS roleplays such as ATC24 are strictly prohibited.

• B9. If you suspect a member of VX is struggling in any way as a pilot or controller, help them in a realistic manner, and at the right time. VX promotes a positive learning environment for everyone, regardless of class.

• B10. If a rules is broken, all users are obligated to file a report of the user in the #reports channel in the VX Discord, or ping an online member of VX Senior Staff to sort out the issue. ARTCC Staff who do not hold a VX Moderation Position are unable to moderate.

• B11. Recording and uploading ATC frequencies to YouTube is permitted to all users. If a member does not want to risk their voice being on the internet, they shall either use text chat, or log off of the VX Network until a later date.

• B12. If the server is full, VX members are allowed to listen into the frequency, and spectate. Users are NOT allowed to transmit radio calls for themselves, or especially for any other aircraft.

• B13. ATC frequencies must only be used for pilot-ATC communications. Using the frequencies for discussing, chatting, or any other purpose is strictly prohibited. Controllers must coordinate using either Discord DMs, or another form of communication.

• B14. Any use of injectable ATC clients such as PTFS UI, PTC Scope, or any other client in an attempt to "improve" the PTFS ATC experience is prohibited. The only allowed way to use a radar client is through the use of VX's OBS Radar Scope method. We do not allow injectable ATC clients due to them breaking ROBLOX TOS.

C. Pilot Conduct
All rules listed pertain to flying as a pilot in the VX ROBLOX PTFS Private Server.

• C1. Before applying for P0, all users must have at least 100 minutes of in-game flying time.

• C2. Submitting troll flight plans for any purpose is strictly prohibited. The flight plan system is used by controllers to coordinate and sequence aircraft, and submitting troll flight plans disrupts the flow of that.

• C3. All flight plans must be filed using the correct ICAO codes of aircraft, departure/arrival airports, and must file a route that is valid for the VX Flight Network.

• C4. Air Force One escorts and roleplays are allowed, however, all controllers that the formation/roleplay will be flying into must approve of the request prior to departure release.

• C5(a). All pilots must abide by our worldwide speed restrictions:

  • • • • AT OR BELOW 1,500ft: 250kt

        • 1,501ft -> Max Altitude: 300kt

• C5(b). Military jets must follow the previous speed restriction above, except for:

  • • • • 1,501ft -> Max Altitude: 700kt

• C6. All pilots must abide by our Maximum Altitude.

  • • • • Max altitude for all aircraft: 10,000ft (FL100)

• C7(a). Pilots must file a flight plan using VX approved charts and resources.

• C8(b). Pilots must file their route using correct VX waypoints, and in the correct format.

  • • • • EXAMPLE: Route should be "LAR1 BTH GRAND GRAND1", not "LAR1 DEPARTURE, BARTHELEMY TRANSITION, DIRECT GRAND, GRAND1 ARRIVAL"

• C9. Pilots must follow all air traffic control instructions given to them. If an instruction seems unreasonable, notify the controller.

• C10(a). Pilots are not allowed to declare an emergency on the live network unless it is a fuel-related emergency. Additionally, an emergency must be a genuine emergency, and cannot be a simulated one by the pilot, such as an unruly passenger.

• C10(b). If a controller is unable to support your emergency on the live network, you are instructed to end your flight, leave the server, or lift the emergency.

• C11(a). The term "flight level" shall only be applicable to altitudes above and including 6000ft, where the VX Class Alpha Airspace begins.

• C11(b). VFR aircraft, like the real world, are not permitted to operate inside of Class Alpha airspace.

• C12. Purposely making a controller's job difficult by roleplaying unrealistic and unnecessary scenarios is prohibited. Controllers are here to provide a realistic service to pilots, and not all requests may be fulfilled. This is ROBLOX after all.

  • • • • Scenarios include, but are not limited to: Fake emergencies, clogging frequency, advanced operations out of VX ATC knowledge, pilot deviations, and more.

D. Air Traffic Controller Conduct
All rules listed pertain to being an Air Traffic Controller on the VX Flight Network.

• D1. Controllers who are new to VX, or are otherwise unfamiliar with an airspace shall educate themselves by first observing operations and/or studying procedures used in that location.

• D2. Controllers shall follow local rules and procedures. Controllers who choose to work in locations other than their requested and assigned location must follow the local rules and procedures at that specific location, and must be approved as a "visiting controller", where required by local controlled.

• D3. When logging onto the VX Network as an observer, users must not sign on as a controller, and instead "spectate" or listen into frequencies.

• D4. The VX Network recognizes the following, and only the following suffixes for air traffic control positions. A user shall only use the corresponding facility type when signing onto a position.

  • • • • DEL - (Clearance) Delivery

        • GND - Ground Control

        • TWR - Local/Tower Control

        • DEP - Departure Control

        • APP - Approach Control

        • CTR - Enroute (Center) Control

        • FSS - Flight Service Station

        • FD - Flight Data

• D5. Positions are occupied on a "first come" basis. Local facilities, with Division approval, may implement a procedure to book or schedule a controlling time within reasonable limits. Additionally, should a controller lose their connection with VX and return within a reasonable time period to find their position taken by another controller, the second controller shall relinquish the position to the original controller, with a proper position relief brief.

• D6. Only approved positions and their corresponding frequencies may be opened by controllers. Controllers may only open a positions that they are authorized to, in accordance with the global and local ratings policy.

• D7. A controller may post no more than four (4) ATIS' facilities to the VX Network to provide ATIS services to pilots. Additionally, a controller must not post an ATIS that is outside of their area of jurisdiction, designated by the area in the local/facility standard operating procedures.

• D8. Controllers are only permitted to delete their own frequency. Controllers are given permission to delete channels in the VX Discord Server as a way to sign off of the network, as that is the only possible way to do so.

• D9. A solo certification may only be given to controllers for Local control positions and above. In the event a solo certification is given, an ARTCC administrator, or whoever has granted the solo certification to the student, must notify the VX ATC Division Director prior to the solo certification being issued.

• D10. Controllers must only give instructions if they are reasonable. Pilots on the VX server have the right to not follow an instruction if the instruction given to the pilot can be deemed as unreasonable.

• D11. The VX Controller Coordination Guilded Server may only be used by VX Air Traffic Controllers. Sharing the Teamspeak information with pilots who do not hold a controller rating or position on the network is prohibited.

• D12. Any controller staffed on a TRACON position or above is required to use the VX OBS Video Maps provided in the Discord Server. These video maps assist controlling and help improve realism. If a video map does not exist for a select position, the controller has the right to freely use what they please.

• D13. Controllers must not control the three major airports without having a specific major endorsement within their ARTCC. The three major fields include:

  • • • • ZGR (Rockford): IRFD (Rockford International Airport

        • ZPH (Perth): IPPH (Perth International Airport)

        • ZTK (Tokyo): ITKO (Tokyo-Haneda International Airport)

• D14. Air Traffic Controllers staffing a Clearance Delivery (XXX_DEL) controller position are required to NOT be in the ROBLOX server. Having delivery controllers in the ROBLOX server when it is not needed wastes space for pilots who are wishing to fly.

This code of conduct was constructed and drafted by the members of the VX Staff Team as a whole. This code of conduct is effective as of January 2, 2024.