 |
Schedule | Fleet | Crew | Forum | Belavia |   |
| Statistics | ||||
|
Belavia |
|||
| pilots: | 22 | flights: | 4,112 | |
| planes: | 20 | hours: | 6,208 | |
| name | dept. | dest. | ||
| name | dept. | dest. | ||
«Belavia» Virtual airlines simulates in VATSIM environment operation of real Transaero airlines:
| Airlines | ICAO | IATA | Callsign | pilots | flights | hours | |
 | Belavia | BRU | B2 | BELAVIA | 159 | 4,112 | 6,208 |
Airline Fleet consists of airliners used by real airlines and includes Boeing B737 Classic, B737 NG, B767 Bombardier CRJ1, CRJ2 Embraer E170, E190 Tupolev Ty-154.
Route network and schedule based on real world network and schedules of Belavia airlines.
Pilots – enthusiasts of virtual aviation, real pilots and air traffic controllers.
Pilot Software is developed by VAU (www.vau.aero) creators and provides the following information to a pilot:
Belavia system provides sufficient information to perform flights within VATSIM network.
Required Software to fly with Belavia:
Belavia is open for pilots with 50 or more online hours in VATSIM.
Belavia Virtual Airlines emulates online operations of real Belavia in VATSIM environment.
The basic sources of data for flight system are VATSIM statistics and network client. The client utility (FS Agent) is designed to transmit to the website more detailed information about the flight.
The site uses the following units: feet, pounds, nautical miles, knots. All times are in UTC.
When performing scheduled and charter flights specified in the airline schedules pilot shall use a call sign corresponding to the Flight Number (for example BRU243).
Flying online with the pilot’s personal call sign (for example, BRU7777) 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 VATSIM).
The booking is performed on the 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.
To be able to register Flight Plan in VATSIM it is necessary to allow pop-up windows for site https://bru.soyuz.aero/ in Internet Explorer.
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.
To perform the flight it is necessary to start Flight Simulator and FS Agent, login to VATSIM (via FSInn or SqawkBox) 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, 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 FS Agent 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.
Flights schedule based on real airline schedule. Recommended commercial loading and number of passengers are generated daily for each flight considering that weight of passenger is equal to 170 lbs independent of aircraft type or cabin class.
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/VPBVR (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/BRU0123.
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:
First Officer TraineeInitially each new pilot is qualified as «First Officer Trainee»/ This rating allows to perform only training flights with according missions. No other permissions required.
First OfficerAfter successful completion of four assessment flights the pilot gets promoted to the rank of «First Officer». Thins rank gives access to flights within the Commonwealth of Independent States. In order to achieve access to international flights, the pilot must pass both practical and theoretical tests (optional). The practical test implies a training flight to one of the European cities. This flight can be requested after at least 10 flights as a «First Officer». All tests are held by one or several authorised VATSIM ait traffic controllers with CTR rating or higher. The tests are performed at least once in two weeks. The details are distributed to the involved pilot(s) several days prior to tests. The necessary program includes radio commucation test with English phraseology, general ATC commands, ability to perform VOR and NDB approaches along with RVSM technics, METAR, NOTAM and other essential skills needed during online flights.
CaptainThe «Сaptain» rank allows gives access to all international flights using any aircraft type. The pilot can request this promotion after successful completion of twenty flights as a First Officer.
These shoulder straps meet overall online hours: up to 500h, up to 1000h, up to 1500h, up to 2000h
| parameter | BRU | description |
| 99 | 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 | |
| 61 | Numbers of days to count average pilot rating | |
| 7 | Maximum days of aircraft idle time out of hubs | |
| 35 | Pilot should report about flight if penalty is above specified value | |
| No | If Yes, charters are permitted. The pilot could fly any available aircraft by any route. | |
| No | 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. | |
| No | 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 | |
| 86 | Average load of aircraft. Required to generate recommended aircraft loading. | |
| 2 | 0 - No additional cargo, luggage only; 1 - Always maximum payload; 2 - Random | |
| 0 | Average weight (in pounds) of crew and cabin crew members | |
| 190 | Average weight (in pounds) of passenger with carry-on baggage | |
| 50 | 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. | |
| 40 | The minimum vertical speed of touchdown, when landing is still treated as perfect | |
| 400 | The maximum vertical speed of touchdown, when landing is still treated as perfect | |
| 500 | 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 | |
| 1 | Possible bonus if aircraft loading is equal to recommended within 10%. | |
| 1 | Possible bonus for long range flight. The longer flight, the bigger bonus. | |
| 1 | Possible bonus for landing with vertical speed within 80-240 ft/min. | |
| 1 | Possible bonus for take-off in bad wather conditions. | |
| 1 | Possible bonus for landing in bad wather conditions. | |
| 1 | Possible bonus for return airliner to hub | |
| 1 | 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. | |
| 50 | Stall is detected by FSUIPC signal. | |
| 5 | Overspeed is detected by FSUIPC signal. | |
| 5 | Exceeding flaps extending speed limit. | |
| 5 | Exceeding gear operating speed limit. | |
| 10 | Descending below 500 ft with gear up and flaps retracted. | |
| 10 | Touchdown vertical speed is over 340 ft/min. | |
| 50 | Touchdown vertical speed is over 700 ft/min. | |
| 5 | Landing weight exceeds limit. | |
| 0 | Possible penalty if the plane landed to airfield, which is not destination or alternate. | |
| 5 | Possible penalty for non-critical pilot mistakes. | |
| 50 | Possible penalty for "refueling" during the flight. | |