Blair S - 1358329
-
Posts
1142 -
Joined
-
Last visited
-
Days Won
25
Content Type
Profiles
Forums
Calendar
Posts posted by Blair S - 1358329
-
-
The operations department have been working hard on several projects over the last few months, including finalizing vatSys sector files and update integration, alongside updating several documents including Local Instructions, vMATS, and policy changes. On top of this, the Operations team worked hard to build and update the sector files for World-Flight, ensuring that the controller team were able to easily manage the vast amounts of traffic.
As always, the operations team is always looking for people who are passionate and would like to assist the team. If you think you have what it takes to help manage the Airspace over the VATPAC sky, send an email to [email protected]; we would love to have you on board!
Projects last 3 months
- Worldflight updates, including adding radar sites, updating sector files, and reviewing frequencies.
- Pacific region SID/STAR & Airspace review.
- AIRAC 2013 released with minor updates to Australian RNAV points.
Ongoing projects (next 1 – 2 months)
- YBBN & YMML Local Instruction review being completed as a priority with an expectation of release late January.
- Controller Position & Rating Policy under review with changes being proposed to make clearer the non-standard position guidelines.
Future Projects (next 3 months)
- vMATS annual review to be carried out, making use of the real-world MATS provided by ASA.
- Controller Position and Frequency audit to better align with real world procedures.
Cheers,
--
Ryan McDonaldActing Director of Airspace and Publications
VATSIM Australia Pacific -
From the Director of Events
2020 is wrapping up fast, so I am very happy to welcome you to the Events Department section of the scope where we intend to update you on changes to the Events Department, as well as tease a few changes coming in 2021!With the 2020 calendar finishing up, we have released the 2021 events calendar detailing 17 thrilling events we will be débuting next year! You can find info on when we will be hosting each of these events here - https://forums.vatpac.org/topic/18457-major-events-list-2021/
Remember that the Events Team is always open to feedback about all of the events that we conduct. Please contact us via https://feedback.vatpac.org/ or email the Director of Events via [email protected].
Thank you all for being apart of the VATPAC Division. I look forward to serving this community into 2021 and am hoping for a successful 2021 within the Events Department!
Cheers,
Josh Micallef
Director of Events
VATSIM Australia Pacific
Staff Changes
There has only been one staff change within the Events Department since the last edition of the scope.- 10SEP20 | Cameron Wilbraham appointed as Deputy Director of Events (VATPAC15)
As of the 1JAN21, Cameron's role name will change to "Events Manager" as per the organisational structure changes outlined here.
Upcoming Major Events
You can see all the upcoming events for 2021 in our 2021 Events Calendar - https://forums.vatpac.org/topic/18457-major-events-list-2021/We will post information about our events at minimum one month before the scheduled event date, you can find a full list of our upcoming announced events here - https://forums.vatpac.org/forum/57-event-announcements/
Future Projects
There have been a few little projects running around the office of the Events Department over the past few months - We are looking to improve the process of rostering systems and policies surrounding rostering into 2021, stay tuned! -
-
LAHSO Tutroial
An informative video made by VATPAC's Nick Falcione on Land & Hold Short Operations (LAHSO) in Australia.
-
Welcome to our first major event for 2021, Transcon Shuttle Sydney. Fly from either Broome (YBRM), Alice Springs (YBAS) or Adelaide (YPAD) to Sydney (YSSY). Each departure airport has a different departure window based off the flight time.
Event Details:
Transcon Shuttle is an event designed to provide pilots with the opportunity to receive ATC services as they cross the country from nominated departure locations, inbound chosen arrival aerodrome.This round, we have provided you with three departure airports ranging between 4.5 -> 2hrs in length all inbound one arrival aerodrome. This event is designed to provide pilots with the opportunity to explore the country from three different locations, travel across the country, and arrive into one concentrated arrival aerodrome. Controllers get the chance to control new and exciting locations with larger levels of traffic and create a sequence inbound to the arrival aerodrome.
Departure Window:
For each of the departure aerodromes, a 2-hour controller block has been rostered to provide ATC services to departure aircraft. You are recommended to depart during this time to arrive in Sydney with ATC Services. The rostered time for all aerodromes is below:- Broome: 0300z - 0500z
- Alice Springs: 0430z - 0630z
- Adelaide: 0530z - 0730z
The planned arrival time into Sydney is between 0730-0930z however ATC will be online between 0630z-1030z .
Routes:
BRM-SYD | 4.5 Hour Flight:
ROUTE: BRM CESCI T11 AS A576 PKS H319 TARAL Y59 RIVET TESAT
ASP-SYD | 3 Hour Flight:
ROUTE: AS KALUG A576 PKS RIVET TESAT
ADL-SYD | 2 Hour Flight:
ROUTE: AD PANKI H247 CULIN Y59 RIVET TESAT
ATC Positions:
Controllers interested in controlling the event are encouraged to submit their ATC Applications here - Applications will remain open until 4 Days before the event date, of which the roster will be compiled on the website.Non-standard positions will be rostered depending on the number of ATC Applications recieved. A non-standard position is denoted with an (*) beside the callsign.
Login Callsign Frequency AD_DEL Adelaide Delivery 126.100 AD_GND Adelaide Ground 121.700 AD_TWR Adelaide Tower 120.500 AD_APP Adelaide Approach 124.200 BRM_GND Broome Ground 121.700 BRM_TWR Broome Tower 126.000 AS_TWR Alice Tower 118.300 SY_APP Sydney Approach 124.400 SY-D_APP* Sydney Director 126.100 SY_GND Sydney Ground 126.500 SY_TWR Sydney Tower 120.500 BN-TRT_CTR Brisbane Centre 133.200 ML-ASP_CTR Melbourne Centre 131.800 ML-BKE_CTR Melbourne Centre 128.200 ML-TBD_CTR Melbourne Centre 125.300 ML-WOL_CTR Melbourne Centre 125.000 ML-GTH_CTR* Melbourne Centre 122.750 Scenery:
YSSY - Sydney International Airport:
Payware - FlyTampa v2 (FSX/P3D)
Freeware - AVSIM (FSX/P3D)
Freeware - ISDG (xPlane)YPAD - Adelaide:
Payware - AUSCENE 2 (FSX/P3D)
Freeware - AusFS(FSX/P3D)
Freeware - TGD (xPlane)YBAS - Alice Springs
Payware - ORBX (FSX/P3D)
Freeware - Flightsim (FSX)
Freeware - Xplane.org (Xplane)YBRM - Broome International Airport
Payware - ORBX (FSX/P3D)
Freeware - Kym Burton (FSX/P3D)
Freeware - Xplane Gateway (Xplane)
Should you have any questions, queries or suggestions, please contact the events department via the VATPAC forums or by emailing [email protected] or via feedback.vatpac.org.
We Look forward to seeing you at our first event for 2021!
-
Bluetooth is also very handy for calling CENSAR to amend your SARTIME or call your flight school if something goes wrong. Some members of VATPAC have been known to use it for discord calls as passengers also.
LightSpeed Zulu’s and second hand A20 are abit cheaper and also get the job done however think of it as an investment as they will last forever and be far more comfortable. People still use the A10’s from the dark ages...
- 1
-
Welcome to the Community Hangar
What is Community Hangar?
Community Hangar is a weekly post which invites the community to comment, share and vote on all aspects of Aviation. We encourage the community to have an open discussion on each topic and become involved.This week in the Hangar:
We take a stroll back down memory lane to look at one of the most influential aspects in Australian aviation history, Sydney (Kingsford Smith) Airport. In 1921 the Australian Government purchased a 65-hectare block of land with fights beginning in 1924. In 1933 the first gravel runways were built and by 1949 the airport had three major runways: 11/29, 16/34 and 04/22. In the late '50s the first paved runways were made at the airport, Runway 07/25 and Runway 16/34, which was extended into Botany Bay to allow international jet traffic. In the late '60s the new International Terminal and later in 2000 with the redevelopment of the Ansett Terminal.The question we pose the community is, do we feel that Mascot was the ideal location for the airport? If you were the designer, where would you have built it, and what would you have done differently?
-
This message (including attachments) is intended for the addressee named above. It may also be confidential, privileged and/or subject to copyright. If you wish to forward this message to others, you must first obtain the permission of the author. If you are not the addressee named above, you must not disseminate, copy, communicate or otherwise use or take any action in reliance on this message. VATPAC is required to comply with the Privacy Act 1988 (Cth) and you should note that the contents may be subject to copyright and therefore may not be reproduced, communicated or adapted without the express consent of the owner of the copyright. If you have received this message in error please notify the sender and delete from any computer.
-
Technically that should also have this in there also.
VATPAC is required to comply with the Privacy Act 1988 (Cth) and you should note that the contents may be subject to copyright and therefore may not be reproduced, communicated or adapted without the express consent of the owner of the copyright.
-
How does a Transceivers Work?
Example 1. The transceiver is 100ft AMSL. Therefore, the range on the ground is 12.3nm. If you are AGL outside of this area, you won't be able to transmit/receive. The aircraft down the bottom is at 35000ft, because of their height, it gives them a range of 230nm. They will be able to broadcast and receive from that transceiver. The higher an aircraft is, the greater range they have.
Example 2: Both aircraft are within range of the transceiver in this photo, however, aren't in range of each other. This means the controller can communicate with both aircraft, however, the aircraft won't be able to hear each other.
Example 3: Another possibility is that an aircraft may be within your range however, isn't in range of the transceiver. This is a situation where you could relay their message to the controller/appropriate traffic.
What about when ATC is offline?
Where a transceiver isn't available, you will have a fixed broadcast range ring of 15nm around your aircraft when tuned to 122.800. If another aircraft (with a range ring of 15nm) is 29nm away from you, you should be able to hear them.
- Adapted from Callum Strawbridge & AFV User Guide Section 4 - https://drive.google.com/file/d/1fLIp1XUnCxPYKTNdzjDo4uKq03ZklTZW/view
- 1
-
Coordination with a Procedural TowerAs an Enroute (CTR) controller, you are required to pass the following information to a procedural tower.
- Callsign (+/- Aircraft Type)
- Estimate time field
- Approach Assigned
- Arrival Altitude
- Sequence Number
Coordination between Enroute and a Procedural Tower should take place at least 15 minutes prior to the aircraft reaching the lateral airspace boundary.
Example A:
(ML-TAS): "Coordination, JST856 A320, estimates Hobart time 42z, IPLET5A arrival, 5000ft, number 1."
(HB TWR): "JST856"
Example B:
(BN-MDE): "Coordination, QLK108D DH8D, estimates Coffs time 15z, inbound 025 radial, 5500ft, number 1."
(CFS TWR): "QLK108D, VOR"After this coordination is complete the tower would then reply generally with the callsign and possibly confirm the arrival expectation (ILS, RNAV). -
CTAF, Unicom and VHF2 Monitoring
When flying through uncontrolled airspace, a pilot shall monitor UNICOM 122.8 and where other pilots would benefit, broadcast their intentions on that frequency. VATPAC also encourages the pilot to use the designated CTAF frequency at an uncontrolled airport however this does not replace the pilot's responsibilities under the VATSIM Code of Conduct.
Australia uses CTAF (Common Traffic Advisory Frequency) for radio comms at uncontrolled airfields. During an event, the Pilots is requested to tune the CTAF as stated in the flight event details. Pilots should also be aware that it is a VATSIM CoC (Code of Conduct) requirement that all pilots at uncontrolled airfields should monitor UNICOM on 122.800. It is highly recommended that pilots ensure that at least one of their "on board" COM radios (COM 2 being the most likely) is tuned to receive unicom transmissions in addition to transmitting and receiving on the published CTAF frequency.
Now for the interpretation, if it's likely that any pilots in range will benefit from a UNICOM call, that call should be made. If the pilot knows that ALL other traffic in the range is listening to their call on the CTAF, the additional UNICOM call will not benefit them. At the end of the day, if in doubt make the call on both.
The Guard frequency 121.5 is not to be used as per the code of conduct.
-
Welcome to Thursday Therapy
Thursday Therapy is a new era in VATPAC events, introducing you to a new series of routes, aircraft and experiences. With the new and improved time of 0800z-1100z based on your feedback. Because of the short distance this week we recommend a C172, SR22 or aircraft of similar size. If you want to do multiple flights, we recommend the TBM930 or King Air 350.
Be sure to join us on the VATPAC discord. To join, visit here.
Welcome back to Therapy Thursday! This week we are jumping across to Western Australia. Departing from either the Perth, Perth Jandakot or Busselton enjoy the stunning coastal WA views. Whether you want to fly via the route or break off to do VFR city orbits on arrival the choice is all yours.
Routes:
YPPH-YBLN: PH MANDU W20 BLN (0:50 Flight Time)
YPJT-YBLN: JT YMUL YBUN (1:00 Flight Time)
YBLN-YPPH: BLN W20 MANDU DCT PH (1:00 Flight Time)
YBLN-YPPH: BLN DCT MANDU DCT JT (0:55 Flight Time)ATC:
Login
Callsign
Frequency
JT_TWR Jandakot Tower 118.100 JT_GND Jandakot Ground 124.300 PH_APP Perth Approach 123.600 PH_TWR Perth Tower 127.400 PH_GND Perth Ground 121.700 PH_DEL Perth Delivery 118.550 ML-ESP_CTR Melbourne Centre 123.950 Scenery:
YPPH - Perth
MFSG - Payware (P3D/FSX)
Axon - Payware (X-Plane 11)
Rasho - Freeware (X-Plane)
YPJT - Perth Jandakot
ORBX - Payware (P3D/FSX)
'fschutzman' - Freeware (X-Plane)
YBLN - Busselton
ORBX - Freeware (P3D/FSX)
TBTX - Freeware (X-Plane)
MISC - Miscellaneous Items:
Payware - AUSv2 (FSX/P3D) -
ATC Phraseology
Below is an explanation of some common or uncommon ATC phrases that are often misunderstood. These are provided for both pilots (to help them understand what the controller means) and controllers (to improve their phraseology).
CONDITIONAL CLEARANCES (AIP GEN 3.4)
A conditional clearance is a procedure where an aircraft is instructed to do something, based on some other condition being met. The most common example is the instruction to "LINE UP BEHIND". AIP requires that the condition be stated at the beginning and then briefly reiterated at the end of the instruction. Note, the runway need only be identified where the possibility of confusion exists.
"QFA123, BEHIND THE ARRIVING A320, LINE UP AND WAIT [RUNWAY 34L] BEHIND."
Note the controller uses the word "behind" twice to promote undestanding and compliance. The pilot would readback:
"BEHIND THE ARRIVING A320, LINE UP [RUNWAY 34L] AND WAIT, QFA123."
This means the pilot must indentify the traffic referred to in the conditional clearance, wait for the arriving aircraft to pass, taxi onto the runway and await further instructions. If any doubt exists, the pilot shall hold position and confirm the clearance with ATC.
CLIMB VIA SID
CLIMB VIA SID TO (level) (AIP ENR 3.4-5.12)
This instruction means the aircraft may climb to the assigned level, while:
a) complying with published level restrictions,
b) following the lateral profile of the SID and,
c) complying with published speed restrictions and ATC issued speed restrictions.These published speed restrictions can be read from the chart applicable to the assigned SID.
It is important to note, that when instructed as part of your clearance to "CLIMB VIA SID TO 5000", you should set your autopilot to 5000ft so as to not find yourself flying through this level. The initially cleared level is an important factor in ensuring separation between arriving and departing aircraft.
Procedures for cancellation of these restrictions are too numerous to mention here. Review the applicable AIP section (GEN 3.4 5.12) for more information.
DESCEND VIA STAR TO (level)
Same as above, only going the other way.
-
Sounds good! Recommend Sydney as the arrival airport.
-
Sunday night in Australia is often pretty quite but ATC is usually around from 0800z to around 1100z. If you wait till Monday Sydney will be fully staffed from around Sydney from 0700z for our Milk Run Monday event till 1100z.
- 1
-
Pilot Phraseology
It seems there is a growing tendency to say too much on the radio at the moment. This may be coming from elsewhere in the world or from the inbuilt ATC functionality of certain simulators but it might help some pilots if we go through some general pointers here.
The idea is to say as little over the radio as you can while still getting the message across. At all times we should try to keep radio transmissions clear and concise.
Some recently observed/heard examples:
FULLY READY (No AIP reference for "FULLY", AIP GEN 3.4-5.16.6 for "READY")
You are not "FULLY READY". You are "READY". There is no graduated scale of how ready you are, you either are, or you are not. For example, don't say "ABC, fully ready at holding point KILO runway 34 left" when you can say "ABC, Ready."FULLY ESTABLISHED (No AIP reference for "FULLY", AIP GEN 3.4-5.17.8 for "ESTABLISHED")
Likewise, you are not "FULLY ESTABLISHED", you are "ESTABLISHED". No, FULLY established does not mean you are on the localiser and glideslope, it is meaningless. You are established when your instruments indicate within half of full scale deflection of the ILS/LOC or VOR radial/course. When you are on the glideslope, you are also established on the glideslope but this is unrelated to being established on the ILS/LOC.IFR CLEARANCE (AIP GEN 3.4-5.11)
In Australia, we do not "PICK UP OUR IFR TO [DEST]" nor do we "REQUEST IFR CLEARANCE" nor are we "READY TO COPY IFR", and it is not "IFR AS FILED". You either need an airways clearance or you do not, so this is what you ask for. Example requesting clearance from DEL/GND/TWR, "MELBOURNE TOWER, ABC FOR MERIMBULA, REQUEST CLEARANCE." If you are talking to a Centre controller who may be controlling multiple primary airports they might need a little bit of help finding you, you might consider telling them where you are, "MELBOURNE CENTRE, ABC AT CANBERRA TO SYDNEY, REQUEST CLEARANCE."TAXIING AT UNCONTROLLED AIRPORT (AIP GEN 3.4-5.16.4)
When departing from an uncontrolled or non-primary aerodrome, all you can expect is a squawk code and a traffic statement, if you are IFR. You will get your airways clearance later. For example:"MELBOURNE CENTRE AND TRAFFIC BENALLA, IFR BARON WITH 3POB TAXIES BENALLA FOR ALBURY, RUNWAY 08."
"ABC, MELBOURNE CENTRE, NO REPORTED IFR TRAFFIC BENALLA, SQUAWK 3245."REPORT VISUAL (AIP GEN 3.4-5.14 and AIP ENR 1.1-2.11.3)
When asked to "REPORT VISUAL", you are being asked if you can continue to fly visually to the expected point of touchdown in the current inflight conditions. You do not need to have the runway or the field in sight. Simply put "Can you fly from where you are now to the airport, without flying through any cloud?".REPORT FIELD/RUNWAY IN SIGHT (AIP GEN 3.4-5.14)
Different to reporting visual. Speaks for itself.AND... (No AIP reference for the use of the word "AND" to begin a transmission)
Adding the word "Annnnnd...." to the beginning of every transmission, just uses up valuable air time. Think about what you want to say, then press the PTT.- 1
-
3 hours ago, Kirk Christie said:
Wouldn't it be more sensible to have people disable Voice Activity mode, its not just people controlling on the network that gets annoying but also non intentional mic activations caused by other noises, and talking not meant for discord.
I find a PTT rather annoying. I know some communities have dedicated (non-PTT) and (PTT) voice rooms. Works well for vatnz I hear.
-
I've adapted the discord support forum article on setting a custom push to mute. Recently there has been a lot of people spamming discord while on frequency, by setting a push to mute as your client's push to talk it makes everyone else have a more enjoyable time.
1. Open your User Settings tab
2. Click the Keybinds tab
And now we're in business. We've got a few points to touch on as far as setting everything up goes. While you can add as many separate Keybinds as you want, you have start add them individually. Start by pressing the "Add a Keybind" button:
Push To Mute: Hold this Keybind to disable your mic activity while in Voice Activity mode. Set this as your PTT on vatSys, V-Pilot and Euroscope and now you won't ever spam the lounge chat again.
- 2
- 1
- 1
-
Weekly Tip - Double TroubleGA Tip:When flying an Australian registered aircraft in Australia and using the registration as the callsign, remove the VH- from the callsign when you log on. An example would be VH-ABC becomes ABC. When conducting flights outside of Australia, you are strongly suggested to use the full registration without the dash. An example of this would be VH-ABC will become VHABC.ATC Tip:When setting up vatSys you do not need to use the AFV standalone client, Audio for VATSIM support is built-in. To configure your audio devices, see the Voice Switching and Control System documentation on the vatSys website.
-
Welcome to Thursday Therapy
Thursday Therapy is a new era in VATPAC events, introducing you to a new series of routes, aircraft and experiences.
Be sure to join us on the VATPAC discord. To join visit here
Welcome back to Therapy Thursday! This week we are jumping across to South Australia. Departing from either the Adelaide or Broken Hill fly between another two stunning cities in Microsoft Flight Simulator. Whether you want to fly via the route or break off to do VFR city orbits on arrival the choice is all yours.
Scenery:
YPAD - Adelaide:
Payware - AUSCENE 2 (FSX/P3D)
Freeware - AusFS(FSX/P3D)
Freeware - TGD (xPlane)YBHI - Broken Hill:
Freeware - OZX (FSX/P3D)MISC - Miscellaneous Items:
Payware - AUSv2 (FSX/P3D) *Required by ORBX Airports*Routes:
YBHI - YPAD: BHI DCT PRICE V395 BLACK DCT AD
YPAD - YBHI: AD W325 BHI
-
Currently the training department can’t use vatSys off the main network given we can’t connect to sweatbox. I will echo was Greg said, there are plans afoot (formal or informal) for this very thing. Things will always take time so at the moment your best bet is to just spend some time observing an event while reading the tutorial docs to get your head around everything. Don’t worry it will take many hours to fully understand it but once you get the hang of it you won’t even think about turning back.
-
Best bet is to please send feedback to [email protected] detailing your connection troubles with vatSys and Sweatbox. Maybe if enough people send feedback, they will change their response.
-
This weeks tip will show the basic function of the Flight Strip within vatSys. While we are only listing 6 of the boxes there are infact 22. Please go to vatSys Documentation - http://virtualairtrafficsystem.com/docs/strips/ to read the full tutorial.
Area 1:
Aircraft Direction Indicator. Either a Diamond or Triangle symbol. Triangle points in the direction of flight. Filled when strip is selected
What Actions can be taken?
LEFT CLICK
to select / deselect track.MIDDLE CLICK
to hide strip.RIGHT CLICK
to cock strip.Area 2:
Controlling Sector Abbreviation
Area 3:
FDR State Abbreviation
If PREA,
LEFT CLICK
to activate FDR.Area 4:
Callsign,
LEFT CLICK
to open Callsign menu.MIDDLE CLICK
to extend strip.Area 5:
Assigned SSR Code,
LEFT CLICK
to open SSR menu.Area 6:
Aircraft Type
- 1
IT Department
in December 2020
Posted
A lot has been happening in the IT department behind the scenes with a new pathway forward being reached. An announcement at the start of new year is expected to come from the department that establishes a new direction for the department.
Department restructure
With the restructure of VATPAC, the IT department has been looking inward to how it can improve efficiency and capabilities. Two new positions are created within the department, Development Manager and Systems & Support Manager. The latter of the two has already been filled by Sam Wilson and we are looking forward to seeing the capabilities that he will be able to bring to the department.
We are calling for expressions of interest for the Development Manager role. If you are interested, please email [email protected] with a brief description of skills, experience and why you suit the position.
We are also looking for IT developers, if you are interested please send an expression of interest to [email protected].
Move to AWS
A large number of the VATPAC services have been transferred to AWS with only a few services remaining. The remaining services are planned to be transferred over the holiday period.
VATPAC Core v2
We have been looking into upgrades to our web services for VATPAC Core v2, expecting to use Amazon’s Web Services (AWS). Core v2 will be the backend of VATPAC’s services, and it will be the one place for all management and permissions. By using AWS, we are able to have:
- Lower management costs, as we are paying by usage rather than a fixed fee
- Greater security and privacy, with Amazon’s own dedicated issues management team and superior storage of confidential data by AWS
- Serverless Architecture, meaning Amazon finds the best available server to serve the requested content
- Greater efficiency, with faster response times from AWS servers and negligible downtime
- Easier management, as AWS services are all managed by one simple control panel, as well as the ability to dynamically change server requirements.
At the moment, we are looking to move VATPAC Core onto AWS services which will allow for a trial of AWS. This also removes some workload off the Vultr server, and may allow for a downgrade in Vultr to save costs. VATPAC Core v2 will also allow for better interactivity with the community and better extensibility for third parties and API access.
Pilot Assist and vatSys
We are currently developing the new Pilot Assist and ensuring Vatpac's IT infrastructure will support the new vatSys Client!
Unfortunately due the voluntary nature of VATPAC staff, progress on pilot assist has significantly slowed. We are looking to further push the project capabilities with the beginning of the year.
We are also working with the members of the vatSys team to ensure it is fully supported by the IT Department and Operations Department for full release.
VATPAX
VATPAX is under redevelopment! We are looking for more developers to dedicate time on this project. If you are interested please send an expression of interest email to Tom Grozev on [email protected].
Cheers,
--
Tom Grozev
Director of Technology
VATSIM Australia Pacific