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.

(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 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:

(a) https://vamsys.io/legal/terms-of-service
(b) https://vamsys.io/legal/acceptable-use
(c) https://vamsys.io/legal/privacy-policy
(d) https://vamsys.io/legal/cookie-policy

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.

Code of Conduct

Our Pledge

In the interest of fostering an open and welcoming environment, the FVAA administration team pledges to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socioeconomic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.

We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.

Our Standards

Examples of behavior that contributes to a positive environment for our community include:

  • Demonstrating empathy and kindness toward other people

  • Being respectful of differing opinions, viewpoints, and experiences

  • Giving and gracefully accepting constructive feedback

  • Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience

  • Focusing on what is best not just for us as individuals, but for the overall community

Examples of unacceptable behavior include:

  • The use of sexualized language or imagery, and sexual attention or advances of any kind

  • Trolling, insulting or derogatory comments, and personal or political attacks

  • Public or private harassment

  • Publishing others’ private information, such as a physical or email address, without their explicit permission

  • Other conduct which could reasonably be considered inappropriate in a professional setting

Enforcement Responsibilities

Community leaders — members of our administration and staff teams — are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.

Community leaders have the right and responsibility to edit or remove chat room messages that are not aligned to this Code of Conduct, as well as to warn and/or temporarily or permanently ban members from our chat rooms, our portion vAMSYS platform, and any other aspects of our community, and will communicate reasons for moderation decisions when appropriate. In extreme cases we will contact our service provider at vAMSYS to request full bans from the complete vAMSYS platform.

Scope

This Code of Conduct applies within all community spaces and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official email address, posting in an official chat room, or acting as an appointed representative at an online or offline event or in other online or offline communities.

Enforcement

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement via Discord or Email. All complaints will be reviewed and investigated promptly and fairly.

All community leaders are obligated to respect the privacy and security of the reporter of any incident.

Enforcement Guidelines

Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:

1. Correction
Community Impact: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.

Consequence: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.

2. Warning
Community Impact: A violation through a single incident or series of actions.

Consequence: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.

3. Temporary Ban
Community Impact: A serious violation of community standards, including sustained inappropriate behavior.

Consequence: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.

4. Permanent Ban
Community Impact: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.

Consequence: A permanent ban from any sort of public interaction within the community.

Attribution

This Code of Conduct is adapted from the Contributor Covenant, version 2.1, available at https://www.contributor-covenant.org/version/2/1/code_of_conduct/.

Community Impact Guidelines were inspired by Mozilla’s code of conduct enforcement ladder.

For answers to common questions about this code of conduct, see the FAQ at https://www.contributor-covenant.org/faq/. Translations are available at https://www.contributor-covenant.org/translations/.