Bylaws
Article I. Name and Objects
Section 1.01 This organization is named vASA and is part of the Fusion Virtual Airline Alliance, or FVAA.
Section 1.02 This organization is not affiliated with Alaska Airlines or any of their subsidiaries, nor with any other airline/aviation companies. All flight and aeronautical information found through membership in the club is for entertainment use only. For any real-world flight operations consult the appropriate procedures and regulations as approved by your local regulatory body.
Section 1.03 This organization is not formally organized and shall not be operated for any financial gain or profit, nor will any service or item purchased for the group be used for personal or commercial activity.
Section 1.04 The purpose of this organization is primarily a social one: to gather like-minded aviation enthusiasts who enjoy enriching their flight simulation hobby through simulating the operations of a real-world airline.
Article II. Membership
Section 2.01 FVAA membership is open to any adult over the age of 18 by either invitation or by application. This age limit matches the age limit of vAMSYS, our service provider, however we do not accept parental permission as an exception to the age limit. A link to the vAMSYS Terms and Conditions can be found in Section 2.05, vAMSYS Terms of Service.
Section 2.02 Membership is fully voluntary.
Section 2.03 Membership is at the sole discretion of the FVAA administration team.
Section 2.04 All members are expected to abide by these bylaws and by all rules, codes of conduct, and/or community guidelines posted in any FVAA websites, chat servers, forums, etc.
Section 2.05 All members are expected to follow all vAMSYS policies in all vAMSYS and FVAA communities. vAMSYS’s policies are available for review at the links below:
Section 2.06 All members are expected to follow whatever posted rules, codes of conduct, and/or community guidelines are found on all VATSIM, IVAO, and PilotEdge websites, chat servers, forums, etc.
Section 2.07 Breach of any of the above may result in immediate termination of membership in the organization at the sole discretion of the administration team.
Section 2.08 To remain active, each member is required to file one (1) PIREP via our automatic flight tracking software, Pegasus, at least once every 120 days with a 10-day grace period. Failing to meet this requirement will result in the users account being deactivated, but not deleted.
Section 2.09 New members are required to file one (1) PIREP in their first ten (10) days after joining. Failing to meet this requirement will result in the users account being deactivated, but not deleted.
Section 2.10 If removed per Section 2.08 or 2.09 you may rejoin in the future by re-registering or by contacting the admin team and requesting that you be reactivated.
Article III. Administration Team
Section 3.01 The administration team of the organization is composed of five members.
Section 3.02 The administration team will, wherever possible, share equally the duties of running the organization, as well as the financial obligations.
Section 3.03 Any FVAA websites, memberships, or subscriptions which are currently owned and administered by a member of the administration team must be transferred to another member of the administration team should that member leave the group.
Section 3.04 The duties of the administration team are ad hoc and are coordinated internally and do not consist of any specifically set roles.
Section 3.05 The administration team has the final say on all operational matters within the organization except where constrained by any external requirements from the organizations in Section 2.05 and 2.06.
Section 3.06 The administration team will take decisions wherever possible by unanimous consent. When a disagreement over a decision cannot be resolved, each of the three members will have one vote on the matter and the majority opinion will be the decision.
Section 3.07 Each administration team member can individually enforce our bylaws and community guidelines on any FVAA websites, chat servers, forums, etc. without waiting for the other four admins, up to and including banning from membership any offending party.
Section 3.08 As required, from time to time, the administration team may delegate some tasks to certain members as is appropriate. These duties will be documented in the future when and if needed.
Section 3.09 Should a vacancy become available on the administration team, filling it will be at the sole discretion of the remaining members of the administration team.
Article IV. Privacy
Section 4.01 vAMSYS retains certain Personal Identifiable Information (PII) from users when they sign up for an account. This information is stored in vAMSYS databases to which FVAA has limited access.
Section 4.02 Refer to the vAMSYS privacy policy for further information on how your information may be collected, used, and removed.
Section 4.03 vAMSYS is the data controller of data input to vAMSYS systems; FVAA is a data processor.
Section 4.04 If a user wants to exercise their rights with regards to vAMSYS data, they must contact vAMSYS via email at hello@vamsys.co.uk.