South Sector Procedures

Section 1: General

1.1 Area of Responsibility

NZCH-S_CTR (South Sector) is responsible for all controlled airspace within their designated area of responsibility (see diagram), excluding Christchurch Terminal and Dunedin, Queenstown and Invercargill Towers when those units are online.

Controls up to FL600. Controls area above NZCH_APP from FL255 to FL600.

Note: NZCH-K_CTR (Kaikoura Sector) is responsible for Christchurch Terminal when they are offline.

Controllers/Standard Operating Procedures/South Sector Procedures/South Sector Diagram

1.2 Frequency and Sector Information

 

CallsignNZCH-S_CTR
Primary Frequency129.300 MHz
RTF DesignatorChristchurch Control
Sector NameSouth
Sector AbbreviationSTH
Telephone DesignatorSouth

 

Section 2: Kaikoura Sector Procedures

2.1 Area of Responsibility:

Kaikoura is responsible for controlled airspace within their area of responsibility as depicted in Part 1, Section 1.1 of the Kaikoura Sector SOP.

2.2 Transfer of Control Points:

Unless otherwise coordinated, the transfer of control point shall be at the common airspace boundary.

2.3 Transfer of Communications

Unless otherwise coordinated, the transfer of communicatons shall occur prior to the common airspace boundary.

Section 3: Christchurch Terminal Procedures

3.1 Area of Responsibility:

Christchurch Terminal is responsible for controlled airspace within their area of responsibility as depicted in Part 1, Section 1.1 of the Christchurch Terminal SOP.

3.2 Arrival Sequencing:

South shall ensure that aircraft on the same or adjacent STARs, landing NZCH, are sequenced such that they are 10 miles in trail of each other, unless otherwise coordinated.

3.3 Standard Descents:

Unless otherwise coordinated, South shall descend aircraft to the following levels:

Landing NZCH: 11,000ft or lower cruise.

3.4 Transfer of Control Points:

Unless otherwise coordinated, the transfer of control point shall be at the common airspace boundary.

3.5 Transfer of Communications:

Unless otherwise coordinated, the transfer of communications shall occur prior to the common airspace boundary.

3.6 Oceanic Flights:

Christchurch Terminal may handoff Oceanic departures to South prior to the common airspace boundary, allowing South to climb oceanic aircraft above FL250 prior to the common boundary.

Section 4: Queenstown Terminal Procedures

4.1 Area of Responsibility:

Queenstown Terminal is reponsible for all flights within the QN CTA/D and CTR/D, FL175 and below.

4.2 Standard Descents:

Unless otherwise coordinated, South shall descend aircraft to:

  • 11,000ft or lower cruise (if on conventional navigation).
  • STAR Profile to FL150 (when on a RNAV STAR).

4.3 Arrival Sequencing:

South shall assign a RNAV STAR arrival for flights arriving into Queenstown unless otherwise coordinated with Queenstown Terminal.  Unless otherwise coordinated, the STAR shall be assigned for the duty runway.

If no STAR arrival is to be flown and the aircraft is anticipating a visual approach, or an approach not served by a STAR then this must be noted in the scratchpad (e.g. 'VIS23', 'VOR-B') and coordinated with Queenstown Terminal at the earliest of oppurtunities.  All approaches (apart from RNAV RNP) are circling approaches and require a visual segment to circle and land.

The preference of approaches at Queenstown is as follows:

  • RNAV F (Runway 05) or RNAV G (Runway 23)
  • VOR/DME C (Runway 05) or VOR/DME B (Runway 23)
  • RNAV RNP Y (Runway 05) or RNAV RNP Y (Runway 23)

Note: Due to the navigation database limitations in most payware addon aircraft, the RNP approaches will not be available to most users.

4.4 Transfer of Control Points:

Arriving Aircraft:  50 QN DME, unless otherweise coordinated.

Departing Aircraft:  Nearing FL175; or 35 QN DME, whichever is first.

4.5 Transfer of Communications:

Arriving Aircraft:  50 QN DME, unless otherweise coordinated.

Departing Aircraft:  Nearing FL175; or 35 QN DME, whichever is first.

4.6 Unattended Procedures:

When Queenstown Terminal & Tower are offline, South is responsible for issuing IFR clearances to departing aircraft.

Section 5: Dunedin Tower Procedures

5.1 Area of Responsibility:

Dunedin Tower is reponsible for all flights within the DN CTA/D and CTR/D, including the CH CTA/C, south of 35 SW DME, 13,500ft and below.

5.2 Standard Descents:

Unless otherwise coordinated, South shall descend aircraft to: 11,000ft or lower cruise.

5.3 Arrival Sequencing:

South shall assign a RNAV STAR arrival for flight arriving into Dunedin unless otherwise coordinated with Dunedin Tower.  Unless otherwise coordinated, the STAR shall be for the duty runway.

5.4 Transfer of Control Points:

Arriving Aircraft: 35 SW DME, unless otherwise coordinated.

Departing Aircraft: 35 SW DME, unless otherwise coordinated.

5.5 Transfer of Communications:

Arriving Aircraft: 35 SW DME, unless otherwise coordinated.

Departing Aircraft: 35 SW DME, unless otherwise coordinated.

5.6 Unattended Procedures:

When Dunedin Tower is offline, South is responsible for issuing IFR clearances to departing aircraft.

Section 6: Queenstown Tower Procedures

6.1 Area of Responsibility:

Queenstown Tower is reponsible for all flights within the QN CTR/D 7,500 ft and below.

6.2 Standard Descents:

Unless otherwise coordinated, South shall descend aircraft to:

  • 7,500ft (if on conventional navigation).
  • Approach Profile to 7,500 ft (when on one of the three approaches in 6.3).

6.3 Arrival Sequencing:

South shall assign an approach for flights arriving into Queenstown unless otherwise coordinated with Queenstown Tower.  Unless otherwise coordinated, the approach shall be assigned for the duty runway.

All approaches including visual, must be noted in the scratchpad (e.g. 'VIS23', 'VOR-B', "RNAV F","RNAV Y") and coordinated with Queenstown tower at the earliest of oppurtunities.  All approaches (apart from RNAV RNP) are circling approaches and require a visual segment to circle and land.

The preference of approaches at Queenstown is as follows:

  • RNAV F (Runway 05) or RNAV G (Runway 23)
  • VOR/DME C (Runway 05) or VOR/DME B (Runway 23)
  • RNAV RNP Y (Runway 05) or RNAV RNP Y (Runway 23)

Note: Due to the navigation database limitations in most payware addon aircraft, the RNP approaches will not be available to most users.

6.4 Transfer of Control Points:

Arriving Aircraft:  Nearing QN CTR/D boundary unless otherwise coordinated.

Departing Aircraft:  Nearing 7,500 ft  or QN CTR/D boundary, whichever is first.

6.5 Transfer of Communications:

Arriving Aircraft:  Nearing QN CTR/D boundary unless otherwise coordinated.

Departing Aircraft:  Nearing 7,500 ft  or QN CTR/D boundary, whichever is first.

6.6 Unattended Procedures:

When Queenstown Tower is offline, South is responsible for issuing IFR clearances to departing aircraft.

Section 7: Invercargill Tower Procedures

7.1 Area of Responsibility:

Invercargill Tower is reponsible for all flights within the NV CTA/D and CTR/D, including CH CTA/D within 50 DME NV, 13,500ft or below.

7.2 Standard Descents:

Unless otherwise coordinated, South shall descend aircraf to:  11,000ft or lower cruise

7.3 Arrival Sequencing:

South shall clear arriving aircraft with a STAR arrival for the duty runway at Invercargill, as listed in the Invercargill ATIS.  Aircraft are still to be cleared a STAR, even if the aircraft is anticipating a visual approach.  This is because of separation requirements in procedurally controlled airspace.

7.4 Transfer of Control Points:

Arriving Aircraft:  50 NV DME, unless otherwise coordinated.

Departing Aircraft:  50 NV DME, unless otherwise coordinated.

7.5 Transfer of Communications:

Arriving Aircraft:  50 NV DME, unless otherwise coordinated.

Departing Aircraft:  50 NV DME, unless otherwise coordinated.

7.6 Unattended Procedures:

When InvercargillTower is offline, South is responsible for issuing IFR clearances to departing aircraft.