-
Notifications
You must be signed in to change notification settings - Fork 13
Initial HTMA #184
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
base: next
Are you sure you want to change the base?
Initial HTMA #184
Changes from all commits
1b5b325
035cc47
f7ca500
88bef60
693807f
4a26570
056fe87
cdab181
a85aa0a
9f238ba
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
| @@ -0,0 +1,54 @@ | ||||||
| --- | ||||||
| title: Hamilton Terminal Area | ||||||
| --- | ||||||
|
|
||||||
| --8<-- "includes/abbreviations.md" | ||||||
|
|
||||||
| !!! note "Hamilton Procedures" | ||||||
| The HTMA procedures build upon information already contained in the [NZHN Aerodrome Procedures](../aerodromes/Class-D/nzhn.md), and any Controller logged on to HTMA shall be familiar with those procedures. | ||||||
|
|
||||||
| ## Positions | ||||||
|
|
||||||
| | Position Name | Shortcode | Callsign | Frequency | Login ID | Usage | | ||||||
| | ----------------- | --------- | --------------------- | --------- | -------- | --------- | | ||||||
| | Hamilton TMA | HTMA | Bay Approach | 125.300 | NZHN_APP | Secondary | | ||||||
|
|
||||||
| !!! note Hamilton TMA | ||||||
| Controllers shall note that HTMA is a **secondary** position therefore BAY must be staffed before a controller may log on HTMA. | ||||||
|
|
||||||
| ## Airspace | ||||||
|
|
||||||
| Hamilton CTA/C follows the lateral and vertical boundaries as shown below. HTMA has a vertical limit of `A095`. Controllers shall be aware of which frequency to hand aircraft to, as shown on the image below. | ||||||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Image doesn't really show any ownership (and hence frequency)?
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Have updated Airspace image to reflect the boundary
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
|
|
||||||
| <figure markdown> | ||||||
|  | ||||||
| <figcaption>Hamilton TMA (CTA/D)</figcaption> | ||||||
| </figure> | ||||||
|
|
||||||
|
|
||||||
| ### Transfer of Control Points | ||||||
|
|
||||||
| |Transfer Flow | Requirements | Notes | | ||||||
| | -------------------- | ------------------------------------------------------------- | --------------------------------------------------------------------------- | | ||||||
| | Tower -> Approach | Once the aircraft becomes airborne off the runway | Tower shall instruct all aircraft to contact HTMA airborne | | ||||||
| | Approach -> Control | Once the aircraft are approaching the lateral bounds | Aircraft may be handed off when nothing further is required of the aircraft | | ||||||
| | Control -> Approach | Once the aircraft is approaching the cleared level by control | Aircraft may not always be cleared to A110 when handed to HTMA | | ||||||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
| | Approach -> Tower | Over the IAF (RNP) or established inbound on the VOR/DME | | | ||||||
|
|
||||||
| ## Departures | ||||||
|
|
||||||
| HTMA may climb all domestic aircraft to their RFL. | ||||||
|
|
||||||
| ## International | ||||||
|
|
||||||
| International Flights departing to the west via `UPLAR`, `MADEP` and `PEBLU` have a restriction of `A100` at `LEKUS`, this may be cancelled with coordination to RAN. All International departures may be climbed to `FL250` by HTMA, with further climb from RAN. | ||||||
|
|
||||||
| ## Arrivals | ||||||
|
|
||||||
| All arrivals will be handed to HTMA prior to `A110`. HTMA may track shorten as required. | ||||||
|
|
||||||
| HTMA shall note that whilst `RNP Z` is available for all RNP capable aircraft, `RNP Y` is CAT A/B only. | ||||||
|
|
||||||
| ## Coordination | ||||||
|
|
||||||
| HTMA shall coordinate any non-nominated approaches with HTWR. Any track shortening outside of HTMA's CTA shall be coordinated with the appropriate ENR sector. | ||||||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
Just to better match with language used in other pages |
||||||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure whether this is needed - does it make sense to expand do you think?