Skip to main content

Bylaws

Article I. Name and Objects

Section 1.01 This organization is named “vAAL”.

Section 1.02 This organization is not affiliated with American Airlines or any affiliates. 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 likeminded aviation enthusiasts who enjoy enriching their flight simulation hobby through simulating the operations of a real-world airline.

Article II. Membership

Section 2.01 Membership in vAAL is open to any adult over the age of 18 by either invitation or by application.

(a) 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 (a).

Section 2.02 Membership is fully voluntary.

Section 2.03 Membership is at the sole discretion of the vAAL 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 vAAL websites, chat servers, forums, etc.

Section 2.05 All members are expected to follow whatever posted rules, codes of conduct, and/or community guidelines are found on all vAMSYS websites, chat servers, forums, etc.

(a) https://vamsys.io/legal/tc

(b) https://vamsys.io/legal/privacy

(c) https://vamsys.io/legal/cookies

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 vAAL requires each member to file one (1) PIREP via our automatic flight tracking software, Pegasus, at least once every 90 days with a 10-day grace period. Failing to meet this requirement will result in the users account being deactivated, but not removed.

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 removed.

Section 2.10 If removed per Section 2.08 or 2.09, you may rejoin in the future by requesting that your account be reactivated. Please contact the administration team at admin@virtual-aal.com to request reactivation. Do NOT create a new account as your old account was not deleted.

Article III. Administration Team

Section 3.01 The vAAL administration team is Mike Gold, Tim Long, Alex Dunbar, and Chase Burrell.

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 All vAAL websites and memberships are currently owned and administered by Mike Gold. Should he leave the organization in the future he will be responsible to migrate those accounts to another member of the administration team.

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 vAAL websites, chat servers, forums, etc. without consulting the other two 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.

Section 3.09 Should a vacancy become available on the administration team, the filling of it will be at the sole discretion of the currently serving 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 vAAL has limited access.

Section 4.02 Please refer to the vAMSYS privacy policy (https://vamsys.io/legal/privacy) 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; vAAL 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.

Section 4.05 From time to time, vAAL will export users first and last names and their email addresses from vAMSYS for the purposes of sending email newsletters. This information is not retained by vAAL.

Section 4.06 vAAL occasionally sends out email newsletters. This is done via Mailchimp, please refer to the Intuit privacy policy for further information about how they use stored information.

(a) (https://www.intuit.com/privacy/statement/).

(b) Users can unsubscribe from these emails. By unsubscribing, they are then manually unsubscribed from receiving future emails by vAAL staff by unsubscribing the member from the vAMSYS emailable pilot database/list.