Skip to main content

A319/A320 Fleet Bulletins

25 DEC 23 | United Airlines A319/A320 Engine Variants and the Fenix A320​

Summary​

United Airlines operates both the A319 and A320 exclusively using IAE V2500 engines. The Fenix A320 is currently only modeled with CFM engines (and the A319 is not yet released).

As we await the release of Fenix Block 2 with IAE engines, use of CFM engines is permitted. When the IAEs are released, there will be a transition period where we reset the approved A320 liveries inside vAMSYS and start cautioning pilots who file PIREPs with CFM engines, and at the end of that transition period we will begin requiring the use of IAE engines.

For all other A319/A320 addons that allow the use of IAE engines, we require that IAEs be used.

25 DEC 23 | Flap Retraction when Parking in High Temperatures​

Summary​

In the summer months, we regularly see PIREPs for Airbus flights where the pilot left their flaps in position 1 when parking because the outside air temperature was 30C or higher, and they were consequently deducted points by the automated PIREP scorer for not retracting flaps prior to parking.

We are aware of this Airbus procedure and acknowledge it is realistic/correct. However, Pegasus does not/cannot record the temperature when you park, and even if it could the PIREP scorers do not have sufficient logic for them to know that you left the flaps out for that reason, only that you left them out.

Since we cannot configure the scorer to correctly detect these conditions, you can either leave the flaps out to be realistic and accept the points deduction, or you can retract the flaps to get the points. It would be too much administrative overhead for us to correct all PIREPs for this condition, and we want to leave the flaps retracted prior to parking scorer in place to make sure pilots are following the procedure that is correct more of the time.

Please reach out to us via Discord with any questions.

25 DEC 23 | Fenix A320 and GSX: False Takeoffs in Log​

Summary​

When using the Fenix A320 along with GSX, you may notice something similar to the following in your PIREP log in Pegasus:

[18:05:13] Engine 1 is on
[18:05:42] Taxiing to runway
[18:05:50] Taking off
[18:06:34] Rejected takeoff conditions met, returning to taxiing phase
[18:07:44] Engine 2 is on

This is a known bug with how the Fenix and GSX interact with each other and is not a problem with Pegasus or vAMSYS. Unfortunately this will cause a points deduction on your PIREP — "-10 - Engines Not Warmed Up (3 Mins)" and "-100 - Flaps not set before Takeoff”.

Suggested Actions​

If this happens to you, please leave a comment on your PIREP alerting staff. We will recognize the sequence in the log and can remove the points deductions from your PIREP.

Some users have had good luck avoiding this happening by ensuring they have removed the chocks in the Fenix EFB before requesting pushback in the GSX menu, however this is not a certain fix.

For those who use FSRealistic, it has been suggested to disable the “Movement” feature under the “Wind Ambience” setting, this has reportedly solved the issue for many people.