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

YPEA Procedures #402

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
64 changes: 63 additions & 1 deletion docs/aerodromes/classc/Pearce.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,69 @@

--8<-- "includes/abbreviations.md"

Reserved.
## Positions

| Name | Callsign | Frequency | Login ID |
| ------------------ | -------------- | ---------------- | --------------------------------------|
| **Pearce ADC** | **Pearce Tower** | **118.300** | **PE_TWR** |
| **Pearce SMC** | **Pearce Ground** | **127.250** | **PE_GND** |
| **Pearce ACD** | **Pearce Delivery** | **134.100** | **PE_DEL** |
| Pearce ATIS | | 136.400 | YPEA_ATIS |

## Airsapce

PE ADC owns the Class C airspace **in the PE CTR** within 5nm of the YPEA ARP from `SFC` to `A035`. This airspace is primarily used for military circuits and initial and pitch approaches.

### SID Selection
Aircraft planned via **WAMAL**, **GUNOK**, **ALKIMOS**, **MULLALOO**, shall be assigned the **Procedural SID** that terminates at the appropriate waypoint.
Copy link
Contributor

Choose a reason for hiding this comment

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

Just double checking the alkimos and Mullaloo waypoints are visual waypoints? If not, change to the waypoint names

Copy link
Contributor Author

@ST6-Bravo ST6-Bravo Dec 17, 2024

Choose a reason for hiding this comment

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

I believe they are visual waypoints

Copy link
Contributor

Choose a reason for hiding this comment

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

Curious how a visual waypoint can be attached to a procedural sid?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

While they are towns, the pilots fly it according to the tacan hence its a proc sid.

Copy link
Contributor

Choose a reason for hiding this comment

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

Can I get a reference for this in the manuals?

Aircraft who are not planned via those points or who are negative RNAV may be assigned a RADAR SID or a visual departure.

!!! Note
Due to Civil Traffic Arriving from the North, the GUNOK SID will have an altitude assignment of A030.

### Level Assignment
The Standard Assignable Level from **PE ADC** to **PE TCU** is:
a) The Lower of `F130` or `RFL` for Aircraft assigned via Procedural or RNAV SID.
b) `F130` for Aircraft assigned a Coded Departure.

#### Miscellaneous

### Circuit Operations
The Circuit Area Airspace is allocated to be within 5nm of the YPEA ARP from `SFC` to `A032`. Aircraft can be instructed to extend outside of this airspace by ATC for traffic management. Hawks have circuit altitude of A016 while both 2FTS and RSAF PC21s are assigned A012.

!!! Note
36L/18R is unsuitable for HAWK Aircraft

### Circuit Direction
| Runway | Direction |
| ------ | ----------|
| 5 | Left |
| 18L | Right |
| 18R | Right |
| 23 | Right |
| 36L | Left |
| 36R | Left |

### Initial and Pitch Procedures
ST6-Bravo marked this conversation as resolved.
Show resolved Hide resolved

| Runway | Direction Initial | Inital Altitude
| ------ | ------------------|----------------|
| 5 | Any | A010
| 18L | Left/Straight | A015 | Right | A010
| 18R | Left/Straight | A015 | Right | A010
| 23 | Any | A015
| 36L | Left | A010 | Right | A015
| 36R | Left | A010 | Right | A015

## Coordination
### PE TCU

'Next' coordination is required from PE ADC to PE TCU for all aircraft.

!!! example
<span class="hotline">**PE ADC** -> **PE TCU**</span>: "Next, ASY01, runway 36L"
<span class="hotline">**PE TCU** -> **PE ADC**</span>: "ASY01, Assigned Heading Right 030, unrestricted"
<span class="hotline">**PE ADC** -> **PE TCU**</span>: "Assigned Heading Heading Right 030, ASY01"
## Charts
!!! note
Additional charts to the AIP may be found in the RAAF TERMA document, available towards the bottom of [RAAF AIP page](https://ais-af.airforce.gov.au/australian-aip){target=new}