Skip to content

Tindal SOP Updates#687

Open
m-9c wants to merge 32 commits intovatpac-technology:mainfrom
m-9c:403-tin
Open

Tindal SOP Updates#687
m-9c wants to merge 32 commits intovatpac-technology:mainfrom
m-9c:403-tin

Conversation

@m-9c
Copy link
Copy Markdown
Contributor

@m-9c m-9c commented Jan 22, 2026

Summary

This update expands the Tindal SOPs to include details about military operations and local procedures. It includes details relevant to ADC, TCU and Enroute controllers for facilitating aircraft movements at YPTN.

Changes

Changes:

  • TN ADC

    • Details local SUA coded clearances.
    • Added guidance and phraseology examples of how to handle aircraft departing via military gates.
    • Added Initial and Pitch details
    • Added details about the Tindal SUA
    • Added details about Victoria Highway Corridor and Katherine Helicopter Corridor
    • Added requirement for ACD to coordinate with TCU prior to clearing an aircraft intending to operate in unactivated SUA.
    • Added details about Choppers East
    • Added Manouvring Area Diagram
    • Added recommended taxi route details
  • TN TCU

    • Details local coded clearances
    • Added guidance and phraseology examples of how to handle aircraft departing via military gates.
    • Added Initial and Pitch details
    • Adds details about the Tindal SUA
    • Adds requirement for ACD to coordinate with TCU prior to clearing an aircraft intending to operate in unactivated SUA.
    • Adds requirement for TCU to coordinate with enroute prior to activation of SUA.
  • TRT

    • Adds details about Special Use Airspace associated with YPTN military operations.
    • Adds details about affected civilian operations passing through activated SUAs.
    • Adds requirement for TCU to coordinate with enroute prior to activation of SUA.

@m-9c
Copy link
Copy Markdown
Contributor Author

m-9c commented Jan 22, 2026

Pending changes following comments on #403

@m-9c m-9c added the hold Issue on hold until further notice label Jan 28, 2026
@m-9c m-9c added notify Send notification to Discord on merge DO NOT MERGE This PR is not ready to be merged. Do not merge until approval from the Publications Manager. ais Awaiting corresponding AIS changes and removed hold Issue on hold until further notice labels Apr 12, 2026
@m-9c m-9c changed the title Tindal Update Tindal SOP Update Apr 12, 2026
@m-9c m-9c changed the title Tindal SOP Update Tindal SOP Updates Apr 12, 2026
@m-9c m-9c marked this pull request as ready for review April 15, 2026 01:33
@m-9c m-9c requested a review from a team as a code owner April 15, 2026 01:33
ST6-Bravo
ST6-Bravo previously approved these changes Apr 15, 2026
mattk04
mattk04 previously approved these changes Apr 15, 2026
@mattk04 mattk04 requested a review from ST6-Bravo April 15, 2026 11:51
@m-9c m-9c requested a review from mattk04 April 16, 2026 00:05
ST6-Bravo
ST6-Bravo previously approved these changes Apr 16, 2026
@m-9c m-9c removed the DO NOT MERGE This PR is not ready to be merged. Do not merge until approval from the Publications Manager. label Apr 16, 2026
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Nothing wrong with having this diagram I guess, but I think in my mind it would be better to keep the diagram for when the ADC/SMC split is not "expected", ie, ADC owns only the runways, and SMC owns only everything else. I'd rather not set the precedent that we need a diagram like this everywhere. Thoughts @mattk04 ?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Yeah, agree that the diagram should only be when it's not as normal; I added this to try and emphasise that ground has no control over the central part of the aerodrome, where the helis are.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Agree with both, I think this diagram is good to highlight the manoeuvring area

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ais Awaiting corresponding AIS changes notify Send notification to Discord on merge

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants