[Thanks to the VATPAC board and helpers]

Thanks for the kind words, Sean.

We've shared your feedback with the rest of the volunteers.

[NOTAM: AIRAC 2210]

2210b is now effective.

• Removes unused boundaries and volumes.
• Renames TMA_CAP volumes to be consistent across all sectors.
• Fixes issues with missing volumes in AlertParameters.
• Modifies the Inhibition Areas at YSSY and adds YBBN.

[NOTAM: AIRAC 2208]

See the below points for clarification on recent airspace changes.

• A Class D Tower that does NOT provide a procedural approach service, does NOT require a procedural tower endorsement.
• A Class D Tower (Procedural Tower) that DOES provide a procedural approach service, requires a procedural tower endorsement.
• Extending approach/departure (TCU) services:
  • A controller may provide control services as HB_APP from LT_APP, and vice versa, by assuming the sectors and activating the applicable frequency in the VSCS.
  • A controller may provide control services as MK_APP from RK_APP, and vice versa, by assuming the sectors and activating the applicable frequency in the VSCS.
  • If in either of the above scenarios, the other TCU position is filled by another controller, the controller providing an extended services shall relinquish the applicable airspace to the new controller, in the same way as Enroute controllers would do.
  • For further clarification, CG_APP is included in the default jurisdiction of Brisbane Approach (is a sub-sector of BN_APP) and therefore not considered as providing extended coverage. Refer to the NOTAM regarding opening of non-standard/child positions.

[Suggestion to implement Position Briefings]

Pheonix. A few comments from me.

• GCAP will give divisions more power to remove incompetent controllers from our controller roster. We will still not be able to revoke ratings.
• The division has limited capacity to take disciplinary action on members outside of local community platforms. With incidents that occur online, as other have already said, best to gather as much evidence as possible and send it to the VATSIM Supervisor or Conflict Resolution department as these are the people that can effect network bans on a members account. Not VATPAC.
• I would say that that statement about policies is partially correct. VATPAC is not interested in over-complicating things, and creating a web of policies and rules. The ultimate goal is to have a small number of policies, that cover a wide range of subjects to make things simpler for the membership (hence the draft ATS Policy).
• In regards to your last point, see my first point. VATPAC has very limited power in what it can do with regards to 'moderating of their controllers'. Take that one up with VATSIM global.
• I disgaree with the notion that controller standards have dropped. I would say it's the opposite and that standards have gotten better, especially in the last 6 months. However, that does not stop bad-eggs from getting through the system and causing issues online. We are aware of those instances, but see my previous comment about limited ability to "moderate".
• Your contribution to policy and procedure writing would be appreciated if it's something you are genuiniely interested in, as there a number of ongoing projects with regard to policies and controller SOPs. Please reach out to myself or @Sam K - 1445607.
• Lastly, as with most conflict that occurs online, unless there is some solid evidence, VATSIM ( and as previously discussed, VATPAC) cannot do much, since everything is "he said/she said".

[VATPAC Financial Update]

I am pleased to inform the community that we have successfully registered and established VATSIM Australia Pacific as an unincorporated association in Australia. Operating not-for-profit, this allows us to tap into financial benefits for community organisation such as ours.

The process for this started many years ago when David Z and his Board introduced the Constitution. This has evolved over the last few years and gave us the bones/structure required to officially establish the organisation. Given that we don’t “own” the rights to the name VATSIM, we couldn’t register the association using those words. The organisation was registered as the Online Aviation Organisation Australia, trading as VATSIM Australia Pacific (VATPAC as we know it).

VATPAC has always been funded by either the Board of Directors and also through minor business sponsorships (NetSpace and Delion in the past). Unfortunately, the finances have not always been shared equally amongst Board members with the highest financial burden often falling to the Director of Technology.

VATPAC now has as a registered not-for-profit community bank account with Bendigo Bank, which is connected to Open Collective, allowing us to transparently show the community the money coming in, and going out. This also allows us contribute equally and reimburse any board members with costs that they incur. It also allows us to transparently collect donations from the community to contribute to operating costs.

Thanks to our newly registered organisation, we have also been able to tap into a number of significantly discounted or free products, which allow us to continue to run our organisation efficiently. This includes services like website hosting and email/document storage. This will overall reduce the total cost to the Board of Directors by about 70%.

This doesn’t change how the organisation operates fundamentally, however it enables us to run more economically and hopefully provide a better service to our local community. The VATPAC constitution cover pages have been amended to reflect the correct organisation names moving forward and you may see the new organisation name referenced in other documentation such as board meeting minutes.

If you have any questions or suggestion around these changes, feel free to reach out.

[Adjusting Waypoint ETA B737]

On 5/5/2022 at 9:21 AM, Christopher S - 1119435 said:

HI Zach,

Yep....simple enough for my simple mind. I guess I was looking for a way to modify the scheduled time at waypoint by modifying the data in the FMC. Typical me, trying to over complicate issues. Thanks for the response. 

Glad it makes sense.

Some aircraft do have the capability of entering a desired "time at waypoint", but not all of them so that's why it's just easier to slow down or speed up as required. It's what we have to do IRL in the aircraft that I fly.

[Adjusting Waypoint ETA B737]

Hi Christopher.

It's hard not to sound condescending when I explain this, but it's fairly simple.

Check your FMS/MCDU to see what time you are currently estimating the waypoint. If it's early, slow down. If it's late, speed up. You might find that you can't slow down enough to get the required ETA, or you can't speed up enough to get the required ETA. In this case, advise ATC and they will give you some "delaying action" which will be vectors.

In summary, speed up or slow down to the achieve desired ETA.

Zach

[VATPAC Board Staffing and Structure Changes]

Hi all,

There have been a few minor changes made to the VATPAC structure (again) to coincide with changes to the Airspace and ATC Standards department, and upcoming policy changes.

Firstly, thanks to Steven C who unfortunately had to take a step back late last year due to some personal circumstances. Another thanks to Clem W who stepped up and managed the Airspace portfolio in the interim.

A decision was made by the board to merge the Airspace and ATC Standards department to one department called "Air Traffic Services". This means that Sam K now take's on this role of managing both ATC Training, Standards, AIS and Documentation. Since all subjects are closely related, we felt this decision makes sense. Sam is well supported by a team of passionate volunteer leaders in Matt K (ATC Training), James H (ATC Standards) and Peter S (Aeronautical Information Services). No doubt, Sam will seek further assistance from the community for a Publications lead moving forward. I'd also like to reach out to anyone that would be interested in becoming involved in distribution of AIRAC Cycles and other AIS, under the guidance of Peter. 

Clem W remains on the VATPAC board as the Deputy Division Director and will assist with the division leadership. This is an interim appointment for 6 months.

For those interested, the VATPAC structure currently looks like this...

If you have any concerns or questions, of course, don't hesitate to reach out.

[VATPAC Board Changes for 2022]

Hi everyone.

A number of changes have occured at the Board level that will be in place for 2022.

Last week I accepted Greg's resignation from his Director of ATC Training & Standards role. Greg has made an outstanding contribution over the last 12-18 months and I hope that he will be able to enjoy the hobby once again. I'm pleased to confirm that Sam Keast will take over responsibility for the Director role. He will continue working with Matt Kelly and others in the training department throughout the next 6 months (at least). Sam was the alternative applicant last year for the role and has demonstrated his commitment to the community throughout the last 12 months.

The appointment committee for the Director of Technology agreed that Will Smart was the outstanding applicant for the role, and I am happy to report he has accepted the offer. Will brings a wealth of knowledge and leadership experience to the team after extensive time volunteering within the ATC Training Department (including the development and rollout of the TMS).

Steve Cullen has asked to take a LoA from the board temporarily due to some personal matters. In the interm, Clem Wu (a long standing member of the Airspace/Documentation team will be acting as Director of Airspace & Publications).

Blair has officially been permanently appointed by a committee, to his current role of Director of Membership.

I am pleased to announce that Sam Wilson will join Ryan McDonald as non-executive directors for 2022. I would like to thank Shannon for his involvement of the last 12 months.

I wish everyone a very Merry Christmas, however you choose to celebrate.

Zach
 

[VATPAC Seeks new Directors]

Hi everyone,

I'm sad to announce that Tom Grozev, who has looked after the Technology portfolio for many years, will be stepping down from his role in the new year. Tom has advised me that his new employment will mean he no longer has the time to commit to VATPAC moving forward. I'd like to thank Tom for putting his time into VATPAC over the last few years. He will stick around in a development capacity and support our new Director, when they are brought on board.

I am now accepting applications for the Director of Technology role. The role requirements can be viewed on the attached document and an application (in a format of your choice) should be submitted to myself via email ([email protected]).

It is also that time of the year again where, as per our constitution, VATPAC opens expressions of interest to senior, long-standing members of our community to join the Board in an advisory capacity as a non-executive Director. The role requirements can also be viewed on the attached document and an application (in a format of your choice) should be submitted to myself via email ([email protected]).

The closing date for all of the above positions is Friday 17th of December, unless a succesful applicant is appointed earlier. If you are considering throwing your hat into the ring, I'd advise you to do so sooner rather than later.

Position Description Non Executive

Position Description Director Technology

 

[16OCT | Various Controllers]

Quote

Feedback for all the ATC for the event today, thanks you all for my third flight I guess, in Australia, the service was professional, will try to flight more often in Australia (it's 3am in France lol)! Keep the good work up!

 

[25SEP | Various Controllers]

This feedback was provided to me via one of our local supervisors.

Quote

I have now finished Bathurst to Sydney on the YSSY TMA Turnaround event and it was just fantastic. I would really appreciate it if you could forward my thoughts to all including the ATC guys. I have three real world flights coming up in the next 2 weeks, the first will be Bathurst to Sydney, then Bathurst to Bankstown, all to finalise my IFR ticket. Tonight with the ATC was incredibly helpful. The ATC crew and other pilots really know their stuff.

 

[Q3 Minutes and Report]

Hi all,

The Q3 meeting minutes are available for download on the VATPAC website:

https://vatpac.org/about/minutes-and-reports/

I have managed to recover and archive a number of minutes and reports from late 2011 onwards. It's great to see these reports available for you all again and shows the depth and history within our organisation.

[TMA Controller - Alex MacDonald]

Congratulations to Alex who received his S3 rating yesterday

[NOTAM: Positions Reserved For Friday Night Ops Downunder]

1 INTRODUCTION
The following positions are reserved under section 4.1 of the VATPAC Controller Positions and Ratings Policy. This NOTAM is the reservation of the positions noted in 2 RESERVED POSITIONS for the purpose of FNO Downunder.

2 RESERVED POSITIONS
The following positions are reserved from 2300z to 0300z on the 15th of October 2021. 
SY_DEL
SY_GND
SY_TWR
SY_APP
SY_DEP
SY-D_APP
ML_DEL
ML_GND
ML_TWR
ML_APP
ML_DEP
AD_DEL
AD_GND
AD_TWR
AD_APP
AD_DEP
ML-BIK_CTR
ML-ELW_CTR
ML-TBD_CTR
ML-WOL_CTR
ML-SNO_CTR
ML-BLA_CTR
ML-MUN_CTR

3 AUTHORITY
This NOTAM Is under the authority of the following:
Joshua Micallef - Events Director (events[at]vatpac.org)

4 CONTACT
The nominated Event Coordinator(s) for this event are:
Tyler Hindle
Paris Ioannidis
Event Coordinators will be available for contact on the VATPAC Discord, using the @eventcoordinator role. They can also be contacted via PM over the VATSIM network. They may also be logged onto the network as VATPAC35.

5 ROSTER
The roster for FNO Downunder can be viewed here.
If you have any questions about the roster, or with to have it amended, please contact roster[at]vatpac.org.
If you find yourself free during the event, and wish to offer your ATC services, please contact one of the dedicated event coordinators

6 CANCELLATION
This NOTAM will self-cancel at 0300z on the 16th of October 2021.

[TMA Rating | Stace Heasley]

Well done Stace, who yesterday, achieved a VATSIM S3 rating

[Tower Controller - Robbie van Leeuwan]

Congratulations to Robbie who passed his Tower Rating this morning.

[Pacific Oceanic Letter of Agreement]

Hi All,

I'm pleased to advise that VATUSA, VATNZ and VATPAC have come together to form a new Pacific Oceanic Agreement.

More information about this can be found here:

Pacific Oceanic LoA - VATSIM Australia Pacific - VATPAC

There are a few alterations from the existing partnership, but essentially the privileges and limitations are the same. Of note, a new requirement to control 1 hour in the previous 3 months to remain active will apply. However, until such time that VATPAC has a system in place to track this, we will waive this requirement.

A local instructions document is currently being prepared by all parties. For now, some information can be found here: VATNZ, Oakland ARTCC.

I'd like to extend thanks to Andrew from VATNZ as well as Manuel, Ryan and Daniel from VATUSA and Oakland ARTCC for coming together to forge this agreement.

This is a great step forward for all of us, together.

[21SEP | Various]

Quote

Hi Team

Just a quick note to say what a great flight I had from MRM on the 20 Sep 21. There was not one individual that I can pinpoint as the experience dealing with all the controllers I got passed to was fantastic.

ALL controllers that I had the pleasure to deal with on the flight from Sydney to Melbourne were very skilled and well spoken.

For the first time I had a perfect flight, with not one incident or mistake. Well done team this is a testament to the great training provided and the standards that are expected of controllers. It also shows the level of dedication and commitment we have to provide a great service for the Vatsim community. 

Congratulations on a very successful event and keep up the great work

Mario

 

 

[Major Changes for AIRAC 2110]

Announcement Published 22 SEP 2021

Hi everyone,

I would like to announce a few major changes for that will be implemented for AIRAC 2110.

• The VATPAC Board voted in favour of removing support for VRC, inline with community/membership demand (polling indicated approximately, only 10% of users are using this client). Resources will be focused on Euroscope (TAAATSMod Euroscope 3.1d) and vatSys.
  This means VRC will no longer receive AIRAC cycle updates and any existing files will not be compatible with the new changes outlined below.
   
• The VATPAC board also voted in favour of removing the Melbourne and Brisbane upper (FSS) positions. The board agreed that the position no longer met the requirement that they were initially created for and that controllers should be encouraged to provide a quality top-down service as per our existing extended coverage policy, rather than a larger quantity (and lower quality) service over a significant geographical area.
   
• Finally, a number of changes to primary (parent) and secondary (child) sectors/frequencies have occurred to re-align most of our sectors with the IRL positions and to also better support the auto-activation of non-standard sectors. The major sector boundary changes occur in the central and west of Australia. Further minor changes between ML-SY-BN.
  
  
  
  
  
  Detailed changes:
  • ORE becomes OLW, freq 134.0
    • Layout changes to main sector and sub-sectors as per AIP Sup S21-H91.
  • ESP primary becomes PIY, freq 133.9.
    • Layout changes as per IRL and draft map above. GVE/DAL merged as GVE only.
  • ASP primary, freq 128.85.
    • Layout and sub sectors as per IRL and draft map above.
    • Include WRA sector from old BKE primary.
  • BKE primary.
    • Removed.
  • TBD primary.
    • Layout and sub sectors as per IRL and draft map above.
    • Include BKE sector from old BKE primary.
  • SNO primary becomes ELW, freq 123.75.
    • HUM renamed BLA as per IRL upper sector, freq 132.20
    • Minor boundary changes to BLA, ELW and SNO.
    • BLA (and by association, the parent sector ELW) continues to be responsible for the CB TCU when the dedicated CB controllers are offline.
  • MDE primary becomes ARL, freq 130.9.
    • OCN sub-sector freq becomes 128.6 as per IRL.
  • DOS primary becomes INL, freq 134.2
    • GRN renamed INL as per IRL upper sector.
    • Minor boundary changes to INL and DOS.
    • SDY freq change to 134.3
  • TBP primary becomes KEN, freq 120.15
  • WOL primary becomes BIK, freq 129.8.
    • Minor boundary changes to BIK and WOL.
  • BN-TSN_FSS primary VHF alias becomes 124.65
    • HWE VHF alias becomes 124.95
    • FLD VHF alias becomes 132.85
    • COL VHF alias becomes 133.15
      • Inclusion of AGGG and ANAU under COL as per existing oceanic documentation and IRL services provided by AsA.
      • Note that the above positions cannot be individually logged in to and are assumed by the COL subsector only.

[NOTAM: AIRAC 2109]

In addition to the above AIRAC changes, a number of changes have been made to the VATPAC Audio For VATSIM databses.

• Fixed transceiver and position heirachy on a number of positions.
• Improved CTR -> TCU hierachy.
• Fix BN-HWE_FSS defininition.
• Improved Tasman Oceania HF transceivers.
• Improved India Oceanic HF transceivers (including new Casey Station HF station).
• Correct a number of transceivers that were assigned to incorrect positions.

 

[NOTAM: Activation of Non-Standard Positions]

1. INTRODUCTION
To assist in providing quality Air Traffic Services (ATS) throughout VATPAC airspace, the board is introducing several changes to our VATPAC ATS Policy. Changes will reflect ongoing improvement and alignment with the new VATSIM Global ATC Administration Policy.

Until our updated VATPAC ATS Policy is released, in the interim to help further online experience of realism on the network, positions listed in the "List of approved non-standard positions" may be opened subject to specific requirements outlined below.

2. OPENING OF APPROVED NON-STANDARD POSITIONS
Activation of a Non-Standard Position by a Controller

A non-standard (child) position may be activated at any time, by an appropriately rated controller and the following additional requirements:

a)    An agreement must be obtained between the controller wishing to open the non-standard (child) position and the controller currently operating the standard (parent) position, under which the non-standard position is to be opened; and

b)    All controllers affected by the activation of the non-standard (child) position must review:

1)    the local instructions applicable to the non-standard position being activated, noting the designated responsible airspace; and
2)    the frequency and login identifier of the non-standard position; and
3)    any additional coordination requirements that arise from the use of the non-standard position; and
4)    any other questions or concerns from either controller.

Affected controllers are encouraged (but not required) to keep a record of their agreement.

Any breaches of this NOTAM or any issues that arise in relation to the opening of a non-standard position should be reported to VATPAC staff at the earliest convenience.

Activation of Non-Standard Positions by Staff and Senior Controllers

Non-standard positions may also be activated in certain circumstances outlined below, by an authorised person. An authorised person is either a VATPAC staff member or a local VATPAC controller holding a Senior Controller (C3) rating.

An authorised person may waive requirement a) (obtaining agreement of the parent controller), should a situation arise where activation of a non-standard position is deemed crucial to the delivery of a quality ATC service, and the existing parent controller does not agree to the opening of this position in the first instance.

An authorised person must not approve themselves to open a non-standard position under the circumstances outlined above, unless exceptional circumstances apply.

3. LIST OF APPROVED NON-STANDARD POSITIONS
The follow is a list of Login Identifiers of approved non-standard (child) positions.

Melbourne Centre Positions: ML-SNO_CTR ML-BLA_CTR ML-WOL_CTR ML-MUN_CTR ML-AUG_CTR ML-FOR_CTR ML-ESP_CTR ML-GVE_CTR ML-MEK_CTR  Brisbane Centre Positions: BN-MLD_CTR BN-OCN_CTR BN-DOS_CTR BN-KPL_CTR BN-SWY_CTR BN-KIY_CTR  Sydney TCU Positions: SY_DEP SY-S_DEP SY-D_APP SY-DE_APP SY-S_APP  Sydney ADC/SMC Positions: SY-E_GND (121.70) SY-E_TWR (124.70)

Melbourne TCU Positions: ML_DEP ML-S_DEP  Brisbane TCU Positions: BN_DEP BN-S_APP BN-S_DEP  Brisbane ADC/SMC Positions: BN-W_TWR BN-S_GND BN-N_GND  Adelaide TCU Position: AD_DEP  Cairns TCU Position: CS_DEP  Canberra TCU Position: CB-W_APP  Perth TCU Position: PH_DEP  Perth SMC Position: PH-E_GND

4. AUTHORITY
Division Director, [email protected]

5. CANCELLATION
This NOTAM will self-cancel when incorporated into official ATS policy, unless otherwise noted.

 

[VATPAC Staff Conduct Policy]

Hi everyone,

This morning I have published the VATPAC Staff Policy, which is available for all members to see.

https://drive.google.com/file/d/1PJGQksBP9e5NGmGsPUpQ7KEEaG0xtXT_/view?usp=sharing

This new policy finally puts to bed a very long and out-of-date forum post made in 2012 by Jackson, a previous Division Director.

The policy has been agreed on by all board members, but for the sake of integrity and respect, if you see something in this new policy that doesn't sit well with you, please contact me directly with your concerns.

The policy is effective today. It should not change how you do anything day-to-day, but set in stone things that most (hopefully all) of us are already doing.

Thanks for your continued hard work as volunteers!

Regards,

Zach

[2021 Q2 Board Meeting Minutes]

Hi all,

The Q2 board meeting minutes are now available to download.

The reason for the delay in publishing, was due to updating the document to match the new styling and getting caught up in other changes going on.

The next meeting is scheduled for on (or around) Saturday 2 October 2021.

Thanks.

Z

[Oceanic Partnership - US to leave]

Follow up.

The VATSIM BoG is currently investigating this proposal.

Our understanding is that the pacific oceanic partnership agreement remains in force, until such time that we hear information contrary from the BoG.

More information about the partnership can be found here:

https://pacificoceanic.vatsim.net