Pilot Conduct and Simulation Standards
Pilots are expected to operate in a respectful and reasonably realistic manner. Network rules apply whenever a flight is conducted on VATSIM, IVAO, or another supported network. Staff may review flights that show implausible movement, unsupported aircraft use, falsified data, or deliberate attempts to obtain unearned credit.
• Use respectful language in Phoenix, network communications, and community spaces.
• Follow the published route, aircraft restrictions, activity requirements, and current NOTAMs.
• Do not manipulate position, time, distance, landing data, or flight phases to obtain points or hours.
• Use simulator pause, reposition, or recovery tools only when necessary to resolve a genuine technical problem, and disclose material interruptions when submitting the PIREP.
• Treat all real airline names, marks, schedules, and procedures as simulation references rather than claims of real-world affiliation.
Flight Operations, Aircraft Selection & Substitution, Pegasus/PIREP Standards
Air France Virtual flights must be booked and dispatched through Phoenix using an available published route.
• Confirm your current departure airport before selecting a flight. Pilots normally begin their next flight from their current Phoenix location and should use the available jumpseat or repositioning options when movement is required.
• Review the flight number, operator, route, permitted fleet, operating days, flight type, and applicable tags before dispatch.
• The route shown in Phoenix is authoritative for the flight being operated. Current NOTAMs, event-specific rules, and staff instructions may impose additional requirements or restrictions.
• Select an aircraft authorized for the booked route. Aircraft substitutions are permitted only under the standing substitution rules or when specifically authorized by a current NOTAM or staff instruction.
• Bookings are normally valid for 24 hours. Cancel or rebook a flight if the route or aircraft no longer matches the operation you intend to fly. Pilots should not hold unnecessary bookings.
• Scheduled, cargo, historic, charter, training, and event operations must be flown under the appropriate Phoenix route and flight category. Sharing the same airport pair does not make aircraft or categories interchangeable.
Pilots are responsible for reviewing the applicable route information and current operational notices before departure.
Aircraft Selection & Substitution.
The fleet shown on the selected Phoenix route is the aircraft authorized for that booking. Pilots may use a different simulator aircraft only when the substitution is listed below or specifically approved by a current NOTAM or staff instruction.
Standing Aircraft Substitutions
• Airbus A320-200 → Airbus A320neo
The booked A320 route and fleet remain unchanged. The A320neo must remain within its own weight, runway, and performance limits.
• Airbus A321-200 → Airbus A321neo
The booked A321 route and fleet remain unchanged. The A321neo must remain within its own weight, runway, and performance limits.
• Airbus A330-200 or A330-300 → Airbus A330-900neo
The route, payload, airport limitations, and planned performance must be suitable for the A330-900neo.
• All other aircraft: No standing substitution is authorized unless specifically permitted by a current NOTAM or staff instruction.
When using an approved substitute:
Book the original fleet listed on the Phoenix route.
Confirm that the substitute is authorized before departure.
Use the actual simulator aircraft profile in SimBrief.
Retain the original flight number, operator, route category, and activity requirements.
Enter the substitution in the PIREP remarks, identifying both the booked fleet and the aircraft actually flown.
The following substitutions are not permitted unless specifically authorized:
• Passenger aircraft for cargo aircraft, or cargo aircraft for passenger aircraft.
• Modern aircraft on historic routes, or historic aircraft on modern routes, simply because the airport pair is the same.
• Unrelated aircraft types used to gain additional range, payload, speed, or performance.
• Substitutions based solely on similar seating capacity or flight time.
If a substitution is not clearly authorized, fly the aircraft listed in Phoenix or contact Air France Virtual staff before departure.
Pegasus ACARS & PIREPs
Pegasus is the normal method for tracking Air France Virtual flights and submitting PIREPs. Pilots are responsible for confirming that Pegasus is connected to the simulator and displaying the correct booking and aircraft before beginning the flight.
• Start Pegasus before major aircraft movement and confirm that tracking has begun correctly.
• Operate the flight normally through pushback, taxi, takeoff, cruise, descent, landing, taxi-in, and shutdown so Pegasus can record the required flight phases.
• At the destination, taxi to an appropriate stand, set the parking brake, complete shutdown, confirm Pegasus has recognized the final phase, and review the PIREP before submission.
Pilots should not manipulate position, flight time, distance, fuel, landing data, or flight phases to obtain credit or improve a score. Simulator pause, reposition, or recovery tools should be used only when necessary to resolve a genuine technical problem, and significant interruptions should be explained in the PIREP remarks.
Diversions, simulator crashes, disconnections, major route deviations, unusual landing events, or other circumstances that may affect the recorded flight should be disclosed in the PIREP remarks. A PIREP sent for staff review is not automatically a rejection; pilots should provide a clear explanation when requested.
Manual PIREPs or claims should be used only when a completed flight could not be properly tracked or filed because of a genuine Pegasus, simulator, or connection failure. Claims should include enough information for staff to reasonably verify the flight, including the flight number, route, aircraft, approximate times, flight duration, and supporting evidence when available.
Do not submit a manual claim merely to improve a score, correct a preference, or obtain credit for an incomplete flight.
Activity Requirements & Holidays
Air France Virtual maintains a light activity requirement to keep the pilot roster current while recognizing that real-world commitments come first.
Initial Activity Requirement
New pilots must complete at least one accepted PIREP within 30 days of joining Air France Virtual.
A reminder is issued after 21 days if the initial activity requirement has not yet been met.
Pilots who do not complete an accepted PIREP within the initial 30-day period may be removed for inactivity. This removal is not permanent, and eligible pilots may rejoin Air France Virtual.
Ongoing Activity Requirement
After completing the initial activity requirement, pilots must complete at least one accepted PIREP every 60 days.
A 14-day grace period follows the 60-day activity period before an inactive pilot is removed.
Rejected or invalidated PIREPs do not satisfy the activity requirement.
Holidays
Pilots may place their account on holiday for up to 30 days per year.
Holiday access becomes available once a pilot account is at least 30 days old.
While a pilot is on holiday, the normal ongoing activity requirement is paused. Holidays do not replace or waive the initial activity requirement for newly registered pilots.
Rejoining
Pilots removed for inactivity may rejoin Air France Virtual unless their account was permanently removed for another reason. Eligible returning pilots may retain their previous Air France Virtual identity and restored flight history, subject to current vAMSYS settings and staff review where applicable.
Air France Virtual is a hobby. If real life gets busy, use the holiday system when possible or return when your schedule allows.
Rank Transfers & Direct Entry.
Air France Virtual recognizes previous virtual airline experience through a direct-entry rank transfer program.
vAMSYS Transfers
Pilots with qualifying experience at another vAMSYS Virtual Airline may request an internal vAMSYS rank transfer. Eligible internal transfers are verified and processed automatically by vAMSYS.
External Transfers
Pilots transferring experience from a virtual airline outside vAMSYS may submit an external transfer request. External requests are reviewed by Air France Virtual staff and may require a publicly accessible pilot profile, statistics page, flight log, or other reasonable proof of previous virtual airline experience.
Direct-Entry Rank
The maximum direct-entry rank is Senior First Officer.
An approved transfer places the pilot at Senior First Officer and awards the minimum requirement for that rank:
125 flight hours
Rank transfers do not import a pilot’s complete previous flight history or total accumulated hours into the Air France Virtual logbook.
Captain, Senior Captain, and Commandant de Bord must be earned through Air France Virtual operations after joining.
Pilots requesting a transfer should submit the request before filing their first Air France Virtual PIREP. External transfer requests may be reviewed while the pilot continues normal Air France Virtual operations.
Transfer requests containing unverifiable or misleading information may be denied.
Flight Execution Standards
Air France Virtual pilots are expected to operate their aircraft in a reasonably realistic and safe manner throughout each flight.
Before Departure
• Confirm the booking, simulator aircraft, registration, route, fuel, payload, and weather.
• Review current NOTAMs, event requirements, and other applicable operational restrictions.
• Program the aircraft using the final operational flight plan and verify relevant performance data.
• When flying online, file and use a network flight plan that reasonably matches the intended operation.
• When using a normal engine-start sequence, allow the engines to operate for at least three minutes before takeoff.
• Observe reasonable taxi speeds. Sustained taxi overspeed may affect PIREP scoring or review.
During Flight
• Operate the aircraft within its published limitations using appropriate speeds, altitudes, fuel planning, and procedures.
• Follow ATC instructions when operating on VATSIM, IVAO, or another supported network. Aircraft safety always takes priority when an ATC instruction cannot safely be followed.
• Monitor actual fuel against the flight plan and divert or land when continuing to the planned destination would be unsafe or unreasonable.
• Do not conceal simulator crashes, disconnections, diversions, significant route deviations, or other material events. Explain them clearly in the PIREP remarks.
After Landing
• Clear the runway and taxi to an appropriate stand or gate.
• Allow the engines to remain running for at least three minutes after touchdown before final shutdown. Normal taxi-in time counts toward this cooldown period.
• At the gate, set the parking brake, complete shutdown, and confirm that Pegasus has recognized the final flight phase before submitting the PIREP.
• Review the completed PIREP and add remarks whenever an unusual event or operational deviation needs explanation.
A firm landing does not automatically invalidate a flight. Severe landing events or other abnormal flight data may be sent for staff review.
SimBrief & Flight Planning
Air France Virtual uses SimBrief as the primary flight-planning tool for scheduled operations.
• Generate the operational flight plan from the Phoenix dispatch workflow whenever available.
• Verify the departure, destination, alternate, flight number, aircraft type, and selected airframe before generating the final OFP.
• Review passengers, cargo, planned altitude, route, runway assumptions, weather, and fuel.
• Confirm takeoff weight, landing weight, zero-fuel weight, and fuel quantities remain within the limits of the simulator aircraft being used.
• Review current NOTAMs and ensure the planned route is appropriate for the current AIRAC cycle.
• Use the actual simulator aircraft profile when an approved aircraft substitution is being flown.
Air France Virtual normally uses the Air France 2017 OFP format and the airline ICAO identifier AFR.
Taxi Time
Phoenix may occasionally send zero taxi-out or taxi-in time to SimBrief. When this occurs, pilots should enter reasonable taxi assumptions manually before generating the final OFP.
A practical starting point is:
• 15 minutes taxi out
• 5 minutes taxi in
Adjust these values as appropriate for airport layout, traffic, weather, and expected runway use.
Pilots are responsible for reviewing the completed OFP and ensuring the plan is suitable for the aircraft and operation before departure.
Events, Tours & Rewards
Air France Virtual may offer special events, tours, focus airports, rosters, community goals, historic operations, and other limited-time activities.
• Read the applicable activity page before booking or dispatching a qualifying flight.
• Registration may be required before a flight can receive event or tour credit.
• Complete qualifying flights within the published start and end dates.
• Use the required route, aircraft, network, callsign, or pilot rank when specified.
• Meet any published landing-rate, takeoff, arrival, or other operational requirements.
• Tours must be completed in the published leg order unless the activity specifically states otherwise.
• Event-specific rules may be more restrictive than normal Air France Virtual operations and take precedence for that activity.
Points, badges, and other rewards are issued according to the configuration of the individual activity. Some rewards may be granted after each qualifying flight, while others are awarded only after completion of an entire event or tour.
Pilots are responsible for confirming that a flight meets all event requirements before departure. A normally valid Air France Virtual flight does not automatically qualify for an event or tour if the published activity requirements were not met.
Rules Authority, NOTAMs & Staff Decisions.
Air France Virtual operating rules are intended to provide a consistent, realistic, and enjoyable simulation environment. Because schedules, aircraft availability, events, and vAMSYS settings may change, pilots are responsible for reviewing current information before each flight.
Order of Authority
When instructions differ, pilots should follow the most current applicable guidance in this order:
The specific Phoenix route and booking
Current Air France Virtual NOTAMs and event rules
Direct staff instructions
The Air France Virtual Pilot Rules and Pilot Handbook
The Pilot Handbook documents standing procedures but does not override a later operational restriction, NOTAM, event requirement, or staff instruction. Air_France_Virtual_Pilot_Handbo…
Staff Review
Air France Virtual staff may review PIREPs, rank transfers, manual claims, aircraft substitutions, event qualification, unusual flight data, or other operational matters when clarification is required.
Pilots should provide accurate information and reasonable supporting evidence when requested. Honest simulator failures, diversions, go-arounds, connection problems, and other genuine operational issues will be considered based on the circumstances of the flight.
Deliberate falsification of flight data, attempts to obtain unearned credit, abusive conduct, or repeated disregard of Air France Virtual rules may result in corrective action up to and including permanent removal from the airline.
Independent Simulation Community
Air France Virtual is an independent flight simulation community and is not affiliated with, sponsored by, or operated by Air France or the Air France-KLM Group.
By registering with and participating in Air France Virtual, pilots agree to follow these rules and the current operational guidance published in Phoenix.