# vAMSYS Documentation > Complete documentation for vAMSYS Virtual Airline Management System > Auto-generated from https://vamsys.co.uk/docs ## Table of Contents - Pilot Data & Marketing: /docs/pilot-data-and-marketing - Import/Export Best Practices: /docs/import-export-best-practices - Using the Imports Page: /docs/imports-page - Using the Exports Page: /docs/exports-page - Getting Started with vAMSYS: /docs/getting-started - New VA Setup Checklist: /docs/new-va-checklist - Contributing to Community Docs: /docs/contributing-to-docs - PFPX AIRAC Validation: /docs/pfpx-airac-validation - Using Regex to Determine Flight Types: /docs/regex-flight-type - Aircraft Import/Export: /docs/aircraft-import-export - Fleet Import/Export: /docs/fleet-import-export - Airport Import/Export: /docs/airport-import-export - Route Import/Export: /docs/route-import-export - Routing Import/Export: /docs/routing-import-export - Load Factor Import/Export: /docs/loadfactor-import-export - Container Import/Export: /docs/container-import-export - Hub Import/Export: /docs/hub-import-export - Badge Import/Export: /docs/badge-import-export - Scenery Import/Export: /docs/scenery-import-export - PFPX Export: /docs/pfpx-export - Fleet: /docs/fleet - Aircraft: /docs/aircraft - Account Management: /docs/account-management - Activity Requirements: /docs/activity-requirements - Airports: /docs/airports - Alerts: /docs/alerts - Badges: /docs/badges - Branding: /docs/branding - Containers: /docs/containers - Holidays: /docs/holidays - How to Apply for a Rank Transfer: /docs/how-to-apply-for-rank-transfer - How to Book Holidays: /docs/how-to-book-holidays - How to Meet Activity Requirements: /docs/how-to-meet-activity-requirements - How to Register with a Virtual Airline: /docs/how-to-register - Hubs: /docs/hubs - Load Factors: /docs/load-factors - NOTAMs: /docs/notams - Pilot Registration: /docs/pilot-registration - Pilot Sharing Agreements: /docs/pilot-sharing-agreements - Presets: /docs/presets - Rank Transfer: /docs/rank-transfer - Ranks: /docs/ranks - Scenery: /docs/scenery - Staff: /docs/staff - Phoenix Dashboard Editor: /docs/phoenix-dashboard-editor - Bookings: /docs/bookings - Liveries: /docs/liveries - PIREPs: /docs/pireps - Scoring Groups: /docs/scoring-groups - Scoring Rules: /docs/scoring-rules - AutoReject Rules: /docs/autoreject-rules - Custom Pages: /docs/custom-pages - Activities: /docs/activities - General Settings: /docs/general-settings - Booking & Dispatch Settings: /docs/booking-and-dispatch-settings - PIREP & Reward Settings: /docs/pirep-and-reward-settings - Callsign Parameters: /docs/callsign-parameters - ACARS Sounds: /docs/acars-sounds - Statistics: /docs/statistics - Billing: /docs/billing - Discord Integration: /docs/discord-integration - How to Book a Flight: /docs/how-to-book-a-flight - PIREPs & Claims: /docs/pireps-and-claims - How to Join Activities: /docs/how-to-join-activities - Your Pilot Profile: /docs/your-pilot-profile - How to Update Your Settings: /docs/how-to-update-your-settings - Leaderboards & Badges: /docs/leaderboards-and-badges - Navigating Phoenix: /docs/navigating-phoenix - Resources & Documents: /docs/resources-and-documents - Alerts, NOTAMs & Notifications: /docs/alerts-notams-and-notifications - My Rosters & Personal Rosters: /docs/my-rosters - Pilot Passport: /docs/pilot-passport - API: /docs/api - Pilots: /docs/pilots - Routes: /docs/routes - Routings: /docs/routings --- # Pilot Data & Marketing Manage marketing opt-ins and export subscriber data for email campaigns. The Marketing system lets pilots opt in to receive communications from your Virtual Airline. Opted-in subscribers can be exported for email campaigns, with built-in unsubscribe handling. **Airline Owners Only**: Access to marketing data is restricted to airline owners. The feature must also be enabled for your airline in settings. ## How Pilots Subscribe Pilots can opt in through several methods, all tracked in the system: - During registration - Checkbox on the signup form - Profile settings - Toggle in Phoenix under Profile → Settings - Dashboard prompt - Alert shown to pilots who have not opted in (can be dismissed) The toggle in Phoenix shows: "Allow [Airline Name] to contact you with news, events, and promotions. Your first name, last name, and email will be shared with the Virtual Airline for direct marketing purposes." ## Viewing Subscribers In Orwell, go to Pilots → Marketing. The stats overview shows: - Total subscribers - New subscribers (last 30 days) - Unsubscribes (last 30 days) - Net change - Breakdown by subscription method (registration vs profile) The table lists all opted-in pilots with their ID, name, email, subscription date, and how they subscribed. ## Exporting Subscribers Click Export Subscribers to download a CSV containing: - First name - Last name - Email address - Unique unsubscribe link The unsubscribe link is unique per pilot and does not require login. When clicked, vAMSYS immediately revokes their marketing consent. ## Unsubscribing Pilots Pilots can unsubscribe through: - Email link - The unsubscribe URL in your marketing emails - Profile settings - In Phoenix, pilots go to Profile → Settings and turn off the Marketing Communications toggle - Staff action - Use the Unsubscribe button on the Marketing page (individual or bulk) ## Usage Guidelines Click Usage Guidelines on the Marketing page for a quick reference. Key points: - Fresh export each time - Generate a new export before each campaign to respect recent unsubscribes - Individual emails only - Send one email per recipient with their unique unsubscribe link. Never use CC or BCC. - Include unsubscribe link - Every marketing email must contain the unsubscribe URL from the export - Delete after use - Do not store exports long-term ## Privacy Law Compliance GDPR (General Data Protection Regulation) is European law that governs how personal data can be collected and used. It applies to anyone handling data of EU residents, regardless of where you are located. Similar laws exist in other regions: - UK GDPR - Nearly identical to EU GDPR, enforced by the ICO - Canada (PIPEDA) - Requires consent for commercial electronic messages - Australia (Privacy Act) - Requires consent or easy opt-out for direct marketing - California (CCPA/CPRA) - Requires transparency and opt-out rights GDPR is the most comprehensive standard. The consent mechanism in vAMSYS satisfies all these laws. If you follow GDPR best practices, you are generally compliant with other privacy regulations. ### Your Role as Data Controller When you export and use pilot data, you become a Data Controller under GDPR. This means: - You decide why and how pilot data is used - You are legally responsible for your use of that data - vAMSYS does not assume responsibility for misuse of pilot data by VAs If pilot data is misused, liability rests with your Virtual Airline, not vAMSYS. ### What vAMSYS Handles vAMSYS collects explicit consent from pilots on your behalf. The opt-in clearly states their name and email will be shared with your Virtual Airline for marketing. This gives you the lawful basis to send marketing emails to opted-in pilots. ### What You Are Responsible For Consent is only one part of GDPR. Once you export pilot data, you become responsible for your own processing activities. This includes how you store the export, what tools you use to send emails, how long you keep the data, and how you handle data requests. If you only view pilot data within vAMSYS for operational purposes (managing registrations, administering pilots), the vAMSYS Privacy Policy covers that processing. However, you need your own privacy policy if you: - Send marketing or engagement emails - Export or download pilot data - Store pilot data outside of vAMSYS - Use third-party tools or services with pilot data ### Service Emails vs Marketing Emails GDPR treats different types of emails differently. Understanding this distinction is essential. Service emails are strictly necessary to operate the service. vAMSYS handles these. Examples: account verification, password resets, security alerts, system notifications. These do not require marketing consent. Marketing emails promote, encourage, or increase participation. Examples: invitations to fly, event announcements, newsletters, "come back and fly" messages. These require explicit opt-in consent. **Engagement is Marketing**: Calling emails "engagement" does not change their legal classification. If the purpose is to encourage participation, it is marketing and requires consent. ### Prohibited Practices The following violate GDPR and may result in enforcement action against your Virtual Airline: - Scraping email addresses - Copying emails from the pilot list or using scripts to collect addresses - CC/BCC bulk emails - This leaks personal data and prevents individual unsubscribe handling - Reusing old exports - Always generate a fresh export to respect recent unsubscribes - Emailing non-opted-in pilots - If they are not in the export, you have no lawful basis to email them - Disguising marketing as service emails - Do not send promotional content under the guise of operational messages ### Using External Mailing Platforms If you use Mailchimp, SendGrid, or similar services, you assume full responsibility for GDPR compliance. You must provide your own lawful basis, transparency notices, and unsubscribe handling. vAMSYS has no liability for that processing. ### Enforcement vAMSYS actively protects pilot data. Access to pilot email addresses may be restricted if misuse is suspected. Serious or repeated violations may lead to suspension or termination of your Virtual Airline. **Best Practice**: Grant pilot data access only to staff who need it. Send marketing emails sparingly and with clear value. Treat pilot email addresses as confidential data. When in doubt, do not send the email. --- # Import/Export Best Practices Everything you need to know about working with CSV files for bulk data management. Importers and exporters let you bulk manage your VA data using CSV files. This guide covers everything from CSV basics to advanced tips. **Imports Cannot Be Undone**: Mismanaged imports can damage your VA data, and vAMSYS cannot restore it. For one-off changes, use the tools in Orwell instead. ## Before You Start ### Tools You Need You need a way to edit CSV files. Choose one: - Google Sheets (recommended) - Free, handles encoding well, less likely to mangle data - Microsoft Excel - Works, but watch out for data formatting issues (see below) - LibreOffice Calc - Free alternative to Excel For verifying files, any text editor works: Notepad (Windows), TextEdit (Mac), or Notepad++. ### The Golden Rule Always export first, then modify. Exported files show you exactly how your data should be formatted and give you the IDs you need for updates. Create a few sample entries in Orwell, export them, and use that as your template. ## Understanding CSV Files ### What is a CSV? CSV stands for Comma Separated Values. It is a plain text file where each line is a row and commas separate the columns. You can open a CSV in spreadsheet software (which shows it as a grid) or in a text editor (which shows the raw text with commas). ### How to Verify Your File If your import fails, your file might not be a valid CSV. Open it in a text editor (not Excel) and check: - Values should be separated by commas, not tabs - Text containing commas should be wrapped in quotes - No strange characters at the start of the file A valid CSV looks like this: ``` Name,ICAO,Country "London Heathrow",EGLL,United Kingdom "Los Angeles",KLAX,United States ``` If you see tabs between values instead of commas, the file is tab-separated and will not work. ### Saving as CSV - Google Sheets: File > Download > Comma-separated values (.csv) - Excel: File > Save As > Choose "CSV UTF-8 (Comma delimited)" - LibreOffice: File > Save As > Choose "Text CSV (.csv)" **Do Not Rename Files**: Renaming an .xlsx file to .csv does not convert it. You must use Save As or Download to create a real CSV file. ### Excel Pitfalls Excel can change your data without asking: - Leading zeros removed: 007 becomes 7 - Dates reformatted: 2025-01-28 might become 28/01/2025 or 1/28/25 - Large numbers become scientific notation: 12345678901 becomes 1.23E+10 To avoid these issues, use Google Sheets, or import the CSV into Excel with all columns set to "Text" format. ## Data Formats Use these exact formats in your CSV files: Data TypeFormatExampleDateYYYY-MM-DD HH:MM:SS2025-01-28 14:30:00TimeHH:MM14:30BooleanTRUE or FALSEFALSE Dates use 24-hour time. Times are in UTC unless your airline has local times enabled for routes. ## How Imports Work Imports do not replace all your data. Each row tells vAMSYS to create, update, or delete one record based on the ID and _delete columns. Example: You have 200 airports and want to rename 10 of them. Export all airports, delete the 190 rows you do not need to change, edit the 10 you want to rename, then import. Those 10 airports update. The other 190 remain exactly as they were. Importing is not the same as replacing. ### Creating Records Leave the ID column empty. Set _delete to FALSE. ### Updating Records Include the ID from your export. Set _delete to FALSE. **Update Instead of Delete + Create**: Updating a record with its ID preserves history and relationships. Deleting and recreating generates a new ID, which breaks references from other records. Updates are also faster. ### Deleting Records Include the ID from your export. Set _delete to TRUE. Deleted records cannot be recovered. ### Exports Match Imports Exported files are designed to work with the importer. Column names match automatically, so you do not need to map columns manually. ## Import Order Some data types depend on others. Import them in this order: 1. Containers, Load Factors, Hubs (no dependencies) 2. Fleets (no dependencies) 3. Aircraft (requires Fleets) 4. Airports (can reference Containers, Load Factors, Hubs) 5. Routes, Routings, Scenery (requires Airports) Wait for each import to complete before starting the next one. ## Performance Tips ### Only Upload Changes If you have 20,000 routes and need to update 100 of them, only import those 100 rows. Do not upload all 20,000. Imports that change nothing are bad for everyone: your import takes longer, and vAMSYS does work that is not needed. Leaving out unchanged records will not delete them. ### Use End Date for Routes To retire routes, set an End Date instead of using _delete. Deletion slows down your import. End Date expiry happens in the background. ### Test First When trying something new, import a few rows first to verify everything works before importing thousands of records. ## Troubleshooting ### Import Gets Stuck Do not re-upload the same file. The file likely contains errors. Ask for help in the community and share your CSV so others can spot the problem. ### Incompatible Files Only comma-separated CSV files work. PDF, XLS, and XLSX files will fail. ### Third-Party Files Some third-party providers (such as VASchedules) claim to offer vAMSYS-compatible exports. These files do not work with vAMSYS importers. If you purchased a product advertised as vAMSYS-compatible and it does not import correctly, contact the provider for a refund or correction. vAMSYS has no control over what third parties advertise, and our attempts to resolve this have been ignored. Never import files blindly. Always open the file, verify it matches the format vAMSYS expects, and check the data before uploading. Importing incorrect data can damage your VA, and vAMSYS cannot restore it. When in doubt, import a small sample first and verify the results in Orwell. --- # Using the Imports Page How to upload CSV files to bulk-create, update, or delete VA data in Orwell. The Imports page lets you upload CSV files to add, update, or delete data in bulk. It's faster than manual entry for large changes, but requires care—imports cannot be undone and vAMSYS cannot restore damaged data. ## Accessing Imports In Orwell, go to Data → Imports. You need the Can Use Importers permission to access this page. Each importer also requires its own permission (e.g., Import/Export Routes for route imports). Permissions are assigned in Orwell under HQ → Staff. ## Available Importers ImporterPermission RequiredAircraftImport/Export AircraftAirportsImport/Export AirportsBadgesImport/Export BadgesContainersImport/Export ContainersFleetImport/Export FleetHubsImport/Export HubsLoad FactorsImport/Export LoadfactorsRoutesImport/Export RoutesRoutingsImport/Export RoutingsSceneryCan Manage Scenery ## File Requirements Your CSV file must meet these requirements: RequirementLimitFormatCSV (comma-separated) onlyMax file size10 MBFilename length50 characters maxFilename charactersLetters, numbers, hyphens, underscores, dots onlyNo spacesUse hyphens or underscores instead Files in other formats (PDF, XLS, XLSX) will be rejected. Files from third-party tools like VASchedules are not compatible. ## How to Import 1. Select the importer type from the list 2. Click the import button that appears 3. Upload your CSV file 4. Map columns — If your CSV came from an export, columns map automatically. If you used custom column names, map each column to the correct field before proceeding. 5. Submit and wait for the import to complete The import runs in the background. You'll see progress and any errors when it finishes. ## Import Order Some data depends on other data existing first. If importing multiple types, follow this order: 1. Hubs (if using hub assignments) 2. Load Factors (if assigning to airports/routes) 3. Containers (if assigning to airports/routes) 4. Airports 5. Fleet (aircraft types) 6. Aircraft (individual registrations) 7. Routings (flight plan strings) 8. Routes (requires airports and fleet to exist) 9. Badges 10. Scenery (requires airports to exist) Do not run multiple imports simultaneously—wait for each to complete before starting the next. ## Tips - Export first — Download existing data to see the correct format, get IDs for updates, and ensure automatic column mapping - Only include changed rows — Don't upload 10,000 rows when you're only changing 3. Unchanged records are not affected by their absence - Not all columns required — You don't need every column in your file. Include only the columns you're setting or changing (plus required columns like identifiers) - Check the specific importer docs — Each data type has its own required and optional columns ## Related - Import/Export Best Practices - Using the Exports Page --- # Using the Exports Page How to download your VA data as CSV files from Orwell. The Exports page lets you download your VA data as CSV files. Use exports to analyze data externally, prepare files for re-import, or back up your configurations. ## Accessing Exports In Orwell, go to Data → Exports. You need the Can Use Exporters permission to access this page. Each exporter also requires its own permission (same as the corresponding importer). Permissions are assigned in Orwell under HQ → Staff. ## Available Exporters ExporterPermission RequiredAircraftImport/Export AircraftAirportsImport/Export AirportsBadgesImport/Export BadgesContainersImport/Export ContainersFleetImport/Export FleetHubsImport/Export HubsLoad FactorsImport/Export LoadfactorsRoutesImport/Export RoutesRoutes - PFPXImport/Export RoutesRoutingsImport/Export RoutingsRoutings - PFPXImport/Export RoutingsSceneryCan Manage Scenery ## How to Export 1. Select the exporter type from the list 2. Click the export button that appears 3. Configure any available filters (Routes and Routings have filter options) 4. Confirm the export 5. Wait for the export to complete and download Exports run in the background. Once complete, only you can download the file—other staff cannot access exports you initiated. ## Export Filters Route and Routing exports let you filter what data to include. This is useful for large datasets. ### Route Export Filters FilterOptionsRoute StatusAll Routes, Active Routes, Routes Starting in the FutureMissing RoutingsAll Routes, Only Empty Routes (no flight plan), Only Full Routes (has flight plan)Route VisibilityAll Routes, Only Visible Routes, Only Hidden RoutesDeparture AirportsSelect specific departure airportsArrival AirportsSelect specific arrival airportsAirport Filter OperatorAND (routes matching both filters) or OR (routes matching either)Tag FilterRoutes with any selected tag, Routes without any selected tag, or Routes with no tags at allTagsSelect which tags the Tag Filter applies to (hidden when filtering for routes with no tags)Internal RemarksFilter by exact internal remarks textInternal Remarks FilterRoutes with matching internal remarks, or Routes without matching internal remarks (appears once remarks text is entered) ### Routing Export Filters FilterOptionsDeparture AirportsSelect specific departure airportsArrival AirportsSelect specific arrival airportsTag FilterRoutings with any selected tag, Routings without any selected tag, or Routings with no tags at allTagsSelect which tags the Tag Filter applies to (hidden when filtering for routings with no tags) ### PFPX Exports Routes - PFPX and Routings - PFPX have a smaller filter set than their standard counterparts: Routes - PFPX supports Route Status, Missing Routings, airport, and tag (include-only) filters, while Routings - PFPX supports airport filters only. These exports generate TXT files formatted for PFPX import. **PFPX Exports Cannot Be Re-imported**: PFPX export files are for importing into PFPX only. To import routes or routings back into vAMSYS, use the standard CSV exporters and importers. ## Export Format Most exporters generate CSV files with: - Comma separation - Column headers matching the importer format - Automatic column mapping when re-imported ## Tips - Export before importing — Always export existing data first to see the correct format and get IDs for updates - Use filters for large datasets — If you have thousands of routes, filter by airport or tag to get manageable files - One export at a time — Wait for each export to complete before starting another ## Related - Using the Imports Page - Import/Export Best Practices --- # Getting Started with vAMSYS A day-by-day guide to setting up your Virtual Airline — from first login to launch day. Whether you are new to Virtual Airlines or a veteran starting fresh — welcome to vAMSYS. Setting up a Virtual Airline takes time, and that is a good thing. vAMSYS is a powerful platform with many options, so you can configure your airline exactly how you want it. This guide will walk you through the process step by step. Follow the instructions in order, take your time, and do not skip steps. vAMSYS has been helping Virtual Airline owners get started for close to 10 years. We have guided thousands of VAs through this process, so trust it — do not rush. ## Key Concepts You will encounter these terms throughout vAMSYS and this documentation: - Orwell — your administration backend. This is where you configure your airline, manage pilots, and handle day-to-day operations. You will spend most of your setup time here. - Phoenix — the pilot-facing portal. This is what your members see when they log in — dashboards, flight booking, PIREPs, and community features. - Pegasus — the ACARS flight tracker. Pilots download Pegasus to track their flights and submit PIREPs automatically. - Hangar — file storage for your Virtual Airline. Upload documents, images, and other files for your pilots to access. - PIREP — a Pilot Report. The flight log submitted after each flight, recording time, fuel, landing rate, and route. Your scoring rules evaluate PIREPs to determine how many points each flight earns. ## Your VA Identifier Every Virtual Airline gets a unique identifier — for example, VTA3187. You will find it on the Orwell dashboard and in the top-right corner of every Orwell page. You need this identifier every time you contact vAMSYS support or post a question — memorise it or at least remember where to find it. There can be many Virtual Airlines with similar names on vAMSYS, so saying "my VA is called Test Airlines" is not enough to identify your airline. The identifier is what matters. ## Trial Period Your Virtual Airline starts with a 14-day free trial. You can start your subscription after 4 full days have elapsed — this evaluation period gives you time to set up your VA and decide if vAMSYS is right for your needs. During the trial, some functionality is restricted. These limitations do not affect your setup work and are lifted once you subscribe: - Pilot registration — public login and registration pages are disabled. Use Pilot Invites to bring in your team during the trial. - API access — you can read the API documentation, but cannot create tokens to use it. - Pilot Sharing Agreements — unavailable during the trial. - Discord bot — disabled until your subscription is active. **Trial Expiry**: If the trial expires without an active subscription, your Virtual Airline is deleted. Start your subscription before the 14-day trial ends. ## Setup Roadmap We have organised the setup process into six days. You do not need to follow the daily timing literally — work at your own pace — but do follow the order. Each day builds on the previous one. - Day 1 — Settings & Identity: Staff permissions, callsign parameters, general settings, pilot registration, branding, and inviting your team. This is the foundation everything else builds on. - Day 2 — Infrastructure: Airports, hubs, fleet types, and individual aircraft. The building blocks of your route network. - Day 3 — Rewards & Scoring: Ranks, badges, scoring groups, scoring rules, and AutoReject rules. Define what good flying means for your VA. - Day 4 — Routes & Content: Route defaults, routes, routings, booking settings, custom pages, and dashboard design. Build what pilots interact with. - Day 5 — Engagement & Communication: Activities, activity requirements, alerts, NOTAMs, and activity emails. Set up tools to keep your pilots informed and engaged. - Day 6 — Test Flight & Launch: Complete a test flight, verify everything works as expected, and start your subscription to open your VA to the public. When you are ready, head to the New VA Setup Checklist to begin. ## Related - New VA Setup Checklist — step-by-step setup guide - Billing — subscription management --- # New VA Setup Checklist Step-by-step checklist for setting up your Virtual Airline from scratch — work through each day in order. This checklist walks you through setting up your Virtual Airline from scratch. Work through each day in order — each step explains what you are doing and why, with a link to the full documentation if you need more detail. **Work at Your Own Pace**: You do not need to complete everything in one sitting. Take each day at your own pace — the trial lasts 14 days. The daily labels are there to keep things manageable, not to pressure you. ## Day 1 — Settings & Identity Your first visit and getting Orwell configured. ### Your first visit When you first log into your Virtual Airline on vAMSYS, you will land in Phoenix — the pilot portal. A popup will appear asking you to select your starting location: [Image: Select Starting Location popup shown on first visit to Phoenix - Every pilot sees this popup when they first join your VA.] This is the same prompt every pilot will see when they join your Virtual Airline — it asks them to choose a hub and starting airport. We have not set up hubs yet, so do not worry about this for now. Click the Take me to Orwell button to go straight to the management backend where we will do all the setup work. ### Getting to know Orwell Orwell is where all VA management and day-to-day operations take place. The first time you open it, it looks empty — just a dashboard with a few menu items. Before adding airports and aircraft, we need to lay the groundwork: permissions, callsigns, settings, and branding. This is the step most VA owners skip and regret later. Taking the time now saves you trouble down the line. Take note of your VA Identifier shown in the Virtual Airline Information panel on the dashboard (and in the top-right corner). This is your unique identifier — you will need it whenever you contact vAMSYS support. ### 1. Enable your staff permissions Your Orwell navigation menu starts with just a few items — that is by design. As a VA Owner, you always have access to Staff and Billing, but everything else is controlled by permissions. Navigate to HQ → Staff, click on your own entry, and toggle all permissions on. Click Save changes at the bottom, then reload the page. Your navigation menu will expand to reveal all of Orwell. While you are on the Staff page, fill in your title (Owner, Director, CEO — whatever you prefer), optionally upload a staff avatar, and set a staff email if you want it shown publicly on your Team Page. Full guide: Staff ### 2. Set up callsign parameters Back on the Orwell dashboard, you will see a red warning banner. This appears because your callsign parameters are not fully configured yet. Navigate to HQ → Settings → Callsign Parameters and click the edit button on your primary callsign. You need to set the ATC Radio Callsign and Operator — the helper text on the page explains what each field means. If your Virtual Airline operates under multiple callsigns (for example, the way Wizz Air uses both WZZ and WUK), you can add additional callsign parameters here. Full guide: Callsign Parameters ### 3. Configure general settings Go to HQ → Settings → Basic Settings. The most important setting here is Timezone — it determines when statistics roll over, when activity checks happen, and when scheduled events trigger. Set it to your primary timezone, not UTC (unless that is your primary timezone). Also fill in your slogan, website, and pilot support URL. The Pilot Support Email is mandatory — it is used as the reply-to address for all emails vAMSYS sends to your pilots, including the registration and activity emails you will configure later in this guide. Full guide: General Settings **Choose Your Timezone Carefully**: Your timezone controls when statistics reset each day, when activity requirements are checked, and when leaderboard rankings update. Changing it after launch shifts all of these at once — pick the right one now. ### 4. Review vAMSYS modules Navigate to HQ → Settings → vAMSYS Modules. This is where you enable or disable major vAMSYS features. Here is what each one does: - Activities — events, tours, and challenges that give pilots goals to fly towards - NOTAMs — important notices pilots must read and acknowledge before they can fly - Claims System — lets pilots submit manual flight reports when ACARS tracking fails - Route Changelist — shows pilots upcoming and ending routes so they can plan ahead - Marketing — adds an email opt-in banner so pilots can subscribe to your announcements - Leaderboards — ranks pilots by performance (global, per-hub, or per-network) - Badges — achievement awards for milestones like "100 Flights" or "Transatlantic Explorer" - Hangar — a file library where you upload documents and downloads for your pilots You do not need all of them right away. Enable what makes sense for your VA now and add more later — every module can be turned on or off at any time. ### 5. Configure pilot registration Navigate to HQ → Settings → Pilot Registration. The most important setting here is the Login/Register Link Modifier — this creates your unique registration URL (for example, vamsys.io/register/your-modifier). Choose something memorable for your VA. Also decide whether to enable Registration Review. When enabled, new pilot applications require manual approval by your staff before the account is activated. This is useful if you want to vet new members. Full guide: Pilot Registration ### 6. Set up registration emails In HQ → Settings → Registration Emails, configure the email templates that pilots receive when they register. If you do not configure these, no emails will be sent — pilots will still be able to register, but they will not receive a welcome message. If you enabled Registration Review, you will also see templates for the "registration received" and "registration rejected" emails. Take the time to write thoughtful templates — this is your first communication with new pilots. Full guide: Pilot Registration ### 7. Set up branding Navigate to HQ → Settings → Logo Settings to upload your logos. You need four variants: a bright and dark background version for Phoenix, and a bright and dark background version for the VA selection page, Orwell, Pegasus, and emails. All are recommended at 1800 x 400 pixels. Then visit Style Settings to configure your VA colours for light and dark mode. If you have social media accounts, head to Social Icons (also in Settings, under the Design group) to add links that appear on your Phoenix dashboard and community menu. Full guide: Branding ### 8. Invite your team If you are not working solo, now is a good time to invite your team. Since pilot registration is disabled during the trial, use HQ → Pilot Invites to bring them in. Invites are not sent immediately — there is a 20-minute grace period before they are processed, giving you time to revoke an invite if you made a mistake. Invites are executed in the order they were created, so usernames are assigned sequentially (for example, XXX0002, XXX0003, XXX0004). If username order matters to you, create invites one at a time and wait for each to be processed before creating the next. Once they have joined, navigate to HQ → Staff, click New Staff, and assign them appropriate permissions. Be thoughtful about which permissions each staff member needs — not everyone needs access to everything. Full guides: Staff, Pilots **Flight Settings**: You may notice other settings pages under the Flight group — Booking & Dispatch, Reward Settings, PIREP Settings, ACARS Sounds, and SimBrief Integration. Do not worry about these yet — they will make much more sense after you have set up fleets and routes. We cover the essential ones in Days 3 and 4. ACARS Sounds (custom cabin audio for Pegasus flight phases) and SimBrief Integration (OFP format preferences) work well at their defaults and can be explored after launch. ## Day 2 — Infrastructure Airports, fleet, and aircraft — the building blocks of your route network. Today we create the physical infrastructure your pilots will fly between and the equipment they will fly. In vAMSYS, a fleet type is an aircraft model — like Boeing 737-800 or Airbus A320neo. An aircraft is an individual registration within that fleet — like G-ABCD. You create the model first (with capacities, images, and scoring group), then add tail numbers to it. Aircraft inherit their fleet's settings but can override them individually. Order matters here: airports come first because routes connect airports, and fleet types come before individual aircraft. ### 1. Create airports Your pilots need somewhere to fly. Navigate to Operations → Airports → Airports and start adding airports. Each airport requires a Name and an Airport Code (ICAO or IATA, 3–4 characters). For now, focus on getting your core network created — just the name and code is enough to get started. You will notice additional tabs on each airport: Taxi Times (override default taxi durations for scoring), Managers (assign staff who can edit routes from this airport), Alternate Management (configure SimBrief alternate airport search and fixed alternates), and Load Management (override passenger and cargo load factors per airport). These are all optional and can be configured at any time — come back to them once your VA is up and running and you want to fine-tune the pilot experience. Full guide: Airports ### 2. Set up hubs Hubs are the starting locations new pilots choose when they join your VA. Navigate to Operations → Airports → Hubs and create at least one hub. Hubs also group airports into regions and can enable hub-based leaderboards — useful for larger VAs with multiple bases of operation. Full guide: Hubs ### 3. Add scenery recommendations (optional) If you want to recommend simulator scenery add-ons for your airports, you can do that at Operations → Airports → Scenery. This is entirely optional and can be done at any time. Full guide: Scenery ### 4. Create fleet types Navigate to Operations → Fleet → Fleet and create your fleet types. Each one defines passenger and cargo capacities, the SimBrief aircraft type (SimBrief is a free flight planning tool that generates fuel loads and route plans — pilots access it by linking their Navigraph account), and default images. Create all your fleet types now — you will need them before setting up scoring groups and routes. Full guide: Fleet ### 5. Add individual aircraft Each fleet type contains individual aircraft registrations — for example, G-ABCD within your Boeing 737-800 fleet. Navigate to Operations → Fleet → Aircraft to add them. Aircraft inherit most settings from their fleet type but can override things like capacity, images, and SimBrief configuration individually. Full guide: Aircraft ### 6. Configure containers (optional) If your VA operates cargo flights with container-based loading (ULDs), set up container types at Operations → Payload → Containers. Most VAs can skip this step. Full guide: Containers ### 7. Configure load factors (optional) Load factors control how passenger and cargo loads are calculated for flights. You can find them at Operations → Payload → Load Factors. The defaults work well for most VAs — you can fine-tune these later if needed. Full guide: Load Factors **Bulk Import**: If you have many airports, fleet types, or aircraft to add, check the import/export tools — they let you create entries in bulk from spreadsheets instead of adding them one by one. Full guide: Import/Export Best Practices ## Day 3 — Rewards & Scoring How pilots earn ranks, badges, and points. Now that your fleet types exist, we can configure how vAMSYS evaluates and rewards flights. After each flight, pilots submit a PIREP (Pilot Report) — a detailed flight log recording flight time, landing rate, fuel usage, and route flown. Your scoring rules evaluate each PIREP and award points accordingly. This is where you define what "good flying" means for your VA — and it is entirely up to you. Some VAs score strictly, others are relaxed. There is no wrong approach. ### 1. Create ranks Ranks are the progression system for your pilots — think Cadet, First Officer, Captain, and so on. Navigate to HQ → Rewards → Ranks. Two default ranks exist (Cadet and Staff Team) and cannot be deleted. You decide what triggers promotion: flight hours, points, flight count, or a combination. Regular ranks are awarded automatically when thresholds are met. You can also create honorary ranks that staff award manually — useful for recognition or special roles. Full guide: Ranks ### 2. Create badges (optional) Badges reward specific achievements — for example, "100 Flights", "Night Owl", or "Transatlantic Explorer". They can be awarded automatically when pilots hit milestones or manually by staff. Navigate to HQ → Rewards → Badges to create them. This is optional — you can always add badges later. Full guide: Badges ### 3. Set up scoring groups Scoring groups bundle scoring rules together and assign them to fleet types. When a PIREP is processed, vAMSYS looks up the scoring group for that flight's fleet type and applies its rules. Navigate to HQ → Rewards → Scoring Groups to create them. You might have one group for all aircraft, or different groups for different fleet types. Full guide: Scoring Groups ### 4. Configure scoring rules Scoring rules are the individual criteria within a scoring group: landing rate thresholds, engine management checks, fuel efficiency, and dozens more. Each rule awards or deducts points from the PIREP. Navigate to a scoring group and add rules within it. Full guide: Scoring Rules ### 5. Set up AutoReject rules (optional) AutoReject rules automatically flag, reject, or invalidate PIREPs that do not meet certain criteria — for example, a landing rate worse than -500 fpm. Navigate to HQ → Rewards → AutoReject Rules to configure them. We recommend starting with just a few lenient rules and tightening them as you learn what works for your VA. Full guide: AutoReject Rules ### 6. Review reward and PIREP settings Go to HQ → Settings → Reward Settings and HQ → Settings → PIREP Settings (both under the Flight group). Reward Settings controls how flight time is calculated (whether taxi time counts, which route types award hours and points) and airport manager bonuses. PIREP Settings controls the appeals process for rejected PIREPs and what happens when a pilot diverts to the wrong airport. The defaults are sensible for most VAs — review them now and adjust after your first test flight. Full guide: PIREP & Reward Settings **Scoring Is Not Permanent**: You do not need to get scoring perfect right now. You can adjust rules, groups, and AutoReject criteria at any time — changes only affect future PIREPs, not past ones. ## Day 4 — Routes & Content Build your route network and the pages your pilots will see. With infrastructure and scoring in place, it is time to build what pilots actually interact with: routes to fly and pages to read. ### 1. Configure route creation defaults Before creating any routes, go to HQ → Settings → Route Creation Defaults. These settings control how callsigns behave on all routes you create from this point forward — they are not applied to existing routes, so it is important to set them now. You can choose whether route times use local airport timezones or UTC, whether pilots can change their callsign during dispatch, and how callsigns are auto-generated (from the pilot's username, name, aircraft registration, or a custom pattern). Full guide: Routes ### 2. Create routes Routes are the core of your VA's operations — each one defines a departure airport, arrival airport, which fleets can fly it, the callsign to use, and the schedule. Navigate to Operations → Routes → Routes to create them. Start with a handful of routes covering your main network and expand later. You do not need every route on day one. Full guide: Routes ### 3. Add routings (optional) Routings are pre-defined flight plan waypoint strings for airport pairs. If you add routings, all routes between the same two airports share the same waypoint data — making AIRAC updates much easier. Navigate to Operations → Routes → Routings. This is optional and can be added at any time. Full guide: Routings ### 4. Configure booking & dispatch settings Go to HQ → Settings → Booking & Dispatch. The most important setting here is the jumpseat system — it lets pilots change their location to a different airport without flying. You can limit it to airports connected by routes, extend it to hub airports, or allow jumping to any airport in your network. Also configure booking validity (how long a booking lasts before expiring), dispatch table columns, and external flight tracking buttons (FlightAware, Flightradar24). These settings shape how pilots experience flight booking. Full guide: Booking & Dispatch Settings ### 5. Restore the Pegasus ACARS page Your pilots need somewhere to download the Pegasus flight tracker. Navigate to HQ → Pages → Custom Pages and click the three-dot menu next to the New Custom Page button. Select Restore ACARS Page. This creates a pre-built page with Pegasus download links and setup instructions for your pilots. Full guide: Custom Pages ### 6. Build custom pages Still in HQ → Pages → Custom Pages, consider creating an "About Us" page and a "Rules" page. If you create a rules page, go back to HQ → Settings → Pilot Registration and assign it as your Rules Page — this displays the rules during registration so pilots must read and agree to them before joining. The page builder supports text, images, alerts, buttons, and YouTube videos — you have plenty of flexibility. Full guide: Custom Pages ### 7. Design the Phoenix dashboard The dashboard is the first thing pilots see when they log into Phoenix. Navigate to HQ → Pages → Phoenix Dashboard Editor to arrange it. You can add statistics, recent activity, social links, flight maps, and more. This is your chance to make the first impression count. Full guide: Phoenix Dashboard Editor ### 8. Create presets (optional) Presets are reusable text and point macros for PIREP review comments, point adjustments, and registration review responses. If you plan to do manual PIREP reviews, presets save a lot of time. Navigate to HQ → Settings → Presets to create them. Full guide: Presets ## Day 5 — Engagement & Communication Activities, alerts, and keeping your pilots informed. Your VA is nearly ready. Before opening for business, set up the tools you will use to communicate with pilots and keep them engaged. ### 1. Create a launch activity (recommended) Activities are events, tours, rosters, or challenges that give pilots something to fly towards — with bonus points, badges, and progress tracking. A launch-week activity is a great way to build excitement when your VA opens to the public. Navigate to Operations → Activities to create one. Full guide: Activities ### 2. Set up activity requirements (optional) If you want to enforce minimum flying activity — for example, one flight per month — configure it at HQ → Settings → Activity Settings. You might want to hold off on this until your VA has a few active pilots — enforcing activity requirements on an empty VA does not make much sense. If you do enable them, you can also define Airline Holidays at Operations → Airline Holidays — these are airline-wide days off (like Christmas or a seasonal break) when activity requirements are paused for all pilots. Full guide: Activity Requirements ### 3. Write a welcome alert or NOTAM Alerts are short messages displayed to pilots in Phoenix and Pegasus — useful for quick announcements. NOTAMs are longer notices that pilots must read and acknowledge before they can fly — useful for important policy updates. Consider writing a welcome message for your launch. Full guides: Alerts, NOTAMs ### 4. Configure activity emails If you enabled activity requirements, navigate to HQ → Settings → Activity Emails to set up the warning and removal email templates. Like registration emails, if you do not configure these, no emails will be sent to pilots. Full guide: Activity Requirements **Trial Reminder**: Public registration is disabled during the trial — only Pilot Invites work. Once you start your subscription, the public registration page goes live. ## Day 6 — Test Flight & Launch Validate everything, then open your doors. Everything is configured. Before starting your subscription and opening registration, do a full test run to make sure the pilot experience works as you intend. ### 1. Switch to Phoenix Click Phoenix in the Orwell navigation. This is what your pilots will see. Check the dashboard layout, browse your custom pages, and look at the community section. Does everything look right? Does it feel like your VA? ### 2. Book a flight Go to Flight Centre → Book Flight and select one of your routes. Walk through the entire booking flow — departure, arrival, fleet selection, dispatch page. Experience it as a pilot would. Check that the dispatch information, SimBrief integration, and flight details all appear correctly. ### 3. Download Pegasus and fly In Phoenix, open the Pegasus ACARS page (under Resources, if using the default page layout) and download the Pegasus client. Complete your test flight from start to finish. This is the best way to verify that your scoring rules work as expected, SimBrief dispatches correctly, and any ACARS sounds you configured play at the right moments. ### 4. Review the PIREP Back in Orwell, navigate to Flight Centre → PIREPs. Your test flight should appear here. Open it and review the scoring breakdown — check how many points were awarded or deducted, whether any AutoReject rules fired, and whether the flight hours and distance look correct. This is your opportunity to fine-tune scoring before real pilots start flying. Full guide: PIREPs ### 5. Check bookings and liveries Verify that your booking appeared correctly in Flight Centre → Bookings and that any aircraft livery was detected during the flight in Flight Centre → Liveries. Full guides: Bookings, Liveries ### 6. Review pilot onboarding settings Before going live, review the settings that shape a pilot's first experience with your VA: - Registration emails — check that your welcome email and any registration review emails are configured and read well - Registration review — if enabled, incoming applications appear at Pilots → Registrations for manual approval. Make sure you and your staff understand the review flow before launch - Ranks — verify your rank structure, promotion thresholds, and starting rank are correct - Activity requirements — if enabled, confirm the thresholds are reasonable for a new VA - Activity emails — if activity requirements are on, check that warning and removal emails are configured To see the registration flow in action, invite a staff member or friend who does not yet have a vAMSYS account via HQ → Pilot Invites. They will go through the full registration process and can give you real feedback on the experience. **Do Not Create Test Accounts**: Do not register a second account to test the flow yourself — having multiple accounts violates the vAMSYS Terms of Service. Instead, invite someone who does not already have an account. They will experience the exact same registration flow and can report back. ### 7. Start your subscription When you are satisfied that everything works, navigate to HQ → Billing and start your subscription. Starting your subscription ends the trial immediately — make sure you are ready before proceeding. Once active, your registration page goes live and pilots can join your Virtual Airline. Full guide: Billing **Trial Expiry**: If your trial expires without an active subscription, your Virtual Airline is deleted. Make sure to start your subscription before the 14-day trial ends. ## After Launch Your VA is live — congratulations! As your airline grows, there are additional features to explore: - Rank Transfer — let experienced pilots from other VAs skip to a higher starting rank - Pilot Sharing Agreements — share pilots between allied VAs - Holidays — let pilots request time off from activity requirements - ACARS Sounds — custom VA sounds for Pegasus flight phases - Statistics — VA-wide analytics dashboard - Import/Export Best Practices — bulk data management as your VA grows - Discord Integration — connect your Discord server for automatic alerts, NOTAM posts, badge awards, and PIREP notifications - Webhooks & API — integrate vAMSYS with external tools or your own website ## Related - Getting Started with vAMSYS — overview and trial information - Billing — subscription management --- # Contributing to Community Docs Share your knowledge with the vAMSYS community by contributing guides, tips, and best practices. The Community section features guides and best practices contributed by Virtual Airline staff and pilots. If you've discovered a useful technique, built a helpful workflow, or solved a tricky problem, we'd love to share it with others. ## What Makes a Good Contribution The best community articles are practical and specific. They solve real problems that other Virtual Airlines face. - Workflow guides - How you use spreadsheets, scripts, or external tools alongside vAMSYS - Configuration tips - Creative ways to set up ranks, awards, or scoring systems - Data techniques - Using regex, formulas, or imports to manage your airline - Integration examples - Connecting vAMSYS with Discord bots, websites, or other tools ## How to Submit Send your guide through our helpdesk, available in Orwell under vAMSYS Support. Our team reviews submissions and works with you to polish the content before publishing. Write in any format you're comfortable with - a Word document, Google Doc, or even bullet points. We'll handle the formatting. ## Recognition All community contributions are credited to their authors. Your name and Virtual Airline appear at the top of the article, helping others in the community discover your work. --- # PFPX AIRAC Validation Validate your vAMSYS routes against the current AIRAC cycle using PFPX software. **Community Contribution**: This guide was contributed by Jan Podlipský (TVS32) from Smartwings Virtual. ## Prerequisites - Own a copy of PFPX (Download edition is enough, no server subscription needed) - Have the latest AIRAC installed in PFPX (via Navigraph) - For European routes, install the RAD (Route Availability Document) for your AIRAC cycle ## Export Routes from vAMSYS Currently there is no official vAMSYS exporter for PFPX, so you need to convert the routes CSV into a compatible format manually. The PFPX format is: DEP_ICAO""DEST_ICAO";"DEP_ICAO" "ROUTE" "DEST_ICAO" For example: LKPRLIEE;LKPR VOZ DCT PISAM DCT TAGAS DCT RADLY DCT NIKOL DCT APSUX DCT DEXUL Q125 KOVAS LIEE Use this Google Sheets/Excel formula on your vAMSYS Routes CSV: ``` =C2&E2&";"&C2&" "&K2&" "&E2 ``` Paste the entire column of generated routes into a TXT file. ## Import into PFPX 1. Open PFPX and click the globe icon 2. Navigate to Route Data → Route Database [Image: PFPX globe menu showing Route Data and Route Database navigation - Navigate to Route Data → Route Database] 1. Click Import and select your saved TXT file [Image: PFPX Route Database showing the Import button location - Click the Import button] 1. PFPX will import the routes and highlight any invalid ones [Image: PFPX showing import progress with routes being validated - PFPX validates routes during import] 1. After import completes, filter to show only Invalid routes [Image: PFPX filter dropdown showing Invalid routes option selected - Filter to show only invalid routes] ## Clean Up Valid Routes Since we only care about invalid routes, remove the valid ones: 1. Set filter to "Valid" 2. Select all valid routes and delete them 3. Switch filter to "All" to see only invalid routes remaining [Image: PFPX showing valid routes selected for deletion - Select and delete valid routes to keep only invalid ones] ## Fix Invalid Routes You can regenerate routes directly in PFPX: 1. Double-click on an invalid route [Image: PFPX route editor showing an invalid route ready for rebuilding - Double-click to open the route editor] 1. Click "Build" to generate a new valid route 2. Click "Apply" to update the route 3. Export the finished routes from Route Database to get them in text format for updating vAMSYS [Image: PFPX showing a rebuilt valid route with Build and Apply buttons - Build and Apply to create the new valid route] **Tip**: You can also note down the invalid routes and generate new ones using SimBrief or other flight planning tools before updating them in vAMSYS. --- # Using Regex to Determine Flight Types Learn how to use Regular Expressions to automatically categorize flights based on callsign patterns. **Community Contribution**: This guide was contributed by Jan Podlipský (TVS32) from Smartwings Virtual. Many Virtual Airlines use logical callsign systems where you can determine the flight type (Scheduled, Charter, Repositioning, Training) based on the callsign pattern. This guide shows how to use Regular Expressions to automate this categorization. ## Regular Expression Basics Regular Expressions (regex) are patterns used to match character combinations in strings. You define character types and quantities. Let's analyze the callsign TVS3BD (a Smartwings scheduled flight using ARCID format): The pattern is: Letter-Letter-Letter-Number-Letter-Letter As a regex: [A-Z]{3}\d{1}[A-Z]{2} ### Breaking It Down - [A-Z]{3} = 3 letters from A to Z = "TVS" - \d{1} = 1 digit (0-9) = "3" - [A-Z]{2} = 2 letters from A to Z = "BD" ## Matching Multiple Patterns What about TVS56H? This looks like a different pattern (3 letters, 2 numbers, 1 letter), but you can match both with one regex using ranges: ``` [A-Z]{3}\d{1,2}[A-Z]{1,2} ``` - \d{1,2} = 1 or 2 digits - [A-Z]{1,2} = 1 or 2 letters ## Practical Flight Type Patterns Ferry/Positioning flights (e.g., TVS240P, TVS240F): ``` [A-Z]{3}\d{3}[FP]{1} ``` Note: [FP] matches only F or P (specific letters in brackets). Charter flights (e.g., TVS2240 - 4 digits): ``` [A-Z]{3}\d{4} ``` ## Using Regex in Google Sheets Google Sheets can use regex in conditional formulas. Basic syntax: ``` =IF(REGEXMATCH(A1;"[A-Z]{3}\d{4}");"Charter Flight") ``` **Regional Settings**: The parameter separator depends on your regional settings - it may be a semicolon (;) or comma (,). For multiple conditions, use IFS instead of IF: ``` =IFS(REGEXMATCH(F2;"[A-Z]{3}[0-9]{3}[FP]");"Repositioning";REGEXMATCH(F2;"[A-Z]{3}[0-9]{4}");"Charter";REGEXMATCH(F2;"[A-Z]{3}\d{1,2}[A-Z]{1,2}");"Scheduled";TRUE;"") ``` **Order Matters**: With IFS, the first matching condition wins. Place more specific patterns before general ones. Add TRUE;"" at the end to leave unmatched cells blank instead of showing an error. ## Deriving Other Fields Once you have a Tag column with flight types, derive other import fields: Type field: ``` =IFS(T2="Scheduled Flight";"scheduled";OR(T2="Charter Flight";T2="Business Jet Flight");"charter";T2="Repositioning Flight";"repositioning";TRUE;"") ``` Flighttype field: ``` =IFS(T2="Scheduled Flight";"s";OR(T2="Charter Flight";T2="Repositioning Flight");"n";TRUE;"") ``` --- # Aircraft Import/Export Import and export individual aircraft with registrations, SimBrief overrides, and capacity settings. The Aircraft importer and exporter let you bulk manage individual aircraft in your fleet. Each aircraft belongs to a Fleet (aircraft type) and can have its own registration, capacity overrides, and SimBrief settings. **Import Fleets First**: Aircraft require Fleet IDs. Import your Fleets before importing Aircraft so you have the Fleet IDs to reference. ## Accessing Import/Export In Orwell, go to Data → Exports to download your aircraft as CSV, or Data → Imports to upload changes. ## Column Reference ### Core Columns ColumnRequiredDescriptionIDFor updatesvAMSYS record ID. Leave empty when creating new aircraft. Include when updating or deleting.NameYesDisplay name for the aircraft (e.g., "Boeing 737-8AS(WL)")RegistrationYesAircraft registration (e.g., "9H-QEU")Fleet IDYesID of the Fleet (aircraft type) this aircraft belongs to. Get this from a Fleet export.SELCALNoSELCAL code (e.g., "AB-CD")Fin NumberNoAircraft fin/tail numberHex CodeNoMode S transponder hex codePassengersNoPassenger capacity override. Only applies to passenger fleet types.FreightNoCargo capacity override. Only applies to cargo-capable fleet types.Container UnitsNoContainer unit capacity override. Only applies to container-capable fleet types.Internal RemarksNoInternal notes (staff only, not visible to pilots)_deleteYesSet to TRUE to delete, FALSE otherwise ### SimBrief Override Columns These columns let you override SimBrief settings at the aircraft level. Leave empty to use Fleet defaults. ColumnDescriptionSB OFP LayoutOFP layout code (e.g., "RYR", "BAW")SB Perf CodePerformance code: A, B, C, D, or ESB Weight CatWake turbulence category: L, M, H, or JSB ETOPS ThresholdETOPS threshold: 60, 75, 90, 120, or 180 minutesSB ETOPS CertETOPS certification: 75-370 minutesSB ICAO EquipICAO equipment codes (e.g., "SDE3FGHIRWY")SB ICAO TransponderICAO transponder code (e.g., "LB1")SB PBN CapabilityPBN capability (e.g., "PBN/A1B1C1D1")SB Extra FPL InfoAdditional flight plan remarks (e.g., "DAT/V RVR/250")SB Engine TypeEngine type codeSB Pax WeightPassenger weight in kgSB Bag WeightBag weight in kgSB OEWOperating empty weight (tonnes)SB MZFWMax zero fuel weight (tonnes)SB MTOWMax takeoff weight (tonnes)SB MLWMax landing weight (tonnes)SB Max Fuel CapMaximum fuel capacity (tonnes) **Fuel Columns**: Additional fuel columns (SB Contingency Fuel, SB Reserve Fuel, SB Block Fuel, SB Arrival Fuel, SB MEL Fuel, SB ATC Fuel, SB WXX Fuel, SB Extra Fuel, SB Tankering Fuel) are available with corresponding unit columns (wgt for kg, min for minutes). ## Creating New Aircraft 1. Export your current Fleets to get Fleet IDs 2. Leave the ID column empty 3. Fill in required columns: Name, Registration, Fleet ID 4. Set _delete to FALSE ## Updating Aircraft 1. Export existing aircraft 2. Modify the columns you need to change 3. Keep the ID column intact 4. Ensure _delete is FALSE ## Deleting Aircraft 1. Export existing aircraft 2. Keep only the rows you want to delete 3. Ensure the ID column has the correct value 4. Set _delete to TRUE **Capacity Based on Fleet Type**: Capacity fields are automatically adjusted based on the Fleet type. For cargo fleets, passenger capacity is ignored. For passenger-only fleets, cargo capacity is ignored. For non-container fleets, container units are ignored. --- # Fleet Import/Export Import and export aircraft types (fleets) with SimBrief configurations and PIREP scoring settings. The Fleet importer and exporter let you bulk manage aircraft types. Each fleet defines the base configuration for a type of aircraft, including capacity, SimBrief settings, and PIREP scoring rules. Individual aircraft belong to fleets. **Import Before Aircraft**: Fleets must exist before you import Aircraft. Aircraft reference Fleet IDs, so import your Fleets first. ## Accessing Import/Export In Orwell, go to Data → Exports to download your fleets as CSV, or Data → Imports to upload changes. ## Column Reference ### Core Columns ColumnRequiredDescriptionIDFor updatesvAMSYS record ID. Leave empty when creating new fleets. Include when updating or deleting.NameYesFleet display name (e.g., "Boeing 737-800")Type CodeYesICAO aircraft type code (e.g., "B738")Type (pax/cargo/...)YesFleet type: pax, pax-cargo, pax-containers, cargo, or cargo-containersMax PassengersConditionalMaximum passenger capacity. Required for passenger fleet types.Max FreightConditionalMaximum cargo capacity. Required for cargo-capable fleet types.Container UnitsConditionalContainer unit capacity. Required for container fleet types.Hide in PhoenixNoSet TRUE to hide this fleet from pilots in PhoenixPIREP Scoring Group IDNoID of the scoring group for PIREP evaluationAllowed Prefix IDsNoComma-separated Parameter IDs this fleet can use_deleteYesSet to TRUE to delete, FALSE otherwise ### Fleet Types TypeDescriptionCapacity FieldspaxPassenger onlyMax Passengerspax-cargoPassengers with belly cargoMax Passengers, Max Freightpax-containersPassengers with container cargoMax Passengers, Container UnitscargoCargo freighter (bulk)Max Freightcargo-containersCargo freighter (containerized)Container Units ### SimBrief Override Columns Fleet-level SimBrief settings serve as defaults for all aircraft in this fleet. Individual aircraft can override these settings. **SimBrief Columns**: The same SimBrief columns from Aircraft Import/Export are available here: SB OFP Layout, SB Perf Code, SB Weight Cat, SB ETOPS settings, SB ICAO equipment codes, weight and fuel settings, and performance profiles. Fleet also includes alternate search settings (SB Altn Radius, SB Altn Min Ceiling, SB Altn Min Rwy Length, SB Altn Avoid Bad Wx). ## Creating New Fleets 1. Leave the ID column empty 2. Fill in required columns: Name, Type Code, Type 3. Fill appropriate capacity fields based on Type 4. Set _delete to FALSE ## Updating Fleets 1. Export existing fleets 2. Modify the columns you need to change 3. Keep the ID column intact 4. Ensure _delete is FALSE ## Deleting Fleets 1. Export the fleets you want to delete 2. Set _delete to TRUE for those rows 3. Import the file **Aircraft Impact**: Deleting a fleet will affect all aircraft that belong to it. Reassign aircraft to a different fleet before deleting if you want to keep them. --- # Airport Import/Export Import and export airports with load factor assignments, container availability, and SimBrief alternate settings. The Airport importer and exporter let you bulk manage the airports your airline operates from. You can configure taxi times, mark hubs, assign load factors and containers, and set SimBrief alternate search preferences. **Import Dependencies First**: Create Load Factors and Containers before importing airports that reference them. The importer validates that all referenced IDs exist. ## Accessing Import/Export In Orwell, go to Data → Exports to download your airports as CSV, or Data → Imports to upload changes. ## Column Reference ### Core Columns ColumnRequiredDescriptionICAO/IATAYesAirport identifier (ICAO 4-character or IATA 3-character code). Used to match records for updates.NameYesDisplay name for the airport in your airlineCategoryNoCustom category for organizing airportsBaseNoTRUE if this is a base/hub airportSuitable AlternateNoTRUE if this airport can be used as an alternateAirport Briefing URLNoLink to external airport briefing or chartsTaxi In MinutesNoDefault taxi time from runway to gateTaxi Out MinutesNoDefault taxi time from gate to runwayPreferred AlternatesNoComma-separated list of preferred alternate ICAO codes_deleteYesSet to TRUE to delete, FALSE otherwise ### Load Factor Columns Assign load factors to control passenger and cargo load calculations for flights at this airport. Load factors must be created first via Data → Load Factors. ColumnDescriptionPassenger LF IDLoad factor ID for passenger count calculationLuggage LF IDLoad factor ID for passenger luggage weightCargo (Weight) LF IDLoad factor ID for cargo weight calculationCargo (Volume) LF IDLoad factor ID for cargo volume calculation ### Container Column ColumnDescriptionContainer IDsComma-separated container IDs available at this airport ### SimBrief Alternate Settings Configure how SimBrief searches for alternates when this airport is the destination. ColumnDescriptionSB Alt RadiusSearch radius in nautical miles for alternate airportsSB Alt Min CeilingMinimum ceiling height in feet for alternate selectionSB Alt Min Rwy LengthMinimum runway length in feet for alternate selectionSB Alt Avoid Bad WeatherTRUE to exclude alternates with thunderstorms, freezing conditionsSB Alt Exclude AirportsICAO codes to exclude from alternate search (space or comma-separated)SB Takeoff Altn ICAO/IATASpecified takeoff alternate airportSB Altn 1-4 ICAO/IATAUp to 4 specific destination alternates (columns 1 through 4) ### Info Columns (Export Only) These columns appear in exports for reference but are ignored during import. - Info-Airport ID - Internal vAMSYS record ID - Info-Airport ICAO - World airport ICAO code - Info-Airport IATA - World airport IATA code - Info-Created, Info-Updated - Timestamps ## Adding Airports 1. Enter the ICAO or IATA code in the ICAO/IATA column (must exist in world airports) 2. Fill in the required Name column 3. Add optional settings (taxi times, load factors, etc.) 4. Set _delete to FALSE ## Updating Airports 1. Export existing airports 2. Modify the columns you need to change 3. Keep the ICAO/IATA column intact (this identifies the record) 4. Ensure _delete is FALSE **Airport Identification**: Unlike Aircraft and Fleet which use internal IDs, Airports are identified by their ICAO/IATA code. The same code in a new import updates the existing airport rather than creating a duplicate. ## Deleting Airports 1. Export the airports you want to delete 2. Set _delete to TRUE for those rows 3. Import the file --- # Route Import/Export Import and export flight routes with schedules, times, SimBrief settings, and fleet assignments. The Route importer and exporter let you bulk manage flight routes. Routes define the flights your pilots can book, including departure/arrival airports, schedule times, fleet assignments, and SimBrief configuration. **Import Dependencies First**: Create Airports, Fleets, Load Factors, and Containers before importing routes. Routes validate that all referenced IDs exist and that fleets are allowed for the assigned parameters. ## Accessing Import/Export In Orwell, go to Data → Exports to download your routes as CSV, or Data → Imports to upload changes. ## Export Filters When exporting routes, you can filter the data to include only what you need. This is especially useful for airlines with thousands of routes. FilterOptionsRoute StatusAll Routes, Active Routes, Routes Starting in the FutureMissing RoutingsAll Routes, Only Empty Routes (no flight plan), Only Full Routes (has flight plan)Departure AirportsSelect specific departure airportsArrival AirportsSelect specific arrival airportsAirport Filter OperatorAND (routes matching both filters) or OR (routes matching either). Only appears when both departure and arrival airports are selected.TagsFilter by route tagsInternal RemarksFilter by exact internal remarks text ## Column Reference ### Core Columns ColumnRequiredDescriptionIDFor updatesvAMSYS record ID. Leave empty when creating new routes. Include when updating or deleting.Departure Airport (ICAO/IATA)YesDeparture airport code or ID. Must exist in your airline.Arrival Airport (ICAO/IATA)YesArrival airport code or ID. Must exist in your airline.TypeYesRoute type: scheduled, cargo, charter, training, vfr, repositioning, or jumpseatCallsignConditionalRadio callsign (4-7 characters). Required for all types except jumpseat.Flight NumberConditionalFlight number (3-6 characters). Required for all types except jumpseat.Fleet IDsConditionalComma-separated Fleet IDs. Required for all types except jumpseat._deleteYesSet to TRUE to delete, FALSE otherwise ### Schedule Columns ColumnDescriptionStart DateRoute becomes available (YYYY-MM-DD HH:MM:SS)End DateRoute expires (YYYY-MM-DD HH:MM:SS)Departure Time (HH:MM)Scheduled departure timeArrival Time (HH:MM)Scheduled arrival timeService DaysComma-separated weekdays: monday, tuesday, wednesday, thursday, friday, saturday, sunday **Timezone Handling**: If your airline uses local times for routes, departure and arrival times are automatically converted between local airport timezone and UTC during import/export. ### Flight Details ColumnDescriptionAltitudeCruise altitude (e.g., FL350, 35000)Cost IndexCost index value (AUTO or 0-9999)Flight Length (HH:MM)Flight duration. Auto-calculated if empty.Flight Distance (NM)Distance in nautical miles. Auto-calculated if empty.RoutingFlight plan route stringRemarksVisible remarks for pilotsInternal RemarksStaff-only notesTagsComma-separated tags for categorizationIs HiddenTRUE to hide from pilots ### Callsign Options ColumnDescriptionAllow Callsign ChangeTRUE to let pilots modify the callsignCS Defaults Username Opt1TRUE to use username option 1 as defaultCS Defaults Username Opt2TRUE to use username option 2 as defaultCS Defaults Aircraft RegTRUE to use aircraft registration as defaultCallsign Generator StrCustom callsign generator pattern. Validated on import — every element must be in brackets (e.g. [0-9][0-9][A-Z]); rows with invalid patterns are rejected ### Load Factor and Container Columns ColumnDescriptionPax LF IDPassenger load factor IDPax Luggage LF IDPassenger luggage load factor IDCargo LF IDCargo weight load factor IDCargo Volume LF IDCargo volume load factor IDContainer IDsComma-separated container IDs available on this route ### SimBrief Columns Route-level SimBrief settings for flight planning. ColumnDescriptionFlight Rulesi=IFR, v=VFR, y=IFR/VFR, z=VFR/IFRFlight Types=Scheduled, n=Non-scheduled, g=General aviation, m=Military, x=OtherSB Pax WgtPassenger weight override (kg)SB Bag WgtBag weight override (kg)SB Contingency FuelContingency fuel policySB Reserve FuelReserve fuel policy **Additional SimBrief Fuel Columns**: Additional fuel columns available: SB MEL Fuel, SB ATC Fuel, SB WXX Fuel, SB Extra Fuel, SB Tankering Fuel, SB Min FOB, SB Min FOD. Each has a corresponding units column (mins, kg, or lbs). Alternate airports: SB Enroute Altn, SB Takeoff Altn, SB Altn 1-4. ## Route Types TypeDescriptionRequirementsscheduledRegular passenger flightsCallsign, Flight Number, Fleet IDscargoCargo-only flightsCallsign, Flight Number, Fleet IDscharterCharter flightsCallsign, Flight Number, Fleet IDstrainingTraining flightsCallsign, Flight Number, Fleet IDsvfrVFR flightsCallsign, Flight Number, Fleet IDsrepositioningFerry/repositioning flightsCallsign, Flight Number, Fleet IDsjumpseatPilot repositioning (no aircraft)None (no callsign, flight number, or fleet) ## Creating Routes 1. Leave the ID column empty 2. Fill in required columns: Departure/Arrival airports, Type 3. Add Callsign, Flight Number, and Fleet IDs (unless jumpseat) 4. Set _delete to FALSE ## Updating Routes 1. Export existing routes 2. Modify the columns you need to change 3. Keep the ID column intact 4. Ensure _delete is FALSE ## Ending Routes Setting _delete to TRUE and letting a route naturally expire via End Date achieve the same result. Using End Date lets vAMSYS handle expiry automatically without needing an import. 1. Export existing routes 2. Set End Date to a date in the past (e.g., yesterday) 3. Keep the ID column intact 4. Ensure _delete is FALSE **Prefer Ending Over Deleting**: If you know when a route should end, set the End Date when creating it. For routes you need to end now, setting an End Date in the past is still faster than using _delete. Deletion slows down your import, while End Date expiry happens in the background. --- # Routing Import/Export Import and export pre-defined flight plan route strings. The Routing importer and exporter let you bulk manage pre-defined flight plan route strings. Route strings are cleaned during import, removing unrecognized waypoints or airways. **Import Airports First**: Both departure and arrival airports must exist in your airline before importing routings. You cannot change airports after a routing is created. ## Routing vs Route Routing stores the flight plan route string between two airports (e.g., "DCT KONAN UN866 DVR UL9 KONAN"). Route defines a complete scheduled flight including callsign, times, and fleet assignments. A Route can reference a Routing for its flight plan. ## Accessing Import/Export In Orwell, go to Data → Exports to download your routings as CSV, or Data → Imports to upload changes. ## Export Filters When exporting routings, you can filter the data to include only what you need. FilterOptionsDeparture AirportsSelect specific departure airportsArrival AirportsSelect specific arrival airportsTagsFilter by routing tags ## Column Reference ColumnRequiredDescriptionIDFor updatesvAMSYS record ID. Leave empty when creating new routings. Include when updating or deleting.Departure Airport (ICAO/IATA)YesDeparture airport code. Must exist in your airline.Arrival Airport (ICAO/IATA)YesArrival airport code. Must exist in your airline.Route StringYesThe flight plan route string. Cleaned during import to remove unrecognized elements.RemarksNoVisible remarksInternal RemarksNoStaff-only notesTagsNoComma-separated tags for categorizationDays of OperationNoComma-separated weekdays: monday, tuesday, wednesday, thursday, friday, saturday, sunday_deleteYesSet to TRUE to delete, FALSE otherwise ### Info Columns (Export Only) These columns appear in exports for reference but are ignored during import. - AIRAC Cycle - The AIRAC cycle the routing was validated against - Created At - Creation timestamp ## Route Processing Route strings are processed during import to clean formatting and remove unrecognized waypoints or airways. Successfully imported routings are tagged with the current AIRAC cycle. **Cannot Change Airports**: Once a routing is created, you cannot change its departure or arrival airports. To use a different airport pair, create a new routing and delete the old one. ## Creating Routings 1. Leave the ID column empty 2. Fill in required columns: Departure Airport, Arrival Airport, Route String 3. Set _delete to FALSE ## Updating Routings 1. Export existing routings 2. Modify the columns you need to change (except airports) 3. Keep the ID column intact 4. Ensure _delete is FALSE ## Deleting Routings 1. Export the routings you want to delete 2. Set _delete to TRUE for those rows 3. Import the file --- # Load Factor Import/Export Import and export load factors for passenger and cargo load calculations. The Load Factor importer and exporter let you bulk manage load factors. Load factors control how passenger and cargo loads are calculated for flights, using statistical distributions to create realistic variation. **Import Before Airports/Routes**: Load Factors can be assigned to Airports and Routes. Create your Load Factors before importing Airports or Routes that reference them. ## Accessing Import/Export In Orwell, go to Data → Exports to download your load factors as CSV, or Data → Imports to upload changes. ## Column Reference ColumnRequiredDescriptionIDFor updatesvAMSYS record ID. Leave empty when creating. Include when updating or deleting.TypeYesLoad factor type: pax, pax-luggage, cargo, or cargo-volumeNameYesDisplay name. Must be unique per type within your airline.Min %YesMinimum load percentage (0-100). Must be less than Max.Max %YesMaximum load percentage (1-100). Must be greater than Min.Average %NoTarget average percentage (1-100)BiasNoDistribution skew factor (0.0-1.0)Deviation (SD)YesStandard deviation for load variation (0-100)Is DefaultNoTRUE to use as default for this type. Only one default per type._deleteYesSet to TRUE to delete, FALSE otherwise ## Load Factor Types TypeDescriptionpaxPassenger count calculationpax-luggagePassenger luggage weight calculationcargoCargo weight calculationcargo-volumeCargo volume calculation **Default Handling**: When you set a load factor as default, all other load factors of the same type are automatically set to non-default. Only one load factor per type can be the default. ## Creating Load Factors 1. Leave the ID column empty 2. Fill in required columns: Type, Name, Min %, Max %, Deviation (SD) 3. Set _delete to FALSE ## Updating Load Factors 1. Export existing load factors 2. Modify the columns you need to change 3. Keep the ID column intact 4. Ensure _delete is FALSE ## Deleting Load Factors 1. Export the load factors you want to delete 2. Set _delete to TRUE for those rows 3. Import the file **Check References First**: Before deleting a load factor, ensure no airports or routes are using it. Reassign them to a different load factor first. --- # Container Import/Export Import and export cargo containers with incompatibility relationships. The Container importer and exporter let you bulk manage cargo containers. Containers define the unit load devices (ULDs) available in your airline, including their capacity and which containers cannot be loaded together. **Import Before Airports/Routes**: Containers can be assigned to Airports and Routes. Create your Containers before importing Airports or Routes that reference them. ## Accessing Import/Export In Orwell, go to Data → Exports to download your containers as CSV, or Data → Imports to upload changes. ## Column Reference ColumnRequiredDescriptionIDFor updatesvAMSYS record ID. Leave empty when creating. Include when updating or deleting.NameYesContainer display name (e.g., "LD3 Container")TypeYesContainer type identifierUnit SizeYesHow many unit positions this container occupies (1-9999)Weight (kg)YesContainer maximum weight capacity in kilogramsNotesNoOptional notes about the containerIncompatible Container IDsNoComma-separated container IDs that cannot be loaded with this container_deleteYesSet to TRUE to delete, FALSE otherwise **Incompatibility is Bidirectional**: When you mark Container A as incompatible with Container B, the system automatically marks Container B as incompatible with Container A. You only need to specify the relationship once. ## Creating Containers 1. Leave the ID column empty 2. Fill in required columns: Name, Type, Unit Size, Weight (kg) 3. Set _delete to FALSE ## Updating Containers 1. Export existing containers 2. Modify the columns you need to change 3. Keep the ID column intact 4. Ensure _delete is FALSE ## Deleting Containers 1. Export the containers you want to delete 2. Set _delete to TRUE for those rows 3. Import the file **Check References First**: Before deleting a container, ensure no airports or routes are using it. Reassign them to a different container first. --- # Hub Import/Export Import and export pilot hubs with airport assignments. The Hub importer and exporter let you bulk manage pilot hubs. Hubs group airports together and can be assigned to pilots to define their home base or operating region. **Import Airports First**: Airport codes in the import must match existing airports in your airline. Create Airports before importing Hubs. ## Accessing Import/Export In Orwell, go to Data → Exports to download your hubs as CSV, or Data → Imports to upload changes. ## Column Reference ColumnRequiredDescriptionIDFor updatesvAMSYS record ID. Leave empty when creating. Include when updating or deleting.NameYesHub display name (e.g., "London Hub", "East Coast")Is DefaultNoTRUE to use as default hub for new pilots. Only one hub can be default.OrderNoDisplay order (lower numbers appear first)Airport Codes (ICAO/IATA)NoComma-separated airport codes belonging to this hub_deleteYesSet to TRUE to delete, FALSE otherwise **Default Handling**: When you set a hub as default, all other hubs are automatically set to non-default. Only one hub can be the default. ## Creating Hubs 1. Leave the ID column empty 2. Fill in the required Name column 3. Add airport codes (comma-separated) if desired 4. Set _delete to FALSE ## Updating Hubs 1. Export existing hubs 2. Modify the columns you need to change 3. Keep the ID column intact 4. Ensure _delete is FALSE ## Deleting Hubs 1. Export the hubs you want to delete 2. Set _delete to TRUE for those rows 3. Import the file **Pilot Assignments**: Before deleting a hub, ensure no pilots are assigned to it. Reassign pilots to a different hub first. --- # Badge Import/Export Import and export pilot badges with rules and page content. The Badge importer and exporter let you bulk manage pilot achievement badges. Badges can be awarded automatically based on rules or manually by staff. ## Accessing Import/Export In Orwell, go to Data → Exports to download your badges as CSV, or Data → Imports to upload changes. ## Column Reference ColumnRequiredDescriptionIDFor updatesvAMSYS record ID. Leave empty when creating. Include when updating or deleting.NameYesBadge name. Must be unique within your airline.CategoryYesCategory for grouping badgesDescriptionNoBadge description shown to pilotsOrderNoDisplay order (lower numbers appear first)Rules (JSON)NoAuto-award rules in JSON format. Leave empty for manual-only badges.Page Content (JSON)NoCustom page content in JSON format_deleteYesSet to TRUE to delete, FALSE otherwise **Manual vs Automatic Badges**: Badges without rules are automatically flagged as manually awardable. Badges with rules are awarded automatically when pilots meet the criteria. ## JSON Format The Rules (JSON) and Page Content (JSON) columns expect valid JSON strings. When exporting, these are output as JSON. When importing, ensure the JSON is properly formatted and escaped for CSV. ## Creating Badges 1. Leave the ID column empty 2. Fill in required columns: Name, Category 3. Add Rules (JSON) for automatic awarding, or leave empty for manual 4. Set _delete to FALSE ## Updating Badges 1. Export existing badges 2. Modify the columns you need to change 3. Keep the ID column intact 4. Ensure _delete is FALSE ## Deleting Badges 1. Export the badges you want to delete 2. Set _delete to TRUE for those rows 3. Import the file **Pilot Awards**: Deleting a badge removes it from all pilots who have earned it. This action cannot be undone. --- # Scenery Import/Export Import and export airport scenery recommendations by simulator and developer. The Scenery importer and exporter let you bulk manage airport scenery recommendations. Each scenery entry links an airport to a specific scenery package for a particular simulator. **Import Airports First**: The airport must exist in your airline before you can add scenery entries for it. Create Airports before importing Scenery. ## Accessing Import/Export In Orwell, go to Data → Exports to download your scenery entries as CSV, or Data → Imports to upload changes. ## Column Reference ColumnRequiredDescriptionICAO/IATAYesAirport code. Must exist in world airports and be configured for your airline.TypeYesScenery type (e.g., "Freeware", "Payware")SimulatorYesSimulator name (e.g., "MSFS 2020", "X-Plane 12", "P3D v5")URLYesLink to the scenery package (must be a valid URL)DeveloperYesDeveloper or publisher name_deleteYesSet to TRUE to delete, FALSE otherwise ### Info Columns (Export Only) These columns appear in exports for reference but are ignored during import. - Airport Name - The airline airport name - Info-Scenery ID - Internal vAMSYS record ID - Info-Airport ICAO, Info-Airport IATA - World airport codes **Uniqueness**: Scenery entries are identified by the combination of airport, type, simulator, and developer. Importing a row with the same combination updates the existing entry rather than creating a duplicate. ## Creating Scenery Entries 1. Fill in all required columns: ICAO/IATA, Type, Simulator, URL, Developer 2. Ensure the airport is already configured in your airline 3. Set _delete to FALSE ## Updating Scenery Entries To update an existing scenery entry, import a row with the same combination of airport, type, simulator, and developer. The URL will be updated to the new value. 1. Export existing scenery entries 2. Modify the URL or other columns as needed 3. Keep the identifying columns intact (ICAO/IATA, Type, Simulator, Developer) 4. Ensure _delete is FALSE ## Deleting Scenery Entries 1. Export the scenery entries you want to delete 2. Set _delete to TRUE for those rows 3. Import the file --- # PFPX Export Export routes and routings in PFPX format for use with Professional Flight Planner X. The PFPX exporters let you export your routes and routings in a format compatible with Professional Flight Planner X (PFPX). The exported files are TXT format and can be imported directly into PFPX. **Export Only**: PFPX exports are one-way only. The TXT format cannot be imported back into vAMSYS. Use the standard Route or Routing importers for vAMSYS data management. ## Accessing PFPX Exports In Orwell, go to Data → Exports and select either Route (PFPX) or Routing (PFPX) from the export options. ## Export Types ### Route PFPX Export Exports scheduled routes with their flight plan route strings. Each route that has a routing assigned will appear in the export. ### Routing PFPX Export Exports all pre-defined flight plan route strings. Useful when you want to export your routing database for use in PFPX. ## File Format The exported TXT file contains one route per line in PFPX format: ```text EGLLKJFK;EGLL DCT WOBUN N57 MATCH MATCH6 KJFK ``` The format is: DEPTICAOARRICAO;DEPTICAO ROUTE_STRING ARRICAO - DEPTICAOARRICAO - Departure and arrival ICAO codes concatenated (identifier) - DEPTICAO - Departure airport ICAO code - ROUTE_STRING - The flight plan route string - ARRICAO - Arrival airport ICAO code ## Using in PFPX 1. Export your routes or routings using the PFPX export option 2. Download the generated TXT file 3. In PFPX, import the file using the appropriate import function **Related Documentation**: For managing routes and routings within vAMSYS, see the Route Import/Export and Routing Import/Export documentation. --- # Fleet Define aircraft types with capacities, route restrictions, SimBrief overrides, and default images inherited by aircraft. Fleets are groups of aircraft that share common characteristics. A fleet defines capacities, route restrictions, SimBrief configuration, and default images that all aircraft in the fleet inherit. Individual aircraft can override these defaults when needed. ## Accessing Fleet Management In Orwell, go to Fleet → Fleet. You need the Manage Aircraft permission. ## Fleet Structure Your fleet structure can be as simple or complex as your VA needs. Most airlines start simple: - B737 - A320 But you can split fleets by region or operation type: - B738 - UK - B738 - EU Or even more granular: - B738 - UK Charter - B738 - UK Scheduled - B738 - EU Charter - B738 - EU Scheduled Split fleets become powerful when combined with Allowed Prefixes to control which aircraft operate which routes. ## Fleet Settings ### General Tab FieldDescriptionNameDisplay name for the fleet (e.g., "B737-800 UK Ops")Type CodeICAO type designator (e.g., "B738"). Must be a real code supported by SimBrief.Fleet TypeDetermines capacity fields and cargo handling (see Fleet Types below)Maximum PassengersNumber of passenger seats. Aircraft inherit this unless overridden.Maximum CargoCargo capacity in kg (commercial freight, not baggage). Aircraft inherit this unless overridden.Maximum ContainersContainer unit count. Aircraft inherit this unless overridden.Allowed PrefixesWhich callsign prefixes this fleet can operate. Empty means all routes.Hide in PhoenixHides this fleet from Phoenix → Resources → AircraftPIREP Scoring GroupGroups this fleet for PIREP scoring comparisons ### Fleet Types TypeRequired FieldsUse CasePassengerMax PassengersPure passenger operations with no commercial freightPassenger & FreightMax Passengers, Max CargoMixed passenger and cargo by weightPassenger & ContainersMax Passengers, Max Cargo, Container UnitsPassengers with containerised cargoCargo - FreightMax CargoDedicated freighter by weightCargo - ContainersContainer UnitsDedicated freighter by container count ### Allowed Prefixes Allowed Prefixes control which routes a fleet can operate. Routes have callsign prefixes (like "BAW" or "SHT") configured in Settings → Callsign Parameters. - Empty: Fleet can operate all routes - With prefixes: Fleet only appears for routes matching those prefixes When you remove a prefix from a fleet, routes using that prefix are automatically deallocated from the fleet. ### SimBrief Integration Tab Configure SimBrief defaults for all aircraft in this fleet. Individual aircraft can override these settings. Enforced SimBrief Aircraft Profiles (Fleet-only) - Specify which SimBrief profiles pilots can choose when booking. This restricts pilot selection to approved profiles. Other SimBrief overrides include: - OFP Layout - Force a specific OFP format - Airframe Equipment - Performance code, weight category, ETOPS settings, ICAO equipment - Airframe Weights - Passenger/baggage weights, OEW, MZFW, MTOW, MLW, max fuel - Fuel Planning - Contingency, reserve, minimum fuel values - Performance - Fuel factor, climb/cruise/descent profiles - Alternate Management - Override how SimBrief searches for alternates **SimBrief Override Advice**: These values override SimBrief aircraft profiles -pilots cannot change them. Avoid being too strict, as different addons have different weights and fuel factors. Sometimes less is better. A good approach: use Enforced Profiles for airframe selection, then only override fuel planning parameters. ### ACARS Sounds Tab Upload custom sounds for Pegasus to play during flights with this fleet. You can customise sounds for: boarding, pushback, safety briefing, climb, cruise, descent, approach, landing, and unloading. ### Image Tab Upload a default image for this fleet. Images are displayed in: - Pegasus during flight - Live Flight map when viewing flight details - Phoenix aircraft resource pages - Orwell fleet management If no fleet image is set, vAMSYS falls back to Planespotters images when available. Individual aircraft images override the fleet default. Recommended size: 400x300 pixels, highly optimised. ## Inheritance Fleets provide defaults that aircraft inherit: SettingInheritance BehaviourCapacitiesAircraft uses fleet value unless aircraft has its own overrideSimBrief settingsAircraft overrides take priority, then fleet, then airline defaultsImageAircraft image → Fleet image → Planespotters ## Tips - Start simple - Begin with basic fleets (B737, A320) and split later if needed - Split fleets for route control - Multiple fleets with the same type code but different Allowed Prefixes lets you control which aircraft serve which routes - Fleet filter setting - If using split fleets, check Settings → Booking & Dispatch → Flight Centre use Fleet Filters to control whether filtering uses fleet name or type code - Pair profiles with overrides - Use Enforced SimBrief Profiles for weight handling, then add fuel planning overrides separately - Scoring groups - Use PIREP Scoring Groups for fair scoring comparisons (e.g., separate turboprop and jet categories) ## Related - Aircraft Management - Individual aircraft registrations that inherit from fleets - Fleet Import/Export - Bulk fleet management --- # Aircraft Manage individual aircraft registrations with optional overrides for capacities, SimBrief settings, and images. Aircraft represent individual registrations within your fleet. Each aircraft belongs to a fleet and inherits its capacities, SimBrief settings, and image -but can override any of these when needed. ## Accessing Aircraft Management In Orwell, go to Fleet → Aircraft. You need the Manage Aircraft permission. ## Aircraft Settings ### General Tab FieldDescriptionNameDisplay name (e.g., "B737-800 'Spirit of vAMSYS'")RegistrationAircraft registration code (e.g., "G-LUJA")SELCALOptional SELCAL codeFin NumberOptional tail/fin numberHex CodeOptional Mode S transponder hex codeFleetWhich fleet this aircraft belongs to (required)PassengersOverride fleet passenger capacity (leave empty to inherit)FreightOverride fleet cargo capacity in kg (leave empty to inherit)Container UnitsOverride fleet container count (leave empty to inherit)Internal RemarksStaff-only notes, not visible to pilots. Shown as tooltip in aircraft list.Hide in PhoenixHides this aircraft from pilots (e.g., for maintenance) Capacity fields show the inherited fleet value as a placeholder. Only enter values if this aircraft differs from its fleet. **No Uniqueness Requirement**: Aircraft registrations do not need to be unique. You can create the same registration (e.g., G-LUJA) multiple times, each assigned to a different fleet. This is useful for split fleet structures. ### SimBrief Integration Tab Override SimBrief settings for this specific aircraft. These take priority over fleet-level settings. Available overrides match the fleet settings: - OFP Layout - Airframe Equipment (performance code, weight category, ETOPS, ICAO equipment) - Airframe Weights (OEW, MZFW, MTOW, MLW, max fuel) - Fuel Planning (contingency, reserve, minimum fuel values) - Performance (fuel factor, climb/cruise/descent profiles) Only set overrides where this aircraft differs from its fleet. Empty fields inherit from the fleet. ### Image Tab Upload a custom image for this aircraft. This overrides both the fleet image and any Planespotters image. Images are displayed in: - Pegasus during flight - Live Flight map when viewing flight details - Phoenix aircraft resource pages - Orwell aircraft management FieldDescriptionAircraft ImageUpload image (recommended: 400x300 pixels, highly optimised)Author/AttributionRequired if image uploadedLinkBackOptional URL to original image source ## Image Cascade vAMSYS uses a three-tier image cascade: 1. Aircraft image - If set, always used 2. Fleet image - Used if no aircraft image 3. Planespotters - Automatic fallback based on registration lookup The same cascade applies to image attribution and linkback. ## Bulk Operations ### Change Type Reassign multiple aircraft to a different fleet: 1. Select aircraft using checkboxes 2. Click Change Type from the bulk actions menu 3. Choose the new fleet 4. Confirm the change ### Hide or Unhide in Phoenix Hide or unhide multiple aircraft from Phoenix in one action—useful when part of your fleet moves in or out of maintenance: 1. Select aircraft using checkboxes 2. Click Hide in Phoenix or Unhide in Phoenix from the bulk actions menu Updates run in the background, so even very large selections are processed without timeouts. Hidden aircraft are removed from Phoenix and cannot be booked until unhidden. ## Inheritance from Fleet Aircraft inherit settings from their assigned fleet: SettingBehaviourCapacitiesUses aircraft value if set, otherwise fleet valueSimBrief settingsAircraft overrides → Fleet settings → Airline defaultsImageAircraft image → Fleet image → PlanespottersHide in PhoenixBoth fleet AND aircraft must be visible for pilots to see it ## Tips - Use internal remarks - Notes appear as tooltips in the aircraft list, helping staff identify aircraft quickly - Hide for maintenance - Use "Hide in Phoenix" to temporarily remove aircraft from bookings without deleting them, either on the edit form or in bulk from the aircraft list - Override sparingly - Only set capacity or SimBrief overrides when an aircraft genuinely differs from its fleet - Favorites tracking - The aircraft list shows how many pilots have favourited each aircraft - Same registration in multiple fleets - You can create the same registration in different fleets for split operations ## Related - Fleet Management - Aircraft type definitions that provide defaults - Aircraft Import/Export - Bulk aircraft management --- # Account Management Merge user accounts, reset or delete pilot accounts, and delete your vAMSYS account. vAMSYS provides several account management options in Phoenix. You can merge duplicate user accounts, reset a pilot account to start fresh, delete a pilot account from a specific VA, or delete your entire vAMSYS account. **Understand the Difference**: Your **User Account** is your vAMSYS identity - your email, password, and network IDs. Your **Pilot Accounts** are separate accounts within each Virtual Airline you join. Deleting a pilot account does not affect your user account or other pilot accounts. ## Merging User Accounts If you accidentally created multiple vAMSYS user accounts, you can merge them into one. This combines your network IDs, staff status, and pilot accounts from both accounts. ### How to Merge 1. Log in to the account you want to keep (the primary account) 2. Click your name in the top bar → My vAMSYS Account 3. Scroll down to Account Settings 4. In the Merge User Accounts box, enter the email address of the account you want to merge in (the secondary account) 5. Click Merge Accounts and confirm 6. Check the email of your secondary account for a confirmation link 7. Click the link to approve the merge ### What Gets Merged - Network IDs - VATSIM, IVAO, POSCON, APOC, and SimBrief are copied to your primary account if not already set - Discord connection - Moves to your primary account if not already connected - Pilot accounts - All pilot accounts are moved to your primary account - Staff status - Transferred to your primary account; VA ownership is preserved ### When Both Accounts Have Pilots in the Same VA If you have pilot accounts in the same VA from both user accounts, the secondary pilot account is merged into the primary one. Whether PIREPs and data are transferred depends on the VA's settings - some VAs preserve the data, others discard it. After the merge completes, the secondary user account is deleted. ## Resetting Your Pilot Account Some VAs allow you to reset your pilot account. This removes all your PIREPs and bookings, letting you start fresh with the same username and account. **This Cannot Be Undone**: Resetting your pilot account permanently deletes your flight history, points, and rank progress in that VA. Only do this if you are certain you want a completely fresh start. ### How to Reset 1. In Phoenix, log in to the VA where you want to reset 2. Go to My Profile → Preferences 3. Find the Reset Pilot Account box 4. Click the reset button 5. Enter your vAMSYS password to confirm ### Requirements - The VA must have pilot reset enabled - You cannot have active bookings - You cannot have PIREPs needing a reply or pending review ## Deleting a Pilot Account If you want to leave a Virtual Airline, you can delete your pilot account. This is a two-step process with a grace period to prevent accidental deletion. ### How to Delete 1. In Phoenix, log in to the VA you want to leave 2. Go to My Profile → Preferences 3. Find the Delete Pilot Account box 4. Click the delete button 5. Confirm when prompted ### The Freeze Period When you request deletion, your pilot account is frozen - not immediately deleted. The freeze lasts until midnight UTC, two days after your request. During this time: - You cannot access the VA - Your other VAs and user account are unaffected - Logging back into that VA cancels the deletion If you do not log back in, the pilot account is permanently deleted after the freeze period. **Rejoining After Deletion**: Some VAs allow you to rejoin after deleting your pilot account. Others do not - you will see a warning before confirming deletion if the VA does not allow rejoining. ## Deleting Your vAMSYS Account Deleting your vAMSYS account removes your user account and all pilot accounts across every VA. **Permanent Removal**: After the grace period, your account is permanently deleted. You will not be able to create a new vAMSYS account or rejoin any VA in the future. ### How to Delete 1. Click your name in the top bar → My vAMSYS Account 2. Scroll down to Account Settings 3. In the Delete User Account box, click Schedule vAMSYS and All Pilot Account Removal 4. Confirm when prompted 5. Close the tab without refreshing the page ### The 90-Day Grace Period Your account is frozen for 90 days before permanent deletion. During this time: - Logging back in cancels the deletion - Your account is automatically reactivated - You cannot access any VAs - After 90 days, the account is permanently removed ### Restrictions - VA owners cannot delete their account - Cancel or transfer your VA first If you only want to leave specific VAs while keeping your vAMSYS account, delete individual pilot accounts instead. ## Staff-Initiated Pilot Merges VA staff can also merge pilot accounts if you have duplicate pilots within their VA. This is useful when the user merge process would not cover your situation (e.g., if you have two pilot accounts in the same VA from the same user account). Contact the VA's staff if you believe you have duplicate pilot accounts that need merging. ## Related - How to Register with a Virtual Airline --- # Activity Requirements Configure initial and ongoing activity requirements for pilots, including grace periods and removal settings. Activity requirements ensure pilots remain engaged with your Virtual Airline. You can set requirements for new pilots (initial) and for all active pilots (ongoing), with customisable grace periods and removal settings. **Two Separate Systems**: Initial and ongoing activity requirements are independent. You can enable one, both, or neither. Initial requirements apply once after joining; ongoing requirements apply continuously. ## Accessing Activity Settings In Orwell, go to Settings → Activity Settings. You need the Manage Airline Settings permission. ## Ongoing Activity Requirements Ongoing requirements apply to all active pilots continuously. Enable Enable Activity Requirements to configure: SettingDescriptionActivity TypeBased on PIREPs (count of reports) or Hours (flight time)Activity AmountNumber of PIREPs or hours required to meet activityActivity PeriodRolling window in days (1-366) over which activity is measuredGrace PeriodDays a pilot has to recover after failing to meet activity (0-366) ### How It Works Each night at midnight in your airline's configured timezone (or UTC if not set), the system checks all pilots: 1. Pilots who have not met activity requirements in the last Activity Period days are put on Activity Grace 2. Pilots on grace receive an email notification 3. If they still fail to meet requirements after the Grace Period, their pilot account is removed 4. If a pilot files a PIREP that satisfies requirements, they are immediately removed from grace (no waiting for midnight) ### Example With settings: 1 PIREP every 7 days, 7-day grace period - Pilot joins January 1st, files a PIREP on January 2nd - On January 9th (7 days since last PIREP), they go on grace - By January 16th, if no PIREP filed, their account is removed ## Initial Activity Requirements Initial requirements apply once to newly joined pilots. Enable Enable Initial Activity Requirements to configure: SettingDescriptionInitial Activity TypeBased on PIREPs or HoursInitial Activity AmountNumber of PIREPs or hours requiredInitial Activity PeriodDays from joining to satisfy the requirementInitial Activity ReminderDays after joining to send reminder if requirement not yet met ### Key Differences from Ongoing - No grace period - If pilots fail to meet initial requirements by the deadline, they are removed immediately - One-time only - Once satisfied, initial requirements never apply again to that pilot - Optional reminder - Can send an email reminder before the deadline **Enabling on Existing VAs**: When you enable initial activity requirements (or expand the period), existing pilots whose accounts fall within that window become subject to the requirement. For example, enabling a 7-day initial requirement means all pilots who joined in the last 7 days and have not yet filed a PIREP will be checked. Consider this before enabling on an established VA. ### Example With settings: 1 PIREP within 7 days, reminder after 5 days - Pilot joins January 1st - On January 6th, if no PIREP filed, they receive a reminder email - By January 8th, if still no PIREP, their account is removed ## What Counts as Activity By default, only accepted and complete PIREPs count toward activity. Two additional toggles allow you to include: - Count Rejected PIREPs - Include rejected PIREPs in activity calculation - Count Invalidated PIREPs - Include invalidated PIREPs in activity calculation For hours-based activity, the system uses flight time. If your VA includes taxi time (configured in Airline Settings), block time is used instead. ### Excluded Flight Types You can exclude specific flight types from activity requirement checks. PIREPs with excluded flight types are ignored entirely — they do not count towards or against activity thresholds for both initial and ongoing requirements. Configure excluded flight types in Settings → Activity Requirements under the Excluded Flight Types checkbox list. The available flight types are: Scheduled, Cargo, Charter, Training, Repositioning, VFR, and Jumpseat. Excluded flights are only ignored for activity requirement checks. They still count towards pilot statistics, rank progression, leaderboards, and all other systems. **Common Use Case**: Exclude training or repositioning flights if you only want scheduled passenger flights to count towards activity requirements. This prevents pilots from satisfying requirements with non-revenue flights. **Not Retroactive**: Changes to excluded flight types only affect future activity checks. Existing activity statuses (grace, initial requirement tracking) are not retroactively recalculated when the exclusion list changes. ## Permanent Removal Enable Pilot Removal is Permanent to prevent removed pilots from rejoining via your registration page or Pilot Sharing Agreement. When disabled, removed pilots can reapply. You can also configure a custom denial message shown to pilots who try to rejoin after permanent removal. ## Email Notifications Go to Settings → Activity Emails to customise email templates for: EmailWhen SentInitial Activity ReminderAfter reminder days pass without initial activity being metInitial Activity RemovalWhen pilot is removed for not meeting initial requirementsActivity Grace StartedWhen pilot is put on activity graceActivity RemovalWhen pilot is removed for not meeting ongoing requirements Available template variables: - {first_name}, {last_name}, {username} - {login_url}, {support_url}, {support_email} ### Email Content Tips Initial Activity Reminder: - Friendly tone - they are new and may just need a nudge - Explain what they need to do (file a PIREP) and by when - Include {login_url} so they can take action immediately - Offer help - link to getting started guides or support Activity Grace Started: - Clear but not alarming - this is a warning, not a removal - State exactly how many days they have to recover - Explain that one flight is usually enough to get off grace - Mention holidays if enabled - they can book time off if needed - Include {login_url} and {support_email} Removal Emails (Initial and Ongoing): - Professional and respectful - avoid blaming language - Explain what happened and why - If rejoining is allowed, explain how they can reapply - If removal is permanent, be clear about this - Thank them for their time with the VA - leave a positive impression ## Activity Immunity Some pilots are automatically exempt from activity requirements: - Staff members - Anyone with an Orwell staff role is exempt - Whitelisted pilots - Pilots with the Activity Whitelist flag enabled in their pilot profile To whitelist a pilot, edit their pilot record in Orwell → Pilots and enable the Activity Whitelist toggle. ### Pending PIREP Deferral A pilot with a recent PIREP still awaiting review — or awaiting their reply — is temporarily deferred from removal, so nobody is removed while their flight is sitting in the review queue. This deferral is time-bounded: it lasts for the airline's PIREP Reply Window plus the activity grace period. A PIREP awaiting a pilot reply that never gets one is automatically invalidated after the reply window, after which normal activity rules apply. For initial activity requirements, a pilot deferred by a pending PIREP is re-checked daily for up to two weeks after their initial activity period ends, rather than being checked only once. ## Holidays Integration When holidays are enabled, pilots can book time off that pauses their activity requirements. See Holidays for full details. Key interactions: - Pilot holidays pause individual activity requirements - Airline holidays pause new grace periods for everyone (but not existing ones) - Returning from holiday may put pilots on grace immediately depending on your settings ## Restoring Pilots When restoring a removed pilot: - Reusing username - Initial activity requirements do not apply (they already passed once). They may go on ongoing activity grace overnight. - New username - Treated as a new pilot. Both initial and ongoing requirements apply normally. ## Pilot View Pilots see their activity status in Phoenix: - Activity Summary - Shows required vs actual activity on their profile dashboard - Grace warning - Alert banner if on activity grace with removal date - Immunity notice - Message if whitelisted that no action will be taken ## Tips - Balance strictness - Very strict requirements (short periods, no grace) will remove casual pilots quickly. Consider your VA culture. - Use reminders - Initial activity reminders give new pilots a nudge before removal. - Consider holidays - If enabling activity requirements, consider also enabling holidays so pilots can take breaks. - Grace after holidays - Set a reasonable grace period to account for pilots returning from holiday who need time to fly. - Whitelist carefully - Use the whitelist for special circumstances, not to exempt all your active members. ## Related - Holidays - Pause activity requirements for individuals or VA-wide --- # Airports Define the locations your pilots fly to and from, with briefings, alternates, and load management. Airports define the locations your pilots fly to and from. vAMSYS pulls airport data from OurAirports, so you only add the airports you actually use rather than working with 83,000+ global entries. ## Adding Airports In Orwell, go to Operations → Airports → Airports. When you create an airport, enter the ICAO or IATA code. vAMSYS looks up the coordinates, elevation, and other data from OurAirports automatically. ## Airport Data & OurAirports vAMSYS sources airport data from OurAirports, an open database of global airports. When you enter an ICAO or IATA code, vAMSYS looks up coordinates, elevation, and other details automatically. If an airport is missing or has incorrect data: 1. Go to OurAirports.com 2. Search for the airport and submit a correction, or add a new entry 3. Wait for your change to be approved by OurAirports moderators 4. vAMSYS syncs OurAirports data daily -your correction will appear automatically This applies to missing airports, wrong coordinates, incorrect ICAO/IATA codes, and wrong elevation or other metadata. **Data Corrections**: Do not contact vAMSYS support for airport data issues -corrections must go through OurAirports. ## Airport Settings FieldDescriptionNameDisplay name (e.g., "London Stansted" or just "Stansted" -your choice)CategoryOptional grouping (informational only, no restrictions)BaseMarks airport on Book Flight and Destination maps; interacts with Jumpseat to BaseSuitable AlternateInclude in the Alternate Finder during flight dispatchAirport Briefing URLExternal link that replaces internal briefing content ### Airport Briefing You can provide pilots with airport information in two ways: 1. Internal content: Use the Briefing and Information fields (rich text) 2. External link: Set Airport Briefing URL to redirect all "Airport Information" buttons to your own documentation (e.g., Hangar PDFs, external knowledgebase) When the URL is set, internal fields are hidden and all buttons link to your external content. ### Taxi Times Set expected taxi-in and taxi-out times for AutoReject validation. vAMSYS also calculates averages from actual PIREP data, displayed alongside your configured values. ## Airport Managers Restrict which staff can edit routes for specific airports. Staff without "Can Manage All Routes" permission only see routes to/from airports they manage. Each manager assignment has an Inbound toggle: - Enabled: Manager can only edit routes arriving at this airport - Disabled: Manager can edit both departing and arriving routes ## Alternate Management Configure how SimBrief selects alternates for flights to this airport. ### Search Parameters ParameterDefaultDescriptionRadius447 nmMaximum distance for alternate searchCeiling3000mMinimum ceiling at alternateRunway Length7000 ftMinimum runway lengthAvoid Bad WeatherOffSkip weather-affected airportsExclude Airports -ICAO codes to never use as alternates ### Fixed Alternates Override SimBrief's selection with specific airports: - Takeoff Alternate (for departures) - 4 arrival alternates (primary through quaternary) **No Validation**: SimBrief won't verify fixed alternates are actually viable from weather or runway perspectives -use with caution. ### Preferred Alternates List ICAO codes that should be highlighted in the Alternate Finder. These aren't forced, just featured more prominently. Note: Fleet-level Alternate Management settings override these airport-level settings. ## Load Management Set default Load Factor profiles and available Containers for routes terminating at this airport. Routes can override these defaults. ## Where Airports Appear LocationWhat's ShownPhoenix → AirportsFull list with favorites, route countsPhoenix → Airport DetailBriefing, information, scenery, METARBooking PageAirport info button, METAR link, favorite toggleLive Flight MapAirport markersOrwell → RoutesDeparture/arrival selection ## Tips - Start small - Only add airports you'll actually use. You can always add more later. - Use categories - Group airports by region, operation type, or any classification useful for your VA. - External briefings - If you maintain detailed airport documentation elsewhere, use Airport Briefing URL rather than duplicating content. ## Related - Hub Management - Group airports into pilot starting locations - Scenery Management - Recommend add-ons for your airports --- # Alerts Display important messages to pilots in Phoenix and Pegasus. Alerts are banner messages displayed to pilots in Phoenix and/or Pegasus. Use them for announcements, warnings, or important information that pilots should see when they log in. ## Accessing Alerts In Orwell, go to Communications → Alerts. You need the View Alerts permission. ## Creating an Alert Each alert requires: FieldDescriptionTitleBold heading shown at the top of the alert (max 255 characters)TypeVisual style: Success (green), Danger (red), Warning (amber), Info (blue), Secondary (grey)ContentMessage body with basic markdown formatting (bold, italic, links)Start ShowingWhen the alert becomes visible (Zulu time). Defaults to now if left empty.Stop ShowingWhen the alert expires (Zulu time). Leave empty for a permanent alert.Show Alert InWhere to display: Phoenix (web dashboard) and/or Pegasus (ACARS client) ## Alert Types Choose a type that matches the message importance: TypeColourUse ForSuccessGreenPositive news, completed updates, achievementsDangerRedCritical issues, service disruptions, urgent warningsWarningAmberScheduled maintenance, upcoming changes, cautionsInfoBlueGeneral announcements, new features, tipsSecondaryGreyLow-priority notices, background information ## Where Alerts Appear Phoenix: Alerts display in an Alerts component on the dashboard. You control where this component appears via Orwell → Pages → Phoenix Dashboard. Position it wherever suits your VA - top of the page for maximum visibility, or elsewhere in the layout. Pegasus: Alerts appear on the first page after airline selection, mirroring the dashboard behaviour in Phoenix. You can choose to show an alert in one or both locations. ## Managing Alerts ### Ordering Alerts can be reordered by dragging rows in the table. The order determines display sequence - alerts at the top show first. ### Stopping an Alert Early Use the Stop Showing action to immediately hide an alert. This sets the end time to now, so the alert won't be deleted and remains in your history. ### Permanent Alerts Leave the Stop Showing field empty to create a permanent alert that doesn't expire. Use the table filter to show or hide permanent alerts. ## Discord Integration If you have Discord notifications configured with an alert channel, new alerts are automatically posted to Discord. When editing an existing alert, enable Resend Notification to Discord to post it again (useful after significant edits). ## Alerts vs NOTAMs Both features display messages to pilots, but they serve different purposes: FeatureAlertsNOTAMsDisplayBanner on dashboard/PegasusDedicated page with read trackingRead trackingNoYes - tracks who has read each NOTAMCan block bookingNoYes - Must Read NOTAMs require acknowledgementBest forQuick announcements, system statusImportant notices requiring acknowledgement ## Tips - Keep alerts concise - Pilots scan quickly. Get to the point. - Use appropriate types - Reserve Danger for genuine emergencies. - Set expiry dates - Time-sensitive announcements should auto-expire so you don't forget to remove them. - Schedule ahead - Use Start Showing to prepare alerts for future events. - Don't overuse - Too many alerts leads to alert fatigue. Alerts that don't apply to most pilots cause general disinterest - soon all alerts get ignored. For example, a permanent "Welcome to our VA" alert isn't relevant to existing pilots; use the welcome email instead, or a Must Read NOTAM that new pilots acknowledge once. Avoid permanent alerts; if information needs to persist, consider NOTAMs or a custom page. ## Related - NOTAMs - Notices requiring pilot acknowledgement --- # Badges Award pilots for achievements with manual or automatic badges based on flight milestones. Badges are optional awards given to pilots for achieving milestones or participating in special activities. Staff create and manage badges in Orwell → HQ → Rewards → Badges. Pilots view their earned badges on their profile and browse all available badges at Community → Badges in Phoenix. ## Enabling Badges Badges are an optional feature. Enable them at Settings → vAMSYS Modules → Badges. You need the Can Manage Badges permission to create and manage badges. ## Badge Types Badges are either manual or automatic, determined by whether they have a rule. Manual (no rule)Automatic (has rule)How awardedStaff awards manuallySystem awards when rule is metWhen checkedN/AEach time a PIREP is processedMultiple awardsYes - can award same badge multiple timesNo - one per pilotCan remove from pilotYesNo **Automatic Badge Timing**: Badge eligibility is checked when PIREPs are processed, not in real-time. A pilot reaching 10 years of service at midnight will not receive their service badge until they file their next PIREP. ## Creating a Badge Click New Badge and configure the following: FieldDescriptionNameBadge name shown to pilotsCategoryGroup badges for organisation (e.g., "Events", "Milestones", "Airports"). Pilots can filter by category.Badge IconImage displayed for the badge (maximum 200×200 pixels)DescriptionPlain text description shown in badge listsRuleAutomation rule (optional). Leave empty for manual badges.Page ContentRich content displayed when pilots view badge details (optional) ### Badge Rules Each badge can have one rule. Adding a rule makes the badge automatic. #### Activity Rules RuleDescriptionEvent ParticipationAwarded for participating in a specific eventActivity Participation - CountAwarded for completing X PIREPs in selected activity types (Event, Tour, Roster, Curated Roster, Focus Airport)Community - Completed / WonTied to a specific Community Goal or Challenge. Goals: awarded to every participant when the goal is achieved. Challenges: awarded to every contributor on the winning team, only if that team reached its target.Community - Top 10% ContributorsTied to a specific Community Goal or Challenge. Awarded to the top 10% of contributors when the activity ends (requires tiered rewards enabled on the activity). Goals: only if the goal is achieved. Challenges: only within the winning team. **Community Rules Award at the End**: Unlike Event Participation, the two Community rules are evaluated when the activity's rewards are distributed — not per PIREP — because the outcome (goal achieved, winning team) is only known once the activity ends. Only active Community Goals and Challenges can be selected; rules cannot be attached to ended activities. #### Milestone Rules RuleDescriptionLength of ServiceAwarded after X days, weeks, months, or years of membershipTransport - PassengersAwarded for transporting X total passengersTransport - CargoAwarded for transporting X total cargoPoints - Regular/Bonus/AllAwarded for accumulating X points (regular, bonus, or combined) #### Flight Rules RuleDescriptionFlight Length - IndividualAwarded for a single flight between X and Y secondsFlight Length - TotalAwarded for X total seconds of flight timeFlight Distance - TotalAwarded for X total nautical miles flownPIREPs - CountAwarded for X completed PIREPs #### Landing Rules RuleDescriptionPIREPs - Landing RateAwarded for landing at an exact FPM value X timesPIREPs - Landing Rate BetweenAwarded for landing within an FPM range X times **Landing Rate Range Values**: When setting landing rate ranges, remember that -200 is a harder landing than -100. To award landings between -100 and -200 FPM, set Min to -200 and Max to -100. #### Airport Rules RuleDescriptionPIREPs - Landing AirportAwarded for X landings at selected airportsPIREPs - Landing Airport RunwayAwarded for X landings on specific runways at a selected airportPIREPs - Departing AirportAwarded for X departures from selected airportsPIREPs - Arriving or Departing AirportAwarded for X flights at selected airports (either arriving or departing) **Airport Rules Use AND Logic**: When multiple airports are selected, pilots must visit ALL of them to earn the badge. For example, a "Go Essex!" badge requiring Luton, Stansted, and Cambridge means pilots must land at all three airports. ### Optional Rule Filters Many rules support optional filters to narrow eligibility: - Online Networks - Only count flights on specific networks (VATSIM, IVAO, POSCON, APOC, PilotEdge, FSCloud, SayIntentions, Offline, Other) - Fleets - Only count flights using specific fleets - Callsign Parameters - Only count flights using specific callsign parameters - Route Tags - Only count flights on routes with specific tags - Airports - Only count flights at specific airports ### Page Content Each badge can have rich content displayed when pilots view its details. Add panels with these components: - Text - Rich text content - Image - Images with optional click-through URL - Button - Styled buttons with links - Alert - Coloured alert boxes - YouTube Video - Embedded videos Each component has a width setting (1-12) for layout control. ## Bonus Points Each badge can optionally award bonus points on every PIREP filed by a pilot who holds that badge. This lets you reward pilots for earning and keeping specific badges. - Bonus Points — the number of bonus points to award per PIREP. Set to 0 or leave empty to disable. - As Percentage — when enabled, the bonus points value is treated as a percentage of the base PIREP score rather than a fixed amount. Use the toggle to swap between fixed and percentage modes. - Bonus Name — optional custom display name for this bonus (e.g., "Veteran Bonus", "Elite Reward"). If left empty, the badge name is used. **Multiple Badge Bonuses Stack**: If a pilot holds multiple badges with bonus points configured, all bonuses stack additively on each PIREP with no cap. Each badge bonus is calculated independently against the base PIREP score — percentage bonuses do not compound on each other. For example, if a pilot has a 10% badge and a 50-point badge, and the base score is 200 points, the total badge bonus is 20 + 50 = 70. Badge bonuses also stack with Staff Bonus and Airport Manager Bonus if those are enabled. ## Managing Badges ### Awarding Manual Badges To award a manual badge: 1. Click on the badge in the badge list 2. Scroll to the Pilots table at the bottom 3. Click Award Badge and select a pilot To remove a manual badge from a pilot, find them in the Pilots table and click Remove Badge. ### Editing Badges You can freely edit a badge's name, description, image, category, or rules. Important behaviours: - Edits do not affect existing awards - Pilots who already earned the badge keep it, regardless of changes. - Rule changes do not re-evaluate - Changing a rule does not remove badges from pilots who no longer meet the new criteria. - PIREP reprocessing triggers checks - If a pilot should have earned a badge but has not filed recently, reprocessing one of their PIREPs will trigger eligibility checks. ### Converting Automatic to Manual To stop an automatic badge from being awarded without deleting it: 1. Edit the badge 2. Remove the rule 3. Save This converts it to a manual badge. Pilots who already earned it keep it. You can now also remove the badge from individual pilots if needed. ### Deleting Badges **Deletion Removes Badges from Pilots**: When you delete a badge, it is permanently removed from all pilots who earned it. There is no way to restore a deleted badge or its pilot associations. To delete a badge, select it from the badge list and click Delete. This action permanently deletes the badge and removes it from all pilots. Consider converting to manual instead if you want to stop awarding while preserving existing awards. ## Where Pilots See Badges LocationWhat It ShowsPilot Profile → BadgesBadges the pilot has earned, most recent firstCommunity → BadgesAll VA badges with image, name, category, description, and recipient count. Filter by category. Click "View Recipients" to see who earned each badge. ## Tips - Use categories - Group related badges (Events, Milestones, Airports, Achievements) for easier navigation. - Create badge series - Progressive badges (100 hours, 500 hours, 1000 hours) give pilots goals to work towards. - Event badges - Create unique badges for special events to commemorate participation. - Manual badges for special recognition - Screenshot competitions, exceptional service, or other achievements that cannot be automatically detected. ## Related - Ranks - Automatic progression based on hours and points - Scoring Groups - Configure how pilots earn points --- # Branding Customise your VA logos, colours, backgrounds, and styling in Phoenix, Orwell, and Pegasus. Make vAMSYS feel like your own with custom logos, colours, backgrounds, and CSS. These settings apply across Phoenix, Orwell, Pegasus, and emails. ## Accessing Design Settings In Orwell, go to Settings → Design. You need the View Design Settings permission. The Design section contains: - Logo Settings - Your logos and login backgrounds - Style Settings - Colour overrides and custom CSS ## Logos You need four logo variants to cover all display contexts: LogoWhere UsedLogo for Bright BackgroundsPhoenix (light theme)Logo for Dark BackgroundsPhoenix (dark theme)Select Logo for Bright BackgroundsVA selection page, Pegasus (light theme), emails, Orwell (light theme)Select Logo for Dark BackgroundsVA selection page, Pegasus (dark theme), Orwell (dark theme) Recommended size: 1800 x 400 pixels for all logos. **Why Two Sets of Logos?**: Phoenix logos appear in the main navigation and need to work within that context. Select/Orwell/Pegasus logos appear in different layouts (VA selection screens, admin panels, emails) and may need different proportions or styling to look best. ## Background Images Upload background images for your login and registration pages. You can upload multiple images - one is selected at random for each page load. Recommended size: 1706 x 1600 pixels. Be mindful of file size - avoid large PNGs; use optimised JPEGs instead. ## Colour Overrides Override the default colour scheme with your VA brand colours. Each colour has light and dark theme variants: ElementDescriptionMenu BackgroundSidebar/navigation menu backgroundTop Bar BackgroundHeader bar backgroundMenu ItemDefault menu and top bar text colourMenu Item ActiveCurrently selected menu item colourMenu Item HoverMenu item colour on mouse hoverBody BackgroundMain content area backgroundBody ColourMain text colourCard BackgroundContent card/panel backgroundsCard Title TextCard header text colourTable Row Odd/EvenAlternating table row coloursPlane IconAircraft icon colour in UI elements Leave a colour empty to use the default. Only override what you need. ## Custom CSS For advanced customisation, upload a custom CSS stylesheet. This is loaded after the default styles, allowing you to override any element. **Advanced Feature**: Custom CSS is for users who understand CSS, browser developer tools, and can inspect the vAMSYS source styles. No support is provided for CSS customisations. Incorrect CSS can break your VA appearance. ### Community CSS Package If you want comprehensive styling without writing CSS from scratch, the community-maintained vAMSYS v5 Custom CSS package provides an end-to-end solution. Simply edit three colour variables (primary, secondary, dark mode) and upload the stylesheet. ### Writing Your Own CSS To create custom CSS from scratch: 1. Use browser developer tools to inspect elements you want to change 2. Write your CSS rules in a .css file 3. Upload the file to Style Settings 4. Test in both light and dark themes ## Tips - Test both themes - Pilots can choose light or dark mode. Ensure your branding works in both. - Use transparent backgrounds - Logos with transparent backgrounds adapt better to theme colours. - Optimise images - Large images slow page loads. Compress backgrounds before uploading. - Check contrast - Ensure text remains readable against your custom colours. - Start minimal - Override only what you need. The defaults are designed to work well together. --- # Containers Define cargo container types for container-based aircraft operations. Containers define the cargo Unit Load Devices (ULDs) available for container-based aircraft. When a fleet is configured as "Passenger & Containers" or "Cargo - Containers", pilots select which containers to load during dispatch rather than specifying cargo by weight alone. ## Accessing Containers In Orwell, go to Payload → Containers. You need the Manage Containers permission. ## Understanding Container Units Container-based cargo operations use a unit system rather than raw weight. Each aircraft has a Container Units capacity (set on the fleet or aircraft), representing available cargo positions. Think of it like parking spaces in a car park: - The aircraft has 12 "spaces" (container units) - An LD3 container takes 2 spaces - A pallet takes 4 spaces - Pilots can load any combination that fits the available spaces This models real-world constraints where physical space - not just weight - determines what can be loaded. ### Real-World ULD Examples ULD TypeTypical UseApproximate SizeLD3Lower deck, narrow-body/wide-bodySmall (1-2 units)LD6Lower deck, wide-bodyMedium (2-3 units)LD11Lower deck, wide-bodyLarge (3-4 units)Pallet (PMC)Main deck freightersLarge (4-6 units)Half PalletSmaller cargo loadsMedium (2-3 units) Your container unit sizes don't need to match real-world exactly - choose values that create interesting loading decisions for your pilots. ## Container Properties FieldDescriptionNameDisplay name shown to pilots (e.g., "LD3 Main Deck"). Should be unique for easy identification.TypeContainer type identifier (e.g., "LD3", "Pallet", "LD-4"). Helps group similar containers.Unit SizeHow many container units this container occupies (1-9999). Must fit within aircraft's Container Units capacity.WeightLoaded weight in kilograms. Used for weight and balance calculations.NotesOptional notes visible to pilots when selecting containers.Incompatible ContainersContainers that cannot be loaded together with this one. ## Container Assignment Containers must be assigned to Airports or Routes to appear in dispatch. Without assignment, pilots cannot select them. ### Assignment Priority Departure AirportRouteResultHas containersHas containersRoute containers usedNo containersHas containersRoute containers usedHas containersNo containersAirport containers usedNo containersNo containersNo containers available Route assignments always override airport defaults. ### Assignment Strategy Use Airport defaults when: - Most routes from an airport use the same containers - You want consistent container options across a hub - You're modelling real-world airport cargo facilities Use Route overrides when: - Specific routes have unique cargo requirements - Charter or special flights need different container options - You want to restrict containers on certain routes **Recommended Approach**: Set up containers at your major hubs first, then add route-specific overrides only where needed. ### Assigning to Airports In Orwell, go to Airports → Airports, select an airport, then open the Load Management tab. The Containers field sets the default containers for flights departing from this airport. ### Assigning to Routes In Orwell, go to Routes → Routes, select a route, then find the Containers section. Containers assigned here override the departure airport's defaults. ## Container Incompatibility Some containers cannot be loaded together due to physical constraints or operational rules. When you mark containers as incompatible: - The relationship is bidirectional (marking A incompatible with B also marks B incompatible with A) - During dispatch, selecting an incompatible container disables conflicting options - Pilots cannot bypass these restrictions Use cases for incompatibility: - Containers requiring special handling equipment that can't be used simultaneously - Hazmat containers that cannot travel with certain cargo types ## The Dispatch Flow When a pilot dispatches a container-capable flight: 1. Load factors calculate limits - Cargo (Weight) and Cargo (Volume) load factors determine maximum weight and units 2. Containers become available - Based on route or airport assignment 3. Pilot selects containers - Choosing types and quantities 4. System enforces limits - Weight, volume, and incompatibility rules apply 5. Generate Random Payload - Optional auto-fill within constraints ### What Pilots See During dispatch on container-capable aircraft, pilots see: - Available containers with their type, weight, and unit size - Any notes you've added to help with selection - Current weight and volume usage as containers are selected - Quantity input for each selected container type - Remaining capacity for both weight and volume The Generate Random Payload button automatically fills containers within the aircraft's weight and volume limits, respecting incompatibility rules. This is useful for pilots who want realistic loads without manual selection. ## Integration with Other Systems ### SimBrief Container weights are included in the payload sent to SimBrief for flight planning. The OFP reflects the actual container load. SimBrief may offload cargo to meet MTOW, MLW weights - vAMSYS will not update with offloaded containers. ### PIREPs Container loads are recorded in the PIREP, showing what cargo was carried on the flight. ### Load Factors Containers work alongside Load Factors: - Cargo (Weight) load factor sets the maximum total container weight - Cargo (Volume) load factor sets the maximum container units - Pilots must stay within both limits ## Tips - Use descriptive names - Include position or purpose (e.g., "LD3 Forward Hold", "Pallet Main Deck") - Set unit sizes realistically - Match your aircraft's actual ULD positions - Add notes for special handling - Help pilots understand when to use specific containers - Use incompatibility for conflicts - Prevent impossible loading configurations - Assign at airport level first - Use route overrides only for specific operational requirements - Create variety - Offer different container sizes so pilots can optimise their loads - Consider your fleet types - Only container-capable fleets use this system ## Troubleshooting Pilots can't see any containers: - Check containers are assigned to the departure airport or route - Verify the fleet type is "Passenger & Containers" or "Cargo - Containers" Containers appear greyed out: - They're incompatible with an already-selected container - Weight or volume limits have been reached Weight/volume limits seem wrong: - Check Cargo (Weight) and Cargo (Volume) load factors - Verify aircraft container unit capacity ## Related - Fleet - Configure container-capable fleet types - Load Factors - Control cargo weight and volume limits - Container Import/Export - Bulk container management - Airports - Set airport-level container defaults --- # Holidays Allow pilots to take time off and suspend activity requirements VA-wide during holiday periods. Holidays pause activity requirements so pilots can take time off without losing their account. There are two types: individual pilot holidays and VA-wide airline holidays. **Requires Activity System**: Holidays only apply when you have activity requirements enabled. Without activity requirements, there is nothing to pause. ## Enabling Holidays In Orwell, go to Settings → Activity Settings. Enable Enable Holidays (only visible when activity requirements are enabled). Configure: SettingDescriptionHoliday AllowanceDays per year each pilot can take. Changing this resets all pilot allowances.Pilot Account Age RequirementHow many days old a pilot account must be before they can book holidays. ## Pilot Holidays Individual pilots can book their own holidays to pause their activity requirements. ### How Pilots Book Holidays Pilots go to Phoenix → My Profile → Settings → Holidays and click Book Holiday. They select start and end dates, limited by their remaining allowance. The page shows: - Remaining holiday allowance - When allowance resets (anniversary of joining) - Total annual allowance - Booked holidays ### During a Holiday - Activity requirements are paused - no grace period, no removal - Pilot cannot book flights - Logging in ends the holiday early - unused days return to allowance **Activity Grace After Return**: When a holiday ends, activity requirements resume immediately. Depending on your settings and the holiday duration, the pilot may go on activity grace overnight. Consider this when setting your grace period. ### Staff Managing Pilot Holidays Staff can view and create holidays on behalf of pilots: Orwell → Pilots → Holidays shows all pilot holidays across the VA. You need the View Pilot List permission. When creating a holiday for a pilot, you can choose whether it counts against their allowance. This is useful for compassionate leave or special circumstances. ## Airline Holidays Airline holidays are VA-wide periods where activity requirements are suspended for everyone - useful for Christmas, major events, or scheduled downtime. Go to Orwell → Operations → Airline Holidays. You need the Manage Airline Holidays permission. ### How Airline Holidays Work - Pilots can still fly if they want - flights are not blocked - No new pilots are put on activity grace during this period - Pilots already on grace are still removed as scheduled - airline holidays do not save them - Does not consume pilot holiday allowance - Shown automatically to pilots - pilots see the airline holiday in their Activity Requirements Summary on their profile ### Creating an Airline Holiday Simply set a start and end date. The system tracks who created it for audit purposes. ## Pilot vs Airline Holidays FeaturePilot HolidaysAirline HolidaysScopeIndividual pilotEntire VAUses allowanceYes (unless staff marks otherwise)NoCan flyNoYesBooked byPilot or staffStaff onlySaves pilots on graceYesNoLocationOrwell → Pilots → HolidaysOrwell → Operations → Airline Holidays ## Holiday Allowance Reset Each pilot's holiday allowance resets annually on the anniversary of when they joined the VA. If a pilot joined on March 15th, their allowance resets every March 15th. ## Tips - Set a reasonable grace period - Pilots returning from holiday may need time to file a PIREP before activity checks resume. - Use airline holidays for major events - Christmas week, summer holidays, or VA-wide breaks. - Account age requirement - Prevents new pilots from immediately going on holiday to avoid initial activity requirements. - Staff-entered holidays - Use the 'counted' toggle for compassionate leave that shouldn't consume allowance. - Overlapping holidays - If a pilot is on their own holiday when an airline holiday starts, they don't get their days back. The pilot holiday continues as booked. - Announce airline holidays - While pilots see airline holidays in their Activity Summary, consider using an Alert or NOTAM for more visibility, especially for longer breaks. --- # How to Apply for a Rank Transfer Skip the starting ranks by applying for a rank transfer when joining a new VA. If you have experience flying for other Virtual Airlines, you may be able to skip the starting ranks when joining a new VA. This is called a rank transfer. **Apply Before Your First Flight**: You can only apply for a rank transfer before you file your first PIREP with the VA. Once you have any flight history, the transfer option disappears. ## How Rank Transfer Works vAMSYS uses a "direct entry" system rather than transferring your exact hours and points. If you qualify, you receive a promotion to a specific rank (often First Officer) chosen by the VA - not a copy of your entire flight history. For example: if the VA's transfer rank is First Officer requiring 100 hours, and you have 500 hours elsewhere, you will receive exactly 100 hours - enough to reach First Officer. Your 500 hours are not transferred directly. ## Checking If Transfer Is Available Not all VAs offer rank transfers. To check: 1. Log in to Phoenix 2. Click your profile button (top right) 3. Look for Apply for Rank Transfer button If you do not see this button, either: - The VA does not offer rank transfers, or - You have already filed a PIREP with this VA ## Transfer Types ### Internal Transfer (vAMSYS to vAMSYS) If you already fly for other VAs on vAMSYS, you can apply for an internal transfer. The system automatically checks your hours and points across all your vAMSYS pilot accounts. - No proof required - the system verifies automatically - Approved automatically if you meet requirements - Processing happens within an hour (usually faster) ### External Transfer If your experience is from Virtual Airlines outside vAMSYS, you will need to provide proof of your flight time. - Requires proof - URLs to your statistics pages or flight logs - Staff review required - approval is not automatic - Enter the total hours you are claiming ## Applying for a Transfer 1. Click Apply for Rank Transfer 2. Read the VA's transfer policy in the modal 3. If both types are available, choose Internal or External 4. For external transfers: - Add URLs to pages showing your flight time (VA statistics pages, pilot profiles, etc.) - Make sure the URLs are publicly accessible - Enter the total hours you are claiming 1. Click Submit ## After Applying You do not need to wait. You can book flights and file PIREPs immediately. Your transfer will be processed in the background. - Internal transfers - automatically approved within an hour if you meet the requirements - External transfers - wait for staff review. The VA decides if your proof is sufficient. When approved, the system creates a transfer PIREP that awards you the hours and points needed for the transfer rank, and your rank is updated. ## Important Notes - One application only - You cannot resubmit if rejected. Make sure your proof is clear and complete. - First PIREP deadline - Apply before filing any flights. The option disappears after your first PIREP. - VA-specific - Each VA has different requirements and transfer ranks. What qualifies at one VA may not at another. - Not all VAs offer transfers - This is entirely at the VA's discretion. ## Tips - Use public statistics pages - Your old VA's pilot statistics page is ideal proof. - Include multiple sources - The more proof you provide, the stronger your application. - Check URL accessibility - Open your links in an incognito/private browser window to ensure they work without login. - Read the VA's policy - The transfer modal explains what proof they accept and what rank you are applying for. --- # How to Book Holidays Take time off from your Virtual Airline without losing your account to inactivity. Need a break from flying? Book a holiday to pause your activity requirements. Your account stays safe while you take time off. **Not All VAs Use This**: Holidays are an optional feature. If you don't see the Holidays section in your settings, your VA hasn't enabled it or doesn't have activity requirements. ## Booking a Holiday 1. Go to My Profile → Settings → Holidays 2. Click Book Holiday 3. Select your start and end dates 4. Confirm The page shows your remaining allowance, when it resets, and any holidays already booked. ## What Happens During Your Holiday - Activity requirements pause - You won't be put on grace or removed for inactivity - You can't book flights - The booking system is disabled while you're on holiday - Logging in ends your holiday - If you log into Phoenix, your holiday ends immediately and unused days return to your allowance ## Ending Your Holiday Early Simply log into Phoenix. Your holiday ends automatically and any unused days are returned to your allowance. ## Your Allowance - Your VA sets how many holiday days you get per year - Your allowance resets on the anniversary of when you joined - You can't book more days than you have remaining - Unused days from ending early are returned ## After Your Holiday Activity requirements resume immediately when your holiday ends. Depending on your VA settings, you may need to fly soon to avoid going on activity grace. Check your dashboard for your activity status. --- # How to Meet Activity Requirements Understand your Virtual Airline activity requirements and what happens if you fall behind. Some Virtual Airlines require you to fly regularly. If your VA has activity requirements, here is how to check your status and what happens if you fall behind. **Not All VAs Use This**: Activity requirements are optional. If you don't see activity information on your profile, your VA doesn't have activity requirements. ## Checking Your Activity Status Go to My Profile → Dashboard. The Activity Requirements Summary shows: - Required Activity - How many PIREPs or hours you need in the activity period - Your Activity - Your actual PIREPs or hours in that period - Status - Whether you are meeting requirements, on grace, or have immunity ## Understanding the Requirements Activity is measured in a rolling window. For example, "1 PIREP every 7 days" means you need at least 1 PIREP in the last 7 days at any point - not 1 PIREP per calendar week. Your VA may measure activity by: - PIREPs - Number of flight reports filed - Hours - Total flight time ## What Happens If You Fall Behind ### Activity Grace If you don't meet activity requirements, you are put on Activity Grace. This is a warning period - you won't be removed immediately. You'll receive an email and see an alert in Phoenix showing: - That you are on activity grace - The date your account will be removed if you do not fly ### Getting Off Grace File a PIREP that meets the requirements. As soon as your PIREP is processed and you meet activity, you are immediately removed from grace - no need to wait for the next day. ### Account Removal If you don't meet activity requirements by the end of the grace period, your pilot account is removed. Depending on your VA's settings, you may or may not be able to rejoin. ## Initial Activity Requirements Some VAs have a separate requirement for new pilots. For example, "file 1 PIREP within 30 days of joining." This is a one-time requirement - once you satisfy it, it never applies again. **No Grace for Initial Activity**: Initial activity requirements typically have no grace period. If you don't meet them by the deadline, your account may be removed without warning. ## Taking Time Off If your VA has holidays enabled, you can book time off to pause your activity requirements. See How to Book Holidays. Your VA may also declare VA-wide holidays (like Christmas) where activity requirements are suspended for everyone. These appear in your Activity Summary when active. ## Activity Immunity Some pilots are exempt from activity requirements: - Staff members - If you have staff access in Orwell - Whitelisted pilots - If staff have granted you immunity If you have immunity, your Activity Summary will note that no action will be taken even if you are not meeting requirements. ## Tips - Check your dashboard regularly - Your activity status is always visible - Book holidays before you leave - Don't wait until you're already away - Don't panic on grace - You have time. One flight is usually enough to recover. - Contact staff if needed - If you have special circumstances, staff may be able to help --- # How to Register with a Virtual Airline Join a Virtual Airline on vAMSYS - finding VAs, registration process, and what to expect. Ready to join a Virtual Airline? Here is how to find one, register, and what happens next. **One Account Per Person**: Creating multiple vAMSYS user accounts is a Terms of Service violation. Use one account for all your Virtual Airlines. If you have multiple accounts, merge them as soon as possible via My Account in Phoenix. ## Finding a Virtual Airline There are several ways to find VAs to join: - VA websites and social media - Most VAs advertise their registration link on their website, Discord, or social channels. - MyNextAirline - The vAMSYS VA directory at mynextairline.com lets you browse and discover VAs. Find one you like and click through to their registration page. - Partner VAs - If you already fly for a VA, check your VA selection screen for partner airlines you can join easily. ## Registration Process ### If You Already Have a vAMSYS Account 1. Go to the VA's registration link 2. Log in with your existing vAMSYS account 3. Accept the VA's rules (if required) 4. Your pilot account is created (or submitted for review) ### If You Are New to vAMSYS 1. Go to the VA's registration link 2. Create a vAMSYS account with your email 3. Verify your email address 4. Complete the VA registration 5. Accept the VA's rules (if required) ## Registration Review Some VAs manually review applications before creating pilot accounts. If review is enabled: 1. You submit your registration 2. You receive a confirmation email that your application is under review 3. VA staff reviews your application 4. You receive an email when accepted (or rejected) Review times vary by VA - some review within hours, others may take days. Check the VA's Discord or website for expected wait times. ## Joining Partner Airlines If your VA has Pilot Sharing Agreements with other VAs, you can join them easily: 1. Log in to vAMSYS 2. On the VA selection screen, look for partner airlines 3. Click to join - registration is streamlined Partner VAs may still have registration review enabled, so you might wait for approval. ## After Registration Once your pilot account is created: - You receive a welcome email with your username and login link - Log in to Phoenix to access your pilot dashboard - Download Pegasus ACARS if you want to track flights automatically - Check if your VA has initial activity requirements - you may need to fly within a certain period ## Joining Multiple VAs You can fly for multiple Virtual Airlines with one vAMSYS account. Each VA gives you a separate pilot account with its own: - Username - PIREP history - Rank and points - Activity requirements Switch between VAs using the VA selection screen after login. ## Troubleshooting Registration link not working? - Check if the VA is still active - contact them through their Discord or website - Make sure you have the correct link Application rejected? - Check the rejection email for the reason - Contact the VA if you believe it was in error - Some VAs allow reapplication - check their policies Already have a pilot account that was removed? - If the VA allows rejoining, you can register again - Your previous data may or may not be restored depending on VA settings - If you were permanently removed, you cannot rejoin that VA **VA-Specific Questions**: Each Virtual Airline sets its own registration policies. For questions about a specific VA's requirements, contact that VA directly - not vAMSYS support. --- # Hubs Define starting locations for new pilots, group airports into regions, and enable hub-based leaderboards. Hubs define starting locations for new pilots and can be used for hub-based leaderboards when enabled. Each hub contains one or more airports that pilots can select when joining your airline. ## Creating Hubs In Orwell, go to Operations → Airports → Hubs. Each hub needs: - Name: City, airport, or region (e.g., "London", "East Coast", "Europe") - Airports: One or more airports that form this hub - Default Hub: Whether new pilots are auto-assigned here ## Default Hub When enabled, all new pilots joining your airline are automatically assigned to this hub. If the hub contains multiple airports, one is selected at random as their starting location. Only one hub can be default. Setting a new default clears the previous one. If you have no default hub, new pilots must manually select their starting hub and location. ## Pilot Hub Assignment New pilots are assigned a hub in one of two ways: 1. Automatic: If a default hub exists, pilots are assigned there with a random airport as their location 2. Manual: Pilots select their hub during first Phoenix visit Pilots can change their hub anytime via Phoenix → My Profile → Dashboard → Statistics card → Details. **Hub vs Location**: Changing hub does not affect current location. A pilot in London can switch to New York hub without moving -they'll still need to fly or jumpseat to get there. ## Editing and Deleting Hubs You can rename hubs, change airports, or modify any settings freely. Existing pilot assignments remain unchanged. Deleting a hub: - Unassigns all pilots from that hub - Does not change pilot locations - Does not force pilots to pick a new hub ## Where Hubs Appear LocationWhat's ShownPhoenix → AirportsHub badges on airport listPhoenix → DashboardPilot's current hub in statisticsHub SelectionNew pilots choose starting hubOrwell → PilotsHub column with pilot counts ## Tips - You need at least one hub - Without a hub, new pilots have nowhere to start. - Geographic naming - "London", "New York", "Southeast Asia" work well for international VAs. - Single-airport hubs - If each hub is one airport, pilot location equals hub location. - Multi-airport hubs - Useful for regions where multiple airports serve as valid starting points. ## Related - Airport Management - The locations that make up your hubs --- # Load Factors Configure passenger and cargo load calculations with statistical distributions. Load Factors control how passenger counts and cargo weights are calculated when pilots dispatch flights. Rather than fixed values, load factors use statistical distributions to create realistic variation - some flights are nearly full, others have empty seats. ## Accessing Load Factors In Orwell, go to Payload → Load Factors. You need the Manage Load Factors permission. ## Load Factor Types Each load factor type applies to a specific capacity calculation. The applicable types depend on your fleet configuration. ### Passenger (People) Applies to: Passenger, Passenger & Freight, Passenger & Containers fleets Determines how many passengers board the flight. The calculation uses the aircraft's passenger capacity (or fleet default if not overridden on the aircraft). Example: Aircraft has 180 seats. Load factor generates 85%. Result: 153 passengers. ### Passenger (Hold Luggage) Applies to: Passenger, Passenger & Freight, Passenger & Containers fleets Determines how many passengers have checked baggage. Unlike other load factors, this calculation is based on the passenger count, not aircraft capacity. Example: 153 passengers boarded. Luggage load factor generates 60%. Result: 92 bags of hold luggage (not 108, which would be 60% of 180 seats). This reflects reality - luggage correlates with passengers, not empty seats. ### Cargo (Weight) Applies to: Passenger & Freight, Cargo - Freight, Passenger & Containers, Cargo - Containers fleets For non-container fleets (Passenger & Freight, Cargo - Freight): Determines how much cargo weight is loaded. Uses the aircraft's cargo capacity in kilograms. Example: Aircraft has 5,000 kg cargo capacity. Load factor generates 70%. Result: 3,500 kg of cargo loaded. For container fleets (Passenger & Containers, Cargo - Containers): Sets the maximum weight limit for container loading. Pilots can load containers up to this weight limit. Example: Aircraft has 20,000 kg cargo capacity. Load factor generates 80%. Result: Pilots can load containers totalling up to 16,000 kg. ### Cargo (Volume) Applies to: Passenger & Containers, Cargo - Containers fleets only Determines how many container units can be filled. Uses the aircraft's Container Units capacity (configured on the fleet or aircraft). Example: Aircraft has 12 container units. Load factor generates 75%. Result: Pilots can load containers occupying up to 9 units. ### Container Aircraft: Dual Limits Container-capable aircraft are constrained by both Cargo (Weight) and Cargo (Volume) load factors. Pilots must stay within whichever limit is reached first. **Dual Limit Example**: Aircraft: 20,000 kg cargo capacity, 12 container units. Cargo (Weight) generates 80% → 16,000 kg limit. Cargo (Volume) generates 75% → 9 units limit. Available LD3 containers: 1,500 kg, 2 units each. If pilots try to load 6 LD3s: 9,000 kg weight, 12 units → stopped by volume limit (only 9 units allowed). They can load 4 LD3s: 6,000 kg, 8 units → both limits satisfied. ### Summary Table Load Factor TypeFleet TypesBased OnControlsPassenger (People)Pax, Pax & Freight, Pax & ContainersAircraft seat capacityPassengers boardedPassenger (Hold Luggage)Pax, Pax & Freight, Pax & ContainersPassenger count (not capacity)Checked bagsCargo (Weight)Pax & Freight, Cargo - FreightAircraft cargo capacityCargo loadedCargo (Weight)Pax & Containers, Cargo - ContainersAircraft cargo capacityMax container weightCargo (Volume)Pax & Containers, Cargo - ContainersAircraft container unitsMax container units ## Load Factor Settings FieldDescriptionNameDisplay name to identify this profile (e.g., "Peak Season", "Low Demand"). Not shown to pilots.Min %Minimum load percentage (0-100). Flights never load below this.Max %Maximum load percentage (1-100). Flights never exceed this.Average %Target average percentage. Use this OR Bias, not both.BiasDistribution skew (0.0-1.0). Values below 0.5 favour the minimum, above 0.5 favour the maximum.DeviationSpread of generated values (0-100). Higher values create more variation.Set as DefaultMakes this the fallback for routes/airports without a specific assignment. Only one default per type.Enable Loaded Amount EditingWhen enabled, pilots can manually adjust the generated values during dispatch. ## Load Factor Calculator Each load factor has a built-in calculator to preview how your settings will behave. Access it by clicking the Calculate button when viewing or editing a load factor. The calculator lets you: - Enter a capacity value (e.g., 180 passengers, 5000 kg cargo) - Run multiple simulations to see the range of generated values - Verify your min, max, average/bias, and deviation produce realistic results - Fine-tune settings before assigning the load factor to routes or airports This is much faster than dispatching test flights and gives you immediate feedback on how your statistical parameters translate to actual load values. ## vAMSYS Defaults When no custom load factor is assigned, vAMSYS uses these default values: SettingValueMin80%Max100%Bias0.9Deviation0.2 This default configuration generates high utilisation rates averaging approximately 97%. For more realistic variation, consider creating custom profiles with lower minimums. ## Setting Your Own Defaults You can override the vAMSYS defaults by creating your own load factors and marking them as default. ### How Defaults Work - One default per type - Each load factor type (Passenger, Passenger Luggage, Cargo Weight, Cargo Volume) can have exactly one default. - Automatic switch - When you mark a load factor as default, any previous default of that type is automatically unmarked. - Overrides vAMSYS defaults - Your custom default replaces the vAMSYS default for that type across your entire airline. - Fallback behaviour - If you have no custom default for a type, the vAMSYS default (80-100%, bias 0.9) applies. To set a default, edit the load factor and enable Set as Default. The load factor list shows a badge indicating which load factor is the current default for each type. **Recommended Setup**: Create four load factors - one for each type - and mark each as default. This gives you full control over baseline loads across your airline. You can then create additional profiles for specific routes or airports without affecting the defaults. ## Assignment Priority Load factors cascade from most specific to least specific: 1. Route - Load factors assigned to the specific route 2. Arrival Airport - Default load factors for the destination (set on the Airport's Load Management tab) 3. Airline Default - The load factor marked as default for each type The system checks each level in order and uses the first load factor found for each type. ### Assignment Strategy Use Airline defaults for: - Your baseline load expectations - Types you don't need granular control over Use Airport defaults for: - Hubs with consistently high demand - Regional airports with lower traffic - Seasonal destinations Use Route overrides for: - Charter routes with specific load requirements - Premium routes that are always full - Training routes where you want specific loads ### Example Setup For a European carrier: LevelPassenger LFPurposeAirline DefaultMin 50%, Max 95%, Avg 75%General baselineLondon Heathrow (Arrival)Min 70%, Max 100%, Avg 90%High-demand hubSeasonal Greek Islands (Route)Min 85%, Max 100%, Avg 95%Peak summer routes ## Distribution Settings Understanding the statistical parameters: ### Min/Max Range Sets the possible range. A route with Min 60% and Max 95% will never dispatch with less than 60% or more than 95% capacity. ### Average vs Bias Choose one approach - do not use both together: Average - Specify a target average. Over many flights, loads will centre around this value. Bias - Control the distribution shape: - 0.0 = Most flights near minimum - 0.5 = Even distribution across the range - 1.0 = Most flights near maximum The bias creates an implied average: Average = Min + ((Max - Min) × Bias) ### Deviation Controls spread around the average/bias point: - Low deviation (0.1-0.2) clusters values tightly - High deviation (0.5+) spreads values across the full min-max range The system uses a bell curve (normal distribution) and clamps results to the min-max range. ### How the Math Works Load factors use the Box-Muller transform to generate normally distributed values: 1. Two random numbers generate a bell-curve offset 2. The offset is scaled by your deviation setting 3. The result is centred on your average or bias-implied average 4. Values outside min-max are clamped to the range This creates realistic variation where most flights cluster around your target, with occasional high and low outliers. ## Practical Use Cases ### Seasonal Variation Create profiles for different demand periods: ProfileMinMaxAvgUse CasePeak Season75%100%92%Summer holidays, ChristmasShoulder50%90%70%Spring, autumnLow Season30%75%50%Winter off-peak Assign these at the route or airport level as seasons change. ### Route Type Profiles Different route types have different load characteristics: ProfileMinMaxAvgUse CaseBusiness Shuttle60%95%80%Frequent city pairs, business travelHoliday Charter85%100%95%Package holiday flightsRegional Commuter40%85%60%Smaller routes with variable demandCargo Trunk70%100%90%Major cargo hub connectionsCargo Feeder30%80%55%Regional cargo collection ## Pilot Editing The Enable Loaded Amount Editing setting controls whether pilots can adjust generated values: Enable when: - Hosting events where load matters - Pilots need flexibility for special operations - You trust pilots to make reasonable choices Disable when: - You want consistent, realistic operations - Load data feeds into challenge events - You're simulating real-world operational constraints When enabled, pilots see editable fields for passengers, luggage, and cargo during dispatch. They can adjust up to the aircraft's maximum capacity. ## Integration with Other Systems ### SimBrief Generated loads are sent to SimBrief for flight planning. The OFP reflects the actual passenger count, baggage weight, and cargo load - not theoretical maximums. SimBrief may offload cargo and passengers to meet aircraft weight requirements - offloaded passengers or cargo will not be updated on vAMSYS. ### PIREPs Load data is recorded in the PIREP, showing what was carried on the flight. ### Scoring Load factors don't directly affect PIREP scoring, but realistic loads contribute to accurate fuel planning and weight management. ## Setting Up Load Management For a new Virtual Airline, follow this sequence: 1. Create default profiles - One per type with reasonable baseline values 2. Mark defaults - Ensure one default exists per type 3. Test with the calculator - Use the built-in calculator to simulate results before going live 4. Add variation - Create seasonal or route-specific profiles 5. Assign to airports - Set up hub and regional airport defaults 6. Override routes - Add route-specific profiles where needed Start simple and add complexity as your operation grows. ## Troubleshooting Flights are always nearly full: - Check your defaults - vAMSYS default is ~97% average - Create profiles with lower min/average values Loads seem random with no pattern: - Check deviation isn't too high - Verify average or bias is set correctly Load factor not applying: - Check assignment priority (route → airport → default) - Ensure the load factor type matches what you're testing Pilots can't edit loads: - Check "Enable Loaded Amount Editing" on the applicable load factor Container limits seem wrong: - Cargo (Weight) and Cargo (Volume) both apply to container aircraft - Check both load factor types ## Tips - Create scenario-based profiles - Name them by purpose ("Charter Full", "Regional Commuter", "Cargo Express") - Use Arrival Airport defaults - Hub airports often have different demand patterns than outstations - Remember luggage is passenger-based - A 50% luggage load factor on 80 passengers gives 40 bags, not 50% of aircraft capacity - Use the calculator - Test your settings with the built-in calculator before assigning to routes - Consider cargo volume separately - Container aircraft need cargo-volume load factors tuned to their ULD capacity - Start with defaults - Get baseline working before adding complexity - Document your profiles - Use clear names so staff understand which to assign ## Related - Load Factor Import/Export - Bulk load factor management - Containers - Container types for cargo-volume calculations - Airports - Set airport-level load factor defaults - Fleet - Configure fleet types that determine which load factors apply --- # NOTAMs Publish notices that pilots must read and acknowledge before flying. NOTAMs (Notice to Airmen) are formal notices that pilots can read and acknowledge. Unlike Alerts, NOTAMs track who has read them and can require acknowledgement before pilots can book flights. **Optional Feature**: NOTAMs are disabled by default. Enable them in Orwell under Settings → vAMSYS Modules → Enable NOTAM. ## Accessing NOTAMs In Orwell, go to Communications → NOTAMs. You need the View NOTAMs permission. ## Creating a NOTAM Each NOTAM requires: FieldDescriptionTitleBold heading for the NOTAM (max 255 characters)ContentRich text content with formatting and file attachmentsTypeVisual style: Success, Danger, Warning, Info, SecondaryPriorityLow, Medium, or High - affects display ordering and badge colourMust ReadWhen enabled, pilots must acknowledge before booking flightsTagOptional label to categorise NOTAMs (e.g., "Maintenance", "Policy")Redirect URLOptional - redirects pilots to an external page instead of showing contentStart/Stop ShowingVisibility window (Zulu time). Leave Stop empty for permanent. ## Must Read NOTAMs The Must Read option is the key difference between NOTAMs and Alerts. When a Must Read NOTAM is active: 1. Pilots are redirected to the NOTAMs page when they try to access booking or dispatch 2. They must open and read the NOTAM 3. They must click the acknowledge button to confirm they have read it 4. Only then can they proceed to book and fly Non-Must Read NOTAMs are automatically marked as read when a pilot opens them. ## Redirect NOTAMs If you maintain NOTAMs elsewhere (your own website, a custom vAMSYS page), use the Redirect URL field. When pilots click a redirect NOTAM: - They're immediately redirected to your URL - The NOTAM is automatically marked as read - The Content field is ignored (not displayed) ## Where Pilots See NOTAMs Phoenix Dashboard: NOTAMs appear in a dashboard widget showing priority, read status, and expiry. NOTAMs Page: Dedicated page (Phoenix → NOTAMs) with the full list. Unread and Must Read NOTAMs are highlighted. The dashboard widget displays: - Priority badge (colour-coded) - Read status: Must Read (red), Unread (amber), Read (green) - Expiry date - NOTAM title ## Tracking Readership The NOTAMs table in Orwell shows how many pilots have read each NOTAM. This helps you gauge whether important notices are being seen. To reset read status (forcing pilots to read again): 1. Edit the NOTAM 2. Enable Reset Read Status 3. Save This is useful after significant content updates when you need pilots to re-read the notice. ## Discord Integration If you have Discord notifications configured with a NOTAM channel, new NOTAMs are automatically posted. Enable Resend Notification to Discord when editing to post again after updates. ## Filtering NOTAMs The Orwell table offers several filters: - Permanent notices - Show/hide NOTAMs without expiry dates - Date range - Filter by when NOTAMs end - Type - Filter by visual style - Priority - Filter by Low/Medium/High - Must Read - Show only mandatory NOTAMs ## Avoiding NOTAM Fatigue Must Read NOTAMs require acknowledgement one at a time. If you have 20 old Must Read NOTAMs still active, every new pilot joining your VA must click through all 20 before they can book their first flight. This creates a terrible first impression and pilots may leave before they even start. ### Regular Maintenance Schedule regular reviews of your NOTAMs: - Review monthly - Check which NOTAMs are still relevant. Delete or expire outdated ones. - Audit Must Read status - Does that 2-year-old policy NOTAM still need Must Read? If existing pilots have seen it, disable Must Read so new pilots can skip it. - Use expiry dates - Time-sensitive NOTAMs (events, temporary procedures) should always have a Stop Showing date. - Consolidate - Multiple related NOTAMs can often be merged into one. Five small policy updates become one comprehensive policy NOTAM. ### Alternatives to Must Read NOTAMs Not everything needs to be a Must Read NOTAM: ContentBetter OptionWelcome/getting started guideWelcome email or custom pagePermanent VA rulesCustom page linked from dashboardOne-time announcementsTimed Alert with expiryHistorical informationRegular NOTAM (not Must Read) **Check Your Must Read Count**: Filter your NOTAMs list in Orwell to show only Must Read notices. Count them - that's how many times a new pilot must click 'Acknowledge' before their first flight. If it's more than a handful, review which ones truly need Must Read status. For the full experience, you can create a test account: clearly label it in the name fields (e.g., 'Test Account'), use an email from your VA's domain if you have one, and delete the account afterwards to stay compliant with vAMSYS ToS. ## Tips - Use Must Read sparingly - Reserve it for genuinely important notices. Overuse causes frustration. - Set appropriate priorities - High priority NOTAMs appear first and are highlighted. - Use tags consistently - Tags help organise NOTAMs. Decide on categories and stick to them. - Set expiry dates - Time-sensitive NOTAMs should auto-expire. - Monitor readership - If important NOTAMs aren't being read, consider making them Must Read. - Use redirects for external content - If you maintain detailed documentation elsewhere, redirect rather than duplicate. ## Related - Alerts - Quick banner announcements without read tracking --- # Pilot Registration Configure how pilots register for your Virtual Airline, including review process, emails, and rejoining options. Control how pilots join your Virtual Airline - from automatic registration to manual review, plus settings for removals, merges, and rejoining. ## Accessing Registration Settings In Orwell, go to Settings → Pilot Registration. You need the View Airline Settings permission. ## Basic Registration SettingDescriptionLogin/Register Link ModifierYour unique URL slug. Creates your registration link: vamsys.io/register/your-slugRules PageIf set, pilots must accept these rules during registrationDefault to Imperial UnitsNew pilots default to imperial (lbs) instead of metric (kg) weight units ## Registration Review By default, pilots are automatically registered. Enable Review Registrations to manually approve each application before a pilot account is created. ### How Review Works 1. Pilot submits registration through your register page 2. They receive the "Registration Received" email and see your custom review message 3. Application appears in Orwell → Pilots → Registrations 4. Staff reviews and accepts or rejects 5. Pilot receives appropriate email and (if accepted) their account is created When review is enabled, configure Review Page Message for Pilots - this is shown after they submit their registration. ### Reviewing Applications Go to Orwell → Pilots → Registrations. You need the View Pilot List permission. The navigation badge shows pending application count. For each application you can see: - Applicant name and email (if email visibility enabled) - Network IDs (VATSIM, IVAO, POSCON, APOC) - Registration route (direct, PSA, etc.) - Application and user registration dates - Previous pilot accounts at your VA - Total pilot accounts across all VAs ### Accepting Applications Click the green checkmark to accept. The pilot account is created immediately and they receive the "Registration Complete" email. ### Rejecting Applications Click the red X to reject. You must provide: - Reject Reason (required) - Internal reason for your records - Preset (optional) - Select from saved rejection presets to populate the public reason - Reject Public Reason (optional) - Shown to the pilot. If left empty, no rejection email is sent **Rejection Presets**: Create reusable rejection reasons in Settings → Presets. Useful for common scenarios like "Duplicate account" or "Incomplete application". ## Registration Emails Go to Settings → Registration Emails to customise email templates. Requires a Support Email to be set in Basic Settings. EmailWhen SentRegistration ReceivedWhen pilot submits registration for review (only if review enabled)Registration CompleteWhen pilot account is created (immediate or after approval)Registration RejectedWhen application is rejected (only if public reason provided) Available template variables: {first_name}, {last_name}, {username}, {login_url}, {support_url}, {support_email}, {reason} (rejection reason) ### Email Content Tips Registration Received: - Set expectations - explain the review process and typical wait time - Welcome them to the community even before approval - Include {support_email} if they have questions Registration Complete: - Welcome them properly - this is their first impression - Include {login_url} prominently - Link to getting started guides or first flight instructions - Mention Discord or other community channels Registration Rejected: - Use {reason} to show the public rejection reason - Be professional and respectful - Explain if and how they can reapply ## Removal, Merges and Rejoining SettingDescriptionRemoved Pilot DigestReceive daily email listing pilots removed that day. Select a staff recipient.Discard Data on MergeWhen users merge accounts, discard PIREPs from the secondary pilot account.Enable Pilot Account ResetAllow pilots to reset their account, moving history to vAMSYS Robot.RejoiningAllow removed pilots to rejoin (unless permanently removed).Reuse Username on RejoinGive rejoining pilots their previous username instead of a new one.Restore Data on RejoinRestore PIREPs and bookings for rejoining pilots (username not included). ## Alternative Entry Routes Pilots can join your VA through: - Direct registration - Your register page link - Pilot Sharing Agreements - Pilots from partner VAs can join easily. See Pilot Sharing Agreements. - MyNextAirline - vAMSYS VA directory where pilots can discover VAs. Links to your direct registration page. ## Pilot Invites Pilot Invites let staff directly create pilot accounts without the pilot going through registration. This is useful for VA migrations, bulk pilot setup, or creating transfer PIREPs for existing pilots. Access Pilot Invites in HQ → Pilot Invites. You need the View Pilot List permission. ### How It Works When you create an invite, the system processes it within 20-30 minutes: 1. User account - If the email does not exist in vAMSYS, a new user account is created and login credentials are emailed to them 2. Pilot account - A pilot account is created at your VA, bypassing registration review 3. Transfer PIREP - If hours, points, or bonus points are specified, a manual transfer PIREP is created ### Creating an Invite Click Create Invite and enter: FieldDescriptionFirst NameUser's first name (for new accounts)Last NameUser's last name (for new accounts)EmailEmail address (used to find existing user or create new)HoursHours to award via transfer PIREP (0 for none)PointsPoints to award via transfer PIREP (0 for none)Bonus PointsBonus points to award via transfer PIREP (0 for none)Count WeightHow many PIREPs this transfer should count as (default: 1) **Express Permission Required**: You may only invite pilots if you have their express permission to do so. The Data Processing Addendum applies. See vamsys.co.uk/legal for details. ### Use Cases - VA Migration - Moving from another platform? Import pilots with their hours and points intact. - Initial VA Setup - Create founding pilot accounts with appropriate starting ranks. - Missed Transfer Window - Pilot missed the rank transfer deadline? Create an invite for their existing email with hours/points to award a transfer PIREP. - Award Hours/Points - For existing pilots, create an invite with their email to award a transfer PIREP without affecting their account. ### Important Notes - Invites process within 20-30 minutes, not immediately - Duplicate invites for the same email are prevented - New users receive login credentials by email - Existing vAMSYS users get a pilot account added without a new email - Pilot accounts bypass registration review - Banned users cannot be invited ## Tips - Share your register link - Include it on your website, Discord, and promotional materials. - Review promptly - If using registration review, check applications regularly. Long waits lose pilots. - Create rejection presets - Save time with pre-written reasons for common rejection scenarios. - Consider your rejoin policy - Allowing rejoins with data restoration gives pilots second chances without losing history. ## Related - Pilot Sharing Agreements - Partner with other VAs for easy pilot transfers - Activity Requirements - Set requirements for new and ongoing pilots --- # Pilot Sharing Agreements Partner with other Virtual Airlines to allow easy pilot transfers between VAs. Pilot Sharing Agreements (PSA) create partnerships between Virtual Airlines, allowing pilots from one VA to easily join another without going through full registration. **Not Available During Trial**: Pilot Sharing Agreements are not available during the trial period. ## Accessing Sharing Agreements In Orwell, go to Settings → Sharing Agreements. You need the View Share Agreements permission. ## How It Works PSA uses a token-based system: 1. VA A creates a token and shares it with VA B 2. VA B enters the token to form the agreement 3. Pilots see each other - Pilots from VA A see VA B on their VA selection screen, and vice versa 4. Easy registration - Pilots can join the partner VA with one click (subject to registration review if enabled) ## Creating Tokens Click Create Token in the Pilot Share Tokens section. Configure: OptionDescriptionRemaining UsesLimit how many VAs can use this token. Leave empty for unlimited.Expires AtSet an expiry date. Leave empty for no expiry. Share the generated token with the other VA through your preferred communication channel. ## Entering Tokens If another VA shares a token with you, enter it in the form above the tokens table. The agreement is created immediately. ## Managing Agreements The Pilot Share Agreements table shows all active partnerships: - Sending Airline - The VA that created the token - Receiving Airline - The VA that entered the token - Registrations at Sender - How many pilots from the receiving VA joined the sending VA - Registrations at Receiver - How many pilots from the sending VA joined the receiving VA Either VA can delete the agreement at any time. Existing pilot accounts are not affected. ## Pilot Experience When a PSA exists, pilots see partner VAs on their VA selection screen (the page shown after login). They can join with one click. If the partner VA has registration review enabled, the pilot still goes through review. The PSA just makes discovery and initial registration easier. ## Tips - Use limited tokens - If partnering with one specific VA, use a single-use token to prevent sharing. - Set token expiry to limit acceptance window - Token expiry controls when the token can be used, not the partnership duration. Once an agreement is formed, it persists until manually deleted. - Check registration counts - Monitor which partnerships are bringing in pilots. - Consider your review settings - PSA pilots still go through registration review if enabled. ## Related - Pilot Registration - Configure registration settings and review process --- # Presets Create reusable text and point macros for PIREP comments, point adjustments, and registration review. Presets are reusable macros that save time when performing common actions. Instead of typing the same comments or entering the same point values repeatedly, create a preset and apply it with one click. ## Accessing Presets In Orwell, go to Settings → Presets. You need the View Score Settings permission. ## Preset Types There are three types of presets: TypeUsed ForPIREP PointsQuickly add or remove points from a PIREP. Includes a point value and a reason shown to the pilot.PIREP/Claim CommentPre-written comments for PIREPs or claims. The text is inserted into the comment box and can be edited before submitting.Pilot Registration ReviewRejection reasons for registration review. Appears in the rejection reason dropdown. ## Creating a Preset Click New Preset and enter: FieldDescriptionNameInternal name shown in the preset dropdown. Make it descriptive so staff can quickly identify it.ModelWhere this preset applies (PIREP Points, PIREP/Claim Comment, or Pilot Registration Review)ContentThe text shown to pilots when this preset is appliedPointsFor PIREP Points presets only. Positive values add points, negative values remove them. ## Using Presets When you are in a context where presets apply, you will see a preset dropdown: - PIREP Points - When editing points or bonus points on a PIREP, select a preset to apply the point value and reason - Comments - When adding a comment to a PIREP or claim, select a preset to populate the comment box. You can edit the text before submitting. - Registration Review - When rejecting a pilot application, select a preset for the rejection reason ## Important Notes - Changing presets does not affect history - If you edit or delete a preset, previously applied comments, points, or rejection reasons are not changed. - Content is editable - For comments, the preset text is inserted into the comment box where you can modify it before submitting. - Use descriptive names - Staff only see the preset name in the dropdown, so make it clear what each preset does. ## Example Presets ### PIREP Points - Event Bonus (+500) - "Thank you for participating in our group flight event!" - VATSIM Bonus (+100) - "Bonus points for flying on VATSIM" - Speed Violation (-200) - "Points deducted for exceeding speed limits" ### Comments - Great Flight - "Nice flight! Keep up the good work." - Fuel Warning - "Please ensure you load adequate fuel reserves for future flights." ### Registration Review - Incomplete Application - "Your application was incomplete. Please reapply with all required information." - Duplicate Account - "You already have an account with us. Please use your existing account." --- # Rank Transfer Allow pilots to receive a rank promotion based on experience from other VAs. Rank Transfer allows experienced pilots to skip starting ranks when joining your VA. Instead of like-for-like hour transfers, vAMSYS uses a direct entry system where pilots are promoted to a specific rank if they meet the requirements. **Direct Entry, Not Like-for-Like**: vAMSYS does not transfer a pilot's entire hour and point history. Instead, pilots who qualify receive the hours and points required for your designated transfer rank - nothing more. This ensures all pilots earn their way through your rank structure while still recognising prior experience. ## Accessing Rank Transfer Settings In Orwell, go to Settings → Rank Transfer. You need the View Airline Settings permission. ## Transfer Types There are two types of rank transfer: ### Internal Transfer (vAMSYS to vAMSYS) For pilots who fly with other vAMSYS Virtual Airlines. The system automatically checks all their other vAMSYS pilot accounts and sums their hours and points. If the total meets your transfer rank requirements, the transfer is approved automatically. - Fully automatic - no staff review needed - Checks hours and points from all vAMSYS pilot accounts - Processing happens in the background (usually within an hour) ### External Transfer For pilots with experience from non-vAMSYS Virtual Airlines. They must provide proof of their flight time (URLs to statistics pages, screenshots, etc.). These transfers require staff review. - Requires staff review - appears in Transfers queue - Pilots submit proof URLs and claimed hours - You decide if the proof is sufficient ## Configuration SettingDescriptionEnable Rank TransferMaster toggle to enable the featureTransfer Modal TextMarkdown text shown to pilots when they apply. Explain your transfer policy and what to expect.vAMSYS → vAMSYS TransferEnable internal transfers (auto-approved)External TransferEnable external transfers (staff review required)Internal Transfer RankThe rank awarded to qualifying internal transfers. Shows required hours, points, and bonus points.External Transfer RankThe rank awarded to approved external transfers. Shows required hours. ### Choosing a Transfer Rank When selecting a transfer rank, consider: - The rank selector shows hours, points, and bonus points required for each rank - Most VAs use their First Officer rank as the transfer target - Internal and external transfers can have different target ranks - Honorary ranks cannot be used as transfer targets ## Reviewing External Transfers External transfer requests appear in Pilots → Transfers. This menu item only appears when external transfers are enabled. A badge shows the number of pending requests. For each transfer request you can see: - Pilot username and name - Hours claimed - Submission date - Current status Click Review to open the review modal, which shows: - Hours claimed by the pilot - Your transfer rank requirements for comparison - Proof URLs provided by the pilot Click each URL to verify the pilot's claims. Then choose Approve Transfer or Reject Transfer. ### Transfer Processing When a transfer succeeds - automatically for internal transfers, or when you approve an external transfer - the system creates a transfer PIREP that awards the pilot the hours, points, and bonus points required for the transfer rank. The pilot's rank is then updated. This happens in the background and may take a few minutes. ## Important Notes - One-time only - Pilots can only apply for a transfer before filing their first PIREP. Once they have any PIREPs, the option disappears. - One application per pilot - Pilots cannot resubmit if rejected. - Pilots can fly immediately - They do not need to wait for transfer approval. They can book flights and file PIREPs while their application is processed. - Missed the window? - If a pilot missed the transfer deadline, use Pilot Invites to create a transfer PIREP with hours and points for them. ## Tips - Use the Populate Default Text button - Provides a clear starting point for your transfer modal text. - Be clear about proof requirements - In your modal text, specify what proof you accept (VA statistics pages, flight logs, etc.). - Enable both types for flexibility - Most VAs benefit from offering both internal and external transfers. - Consider your rank structure - If your starting rank is already First Officer, transfers may not be meaningful. Consider what rank makes sense as a transfer target. ## Related - Ranks - Configure your rank structure and requirements - Pilot Registration - Registration flow and review settings --- # Ranks Configure pilot ranks with automatic progression, honorary titles, and custom epaulettes. Ranks recognise pilot achievement and progression within your VA. Regular ranks are awarded automatically based on hours, points, and flight count, while honorary ranks are assigned manually for special recognition. **Recognition, Not Restriction**: In vAMSYS, ranks are purely for recognition. They cannot restrict access to routes, aircraft, or airports. Pilots have full access to your entire route network from the moment they join - this freedom of movement is a core vAMSYS principle. ## Accessing Ranks In Orwell, go to HQ → Rewards → Ranks. You need the View Ranks permission. ## Rank Types ### Regular Ranks Regular ranks are awarded automatically when pilots meet the requirements. Each pilot has exactly one regular rank at any time - the highest rank they qualify for. Requirements can include any combination of: - Hours - Total flight hours - Points - Cumulative points earned - Bonus Points - Bonus points from events, staff awards, etc. - PIREPs - Number of flights filed A pilot must meet all requirements to earn a rank. For example, if a rank requires 100 hours and 10,000 points, the pilot needs both. ### Honorary Ranks Honorary ranks are assigned manually to individual pilots. They have no requirements and are used for special recognition: - Staff members - Screenshot competition winners - Real-world pilots - Virtual fleet instructors - Any special occasion you want to recognise Pilots can have one honorary rank in addition to their regular rank. When a pilot has both, they can choose which to display in Phoenix → My Profile → Preferences → Prefer Honorary Rank. This is enabled by default, showing the honorary rank in most places. Assign honorary ranks from the pilot list or individual pilot profiles in Orwell. ## Default Ranks When you create a new VA, two ranks are created automatically: NameAbbreviationTypePurposeCadetCdtRegularStarting rank for all new pilots (no requirements)Staff TeamSTHonoraryFor staff member recognition These default ranks cannot be deleted but can be renamed and customised. You are encouraged to rename them and add epaulette images to match your VA branding. ## Creating a Rank Click New Rank and configure: FieldDescriptionNameFull rank name (e.g., First Officer, Captain)AbbreviationShort form shown in compact views (e.g., FO, CPT)Position / SeparatorControls ordering. See "Rank Ordering" below.HoursRequired flight hours (regular ranks only)PointsRequired points (regular ranks only)Bonus PointsRequired bonus points (regular ranks only)PIREPsRequired number of filed PIREPs (regular ranks only)Honorary RankToggle on to make this an honorary rank (manually assigned, no requirements)ImageEpaulette or badge image. Recommended size: 85×36 pixels. ## Rank Ordering Ranks must be ordered from easiest to hardest to achieve. The ordering determines which rank a pilot receives when they qualify for multiple ranks. **Order Matters**: Incorrect ordering can cause rank assignment issues. A sequence like Cadet → Type Rating Examiner → Second Officer would be wrong because pilots would jump from Cadet to TRE without going through intermediate ranks. Reorder ranks by dragging them in the list or editing the Position field. Lower position numbers appear first (easier ranks). ## Example Rank Structure Here is a typical progression structure for inspiration: NameAbbrHoursPointsCadetCdt00Second Officer2/O1100First OfficerFO12013,500Type Rating InstructorTRI31034,100CaptainCPT66066,000Line Training CaptainLTC85093,500Type Rating ExaminerTRE1,200132,000 ## Example Epaulettes vAMSYS provides a set of epaulette images you can use for your ranks. Feel free to use them as-is or create your own. Download these images by right-clicking and saving. The recommended image size is 85×36 pixels. ## How Rank Assignment Works Rank assignment happens automatically when: - A PIREP is processed - A pilot receives bonus points - A transfer PIREP is created The system checks all rank requirements and assigns the highest rank the pilot qualifies for. Pilots cannot be manually promoted or demoted in their regular rank - it is always calculated based on their totals. ## Where Ranks Appear Ranks are displayed throughout vAMSYS: - Phoenix - Pilot profile, leaderboards, pilot roster - Pegasus - ACARS client displays pilot rank - Orwell - Pilot lists and profiles - Live Map - Active flight information ## Tips - Plan progression carefully - Space requirements so pilots feel progression without ranks being unreachable. - Use consistent abbreviations - Keep abbreviations short (2-4 characters) for clean display. - Create multiple honorary ranks - Different honorary ranks for different roles (Staff, Instructor, Event Winner, etc.). - Consider your transfer rank - If using Rank Transfer, think about where transferred pilots should start. A common choice is First Officer. ## Related - Rank Transfer - Allow experienced pilots to transfer in at higher ranks - Scoring Groups - Configure how pilots earn points --- # Scenery Recommend airport scenery add-ons to help pilots enhance their simulator experience. Scenery recommendations help pilots find quality add-ons for airports in your network. When pilots explore new destinations, they can see your curated scenery suggestions with download links. ## Adding Scenery In Orwell, go to Operations → Airports → Scenery, or manage scenery directly from an airport's edit page under the Sceneries tab. Each scenery entry requires: FieldDescriptionAirportWhich airport this scenery is forURLDownload or purchase linkDeveloperScenery creator (e.g., "FlyTampa", "Orbx")TypeFree text (e.g., "Payware", "Freeware")SimulatorFree text (e.g., "MSFS", "X-Plane 12", "P3D") ## Where Scenery Appears Pilots see scenery recommendations on the Airport Detail Page in Phoenix (Phoenix → Resources → Airports → [Airport]). The scenery section displays: - Simulator - Developer - Type - Download/Link button If no scenery exists for an airport, the section doesn't appear. ## Tips - Curate quality - Only recommend scenery you'd actually use. A short list of good options beats a long list of mediocre ones. - Keep links current - Check periodically that download URLs still work. - Cover your network - Focus on hubs and popular destinations first. - Multiple options - You can add multiple scenery entries per airport for different simulators or quality tiers. - Be consistent - Type and Simulator are free-text fields. Use consistent naming across entries (e.g., always "MSFS 2020" not sometimes "MSFS" and sometimes "Microsoft Flight Simulator"). ## Related - Airport Management - Manage the airports scenery is linked to --- # Staff Add team members, assign permissions, and manage who can access Orwell and Hangar. Staff members are pilots with elevated permissions to manage your Virtual Airline. Each staff member can have customised access to different parts of Orwell and Hangar based on their role. ## Accessing Staff In Orwell, go to HQ → Staff. You need the Can See Staff permission or be the VA owner. ## Staff Types ### VA Staff Your team members. You control their permissions, visibility, and can remove them at any time. ### vAMSYS Staff Team vAMSYS members who provide platform support. They appear in your staff list but: - Cannot be removed - Always have full access for support purposes - Are hidden from your Team Page by default - Have usernames like HTA-Lukas or HTA-Robot You can give vAMSYS staff a title, staff email, and image if they are also part of your VA team. ## Adding Staff Click New Staff and search for an existing pilot by name or username. Only pilots who are not already staff can be added. **Pilots First**: A person must be a pilot in your VA before they can become staff. If adding team members during initial setup, use Pilot Invites to create their pilot accounts first. ## Staff Details FieldDescriptionTitleRole displayed on the Phoenix Team Page (e.g., "Chief Pilot", "Operations Manager")Staff EmailContact email shown on Phoenix Team Page. Can be different from their personal email.HiddenWhen enabled, staff member is not shown on the Phoenix Team PageStaff AvatarProfile image for Team Page. Cropped to 1:1 aspect ratio. Recommended size: 300×300 pixels. ## Permissions Permissions control what each staff member can see and do in Orwell and Hangar. Permissions are organised into categories. ### Subsystem Access Controls access to the main vAMSYS subsystems: - Can Access Orwell - Required for any staff management functions - Can Access Hangar - Access to file storage system ### Pilot Actions PermissionWhat It ControlsCan View PilotsAccess to pilot list, profiles, and pilot-related pages. Also shows New Pilots and Recent Bookings on the Orwell dashboard.Can Delete Pilot ProfileBan or delete pilot accounts, including merge functionalityCan Restore PilotsRestore previously removed pilot accountsCan See Flight Centre - BookingsAccess to the bookings list ### Announcements PermissionWhat It ControlsCan Manage AlertsCreate and manage pilot alertsCan Manage NOTAMsCreate and manage NOTAMs ### PIREP and Livery PermissionWhat It ControlsCan Manage LiveriesReview and approve/reject aircraft liveriesCan Manage PIREPs & ClaimsReview PIREPs and claims, add comments, adjust points ### Operations PermissionWhat It ControlsCan Manage ActivitiesCreate and manage events and toursCan Manage AircraftCreate, update, and delete aircraft and fleetsCan Manage Airports & HubsCreate, update, and delete airports and hubsCan Manage Airport ManagersAssign pilots as airport managers (requires Can Manage Airports)Can Manage SceneryCreate, update, and delete scenery recommendationsCan Manage Load FactorsConfigure passenger and cargo load settingsCan Manage ContainersCreate and manage cargo containersCan Manage RoutesCreate, update, and delete routes at airports where assigned as Airport ManagerCan Manage All RoutesManage routes at any airport regardless of Airport Manager assignment (requires Can Manage Routes)Can Manage Airline HolidaysConfigure VA-wide holidays if enabled in Pilot Activity settings ### Settings PermissionWhat It ControlsCan Manage Airline SettingsActivity settings, basic airline settings, modules, pilot registration/review/transfer, PIREP settings, route settings, SimBrief integrationCan Manage Design SettingsVA branding and visual customisationCan Manage Score and Preset SettingsScoring groups, autoreject rules, point and comment presetsCan Manage ACARS SettingsPegasus ACARS configurationCan Manage Discord Integration SettingsDiscord bot and notification settingsCan Manage Callsign Parameter SettingsVDS callsign configurationCan Manage Airline Share SettingsPilot sharing agreements with other VAsCan Manage API SettingsAPI tokens and webhook configuration ### Data Import and export permissions are granted separately. Enable Can Use Exporters and/or Can Use Importers, then toggle which data types they can access: - Aircraft - Airports - Badges - Containers - Fleet - Hubs - Load Factors - Routes - Routings ### Others PermissionWhat It ControlsCan See Airline StatisticsAccess to VA-wide statisticsCan See StaffView the staff listCan Manage StaffAdd, edit, remove, or restore staff members (requires Can See Staff)Can Manage RanksCreate and edit pilot ranksCan Manage BadgesCreate and edit achievement badgesCan Manage PagesCreate and edit Phoenix pages ## Team Page Staff members appear on the Phoenix Team Page unless marked as hidden. The order of staff on the team page can be changed by dragging rows in the staff list. For each visible staff member, pilots see: - Staff avatar (or default if none set) - Name - Title - Staff email (if provided) ## Managing Staff ### Removing Staff Click the delete icon next to a staff member to remove them. This: - Revokes their Orwell and Hangar access - Removes them from the Team Page - Removes their staff honorary rank if one was automatically assigned The VA owner and vAMSYS staff cannot be removed. ### Restoring Staff Use the filters to show deleted staff, then click the restore icon. Restoring a staff member: - Restores their previous permissions - Re-adds them to the Team Page (unless hidden) - Restores their staff honorary rank if applicable ### Changing Owners Owner of the Virtual Airline can transfer said ownership to another member of VA Staff: - New VA Owner needs to be a member of staff in the VA with the permissions configured in Orwell - Current VA Owner needs to create a helpdesk ticket (Orwell -> vAMSYS Support) asking Team vAMSYS to transfer ownership to a different person. Email should include VA Identifier (available from Orwell Dashboard) and email address of the new owner. Email address needs to match the address of the user which has the pilot and staff access in your VA. - New VA Owner needs to create a helpdesk ticket as well confirming they are taking ownership and billing responsibilities - ticket needs to be created from the email address provided by the current VA Owner and needs to include VA Identifier as well. - Once ownership is changed, both parties will receive an email confirming the change. As part of owership change, any billing details provided by the previous owner will be automatically deleted. ## Tips - Create role templates mentally - Common roles like "Route Manager" or "PIREP Reviewer" need specific permission combinations. Document your standard roles. - Use Airport Manager assignment - For route managers at specific hubs, assign them as Airport Manager and give Can Manage Routes (without Can Manage All Routes). - Hidden staff for backend roles - Use the hidden flag for staff who handle backend operations but should not appear on the public team page. - Staff honorary rank - Consider creating a Staff Team honorary rank and configuring it in your VA settings to automatically assign to staff members. ## Related - Ranks - Configure ranks including honorary ranks for staff - Pilot Registration - Pilot Invites for adding team members during setup --- # Phoenix Dashboard Editor Customise the pilot dashboard layout with statistics, activities, flight maps, and social links. The Phoenix Dashboard is the first page pilots see when they log in. Customise it to show the information most relevant to your VA - from statistics and activities to custom images and quick action buttons. ## Accessing the Dashboard Editor In Orwell, go to Pages → Phoenix Dashboard. You need the View Pages permission. ## Layout System The dashboard uses a row-based layout. Each row contains width blocks, and each block contains components. ### Width Blocks Block TypeUsageFullSingle component spanning the entire widthHalfTwo components side by sideThirdThree components in a rowQuarterFour narrow componentsTwo ThirdsPaired with a Third block for 2:1 layouts Mix block types within a row - for example, one Third block and one Two Thirds block create an asymmetric layout. ### Components Each component has a width setting (25%, 33%, 50%, 66%, or 100%) controlling how much space it takes within its block. Leave at 100% unless combining multiple components in a single block. Each component also has a Hidden toggle. Hidden components are not displayed to pilots but preserve all their configuration — size, position, and settings. This makes it easy to seasonally enable or disable dashboard sections without re-entering settings. ## Available Components ### Content Components ComponentDescriptionTextRich text with basic formatting (bold, italic, lists, links). Optional "Wrap in Card" for a bordered appearance.ImageUpload an image with optional dark mode variant. Can link to a URL and open in same or new tab.ButtonsQuick action buttons for Booking, Events, and PIREPs. Add custom buttons with any URL. ### Statistics Components ComponentDescriptionPilot StatisticsThe logged-in pilot's stats (flights, hours, distance) with time period tabs.Pilot Statistics (Slim)Compact version of pilot statistics.Airline StatisticsVA-wide statistics for recent periods (today, 24 hours, 30 days, year to date). ### Activity Components ComponentDescriptionAlertsDisplays active alerts. No configuration needed.NOTAMsPaginated NOTAM list. Configure entries per page (5, 10, or 15) and optionally show only when pilot has unread NOTAMs.EventsSlideshow of current activities. Filter by activity type or tags. Show all, random, or first only.Event (Single)Display a specific activity by selecting it from a dropdown.Event (Ordinal)Display the first, second, third, etc. activity from the list. Useful for predictable positioning with multiple activities.Community Goal/ChallengeProgress bar for active community goals or challenges. Hides automatically when none are active. ### Flight Components ComponentDescriptionPIREP and Booking BoxesCards showing active flight, current bookings, and recent PIREPs. Configure which to show, how many items, and which data fields appear in each box.Flight MapLive map showing active flights. Set a minimum height when used in a Full block.Flight ListList of active flights with optional hiding of past flights. ### Configuring PIREP and Booking Boxes The PIREP and Booking boxes can be fully customised. In the Dashboard Builder, expand the PIREP and Booking Boxes component to access these settings. #### Airport Identifier Format Controls how airports are displayed in the middle row of both PIREP and Booking boxes. OptionExampleICAO onlyEGLLIATA onlyLHRBoth ICAO & IATAEGLL/LHR #### Header Items Choose up to two items for the top-left of each box. PIREP boxes can show PIREP ID, Callsign, or Flight Number. Booking boxes can show Booking ID, Callsign, or Flight Number. When two items are selected, they are separated by a divider. #### Bottom Row Data Each box has three bottom row slots that can be set independently. Set a slot to "None" to leave it empty. PIREP box options: Flight Time, Points (Combined), Regular Points, Bonus Points, Landing Rate (FPM), Landing Rate (G), Landing Rate (FPM + G), Distance Flown, Aircraft Reg, Aircraft Type, Network. Booking box options: Departure Time, Arrival Time, Aircraft Reg, Aircraft Type, Flight Number, Callsign, Flight Length, Flight Distance. Hovering over a bottom row value shows a descriptive label in a popover. **Backward Compatible**: All box configuration settings default to the current layout. Existing dashboards are unaffected until you change the configuration. ### Social Component ComponentDescriptionSocial IconsDisplays your social media icons. Configure icons in Settings → Social Icons. ## Social Icons Social icons link to your external communities (Discord, Facebook, Instagram, forums, etc.). ### Configuring Social Icons In Orwell, go to Settings → Social Icons. You need the View Design Settings permission. Each social icon has: FieldDescriptionNameDisplay name shown in the Community navigation menuIconFontAwesome icon (e.g., brands.facebook, brands.discord, light.globe)URLThe link destinationImageBanner image shown in the Dashboard component (recommended: 200 x 50 pixels)Image - Dark ModeOptional dark mode variant of the image ### Display Options OptionWhere It AppearsShow in Phoenix DashboardDisplays the image in the Social Icons dashboard componentShow in Community Navigation MenuAdds a text link under Phoenix → CommunityDiscord Icon? Enable IntegrationTriggers automatic Discord join (only visible if Discord is configured) ### Discord Integration If you've configured Discord integration for your VA, enabling "Discord Icon? Enable Integration" on a social icon makes it a one-click Discord join button. Instead of opening a URL, it automatically adds the pilot to your Discord server (with their consent). ## Restoring Defaults Click Default Config at the top of the dashboard editor to restore the default layout. This replaces your current configuration entirely - there is no undo. ## Layout Best Practices ### Understanding Rows and Columns The dashboard is built row by row, but within each row, width blocks create columns. Think of it like a spreadsheet: - A row is a horizontal band across the page - Width blocks divide that row into columns - Components fill those columns ### Stay Consistent The most common layout mistake is inconsistency. If you choose a two-column layout, commit to it: - Don't overload one column - piling components into one side while the other sits empty creates visual imbalance - Don't start new rows prematurely - breaking into single Full-width blocks disrupts the rhythm - Pair components thoughtfully - components have different heights, so similar-height components work better side by side ### Start from the Default The default dashboard configuration is reasonably proportioned and demonstrates good layout principles. Rather than building from scratch: 1. Click Default Config to see a working layout 2. Make incremental changes 3. Preview often to check balance For custom layouts, expect to experiment. There's no formula - you'll need to try different combinations until the proportions feel right. ## Tips - Flight Map pairs well - Use a Two Thirds + Third layout with Flight Map alongside Events or a custom image. - Test both themes - Preview your dashboard in light and dark modes to ensure images and colours work in both. - Use ordinal events for predictability - If you always want your main event in the same position, use Event (Ordinal) instead of Events. - Set map heights in full blocks - The Flight Map needs a minimum height when placed in a Full width block, otherwise it may not display. - Social icon images vs icons - The FontAwesome icon appears in navigation; the uploaded image appears on the dashboard. Design both for their context. --- # Bookings Monitor active and completed flight bookings, cancel bookings, and export VATSIM compliance reports. The Bookings page gives staff a read-only view of all flight bookings in the Virtual Airline. From here you can monitor live and completed flights, view booking details, cancel bookings, and export VATSIM VA Partner compliance reports. ## Accessing Bookings In Orwell, go to Flight Centre → Bookings. You need the Can See Flight Centre - Bookings permission. ## Predefined Views The bookings table has four predefined views to quickly filter what you see: ViewWhat It ShowsDefault (Live)Active bookings — in progress or booked for the future. No PIREP filed, not cancelled.Complete & CancelledBookings that resulted in a PIREP or were cancelled by the pilot, staff, or system.Complete with PIREPOnly bookings that have a PIREP filed against them.Online BookingsAll bookings where the network is not Offline (VATSIM, IVAO, etc.). ## Table Columns The table shows key booking information by default. Use the column toggle to show or hide additional columns. Default columns: ID, Route ID, Pilot Username, Pilot Name, Fleet Code, Callsign, Departure, Arrival, Network. Additional columns: Fleet Name, Aircraft Registration, SimBrief OFP, Departure Stand, Arrival Stand, Flight Number, Altitude, Cost Index, Departure Time, Arrival Time, Type, Passengers, Cargo, Created, Cancelled, Valid To, Has PIREP. ## Filtering Beyond the predefined views, the table supports advanced filtering: - Live / Cancelled toggle — switch between active bookings, cancelled/completed, or both - Date filter — filter by cancellation/completion date - Column search — search by callsign, flight number, departure, arrival, or network ## Viewing a Booking Click the view icon on any booking to see its full details. The booking view displays: - Booking details — departure/arrival airports, callsign, flight number, passengers, cargo, type, network, altitude, cost index, booking time, and cancellation time - Pilot information — username, full name, rank, registration date - Aircraft — registration, name, fleet code, fleet name - Route — route ID, route callsign, route flight number - Network Connections — for bookings flown on VATSIM with a PIREP filed, shows detected network connections including callsign, flight plan status, departure/arrival, and connect/disconnect times ## Actions The booking view header provides quick actions: ActionDescriptionCancel BookingCancels the booking and all subsequent bookings by the same pilot. Only available for live bookings. Blocked if the pilot has position reports within the last 5 minutes (still actively tracking).View PilotOpens the pilot's Orwell profile page.View PIREPOpens the associated PIREP review page. Only shown when a PIREP exists for this booking. **Booking Expiry**: Bookings automatically expire after a validity period (default 24 hours). You can change this at **Settings → Booking & Dispatch**. Diversions can have a separate, shorter validity period. ## Booking Types Each booking has a type copied from the route it was booked on: - Scheduled, Cargo, Charter, Training, Repositioning, VFR, Jumpseat ## VATSIM VA Partner Compliance Export VATSIM requires Virtual Airline Partners to demonstrate a minimum level of activity. The compliance export produces a privacy-conscious CSV with the minimum data required for verification. Click VATSIM VA Partner Compliance Export in the table header to generate the report. The export: - Covers the last 90 days - Targets 60 flights from 20 or more different pilots - Only includes flights made on VATSIM with a filed PIREP - Validates that pilots were connected to the VATSIM network for at least 50% of flight duration - CSV contains only: Pilot ID, Callsign, Departure ICAO, Off-Blocks Time, Arrival ICAO, Landing Time **VATSIM ID Required**: For flights to appear in the export, pilots must have their VATSIM ID entered in their User Settings. Without it, network connectivity cannot be verified. ## Webhooks Bookings trigger webhook events if configured: - booking.created — fired when a pilot makes a new booking - booking.cancelled — fired when a booking is cancelled (by pilot, staff, or system expiry) ## Related - PIREPs — review PIREPs filed against bookings - Liveries — approve or reject aircraft liveries detected during flights --- # Liveries Review and approve aircraft liveries detected during flights to ensure pilots fly the correct aircraft type. Livery Management is a quality control system that ensures pilots fly the correct aircraft type. When Pegasus ACARS detects an aircraft paint scheme during a flight, it creates a livery record. Staff review these liveries and approve, reject, or ignore them. A badge on the navigation item shows the count of pending liveries. ## Accessing Liveries In Orwell, go to Flight Centre → Liveries. You need the Can Manage Liveries permission. ## How Liveries Are Created Livery records are created automatically during PIREP processing — staff do not create them manually. When a pilot files a PIREP through Pegasus ACARS, the system detects the aircraft livery name and checks it against existing records. If no match is found, a new livery record is created with a pending status. **Prerequisites**: For livery review to work, both the **Livery Name** and **Rejected Livery Rejector** AutoReject rules must be enabled in **Settings → Rewards**. Without these, liveries are not tracked. ## Livery Statuses StatusColourMeaningNewGreyNot yet reviewed. Future uses flag PIREPs for review.AcceptedGreenApproved by staff. Future uses will not trigger review.RejectedRedRejected by staff. Future uses trigger the Rejected Livery Rejector AutoReject.IgnoredBlueMarked as ambiguous. Future uses still flag PIREPs for review. ## Tabs and Filtering The livery table has five tabs: - Pending — liveries awaiting review (default when pending exist, badge shows count) - Accepted — approved liveries - Rejected — rejected liveries - Ignored — ignored liveries - All — all liveries regardless of status Additional filters are available for fleet, status toggles, and the user who last changed the livery status. ## Table Columns The table shows key livery information: ColumnDescriptionNameThe livery name as detected by PegasusFleet CodeThe fleet type this livery belongs toTypeDetected aircraft type code (e.g. B738)AircraftDetected aircraft name from the simulatorAddonDetected addon package or developer (e.g. PMDG)SimulatorWhich simulator was used (MSFS 2020/2024, X-Plane 12, etc.)PIREPsNumber of PIREPs that have used this liveryStatusCurrent review status (New, Accepted, Rejected, Ignored) ## Review Actions Livery review can be done directly from the table row actions or from the livery detail page: ActionEffectEffect on Pending PIREPsAccept LiveryMarks as approved. Future uses pass without review.PIREPs pending only for this livery are auto-accepted.Reject LiveryMarks as rejected. Future uses trigger the Rejected Livery Rejector AutoReject.No change to pending PIREPs.Reject (Reject PIREPs)Same as Reject Livery.PIREPs pending only for this livery are rejected.Reject (Invalidate PIREPs)Same as Reject Livery.PIREPs pending only for this livery are invalidated.Ignore LiveryMarks as ambiguous. Future uses still flag PIREPs for review. Supports an internal note.No change to pending PIREPs. **Reject vs Reject & Invalidate PIREPs**: Whether you see "Reject PIREPs" or "Invalidate PIREPs" depends on your Rejected Livery Rejector AutoReject configuration. The action label matches the rule's configured action. ## PIREP Auto-Processing Rules When a livery action affects pending PIREPs, the system applies these rules: - Only PIREPs in the Awaiting Review state are affected - PIREPs where the pilot has already commented are skipped — they need manual review - PIREPs with multiple other AutoReject failures are skipped when accepting — the PIREP needs review for other reasons - Each affected PIREP gets a staff action log entry noting the change was made via Livery Review ## Livery Detail View Click any livery to see its full details: - Livery information — name, fleet code, fleet name, detected aircraft name, type, addon, status, timestamps - Internal note — markdown-formatted staff note (editable from the detail view) - Review actions — same approve/reject/ignore actions as the table - PIREP history — table of all PIREPs that have used this livery, with links to their review pages - Next Pending Livery — header button to quickly navigate to the next unreviewed livery ## Bulk Actions Select multiple liveries using checkboxes to perform bulk actions. All require confirmation: - Accept Livery — bulk approve selected liveries - Reject Livery — bulk reject without affecting PIREPs - Reject (Reject/Invalidate PIREPs) — bulk reject with PIREP processing - Ignore Livery — bulk ignore with optional internal note **Liveries Are Per-Fleet**: The same livery name on different fleet types creates separate records. For example, "British Airways" on a B738 fleet and "British Airways" on an A320 fleet are two different livery records that need to be reviewed independently. ## Typical Workflow 1. A pilot flies a flight with Pegasus ACARS 2. The system detects the livery name and creates a record if it's new 3. The Livery Name AutoReject flags the PIREP for review 4. Staff check the fleet code, aircraft type, and addon to confirm the correct aircraft was used 5. Staff accept the livery — the PIREP is automatically accepted if no other issues exist 6. Future flights with the same livery and fleet pass without review ## Webhooks Livery events trigger webhooks if configured: - livery.created — new livery record detected during PIREP processing - livery.updated — livery status changed (accepted, rejected, or ignored) - livery.deleted — livery record removed ## Related - PIREPs — review PIREPs that may be affected by livery decisions --- # PIREPs Review, accept, reject, and manage pilot reports filed through Pegasus ACARS or as manual claims. PIREPs (Pilot Reports) are how pilots earn hours and points towards rank progression and activity completion. The PIREP Management page is where staff review, accept, reject, or adjust PIREPs. A badge on the navigation item shows the count of PIREPs awaiting review. ## Accessing PIREPs In Orwell, go to Flight Centre → PIREPs. You need the Can Manage PIREPs & Claims permission. ## PIREP Sources PIREPs are created through several channels: - Pegasus ACARS — automatically filed when a pilot completes a tracked flight - Claims — manually filed by pilots for flights not tracked by Pegasus (must be enabled in Settings → vAMSYS Modules) - Transfer PIREPs — created via Pilot Invite or Rank Transfer to credit previous hours ## PIREP Statuses StatusColourMeaningProcessingBluePIREP is being processed or scored by the systemAcceptedGreenPIREP passed all checks or was accepted by staff. Hours and points awarded.Awaiting ReviewYellowPIREP failed one or more AutoReject rules and needs staff review.RejectedRedPIREP was rejected by staff. Pilot receives credited time but no points.InvalidatedRedPIREP was invalidated by staff. Pilot receives no time and no points. ## Predefined Views ViewDescriptionPending ReviewPIREPs awaiting staff review that are not waiting for a pilot reply. Default view when pending PIREPs exist. Badge shows count.Awaiting PilotPIREPs flagged as Reply Needed — waiting for the pilot to comment before further action. Badge shows count.AllAll PIREPs regardless of status. Default view when no pending PIREPs exist. ## Review Actions When reviewing a PIREP, staff have the following actions available: ActionEffectAccept PIREPPIREP passes review. Hours and points are awarded as listed.Reject PIREPPIREP is marked as rejected. Pilot only receives credited time, no points.Invalidate PIREPPIREP is marked as invalidated. Pilot receives no time and no points.Reprocess PIREPSends the PIREP back through the processing pipeline. The landing rate is cleared so it can be re-evaluated.Mark Reply NeededFlags the PIREP so the pilot must leave a comment before they can book and fly additional flights. Can only be set when the PIREP is in the Awaiting Review state. PIREPs left unanswered beyond the airline's PIREP Reply Window are automatically invalidated.Next Pending PIREPNavigates to the next PIREP awaiting review. **Activity Counting**: Rejected and invalidated PIREPs may still count towards activity progress depending on your VA's Activity Settings. ## Review Page Layout Clicking a PIREP opens the review page with a two-column layout. The left column (two-thirds width) shows flight data and visualizations. The right column (one-third width) shows review tools, communication, and metadata. All panels load lazily for performance. ### Left Column — Flight Data #### Status Panel Always shown at the top of the review page. Displays: - Status badge — colour-coded PIREP status (see PIREP Statuses table above). Claims show an additional "Claim" badge. - Pilot information — username, full name, and rank. A "View Pilot" link opens their profile in a new tab. - Reply Needed flag — displayed when the PIREP has been marked as requiring a pilot reply before further action. - AutoReject violations — for ACARS PIREPs only. Lists which AutoReject rules were triggered, displayed in a red warning box. - Claim message — for claims only. Shows the message the pilot submitted when filing their claim. - Touchdown selection warning — shown when multiple touchdowns were detected and none has been selected yet. Staff must select a landing before accepting or rejecting. #### Landing Rate Selection Shown only when Pegasus detected multiple touchdowns during landing and no touchdown has been selected yet. Each detected touchdown is displayed as a selectable card showing: - Rate — vertical speed in feet per minute (FPM) - G-force — impact force at touchdown - Time — when the touchdown occurred - Gear status — whether landing gear was down - Pitch and Roll — aircraft attitude in degrees - Speed — groundspeed at touchdown in knots - Runway — detected runway identifier - LDA — Landing Distance Available in feet Staff select a touchdown and click Save Selection. Once selected, the PIREP's landing rate and G-force are updated and the pilot's statistics are recalculated. **LDA Availability**: LDA (Landing Distance Available) requires runway data from the vAMSYS database. If the runway cannot be identified, LDA will not be shown. #### Proof of Flight Shown for claims only. Displays the evidence the pilot provided when filing their claim: - Uploaded images — displayed as thumbnails with links to full-resolution versions - External links — URLs provided by the pilot, shown with their domain name #### Visualisations Shown for ACARS PIREPs only (not available for claims). A multi-tab panel where each tab can be toggled independently — Map, Departure, Flight, and Approach. Tab state is remembered in your browser. Map — displays the flight path colour-graded by altitude with a planned route path overlay. Flight Chart — plots altitude (ft) and groundspeed (kts) over time. Supports zoom (scroll), pan (drag), and area select (shift+drag). Colour-coded event annotations can be toggled by category: - Pushback events (indigo) - Engine starts/stops (amber) - Flap changes (cyan) - Touchdowns (green) - Gear changes (orange) - Stability gates (purple) Clicking an event in the legend scrolls the chart to that event and highlights it. Departure Analysis — detailed departure performance data. Requires position reports, a detected liftoff event, and a matchable runway. Shows: - Detected runway — identifier, bearing, and coordinates of the departure runway - Liftoff metrics — pitch, max pitch, roll, speed, rejected takeoff count, altitude AGL, distance from threshold - Climb profile — altitude plotted against distance and time for the first 5 minutes after liftoff - Performance metrics — runway utilisation (feet used, percentage, remaining distance), climb gradient (ft/NM), climb rate (FPM), centreline tracking (max and average cross-track deviation) - Departure events — gear retraction and flap changes during climb-out **Departure Analysis Availability**: Departure Analysis is unavailable when: (1) there are no position reports (claims), (2) Pegasus did not detect a liftoff event, or (3) the aircraft heading at liftoff does not match any runway within 15 degrees — which can happen if the aircraft was not aligned with a runway, wind caused significant drift, or airport runway data is missing from the vAMSYS database. Approach Analysis — detailed approach and landing performance data. Requires position reports, a runway identifier in the touchdown data, and that runway being found in the vAMSYS database. Shows: - Approach profile — data for the final 15 NM: altitude MSL and AGL, distance from threshold, ideal glideslope (3 degrees with threshold crossing height), glideslope deviation in feet and dots, cross-track error, groundspeed, and heading - Landing report — data at altitude gates (2000ft, 1000ft, 500ft, 200ft, 100ft, 50ft, touchdown): airspeed, vertical speed, pitch, roll, and gear status - Flare analysis — sink rate at 50ft vs touchdown, sink arrest percentage, pitch increase, and quality assessment (Excellent, Good, Fair, or Poor) - Touchdown data — rate, G-force, distance from threshold (feet and percentage), runway remaining, pitch, roll, speed, rollout distance, and assessment (Short, Early, Good, or Long) - Runway path visualisation — overhead view of the approach path relative to the runway centreline **Approach Analysis Availability**: Approach Analysis is unavailable when: (1) there are no position reports (claims), (2) the touchdown data does not contain a runway identifier, or (3) the runway is not found in the vAMSYS database. Without runway data, LDA and distance-from-threshold metrics cannot be calculated. #### Flight Details Always shown, but the available fields differ significantly between ACARS PIREPs and claims. For ACARS PIREPs, the panel displays comprehensive flight data grouped into the following sections: Identity and Aircraft — callsign, flight number, flight type, network (if applicable), aircraft registration with link to aircraft management, fleet name with link to fleet management, and livery details (name, approval status with link to livery management). Event Timeline — a comparison table showing times for each flight phase. Columns adapt based on available data: - Actual — off blocks, takeoff, landing, on blocks (always shown) - Route — scheduled departure and arrival times from the route definition, with derived takeoff/landing using average taxi times from airport analytics - Estimated — SimBrief Out, Off, On, In times (only when dispatched via SimBrief) - Booked — departure and arrival times from the booking, with derived takeoff/landing Each column includes a delta showing early, on-time, or late against actuals. Duration rows between events show taxi out, airborne time, taxi in, and total block time with their own deltas. Night flight indicators (sun/moon icons) appear next to takeoff and landing times. Tracking and Time Summary — tracking start and end times, awarded (credited) time, paused air time, paused ground time, and total paused time. A warning is shown if the paused percentage exceeds 5%. Performance (ACARS only) — shown below the timeline. When dispatched via SimBrief, displays a comparison grid with Actual, Estimated, and Delta rows for: - Distance — flight distance vs SimBrief air distance (NM) - Average Groundspeed — calculated vs SimBrief estimated (kts) - Weights — ZFW, TOW, and LDW vs SimBrief estimates (shown in the pilot's preferred unit: kg or lbs) Without SimBrief, these values are shown in a simple grid without comparison rows. Fuel (ACARS only) — shown in the pilot's preferred unit (kg or lbs). With SimBrief: a comparison grid showing Actual, Estimated, and Delta for ramp fuel, takeoff fuel, fuel used, landing fuel, and fuel flow per hour. Without SimBrief: a simple grid of the same values without comparison. Touchdown (ACARS only, when touchdown data exists) — rate (FPM), G-force, runway, touchdown point (distance from threshold in feet and percentage), LDA, rollout distance, speed, pitch, and roll. For claims, only basic information is shown: callsign, flight number, aircraft, fleet, and livery. All operational flight metrics (timeline, performance, fuel, touchdown) are hidden since no tracking data is available. **SimBrief Integration**: When dispatched via SimBrief, the Flight Details panel gains additional "Estimated" columns comparing actual performance against the SimBrief flight plan. This includes estimated times, fuel, weights, and distances — giving a complete actual-vs-planned analysis. #### Dispatch Panel Always shown. Displays the dispatch configuration for the flight: - Cost index — the cost index used for flight planning - FL / Altitude — planned cruise altitude, formatted as a flight level (e.g. FL350) when applicable - Passengers — number of passengers on board - Freight — cargo weight in kg or lbs based on pilot preference - Luggage — luggage weight in kg or lbs - Containers — if applicable, an expandable section showing each container with its name, type, notes, unit size, unit weight, quantity loaded, and total weight. Links to container management. When the flight was dispatched via SimBrief, a SimBrief OFP button appears in the panel header, linking to the Operational Flight Plan PDF download. **SimBrief OFP**: The SimBrief OFP (Operational Flight Plan) is available as a PDF download when the flight was dispatched via SimBrief. The PDF is available for at least 30 days after dispatch. #### Flight Data Logs Shown for ACARS PIREPs only. A filterable log of all events recorded by Pegasus during the flight. Each log entry shows: - Timestamp — when the event occurred - Message — description of the event - Type label — category of the event - Departure offset — time relative to departure (+/- HH:MM) - Arrival offset — time relative to arrival (+/- HH:MM) - Flight phase — Init, Ground (Departure), Departure, Enroute, Arrival, Landing, Ground (Arrival), or Other Events can be filtered by flight phase using the grouped filter buttons. ### Right Column — Review Tools #### Internal Notes Always shown. Staff-only notes attached to this specific PIREP — not visible to pilots. Useful for recording exceptions, observations, or internal decisions about a flight. Notes can be edited at any time. #### Pilot Notes Always shown. Staff-only notes attached to the pilot rather than the PIREP — they appear on every PIREP from this pilot. Useful for tracking warnings, special circumstances, or ongoing issues. Staff can add and delete individual notes. See Pilots — Pilot Notes for full details on managing pilot notes. #### Comments Always shown. Two-way communication channel between staff and the pilot. - Staff can use comment presets to quickly insert standard responses - The Hide Name option lets staff post comments without revealing their identity to the pilot - Reply Needed toggle blocks the pilot from booking new flights until they reply. If the pilot never replies, the PIREP is automatically invalidated after the airline's PIREP Reply Window (default 7 days) — the PIREP's action log records the auto-invalidation and the booking block is lifted immediately - When either party adds a comment, the PIREP returns to the review queue - Comments are disabled on rejected or invalidated PIREPs when the corresponding appeal setting is enabled in PIREP Settings #### Time Always shown, but content differs between ACARS and claims. For ACARS PIREPs, displays: - Awarded (credited time) — prominently displayed in the centre, this is the time that will be awarded to the pilot - Airborne — time from takeoff to landing - Block — time from off-blocks to on-blocks - Scheduled — expected time from the route definition - Estimated — expected time from the booking - Paused times — air paused, ground paused, and total paused. A warning highlight appears if paused time exceeds 5%. Staff can click Edit to adjust airborne time, block time, paused air, and paused block. Changes are saved and credited time is recalculated based on the airline's include_taxi_time setting. For claims, only the awarded time is shown (set when the claim was accepted). **Manual Time Edits**: Manual time edits are reset if the PIREP is reprocessed. #### Points Always shown. Displays the point breakdown for the PIREP with two sections: - Flight Scores — individual scoring rule results (each showing name and +/- points) with a flight score total - Bonus Points — additional points from activity completions, manual adjustments, awards, or penalties with a bonus total Staff can click Edit to open a modal where both flight scores and bonus points can be modified. Presets can be applied to quickly add standard point adjustments to both sections. Individual score entries can be added, removed, or renamed. **Manual Point Edits**: Manual point edits are reset if the PIREP is reprocessed. #### Previous Claims Shown for claims only, when the pilot has previous claim history. Displays recent claims from the same pilot showing each claim's PIREP ID, date, and status. Useful for spotting patterns in claim frequency or legitimacy. #### Route Always shown. Displays route information for the flight: - Airports — departure and arrival airports with links to airport management - Flight identification — callsign and flight number - Company route vs pilot route — if the pilot's filed route differs from the company route, both are shown - Route remarks — any notes attached to the route - Scheduled times — departure and arrival times with duration #### METAR Always shown. Displays historic weather data: - Departure METAR — weather at the departure airport at the time of departure - Arrival METAR — weather at the arrival airport at the time of landing #### Activity Logbooks Shown when the PIREP contributes to one or more activities. Displays which activities (tours, events, challenges) this PIREP counts towards, including tour leg information where applicable. #### Staff Actions Always shown. A complete, immutable audit trail of every staff action taken on this PIREP. Shows who performed each action, what they did, and when. This log cannot be edited or deleted. **Reprocessing Resets Manual Edits**: Reprocessing a PIREP will reset any manual point or time edits you have made. Only reprocess when necessary. ## ACARS vs Claims Comparison The review page adapts based on whether the PIREP was filed via Pegasus ACARS or as a manual claim. Claims lack flight tracking data, so staff review based on the pilot's submitted proof and historical averages. - ACARS only — Visualisations (Map, Flight Chart, Departure Analysis, Approach Analysis), Flight Data Logs - Claims only — Proof of Flight, Previous Claims - Both but different content — Status Panel (ACARS shows AutoReject violations; claims show claim message), Flight Details (ACARS shows full metrics with timeline, performance, fuel, and touchdown; claims show only basic identity and aircraft info), Time (ACARS shows full breakdown with edit; claims show only awarded time) - Both with same content — Dispatch, Internal Notes, Pilot Notes, Comments, Points, Route, METAR, Activity Logbooks, Staff Actions ## Reviewing Claims Claims are a special type of PIREP filed manually by pilots for flights not tracked by Pegasus. All claims require manual review — they cannot be auto-accepted. ### Accepting a Claim When you click Accept on a claim, a modal displays computed reference data to help you set fair time and point values: - Claimed Time — the duration between the pilot's submitted departure and arrival times - Average Route Time — average credited time for completed PIREPs on this specific route. Helps determine if the claimed time is reasonable. - Average Route Points — average points awarded on this route - Average Pair Time — average credited time for all PIREPs between this departure and arrival airport pair, across all routes. Useful when the route is new or has limited history. - Average Pair Points — average points for the same airport pair **Averages May Not Display**: If there is insufficient data (few or no completed PIREPs on the route or airport pair), averages may show as 00:00 or 0. In these cases, use your airline's standard time and point policies. You must enter the following values: - Hours — 0 to 24 - Minutes — 0 to 60 - Points — optional, defaults to 0 When a claim is accepted, the status changes to accepted, credited time is set to the entered hours and minutes, points are set to the entered value, activity progress is recalculated for any tours, events, or challenges, and the pilot's total hours and points are updated. Accepted claims can still be rejected later, and rejected claims can be accepted. Claims do not trigger automated scoring rules since they lack flight data — all time and point values are set manually by staff. ### Rejecting a Claim Rejecting a claim awards no points and no hours. Rejected claims may still count towards activity requirements depending on your VA settings. **Enabling Claims**: Claims must be enabled at **Settings → vAMSYS Modules**. You can add a custom claim message to set out your requirements for pilots. ## Bulk Actions Select multiple PIREPs using the checkboxes to perform bulk actions. All bulk actions require confirmation. ActionDescriptionBulk Accept PIREPsAccept all selected PIREPs (excludes claims and already accepted PIREPs)Bulk Reject PIREPsReject all selected PIREPs (excludes claims and already rejected PIREPs)Bulk Reject ClaimsReject all selected claims (excludes non-claims and already rejected claims)Bulk Invalidate PIREPsInvalidate all selected PIREPs (excludes claims and already invalidated PIREPs)Bulk Reprocess PIREPsReprocess all selected ACARS-filed PIREPs (skips claims, transfers, and non-ACARS PIREPs) ## Comments System The comments panel enables two-way communication between staff and pilots on a PIREP. - Staff can use comment presets to quickly insert standard responses - The Hide Name option lets staff post without showing their name - When either party adds a comment, the PIREP returns to the review queue - Comments are disabled on rejected PIREPs if Rejected PIREP Appeal is enabled in PIREP Settings, and likewise for invalidated PIREPs ## Notes: Internal vs Pilot TypeScopeVisible ToBest ForInternal NotesPer PIREPStaff onlyRecording exceptions, observations about a specific flightPilot NotesPer PilotStaff onlyWarnings, special circumstances, or ongoing issues with a pilot ## Staff Actions Audit Trail Every action taken on a PIREP is logged in the Staff Actions panel. This includes who performed the action, what they did, and when. Tracked actions include: accepting, rejecting, invalidating, reprocessing, landing rate selection, comment creation/deletion, point and time edits, internal note changes, and reply needed toggles. ## Table Columns Default columns: PIREP ID, Pilot Name, Username, Callsign, Departure, Arrival, Landing Rate, Points, Bonus Points, Status. Additional columns: Flight Number, Aircraft Registration, Fleet Name/Code, Livery, Booking Type, Route Tag, G-Force, Credited Time, Network, Simulator, Reply Needed, Created. ## Filtering The table supports advanced filtering by: - Created date — filter by when the PIREP was filed - Status — complete, accepted, failed, rejected, or invalidated - Departure / Arrival airport — filter by airport codes ## Related - Bookings — view the bookings that generated PIREPs - Liveries — approve or reject aircraft liveries that may affect PIREP status - Presets — create reusable comment and point macros for PIREP review - Pilots — manage pilot accounts, view statistics, and maintain pilot notes --- # Scoring Groups Create and manage scoring groups that bundle scoring rules for specific fleets, controlling how PIREPs are scored. Scoring Groups are containers that bundle scoring rules together for specific fleets. Each fleet can be assigned to one scoring group, and one scoring group can apply to multiple fleets. When a PIREP is filed, vAMSYS looks up the fleet's scoring group and evaluates all its configured rules to calculate the pilot's score. Without a scoring group, PIREPs from a fleet receive no point scoring. ## Accessing Scoring Groups In Orwell, go to HQ → Rewards → Scoring Groups. You need the Can See Score Settings permission. ## How Scoring Groups Work The scoring system is built on a simple hierarchy: 1. Your airline creates scoring groups — for example "Narrow Body", "Wide Body", "Turboprop" 2. Each scoring group has its own set of enabled scoring rules with customised parameters 3. Each fleet is assigned to one scoring group (or none) 4. When a PIREP is filed, the system looks up the fleet's scoring group and evaluates all its rules This design lets you tailor scoring to different aircraft types. A turboprop fleet might have simpler engine rules, while a widebody fleet could have strict engine start sequences and fuel management scoring. **Not Retroactive**: Changes to scoring rules and groups are not retroactive. Edits only affect PIREPs filed or reprocessed after the change. ## Creating a Scoring Group A scoring group only has one field: - Name — required, maximum 240 characters. This name is shown to pilots on the Phoenix Scores page. Once created, you configure the group by adding scoring rules and associating fleets. ## List View The scoring groups list displays: ColumnDescriptionIDDatabase identifierGroup NameThe scoring group name (sortable)Applicable FleetsFleets assigned to this groupEnabled Scoring RulesCount of rules configured in this group ## Editing a Scoring Group The edit page has two tabs: Scoring Rules and Fleets. ### Scoring Rules Tab This tab lets you add and manage the scoring rules for this group. Click the add button to select rules from the master list of available scoring rules. Each rule can be customised with: - Name — how the rule appears in the PIREP scorer (staff view) - UI Name — optional override for how the rule appears on the Phoenix Scores page (pilot view). If empty, defaults to Name. - Points — how many points to award (positive) or deduct (negative). Some rules use thresholds instead of a single points value. - Rule-specific parameters — additional configuration fields that vary by rule type Rules can be individually edited or deleted from the group. See Scoring Rules for a complete reference of all available rules and their parameters. ### Fleets Tab This tab shows which fleets currently use this scoring group. Two actions are available: - Associate — assign a fleet to this group. Only fleets not already assigned to any scoring group appear in the list. - Dissociate — remove a fleet from this group. The fleet will no longer receive scoring. **One Fleet, One Group**: A fleet can only belong to one scoring group. If a fleet is already assigned to another group, it won't appear in the associate list. Remove it from the other group first. ## Copying Rules Between Groups A header action on the list page lets you copy all scoring rules from a source group to a destination group. This is useful when creating a new group that should start with a similar configuration to an existing one. **Destructive Action**: Copying replaces all existing rules in the destination group. The source group is not affected. ## Reward Settings At Orwell → HQ → Settings → Reward Settings, you can configure additional scoring behaviour that applies across all scoring groups: - Toggle whether Repositioning, Training, and Charter flights earn time and points - Toggle whether taxi time is included in awarded flight time - Configure bonus points for Airport Managers **Not Retroactive**: Changes to reward settings are not retroactive and only affect PIREPs filed after the change. ## Permissions PermissionGrantsCan See Score SettingsAccess to Scoring Groups and Scoring Rules ## Related - Scoring Rules — complete reference for all available scoring rules and their parameters - PIREPs — review PIREPs where scoring is applied - Fleet — assign fleets to scoring groups - Ranks — configure rank progression based on points - Badges — award badges based on pilot achievements - AutoReject Rules — automatic PIREP rejection criteria --- # Scoring Rules Complete reference for all available scoring rules — from landing rates and engine sequences to fuel management and network connectivity. Scoring rules are the individual evaluations applied to PIREPs within a scoring group. Each rule awards or deducts points based on specific aspects of pilot performance during a flight. Rules are added and configured within a Scoring Group, and you can customise names, points, and rule-specific parameters for each one. Every scoring rule shares three common fields: - Name — how the rule appears in the PIREP scorer (staff view) - UI Name — how the rule appears on the Phoenix Scores page (pilot view). If empty, defaults to Name. - Points — how many points to award (positive) or deduct (negative). Some rules use thresholds instead of a single points value. ## General Scoring Rules ### Starting Points Base points awarded to every PIREP. This is the simplest rule — every filed PIREP gets this score regardless of performance. - Points — integer value awarded ### Step Climb/Descent Points awarded if a step climb or step descent is detected during the flight. This triggers once per PIREP regardless of how many step changes occurred. - Points — integer value awarded ### Multiple Flights Per Day Bonus points for filing multiple PIREPs in a single day (using the VA's configured timezone). Only the highest matching threshold is awarded — thresholds do not stack. PIREPs across all fleets count towards the daily total, not just the fleet using this scoring group. Claims also count. - Thresholds — repeater with the following fields per threshold: - Apply from PIREP # — which flight number triggers this threshold (inclusive, e.g. 2 = second flight onwards) - Name — threshold name shown in the scorer - Points — points to award for this threshold - Apply as Bonus Points — toggle; if enabled, points are added as bonus points instead of regular points ### Rank Points Awards points based on the pilot's current rank at the time the PIREP is processed. - Ranks — repeater with the following fields per entry: - Rank(s) — one or more ranks to match - Points — points to award for pilots holding those ranks - Apply as Bonus Points — toggle; if enabled, points are added as bonus points instead of regular points ## Engine Scoring Rules — Sequence Engine sequence rules check that engines were started in the correct order. Pick the most applicable sequence for the fleets using the scoring group. Only one engine sequence rule can be added per scoring group. Each sequence rule shares these parameters: - Time between engine starts — minimum time that must elapse between each engine start (HH:MM:SS) - Points — base points awarded if the sequence is correct - Penalise Out of Sequence — toggle; if enabled, deducts points when engines are started in the wrong order - Name — how the penalty shows in the scorer - Points — penalty points (negative) - Penalise Insufficient Time — toggle; if enabled, deducts points when the time between starts is too short - Name — how the penalty shows in the scorer - Points — penalty points (negative) Available engine start sequences: RuleEngine Start OrderAny Engine StartedAny engine (base rule)Number 1 First of 21 → 2Number 2 First of 22 → 1Number 1 First, Then 21 → 2Number 1, Then 2, Then 31 → 2 → 3Number 2, Then 1, Then 32 → 1 → 3Number 1, Then 2, Then 3, Then 41 → 2 → 3 → 4Number 1, Then 2, Then 4, Then 31 → 2 → 4 → 3Number 1, Then 3, Then 21 → 3 → 2Number 2 First, Then 3 Dual2 → 3 (dual spool)Number 2, Then 3, Then 1, Then 42 → 3 → 1 → 4Number 3 First of 33 → (others)Number 3, Then 1, Then 23 → 1 → 2Number 3, Then 2, Then 13 → 2 → 1Number 3 First, Then 43 → 4Number 3, Then 4, Then 2, Then 13 → 4 → 2 → 1Number 4, Then 2, Then 1, Then 34 → 2 → 1 → 3Number 4 First, Then 34 → 3Number 4 First, Then 3 Dual4 → 3 (dual spool)Number 4, Then 3, Then 2, Then 14 → 3 → 2 → 1 ## Engine Scoring Rules — General ### Engines Shut Before Filing Points awarded if all engines are turned off before the PIREP is filed. - Points — integer value awarded ### Selected Engine Taxi In Points awarded if selected engines remained running after landing for a minimum duration before the other engines are shut down. This rewards pilots who taxi in on reduced engines to save fuel. - Engines — comma-separated engine numbers (e.g. "1,2") - Time — minimum run time after landing (HH:MM:SS) - Points — integer value awarded ### Selected Engine Taxi Out Points awarded if selected engines remain off during taxi out, with a minimum time between turning on other engines and turning on the selected engines. This rewards single-engine taxi out procedures. - Engines — comma-separated engine numbers - Time — minimum time between starts (HH:MM:SS) - Points — integer value awarded ### Engines Cooled Down Points awarded if engines remain running for the minimum time after landing. This evaluates whether the pilot allowed sufficient engine cool-down time before shutdown. - Minimum Time — required cool-down duration (HH:MM:SS) - Points — integer value awarded ### Engines Not Cooled Down Points deducted if engines are not running for the minimum time after landing. - Minimum Time — required duration (HH:MM:SS) - Taxi Time Aware — toggle; when enabled, ignores the rule if taxi time is less than the minimum time (avoids penalising pilots who parked at a gate near the runway) - Points — integer value (typically negative) ### Engines Warmed Up Points awarded if engines are properly warmed up before takeoff — that is, they have been running for at least the minimum time before the aircraft departs. - Minimum Time — required warm-up duration (HH:MM:SS) - Conditional Warmup — toggle. When enabled, warmup is only required after a long turnaround. If the aircraft has been on the ground for less than the threshold hours, it is assumed the engines are still warm and the points are awarded automatically. - Turnaround Threshold Hours — hours on ground before warmup is required (default: 2.0) - Taxi Time Aware — toggle; ignores the rule if taxi time is less than the minimum time - Points — integer value awarded ### Engines Not Warmed Up Points deducted if engines are not properly warmed up before takeoff. Has the same parameters as Engines Warmed Up. - With Conditional Warmup enabled: short turnarounds (below threshold) receive no penalty, while long turnarounds (at or above threshold) are penalised if warmup time is insufficient. ## Flap Scoring Rules ### Flaps Retracted Before Parking Points awarded if flaps are set to 0 after landing. - Timer Start — when the evaluation begins: "Last Touchdown" or "30kts" - Points — integer value awarded ### Flaps Not Retracted Before Parking Points deducted if flaps are NOT set to 0 after landing. Same parameters as the award variant. ### Hot Weather Flap Exemption Both parking flap scorers (Flaps Retracted Before Parking and Flaps Not Retracted Before Parking) support a hot weather exemption. When the arrival airport temperature exceeds a configurable threshold, an alternative flap range is accepted instead of requiring full retraction. This prevents pilots from being penalised for leaving flaps extended in hot weather, which is a common real-world procedure. - Temperature Threshold (°C) — the minimum arrival temperature in Celsius that triggers the exemption. Default is 30°C. Temperature is read from the arrival airport METAR. - Min Flap Position (Hot Weather) — minimum flap position accepted during hot weather - Max Flap Position (Hot Weather) — maximum flap position accepted during hot weather - Bonus Points — optional bonus points awarded when the hot weather exemption applies (set to 0 to only skip the penalty without awarding extra points). Only available on the Flaps Not Retracted Before Parking scorer. - Bonus Name — optional custom display name for the bonus (only available on the Flaps Not Retracted Before Parking scorer). The flap evaluation type (Level or Human) follows the parent scorer's setting. #### How Temperature Is Determined The system uses the most recent METAR observation for the arrival airport recorded within 6 hours before landing. Only the temperature_celsius value from the METAR is used. If no METAR is available for the arrival airport within this window, the exemption does not apply and normal scoring rules are used — the pilot is neither penalised nor exempted based on hot weather. #### Behaviour Per Scorer - Flaps Retracted Before Parking — if the exemption applies and the flap position is within the hot weather range, points are awarded as if flaps were fully retracted. No separate bonus is awarded. - Flaps Not Retracted Before Parking — if the exemption applies and the flap position is within the hot weather range, the penalty is skipped. If Bonus Points are configured above zero, a bonus score entry is added to the PIREP instead. ### Flaps Set Before Takeoff Points awarded if flaps are set within the specified range before takeoff. - Flap Evaluation Type — "Level" uses simulator-specific numeric positions. "Human" uses consistent flap names like "2", "FULL", "UP", "1+F" that work across simulators. - Minimum Flap / Maximum Flap — range bounds (format depends on evaluation type) - Points — integer value awarded ### Flaps Not Set Before Takeoff Points deducted if flaps are NOT within the configured range before takeoff. Same parameters as the award variant. ### Flaps Set Before Landing Points awarded if flaps are within the specified range before landing. Same parameters as the takeoff variant. ### Flaps Not Set Before Landing Points deducted if flaps are NOT within range before landing. Same parameters as the takeoff variant. ## Flight Length Scoring Rules ### Flight Length Threshold-based scoring on airborne time. Use this to reward or penalise flights of certain durations — for example, awarding more points for longer flights. - Thresholds — repeater with the following fields per threshold: - Name — threshold label - From (inclusive) — minimum airborne time (HH:MM:SS) - To (exclusive) — maximum airborne time (HH:MM:SS) - Points — points to award ### Prep Time Points awarded if the time between tracking start and pushback falls within a specified range. This rewards pilots who take appropriate time to prepare before departure. - From — minimum prep time (HH:MM:SS) - To — maximum prep time (HH:MM:SS) - Points — integer value awarded ### Block Length Threshold-based scoring on block time (off blocks to on blocks). Uses the same threshold format as Flight Length. ## Takeoff Scoring Rules **Pegasus v2 Only**: These rules require Pegasus ACARS version 2. ### Liftoff Pitch Within Range Points awarded if the maximum pitch angle at liftoff is within the configured range. - Min Degrees / Max Degrees — acceptable pitch range - Points — integer value awarded ### Liftoff Pitch Outside Range Points deducted if the maximum pitch angle at liftoff falls outside the configured range. Same parameters as the award variant. ### Liftoff Roll Within Range Points awarded if the roll angle at liftoff is within the acceptable range. - Max Degrees — maximum acceptable roll magnitude - Points — integer value awarded ### Liftoff Roll Outside Range Points deducted if the roll angle at liftoff exceeds the maximum. Same parameters as the award variant. ### Takeoff Weight Within MTOW Points awarded if the takeoff weight is within the Maximum Takeoff Weight tolerance. The MTOW used is from SimBrief (planned weight), not the aircraft's structural limit. - Weight Source — SimBrief (planned) or Structural - Bound Check — Both (over and under), Upper Only, or Lower Only - Over Tolerance (kg) — allowance above MTOW - Under Tolerance (kg) — allowance below MTOW - Points — integer value awarded ### Takeoff Weight Outside MTOW Points deducted if the takeoff weight falls outside the MTOW tolerance. Same parameters as the award variant. ## Landing Scoring Rules ### Graduated Landing (FPM) Threshold-based scoring on landing rate in feet per minute. Most Virtual Airlines use this as their primary landing scorer. You can define multiple thresholds for different landing qualities (e.g. "Butter", "Good", "Acceptable", "Hard") and optionally enable graduated adjustment to scale points within each range. - Thresholds — repeater with the following fields per threshold: - Name — threshold label (e.g. "Butter", "Good", "Hard") - Heaviest (FPM From) — harder landing limit (more negative value) - Lightest (FPM To) — softer landing limit (closer to 0) - Points — base points for this range - Graduated Adjustment — toggle; when enabled, points are adjusted within the range - Direction — "Lighter" (reward softer landings) or "Heavier" (penalise harder landings) - Adjust Points — points per FPM difference FPM values of -9999 or 9999 are treated as infinite bounds. ### Graduated Landing (G-Force) Same concept as the FPM variant but uses G-force values instead (range 0 to 9.99). A G-force of 9.99 is treated as infinite. Uses the same threshold structure with graduated adjustment support. ### Diversion Point Reducer On diverted PIREPs, reduces total points based on the ratio of distance flown to the scheduled distance. For example, if the pilot diverted halfway through the flight, roughly 50% of earned points are kept. - Points — the percentage-based reduction to apply ### Touchdown Pitch Within Range Points awarded if the pitch angle at touchdown is within the configured range. - Min Degrees / Max Degrees — acceptable pitch range - Points — integer value awarded ### Touchdown Pitch Outside Range Points deducted if the pitch angle at touchdown falls outside the range. Same parameters as the award variant. ### Touchdown Roll Within Range Points awarded if the roll angle at touchdown is within the acceptable range. - Max Degrees — maximum acceptable roll magnitude - Points — integer value awarded ### Touchdown Roll Outside Range Points deducted if the roll angle at touchdown exceeds the maximum. Same parameters as the award variant. ### Landing Weight Within MLW Points awarded if the landing weight is within the Maximum Landing Weight tolerance. Uses SimBrief MLW by default. - Weight Source — SimBrief (planned) or Structural - Bound Check — Both, Upper Only, or Lower Only - Over Tolerance (kg) — allowance above MLW - Under Tolerance (kg) — allowance below MLW - Points — integer value awarded ### Landing Weight Outside MLW Points deducted if the landing weight falls outside the MLW tolerance. Same parameters as the award variant. ### Away From Destination Triggers when a pilot lands at an airport other than the scheduled destination (diversion detected). - Points — integer value (typically negative) ### Stabilized Approach (Altitude Gates) **Pegasus v2 Only — Beta Feature**: This rule requires Pegasus ACARS version 2. It is currently a beta feature — we recommend setting points to 0/0 during initial testing. Evaluates approach stability at configurable altitude gates above the touchdown point. This is one of the most complex scoring rules, allowing detailed evaluation of the pilot's approach at multiple altitudes. - Points Award — points if all gates are passed - Points Deduct — points if any gate is failed - Unstable Name — how failures appear in the scorer - Show Zero Scores — toggle; whether to show the rule when no points are awarded or deducted Gates can be configured at the following altitudes above field elevation: 2000, 1500, 1000, 500, 200, 100, 50, 40, 30, 20, 10, and 0 feet. Each gate can evaluate: - Min/Max Vertical Speed (FPM) - Min/Max Airspeed (groundspeed) - Min/Max Flap Position - Max Bank Angle - Min/Max Pitch - Gear Down Required — from this gate onwards, landing gear must be down - No Flap Changes — from this gate onwards, flaps must not move Gates are forward-looking — a 1000ft gate monitors values from 1000ft down to the next configured gate (or touchdown). Subsequent gates override the restrictions set by previous gates. ## Fuel Scoring Rules ### Landing with Too Much Fuel Triggers when the pilot lands with more fuel than the configured threshold. An additional penalty can be applied per 1000kg of excess fuel. - More Fuel Than (kg) — fuel threshold - Fuel Penalty — additional points per 1000kg above threshold - Points — base points ### Landing with Too Little Fuel Triggers when the pilot lands with less fuel than the configured threshold. - Less Fuel Than (kg) — fuel threshold - Points — integer value ### Pushback with More Fuel Than Triggers when the fuel at pushback exceeds the configured threshold. - More Fuel Than (kg) — fuel threshold - Points — integer value ### Pushback with Less Fuel Than Triggers when the fuel at pushback is below the configured threshold. - Less Fuel Than (kg) — fuel threshold - Points — integer value ### Pushback Fuel Within Planned Range Points awarded if the fuel at pushback is within the tolerance range of the SimBrief planned ramp fuel. - Over Tolerance (kg) — allowance above planned fuel - Under Tolerance (kg) — allowance below planned fuel - Bound Check — Both, Upper Only, or Lower Only - Points — integer value awarded ### Pushback Fuel Outside Planned Range Points deducted if the fuel at pushback falls outside the tolerance range of the SimBrief planned ramp fuel. Same parameters as the award variant. ### Landing Fuel Above Reserve Points awarded if the pilot lands with more fuel than the SimBrief final reserve fuel amount. - Points — integer value awarded ### Landing Fuel Below Reserve Points deducted if the pilot lands with less fuel than the SimBrief final reserve fuel amount. - Points — integer value (typically negative) ### Takeoff Fuel Within Planned Range **Pegasus v2 Only**: This rule requires Pegasus ACARS version 2. Points awarded if takeoff fuel is within the tolerance range of the SimBrief planned takeoff fuel. Same parameters as the pushback fuel planned range variant. ### Takeoff Fuel Outside Planned Range Points deducted if takeoff fuel falls outside the tolerance range. Requires Pegasus ACARS version 2. Same parameters as the pushback fuel planned range variant. ## Network Connectivity Scoring Rules ### Connected to Network Points awarded for flying on VATSIM, IVAO, or APOC with configurable matching requirements. You can require that certain flight details match between the PIREP and the network connection. - Require Correct Callsign Prefix — the first 3 characters of the callsign must match - Require Correct Callsign — the full callsign must match - Require Correct Departure Airport — departure ICAO must match - Require Correct Arrival Airport — arrival ICAO must match - Required Percentage — minimum percentage of the flight that must be connected to the network - Points — integer value awarded ## Departure and Arrival Scoring Rules These rules evaluate whether a pilot departs and arrives on time. Two sets are available: one comparing against booking times, one against route times. All share the same parameters: - Tolerance (minutes) — how many minutes early or late is acceptable - Tolerance Mode — "Both" (early and late), "Late Only", or "Early Only" - Points — integer value ### Booking-Based Rules These compare actual times against the booked departure and arrival times: - On-Time Booking Departure — award if off-blocks within tolerance of booked departure - Missed Booking Departure Time — deduct if off-blocks outside tolerance of booked departure - On-Time Booking Arrival — award if on-blocks within tolerance of booked arrival - Missed Booking Arrival Time — deduct if on-blocks outside tolerance of booked arrival ### Route-Based Rules These compare actual times against the route's published departure and arrival times: - On-Time Route Departure — award if off-blocks within tolerance of route departure time - Missed Route Departure Time — deduct if off-blocks outside tolerance - On-Time Route Arrival — award if on-blocks within tolerance of route arrival time - Missed Route Arrival Time — deduct if on-blocks outside tolerance **Route Times in UTC**: For route time scorers to work properly, routes must have arrival and departure times entered in UTC. ## Social Scoring Rules ### Group Flight Points awarded when two or more pilots who are friends on vAMSYS fly between the same airports, on the same online network, with departure and arrival times within an hour of each other. - Points — integer value awarded ### Shared Cockpit Points awarded when two pilots who are friends on vAMSYS book a shared cockpit flight on the same route, same online network, and their takeoff and landing times are within 5 seconds of each other. - Points — integer value awarded ## Taxi Scoring Rules ### Taxi Overspeed Detects overspeed events during taxi phases. Can be configured to reward no overspeeds, penalise overspeeds, or both. - Evaluation Type — "Single Event" (any single overspeed triggers the rule) or "All Events" (evaluates all taxi events collectively) - Threshold Seconds — duration of overspeed before it triggers - Penalise Overspeed — toggle: - Name — penalty label - Points — penalty points (negative) - Reward No Overspeed — toggle: - Name — reward label - Points — reward points (positive) ## Related - Scoring Groups — create and manage scoring groups that contain these rules - PIREPs — review PIREPs where scoring is applied - Fleet — assign fleets to scoring groups - AutoReject Rules — automatic PIREP rejection criteria --- # AutoReject Rules Configure automatic PIREP rejection criteria — flag, reject, or invalidate PIREPs based on landing rates, fuel management, flight length, engine start sequence, route tags, and more. AutoReject rules are automatic evaluations that run after PIREP scoring to flag, reject, or invalidate PIREPs that don't meet quality or safety criteria. Unlike scoring rules which award or deduct points within a scoring group, autoreject rules are airline-wide — they apply to every PIREP regardless of fleet or scoring group. They save staff time by catching problematic PIREPs automatically. ## Accessing AutoReject Rules In Orwell, go to HQ → Rewards → AutoReject Rules. You need the Can See Score Settings permission. ## How AutoReject Rules Work 1. A pilot files a PIREP via Pegasus 2. The PIREP is scored by the fleet's scoring group rules (points calculated) 3. AutoReject rules evaluate the scored PIREP 4. If any rule triggers, the PIREP status changes and an action record is created 5. When multiple rules trigger, the harshest outcome applies ## Rule Outcomes Each autoreject rule is configured with one of three possible outcomes: OutcomeEffectPointsHoursStaff ReviewFailedSent for staff reviewPendingPendingRequiredRejectedAutomatically rejectedNoneCreditedNot requiredInvalidatedAutomatically invalidatedNoneNoneNot required Reply Needed — an optional flag available on Failed rules. When enabled, the pilot must leave a reply on the PIREP before they can book new flights. The PIREP is only sent for staff review after the pilot has replied. **Harshest Outcome Wins**: When multiple autoreject rules trigger on the same PIREP, the most severe action applies: Invalidated overrides Rejected, which overrides Failed. The PIREP's final status reflects the harshest triggered rule. Silent rules — rules can be marked as silent so they do not appear in the PIREP scorer or comments visible to the pilot. The rule still triggers and changes the PIREP status, but the pilot does not see which specific rule was responsible. ## Adding an AutoReject Rule To add a rule, click the create button and select a rule from the available list (grouped by category). Only rules not already enabled for your airline appear in the list. Once added, a rule cannot be changed to a different type — delete and re-add instead. Each rule is configured with: - Name — how the rule appears in the PIREP scorer when triggered - Action — Failed, Rejected, or Invalidated. Some rules have a fixed action that cannot be changed. - Reply Needed — only available when action is Failed - Rule-specific parameters — thresholds, tolerances, and other settings that vary by rule type ## Fleet Overrides Many threshold-based rules support per-fleet parameter overrides. This lets you set different thresholds for different aircraft types — for example, a stricter landing rate limit for turboprops than for widebodies. Each override specifies: - Fleet(s) — which fleet type codes this override applies to - Name — optional custom rule name for this fleet (overrides the main rule name in the scorer) - Parameter overrides — fleet-specific values for the rule's threshold parameters Rules that support fleet overrides are noted in their descriptions below. ## Aircraft AutoReject Rules ### Livery Name Tracks aircraft liveries used in flights. When a pilot flies with a livery not previously seen on the fleet, the PIREP is flagged for staff review so the livery can be approved or rejected. If the livery has been used before by any pilot on the same fleet, the rule does not trigger — regardless of the livery's current approval status. - Action must be set to Failed with Reply Needed off - Pair with Rejected Livery Rejector to handle liveries that have been explicitly rejected **New Liveries Only**: This rule does not check a livery's approval status for previously-seen liveries. It only triggers for completely new, unseen liveries. Use the Rejected Livery Rejector rule to catch flights using rejected liveries. ### Rejected Livery Rejector Triggers if the pilot flies with a livery that has been explicitly rejected by staff. Action can be set to any outcome. ## Flight Length AutoReject Rules ### Excessive Flight Length (Average) Triggers if total flight time exceeds a dynamically calculated threshold based on historical data. The baseline is the average actual flight time from your airline's accepted PIREPs on the same route and fleet, or the published route time — whichever is longer. Two cutoffs are calculated: baseline + Maximum Time grace, and baseline multiplied by Coefficient. The larger value is used as the threshold. - Maximum Time — fixed grace period added to the baseline (HH:MM:SS) - Coefficient — multiplier applied to the baseline (e.g. 1.2 = 20% longer than baseline) Example: baseline 3,900 seconds + 600s grace = 4,500s; or 3,900s x 1.2 = 4,680s. The larger value (4,680s) is used as the threshold. ### Excessive Flight Length (Scheduled) Same logic as the average variant but uses the route's published scheduled flight time as the baseline instead of historical averages. - Maximum Time — fixed grace period (HH:MM:SS) - Coefficient — multiplier ### Excessive Taxi In Triggers if taxi-in time exceeds a calculated threshold. The baseline is determined by priority: the airport's configured taxi-in time, then the airline average from 20+ historical PIREPs at the same airport, then the Maximum Time parameter as a fallback. The threshold is the baseline multiplied by the Coefficient. - Maximum Time — fallback duration if no airport data exists (HH:MM:SS) - Coefficient — multiplier applied to the baseline ### Excessive Taxi Out Same logic as Excessive Taxi In but evaluates departure airport taxi-out time. ### Time Acceleration Use Triggers if time acceleration (sim rate) was detected at any point during the flight. No configurable parameters. ## Fuel AutoReject Rules ### Fuel Increase in Air Triggers if a fuel increase is detected while the aircraft is airborne — an impossible scenario in real aviation that indicates data tampering or a simulator issue. No configurable parameters. ### Pushback Fuel Outside Planned Range Triggers when pushback fuel deviates from the SimBrief planned ramp fuel beyond the configured tolerance. - Over Tolerance (kg) — allowance above planned fuel - Under Tolerance (kg) — allowance below planned fuel - Fleet overrides supported ### Landing Fuel Below Reserve Triggers when the pilot lands with less fuel than the SimBrief final reserve fuel amount. No configurable parameters beyond name and action. ### Takeoff Fuel Outside Planned Range **Pegasus v2 Only**: This rule requires Pegasus ACARS version 2. Triggers when takeoff fuel deviates from the SimBrief planned takeoff fuel beyond the configured tolerance. Same parameters as Pushback Fuel Outside Planned Range. ## Takeoff AutoReject Rules **Pegasus v2 Only**: These rules require Pegasus ACARS version 2. ### Liftoff Pitch Angle Is Excessive Triggers when the pitch angle during rotation falls outside the configured range. - Min Degrees / Max Degrees — acceptable pitch range - Fleet overrides supported ### Liftoff Roll Angle Is Excessive Triggers when the roll angle during rotation exceeds the configured maximum. Uses the absolute value, so it applies to both left and right roll. - Max Degrees — maximum acceptable roll magnitude - Fleet overrides supported ### Takeoff Above MTOW Triggers when the takeoff weight exceeds the SimBrief Maximum Takeoff Weight plus the configured tolerance. - Over Tolerance (kg) — allowance above MTOW - Under Tolerance (kg) — allowance below MTOW - Fleet overrides supported ## Landing AutoReject Rules ### Excessive Landing (FPM) Triggers if the landing rate is harder (more negative) than the configured threshold. You can add multiple instances with different thresholds and actions — for example, -500 FPM to Reject and -1000 FPM to Invalidate. When multiple landing rate rules trigger on the same PIREP, only the most severe action applies. - Heavier Than — FPM threshold (e.g. -500). A PIREP with exactly this value triggers the rule. - Fleet overrides supported ### Excessive Landing (G-Force) **Pegasus v2 Only**: This rule requires Pegasus ACARS version 2. Same concept as the FPM variant but uses G-force values. Triggers when G-force at landing meets or exceeds the threshold. - Heavier Than — G-force threshold (e.g. 2.0). A PIREP with exactly this value triggers the rule. - Fleet overrides supported ### Soft Landing (FPM) Triggers if the landing rate is softer (closer to 0) than the configured threshold. - Lighter Than — FPM threshold (e.g. -100). A PIREP with exactly this value triggers the rule. - Fleet overrides supported ### Soft Landing (G-Force) Triggers when G-force at landing is at or below the threshold. Pegasus v2 only. - Lighter Than — G-force threshold (e.g. 1.0) - Fleet overrides supported ### Gear Up Landing Triggers if any touchdown is detected with the landing gear up. No configurable parameters. Fixed gear aircraft (e.g. C208 Caravan) are automatically excluded from this rule, since they do not send gear change data and cannot be evaluated for gear state. ### Multiple Landings Triggers if more than one touchdown is detected — for example, a bounced landing or go-around. Action should be set to Failed with Reply Needed on, as the pilot may have a valid explanation. ### Landing Above MLW Triggers when landing weight exceeds the SimBrief Maximum Landing Weight plus the configured tolerance. - Over Tolerance (kg) / Under Tolerance (kg) - Fleet overrides supported ### Landing Away From Destination Triggers when the pilot lands at an airport other than the scheduled destination (diversion detected). This rule integrates with the vAMSYS diversion system. Action should be set to Failed with Reply Needed on. ### Touchdown Pitch Angle Is Excessive Triggers when the pitch angle at touchdown falls outside the configured range. - Min Degrees / Max Degrees — acceptable pitch range - Fleet overrides supported ### Touchdown Roll Angle Is Excessive Triggers when the roll angle at touchdown exceeds the configured maximum. Uses the absolute value, so it applies to both left and right roll. - Max Degrees — maximum acceptable roll magnitude - Fleet overrides supported ## Points AutoReject Rules ### Negative Points Triggers when the PIREP's final score (after all scoring rules have been evaluated) is negative. No configurable parameters. ## General AutoReject Rules ### Force Review Unconditionally flags every PIREP for staff review. No configurable parameters — useful for airlines that want to manually review all PIREPs. ### Force Empty Route Review Flags PIREPs where the route has no VA-provided waypoints. Silent rule option available. ### Force Charter Flight Review Flags all charter flight PIREPs for review. Silent rule option available. ### Force Training Flight Review Flags all training flight PIREPs for review. Silent rule option available. ### Force Repositioning Flight Review Flags all repositioning flight PIREPs for review. Silent rule option available. ### ACARS Comment Rejector Flags PIREPs that were filed with a comment in Pegasus. Useful for catching PIREPs where the pilot noted an issue during the flight. ### Random Chance Review Flags PIREPs for review based on a random percentage chance. Useful for spot-checking SOP compliance across your airline. - Chance — percentage (1–100%) ### Paused During Flight (Absolute) Triggers if the simulator was paused for more than a set number of seconds during the flight. - More Than (seconds) — pause time threshold in seconds ### Paused During Flight (Percentage) Triggers if pause time exceeds a percentage of total airborne time. For example, on a 2-hour flight with 1% configured, the rule triggers if the pilot paused for more than 72 seconds. - More Than Percent — percentage of airborne time (1–100%) ### Paused During Flight (Distance-Based) Triggers if pause time exceeds a threshold that varies by flight distance. Longer flights get more pause tolerance. You configure multiple distance/time thresholds and the system selects the appropriate one based on the flight's distance. - Distance Thresholds — repeater with the following fields per threshold: - Min Distance (nm) — minimum flight distance for this threshold to apply - Allowed Seconds — maximum pause time allowed at this distance Example: 0–999nm = 60 seconds allowed, 1000–1999nm = 120 seconds, 2000nm+ = 180 seconds. ## Taxi AutoReject Rules ### Taxi Overspeed Triggers when taxi overspeed is detected for longer than the configured duration. - Evaluation Type — "Single Event" (any single overspeed event exceeding the threshold) or "All Events" (total overspeed time across all taxi events) - Threshold Seconds — duration before triggering (1–600 seconds) ## Engine AutoReject Rules ### Engine Start Sequence Triggers when the pilot starts engines in the wrong order. Uses the same detection logic as the Engine Start Sequence scoring rule. - Required Engine Start Sequence — select Engine 1–4 in the required start order. The selection order defines the required sequence. - Fleet Overrides — set different required sequences for specific aircraft type codes (e.g., a different engine start order for four-engine aircraft vs twins). Each override can also have a custom rule name. The required sequence is displayed to pilots on the Scores page using the format "Engine 2 → Engine 1". Fleet-specific overrides are listed separately. ## Route AutoReject Rules ### Route Tag Review Triggers when a pilot flies a route that has one or more of the configured tags. Use this to automatically reject or flag PIREPs for routes tagged as exam, checkflight, or any other category that requires special handling. - Tags — select which route tags trigger this rule. If the flown route has any of the configured tags, the rule triggers. Tag matching is case-insensitive. Tag suggestions are auto-populated from existing route tags for your airline. ## Permissions PermissionGrantsCan See Score SettingsAccess to AutoReject Rules (shared with Scoring Groups and Scoring Rules) ## Related - Scoring Groups — group scoring rules by fleet - Scoring Rules — configure point-based PIREP scoring - PIREPs — review PIREPs affected by autoreject rules - Fleet — fleet types referenced by fleet overrides - Liveries — manage aircraft liveries (related to Aircraft autoreject rules) --- # Custom Pages Create content pages for pilots in Phoenix with a flexible page builder supporting text, images, buttons, alerts, and videos. Custom Pages is a built-in page builder that lets you create content pages for pilots in Phoenix. Pages can contain rich text, images, buttons, alerts, and embedded videos — all arranged in a flexible grid layout. Pages are organised into categories that control where they appear in Phoenix navigation. ## Accessing Custom Pages In Orwell, go to Pages → Custom Pages. You need the Can See Pages permission. ## Page Categories Each page belongs to a category that determines where it appears in Phoenix navigation: CategoryNavigation PlacementURL PathDocumentsDocuments submenu/phoenix/documents/{url}ResourcesResources submenu/phoenix/resources/{url}StandaloneTop-level menu item with custom icon/phoenix/pages/{url}SpecialNot shown in navigation/phoenix/pages/{url} - Documents and Resources appear grouped under their respective submenus in the Phoenix sidebar - Standalone pages appear as top-level menu items with a custom FontAwesome icon - Special pages are system-managed (e.g. the ACARS page) — they cannot be edited or deleted by staff ## Creating a Page Each page has the following settings: - Title — page name shown in navigation. Auto-generates the URL slug. - Category — determines navigation placement: Documents, Resources, or Standalone. - URL — auto-generated from the title, editable. Prefixed with the category path (e.g. /phoenix/documents/). - Enabled — whether pilots can see the page. Disabled pages are only visible to airline staff. - Hidden in Nav — the page is accessible via its direct URL but not shown in navigation menus. Useful for pages you link to from other content. - External URL — makes the page a redirect link to an external website. No content editor is shown when enabled. - Icon — FontAwesome Light icon name (e.g. "magnifying-glass"). Only available for Standalone pages. - Rank Restriction — limit page visibility to specific ranks. Leave empty for all pilots to see the page. ## Page Content Page content is built using a visual builder with two types of containers: - Panels — card containers with a visible heading. Each panel has a width (1–12 grid columns), an optional internal note (visible only to staff), and can contain multiple components. - Headless Panels — same as panels but render without a visible heading. Useful for layout sections that don't need a title. Inside panels, you add components — text, images, buttons, alerts, or videos. Each component also has its own width setting and optional rank restriction, giving you fine-grained control over layout and visibility. The width setting uses a 12-column grid. A width of 12 means full width, 6 means half width, 4 means one-third, and so on. Components placed next to each other will flow into rows automatically. ## Component Types ### Text Rich text content using the TipTap editor. Supports formatting, links, lists, and more. ### Image Upload images with optional dark mode support: - Light mode image (required) — the default image shown to pilots - Dark mode image (optional) — automatically displayed when the pilot uses dark mode - URL (optional) — makes the image a clickable link - Positioning — left, right, or centre alignment ### Button A styled button linking to an external URL: - Title and URL (required) - Style — Info, Success, Warning, Danger, Primary, or Secondary - Optional rich text description displayed below the button ### Internal Button Same as Button but links to another custom page within the airline instead of an external URL. Select the target page from a dropdown. Only non-external pages appear in the list. ### Alert A coloured notice box with rich text content. Available styles: Info, Success, Warning, Danger, and Primary. ### YouTube Video Embed a YouTube video by entering its video ID — the part after v= in a YouTube URL. **Width and Rank Restriction**: Every component type supports a width setting (1–12 grid columns) and an optional rank restriction to control who can see it. ## Rank-Based Visibility Rank restrictions can be applied at three levels: 1. Page level — controls who sees the page in navigation and can access it via URL 2. Panel level — controls who sees specific panels within an accessible page 3. Component level — controls who sees individual components within a visible panel When no ranks are selected at any level, all pilots can see that element. Both a pilot's primary rank and honorary rank (if assigned) are checked against the restriction. ## Special Pages and the ACARS Page Special pages are system-managed and protected — their category, enabled state, and navigation visibility cannot be changed, and they cannot be deleted. The ACARS page (Pegasus ACARS) is a special page that displays ACARS download and setup information for pilots. If this page is accidentally modified, use the Restore ACARS Page header action on the list page to reset it to the default template. ## Rules Page Any enabled custom page can be designated as the airline's rules page via Settings → Pilot Registration. The rules page is displayed to pilots during registration and is accessible publicly without login. A page set as the rules page cannot be deleted. **Publicly Accessible**: The rules page is publicly accessible — anyone with the link can view it without logging in to vAMSYS. ## List View The custom pages list displays: ColumnDescriptionTitlePage name (searchable)CategoryDocuments, Resources, Standalone, or Special (sortable)EnabledWhether the page is visible to pilotsExternalWhether the page redirects to an external URLHiddenWhether the page is hidden from navigationURLThe page URL slug (searchable) Pages can be reordered by drag-and-drop. Filters are available for page status (enabled/disabled) and category (multi-select). Each row has actions to view the page in Phoenix (opens in a new tab), edit, or delete. ## Permissions PermissionGrantsCan See PagesAccess to Custom Pages management ## Related - Phoenix Dashboard Editor — customise the pilot dashboard layout - Pilot Registration — configure the rules page requirement - Ranks — rank system used for page visibility restrictions --- # Activities Create events, tours, rosters, and community challenges that give pilots something to fly towards — with bonus points, badges, and progress tracking. Activities are time-limited events, tours, rosters, and community challenges that give pilots something to fly towards. They award bonus points and badges, and appear in the Activities section of Phoenix. vAMSYS supports seven activity types — each tailored to a different style of engagement. ## Accessing Activities In Orwell, go to Operations → Activities. You need the Can See Event List permission. The Activities module must be enabled for your airline. ## Activity Types Overview vAMSYS supports seven activity types: TypeLegsRegistrationHow It WorksEventNoOptionalFly matching routes or airport pairs during the time windowFocus AirportNoOptionalFly to or from a spotlighted airportTourYesRequiredComplete a sequence of legs in orderRosterYesRequiredComplete assigned legs with specific aircraftCurated RosterYesRequiredExperience a rotation a pilot or aircraft flies in a day — shown in Flight Centre, not ActivitiesCommunity GoalNoAutomaticAll pilots contribute towards a shared target (e.g. 10,000 flights)Community ChallengeNoAutomaticPilots are assigned to teams competing against each other **Community Activities**: Community Goals and Community Challenges appear in their own section in Phoenix, separate from the main Activities page. ## Common Settings These settings are shared across most or all activity types. ### Presentation - Name — activity title shown to pilots. - Sidebar Title and Sidebar Content — optional text shown in a sidebar panel on the activity detail page. Not available for Curated Rosters. - Tags — sub-categories for filtering in Phoenix. - Image / Dark Mode Image — banner image displayed on the activity page. Not available for Curated Rosters. - Description — rich text description of the activity. ### Time Window - Start and End — UTC timestamps defining when the activity is active. PIREPs must fall within this window (adjusted by Time Award Scale). - Show From — optional; controls when the activity becomes visible in Phoenix. If not set, the activity is visible immediately. - Time Leeway — 0 to 120 minutes of hidden grace added to both ends of the time window. Pilots do not see this value — they only see the start and end times. Useful for quietly accommodating flights that depart just before or land just after the activity window. ### Time Award Scale Determines which part of the flight must fall within the activity time window: RuleMeaningTakeoff onlyDeparture time must be within the windowLanding onlyLanding time must be within the windowEntire flightBoth takeoff AND landing must be within the windowAny partEither takeoff OR landing can be within the window **UTC Times**: All times are UTC. Make sure your activity start and end times account for the time zones your pilots fly in. ### Restrictions Optional filters that limit which PIREPs qualify for the activity: - Network — offline, VATSIM, IVAO, POSCON, APOC, PilotEdge, FSCloud, SayIntentions, other. - Fleet — only specific fleet types. - Callsign — only specific callsign prefixes. - Ranks — only pilots of specific ranks. - Landing Rate — minimum and/or maximum FPM. ### Registration - Registration Required — if enabled, pilots must register before their PIREPs count. Always required for Tours, Rosters, and Curated Rosters. - Registration Start / End — window during which pilots can register for the activity. ### Rewards - Points — bonus points awarded. Can be a fixed amount or a percentage of the PIREP's base score. - Create Badge — auto-create a placeholder badge linked to this activity. Only available during activity creation. - Allow Repeat Participation — whether pilots can complete the activity multiple times. ## Events Fly matching flights during a time window. No specific leg order. PIREPs are matched automatically — no registration required unless you enable it. Points are awarded immediately when a qualifying PIREP is filed. Events have two subtypes: Airport-Based Events — configure departure and arrival airports with an operator: - Departure airports — one or more airports. - Arrival airports — one or more airports. - Operator (AND/OR) — AND means the PIREP must match both a listed departure AND a listed arrival. OR means matching either a listed departure OR a listed arrival is sufficient. Route-Based Events — configure specific routes. Each entry specifies a departure airport, arrival airport, and optionally a specific route ID. ## Focus Airport A simplified event centred on a single airport. Any flight departing from or arriving at the focus airport qualifies. No subtypes, no route configuration — just pick the airport. Points are awarded immediately when a qualifying PIREP is filed. ## Tours Tours are multi-leg journeys that pilots complete in sequence. They are the most complex activity type. ### How Tours Work 1. Staff creates a tour with an ordered list of legs (minimum 2). 2. Pilots register for the tour during the registration window. 3. Registration creates a logbook tracking progress for each leg. 4. Pilots fly each leg in order — each PIREP is matched against the next incomplete leg. 5. Legs must be flown sequentially: a pilot must land leg N before departing leg N+1. However, pilots can fly other non-tour flights in between legs — they are not limited to flying tour legs back-to-back. 6. When all legs are completed, the tour is marked as complete. ### Tour Subtypes Airport-Based Tours — each leg defines a departure and arrival airport. Any PIREP flying between those airports qualifies for the leg. Route-Based Tours — each leg specifies a departure airport, arrival airport, and a specific route ID. The PIREP must be on that exact route, not just between the same airports. **Choose Carefully**: The subtype cannot be changed after creation. Airport-based tours are the preferred option — they match by airport pair and do not care about route IDs. Route-based tours match by route ID, which means changing a leg's route ID in the tour editor will invalidate all existing completions for that leg on reprocess. ### Leg Visibility (Show From) Each tour leg has an optional Show From date. Before this date, the leg is hidden from the pilot's tour progress view. Use this to reveal legs gradually — for example, one leg per week. ### How PIREPs Match Tour Legs A PIREP matches a tour leg when ALL of the following are true: 1. Departure airport matches the leg's departure airport (exact ICAO match). 2. Arrival airport matches the leg's arrival airport (exact ICAO match). 3. Route ID matches the leg's route ID (only for route-based tours). 4. The flight falls within the activity time window (based on Time Award Scale, adjusted by Time Leeway). 5. The pilot departed after landing the previous leg (sequential requirement). 6. All activity restrictions are met (network, fleet, callsign, rank, landing rate). **Editing Routes vs Editing Tours**: Editing a route in the route editor does not affect tour progress — matching is based on the airport pairs or route IDs stored in the tour, not the route's current configuration. The problem is editing the tour itself: if you change a leg's airports or route ID, previously matching PIREPs no longer count and pilots lose that leg on reprocess. ### What Happens When You Edit a Tour When you save changes to a tour's legs, the system runs a reprocessing job: 1. All bonus points from this tour are removed from every affected PIREP. 2. All logbooks are reset to Incomplete with all legs marked as not completed. 3. Duplicate logbooks are cleaned up (one per pilot). 4. PIREPs are re-matched against the new leg definitions for each registered pilot. 5. Bonus points are re-awarded where PIREPs match the updated legs. This means: - If you change a leg's airports, pilots who flew the old airports lose credit for that leg. - If you add new legs, existing progress on earlier legs is preserved (assuming they still match). - If you remove legs, the tour becomes shorter and may auto-complete for some pilots. - The reprocessing runs asynchronously — it may take a few minutes for all pilots to see updated progress. **Destructive to Pilot Progress**: Editing tour legs is destructive to pilot progress. If you change airports on a leg that pilots have already flown, those PIREPs will no longer match and pilots lose that progress. There is no way to recover it other than reverting the change. Add new legs or extend the tour rather than modifying existing ones. ### Tour Point Award Modes Two settings control when and how points are awarded: Award Per LegWhen Tour CompleteBehaviourYesNoPoints added to each PIREP immediately as each leg is completedYesYesPoints added to ALL leg PIREPs, but only after the entire tour is completeNoYesPoints added only to the final leg's PIREP when the tour is complete ### Claims and PIREP Statuses Both ACARS PIREPs (flights tracked by Pegasus) and accepted claims count towards tour leg completion. The activity system does not distinguish between them — once a claim is accepted by staff, it is processed through the same matching logic as a normal PIREP. How each PIREP status affects tour progress and scoring: PIREP StatusCounts Towards Leg?Points Awarded?Accepted / CompleteYesFull pointsRejectedThe leg remains completed — rejecting a PIREP does not automatically revoke tour progressRejected PIREPs do not count towards rank progression or statistics. When the award mode is set to award on tour completion, the system pro-rates the points the same way as invalidated PIREPsInvalidatedThe leg remains completedInvalidated PIREPs do not count towards rank progression or statistics. When the award mode is set to award on tour completion, the system pro-rates the points: it calculates the ratio of valid (non-invalidated) legs to total legs and multiplies the tour points by that ratio Example of pro-rated points: A 5-leg tour awards 500 points on completion. A pilot completes all 5 legs, but 1 PIREP is later invalidated. The system calculates: 4 valid legs / 5 total legs = 80%. The pilot receives 400 points instead of 500. **Leg Completion Persists**: Rejecting or invalidating a PIREP does not automatically remove the pilot's tour leg completion. The leg stays marked as completed in their logbook. Point totals are recalculated when the tour is edited or reprocessed. ## Rosters Rosters work like tours but with aircraft assignments. Each leg specifies a departure, arrival, and a specific aircraft the pilot must fly. Differences from Tours: - Each leg has a mandatory aircraft assignment (specific registration, not just fleet type). - Registration is always required. - Registration window is automatically set to the activity's start/end dates. - Aircraft selection is filtered by routes available between the leg's airports. All other behaviour (sequential completion, PIREP matching, point award modes, claims and PIREP statuses, reprocessing on edit) works identically to tours. ## Curated Rosters Curated Rosters are multi-leg activities with aircraft assignments — functionally similar to Rosters but designed to let pilots experience the rotation a pilot or aircraft flies in a day. They are shown in Flight Centre rather than the Activities page. Key differences from Rosters: RosterCurated RosterDisplayed inActivities pageFlight Centre → Curated RostersPointsConfigurableOptional — configurable points, percentage mode, or leave at 0Registration purposeRequired to earn pointsFor progress tracking and My RostersBanner imageYesNo — shows mini route map insteadSidebar contentYesNoShow From dateYesNoTypical useShort-term competitive schedulePilot-in-a-day experience (a rotation a pilot or aircraft flies in a day) How pilots find them: Curated Rosters appear under Flight Centre → Curated Rosters in the Phoenix sidebar. The menu item only appears if the airline has at least one Curated Roster. A red badge shows how many registered-but-incomplete Curated Rosters the pilot has. Display: Instead of a banner image, each Curated Roster shows a mini route map. Instead of point values, it shows the number of legs and the aircraft types involved. All other behaviour (sequential leg completion, PIREP matching, reprocessing on edit) works identically to Rosters and Tours. Fleet-per-leg: Each leg can assign a fleet type instead of a specific aircraft. This lets pilots choose any aircraft within that fleet type when dispatching the leg. My Rosters integration: When a pilot registers for a Curated Roster, it also appears on their My Rosters page alongside personal rosters. Pilots can track progress and unregister directly from My Rosters. See My Rosters & Personal Rosters for the pilot perspective. ## Community Goals Community Goals are collaborative targets where all pilots contribute towards a shared objective. They work fundamentally differently from other activity types. ### How Community Goals Work 1. Staff defines a target — for example, "Transport 1,000,000 passengers". 2. Any PIREP that meets the goal's filters contributes automatically — no registration needed. 3. Each qualifying PIREP adds to the airline-wide progress (passengers, cargo, flights, distance, or flight time). 4. When the target is reached, the goal is achieved and completion rewards are distributed. ### Count Types TypeWhat CountsUnitPassengersPassengers transported per PIREPPassengersFreightCargo weight per PIREPkgFlightsNumber of qualifying PIREPsFlightsDistanceRoute distance per PIREPnmFlight TimeFlight duration per PIREPHours ### Filters Community Goals use a flexible filter system. Only PIREPs that pass ALL enabled filters count towards the goal. Available filters: - Airport Groups — departure/arrival airport restrictions with AND/OR operators. - Distance Range — minimum and/or maximum flight distance (nm). - Night Takeoff / Night Landing — require night operations. - Landing Rate Range — minimum and/or maximum FPM. - Landing G-Force Range — minimum and/or maximum G-force. - No Violations / Max Violations — PIREP violation limits. - Fleets — specific fleet types. - Callsign Prefixes — specific callsigns. - Ranks — specific pilot ranks. - Networks — specific online networks. - Route Tags — routes with specific tags. - Route Types — scheduled, cargo, charter, training, VFR, repositioning. ### Rewards - Participation Points Per PIREP — points added to every qualifying PIREP. - Completion Points — bonus points awarded to all participants when the goal is reached. - Tiered Multipliers — when enabled, top contributors receive multiplied completion points based on their ranking among all participants. Four configurable tiers with default multipliers: TierDefault MultiplierTop 10%3.0×Top 25%2.0×Top 50%1.5×Top 75%1.25× Pilots below the top 75% still receive the base completion points (1.0× multiplier). All multipliers are configurable per activity. - Badges can be linked for participation (first qualifying PIREP), completion (every participant, only if the goal is reached), and Top 10% contributors (shown when tiered multipliers are enabled). Badges can also be tied to the goal from the badge side using the Community badge rules — see Badges. **No Overlapping Community Activities**: Community Goals cannot overlap with other Community Goals or Community Challenges in the same time window. ## Community Challenges Community Challenges are team-based competitions. Pilots are split into exactly two teams competing against each other over the same time window. ### How Community Challenges Work 1. Staff defines exactly 2 teams, each with their own target, count type, and filters. 2. When a pilot files a qualifying PIREP, it counts towards the first matching team. 3. The challenge runs until the end date. Reaching 100% does not end the challenge early — teams can exceed their target. 4. At the end, the team with the highest completion percentage wins. At least one team must reach 100% for there to be a winner. 5. All rewards are distributed after the challenge ends — participation points, completion points, tier multipliers, and winner bonuses. ### Team Configuration Each team has: - Name — team display name. - Count Type — what to count (passengers, freight, flights, distance, flight time) — can differ per team. - Count Target — the target number. - Filters — same filter system as Community Goals — can differ per team. ### Rewards - Participation Points Per PIREP — points added to every qualifying PIREP during the challenge. - Winner Bonus Points — flat bonus points awarded to members of the winning team. Distributed after the challenge ends. - Tiered Multipliers — same tier system as Community Goals. When enabled, top contributors within each team get their winner bonus points multiplied based on contribution ranking. - Badges can be linked for participation (first qualifying PIREP), winning (every contributor on the winning team, provided the team reached its target), and Top 10% contributors within the winning team (shown when tiered multipliers are enabled). Badges can also be tied to the challenge from the badge side using the Community badge rules — see Badges. Only the winning team receives winner bonus points and tier rewards. The losing team receives nothing beyond per-PIREP participation points. If neither team reaches 100%, there is no winner and no bonus points are distributed. **Reward Flexibility**: The combination of participation points (per PIREP), winner bonus points (at the end), and tiered multipliers (top contributors) gives you fine-grained control over how to reward ongoing participation vs. final contribution ranking vs. being on the winning side. **One Team Per PIREP**: A PIREP can only count towards one team. If it matches multiple teams' filters, it counts for the first matching team. ## Customising Activity Type Names Airlines can rename every activity type in Settings → Modules. Three sections: - Activity Names — Event, Focus Airport, Tour, Roster. Shown in Phoenix Activities page tabs and filters. - Community Activity Names — Community Goal (singular/plural), Community Challenge (singular/plural). - Roster Names — five labels: Roster (singular), Curated Roster (singular), Curated Rosters (plural), My Rosters, and Roster Generator. Shown in Flight Centre sidebar, page titles, tabs, filter headings, and call-to-action buttons. Custom names replace the defaults everywhere in Phoenix: navigation, page titles, tabs, filter labels, and call-to-action buttons. When left empty, sensible defaults are used. These overrides are configured per airline in Settings → Modules under the Roster Names section. ## Replicating Events Events and Focus Airports can be set to replicate automatically: - Weekly — new instance every week. - Bi-weekly — every two weeks. - Monthly — every month. When replicated, a new activity is created with the same settings but shifted dates. You can optionally set a Repeat Until date — once this date is reached, no further replications are created. ## List View The list page has tabs for filtering by type: Current, Event, Focus Airport, Tour, Roster, Curated Roster, Personal Roster, Community Goal, Community Challenge, and VA All. ColumnDescriptionIDDatabase identifier (sortable, searchable)NameActivity name (searchable)TypeActivity type (visible on Current and All tabs)Show FromWhen the activity becomes visible (not shown for Curated Roster)StartActivity start timeEndActivity end timeRegistrationsNumber of registered pilots (N/A if registration not required)CompletionsNumber of pilots who completed the activityTagsSub-category tags Actions: Edit, View in Phoenix, Copy (creates a new activity with the same settings), Delete. **Custom Tab Names**: Community Goal and Community Challenge tab names can be customised per airline. If your airline uses custom names, they appear in the tabs and navigation instead of the defaults. ## Roster Generator Toggle The Roster Generator lets pilots create personal rosters. Enable it in Settings → Modules under the Roster Generator toggle. When enabled, pilots can access the Roster Generator from the My Rosters page via a "Generate New Roster" card. The generator requires at least two legs. When disabled, pilots cannot create personal rosters, and the My Rosters sidebar link is hidden unless curated rosters exist for the airline. ## Flight Time on Activity Cards Activity cards in Phoenix display estimated flight time information to help pilots gauge the time commitment. Tours and rosters show the total flight time across all legs, while airport-based events show a time range. Flight times are calculated automatically from the activity's routes. ## Permissions PermissionGrantsCan See Event ListAccess to Activities management Prerequisite: The Activities module must be enabled for the airline. ## Related - Badges — link badges to activity completion - Ranks — restrict activities by rank - Fleet — restrict activities by fleet type - PIREPs — PIREPs are scored against activities - Scoring Rules — activity points are added as bonus scores on top of PIREP scoring --- # General Settings Core airline configuration — name, timezone, support details, maintenance mode, and feature modules. General Settings cover the foundational configuration of your Virtual Airline — identity, support details, maintenance mode, and which vAMSYS features are enabled. These are typically the first settings you configure when setting up a new airline. ## Accessing General Settings In Orwell, go to Settings → Basic and Settings → Modules. You need the Can See Airline Settings permission. ## Basic Settings Core identity and support configuration for your airline. FieldDescriptionVA NameRead-only. Set during your application. Can only be changed by Team vAMSYS via a support ticket.SloganShown on login/register pages and the Select VA page. Maximum 250 characters.WebsiteYour VA homepage URL. Used in emails and across vAMSYS. Must start with https:// and end with TLD — no trailing slashes.TimezoneControls when statistics roll over and when scheduled actions run (activity checks, leaderboard updates, etc.).Pilot Support EmailUsed as the reply-to address on system emails sent to pilots.Pilot Support URLLink to your support system. If set, appears in Phoenix navigation. ### Maintenance Mode When enabled, pilots cannot access Phoenix. They see a maintenance message instead. Staff can preview the maintenance page via a link shown next to the toggle. Use the rich text editor to customise the maintenance message — explain why Phoenix is unavailable and when you expect it to return. ## Modules Modules control which major vAMSYS features are enabled for your airline. Disabling a module hides it from both staff and pilots. ### Systems ToggleWhat It EnablesEnable ActivitiesActivities system — events, tours, rosters, community goals, and community challenges.Enable NOTAMNOTAM system for publishing notices to pilots.Claims SystemAllows pilots to submit a claim for hours and points if they were unable to track their flight via ACARS. When enabled, an optional Claim Message can be configured — this text is shown to pilots in the claim modal.Enable Route ChangelistShows a Route Changes section in Phoenix where pilots can see upcoming and ending routes.Enable MarketingEnables a marketing email opt-in for pilots. When active, pilots can subscribe to receive marketing communications from your airline. ### Activity Type Names Rename activity types displayed in Phoenix. Three sections are available: - Activity Names — Event, Focus Airport, Tour, Roster - Community Activity Names — Community Goal (singular/plural), Community Challenge (singular/plural) - Roster Names — Curated Roster (singular/plural) **Custom Names Apply Everywhere**: Custom names replace the defaults everywhere in Phoenix: navigation, page titles, tabs, and filter labels. ### Leaderboard ToggleDescriptionEnable LeaderboardMain pilot leaderboards.Hub LeaderboardLeaderboards per hub.Online LeaderboardLeaderboards for online network flights.Split Online LeaderboardSeparate leaderboards per network. Only visible when Online Leaderboard is enabled.Online Leaderboard NetworksChoose which networks to include: Offline, VATSIM, IVAO, POSCON, APOC, PilotEdge, FSCloud. ### Badges ToggleDescriptionEnable BadgesEnables the badge system.Show Badges in PhoenixMakes badges visible to pilots and starts awarding them.Badge NameCustom name for badges (e.g. "Awards"). Shown in Phoenix navigation. ### Hangar ToggleDescriptionEnable HangarEnables file storage for staff.Make Hangar PublicMakes files available to pilots.Hangar NameCustom name (e.g. "Downloads", "Resources"). Shown in Phoenix navigation. Maximum 240 characters. ## Permissions PermissionGrantsCan See Airline SettingsAccess to Basic Settings and Modules pages ## Related - Activities — requires Activities module - Badges — requires Badges module - NOTAMs — requires NOTAM module - Branding — logo and style settings - PIREP & Reward Settings — PIREP processing and point awards - Booking & Dispatch Settings — booking and dispatch configuration --- # Booking & Dispatch Settings Configure jumpseats, booking validity, dispatch table columns, route creation defaults, and external flight tracking buttons. Booking & Dispatch Settings control how pilots book flights, what they see on the dispatch page, and how new routes are configured by default. ## Accessing Booking & Dispatch Settings In Orwell, go to Settings → Booking & Dispatch and Settings → Route Defaults. You need the Can See Airline Settings permission. ## Jumpseat System Jumpseats allow pilots to change their location without flying. Three tiered toggles control the scope: ToggleDescriptionJumpseat SystemPilots can jumpseat to airports within the route network of their current location.Jumpseat to BasesAlso allows jumpseating to hub/base airports outside the current route network.Jumpseat AnywhereAllows jumping to any airport in the entire network. ## Booking Settings FieldDescriptionShow Event/Focus Airport MarkersReplaces airport markers with red on the Book Flight and Destination maps for airports involved in active events or focus airports.Enable Manual SimBriefAllows creating SimBrief OFPs from the View Booking page as a secondary method. The primary method is via the Dispatch page.Booking Validity — DefaultHow long a booking remains valid, in hours (1–200).Booking Validity — Diversion RepositioningHow long a repositioning booking after a diversion remains valid, in hours (1–200). ## Dispatch Functions Features you can enable for the Dispatch page in Phoenix. ### Aircraft Selection - Require Explicit Aircraft Selection — pilots must select an aircraft before seeing the rest of the dispatch options. Bypassed if there is only one fleet type or the pilot has enabled a bypass in their settings. - Force Aircraft Selection Even with Single Fleet — disables the single-fleet bypass, but the pilot's personal bypass setting is still honoured. ### Highlight Booked Aircraft Three mutually exclusive options — only one can be active at a time: 1. Highlight aircraft booked in other bookings 2. Highlight aircraft currently in the air 3. Highlight aircraft booked in the past hour ### Departure & Arrival Times - Enable Departure and Arrival Times — shows route times in the dispatch table. - Invent Times if Empty — auto-generates departure times based on current time + 45 minutes when a route has no times set. - Show Local Route Times — displays route times in the local timezone of the airport instead of UTC. ### Next Departures When departure times are enabled, you can add a "Next Departures" preset button to the dispatch table and Book Flight map. It filters to flights departing within a configurable time window. - From (hours from now) — start of window. Default: 0 (now). Range: 0–23.5 in 30-minute steps. - To (hours from now) — end of window. Default: 3. Range: 0.5–24 in 30-minute steps. ### Other Dispatch Functions ToggleDescriptionEnable Route TagsAllows adding tags to routes. Tags are shown in the dispatch table and can be filtered in the Book Flight page.Flight Centre Fleet FiltersAdds fleet type filters across Flight Centre.Enable SimBrief Overrides PreviewAllows pilots to preview the exact data and overrides sent to the SimBrief API. Staff always have access regardless of this setting. ## Dispatch Extras External flight tracking buttons shown in the Dispatch and View Booking pages. ToggleDescriptionFlightAware ButtonLink to FlightAware.Flightradar24 ButtonLink to Flightradar24. Optionally set a callsign prefix override (max 3 characters) to force a custom flight number on all FR24 links.FR24 Aircraft LookupPilots can look up which aircraft flew a route historically using Flightradar24 data.AirNav Radar ButtonLink to AirNav RadarBox. ## Dispatch Table Defaults Configure the column order, visibility, and labels for the dispatch table. Column visibility is controlled entirely by these settings — pilots see exactly the columns you configure here. Available columns: Departure, Arrival, Callsign, Flight Number, Operator, ATC Callsign, Fleets, Remarks, ETD, ETA, Flight Time, Distance, Days of Operation, Flight Type, and Tags. Per-column options: - Visible by Default — whether the column is shown initially. - Custom Label — override the default column header text. - Airport Identifier Display — ICAO, IATA, or both (Departure and Arrival columns only). - Days Display Format — abbreviated (Mon, Tue) or numeric (1, 2) for the Days of Operation column. Default sorting can be configured by column and direction (ascending or descending). Drag rows to reorder columns. ## Route Creation Defaults Default settings applied when creating new routes. Found under Settings → Route Defaults. **Not Retrospective**: These settings only affect newly created routes. Existing routes are not changed. ### Local Times Route Times Use Local — when enabled, departure and arrival times entered for routes are treated as the local time of the airport instead of UTC. This affects route creation and editing in Orwell, importers/exporters, and the API. ### Callsign Defaults Controls how callsigns are generated for new routes. The options are mutually exclusive — only one can be active: OptionBehaviourAllow Callsign ChangePilots can enter their preferred callsign during dispatch.Username Callsign (Option 1)Callsign defaults to the pilot's username.Username Callsign (Option 2)Callsign defaults to the first letters of each word in the pilot's name.Aircraft RegistrationCallsign defaults to the aircraft registration. Callsign cannot be changed during dispatch. If none of the above are enabled, a Callsign Generator regex pattern can be configured. For example, [A-Z][A-Z][0-9][0-9] generates callsigns like AB97. A "Generate Sample" button lets you test the pattern. ## Permissions PermissionGrantsCan See Airline SettingsAccess to Booking & Dispatch and Route Defaults pages ## Related - Bookings — booking system overview - Routes — route management - Routings — routing configuration - Callsign Parameters — airline callsign codes and fleet assignments --- # PIREP & Reward Settings Configure PIREP appeals, diversion behaviour, flight time awards, point settings, and Airport Manager bonuses. PIREP & Reward Settings control how PIREPs are handled after filing — appeal options, diversion behaviour, which route types earn hours and points, and Airport Manager bonuses. ## Accessing PIREP & Reward Settings In Orwell, go to Settings → PIREP Settings and Settings → Reward Settings. You need the Can See Airline Settings permission. ## PIREP Review ### Appeal Settings By default, pilots can comment on rejected or invalidated PIREPs to dispute them. These toggles replace the commenting system with a link to an external appeal process instead. ToggleDescriptionRejected PIREP Appeal OffsiteDisables commenting on rejected PIREPs. Shows the appeal URL instead.Invalidated PIREP Appeal OffsiteDisables commenting on invalidated PIREPs. Shows the appeal URL instead.Appeal URLLink to your appeal procedure or form. Required when either toggle above is enabled. ### PIREP Reply Window When staff mark a PIREP as Reply Needed, the pilot is blocked from booking new flights until they respond. The PIREP Reply Window sets how many days the pilot has to reply before the PIREP is automatically invalidated. The default is 7 days; any value from 0 to 365 is accepted, where 0 means the PIREP becomes eligible on the next nightly run. Auto-invalidation runs nightly. When a PIREP is auto-invalidated: - The PIREP is set to Invalidated — the pilot receives no time and no points, the same as a staff invalidation - The Reply Needed flag is cleared and the pilot can book flights again immediately - The PIREP's action log records "Auto-invalidated - no pilot response within X days" **The Clock Starts at Reply Needed**: The reply window counts from the moment the PIREP was flagged as Reply Needed, not from when it was filed. If staff flag the same PIREP again later (for example after reprocessing), the window restarts. ### Diversion Settings Controls what happens when a pilot lands at an airport other than their intended destination. These settings only take effect when the "Landing Away From Destination" AutoReject rule is enabled. Landed at Company Airport (airport exists in your route network): OptionWhat HappensContinue from said company airportPilot stays at the diversion airport.Move to Intended Arrival AirportPilot is relocated to the original destination.Move to Departure AirportPilot is relocated back to the origin.Book empty transfer to intended arrivalSystem books a repositioning flight to the destination.Book scheduled flight to intended arrivalSystem books a scheduled flight to the destination.Book empty transfer to departure airportSystem books a repositioning flight back to the origin.Book scheduled flight to departure airportSystem books a scheduled flight back to the origin.Let Pilot ChoosePilot picks from the available options. Landed at Non-Company Airport (airport not in your route network): OptionWhat HappensMove to Departure AirportPilot relocated to origin.Move to Intended Arrival AirportPilot relocated to destination.Let Pilot ChoosePilot picks. ## Reward Settings ### Flight Time ToggleDescriptionInclude Taxi TimeTaxi time is included in the PIREP's flight time and counts towards rank progression.Repositioning HoursAward hours for PIREPs flown via Repositioning route type.Training HoursAward hours for PIREPs flown via Training route type.Charter HoursAward hours for PIREPs flown via Charter route type. ### Point Settings ToggleDescriptionInclude Bonus Points for RankBonus points are treated as regular points for rank calculations.Repositioning PointsAward points for PIREPs flown via Repositioning route type.Training PointsAward points for PIREPs flown via Training route type.Charter PointsAward points for PIREPs flown via Charter route type. ### Airport Manager Rewards When enabled, Airport Managers receive bonus points with every PIREP they file. - Award Manager Points — enable or disable the bonus. - Bonus Points Amount — how many bonus points per PIREP (visible when enabled). - As Percentage — when enabled, the bonus points value is treated as a percentage of the base PIREP score rather than a fixed amount. - Bonus Name — optional custom display name for this bonus. ### Staff Bonus Rewards When enabled, all staff members receive bonus points with every PIREP they file. This rewards staff for their contributions to the Virtual Airline. - Enable Staff Bonus — enable or disable the bonus for staff members. - Bonus Points Amount — how many bonus points per PIREP. - As Percentage — when enabled, the bonus points value is treated as a percentage of the base PIREP score rather than a fixed amount. Use the toggle to swap between modes. - Bonus Name — optional custom display name for this bonus (e.g., "Staff Reward"). **How Bonus Points Stack**: Airport Manager Bonus, Staff Bonus, and Badge Bonus are all calculated independently against the base PIREP score and then summed. Percentage bonuses are not multiplicative — each percentage is applied to the original base score, not to accumulated bonuses. A pilot who qualifies for multiple bonus types receives all of them. For example, a staff member who is also an Airport Manager and holds a badge with bonus points will receive all three bonuses on every PIREP. ## Permissions PermissionGrantsCan See Airline SettingsAccess to PIREP Settings and Reward Settings pages ## Related - PIREPs — PIREP management and statuses - AutoReject Rules — diversion settings require the "Landing Away From Destination" rule - Scoring Rules — point calculation - Scoring Groups — scoring group configuration - Ranks — rank progression uses hours and points --- # Callsign Parameters Manage your airline's ICAO and IATA codes, ATC radio callsigns, operator names, and fleet assignments. Callsign Parameters define the airline identifiers used across vAMSYS — ICAO codes, IATA codes, ATC radio callsigns, and operator names. Each parameter can be assigned to specific fleets, controlling which callsigns are available for which aircraft types. ## Accessing Callsign Parameters In Orwell, go to Settings → Callsign Parameters. You need the Can Manage Callsign Parameter Settings permission. ## Parameter Fields ColumnDescriptionICAO Code3-character ICAO airline code (e.g. BAW, RYR). ASCII characters only.IATA Code2-character IATA airline code (e.g. BA, FR). ASCII characters only.ATC Radio CallsignHow ATC addresses the airline (e.g. "Speedbird", "Ryanair"). Shown in the dispatch table and used for VATSIM radar.Operator NameOperator display name shown in the dispatch table.FleetsWhich fleet types can use this callsign.ApprovedWhether the parameter is approved for use.ProtectedWhether exclusive rights are held by a Virtual Airline. Only visible on some parameters. ## Creating Parameters When creating a new callsign parameter, you enter the ICAO code, IATA code, ATC radio callsign, operator name, and fleet assignments. If the ICAO or IATA code you request matches a protected parameter (held exclusively by another Virtual Airline), you must provide a reason for the request. Your request, together with your full name and Virtual Airline support email, is sent to the rights holder for review. ## Editing Parameters Only approved parameters can be edited. You can change the ATC Radio Callsign, Operator Name, and Fleet assignments. **Fleet Removal**: Removing a fleet from a callsign parameter will deallocate it from any routes where it is already assigned. ## Permissions PermissionGrantsCan Manage Callsign Parameter SettingsAccess to Callsign Parameters management ## Related - Fleet — fleet types assigned to callsign parameters - Booking & Dispatch Settings — callsign defaults for new routes --- # ACARS Sounds Upload custom audio files that Pegasus plays at different flight phases — boarding, pushback, taxi, climb, cruise, descent, approach, landing, and unloading. ACARS Sounds lets you upload custom audio files that Pegasus plays at different flight phases. These default sounds apply to all flights — individual fleet types can override them with their own sounds. ## Accessing ACARS Sounds In Orwell, go to Settings → ACARS Sounds. You need the Can See ACARS Settings permission. **Route Type Restriction**: Sounds are only played on Scheduled and Charter route types. ## Flight Phase Sounds Each phase accepts multiple audio files. Upload any audio format. PhaseWhen It PlaysBoardingStart of flight tracking.PushbackPushback phase.TaxiTaxi phase detected.ClimbPassing 10,000 ft.CruiseCruise phase detected.DescentDescent phase detected.ApproachApproach phase detected.LandingTaxi-in after slowing down post-landing.UnloadingAfter engines off at the gate. **Fleet-Level Overrides**: Fleet-specific sounds override these defaults. If you set sounds on a fleet, those play instead of the sounds configured here. ## Permissions PermissionGrantsCan See ACARS SettingsAccess to ACARS Sounds page ## Related - Fleet — fleet-level sound overrides --- # Statistics VA-wide analytics dashboard with pilot counts, booking trends, PIREP breakdowns, fleet logbooks, and airport movement tables. The Statistics page is a comprehensive analytics dashboard for your Virtual Airline. It shows pilot account trends, booking activity, PIREP breakdowns, fleet performance, and airport movements — all filterable by date range. ## Accessing Statistics In Orwell, go to HQ → Statistics. You need the Can See Airline Statistics permission. ## Date Range Filter Use the Filter button to set a start and end date. All widgets update to show data within that range. The filter defaults to January 1st through today and respects your airline's configured timezone. ## Overview Metrics The overview section displays 30+ key metrics grouped by category. ### Pilot Accounts MetricDescriptionAccounts CreatedNew pilot registrations in the periodAccounts RemovedPilots removed from the airlineAccounts BannedPilots banned from the airlineNet DifferenceCreated minus removed — net pilot growth ### Infrastructure Counts of fleets, aircraft, airports, and sceneries created in the period. ### Liveries Liveries recorded, accepted, and rejected in the period. ### Bookings Total bookings made, plus a breakdown by network: Offline, VATSIM, IVAO, POSCON, APOC, and Others. ### PIREPs & Claims MetricDescriptionPIREPs FiledACARS-tracked flight reports (excludes claims)Claims MadeManual flight claims submittedClaims AcceptedClaims approved by staffClaims RejectedClaims denied by staff ### PIREP Status Breakdown of PIREPs by final status: manually accepted, automatically accepted, rejected, and invalidated. ### Gamification Badges created and awarded, plus total points and bonus points awarded in the period. ### Operations MetricDescriptionEvents CreatedActivity events created in the periodTime FlownTotal flight hoursDistance FlownTotal nautical milesFuel UsedTotal fuel consumption in kilograms ## Charts ### Live Flights A line chart showing concurrent flights on the network over time. Three lines show the maximum, average, and minimum number of simultaneous flights. The time resolution adjusts automatically based on your date range — from 5-minute intervals for a single day up to daily intervals for longer periods. ### PIREPs Filed A daily count of PIREPs filed over the selected period. ### Landing Rate Daily average landing rate for scheduled flights over the selected period. ## Tables ### Fleet Logbook A per-fleet-type breakdown of operational statistics. ColumnDescriptionFleetFleet type nameFlightsTotal flights completedPassengersTotal passengers carriedCargoTotal cargo weight (respects your unit preference)Air TimeTotal airborne timeDistanceTotal nautical milesFuelTotal fuel used (respects your unit preference)Takeoffs / LandingsDay and night counts for both takeoffs and landings The table is sortable by any column and can be filtered by aircraft code. ### Airport Movements A per-airport breakdown of traffic activity. ColumnDescriptionAirportICAO/IATA identifierTotal MovementsAll takeoffs and landings combinedTakeoffsTotal, day, and night takeoffsLandingsTotal, day, and night landings The table is sortable by any column and searchable by ICAO or IATA code. ## Permissions PermissionGrantsCan See Airline StatisticsAccess to the Statistics page ## Related - Pilots — individual pilot statistics - PIREPs — PIREP management - Phoenix Dashboard Editor — dashboard statistics components --- # Billing Manage your Virtual Airline subscription, view invoices, and update payment details. The Billing page lets airline owners manage their vAMSYS subscription — choose a plan, update payment details, view invoices, and manage the subscription lifecycle. ## Accessing Billing In Orwell, go to HQ → Billing. Only Airline Owners can access this page — it is not controlled by a staff permission toggle. ## Subscription Plans PlanPriceMonthly£25/monthYearly£250/year **Legacy Plans**: Airlines that migrated from earlier vAMSYS versions may be on legacy plans at different price points. These plans are no longer available to new subscribers. ## Trial Period Every new Virtual Airline starts with a 14-day free trial. You can start your subscription after a 4-day evaluation period — this gives you time to set up your VA and decide if vAMSYS is right for you. Starting your subscription ends the trial immediately. If the trial expires without an active subscription, the Virtual Airline is deleted. ## Managing Your Subscription The Billing page links to a Stripe-powered billing portal where you can: - Subscribe — select a monthly or yearly plan and enter payment details - Change plan — switch between monthly and yearly billing. Charges are pro-rated automatically. - Update payment method — change your card or billing details - View invoices — download past invoices - Cancel — cancellation takes effect at the end of the current billing period. No refunds are issued. **Cancellation**: Cancelling your subscription will result in your Virtual Airline being deleted at the end of the billing period. ## Incomplete Payments If a payment fails, a warning appears on the Billing page. Use the Manage Subscription button to complete the payment promptly — unresolved payment issues may result in your Virtual Airline being deleted. ## Terminate Trial Owners on a trial can terminate it early from the Billing page. This permanently deletes the Virtual Airline and requires confirmation. All airline owners are notified by email. ## Payment Security All payment processing is handled by Stripe. Your card details never touch vAMSYS servers. ## Related - Getting Started — initial VA setup and trial --- # Discord Integration Connect your Discord server to vAMSYS for automatic role assignment, nickname management, and VA notifications. The vAMSYS Discord bot connects your Discord server to your Virtual Airline. It automatically assigns roles based on pilot ranks, manages member nicknames, and posts notifications for alerts, NOTAMs, badge awards, PIREPs, flights, and daily statistics. **Subscription Required**: Discord integration is only available to airlines with an active subscription. It is not accessible during the trial period. ## What the Bot Does - Assigns Discord roles based on pilot ranks — when a pilot is promoted, their Discord roles update automatically - Sets member nicknames using vAMSYS data (name, Pilot ID, or both) - Posts notifications to designated channels — alerts, NOTAMs, activities, badge awards, PIREP reviews, bookings, departures, landings, and daily VA statistics - Removes pilots from the Discord server when they are banned, removed for inactivity, or leave the VA - Supports multiple Virtual Airlines in a single Discord server ## Setting Up the Bot Setup is done partly in Discord and partly in Orwell. You need Manage Server permission on your Discord server (the server owner should handle the initial invite). ### Step 1: Open Discord Settings in Orwell Go to HQ → Settings → Discord Settings. This page shows the setup wizard and your airline's setup token. ### Step 2: Invite the Bot Click the Invite Bot button on the Discord Settings page. This opens the Discord authorization screen. The server owner (or someone with Manage Server permission) should authorize the bot. Do not untick any permissions — the bot needs Manage Roles, Manage Nicknames, Send Messages, Manage Messages, and View Channel to function. ### Step 3: Link the Bot In any channel on your Discord server, run the /link command. A dialog appears asking for an Airline Token. Copy the token shown in Orwell (Step 3 of the setup wizard) and paste it in. The bot verifies its permissions and links your server. ### Step 4: Verify the Connection Back in Orwell, click Check Connection. If successful, the page refreshes and shows your Discord channels and roles in the configuration form below. You can now set up notification channels and rank role mappings. ## Notification Channels Once the bot is connected, you can assign Discord channels for various types of notifications. Each channel also has an optional role mention — when a notification is posted, the specified role is @mentioned so those members get pinged. NotificationWhat Is PostedAlertsWhen a new Alert becomes visible. Checked every 5 minutes.NOTAMsWhen a new NOTAM becomes visible. Checked every 5 minutes.ActivitiesWhen a new Activity starts showing. Checked every 5 minutes.Badge AwardsWhen a pilot earns a badge.PIREP ReviewWhen a PIREP needs staff review. Best pointed at a staff-only channel.Booking / Departure / LandingWhen a pilot books a flight, takes off, or lands. Each has its own channel.VA Statistics (Full)Detailed daily statistics posted at midnight (your VA timezone). Best suited for a staff channel.VA Statistics (Simple)Summary daily statistics posted at midnight. More suitable for a public channel. All notification channels are optional. If you leave a channel empty, that notification type is simply not sent. ## Pilot Rank Roles Map each of your VA ranks to one or more Discord roles. When a pilot is promoted in vAMSYS, the bot automatically updates their Discord roles to match. Create the roles in Discord first, then select them on the Discord Settings page in Orwell. **Role Hierarchy**: The vAMSYS Bot's role must be positioned above all pilot rank roles in your Discord server's role list. The bot cannot assign roles that are at or above its own level. If you see permission errors, check the role order in Discord Server Settings → Roles. Each VA in a shared Discord server must use unique roles — the same Discord role cannot be assigned to ranks from different airlines. ### Auto-Assign on Join Enable the Automatically Assign toggle to have the bot assign roles and set nicknames automatically when a pilot joins your Discord server — provided they have already linked their Discord account to vAMSYS. If they have not linked yet, the bot sends them a message with a link to do so. ## Bot Commands All commands are run in Discord, not in Orwell. Most require Manage Server permission. CommandPermissionDescription/linkManage ServerLink your Discord server to a vAMSYS airline using the setup token from Orwell/unlinkManage ServerUnlink the server from all connected airlines. Existing roles are not removed./configManage ServerOpen the server configuration panel to set nickname format, separator, and a staff notification channel/setup-role-buttonServer OwnerCreate a customizable button that members click to request their pilot roles and nickname/resyncManage ServerBulk re-sync all member roles and nicknames with vAMSYS. Has a 6-hour cooldown. Supports a dry-run preview./healthcheckManage ServerRun diagnostic checks on the bot — database connection, API connectivity, permissions, and uptime/pingEveryoneCheck bot latency ## Nickname Configuration Use /config in Discord to set how member nicknames appear. There are four formats: FormatExampleName - Pilot ID (default)John Smith - ABC1234Pilot ID - NameABC1234 - John SmithName OnlyJohn SmithPilot ID OnlyABC1234 For formats that include both name and Pilot ID, you can choose a separator: space, dash (default), pipe, forward slash, backslash, or comma. Nicknames are truncated to 32 characters (Discord's limit) — the bot removes words from the end of the name while preserving the Pilot ID suffix. Nickname changes only take effect on new role requests; existing members must click the role request button again to update. ## How Pilots Get Their Roles There are two ways pilots receive their Discord roles: ### Role Request Button Use /setup-role-button (server owner only) to create a button in a channel of your choice. Members click it, the bot looks up their vAMSYS account via their linked Discord, and assigns the correct roles and nickname. If a pilot belongs to multiple VAs in the same server, they choose which Pilot ID to display — but they receive roles from all VAs regardless. If a member's Discord account is not linked to vAMSYS, the bot directs them to link it at https://auth.vamsys.io/user/social. ### Automatic on Join When Automatically Assign is enabled in Orwell, the bot handles new members joining the server: - Linked and a pilot — roles and nickname are assigned automatically. A welcome message is posted briefly in the first text channel. - Linked but not a pilot — the bot sends a message explaining they are not a pilot in any of the server's linked VAs. - Not linked — the bot sends a message (via DM or in-channel) with a link to connect their Discord account. ## Automatic Updates Once set up, the bot stays in sync with vAMSYS automatically: - Rank promotion — Discord roles are updated when a pilot's rank changes - Name change — Discord nickname is updated when a user changes their public name preference in vAMSYS (polled every 30 seconds) - Pilot removal — when a pilot is banned, removed for inactivity, or leaves the VA, the bot removes them from the Discord server ## Multiple Airlines Per Server One Discord server can host multiple Virtual Airlines. Each VA admin runs /link with their own token. Pilots who are members of multiple VAs in the same server receive roles from all of them. Nickname format and notification channel are server-level settings shared by all linked airlines; rank-to-role mappings and auto-assign are configured per airline in Orwell. ## Staff Notification Channel Separate from the VA notification channels configured in Orwell, the bot has its own staff notification channel set via /config in Discord. This receives operational messages: successful role assignments, permission errors, and system events. Point it at a staff-only channel. ## Permissions The bot requires these Discord permissions to function: - Manage Roles — to assign and remove pilot rank roles - Manage Nicknames — to set member nicknames - Send Messages — to post notifications and respond to commands - Manage Messages — to clean up temporary welcome messages - View Channel — to see channels it needs to post in The bot's role must be positioned above all pilot rank roles in your Discord role hierarchy. It cannot manage the server owner or users with roles higher than its own (Discord limitation). ## Removing the Bot If you remove the bot from your Discord server (kick or ban it), the airline is automatically unlinked from vAMSYS. Existing roles are not removed from members — you need to clean those up manually in Discord. To re-enable, invite the bot again and run /link with a fresh token. ## Orwell Permission Access to the Discord Settings page in Orwell requires the Discord Settings staff permission. ## Related - Alerts — create the alerts that get posted to Discord - NOTAMs — create the NOTAMs that get posted to Discord - Ranks — define the ranks that map to Discord roles - Badges — badge awards that trigger Discord notifications --- # How to Book a Flight Search routes, generate random flights, and dispatch your next flight from the Phoenix Flight Center. The Flight Center is your central hub for finding, dispatching, and managing flights. Whether you want to search for a specific route, generate a random trip, or browse staff-curated schedules, everything starts here. ## Finding a Flight There are several ways to discover flights in the Flight Center. Each entry point leads to the same dispatch process, so pick whichever suits how you like to fly. ### Book Flight Map Go to Flight Center → Book a Flight. The interactive map shows airports in your VA's network. Click an airport on the map to see available routes from that location. Your current position is highlighted so you can quickly find flights departing from where you are. The map and dispatch table both offer filters to narrow your options: - Departure / Arrival — Search for specific airports - Flight Type — Filter by route type (passenger, cargo, VFR, etc.) - Fleet / Aircraft Type — Restrict to specific fleets or aircraft type codes - Operator — Filter by the callsign operator (useful if your VA operates multiple brands) - Tags — Filter by route tags if your VA uses them - Flight Length — Set minimum and maximum flight times - Days of Operation — Filter routes by which days they operate If only one route matches your departure and arrival pair, you go straight to the dispatch page. If multiple routes exist between the same airports, you see a dispatch table where you can pick the specific route. **Next Departures**: If your VA has departure times enabled, you may see a "Next Hour" or similar time-window button at the top of the dispatch table. This filters routes to only show flights departing within that window, sorted by departure time. Useful for real-time-style operations. ### Available Destinations Go to Flight Center → Available Destinations. This map-based view answers the question "Where can I fly from here?" It shows every airport in the network that has outbound routes, and when you select one, it reveals all the destinations reachable from that airport. The same filters (flight type, fleet, operator, tags) are available to narrow the results. ### Flight Generator Go to Flight Center → Flight Generator. Instead of picking routes manually, the Flight Generator builds a multi-leg itinerary for you. It is ideal when you want to fly but have no particular destination in mind. Configure the generator with these options: - Generator Type — Random picks legs without constraints, Trip - One Airport Out flies out to a destination and returns, and Trip - Two Airports Out goes further before looping back - Legs to Generate — Choose between 2 and 10 legs - Starting / Final Airport — Optionally pin the start or end of your itinerary to a specific airport - Min / Max Leg Length — Set time boundaries for each individual leg - Fleet, Operator, Tags — Restrict the routes the generator can use - Exclude / Include Airports — Block certain airports or request the generator tries to include specific ones - Only Unique Airports — Prevents the generator from visiting the same airport twice (only available in Random mode) Click Generate and the system builds an itinerary showing each leg with departure, arrival, callsign, and flight time. You can then dispatch individual legs from the results. ### Curated Rosters Go to Flight Center → Curated Rosters. Your VA staff can publish pre-built flight schedules, themed events, or tour itineraries. Browse them here and filter by fleet, aircraft, starting airport, or tags. Some curated rosters may be rank-restricted, so you only see what is available to you. **Name May Vary**: Your VA can rename sections of the Flight Center. If you do not see "Curated Rosters" or "Flight Generator" by that exact name, look for similarly positioned menu items -- your VA may have customized the labels. ### Route Changes Go to Flight Center → Route Changes. This page displays four tables that help you stay on top of network updates: - Ending Routes — Routes that will stop operating within the next 14 days. Fly them before they are gone. - Ended Routes — Routes that have recently been retired. - Starting Routes — New routes launching in the next 14 days. Plan ahead for new destinations. - Started Routes — Routes that recently became active and are now bookable. ## Jumpseats If your VA has jumpseats enabled, you can reposition to a different airport without flying. The Jumpseat button appears at the top of the dispatch table when you are viewing routes from your current location. - By default, you can jumpseat to any airport reachable via routes from your current position. - If your VA has Jumpseat to Bases enabled, you can also jumpseat to airports marked as hubs or bases. - If Jumpseat Anywhere is enabled, every airport in the network is available. - If you are stuck at an airport with no outbound routes, the jumpseat option becomes available regardless of your VA's settings. ## Dispatching a Flight Once you select a route, you land on the dispatch page. This is where you configure the details of your flight before creating a booking. ### Aircraft Selection Depending on your VA's settings, you may see an aircraft type picker before the rest of the dispatch form appears. This happens when the route has multiple fleets assigned to it and the VA requires explicit aircraft selection. If only one fleet is available, or your VA does not enforce this, the system picks an aircraft automatically. You can change aircraft at any time using the dropdown or the aircraft picker on the dispatch page. If you have favorite aircraft set in your profile, the system prioritizes them when selecting the default. Aircraft currently booked by other pilots may be highlighted (depending on VA settings), but you can still select them. **Bypass Aircraft Picker**: If you find the explicit aircraft picker slows you down, you can disable it in My Profile → Account Settings → Global Preferences → vAMSYS Experience. ### Dispatch Details The dispatch form includes the following fields: - Aircraft — The selected aircraft, changeable via dropdown or picker - Callsign — Taken from the route. Depending on VA settings, it may be editable or auto-generated - Cost Index — A non-editable field pulled from the fleet, aircraft, or route configuration - Departure Time — Your estimated pushback time in UTC. The default is set to roughly 35 minutes from now. A time-setter hint helps you convert between your local timezone and UTC - Flight Level — Cruising altitude, pre-filled from the route if configured - Route — The flight plan route, selected from the routings configured by your VA - Payload — Passengers and hold luggage for passenger aircraft, freight for cargo aircraft, or container selection for container-type fleets. Load factors are calculated automatically and can be regenerated ### Flight Options - Network — Select which online network you plan to fly on (VATSIM, IVAO, etc.). Only networks where you have provided your ID in your profile settings are available. Select Offline if flying without a network. - Shared Cockpit — If available, select a shared cockpit partner - SimBrief Dispatch — If you have linked your Navigraph account, toggle this on to generate a full operational flight plan (OFP) through SimBrief. When enabled, additional SimBrief settings appear for maps, NOTAMS, step climbs, alternates, and fuel options When you are satisfied with your selections, click Book Flight to create the booking. ## Your Booking After dispatching, you are taken to the booking page. This is your pre-flight briefing and the place you return to before starting your tracker. ### Booking Overview The booking page displays: - Flight map — Shows the planned route between departure and arrival - Booking details — Aircraft, callsign, flight number, departure time, and booking ID - Airport information — Departure and arrival airports with current METARs. Click the Airport Information button to view detailed briefings - Flight comparison — How other flights between these airports have performed in terms of landing rate, fuel use, flight time, and points earned - OFP details — If dispatched via SimBrief, the full operational flight plan with key data and the complete OFP document ### Booking Validity Bookings are live for a set period (typically 24 hours, but your VA can customize this). If you do not start tracking before the booking expires, it is automatically cancelled. If you have multiple active bookings, use the booking tabs at the top of the page to switch between them. ### Booking Actions Depending on your VA's configuration and how you dispatched, the booking page offers these actions: - Network Prefile — Send your flight plan to VATSIM, IVAO, or another supported network. Only available if you selected a network during dispatch - Open OFP — View your SimBrief operational flight plan as a PDF - Edit SimBrief OFP — Opens SimBrief to modify the OFP. Changes are automatically imported back into vAMSYS - Open Navigraph Charts — Opens Navigraph Charts with the charts for your route pre-loaded - SimBrief Downloads — Download SimBrief files for your flight planning software - Make Additional Booking — Go back to the flight map to book another flight while keeping this one active - Cancel Booking — Cancels the booking and returns you to the flight map - Cancel & Rebook — Cancels the booking and takes you directly back to the dispatch page for the same route - Flight Tracker Links — Flightradar24, RadarBox, and FlightAware links (if enabled by your VA) ## Favorite Airports and Aircraft You can mark airports and aircraft as favorites directly from the booking and dispatch pages. - Favorite airports get a special marker on the flight map, making them easy to spot when browsing routes - Favorite aircraft are prioritized when the system selects a default aircraft for dispatch. If you have linked your Navigraph account, you can also assign a SimBrief aircraft profile to your favorite ## Typical Booking Workflow 1. Discover — Use the flight map, available destinations, flight generator, curated rosters, or route changes to find a flight 2. Select — Pick a route from the dispatch table (or go directly if only one route matches) 3. Dispatch — Configure your aircraft, callsign, departure time, payload, network, and SimBrief options 4. Review — Check your booking page for METARs, OFP, and flight comparison data 5. Fly — Start your tracker and complete the flight before the booking expires **SimBrief Integration**: For the best experience, link your Navigraph account in your profile settings. This enables SimBrief dispatch, automatic OFP generation, and network prefiling — all from within vAMSYS. --- # PIREPs & Claims View your flight reports, understand scoring panels, and file manual claims when ACARS tracking is unavailable. PIREPs (Pilot Reports) are how you earn hours and points towards rank progression and activity completion. Every flight tracked by Pegasus ACARS generates a PIREP. You can view all your PIREPs in Phoenix, see detailed breakdowns of each flight, and leave comments if staff need more information. ## Your PIREP Table To view your PIREPs, go to Flight Centre → PIREPs in Phoenix. This page shows every flight report filed under your account, sorted by most recent first. ### Table Columns Each row in the table displays key information about a flight: - Callsign — The callsign and flight number used for the flight - Departure / Arrival — Airport codes and names for your origin and destination - Aircraft — Registration, fleet code, and fleet name of the aircraft used - FPM — Landing rate in feet per minute - G — G-force at touchdown - Time — Credited flight time in hours and minutes - R-Pts — Regular points earned from the flight scoring rules - B-Pts — Bonus points from activities (tours, events, etc.) - Status — Current PIREP status with the date it was filed You can also toggle additional columns like ID, PIREP Type, Route Tag (if your Virtual Airline uses route tags), and Reply Needed using the column toggle button. ### Filtering and Searching The PIREP table has extensive filtering options displayed above the table. You can combine multiple filters to narrow down your results: - Departure / Arrival Airport — Search by airport name, ICAO, or IATA code - Fleet — Filter by aircraft fleet type - PIREP Type — Show only scheduled flights, claims, or transfer PIREPs - Reply Needed — Filter to PIREPs where staff have requested a reply - PIREP Status — Filter by Accepted, Rejected, Invalidated, or Awaiting Review - Points / Bonus Points Range — Set minimum and maximum point values - FPM Range — Filter by landing rate range - Filed Date — Filter by a date range - Flight Time — Filter by flight duration range - Route Tag — Filter by route tags (only visible if your Virtual Airline uses them) You can also use the search bar to search by PIREP ID or callsign. Click the eye icon on any row to open the full PIREP detail page. ## PIREP Statuses Every PIREP has a status that tells you where it is in the review process: - Processing — Your PIREP has been received and the system is scoring it. This usually takes a few seconds after landing. - Accepted — The PIREP passed all checks. Hours and points have been fully awarded and count towards your rank progression and statistics. - Awaiting Review — The PIREP triggered one or more autoreject conditions and has been flagged for manual review by staff. You can still see the PIREP details while it is under review. - Rejected — Staff have reviewed the PIREP and rejected it. You receive only the credited flight time but no points. Rejected PIREPs may still count towards some activity requirements depending on your Virtual Airline settings. - Invalidated — Staff have invalidated the PIREP entirely. You receive no time and no points for this flight. - Error — Something went wrong during processing. This is rare and usually resolves automatically. If it persists, contact your Virtual Airline staff. **Reply Needed**: If you see a "Reply Needed" badge on a PIREP, staff have requested that you leave a comment before you can book and fly additional flights. Open the PIREP and use the comment system to respond. ## PIREP Detail View Click the eye icon on any PIREP to open its full detail page. The detail view uses a two-column layout with the main flight information on the left and summary panels on the right. ### Left Column - Status Panel — Shows the current PIREP status, your pilot details and rank, and any autoreject reasons that triggered review. If the PIREP is a claim, it also displays the claim message you submitted. When a reply is needed, this panel shows a prompt to check comments. - Flight Map — An interactive map showing the flight path. The coloured line represents the actual flown path, graded by altitude. Additional lines show the planned route. - Flight Profile Chart — A chart plotting altitude and groundspeed over time, with event markers for pushback, engine start/stop, flap changes, gear up/down, stability gates, and touchdown. Not shown for claims. - Departure Analysis — Detailed analysis of the departure phase. Not shown for claims. - Approach/Landing Analysis — Detailed analysis of the approach and landing. Not shown for claims. - Flight Details — Comprehensive flight information including aircraft, livery, actual departure and arrival times, block time, and touchdown data (gear status, pitch, roll, speed, runway, and landing distance). - Flight Dispatch — If the flight was dispatched via SimBrief, this section shows dispatch information and a link to the OFP (Operational Flight Plan). - Flight Data — The full Pegasus event log for the flight. Each entry includes the time of the event, time to departure or landing, the log message, and its type. You can filter the log by event type. Not shown for claims. ### Right Column - Comments — Where you and staff can exchange messages about the PIREP. Only visible on your own PIREPs. See the Comments section below for details. - Credits / Time — Shows the time breakdown for the flight: credited time (the hours you are awarded), block time (gate to gate), flight time (wheels up to touchdown), scheduled time, paused air time and paused ground time. For claims, only the credited time is shown. - Points — A detailed breakdown of every scoring rule applied to the flight. Each line shows the rule name and points awarded (positive or negative). Below the individual rules, you see the flight score total. If the flight earned bonus points from activities, those are listed separately with their own total, followed by a grand total. - Route — Departure and arrival airport details, callsign, flight number, the company route (if assigned), and your pilot route (if different from the company route). Also shows scheduled departure/arrival times and duration. - Activity Logbooks — Shows which activities (tours, rosters, events) this flight contributed to. - METAR — Weather reports for the departure airport at the time of departure and the arrival airport at the time of landing. ## Comments The Comments panel appears on the right side of your PIREP detail page. Both you and Virtual Airline staff can leave comments on the PIREP. When you add a comment, the PIREP is automatically returned to the review queue so that staff see it. This is useful if your PIREP was flagged and you want to explain a situation or respond to staff questions. If your Virtual Airline has configured an external appeals process for rejected or invalidated PIREPs, the comment form will instead direct you to the appropriate URL to make your appeal there. **Diversions**: If the system detects that your flight involved a diversion, you may be prompted to submit a Diversion Report via a modal. You will need to explain the reason for the diversion and, depending on your Virtual Airline settings, choose what happens next (continue from the diversion airport, be moved to your original departure or arrival, or have a transfer flight booked for you). ## Claims Claims (also called Manual PIREPs) let you file a flight report when Pegasus ACARS was not able to track your flight. This might happen if your ACARS disconnected, you flew on a device without the tracker, or something else prevented normal tracking. **Not All VAs Use This**: Claims are an optional feature. If you do not see the "Manual PIREP / File a Claim" button on your booking page, your Virtual Airline has not enabled claims. ### How to File a Claim 1. Go to Flight Centre → Bookings and open the booking for the flight you want to claim 2. In the booking sidebar, click Manual PIREP / File a Claim 3. Fill in the claim form with the required information (see below) 4. Submit the claim Once submitted, the booking is removed and you are moved to the arrival airport, just like a normal flight. The claim PIREP is placed in the review queue for staff to process manually. ### What Information Is Needed The claim form shows your departure and arrival airports (from the booking) and asks you to provide: - Departure Time — When you departed, in Zulu (UTC) time. Must be in the past. - Arrival Time — When you arrived, in Zulu (UTC) time. Must be after your departure time. - Message — An explanation for staff describing why you are filing a claim and any details that may help them process it. - Proof of Flight — At least one piece of evidence that you completed the flight. You can add up to five items, and each can be either an uploaded image (screenshot) or a link (for example, to a VATSIM or IVAO flight record). This is what staff use to verify your claim. Your Virtual Airline may also display a custom message at the top of the claim form with their specific requirements for what they expect in a claim submission. ### Viewing Your Claims To see all your claims, go to Flight Centre → Claims. This page shows a dedicated table with your claim history, including: - Claim ID and PIREP ID — Reference numbers for the claim and its associated PIREP - Departure / Arrival — Airports and times you provided - Status — The current claim status (see below) - Needs Reply — Whether staff have requested additional information from you - Claim Date — When you submitted the claim From this table, you can click the view icon to open the PIREP detail page for an accepted or reviewed claim, or delete a claim that is still pending (before staff have started reviewing it). ### Claim Statuses - Pending — Your claim has been submitted and is waiting to be picked up by staff. You can still delete the claim at this stage. - Waiting — Staff are reviewing your claim. It has been picked up but no decision has been made yet. - Accepted — Staff have accepted your claim. Hours and points are awarded based on what staff enter during the review. The time awarded may differ from your claimed times, as staff compare your claim against average route data. - Rejected — Staff have rejected your claim. No hours or points are awarded. ### Claims and Activities Claims are treated as regular PIREPs for activity purposes. An accepted claim counts towards initial and ongoing activity requirements, tour and roster leg completion, and event participation. Rejected claims may also count towards some activity requirements, depending on your Virtual Airline settings for whether rejected PIREPs count. --- # How to Join Activities Browse tours, events, community goals, and challenges — then sign up and start flying. Activities are time-limited flying challenges organised by your Virtual Airline. They range from single-flight events to multi-leg tours, competitive challenges, and airline-wide community goals. This guide covers how to find them, what each type involves, and how to sign up. **Availability Varies by VA**: Activities are an optional module. If you do not see an Activities or Events page in Phoenix, your Virtual Airline has not enabled this feature. ## Where to Find Activities Most activities appear under Events in the Phoenix navigation. This page lists all current and upcoming activities you are eligible for — events, focus airports, tours, and rosters all appear here. Each activity card shows its name, dates, type, point reward, and your registration status. Community Goals and Community Challenges are the exception — they live under Community → Community Goals instead. When a goal or challenge is active, it may also appear as a top-level menu item. Curated Rosters are also separate — you will find them under Flight Centre → Curated Rosters. ### Filtering the List The Events page includes filters to help you narrow things down: - Event Type — Show only specific types such as events, tours, or rosters - Categories / Tags — Filter by tags your VA has applied to activities - Only Where I'm Registered — Narrow the list to activities you have already signed up for Click any activity card to open its detail page, where you can see the full description, map, airports or legs, restrictions, and registration controls. **Custom Names**: Your Virtual Airline may rename activity types — for example, calling Tours something like "Expeditions" or Events something like "Ops". The underlying mechanics remain the same regardless of what they are called. ## Events Events are the most common activity type. They run for a defined period and reward you for flying specific routes or between specific airports. There are two styles: - Airport-based — Fly between designated departure and arrival airports. The activity page shows which airports qualify and may display an interactive map with the eligible connections. - Route-based — Fly specific routes from the schedule. The qualifying routes are listed on the activity page and you can book directly from there. To participate, simply fly a qualifying flight while the event is active. If the event requires registration, you must register first. Points are awarded based on when your flight takes off and/or lands relative to the event window — check the detail page for the exact timing rule. ## Tours A tour is a multi-leg activity where you fly a sequence of flights in order. Think of it as a road trip with scheduled stops — you must complete each leg before moving on to the next. Each leg defines a departure and arrival airport (and sometimes a specific route). The activity page shows a table of all legs with their status: Incomplete, Booked, or Completed. A map visualises the route across all visible legs. Tours always require registration. After registering, you can book each leg directly from the activity page using the Book Flight button next to each leg. Legs must be flown in order — you cannot skip ahead. **Hidden Legs**: Some legs may be hidden until a certain date. The table will show when they become visible. If you happen to fly a hidden leg before it is revealed, it still counts towards your progress. Points for tours can be awarded per leg as you complete them, or as a lump sum when you finish the entire tour — it depends on how your VA has configured it. ## Rosters Rosters work like tours but with an important addition: each leg assigns a specific aircraft. When you book a roster leg, the designated aircraft is automatically selected at dispatch and cannot be changed. This simulates a realistic pilot schedule — a "day in the life" flying a particular airframe. Like tours, rosters require registration. The activity page table shows each leg with its departure, arrival, callsign, flight time, distance, and the specific aircraft registration you will fly. Book and fly the legs in order. ## Curated Rosters Curated Rosters are a streamlined variant of rosters that appear under Flight Centre → Curated Rosters rather than the Events page. They represent a specific aircraft schedule — for example, "A Day in G-LUJA" — and show the map and leg list for that aircraft. Registration for curated rosters is optional and only tracks your progress. Curated rosters do not award bonus points. ## Focus Airports A Focus Airport activity highlights a single airport. Any flight that departs from or arrives at that airport during the active period earns you points — no registration required (unless the VA has set it up that way). The activity detail page shows the featured airport, a map, connected airports with routes, and Book Flight From / Book Flight To buttons so you can quickly dispatch a flight without leaving the page. Focus Airports may also appear as markers on the Book Flight and Destination maps if your VA has enabled that option. ## Community Goals Community Goals are collective targets where every pilot in the airline contributes. Rather than individual completion, the entire airline works towards a shared objective — for example, transporting 1,000,000 passengers or flying 50,000 nautical miles. Goals can track: - Passengers transported - Cargo transported - Number of flights - Distance flown - Time flown There is no registration — every qualifying PIREP you file automatically counts towards the goal. The Community Goals page shows a progress bar, the overall target, how many pilots have contributed, and your personal contribution. If the goal reaches 100%, a completion bonus may be awarded. Your VA may set filters that determine which flights qualify — for example, only flights above a certain distance, or only flights using specific aircraft. These requirements are listed on the goal page. **Tiered Rewards**: Some goals use tiered rewards. Pilots who contribute the most earn a higher point multiplier. For example, the top 10% of contributors might earn 5x the base bonus, while the top 25% earn 4x. Your current tier and ranking are shown on the goal page. ## Community Challenges Community Challenges add a competitive twist to community goals. Instead of one shared target, pilots are split into teams that compete against each other. The team with the highest progress — or the first to reach its target — wins. Teams are formed automatically based on criteria set by your VA. For example, Team Longhaul vs Team Shorthaul, or Day Flights vs Night Flights. Your PIREPs are assigned to a team based on the flight you flew — you do not choose a team manually. Like community goals, there is no registration. Every qualifying PIREP is evaluated and assigned to a team. The challenge page shows each team's progress, participant counts, and — once the challenge ends — the winner. Pilots who contributed to the winning team earn bonus points. You can contribute to more than one team if your different flights match different team criteria. Your personal contribution, flights count, and ranking within each team are all visible on the challenge page. ## How Registration Works Some activities require you to register before you can earn points. Tours and rosters always require registration. Events and focus airports may or may not — check the activity card or detail page. ### Registering for an Activity 1. Open the activity from the Events page 2. Look for the Registration section in the right-hand sidebar 3. Click Register 4. For tours and rosters, a logbook is automatically created to track your leg-by-leg progress Registration is only possible during the registration window — the activity page shows when registrations open and close. If you arrive after registrations have closed, you will not be able to sign up. ### Cancelling Registration You can cancel your registration at any time by clicking Cancel Registration on the activity page. For tours and rosters, cancelling also removes your progress — your logbook entries for incomplete legs are deleted. You will be asked to confirm before this happens. ### Who Can See Your Registration Activities that require registration display a list of all registered pilots. Your entry is highlighted in the list. Other pilots can see who has signed up. ## Restrictions Activities may have restrictions that limit who can participate or what flights qualify. These are always shown on the activity detail page under a Restrictions section: - Ranks — Only pilots holding certain ranks can see or join the activity - Callsigns — Flights must use specific callsign prefixes - Fleets — Flights must use aircraft from specific fleets - Networks — Flights must be flown on specific networks (VATSIM, IVAO, offline, etc.) - Landing rate — Some activities require your landing to fall within a certain range, which also means manual PIREPs / claims are not accepted If an activity is rank-restricted and you do not hold the required rank, it will not appear in your Events list at all. ## Points and Rewards Completing an activity earns bonus points. The amount is shown on the activity card and detail page. Points can be a fixed value or a multiplier applied to the points your PIREP already earned. For tours and rosters, points may be awarded per leg or only when you complete the entire activity — check the detail page. Some activities can only be completed once. If repeat participation is not allowed, you will see a notice on the activity page and you will not be able to register again after completing it. For repeatable tours and rosters, once you finish all legs you can start again from the activity page if the activity is still running. ## Tracking Your Progress Each activity page includes a Logbook section that shows who has completed or started the activity. For tours and rosters, this includes a per-pilot breakdown of how many legs have been completed. For tours and rosters, the legs table shows your personal status for each leg. Completed legs link to the corresponding PIREP so you can review the flight. For community goals and challenges, your personal contribution (total contributed and number of flights) is shown on the goal or challenge page, along with your ranking and tier if applicable. ## Quick Reference Activity TypeWhere to Find ItRegistrationHow to ParticipateEventEvents pageOptionalFly qualifying routes or airport pairsFocus AirportEvents pageOptionalFly to or from the featured airportTourEvents pageRequiredRegister, then fly legs in orderRosterEvents pageRequiredRegister, then fly legs in order with assigned aircraftCurated RosterFlight Centre → Curated RostersOptional (tracking only)Fly legs with assigned aircraft; no points awardedCommunity GoalCommunity → Community GoalsNoneFly qualifying flights; contribution is automaticCommunity ChallengeCommunity → Community GoalsNoneFly qualifying flights; team assigned automatically --- # Your Pilot Profile Your flight statistics, logbook, badges, flight map, and promotion progress — all in one place. Your pilot profile is the hub for everything about your flying career within a Virtual Airline. It brings together your statistics, recent activity, rank progress, badges, logbook, and a visual flight map — giving you (and others) a clear picture of your achievements. **Who Can See Your Profile?**: Other pilots can view your profile if you have profile visibility enabled in your privacy settings. You always see your own profile in full. VA staff can also view pilot profiles regardless of your privacy settings. ## Profile Overview When you open your profile from My Profile, you land on the overview page. This is a snapshot of who you are as a pilot. On the right-hand side, you will see your name, pilot username (your unique ID within this VA), your current rank epaulette, and rank name. If you have linked your YouTube or Twitch accounts and have social visibility enabled, those links appear here too. The main content area shows several key sections: ### Statistics Summary At the top of the overview, a tabbed statistics panel lets you view your numbers across different time periods: - Today and Last 24 Hours — your most recent activity - Yesterday and 30 Days — short-term performance - This Year, Last Year, and All Time — the bigger picture - Details — your registration date, total unique airports visited, and your current hub location For each time period, the statistics cards show: - PIREPs — broken down by status: accepted, rejected, invalidated, and manual - Points — regular and bonus points, plus your average points per flight - Time & Distance — total flight time and distance flown in nautical miles - Pax & Freight — total passengers and cargo transported, with per-flight averages - Fuel & Landing Rate — total fuel used, average fuel per flight, and your average landing rate in FPM Below the statistics, you will also see your most popular airports and most popular aircraft types in the sidebar, and your recent PIREPs and bookings in the main area (if PIREP visibility is enabled in your privacy settings). ### Activity Status If your Virtual Airline has activity requirements enabled, an activity status indicator appears on your profile overview. This shows whether you are currently active, on grace, or on holiday — so you always know where you stand. ### Friends When viewing another pilot's profile, you can send or remove friend requests (if both parties have friend visibility enabled in their privacy settings). Friends on vAMSYS can unlock social scoring bonuses like Group Flight and Shared Cockpit points. ## Rank Tracker The Rank Tracker sits on your profile overview and shows your progress toward your next rank. It displays the next rank's name and epaulette image alongside four progress bars: - Hours — flight hours accumulated vs. the requirement, with hours remaining shown - Points — total points earned vs. the requirement - Bonus Points — bonus points earned vs. the requirement - PIREPs — total PIREPs filed vs. the requirement Each bar shows a percentage and tells you exactly how many more hours, points, bonus points, or PIREPs you need. Your Virtual Airline sets the requirements for each rank, so the thresholds vary between VAs. If you have already reached the highest rank, the tracker lets you know — there is nothing left to chase (except bragging rights). **How Ranks Work**: Ranks are awarded automatically by vAMSYS based on your cumulative hours, points, bonus points, and PIREPs. You must meet all of the criteria set for a rank to be promoted. Your VA may also have Honorary Ranks — special ranks assigned by staff for things like winning events or being a real-world pilot. If you hold an Honorary Rank, you can choose which rank to display in your preferences. ## Statistics Dashboard The dedicated Statistics page goes deeper than the overview summary. Access it by clicking the Statistics button on your profile overview. The page is divided into two sections: charts and the logbook. ### Charts The top section contains eight charts arranged in a grid, giving you a visual breakdown of your flying habits: - Aircraft Type — which aircraft types you fly most often - Operator — flight distribution across different operators (callsign prefixes) - Network — how your flights split between VATSIM, IVAO, POSCON, APOC, and offline - Daytime Stats — breakdown of day vs. night takeoffs - Route Type — scheduled, repositioning, charter, training, and other flight types - Simulator — which flight simulators you use (MSFS, X-Plane, Prepar3D, etc.) - Event Flights — participation in VA events vs. regular flights - Daytime Landings — day vs. night landings Below the grid, two wider charts track trends over time: - Flights per Month — your monthly flight count, making it easy to spot busy and quiet periods - Landing Rate per Month — your average landing rate (FPM) per month, so you can track whether your landings are improving ### Logbook At the bottom of the Statistics page sits your Logbook — a detailed table that aggregates your flight history by aircraft type. For each aircraft type you have flown, the logbook shows: - Flights — total number of flights - Passengers — total passengers carried - Freight — total cargo transported - Air Time — cumulative time in the air - Distance — total distance flown in nautical miles - Fuel Used — total fuel consumed - Takeoffs (Day / Night / Total) — broken down by time of day - Landings (Day / Night / Total) — broken down by time of day - Average FPM — your average landing rate for that aircraft type A totals row at the bottom sums everything up across all aircraft types, giving you a complete career overview at a glance. ## Flight Map The Flight Map is an interactive, full-width map that visualises every route you have flown. Access it by clicking the Flight Map button on your profile overview. Airports you have visited are shown as markers on the map, with lines connecting departure and arrival airports for each route. Hub airports are highlighted so you can see your VA's base of operations. The map includes several filters to help you focus on specific flights: - Date range — narrow down to a specific time period - Flight type — filter by scheduled, repositioning, charter, or training flights - Fleet — show only flights with a specific aircraft type - Operator — filter by callsign operator - Tags — filter by route tags set by your VA - Departure / Arrival airports — see only flights to or from specific airports You can also toggle Show Path to display the actual flight paths (based on your Pegasus position reports) rather than straight lines between airports. If you enable Altitude Gradient, the paths will be coloured based on your altitude — a nice way to see your climb and descent profiles. **Navigraph AMDB**: If you have a Navigraph subscription linked to your vAMSYS account, the flight map will display Navigraph AMDB airport overlays on the map. ## Badges The Badges section shows all badges you have earned within your Virtual Airline. Each badge displays its image, name, and the date you earned it. Clicking a badge takes you to the badge's detail page where you can see more information about it. Badges can be earned in two ways: - Automatically — awarded when you meet specific criteria (like flying to certain airports, reaching a landing rate target, or hitting a flight count milestone). These are checked with each PIREP you file. - Manually — awarded by VA staff for special achievements like winning a screenshot competition, participating in events, or other recognitions. Your VA may use a custom name for badges — so they might appear as "Awards", "Achievements", or something else entirely. Not all VAs enable badges, so this section only appears if badges are active. ## Profile Sidebar The sidebar on your profile overview includes a couple of extra features worth mentioning: - Popular Airports — the airports you visit most frequently - Popular Aircraft — the aircraft types you fly most often - Copy Profile URL — when viewing another pilot's profile, you can copy a direct link to share it ## Privacy & Visibility Your profile visibility is controlled through your privacy settings. Key toggles include: - Profile visibility — whether other pilots can view your profile at all - PIREP visibility — whether others can see your recent PIREPs and bookings on your profile - Friend requests — whether other pilots can send you friend requests If another pilot has their profile visibility disabled, you will see a 404 page when trying to visit their profile (unless you are VA staff). --- # How to Update Your Settings Change your name, avatar, and privacy preferences in Phoenix. vAMSYS gives you two places to manage your settings: Pilot Preferences in Phoenix (per-airline) and Global Preferences in your vAMSYS Account (across all airlines). This guide covers both. ## Where to Find Your Settings - Pilot Preferences — Go to My Profile → Settings. These settings apply only to the Virtual Airline you are currently viewing. - Privacy and Account Preferences — Click the user dropdown in the top-right corner, then My vAMSYS Account → Preferences. These settings apply across all your Virtual Airlines. You will need to confirm your password. ## Pilot Preferences These settings are specific to each Virtual Airline. If you fly with multiple airlines, you can configure them independently. - Use Imperial Units — When enabled, all weights are shown in pounds instead of kilograms. - Prefer Honorary Rank — If your VA has awarded you an honorary rank, enabling this displays it instead of your regular pilot rank in flight lists, leaderboards, and elsewhere. - Preferred Network — Sets the default online network selected when you dispatch a flight. Options include Offline, VATSIM, IVAO, POSCON, APOC, PilotEdge, FSCloud, SayIntentions, and Other. VATSIM, IVAO, POSCON, and APOC only appear if you have linked those network IDs to your vAMSYS account. - SimBrief OFP Format — Chooses which OFP layout SimBrief uses when generating your flight plan. Some Virtual Airlines lock this to a specific format, in which case you will not be able to change it. - Marketing Communications — Allows the Virtual Airline to contact you with news, events, and promotions. Your first name, last name, and email are shared with the VA for marketing purposes. You can unsubscribe at any time. This option only appears if the VA has enabled marketing. After changing any pilot preferences, click Submit to save. **Missing a Network Option?**: If you don't see VATSIM, IVAO, POSCON, or APOC in the Preferred Network dropdown, you need to link that network to your vAMSYS account first. Click the **Missing Network?** hint next to the dropdown for a direct link to your account settings. ## Privacy Settings Privacy settings are global, meaning they apply across every Virtual Airline you belong to. You will find them under My vAMSYS Account → Preferences → Privacy. - Public Profile — When enabled, other pilots in your Virtual Airlines can view your profile page. When disabled, your profile is hidden from everyone except yourself and VA staff. - Public PIREPs — When enabled, other pilots can see your PIREPs. This has no effect if your profile is already set to private, since PIREPs are accessed through your profile. - Show in Flight Map, Lists and Leaderboards — Controls whether your name appears in leaderboard rankings, the live flight map, and pilot lists. When disabled, your name is obfuscated in these views. - Allow Friend Requests — Controls whether other pilots can send you friend requests. Disabling this does not remove existing friends. Privacy changes take effect immediately. There is no separate save button — each toggle updates as soon as you flip it. **Privacy Is Layered**: If you disable **Public Profile**, your PIREPs are automatically hidden from others as well, regardless of the Public PIREPs toggle. If you want PIREPs visible but your profile private, that is not possible — the profile must be public for PIREPs to be visible. ## vAMSYS Experience Settings Also found under My vAMSYS Account → Preferences, these options let you customise your overall vAMSYS experience. - Enable Beta Features — Opts you into the beta channel so you can try new features before they roll out to everyone. - Bypass Explicit Aircraft Selection — Some Virtual Airlines require you to manually confirm the aircraft variant when dispatching. This toggle skips that step, overriding the VA setting. ## Related - How to Book Holidays — Pause your activity requirements while you take time off. - Account Management — Merge accounts, reset pilot data, or delete your account. --- # Leaderboards & Badges Check your ranking against other pilots and browse the badges you can earn. The Community section in Phoenix includes leaderboards for tracking pilot rankings, a badge gallery for viewing achievements, and a team page showing VA staff. These features vary between Virtual Airlines — your VA decides which ones are enabled and how they are configured. ## Leaderboards Leaderboards rank pilots based on their flying activity. You can find them at Community → Leaderboard in Phoenix. ### Ranking Metrics Pilots are ranked by four metrics. You can switch between them using the sort buttons above the table: - Flights — Total number of completed PIREPs - Hours — Total credited flight time - Points — Total regular points earned from scoring rules - Bonus — Total bonus points earned ### Time Periods Leaderboards are broken down by time period. Use the tabs at the top to switch between: - 7 Days — The last seven days of activity - Month — The current calendar month - Last Month — The previous calendar month - This Year — The current calendar year - Previous Years — Individual tabs for each past year the VA has been active - All Time — Every flight since the VA was created ### Your Position A highlighted panel at the top of the leaderboard shows your personal ranking for the selected period, including your position out of total active pilots, your stats (flights, hours, points, bonus), and a trend indicator comparing your performance to the previous equivalent period. ### Position Changes For all periods except All Time, a Change column shows how each pilot's ranking has moved compared to the previous equivalent period. An upward arrow means the pilot has climbed in the rankings, a downward arrow means they have dropped, and a dash means there is no previous data to compare. ### Leaderboard Types Depending on how your VA is configured, you may see additional leaderboard types beyond the default global leaderboard: - Global Leaderboard — Rankings across the entire VA (always available) - Hub Leaderboards — Rankings filtered by hub. If your VA has enabled hub leaderboards, you can select a specific hub from the dropdown. - Online Network Leaderboards — Rankings filtered by online network. Your VA may show a combined "Online Leaderboard" covering all networks, or separate leaderboards for individual networks like VATSIM, IVAO, or others. **Not Seeing Hub or Network Leaderboards?**: These are optional features that your VA enables in their settings. If you only see the global leaderboard, your VA has not enabled hub or network leaderboards. ### Searching for a Pilot Use the search box above the leaderboard table to find a specific pilot by name. Only pilots who have chosen to appear in lists will show up in search results. ### Opting Out of Leaderboards If you prefer not to appear on leaderboards, you can disable the Show in Flight Map, Lists and Leaderboards toggle in your privacy settings. When this is turned off, your name appears as "Anonymous" to other pilots. VA staff can still see your entry. ## Badges Badges are awards that recognise your achievements and milestones. Browse all available badges at Community → Badges (your VA may use a custom name for this section, such as Awards or Achievements). **Not All VAs Use Badges**: Badges are an optional feature. If you do not see a Badges section in the Community menu, your VA has not enabled them. ### The Badge Gallery The badge gallery shows every badge your VA has created. For each badge, you can see: - Image — The badge icon - Name — The badge name - Category — The group the badge belongs to (e.g., Events, Milestones, Airports) - Description — What the badge is for - Recipients — How many pilots have earned the badge You can filter badges by category using the dropdown filter, and search by name. Click View Recipients on any badge to see the list of pilots who have earned it and when they received it. ### How Badges Are Earned There are two types of badges: - Automatic badges — Awarded by the system when you meet specific criteria. These are checked each time one of your PIREPs is processed. You do not need to do anything special to claim them; they are awarded as soon as you qualify. - Manual badges — Awarded by VA staff for things that cannot be automatically detected, such as competition wins, special recognition, or event participation. **Badge Timing**: Automatic badges are checked when PIREPs are processed, not in real-time. For example, a seniority badge based on account age triggers on a date, but it will not appear until your next PIREP is processed. ### Types of Automatic Badges Your VA can create automatic badges based on a wide range of criteria. Common types include: - Length of service — Membership milestones (e.g., 1 year, 5 years) - Flight milestones — Total PIREPs, flight hours, or distance flown - Point milestones — Accumulating regular, bonus, or combined points - Airport badges — Landing at, departing from, or visiting specific airports - Landing rate badges — Achieving a specific landing rate or landing within a certain FPM range a set number of times - Event and activity badges — Participating in events, tours, or completing roster flights - Transport badges — Transporting a total number of passengers or cargo Automatic badges can only be earned once per pilot. Manual badges can be awarded multiple times. ### Viewing Your Badges Your earned badges are displayed on your pilot profile under the Badges tab. Badges appear in the order you received them, with the most recent first. Other pilots can also see your badges when visiting your profile (if your profile is public). ## Team Page The Team Page at Community → Team Page shows your VA's staff members. Each staff member card displays their name, title, photo (if provided), and contact email (if provided). This is a quick way to find out who runs your VA and how to reach them. **Staff Visibility**: Only staff members who are not marked as hidden will appear on the Team Page. The order is determined by the VA. --- # Navigating Phoenix Your guide to the Phoenix pilot portal — dashboard, navigation, and finding your way around. Phoenix is the pilot portal — the place where you book flights, track your career, and connect with your Virtual Airline community. This guide walks you through what you will see when you first log in and how to find your way around. **Every VA Looks Different**: Your Virtual Airline staff customize the dashboard layout, colors, and which widgets appear. What you see may differ from another VA — that is by design. The navigation structure remains the same across all VAs. ## The Dashboard When you log in to Phoenix, you land on the dashboard — your home page. Think of it as a personalized overview of your pilot life at this VA. The dashboard is built from widgets that your VA staff have arranged, so the exact layout varies, but here are the widgets you may encounter. ### Booking and PIREP Boxes Quick-glance cards showing your upcoming booking and recent PIREPs. If you have a flight booked, the first card shows your next departure — click it to go straight to the booking details. Remaining cards display your latest filed PIREPs with their status. ### Your Statistics A detailed breakdown of your personal flying statistics. You can switch between time periods — all time, last 90 days, last 30 days, or last 7 days — to see how your numbers stack up. The statistics cover: - PIREPs — accepted, rejected, invalidated, and manual counts - Points — regular, bonus, total, and average per flight - Flight time — total hours flown - Distance — nautical miles covered - Transport — passengers carried and cargo hauled - Fuel and landing rate — fuel used and average landing rate - Current location — the airport where your pilot is currently based If you have not filed any PIREPs yet, you will see a welcome message instead — nothing to worry about, it will populate after your first flight. ### Airline Statistics Similar to your personal statistics but for the entire Virtual Airline. See how the VA is performing as a whole — total PIREPs, points, flight time, and distance flown across all pilots. You can filter by time period (last 7, 30, or 90 days) to see recent trends. ### NOTAMs Notices to Airmen from your VA staff. These are announcements, updates, or important information your VA wants you to see. NOTAMs are color-coded by priority (low, medium, high) and show their read status. Must-read NOTAMs are highlighted — make sure to open and read those. Click any NOTAM to view its full content. ### Events If your VA runs events, you may see upcoming or active events displayed on the dashboard. These could be group flights, fly-ins, or special challenges. Click through to see event details and sign up. ### Community Activity Shows the current Community Goal or Community Challenge if your VA has one running. You will see overall progress toward the target, time remaining, and your personal contribution. For Community Challenges, the widget also shows team standings and which team is in the lead. ### Live Flights A real-time list of pilots currently flying for the VA. See who is in the air right now, where they are headed, and what aircraft they are flying. If no one is currently airborne, the widget backfills with recent completed flights so there is always something to see. ### Social Icons Links to your VA's social media and community platforms — Discord, Instagram, Facebook, YouTube, and more. If your VA has Discord integration and you have linked your Discord account, you may also see a button to join the VA's Discord server directly from the dashboard. ### Quick Action Buttons Shortcut buttons that your VA may place on the dashboard for common actions — book a flight, file a PIREP, view events, or jump to custom pages. These give you one-click access to the things you do most often. ### Images and Text Your VA staff can place custom images and text blocks on the dashboard — anything from welcome banners and airline branding to important notices or quick reference guides. ## Main Navigation The sidebar navigation organizes everything into clear sections. Here is what you will find in each area. ### Flight Center This is where the flying happens. Book flights, view your bookings, and access your PIREP history. If your VA uses SimBrief integration, you will also dispatch flights from here. ### My Profile Your pilot profile page — your rank, statistics, badges, and flight history. This is also where you manage your pilot settings such as preferred network, imperial or metric units, and holidays. ### Activities If your VA runs activities like Challenges, Tours, or Community Goals, you will find them here. Browse available activities, track your progress, and see leaderboards. ### Community The social side of your VA. View other pilots, check leaderboards, and find links to your VA's social channels. Community resources and shared content from your VA live here too. ### Resources Reference material for your flying. This section includes airports, aircraft, fleet information, and any custom pages your VA has created — such as SOPs, livery guides, or rules. ## Browsing Airports The Airports page, found under Resources, gives you a searchable table of every airport your VA operates from. You can search by ICAO code, IATA code, airport name, or country. The table shows: - ICAO and IATA codes — standard airport identifiers - Airport name and country — so you can browse by region - Hub — which hub the airport belongs to, if any - Outbound routes — how many routes depart from this airport - Outbound bookings — how popular the airport has been in the last year You can filter the list to show only your favorite airports. To mark an airport as a favorite, click the star icon next to it — favorited airports also appear differently on the flight booking map, making them easy to spot when planning your next trip. ### Airport Detail Pages Click any airport to open its detail page. Here you will find: - Current weather (METAR) — live weather data for the airport - Destinations — every airport you can fly to from here - Airport statistics — overall traffic data for the airport - Your personal stats — your own history at this airport, including flights in and out, passengers carried, cargo hauled, and average landing rate - Stands and gates — available stands, organized by group - Scenery — simulator scenery packages for the airport, if your VA has added any - Briefing and information — any notes your VA staff have written about the airport ## Your Settings You can access your pilot settings directly from the dashboard if your VA has the settings button enabled. From here you can: - Switch between imperial and metric units - Toggle your honorary rank display - Set your preferred flying network (VATSIM, IVAO, offline, etc.) - Manage your favorite aircraft and airports - Book holidays (if your VA uses activity requirements) - Apply for a rank transfer (if eligible and if your VA supports transfers) ## Where to Go Next Now that you know your way around, here are some guides for the things you will do most often: - How to Meet Activity Requirements — understand what your VA expects and how to stay active - How to Book Holidays — take a break without losing your account - How to Apply for a Rank Transfer — bring your experience from other VAs - Account Management — manage your vAMSYS account and linked services --- # Resources & Documents Find your Virtual Airline's manuals, guides, and reference materials in Phoenix. Phoenix includes two navigation sections — Documents and Resources — where your Virtual Airline publishes reference materials, guides, and operational information. The content on these pages is created by your VA staff, so what you see will vary between airlines. ## Documents The Documents section in the Phoenix sidebar contains reference pages about how the airline operates. Alongside any custom pages your VA has created, you will always find two built-in pages here: - Ranks — the Rank Manual (covered below) - Scores — explains PIREP statuses, auto-reject rules, and scoring rules for each aircraft group Your VA may also add custom document pages here — things like SOPs, rules, training manuals, or any other written material relevant to pilots. ## Resources The Resources section provides operational reference data. It always includes two built-in pages: - Airports — browse all airports in your airline's network - Aircraft — browse the airline's fleet, view individual aircraft details, mark favourites, and assign SimBrief profiles Your VA may add additional custom resource pages here, and if Hangar (the vAMSYS file sharing service) is enabled, you may also see a link to download liveries, utilities, or other files your VA has shared. ## Standalone Pages Some custom pages appear as standalone items in the sidebar rather than being grouped under Documents or Resources. These have their own icon and sit at the top level of the navigation. Your VA decides which pages appear this way. ## Rank Manual The Rank Manual is a built-in page found under Documents → Ranks. It shows every rank available at your airline, along with the requirements to achieve each one. For each rank, you can see the following promotion requirements (where applicable): - Hours — total flight hours needed - Points — total points earned - Bonus Points — bonus points accumulated - Accepted PIREPs — number of accepted flight reports Your current rank is highlighted so you can quickly see where you stand. The entry-level rank has no requirements — it is assigned when you join. Below the main rank list, a separate section shows Team & Honorary Ranks. These are special ranks that may be assigned by VA staff and are not part of the standard progression path. ## Scores Page The Scores page, found under Documents → Scores, explains how your PIREPs are processed and scored. It covers: - PIREP statuses — what each status means (Accepted, Complete, Rejected, Invalidated, Awaiting Review, Reply Needed, Processing, Scoring) and whether any action is needed from you - Auto-reject rules — conditions that automatically flag a PIREP for staff review - Aircraft scoring rules — detailed scoring criteria grouped by aircraft type, covering categories like engines, flaps, landing, and more **Content Varies by Airline**: The custom pages you see under Documents, Resources, and Standalone are created and managed by your VA staff. Different airlines will have different pages — and some may have very few or none at all. The built-in pages (Ranks, Scores, Airports, and Aircraft) are always available. ## Rank-Restricted Pages Your VA can restrict certain custom pages to specific ranks. If a page is restricted to ranks you haven't reached yet, it simply won't appear in your navigation. As you progress through ranks, new pages may become visible to you. ## Related - Custom Pages — how VA staff create and manage custom pages (Orwell documentation) - Ranks — how the rank system works - Scoring Rules — how PIREP scoring is configured --- # Alerts, NOTAMs & Notifications Stay informed with VA alerts, NOTAMs, and manage your email notification preferences. Your Virtual Airline uses several ways to keep you informed: alerts for quick announcements, NOTAMs for detailed notices, and marketing emails for news and events. This article covers where to find each one and what to do when you see them. ## Alerts Alerts are short banner messages from your VA staff. They appear on your Phoenix dashboard and may also appear in Pegasus. Think of them as quick updates — a line or two about something you should know. ### Where Alerts Appear Alerts display in the Alerts component on your Phoenix dashboard. Your VA controls where this component sits in the dashboard layout, so the exact position varies between Virtual Airlines. If your VA has also enabled alerts in Pegasus, you will see them there after selecting your airline. ### Alert Styles Alerts are colour-coded to signal their importance: - Info (blue) — General announcements, new features, or tips - Success (green) — Positive news, completed updates, or achievements - Warning (amber) — Upcoming changes, scheduled maintenance, or cautions - Danger (red) — Critical issues, service disruptions, or urgent warnings - Secondary (grey) — Low-priority background information Alerts do not require any action from you. They are informational — read them and carry on. ### System Alerts In addition to alerts from your VA, vAMSYS itself may display certain automatic alerts: - New pilot alert — If you haven't filed a PIREP yet, you will see an info alert suggesting you check your account settings and network preferences. - PIREP needs reply — If one of your PIREPs requires a reply, a red alert links you directly to it. You need to respond before you can book another flight. - Activity grace warning — If your account is not meeting activity requirements, a red alert appears with a link to your profile for details. - vAMSYS announcements — Occasionally, Team vAMSYS posts platform-wide alerts about maintenance windows, new releases, or community activities. These are kept to a minimum. ## NOTAMs NOTAMs (Notices to Airmen) are longer, more detailed notices from your VA. Unlike alerts, NOTAMs have their own dedicated page, track whether you have read them, and some may require you to acknowledge them before you can fly. **Not All VAs Use This**: NOTAMs are an optional module. If you do not see a NOTAMs page or widget, your VA has not enabled this feature. ### Where to Find NOTAMs NOTAMs appear in two places: - Dashboard widget — If your VA has added a NOTAMs component to the dashboard, it shows a summary table of recent NOTAMs. Unread NOTAMs are highlighted in amber; unread Must Read NOTAMs are highlighted in red. Click any row to open the full NOTAM. - NOTAMs page — The full NOTAMs list is available from Phoenix → NOTAMs. This page shows every active NOTAM with filters for priority, read status, and tags. ### Reading a NOTAM Each NOTAM in the list shows: - Priority — Low (blue), Medium (amber), or High (red) - Status — Must Read (red), Unread (amber), or Read (green) - Expiry — When the NOTAM stops being shown, or "Never" for permanent NOTAMs - Title — The NOTAM heading - Tag — An optional category label set by your VA (useful for filtering) Click a NOTAM to read its full content. Regular NOTAMs are automatically marked as read when you open them — no further action needed. ### Must Read NOTAMs Some NOTAMs are marked as Must Read by your VA. These are important enough that you need to explicitly acknowledge them. When you have unread Must Read NOTAMs: 1. You will be redirected to the NOTAMs page when you try to book or dispatch a flight 2. Open the NOTAM and read through the content 3. Click the Acknowledge button at the bottom of the NOTAM 4. Once all Must Read NOTAMs are acknowledged, you can proceed to book flights as normal **Cannot Book Flights?**: If you are being redirected to the NOTAMs page every time you try to book a flight, you have unread Must Read NOTAMs. Look for entries highlighted in red with a "Must Read" badge. Open each one, read the content, and click Acknowledge. ### Filtering NOTAMs On the NOTAMs page, you can filter the list by: - Priority — Low, Medium, or High - Status — Must Read, Unread, or Read - Tag — Category tags set by your VA (only shown if tags exist) The list is sorted so that unread and Must Read NOTAMs always appear at the top, with the newest NOTAMs first within each group. ## Marketing Communications Some Virtual Airlines offer marketing communications — emails about news, events, and promotions. This is entirely optional and controlled by you. ### The Dashboard Prompt If your VA has marketing communications enabled and you haven't opted in yet, you may see a banner on your dashboard asking if you'd like to subscribe. You can click Subscribe to opt in, or No Thanks to dismiss it. If you dismiss it, the prompt won't appear again. ### Managing Your Preference You can change your marketing preference at any time: 1. Go to My Profile → Settings 2. Under Pilot Preferences, find the Marketing Communications toggle 3. Turn it on to subscribe, or off to unsubscribe 4. Save your preferences When you opt in, your first name, last name, and email address are shared with the Virtual Airline for direct marketing purposes. You can unsubscribe at any time by returning to this setting. **Per-Airline Setting**: Marketing communications are configured per Virtual Airline. If you fly with multiple VAs, you can opt in or out independently for each one. The toggle only appears if the VA has enabled marketing communications. ## Alerts vs NOTAMs — Quick Comparison AlertsNOTAMsWhat they areShort banner messagesDetailed notices with full contentWhere they appearDashboard banner and/or PegasusDashboard widget and dedicated NOTAMs pageRead trackingNoYes — tracks whether you have read each oneCan block flight bookingNoYes — Must Read NOTAMs require acknowledgement firstAction requiredNone — read and carry onClick Acknowledge for Must Read NOTAMs ## Related - Alerts (Staff Guide) — How VA staff create and manage alerts - NOTAMs (Staff Guide) — How VA staff create and manage NOTAMs --- # My Rosters & Personal Rosters Save generated rosters, track progress on personal and curated rosters, and dispatch flights from a single page. My Rosters is a unified page in Phoenix where you can see all your active rosters — both personal rosters you have created and curated rosters you have registered for. Each roster shows your progress, and you can dispatch flights directly from individual legs. **Custom Names**: Your Virtual Airline may have renamed "My Rosters", "Roster", "Curated Rosters", and related labels to something different. The functionality described here remains the same regardless of the name used. ## Accessing My Rosters In Phoenix, go to Flight Centre → My Rosters. This menu item appears when either the roster generator is enabled for your Virtual Airline or when curated rosters are available. ## Personal Rosters Personal rosters are rosters you create yourself from the Roster Generator. They let you plan a multi-leg trip and track your progress as you fly each leg. ### Using the Roster Generator From the My Rosters page, click the Generate New Roster card to open the Roster Generator. Configure the following options: - Generator Type — three modes: Random picks legs without constraints; Trip - One Airport Out flies out to a destination and returns (even leg counts only); Trip - Two Airports Out goes further before looping back (4 or 8 legs). - Only Unique Airports — prevents the generator from visiting the same airport twice. Only available in Random mode. - Starting / Final Airport — optionally pin the start or end of the itinerary to a specific airport. - Fleets — restrict routes to specific fleet types. - Operators — restrict routes to specific operators (shown by Callsign Parameter name). Only appears when the airline has more than one operator configured. - Legs to Generate — choose between 2 and 10 legs. Available options depend on the generator type. - Min / Max Leg Length — set time boundaries for each individual leg, in 30-minute increments. - Route Tags — restrict routes to those with specific tags. Only appears when the airline has tagged routes. - Exclude Airports — prevent the generator from using specific airports. - Try to Include Airports — request the generator tries to include specific airports in the itinerary (not guaranteed). Click Generate to build the itinerary. The result shows each leg with departure, arrival, flight time, distance, and route details on an interactive map. If a leg does not suit you, you can regenerate from that leg onwards while keeping earlier legs intact. ### Saving as a Personal Roster Once you are happy with the generated itinerary, click Save Roster. Your roster appears on the My Rosters page where you can track progress and dispatch individual legs. **Minimum Two Legs**: Personal rosters require at least two legs. Single-leg flights should be booked directly from the route list. ## Curated Rosters in My Rosters When you register for a curated roster (from Flight Centre → Curated Rosters), it also appears on your My Rosters page. This gives you a single view of all your active rosters — personal and curated — in one place. ## Tracking Progress Each roster on the My Rosters page shows your completion progress. The roster detail view includes: - Leg status — see which legs you have completed and which remain - Interactive map — view the full route on a map - Real-time updates — progress updates automatically as you complete flights ## Dispatching Flights You can dispatch flights directly from individual roster legs. Click a leg to book it and begin the dispatch process. Legs must be completed sequentially — you cannot skip ahead. Each leg can only be completed by one PIREP. ## Unregistering For curated rosters, you can unregister directly from My Rosters. Unregistering cancels your registration and removes any incomplete logbook entries for that roster. Completed legs are not affected. For personal rosters, you can delete them from the roster detail view. Deleting a personal roster removes your registration and any incomplete logbook entries. Completed legs are preserved in your logbook history. ## Related - How to Book a Flight — booking and dispatch process - How to Join Activities — registering for activities and curated rosters - Activities — staff guide to creating and managing activities --- # Pilot Passport Track every airport and country you have visited — see exploration progress, completion percentages, and earn gold stars for fully explored countries. The Pilot Passport tracks every airport and country you visit across your flights. It appears on your pilot profile page and shows your exploration progress with country and airport completion percentages, per-country progress bars, and detailed airport visit histories. ## Viewing Your Passport Your Passport appears on your pilot profile page, below the badges section. It is visible to you, to airline staff, and to other pilots if you have enabled PIREP visibility in your privacy settings. ## What Counts as a Visit An airport is marked as visited when you depart from or arrive at it in an accepted or complete PIREP. Both the departure and arrival airports count. A country is marked as visited when you have visited any airport in that country. **Visits Are Permanent**: Once you visit an airport, that stamp is permanent. If the airport is later removed from the route network, your visit is preserved and the airport shows a "Historical" badge in your passport. Your exploration history is never lost. ## Passport Overview The top of the passport shows two progress statistics: - Countries Explored — how many countries you have visited out of all countries in the airline's route network. - Airports Visited — how many airports you have visited out of all airports in the airline's route network (including any historical airports you have visited that are no longer in the network). ## Visited Countries Countries you have visited are displayed as cards grouped by the year you first visited them, with the most recent year shown first. Each country card shows: - Country flag and name - Date of your first visit - Per-country airport progress bar (e.g., 3 of 5 airports visited) - A gold star when all airports in that country have been visited ### Fully Explored Countries A country earns a gold star when you have visited every airport in the airline's route network for that country. If airports are added to the route network in a country you have already fully explored, the gold star is removed until you visit the new airports. ### Airport Detail Click a country card to expand it and see each airport in that country. For each airport you can see: - ICAO code and airport name - Visit count (total flights to or from the airport) - First and last visit dates - Historical badge — shown for airports you have visited that are no longer in the airline's bookable route network ## Yet to Visit Below your visited countries, a "Yet to Visit" section shows countries in the route network where you have not visited any airports yet. These are displayed with greyed-out flags, sorted alphabetically. ## Route Network The route network used for passport calculations includes all departure and arrival airports from the airline's currently bookable routes. This determines which countries and airports appear in your progress statistics and "Yet to Visit" section. The route network is refreshed periodically — changes to routes (adding, removing, or updating bookable status) are reflected within an hour. ## Privacy Your passport shares the same privacy setting as your PIREPs. If you have disabled PIREP visibility in your privacy settings, other pilots cannot see your passport. Airline staff can always see it. ## Related - Your Pilot Profile — overview of all profile sections - Badges — earn badges for visiting specific airports --- # API Create API clients for the Operations API (server-to-server) and Pilot API (pilot-facing OAuth) — manage scopes, view request logs, and access interactive documentation. vAMSYS provides two APIs for integrating with external systems. Both are managed from the same page in Orwell and have interactive OpenAPI documentation. ## Accessing API Settings In Orwell, go to Settings → API → API v3. You need the Can See API Settings permission. Airlines on trial do not have access to API settings. ## The Two APIs Operations APIPilot APIPurposeServer-to-server integration — manage fleet, routes, pilots, PIREPs, activities, and morePilot-facing applications — third-party apps that authenticate pilots and access their dataGrant TypeClient CredentialsAuthorization Code + PKCEAuthenticationClient ID + SecretOAuth PKCE flow — no secret, pilot authorises in browserDocumentationAvailable at /docs/operations on your vAMSYS instanceAvailable at /docs/pilot on your vAMSYS instance ## Creating a Client Click New Client and select the grant type for the API you want to use. ### Operations API Client (Client Credentials) Provide a client name and optionally select scopes to restrict what the client can access. If no scopes are selected, the client has unrestricted access to all endpoints. Available scopes: - ops:read — all GET endpoints. Safe to embed in client-side JavaScript for public displays. - ops:config:write — manage fleet, aircraft, airports, hubs, ranks, badges, routes, and related configuration. - ops:flights:write — manage bookings, PIREP comments, points, notes, and pilot data. - ops:moderation:write — accept, reject, and invalidate PIREPs; ban and delete pilots; manage registrations and transfers. - ops:activities:write — manage events, tours, rosters, focus airports, community goals, and challenges. After creation, the client ID and secret are shown once. Store the secret securely — it cannot be retrieved later. Use Reset Secret to generate a new secret if needed (this revokes all existing tokens). ### Pilot API Client (Authorization Code + PKCE) Provide a client name, redirect URI, privacy policy URL, and select the scopes your application needs. - Redirect URI — HTTPS URL or custom URI scheme for native apps (e.g., myapp://callback). Plain HTTP is not allowed. - Privacy Policy URL — must be a publicly accessible privacy policy covering how pilot data is handled. - Allowed Scopes — select which pilot data your application can access (identity, pilot profile, flights, activities). **Attestation Required**: Pilot API clients are created in a revoked state. The VA Owner must review and attest the client before pilots can authorise it. This confirms the privacy policy is adequate and the application is approved for pilot data access. ## Managing Clients From the API page you can: - View request statistics — see today, this week, this month, and all-time request counts per client. - Edit client settings — update the name, redirect URI, privacy policy, or allowed scopes. - Revoke a client — disable a client without deleting it. - Delete a client — permanently remove a client and all its tokens. ## Request Logs Below the client table, a live request log shows recent API requests with method, endpoint, status code, response time, and IP address. The log refreshes automatically every 30 seconds. Filter by client, HTTP method, status code range, or date. ## API Documentation Interactive API documentation is available directly on your vAMSYS instance: - Operations API — /docs/operations - Pilot API — /docs/pilot The documentation is auto-generated from the codebase and includes all endpoints, request/response schemas, and authentication requirements. Links to both are also shown at the bottom of the API settings page in Orwell. ## Permissions PermissionGrantsCan See API SettingsAccess to API client management, request logs, and documentation links Note: Only the VA Owner can attest and activate Pilot API clients. --- # Pilots Manage pilot accounts, view statistics, handle removals and bans, merge accounts, and maintain staff notes on pilots. The Pilots section in Orwell is the central hub for managing pilot accounts. From here you can view pilot details and statistics, perform administrative actions such as bans and removals, manage pilot notes, and handle account merges. ## Users vs Pilots vAMSYS is a multi-tenant application — each Virtual Airline operates independently. Understanding the distinction between User Accounts and Pilot Accounts is key to managing your roster effectively. ### User Account A User Account is a person's identity on vAMSYS — it stores their name, email, password, and preferences. Each person has exactly one User Account (vAMSYS Terms of Service prohibit creating multiple user accounts). User Accounts are centrally managed by vAMSYS LTD as data controller. VA staff cannot edit user account details directly. The only exception is the Capitalise Name action, which standardises the format of a user's name (e.g. "john doe" to "John Doe"). ### Pilot Account A Pilot Account is a membership token linking a User to your Virtual Airline. One user can have pilot accounts with many different VAs. Pilot accounts are created when a user registers with your VA, is invited by staff, or transfers from another airline. The Pilot Account is the conduit which enables VA staff to view user details like name and email. ### Pilot Username When a user joins your VA, a Pilot Username (sometimes called Pilot ID) is automatically assigned. Usernames are assigned incrementally and follow the format of your VA's ICAO prefix plus 4 digits (e.g. BAW1249). Pilot usernames cannot be edited, swapped between users, or otherwise reassigned. **Team vAMSYS Accounts**: Team vAMSYS accounts and the vAMSYS Robot show as special usernames — for example BAW-Robot, BAW-Lukas, BAW-Matt. These accounts cannot be removed from your airline. ## Pilot List In Orwell, go to Pilots → List. You need the Can View Pilot List permission. The pilot table is a powerful interface that allows you to toggle which columns are shown, reorder columns, set up filters, and save your configurations as preset views for quick access later. ### Columns Default visible columns: - Pilot ID, Username, Name, Rank, Honorary Rank, PIREPs count, Last PIREP date Additional toggleable columns: - User ID, Email (if your airline permits email visibility), Platform Ban, Airline Ban, Permanent Remove, Frozen Date, Holiday Allowance, Activity Grace, Activity Whitelist, Created date, Deleted date, Entry Route, Hub, IVAO/VATSIM/POSCON/APOC IDs, Twitch, YouTube, Discord, Staff status ### Filters In addition to the trashed filter (to show active, deleted, or all pilots), the filter builder supports: - Rank — single or multiple rank selection - Honorary Rank — single or multiple selection - Staff status — has staff role, does not have staff role, or any - IVAO/VATSIM/POSCON/APOC ID — has or does not have a network ID - PIREP count — with comparison operators (equals, greater than, less than, etc.) ### Preset Views Several preset views are available for common tasks: ViewDescriptionShown WhenDeleted PilotsShows soft-deleted pilots with permanent remove, platform ban, and airline ban columnsAlwaysActivity WhitelistShows pilots who are exempt from activity requirementsActivity enabledUnmet Ongoing ActivityShows pilots currently under activity grace periodOngoing activity enabledUnmet Initial ActivityShows new pilots who have not yet met initial activity requirementsInitial activity enabled ## Pilot Profile Click any pilot row to open their profile page. The profile displays comprehensive information across several sections: ### User Information Full name, email (if your permission level and airline settings allow), and the date the user registered their vAMSYS account. ### Pilot Information Username, current airport, rank (linked to the Ranks resource), honorary rank, entry route (how they joined — register, invite, or transfer), hub, frozen date, VA staff status, and when the pilot account was created. ### Statistics Total, accepted, rejected, and invalidated PIREPs. Hours flown, points, bonus points, unique airports visited, total distance, fuel used, day and night takeoffs and landings, average landing rate (FPM), and average landing G-force. ### Online Networks and Third-Party Accounts IVAO, VATSIM, POSCON, and APOC IDs, Navigraph link status, Discord ID, Twitch, and YouTube. ### Bans and Removals Airline ban status and reason, platform ban status and reason, permanent remove flag, and removal reason. ### Activity Holiday allowance, activity grace status, activity whitelist flag, grace start date, and activity type. Only shown if activity requirements are enabled. ### Relationship Tabs At the bottom of the profile page, tabbed sections show related data — a great place to quickly see a pilot's full activity in one place: - PIREPs, Comments, Notes, Bookings, Claims, Holidays, Badges, Favourite Aircraft, Favourite Airports ## Pilot Actions A context menu of actions is available from both the pilot list (click the ... on a row) and the pilot profile page (click Pilot Actions). Not all actions are available for all accounts — availability depends on permissions and the pilot's current state. ActionDescriptionPhoenix ProfileOpens the pilot's public Phoenix profile pageRefresh RankRecalculates the pilot's statistics and rank based on their current PIREPsCreate Manual PIREPAwards hours, points, and bonus points to the pilot via a transfer PIREP. Processed after a 20-minute delay, giving you time to correct any mistakes.Capitalise NameConverts the user's first and last name to title case (e.g. "john doe" becomes "John Doe")Edit Honorary RankAssigns or changes the pilot's honorary rank from available honorary ranksSend Name for ReviewFlags the user's name for Team vAMSYS to review. Requires a reason (max 250 characters). Use if you suspect the user has not provided a real name.Activity WhitelistMakes the pilot immune to activity requirements. Only shown if activity is enabled.BanIssues an airline ban with a public message (up to 250 characters). Optionally escalates to a platform ban with a private note for Team vAMSYS.UnbanReverses an airline ban. Note: this does not auto-restore the pilot account — a separate Restore action is needed.Remove Permanent RemovalClears the permanent removal flag, allowing the pilot to rejoin (subject to other rejoin settings)RestoreRestores a deleted pilot account with options to reuse the previous username and restore PIREPs and bookingsDeleteSoft-deletes the pilot account. Requires a removal reason (free text). Optionally sets permanent removal.Erase Pilot RecordIrreversible hard delete. Removes the pilot and all associated data — PIREPs, comments, notes, bookings, claims, and event registrations. Only available to Airline Owner and vAMSYS staff. **Protected Accounts**: Team vAMSYS accounts are protected and cannot be deleted, banned, or erased. ### Bulk Actions Select multiple pilots in the list to access bulk actions: - Merge Accounts — combine multiple pilot accounts (see Account Merging below) - Restore — bulk restore deleted pilots using your airline's default rejoin settings - Delete — bulk soft delete with a shared removal reason - Erase Pilot Record — bulk hard delete (irreversible) ## Removal and Permanent Removal Pilot accounts can be removed in several ways — manually by staff, automatically due to activity requirements, by the pilot themselves, or as a result of a ban. When a pilot is removed, a removal reason is stored on the record. ### Removal Reasons The following removal reasons are set automatically by the system: Removal ReasonTriggerActivity Requirements UnmetOngoing activity grace period expired with no qualifying PIREPsInitial Activity Requirements UnmetNew pilot did not meet initial activity requirements within the configured periodfrozenPilot froze their own account and did not log back in within 2 daysUser Account DeletedThe parent vAMSYS user account was deleted(Staff-provided text)Manual removal by VA staff — free-text reason up to 250 characters **Bans Are Separate**: Bans store their reason in separate fields (airline ban reason and platform ban reason), not in the removal reason field. A pilot can have both a ban reason and a removal reason. ### Permanent Removal The permanent removal flag prevents a pilot from ever rejoining the airline, even if the VA's "Allow Rejoin" setting is enabled. It is set in the following cases: - Activity removals — only if the VA setting "Activity Removal is Permanent" is enabled - Frozen accounts — always permanent (the pilot chose to leave) - Manual staff deletion — optional toggle in the delete form Staff can reverse permanent removal using the Remove Permanent Removal action, which clears the flag and allows the pilot to re-register (subject to other rejoin settings). ### Account Freezing (Pilot Self-Deletion) Pilots can freeze their own account from Phoenix → My Profile → Settings. The flow works as follows: 1. Pilot clicks "Delete Account" — the account is frozen but not yet deleted 2. A grace period begins until midnight UTC of the following day (roughly 2 days) 3. If the pilot logs back into the airline during this window, the freeze is cancelled automatically 4. If the pilot does not log back in, the account is deleted with removal reason "frozen" and permanent removal set If the airline has rejoin disabled, the pilot sees a warning that they will not be able to register again. ### Erase vs Delete - Delete (soft delete) — the pilot record is retained with a deletion timestamp. It can be restored later. Deleted pilots appear in the "Deleted Pilots" preset view. - Erase (hard delete) — irreversible. Removes the pilot record and all associated data: PIREPs, comments, notes, bookings, claims, and event registrations. Only available to Airline Owner and vAMSYS staff. Use with extreme caution. ## Bans vAMSYS has two levels of ban with an escalation path between them. ### Airline Ban - Issued by VA staff via the Ban action - Requires a public message (up to 250 characters) explaining the reason — this is visible to the pilot - Soft-deletes the pilot account and prevents re-registration with this airline - Reversible by VA staff via the Unban action **Unban Does Not Restore**: Unbanning a pilot clears the airline ban flag but leaves the pilot account in a deleted state. You must also use the **Restore** action to bring the pilot back to active status. ### Platform Ban - Escalated from an airline ban — when banning a pilot, staff can optionally select "Escalate to Platform Ban" and provide a private note for Team vAMSYS - Affects the pilot across all Virtual Airlines on vAMSYS, not just the issuing VA - Can only be removed by Team vAMSYS — VA staff cannot reverse a platform ban - The private escalation note is only visible to Team vAMSYS, not to the pilot or other VA staff ### Ban vs Removal A ban is different from a regular removal in several key ways: - A banned pilot cannot rejoin regardless of the airline's rejoin settings or the permanent removal flag - Bans store their reason in dedicated fields separate from the removal reason - Unbanning does not automatically restore the pilot — both Unban and Restore actions are needed to fully reinstate a banned pilot ## Account Merging Two different merge operations exist — one for staff, one for users themselves. ### Pilot Account Merge (Staff Action) Available as a bulk action on the Pilot List. Staff select multiple pilot accounts within the same airline: 1. Choose the primary account — this one is kept 2. All other selected accounts become secondary accounts — these are erased 3. The VA setting "Discard Secondary PIREPs on Merge" controls whether PIREPs from secondary accounts are discarded or transferred to the primary account Use case: cleaning up duplicate pilot accounts within the same airline (e.g. created through both an invite and a registration). ### User Account Merge (User Self-Service) The preferred method for resolving multi-accounting. Users merge their own user accounts via My vAMSYS Account → Account Settings → Merge User Accounts. This combines all pilot accounts from both user accounts under a single user identity. **Prefer User Merge for Multi-Accounting**: When a user is suspected of having multiple vAMSYS user accounts (a breach of vAMSYS Terms of Service), direct the user to self-merge rather than performing pilot-level merges. User-level merging consolidates the identity across all Virtual Airlines — not just yours. If a user is unable or unwilling to self-merge, report the suspected multi-accounting to Team vAMSYS via **Orwell → HQ → vAMSYS Support**. ## Pilot Notes Pilot Notes are internal staff-only notes attached to a pilot account. Unlike internal notes (which are per-PIREP), Pilot Notes are per-pilot — they appear on every PIREP from that pilot during review, making them ideal for tracking warnings, special circumstances, or ongoing issues. ### Creating and Managing Notes - Standalone page — go to Orwell → Pilots → Notes to view and search all pilot notes across the airline - Pilot profile — the Notes tab on any pilot's profile page shows and allows creating notes for that specific pilot - PIREP review — Pilot Notes are displayed in the right column during PIREP review, where staff can add and delete notes Each note stores the note content, who entered it (auto-set to the current staff member), and the creation date. Notes can be edited and deleted. The notes table is searchable by pilot username, pilot name, note content, and the staff member who entered the note. **Notes vs Comments**: Pilot Notes differ from Internal Notes (per-PIREP, staff-only) and PIREP Comments (per-PIREP, two-way between staff and pilot). See [PIREPs](/docs/orwell/pireps) for the full comparison of all three. ## Reporting User Accounts ### Name Review If staff suspects a pilot has not provided a real name, they can use the Send Name for Review action. This flags the user account for Team vAMSYS to review. If confirmed, vAMSYS may lock the user account until the user updates their details. ### Multi-Accounting vAMSYS Terms of Service restrict each person to one user account. If you suspect a person has multiple user accounts: 1. Direct the pilot to merge their user accounts via My vAMSYS Account → Account Settings → Merge User Accounts 2. If the user is unable or unwilling to self-merge, report the issue to Team vAMSYS via Orwell → HQ → vAMSYS Support. Include details such as email addresses, names, and pilot usernames to help locate the records. ## Permissions PermissionWhat It GrantsCan View Pilot ListAccess to the Pilots area in Orwell (list, profiles, notes)Can Delete PilotsRemove (soft delete) pilot accountsCan Restore PilotsRestore removed pilot accounts and clear permanent removal flags The Airline Owner can perform all actions including Erase Pilot Record. ## Related - PIREPs — review PIREPs filed by pilots - Pilot Registration — registration settings, review process, and registration links - Activity Requirements — configure ongoing and initial activity requirements - Rank Transfer — pilot transfers between airlines - Badges — achievements awarded to pilots - Holidays — pilot holiday allowance system - Staff — manage VA staff accounts and permissions --- # Routes Create and manage the flight network that pilots book from — defining airports, schedules, fleets, callsigns, and SimBrief configuration. Routes define the flight network of your Virtual Airline. Each route is a connection between two airports, enriched with a callsign, flight number, schedule, available fleets, load factors, and dispatch configuration. Without routes, pilots cannot book flights. ## Accessing Routes In Orwell, go to Operations → Routes → Routes. You need the Can Manage Routes permission. **Airport Managers**: Unless a staff member has the **Can Manage All Routes** permission, they will only see and be able to create routes to and from airports they are assigned as manager of. ## Predefined Views ViewDescriptionDefaultAll routes with standard columns.Ending SoonRoutes with an end date within the next 2 weeks. Badge shows count.Starting SoonRoutes with a start date within the next 2 weeks. Badge shows count. ## Route Types TypeDescriptionNotesScheduledStandard scheduled passenger flightMost common route typeCargoCargo-only operationNo passenger loading option at dispatchCharterCharter passenger flightFunctions the same as ScheduledTrainingTraining flightNo passengers or freightVFRVisual Flight RulesDisables route string processing — allows freeform VFR navigation info like visual landmarks and reporting pointsRepositioningAircraft ferry/transfer flightNo passengers or freightJumpseatCustom jumpseat routeFor creating manual jumpseats when automated jumpseats are disabled. Hides most form fields (callsign, routing, fleet, times, etc.) ## Creating a Route The route creation form is organised into sections. Fields that appear depend on the selected route type — jumpseat routes hide most sections, and repositioning/training routes hide load factor and container sections. ### Basic Information - Departure Airport — search by ICAO, IATA, or airport name. The dropdown shows no results until you type a search term. Cannot be changed after the route is created. - Arrival Airport — search by ICAO, IATA, or airport name. The dropdown shows no results until you type a search term. Cannot be changed after the route is created. - Type — the route type (see table above). Changing the type adjusts which form sections are visible. ### Dates and Times - Start Date — when the route becomes available. Leave blank to make the route available immediately. - End Date — when the route will be removed from availability. Leave blank for no end date. - Departure Time — scheduled departure time. Entered in UTC unless local timezone mode is enabled. Used by on-time departure scoring rules. - Arrival Time — scheduled arrival time. Entered in UTC unless local timezone mode is enabled. Used by on-time arrival scoring rules. **Timezone Handling**: By default, all route times are entered and stored in UTC. When **Route Times Use Local** is enabled in airline settings, the form accepts times in local airport timezone and converts them to UTC automatically. The dispatch table will show local times with UTC in a tooltip. ### Flight Details - Callsign — ATC callsign in ICAO format (4-7 characters, uppercase letters and digits only). The first 3 characters must match an approved ICAO prefix from your airline parameters. If the prefix is not approved, you will see: "The combination of callsign prefix 'XXX' and flight number prefix 'XX' is not an approved parameter." The fleet selector also depends on this prefix — only fleets linked to the matching airline parameter entry will appear. - Flight Number — IATA flight number (3-6 characters, uppercase letters and digits only). The first 2 characters must match an approved IATA prefix from your airline parameters — the same entry that the callsign ICAO prefix matches. - FL / Altitude — planned cruise altitude. Accepts multiple formats: FL380, 360, or 36000 all resolve to 36,000 feet. Can be left empty — when dispatched via SimBrief, an appropriate flight level will be selected. - Cost Index — cost index for the flight (0-999). Enter a number to set a specific value, or enter AUTO to let SimBrief generate one. When left empty, the value is resolved in order: route → aircraft override → fleet override → SimBrief profile → AUTO. Leaving this empty is usually the best option unless you need a specific override for this route. - Flight Length — time from takeoff to landing (HH:MM). Optional — if not provided, vAMSYS will calculate an estimate based on route distance. Used in the pilot flight map, filters, tables, and flight length AutoReject rules. - Flight Distance — route distance in nautical miles. Optional — if not provided, vAMSYS calculates a great circle distance. Used in the pilot flight map, filters, and tables. - Days of Operation — which days this route operates. Select individual days or leave empty to indicate daily operation. Informational — pilots can filter by operating days in the dispatch table. **Auto-Calculation**: When **Flight Length** is left empty, it is estimated from flight distance using: `floor(((0.002393 × distance) + 0.6415) × 60 × 60)` where distance is in nautical miles and the result is in seconds. When **Flight Distance** is left empty, it is calculated as the great circle distance between the two airports. ### Callsign Options These options control how the callsign is presented and modified during pilot dispatch. New routes are pre-populated from your Route Defaults (configurable at HQ → Settings → Route Defaults). - Allow Pilots to Change Callsign — lets pilots enter their own callsign or use the callsign generator during dispatch - Callsign Defaults to Pilot Username — two options. Option 1 uses the airline ICAO prefix plus the numeric portion of the pilot's username (e.g., pilot 1234 on airline BAW → callsign BAW1234). Option 2 uses the ICAO prefix plus the last 2 digits of the username plus the pilot's initials (e.g., pilot 1234 named Lukas Keller on airline BAW → callsign BAW34LK). Both options disable the callsign change toggle. - Callsign Defaults to Aircraft Registration — auto-populates the callsign from the selected aircraft registration (e.g. G-LUJA becomes GLUJA) - Callsign Generator — generates up to 4 remaining callsign characters after the prefix using regex-like patterns. Each position accepts patterns like [A-Z], [0-9], [A-Z0-9], [A-C,1-5], or [A,D,G,3,5,9]. A preview shows the total number of possible combinations. Generated suffixes are automatically filtered to avoid ambiguous letters (O, I, Q), endings in 0/5/S, adjacent repeated characters, runway-style codes (e.g. 27L), emergency codes (PAN, SOS, QNH), and confusable letter-digit pairs (B8, D0, G6). Patterns are validated on save — every element must be in brackets — and invalid patterns are rejected wherever they can be entered (route form, route import, and Route Defaults). **Route Defaults**: Callsign options on new routes are pre-populated from your **Route Defaults** at **HQ → Settings → Route Defaults**. Changes to defaults do not retroactively affect existing routes — they only apply when creating new ones. ### Routing The routing field accepts a flight plan string of waypoints, airways, and coordinates. The field is smart — it parses the input against current AIRAC data, strips speed/altitude prefixes, removes SID/STAR names, and simplifies the route automatically. For example: - N0411F230 NIT2Y NIT M748 ERGOM/N0454F330 DCT TEGRI DCT ARTAT UP975 TEPKI/N0454F350 UP975 ERGUN UL124 EVSAS DCT SIDAD P975 SESRU M677 ITBUL Q322 DATOB DATOB5Y → NIT M748 ERGOM DCT TEGRI DCT ARTAT UP975 ERGUN UL124 EVSAS DCT SIDAD P975 SESRU M677 ITBUL Q322 DATOB - Speed/altitude prefixes like N0466F340 and M085F400 are stripped, SID/STAR names are removed, and DCT is inserted between adjacent waypoints not connected by an airway. See the AIRAC Validation section in Routings for full details on what gets stripped and what passes through. For VFR routes, routing processing is disabled — you can enter freeform VFR navigation information like visual landmarks and reporting points. This field can be left empty. If you use the Routings feature, pilots will be able to select from pre-defined routings during dispatch. If dispatched via SimBrief with no routing, SimBrief will pick an appropriate route. ### Notes, Tags and Visibility - Remarks — shown to pilots on the dispatch page and added to the SimBrief OFP when dispatching. Supports markdown formatting (bold, italic, links, bullet and ordered lists). - Route Tags — organisation labels that pilots can filter by in the dispatch table (e.g. DOMESTIC, LONG_HAUL). Must be enabled in airline settings. - Hidden — hides the route from the book flight map and table. Hidden routes can still be booked via Activities — useful for event-only routes. - Internal Remarks — staff-only notes. Not visible to pilots. **Pilot Visibility**: For a route to appear on the Book Flight map and dispatch table, all of the following must be true: the route is **not hidden**, at least **one fleet is assigned**, the **start date** is in the past or empty, and the **end date** is in the future or empty. Routes that fail any of these checks are invisible to pilots. ### Load Factors and Containers Load factors and containers set at route level override those set at airport level. For load factors to take effect or containers to be bookable, an appropriate fleet must be assigned to the route — a passenger fleet will not load containers, for example. Hidden for jumpseat, repositioning, and training routes. ### Fleets Select which fleets can operate this route. The fleet selector only appears after entering a callsign, and only shows fleets configured to use that callsign prefix. If no fleets are selected, the route will not be bookable and pilots will see a warning message. **Fleets Required**: Routes with no fleets assigned cannot be booked by pilots. Make sure at least one fleet is selected for every non-jumpseat route. ### SimBrief Overrides Override SimBrief dispatch settings at the route level. These take priority over fleet and aircraft-level SimBrief configuration. - Flight Rules — IFR, VFR, Y (IFR then VFR), or Z (VFR then IFR) - Flight Type — Scheduled, Non-scheduled, General Aviation, Military, or Training - Fuel Overrides — MEL, ATC, WXX, Tankering, Extra, Min FOB, and Min FOD with a unit toggle (minutes, kg, or lbs). Overrides values set in fleet or aircraft configuration. - PAX and Bag Weight — override passenger and baggage weight assumptions (in lbs) - Enroute Alternate — ICAO code of an enroute alternate airport - Contingency and Reserve — contingency percentage and reserve fuel rules - Fixed Alternates — takeoff alternate plus up to 4 landing alternates ## Turbo Mode A toggle in the top-right corner of the create/edit form switches between Normal and Turbo mode. Turbo mode replaces dropdowns and pickers with text inputs for faster data entry — airports accept ICAO/IATA codes directly, fleets and load factors accept names, and date/time fields use simple text inputs. The data entered is the same; Turbo mode just reduces clicks for experienced users. ## Save Options When creating a route, four save options are available: - Create — saves the route and opens it in the edit page - Create & Start New — saves the route and opens a blank create form - Create & Start Same — saves the route and opens a new create form with the departure airport, type, and callsign generator pre-populated - Create & Start Return — saves the route and opens a new create form with departure and arrival airports swapped, carrying over the type, dates, callsign, flight number, fleet, and callsign generator. When local timezone mode is enabled, departure and arrival times are also swapped. ## Editing Routes Editing uses the same form as creation, with departure and arrival airports locked. The row action menu also offers Copy Route (duplicates all fields into a new route) and Create Return (creates a new route with departure and arrival swapped). ## Relationship Tables At the bottom of the route edit page, three tabs show related data: - Routings — Routings stored for this airport pair. You can create new routings directly from this tab. - Bookings — all bookings made for this route - PIREPs — all PIREPs filed using this route ## Bulk Route Editing Select routes using the table checkboxes and choose Bulk Full Edit from the bulk actions menu (maximum 20 routes per batch). This opens a sequential editor that presents the full edit form for each selected route one at a time. After saving one route, the editor automatically advances to the next. The page scrolls to the top on each transition. You cannot skip routes or go back to a previous one. ## Route Changes Route Changes is an optional Phoenix module that lets pilots see upcoming and recent route changes. Enable it at Settings → vAMSYS Modules → Enable Route Changelist. When enabled, a Route Changes page appears in Phoenix → Flight Centre. The page shows four tables, each covering a 14-day window: - Ending Routes — routes with an end date within the next 14 days - Starting Routes — routes with a start date within the next 14 days - Ended Routes — routes that ended within the last 14 days - Started Routes — routes that started within the last 14 days Each table shows the callsign, departure, arrival, flight number, and the relevant date. Tables are searchable and paginated. **Graceful Route Removal**: When removing routes via importers, set `end_date` instead of using the `_delete` column. This ensures routes appear in the "Ending Routes" table before they are removed, giving pilots advance notice of the change. ## Row Actions ActionEffectEditOpens the route edit pageCopy RouteOpens the create form pre-populated with all fields from this routeCreate ReturnOpens the create form with departure and arrival airports swappedEnd RouteAvailable for live routes (already started). Sets the end date to now, gracefully removing the route from availability.DeleteAvailable for future routes (not yet started). Shows a confirmation suggesting you set an end date instead for graceful removal. ## Bulk Actions ActionDescriptionSet Start DateSets a new start date for all selected routes. Can also set to now.Set End DateSets a new end date for all selected routes.End/Delete NowFor active routes, sets end date to now. For routes that haven't started yet, deletes them entirely.Set HiddenHides all selected routes from the pilot dispatch table and map.Set UnhiddenMakes all selected routes visible to pilots.Bulk Full EditOpens the sequential route editor for up to 20 selected routes. ## Table Columns Default columns: Departure, Arrival, Callsign (with flight number), Type, Fleets, Hidden status. Additional columns: Route ID, Start Date, End Date, Lifespan, Flight Length, Flight Distance, Tags, Remarks, Internal Remarks, Route string. ## Filtering The table supports advanced filtering by: - Departure / Arrival — filter by airport - Flight Number — text search - Fleets — filter by assigned fleet - Start Date / End Date — date range filters - Route — search the routing string - Flight Distance — numeric filter with comparison operators - Hidden — filter by visibility status ## Related - Routings — pre-defined flight plan strings shared across routes on the same airport pair - Bookings — flight bookings created from routes - Fleet — aircraft type definitions assigned to routes - Airports — airport management and airport manager assignments - Load Factors — passenger and cargo load configurations - Route Import/Export — bulk route management via CSV --- # Routings Pre-defined flight plan waypoint strings shared across all routes on the same airport pair, simplifying AIRAC updates and route management. Routings decouple flight plan waypoint strings from individual routes. A Routing is stored between an airport pair and is automatically available to all routes connecting those two airports. This means updating one Routing propagates to every route on that pair — no need to edit each route individually. ## Accessing Routings In Orwell, go to Operations → Routes → Routings. You need the Can Manage Routes permission (same as for Routes). ## Why Use Routings Routings are optional — you can continue using the routing field directly on each route. However, Routings offer several advantages: - One update, many routes — a single Routing serves all routes between the same airport pair. When the routing changes, you only update it once instead of editing every route. - Multiple routings per pair — you can create several Routings for the same airport pair, for example different paths for different days of the week. This is not possible with the route-level routing field alone. - Faster AIRAC updates — updating Routings with new AIRAC data is quicker than editing individual routes, especially with importers. - Persist across seasons — when a route is removed (e.g. end of season), the Routings remain. If the route is recreated next season, the existing Routings are immediately available without re-entry. ## Creating Routings Routings can be created in three ways: - From a route edit page — open a route, go to the Routings tab at the bottom, and click New Routing. The departure and arrival airports are pre-filled from the route. - From the Routings page — go to Operations → Routes → Routings and create a new Routing. You will need to select the departure and arrival airports manually. - Via import — use Routing Import/Export for bulk creation and updates. ### Fields - Departure Airport — the origin airport (pre-filled when creating from a route) - Arrival Airport — the destination airport (pre-filled when creating from a route) - Routing — the flight plan waypoint string (required). Validated and cleaned against current AIRAC data — speed/altitude prefixes are stripped and waypoints are verified. - Remarks — operational notes shown to pilots during dispatch and included in the SimBrief OFP - Internal Remarks — staff-only notes, not visible to pilots - Tags — organisation labels for filtering - Days of Operation — which days this routing is valid for. Leave empty for all days. ## AIRAC Validation Routing strings are validated against current AIRAC navigation data (from Navigraph) every time they are saved. The system processes the input in several steps: ### What Gets Stripped - Speed/altitude prefixes (e.g., N0411F230, M085F400, K0460F350) - SID and STAR names (not present in AIRAC enroute navigation data) - Invalid or unrecognised waypoint and airway identifiers - Special instructions (e.g., "MANUAL ROUTE PLANNING REQUIRED") ### What Passes Through - Valid airways from Navigraph enroute airways data - Valid waypoints and navaids (VHF navaids, NDB navaids, enroute waypoints, terminal waypoints) - DCT (direct routing indicator) - Coordinate waypoints in various formats (e.g., 62N020W, 59N020W, 63N040W) ### Automatic Formatting - DCT is automatically inserted between adjacent waypoints or coordinates that are not connected by an airway - Consecutive duplicate waypoints are removed - Leading and trailing DCT are removed ### Example A route string entered as: N0411F230 NIT2Y NIT M748 ERGOM/N0454F330 DCT TEGRI DCT ARTAT UP975 TEPKI/N0454F350 UP975 ERGUN UL124 EVSAS DCT SIDAD P975 SESRU M677 ITBUL Q322 DATOB DATOB5Y Will be cleaned to: NIT M748 ERGOM DCT TEGRI DCT ARTAT UP975 ERGUN UL124 EVSAS DCT SIDAD P975 SESRU M677 ITBUL Q322 DATOB The speed/altitude prefixes (N0411F230, N0454F330, N0454F350), the SID (NIT2Y), and the STAR (DATOB5Y) are all removed. DCT is preserved between waypoints not connected by airways. **Empty Routing String**: If AIRAC validation produces an empty routing string (all elements were invalid), the save is halted and a warning is shown. The routing string cannot be empty. ### AIRAC Cycle Tracking Each Routing is tagged with the AIRAC cycle it was last validated against, shown as a cycle number (e.g. 2504) in the AIRAC Cycle column. This lets you identify routings that may need revalidation after a new AIRAC cycle is published. ## Routings in Phoenix When Routings exist for an airport pair, a "Pick Routing" button appears on the dispatch page. Clicking it opens a selector showing each Routing's waypoint string as a selectable option, with the Routing's remarks and days of operation shown as a description below each option. The default routing selection follows this priority: - If the route has its own routing string, that is shown as the default - If the route has no routing string, a random Routing from the airport pair is pre-selected - If no Routings exist for the pair, the routing field is empty (pilots can still dispatch via SimBrief, which will generate a route) When a Routing is selected, a "Routing Remarks" info box appears on the dispatch page showing the remarks text and the days the routing operates. Pilots can also manually edit the routing text in the field — doing so clears the Routing selection. The selected Routing is stored on the booking record. ## Table Columns Departure, Arrival, Routing string (truncated with tooltip for full text), Days of Operation, Tags, AIRAC Cycle, Created date. ## Filtering The table supports filtering by departure and arrival airport. ## Actions - Row actions — Edit and Delete on each individual routing - Bulk actions — Delete selected routings. Select routings using the table checkboxes. ## Import and Export Routings can be managed in bulk via Routing Import/Export. The import supports creating, updating, and deleting routings via CSV. Available columns: ID, Departure Airport (ICAO/IATA), Arrival Airport (ICAO/IATA), Route String, Remarks, Internal Remarks, Tags (comma-separated), Days of Operation (comma-separated weekday names), and a _delete flag. Imported routing strings are validated against AIRAC data and tagged with the current cycle, just like manually entered routings. Departure and arrival airports cannot be changed on existing routings via import. A special PFPX export is also available, which outputs routings in the format required by PFPX for route validation. Requires the Import/Export Routes permission. ## Related - Routes — flight route definitions that use Routings - Route Import/Export — bulk route management via CSV - Routing Import/Export — bulk routing management via CSV