# 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 - 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 - 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)Departure AirportsSelect specific departure airportsArrival AirportsSelect specific arrival airportsAirport Filter OperatorAND (routes matching both filters) or OR (routes matching either)TagsFilter by route tagsInternal RemarksFilter by exact internal remarks text ### Routing Export Filters FilterOptionsDeparture AirportsSelect specific departure airportsArrival AirportsSelect specific arrival airportsTagsFilter by routing tags ### PFPX Exports Routes - PFPX and Routings - PFPX have the same filters as their standard counterparts. 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 Welcome to vAMSYS! This guide will help you get your Virtual Airline up and running. Welcome to vAMSYS, the professional platform for managing Virtual Airlines. This guide will walk you through your first steps. ## What is vAMSYS? vAMSYS provides a complete software solution for running a Virtual Airline in flight simulators. It includes pilot management, flight tracking via Pegasus, route scheduling, and much more. ## Your First Steps ### 1. Access Orwell Orwell is your administration control room. This is where you configure your airline, manage pilots, set up routes, and more. ### 2. Configure Your Airline Start by setting up your airline basics: name, ICAO code, logo, and theme colors. These appear throughout Phoenix (the pilot portal) and set the tone for your VA. ### 3. Add Your Fleet Add aircraft types and individual aircraft to your fleet. vAMSYS supports all major simulators including MSFS 2020/2024, X-Plane 11/12, and Prepar3D. ## Next Steps Once you have the basics configured, explore the following areas: - Setting up routes and schedules - Configuring ranks and awards - Customizing pilot registration - Setting up Discord integration --- # 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 ### 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 ## 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 - 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, 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. ## 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. ## 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) #### 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, 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. ## 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) - 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 ## 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. ## 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 and how many items.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. ### 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.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. #### 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 - 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 --- # 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). **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