Virtual Airlines of Ukraine 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.
Virtual Airlines of Ukraine Virtual Airlines of Ukraine (VAU) simulates in VATSIM and IVAO environments operation of real Ukrainian airlines. Route network and Schedule based on real world network and schedules of Ukrainian airlines.
Airlines Fleet consists of airliners used by real airlines and includes Airbus A320 and A321, Boeing B737 Classic, B737NG and B767, Embraer E145 and E190, some other airliners.
Virtual Airlines of Ukraine system provides sufficient information to perform flights within VATSIM and IVAO network. We are not asking pilot to know aircraft documentation in details, aerodynamics, navigation, meteorology and all other necessary stuff. Each individual have his own understanding to fly "as real as it gets" and there are a lot of available information for self education through internet. We appreciate our pilots to know aircraft, local procedures and all basic information necessary to perform professional and safe online flights.
Virtual Airlines of Ukraine (VAU) emulates online operations of Ukrainian airlines in VATSIM and IVAO environments. Pilots, having proper permissions, could fly any regular flight on behalf of any airlines. Special subdivision Challenge Aero was created especially for private charter flights.
Own Software designed to simplify the process of preflight preparation by providing the following services to the pilot:
Upon completion of flight, the pilot get detailed information about the flight on Google Maps.
Required Software to fly with Virtual Airlines of Ukraine:
The basic sources of data for flight system are VATSIM or IVAO statistics and network client. The client utility (Soyuz FDR) is designed to transmit to the website more detailed information about the flight.
When performing scheduled and charter flights specified in the airline schedules pilot shall use a call sign corresponding to the Flight Number (for example, AUI101, WRC243, UDN505).
Flying online with the pilot’s personal call sign (for example, UKR7188) allowed for group flights or fly-ins as well as when it is not possible to use Flight Number call sign (call sign is in use by another pilot in network).
The booking is performed on the VAU website. A pilot selects an available scheduled flight, specifies some flight parameters and confirms the booking. The flight is registered in EUROBOOK and Flight Plan could be registered in VATSIM.
The pilot could book the flight in 24 hours prior to departure. But VATSIM keeps Flight Plan two hours only and, because of this, Flight Plan could be registered in 2 hours prior to departure. The airplane and the flight stay booked during 30 minutes after planned departure. But if the flight is not started by this moment, the booking is canceled.
IVAO pilots file the Flight Plan in IvAp client.
To perform the flight it is necessary to start Flight Simulator and Soyuz FDR, login to VATSIM (via vPilot, FSInn or SqawkBox) or to IVAO (via IvAp) with proper callsign, check the Flight Plan (if it was registered in VATSIM) or create a new one. VATSIM renews its statistic every two minutes (IVAO statistics renews every five minutes), so it could take a couple of minutes to confirm the flight in VAU system. It is recommended to make sure that the flight is accepted by VAU system before engine start, but it is possible by take-off.
If during the flight Internet connection is lost (or Soyuz FDR is off) longer of 20-30 minutes, the flight is cancelled.
The flight is considered as completed, if the pilot entered VAU system before take-off, was airborne, covered 5 nm or more, landed, speed reduced below 20 knots, engines were off. Only online flights are registered by VAU system.
It is prohibited to change time rate during the flight. In this case the flight is ignored and will not be included to statistic.
Regular flights schedule based on real airlines schedule. Recommended commercial loading and
number of passengers are generated daily for each flight considering that weight of passenger is
equal to
Departure and arrival time, length of route are supplemental information and could be specified during flight planning. On each flight could be assigned one or more types of aircraft by ICAO code. The pilot could choose any aircraft from available.
The company could include charters in common schedule, but these charters system treats as regular flights.
Recommended routes for regular flights are checked by administration and validated by current AIRAC. During flight planning system suggests a recommended route and flight level, however the pilot could enter own parameters.
To provide normal work of the VA system, it is necessary to put aircraft tail number in Remarks field of a Flight Plan in standard format REG/URDME (without hyphen). It is strictly recommended to use flight number as a callsign. In case if callsign is not corresponding to flight number, it should be included to Remarks in special format RTE=PS101.
Dispatch check route in accordance with current AIRAC and perform simplified fuel planning for some aircraft types. The total fuel quantity required to fly is the sum of the following quantities:
The system keeps the last landing airport as locations of pilots and planes. The company could allow flights of pilots and planes from current location only, or set more flexible rules.
The VA system registers weather conditions during take-off and landing: intensity of perceptions (by five-point scale), lateral component of wind, horizontal visibility. The weather conditions are treated as complicated if intensity of perceptions is higher of 3 points, or lateral component is 10-20 knots, or horizontal visibility is lower 1,1 nm.
Minimal horizontal visibility for last six months stated as RVR (runway visual range) for each pilot.
For each aircraft type next operational parameters are defined and controlled:
This parameters are published on aircraft page in "Limitation" part and on Dispatch page when flight is booked.
For all aircraft types next parameters are controlled:
TraineePilots without experience in VATSIM or IVAO network could be ranked as Trainee with some probation period. However, the better way is to start with Challenge Aero.
First OfficerAs a rule, all new pilot get First Officer rank and could fly regular domestic flights on some aircraft of Ukrainian Aviation Group. First Officer should make at least 10 flights without rude mistakes before apply for higher rank and clearances. The pilot could contact VAU management via forum or "Contact Us" form.
CaptainTo get Captain rank the pilot has to pass online practical test to prove his knowledge and skills within VATSIM Online Pilot rating requirements. Depending on test results Сaptain could get limited clearance for international flight (Ukraine and CIS) or unlimited.
Captain's shoulder strap depends on flight hours: above 500h, 1000h, 1500h or 2000h
| parameter | VAU | description |
| 60 | During these days a pilot should perform the required number of flights | |
| 1 | Minimal numbers of flights required to fly during reference period to confirm a membership | |
| 91 | Numbers of days to count average pilot rating | |
| 5 | Maximum days of aircraft idle time out of hubs | |
| 5 | Pilot should report about flight if penalty is above specified value | |
| Yes | If Yes, charters are permitted. The pilot could fly any available aircraft by any route. | |
| Yes | If Yes, CARGO charters are permitted. The pilot could fly any available cargo aircraft by any route. | |
| Yes | If Yes, the pilot could fly only airplanes located in departure airport. For example, the pilot cannot fly from UKCC using airplane located in UKBB. | |
| No | If Yes, the pilot could fly only from his current location. For example, if the pilot is in UKBB, he cannot fly from UKCC. | |
| No | If Yes, the pilot could use any callsign. If No, the pilot should use flight number (for regular flights), or tail number (for private charters), or personal VA callsign. | |
| Yes | In general, any flight should be finished in destination or alternate airfield. If the parameter sets as Yes, the pilot could land to any airfield, but perhaps with some penalty (according to parameter 'Penalty for not arrival at destination'). If the parameter sets as No, in case of landing to not destination or alternate the flight will be ignored by the VA system. | |
| Yes | If No, in case if timerate was changed during the flight, it will be ignored by VA system. | |
| Yes | If there is flight mission for the aircraft, other flights are not permitted | |
| 85 | Average load of aircraft. Required to generate recommended aircraft loading. | |
| 2 | 0 - No additional cargo, luggage only; 1 - Always maximum payload; 2 - Random | |
| 170 | Average weight (in pounds) of crew and cabin crew members | |
| 190 | Average weight (in pounds) of passenger with carry-on baggage | |
| 40 | Average weight (in pounds) of checked luggage | |
| Yes | If Yes, booked flight is registered in EUROBOOK. | |
| Yes | If Yes, Flight Plan could be registered to VATSIM. | |
| 80 | The minimum vertical speed of touchdown, when landing is still treated as perfect | |
| 240 | The maximum vertical speed of touchdown, when landing is still treated as perfect | |
| 340 | The maximum vertical speed of touchdown, when landing is still treated as normal. If above the landing is hard. | |
| 700 | If vertical speed of touchdown is above, the landing is severe hard: gear damage is possible | |
| 0 | Possible bonus if aircraft loading is equal to recommended within 10%. | |
| 5 | Possible bonus for long range flight. The longer flight, the bigger bonus. | |
| 5 | Possible bonus for landing with vertical speed within 80-240 ft/min. | |
| 0 | Possible bonus for take-off in bad wather conditions. | |
| 0 | Possible bonus for landing in bad wather conditions. | |
| 5 | Possible bonus for return airliner to hub | |
| 5 | Possible bonus for the execution of the flight task | |
| 99 | Crash is detected by signal 'CRASH' from FSUIPC, or in case of hit the ground with vertical speed over 1600 fpm. | |
| 15 | Stall is detected by FSUIPC signal. | |
| 2 | Overspeed is detected by FSUIPC signal. | |
| 2 | Exceeding flaps extending speed limit. | |
| 2 | Exceeding gear operating speed limit. | |
| 2 | Descending below 500 ft with gear up and flaps retracted. | |
| 5 | Touchdown vertical speed is over 340 ft/min. | |
| 20 | Touchdown vertical speed is over 700 ft/min. | |
| 2 | Landing weight exceeds limit. | |
| 1 | Possible penalty if the plane landed to airfield, which is not destination or alternate. | |
| 1 | Possible penalty for non-critical pilot mistakes. | |
| 10 | Possible penalty for "refueling" during the flight. | |
