I hereby agree to the storage and publishing on Soyuz Alliance sites of my personal data to the extent of my forename and surname, VATSIM id, IVAO vid, and statistics of my flights in Soyuz Alliance. The email address could be used exclusively by site administration to contact me.

I agreed to get email notifications related to the functioning of virtual airlines, but have the ability to unsubscribe from them any time.

I was informed that the site uses cookies for authorization only and could be switched off.

I am able to cancel my membership in Soyuz Alliance anytime and ask the administration to remove my name and email from the database forever.


Flight Data Recorder

Soyuz FDR (Flight Data Recorder) is designed to work in Soyuz Alliance system to transmit to the website detailed information about the flight. The basic source of flight data is VATSIM and IVAO statistics. Soyuz FDR client registered detailed flight information and send it to a server. Only online flights in VATSIM or IVAO networks are allowed.

Flight booking, information about current flights, statistics and other information are available on this site.

It is recommended to install the program to separated folder, because it creates a lot of files. Under Windows 7 (8) do not install the program to Program Files or Windows folders, because by default they are "read only" and Soyuz FDR will not be able to create working files.

Registered FSUIPC (XPUIPC for X-Plane) and .Net 3.5 (or higher) are required.

Follow simple rules:
  • Soyuz FDR has to be started before engine start or at least before take off
  • Do not take off until the flight is not accepted! It is recommended to make sure that the flight is accepted by the system before engine start
  • If Flight Simulator was crashed, you have to stop Soyuz FDR and delete current flight in Profile
  • If you change aircraft type, you should restart Soyuz FDR

Flight will be registered by the system if:
  • Pilot's callsign in VATSIM or IVAO is the same as booked.
  • Pilot's callsign is corresponded to flight number (or flight number included to Flight Plan Remarks in special format RTE=PS101).
  • Booking should be active. Booking is still active in 30 minutes after planned departure time. If by this moment flight is not registered by the system, booking will be deleted.
  • Flight Plan should be registered in the network (VATSIM or IVAO). It could take up to 5 minutes to get Flight Plan from the network to the system.
  • The airplane should be on a ground in departure airport.
  • Flight Plan should correspond to booking:
    • Airplane type (ICAO code)
    • Tail number (included to Flight Plan Remarks in standard format REG/ABCDE)
    • Departure airport (ICAO code)
    • Destination airport (ICAO code)

The program starts in background mode, status of flight is shown in system tray:

 1. Waiting mode. Connection to FSUIPC is established, waiting for Flight Plan from the network (VATSIM or IVAO).
 2. Online. The flight is registered in VA system, Flight Plan is corresponding to booked parameters.
 3. Online. The flight is refused by VA system, because Flight Plan is not corresponding to booked parameters.
 4. There is no connection to FSUIPC. Perhaps, FS is not running.
 5. There is no connection to site. Perhaps, wrong login or password.

Main window could be opened by double-click on system tray icon or via context menu Options (right-click on system tray icon).

You have to set your Login (e-mail) and Password (the same as for Soyuz Alliance account).

Optionally, you could set checkbox Sound to turn on sound signals and Warnings to receive flight alerts.

All settings are saved to ini-file.

In online mode main window shows aircraft type and tail number, flight number, departure and destination airports. After landing, vertical speed of touchdown is shown.

Debug mode could be used to get more information about programm errors in case of need. Debug messages are shown in main window.

Main window indicators shows system status. The first light shows connection to site, the second shows connection to simulator (via FSUIPC), the third shows connection to the network (VATSIM or IVAO):

 no FS+HTML connect   No connection both to FSUIPC and site
 no FS connect  No connection to FSUIPC. Perhaps, FS is not running
 no HTML connect  No connection to the site. Perhaps, wrong login or password
 NOT REGISTERED  The flight is refused by Soyuz system
 OFFLINE  Network connection to the network (VATSIM or IVAO) is lost
 online  Flight is registered by Soyuz system

 Your e-mail: 
Chat on Discord: https://discord.vacc-ua.org
 Nothing is real