Skip to content

Comments

Tamworth SOPs Update#679

Open
AtAwesome wants to merge 24 commits intovatpac-technology:mainfrom
AtAwesome:patch-1
Open

Tamworth SOPs Update#679
AtAwesome wants to merge 24 commits intovatpac-technology:mainfrom
AtAwesome:patch-1

Conversation

@AtAwesome
Copy link

@AtAwesome AtAwesome commented Jan 21, 2026

Summary

Changes to Tamworth covering standard taxi procedures, departure procedures and ATIS formatting. With phraseology examples for taxi, departure and inbound clearances

Fixes

Fixes:

  • Amended circuit altitude from A025 to A023

Additions:

  • Phraseology examples for taxi, departure and inbound clearance (both GST & GWT and CTA)

Removals:

  • Removed specified RWY controller info from ATIS runway mode formatting

*Note: There are images pending creation for the standard taxi routes

Added standard taxi procedures and updated departure procedures and ATIS formatting.
@AtAwesome AtAwesome requested a review from a team as a code owner January 21, 2026 13:39
Added standard taxi procedures and clarified VFR departure instructions for both northern and southern runways.
@m-9c m-9c marked this pull request as draft January 21, 2026 22:27
@m-9c
Copy link
Contributor

m-9c commented Jan 21, 2026

Will start work on the diagrams.

Comment on lines 66 to 71
!!! phraseology
**83C**: "Tamworth Ground, Cherokee 83C, departure details"
**TW SMC**: "83C"
**83C**: "83C, at IFTT, received A, for a GST departure, request taxi"
**TW SMC**: "83C, Tamworth Ground, taxi to holding point J Runway 12R"
**83C**: "Taxi to holding point J Runway 12R, 83C"
Copy link
Collaborator

Choose a reason for hiding this comment

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

@AtAwesome is this a flight school-specific procedure, or does every aircraft prefix their taxi call with the 'departure details' call? Just wondering if we could standardise this with the other aerodromes to reduce complexity.

Copy link
Author

Choose a reason for hiding this comment

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

@mattk04 All aircraft using the southern runway are expected* to call SMC with "Departure Details" prior to requesting taxi (with intended departure procedure) otherwise the SMC guys here get pissy

Copy link
Collaborator

Choose a reason for hiding this comment

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

I reckon we'll standardise and remove the initial cold call

Copy link
Author

Choose a reason for hiding this comment

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

Sounds good 😊

Comment on lines 76 to 81
!!! phraseology
**ZFN**: "Tamworth Ground, Cherokee ZFN, departure details"
**TW SMC**: "ZFN"
**ZFN**: "Tamworth Ground, Cherokee ZFN, at IFTT, received A, request airways and taxi clearance to YSTW via MAL"
**TW SMC**: "ZFN, Tamworth Ground, taxi to holding point B Runway 12L, cross runways 18 and 24"
**ZFN**: "Taxi to holding point B Runway 12L, cross runways 18 and 24, ZFN"
Copy link
Collaborator

Choose a reason for hiding this comment

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

@AtAwesome I assume this example is targeting clearance through the TW ADC owned Class C, and not into the overlying ENR airspace? The example doesn't issue clearance, would there be coordination requirements for this?

Copy link
Author

Choose a reason for hiding this comment

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

@mattk04 Missed this, should be fixed now 😄

@m-9c
Copy link
Contributor

m-9c commented Jan 28, 2026

Have created the taxi routes as per the document provided by @AtAwesome . I couldn't find a reference in the ERSA though?

m-9c added a commit to vatpac-technology/image-source-files that referenced this pull request Feb 1, 2026
@m-9c m-9c marked this pull request as ready for review February 2, 2026 22:50
@mattk04 mattk04 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. labels Feb 2, 2026
VFR Arrivals from the 160 radial through to the 295 radial should route via **DUA**. Clearance required prior to DUA. Aircraft should report 5NM for circuit entry instructions.
### Departures
#### Northern Runway Departures
VFR aircraft not departing between the 160 radial through to the 295 radial shall make a standard CTA departure from the northern runway (12L/30R).
Copy link
Collaborator

Choose a reason for hiding this comment

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

@AtAwesome To clarify, a CTA departure in this context means entering the overlying Class C? Or just a departure into the Class D/C as opposed to exiting the CTR directly into Class G?

mattk04 pushed a commit to vatpac-technology/image-source-files that referenced this pull request Feb 18, 2026
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