Virtual airlines Challenge Aero is a special subdivision of Virtual Airlines of Ukraine and emulates in VATSIM and IVAO environment charter and general aviation flights on different types of craft and copters. There is no any regular schedule in Challenge. Pilots, having proper permissions, may fly any available aircraft from any airport to any destination. No booking is required, but available.
Required Software to fly with Challenge Aero:
The basic source of data for system is VATSIM and IVAO network clients. The client utility (Soyuz FDR) is designed to transmit to the server detailed information about the flight.
The system simplifies a 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.
When flying an airplane of Challenge Aero pilot shall use aircraft tail number as a call sing -
without hyphen (for example,
Using of any other type of callsign is not recommended.
A pilot of Challenge Aero could fly any available aircraft by any route without booking
(despite booking is available). To do this the pilot has to use aircraft tail number as a callsign
or put the tail number to Remarks field using standard tag
The booking could be performed on the website. A pilot selects an available aircraft, choose departure and destination, specifies some flight parameters and confirms the booking. The flight is registered to EUROBOOK and Flight Plan could be registered to VATSIM.
Rank of Private Pilot allows to fly light craft only. To get permissions to fly other types, the pilot has to obtain the rank of Commercial Pilot or Captain. To apply for higher rank and clearances the pilot could contact management via forum or Contact Us form.
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 FSInn, vPilot 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 every five minutes), so it could take a couple of minutes to confirm the flight in the system. It is recommended to make sure that the flight is accepted by the system before engine start, but it is possible by take-off.
If during the flight Internet connection is lost (or Soyuz FDR is off) for longer of 25-30 minutes, the flight is cancelled.
The flight is considered as completed, if the pilot entered the system before take-off, was airborne, covered 5 nm or more, and landed. The flight is finished when engines stopped after landing and speed reduced below 20 knots.
Only online VATSIM or IVAO flights are registered.
It is prohibited to change time rate during the flight. In this case the flight is ignored and will not be included to statistic.
All new pilots are ranked as Private Pilot. Private Pilot could fly any route, but on light aircraft only. Flight clearance could be limited to Russian-speaking space for pilots with pure English.
Ranks of Commercial Pilot and Captain get permissions to fly wider range of aircraft types. Captain could fly any Challenge Aero aircraft.
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:
|90||During these days a pilot should perform the required number of flights|
|2||Minimal numbers of flights required to fly during reference period to confirm a membership|
|91||Numbers of days to count average pilot rating|
|0||Maximum days of aircraft idle time out of hubs|
|0||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.|
|No||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.|
|No||If No, in case if timerate was changed during the flight, it will be ignored by VA system.|
|No||If there is flight mission for the aircraft, other flights are not permitted|
|90||Average load of aircraft. Required to generate recommended aircraft loading.|
|0||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|
|360||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%.|
|0||Possible bonus for long range flight. The longer flight, the bigger bonus.|
|0||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.|
|0||Possible bonus for return airliner to hub|
|0||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.|
|10||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.|
|0||Possible penalty if the plane landed to airfield, which is not destination or alternate.|
|1||Possible penalty for non-critical pilot mistakes.|
|0||Possible penalty for "refueling" during the flight.|
Soyuz FDR (Flight Data Recorder) is designed to work
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.
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
You have to set your
Optionally, you could set checkbox
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.
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|