Network rules

Provide accurate account information and keep it current. Your real name is used for private account administration and is not displayed as your public pilot identity.

Each person may operate one pilot account. Shared accounts, transferred accounts, and attempts to avoid an account restriction are not permitted.

Use your assigned Pilot ID, public display name, and a suitable callsign when taking part in network operations. Do not impersonate another member, airline, staff role, or real-world authority.

Treat pilots, staff, and visitors with respect. Harassment, discrimination, threats, targeted disruption, and deliberately inflammatory conduct are not accepted on AVL Network services.

Disagreement is allowed; personal attacks are not. Step away from an exchange and contact Support when a situation cannot be resolved constructively.

Keep operational messages brief, relevant, and understandable. Plain aviation English is preferred where a shared language is needed; reasonable mistakes from pilots of every experience level should be handled patiently.

Before connecting, review the departure, destination, aircraft capability, planned route, cruise level, expected fuel, and relevant simulator conditions. A filed plan must be plausible for the selected aircraft and airports.

Drafts are private working records and are not active flight plans. Review every field before filing. If the intended operation changes materially, update or refile the plan before departure whenever the platform permits.

Load at a suitable stand or parking position, not on an active runway or occupied movement area. Confirm that your simulator, aircraft, internet connection, and AVLpilot are stable before joining.

Remain able to monitor and manage the flight while connected. Extended unattended operation, deliberate obstruction, unrealistic repositioning around other traffic, and repeated connection cycling are not permitted.

Use a supported AVLpilot release and install updates that are designated as required. Do not modify the client, interfere with its connection safeguards, or use unofficial software to submit operational data.

Do not fabricate flights, manipulate time or distance records, automate activity to gain statistics, or exploit a platform defect. If a record is clearly incorrect, report it through Support with the relevant flight reference.

A diversion, rejected takeoff, return to stand, or simulator failure may be recorded when it reflects the flight that occurred. Add a concise factual remark where useful and avoid repeatedly recreating an incident for attention or statistics.

A simulated emergency must remain controlled, credible, and proportionate to the surrounding operation. It never takes priority over real-world safety, platform security, or a staff instruction to stop the scenario.

Staff may issue guidance, a warning, a temporary restriction, or an account suspension when needed to protect the network. Serious abuse, evasion, threats, or deliberate data manipulation may justify immediate restriction.

The response considers severity, impact, available evidence, prior conduct, and whether the member acted constructively after the event.

Submit a concise report through Support with dates, UTC times, Pilot IDs or callsigns, and relevant flight references. Do not conduct public accusations or encourage others to target a reported member.

A member may request a review of a moderation decision through Support. The request should identify the decision and explain any missing context or factual error.