Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added details about AYPM Class F and ATZ operations #424

Open
wants to merge 35 commits into
base: main
Choose a base branch
from

Conversation

m-9c
Copy link
Contributor

@m-9c m-9c commented Dec 26, 2024

Summary

Added details about AYPM Class F and ATZ operations, using the PNG AIP as a reference.

Changes:

  • Aded detail of Class F and ATZ to Papua New Guinea index.md
  • Modified all Class F PNG aerodromes to include descriptions of airspace, diagrams and link to overview.
  • Modified AYPY TCU with link to Class F description.

Fixes:

  • Standardises display of Pacific position lists

@m-9c
Copy link
Contributor Author

m-9c commented Dec 26, 2024

Hello,

Again, I hope this is useful and welcome.

I've tried to document enough to provide people with enough accurate information to jump off into the PNG AIP themselves and build there knowledge from there. :)

@m-9c m-9c marked this pull request as ready for review December 26, 2024 00:53
@mattkelly4
Copy link
Collaborator

@m-9c looks great, thanks for putting this together! Obviously Class F is a foreign concept for most of us, how does it work with an ADC being responsible for uncontrolled airspace? I take it they issue takeoff/landing clearances but provide no airspace services? Or do they manage the airspace within a certain radius of the aerodrome and provide a control service to those pilots? How would this work with an aircraft conducting circuits, for example?

Copy link
Collaborator

@alphadelta332 alphadelta332 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice work @m-9c ! I'm happy with everything, I'll just hold off on approving for now though, to look at potentially fleshing out the Class F ATZ Operations as per @mattkelly4 's comment. Cheers

@mattkelly4 mattkelly4 added the DO NOT MERGE This PR is not ready to be merged. Do not merge until approval from the Publications Manager. label Dec 31, 2024
@m-9c
Copy link
Contributor Author

m-9c commented Dec 31, 2024

No problem; thanks for the feedback. I’ll flesh out the ATZ section when I’ve returned from overseas. :)

@m-9c
Copy link
Contributor Author

m-9c commented Jan 20, 2025

Hey @alphadelta332 / @mattkelly4 , I'm back and working on this now. I wanted to clarify: Does AYGA, AYMD, AYMH, AYTK require a procedural endorsement?

I was assuming it does, as It's a non-surveillance position with airspace up to A200, but it's not listed as requiring an endorsement on the position list (https://vatpac.org/controllers/position).

Add Circuit Direction note.
Add Circuit Direction Note.
@mattkelly4
Copy link
Collaborator

Hey @alphadelta332 / @mattkelly4 , I'm back and working on this now. I wanted to clarify: Does AYGA, AYMD, AYMH, AYTK require a procedural endorsement?

I was assuming it does, as It's a non-surveillance position with airspace up to A200, but it's not listed as requiring an endorsement on the position list (https://vatpac.org/controllers/position).

It likely does in that case. We've essentially required the procedural tower endorsement for any aerodrome position which provides an approach service (as per ERSA). Given that this is uncontrolled airspace but a traffic information service is provided, it likely exceeds the skills of an S2.

@alphadelta332 what are your thoughts?

@alphadelta332
Copy link
Collaborator

alphadelta332 commented Jan 20, 2025

@alphadelta332 what are your thoughts?

I would say given that there are no procedural separation standards that need to be applied, the complexity is somewhat reduced.

But I also think on review, that even with the SOPs, no one (Procedural Endorsement or not) really would have suitable training to operate these towers. Given they don't actually separate and just provide a traffic service, we would probably be better off leaving them out.

We made the same decision for SFIS/AFIS towers such as Ballina and Port Hedland, although the difference being that these PNG towers provide runway and SMC sep standards. So maybe that's good enough to include them? What do you reckon @mattkelly4 ?

Expand ATZ operations
@m-9c
Copy link
Contributor Author

m-9c commented Jan 20, 2025

Also have now updated the index page with as much information as I could gather for ATZ operations. I hope it makes sense?

@mattkelly4 @alphadelta332

@mattkelly4 mattkelly4 added the notify Send notification to Discord on merge label Jan 21, 2025
@mattkelly4
Copy link
Collaborator

Also have now updated the index page with as much information as I could gather for ATZ operations. I hope it makes sense?

@mattkelly4 @alphadelta332

Yep that looks great, thanks. We'll take some time to wrap our heads around it and go from there

docs/pacific/Papua-New-Guinea/Madang.md Outdated Show resolved Hide resolved
includes/abbreviations.md Outdated Show resolved Hide resolved
@m-9c m-9c requested a review from a team as a code owner February 1, 2025 04:08
@mattkelly4
Copy link
Collaborator

Opened internal discussion, but leaning towards clipping ADC's vertical limit to a couple of thousand feet and introducing a no change boundary requirement so that ADC can look at an inbound aircraft's FDR to determine the relevance of traffic information with outbound/other inbound aircraft. If an aircraft wants to change their flightpath, ENR advises ADC if inside the no change boundary.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
DO NOT MERGE This PR is not ready to be merged. Do not merge until approval from the Publications Manager. notify Send notification to Discord on merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants