Light logo Small logo
Dark logo Small logo
Light logo
Dark logo
Before you join, please read the following thoroughly

This page is a brief rundown of our general operational requirements and policies. More detailed information is available after joining.

PVA has no relationship with Piedmont Airlines, American Airlines or any of its affiliates or subsidiaries. We are an independent group of hobbyists and are in no way endorsed by Piedmont or American.

What's PVA?

The Piedmont Virtual Airlines Historical Group (PVA-HG) is one of four virtual airlines in the Fusion Virtual Airline Alliance (FVAA). We are based on the real-world Piedmont Airlines as it existed from 1948 through 1989 but with a twist - we specialize in offering curated historical schedule sets from other vintage airlines. Some of our most popular offerings at this time are Northwest Airlines, Skybus Airlines, and Virgin America - but we offer many more.

What's vAMSYS?

vAMSYS (Virtual Airline Management System) is a platform to which we, VirtUAL, subscribe.

Each VA on vAMSYS is a separate entity and are operated by different owners and volunteers.


Simulators Supported

We do not and cannot support any mobile or console based simulators.

Activity Requirements
  • We require one (1) PIREP filed via Pegasus within ten (10) days after joining.

  • Thereafter, we require one (1) PIREP filed via Pegasus every ninety (90) days, with a ten (10) day grace period.

  • Rejected PIREPs count towards the activity requirement.

  • Invalidated PIREPs do not count towards the activity requirement.

  • PIREP Claims do not count towards the activity requirement.

  • After completing the initial activity requirement, 180 days' worth of "holiday" time is available.

  • If you are marked inactive, you can rejoin and your prior pilot ID and PIREP/points history will be restored.

Livery Requirements

In order for your PIREPs to be accepted, we have the following requirements for liveries:

  1. The booked aircraft type must match the flown aircraft type. This extends to sub-variants: you cannot book an A300 and fly an A310, or book a B742 and fly a B744. They must match.

  2. The booked airline must match the airline of the flown livery. A Piedmont flight must be flown with a Piedmont livery, a Northwest flight with a Northwest livery, etc.

  3. Historical liveries are obviously allowed as they're the only kind of livery here -- so long as the aircraft you are flying wore that livery. For example, Piedmont's F-28s never wore their original livery.

  4. Fictional liveries are not allowed; neither are blank, "house" or manufacturer liveries.

Prohibited Aircraft Add-ons

We understand that by prohibiting certain add-ons, we may disappoint some users. We also understand that these prohibitions exclude several aircraft types entirely from MSFS at this time. An aircraft type being included in our schedules does not mean that any add-on representing that type is approved for PIREPs.

The PVA-HG team wants these aircraft types to be represented as badly, if not more so, than our users do. We have a certain standard of realism and quality that we want to promote, and so for add-ons that we feel fall outside of these standards, or add-ons that we think take advantage of the flight simulation community, we chose to exclude them so that we are able to deliver on one of our goals: maximizing realism where it counts.

 The following aircraft are prohibited from use; any PIREP filed with them will be invalidated.
- MSFS FlyByWire/Default A320neo (All A320s in our schedules are A320ceos; a NEO cannot be substituted for them)
- MSFS CaptainSim 767
- MSFS FSS 727F (prohibited from operating passenger flights, it can be used for cargo B727 flights)
- MSFS LatinVFR Airbus Family
- MSFS RHDSimulations 767-300ER
- MSFS SkySimulations MD-11
- Use caution with the XP11/12 Rotate MD-11. The cargo variant must be used for cargo flights and the passenger variant must be used for passenger flights, they cannot cross-substitute.