At Iberia Virtual, our goal is to offer pilots the chance to simulate Iberia’s operations in a fun and realistic way. We do not enforce strict activity requirements or rigid rules that take away from the enjoyment of flight simulation, but it is essential to understand that flying for a virtual airline involves more than just using a flight tracker like Volanta. Generally, we do not recommend virtual airlines as a starting point for newcomers to flight simulation, as we expect our members to have a basic understanding of how real-world flights are planned and operated.

This document sets out the rules and policies that provide a clear structure for all our pilots to make their flightsim experience feel more purposeful. If we come across serious rule violations, PIREPs may be declined or invalidated; however, our main focus is always on offering support and constructive feedback where needed. We encourage pilots to seek assistance through our Discord server, where they’ll find a welcoming community—the invite link can be found on your vAMSYS dashboard.

As in real aviation, it is always better to ask if you are unsure. We have a fantastic community of pilots on Discord, ready to assist. With that in mind, we wish you safe flights and many enjoyable hours with Iberia Virtual.

We reproduce seven different AOCs. Each one has its own ATC callsign.

The bookable city pairs in vAMSYS reflect those; however, two or more AOCs may operate the same route. The AOC’s “IBC” or “ANS” refer to classic flights and routes, and with it you can only fly routes with classic models and liveries.

Refer to the table below.

PIREPs that intentionally use time acceleration will be invalidated without exception. PIREPs that intentionally use time acceleration will be invalidated without exception. Similarly, PIREPs that make use of slewing or repositioning functions—except for gate changes before departure—will also be invalidated. Pausing during a flight is permitted, but if the total paused time exceeds 5% of the flight’s duration, it will be subject to review by the Staff Team. Flights should be completed in one continuous session, so starting a flight, pausing for an extended period, and resuming later is not allowed. However, we understand that real life doesn’t always align with flight simulation plans. In most cases, a brief explanation of why you needed to pause will be enough for the PIREP to be accepted after review. While we do not require pilots to remain at the controls at all times—since real-world long-haul flights include mandatory rest periods—you must return to the flight deck by the Top of Descent at the latest. Flights that rely on a “Pause at Top of Descent” function will be rejected. Additionally, please refrain from using the “Active Pause” feature in MSFS, as it causes Pegasus to log inaccurate flight times. Flights that excessively use Active Pause and accumulate unrealistically long flight durations while paused will be invalidated.

Pilots must ALWAYS use an Iberia livery when flying. PIREPs submitted with liveries from other airlines (or without any livery) will be automatically rejected. Additionally, pilots must ensure their livery matches the type of route they are flying: an Iberia Classic route cannot be flown with a modern livery, nor can a Binter route be operated with an Iberia livery. Iberia Express routes must be flown with the appropriate Iberia Express livery. If an exception is necessary, it must be noted in the PIREP comments for staff review; otherwise, the PIREP will be automatically invalidated.

A wide selection of Iberia and Binter liveries—both classic and modern—is available for download in our Hangar. You can access the Hangar through the vAMSYS website using your vAMSYS email and password.

When you submit a PIREP, Pegasus and vAMSYS log the livery used and check it against past flights. If the livery has never been used before, it goes into a manual review for the admin team to verify. This helps make sure pilots are using the right aircraft and a suitable livery.

If your PIREP is held for livery review, this is not a problem and you have no need to worry. As long as you used a valid livery, you can carry on flying. A staff member will check it, approve it if it’s fine, and add it to the approved list.

We provide a diverse selection of both modern and historical aircraft. While each route has designated bookable aircraft, pilots should refer to our Aircraft Substitutions Policy document for a complete list of permitted substitutions. This policy is in place to offer greater operational flexibility, ensuring pilots are not strictly bound to fleet limitations that may not always reflect real-world scenarios. However, it is important to understand that the Aircraft Substitutions Policy consists of strict rules, not just recommendations. For instance, a route booked with a CRJX cannot be flown using an A320. Such substitutions will not be accepted.

In the flight simulation community, there is a growing trend of aiming for the lowest possible landing speeds. While a smooth landing is satisfying, prioritizing an ultra-low vertical speed is neither practical nor safe. Airbus recommends that landings be executed within a range of 1 to 1.2G, which translates to a vertical speed between -150 and -200 feet per minute (fpm). The further a pilot deviates from this range, the fewer points they will receive for the landing.

PIREPs with landing rates exceeding -350 fpm will be flagged for review, as this is considered an excessively hard landing. Any landing recorded at -600 fpm or greater will be automatically invalidated, as this exceeds the structural limits of the aircraft and is classified as a crash.