¶
¶ Tokyo Terminal Area
In this article, you will information useful to connect as RJTT_APP (Roughly Tokyo TMA)
¶ Table of Contents:
- Overview of Tokyo Approach Services
1.1 Air Traffic Services
1.2 Position Restrictions
1.3 Roles and Responsibilities
1.4 Approach Control Area
1.5 Terminal Control Area
- Procedures
2.1 Separation
2.2 Transition Level / Altitude
2.3 Coordination
2.4 Simultaneous Parallel ILS Approaches (SPIA)
2.5 Simultaneous Parallel LDA Approaches (SILA) (RJTT)
2.6 Simultaneous Parallel RNP Approaches (SIRA) (RJTT)
2.7 Simultaneous Parallel Independent Departures (SPID) (RJAA)
¶ Overview of Tokyo Approach Services
Approach Services provide control to aircraft within the Approach Control Area, usually in the arrival and departure phase of their flight.
The Objective of the Approach Services are the following (ICAO-ANNEX 11):
- Prevent collision between aircraft
- Prevent collision between the aircraft on the manoeuvering area and obstructions within that area
- Expedite and maintain orderly flow of air traffic.
¶ 1.1 Air Traffic Services
| Position | Callsign | ICAO | Frequency |
| RJTT ATS Services | |||
|
APP |
Tokyo Approach |
RJTT_APP |
119.1 MHz |
|
APP |
Tokyo Approach |
RJTT_F_APP |
119.65 MHz |
|
DEP |
Tokyo Departure |
RJAA_DEP |
126.0 MHz |
|
TWR |
Tokyo Tower |
RJTT_TWR |
118.100 MHz |
|
GND |
Tokyo Ground |
RJTT_GND |
118.225 MHz |
|
DEL |
Tokyo Delivery |
RJTT_DEL |
121.825 MHz |
| RJAA ATS Services | |||
|
APP |
Tokyo Approach |
RJAA_APP |
124.4MHz |
|
APP |
Tokyo Approach |
RJAA_F_APP |
119.45MHz |
|
DEP |
Tokyo Departure |
RJAA_DEP |
124.2MHz |
|
TWR |
Narita Tower |
RJAA_TWR |
118.2MHz |
|
GND |
Narita Ground |
RJAA_GND |
121.95MHz |
|
DEL |
Narita Delivery |
RJAA_DEL |
121.9MHz |
| Other ATS Services in Tokyo ACA | |||
|
APP |
Tokyo TCA |
RJTT_TCA_APP |
119.45MHz |
|
TWR |
Tateyama Tower |
Not On IVAO |
126.2 MHz |
|
FIS |
Koto Flight Service |
Not On IVAO |
122.7MHz |
|
TWR |
Kisarazu Tower |
RJTK_TWR |
236.8MHz |
|
TWR |
Shimofusa Tower |
RJTL_TWR |
325.4MHz |
|
GND |
Shimofusa Ground |
RJTL_GND |
228.2MHz |
¶ 1.2 Position Restrictions
RJTT_APP is the master position, and may be opened at any time. When other positions are not online, RJTT_APP covers top down for all Tokyo Airports. If RJAA_APP, RJTT_APP should relinquish control of all Narita arrivals.
Note 1: Tokyo Approach shall provide approach services for : RJTE, RJTK and RJTL.
For RJTT
- RJTT_APP will cover Departure until they connect, even when RJTT_F_APP is online.
- RJTT_F_APP can be opened when traffic requires, providing RJTT_TWR and RJTT_APP are both online. If Tower or Approach disconnects, and a suitable replacement is unavailable, RJTT_F_APP must disconnect or switch to Tower or Approach.
- RJTT_DEP can be opened when traffic requires, providing RJTT_TWR and RJTT_APP are both online. If Tower or Approach disconnects, and a suitable replacement is unavailable, RJTT_DEP must disconnect or switch to Tower or Approach.
For RJAA
- RJAA_APP may connect, provided that RJTT_APP is online
- RJAA_APP will cover Departure until they connect, even when RJAA_F_APP is online.
- RJAA_F_APP can be opened when traffic requires, providing RJAA_TWR and RJAA_APP are both online. If Tower or Approach disconnects, and a suitable replacement is unavailable, RJAA_F_APP must disconnect or switch to Tower or Approach.
- RJAA_DEP can be opened when traffic requires, providing RJAA_TWR and RJAA_APP are both online. If Tower or Approach disconnects, and a suitable replacement is unavailable, RJAA_DEP must disconnect or switch to Tower or Approach.
RJTT_TCA_APP is a VFR traffic advisory service and should only be opened when RJTT_APP is online and there is a significant amount of VFR traffic.
¶ 1.3 Roles and Responsibilities
¶ 1.3.1 Approach Services
- Handles all IFR arrivals
- Handles all traffic passing within the AoR
- Handles missed approaches
- Provide and maintain separation between all aircraft, using altitude, speed and vectors.
- Coordination with adjacent controllers for safe and efficient traffic flow
Note 1: If Final Approach is online, they handle IFR traffic within their AoR (coordinated with Approach), Usually once the traffic is established downwind until the final approach.
¶ 1.3.2 Departure Services
- Handles all IFR departures
- Handles go-around traffic, until a coordinated FL or point, where they are transferred to approach.
- Provide and maintain separation between all aircraft, using altitude, speed and vectors.
- Coordination with adjacent controllers for safe and efficient traffic flow
¶ 1.3.3 TCA Services
- Tokyo TCA, is a VFR traffic advisory service
¶ 1.4 Approach Control Area
¶ 1.5 Terminal Control Area
¶ Procedures
¶ 2.1 Separation
Inside of the Tokyo ACA, either horizontal or vertical separation must be applied:
- Due to Reduced Horizontal Separation, horizontal separation minima is 3NM
- The radar separation minimum may be reduced to 2.5NM (4.6km) between succeeding aircraft on final approach track within 10NM (18.5km) of the runway end.
- Vertical separation is 1000ft
Note 1: Radar wake separation must be applied
¶ 2.2 Transition Level / Altitude
Transition Level is always: FL140
Transition Altitude is always: 14 000ft
¶ 2.3 Coordination
Due to the layout and complexity of the Tokyo ACA, effective coordination between all active controllers is essential. For proper coordination the following shall be done:
- Maintain continuous communication with all relevant positions. (ACC, APP, DEP, TWR, OCA)
- Immediately inform adjacent positions of operational changes
- Negotiate/Coordinate handoff points for transfers
- Notify of emergency declarations
¶ 2.4 Simultaneous Parallel ILS Approaches (SPIA)
(Not to be confused with: Simultaneous Parallel ILS/PAR Approaches)
An Approach Controller shall be online for these procedures.
Simultaneous Parallel ILS Approaches are a type of ILS approaches to parallel runways with centerlines spaced by at least 4,300feet and with a No Transgression Zone(NTZ) established between the extended runway centerlines, where radar separation minima between aircraft on adjacent extended centerlines are not prescribed. ATC instructions are issued as necessary to ensure aircraft do not enter NTZ.
At Narita INTL airport, the applicable runways are:
- Runway 34L and 34R, Runway 16L and 16R at Tokyo INTL Airport
- Runway 34L and 34R, Runway 16L and 16R at Narita INTL Airport
Aircraft shall be advised that SPIA are in force. This information may be provided through the ATIS broadcasts. Example: “Simultaneous Parallel ILS Approaches to RWY34L and 34R are in progress.”
SPIA may be cleared when the following conditions are met. However, SPIA shall not be applied under certain adverse weather conditions which might affect safe operations (e.g. windshear on the final approach course, etc.):
- Straight-in landings will be made.
- Missed approach courses are diverged by at least 30°.
- ATC is monitoring the approaches to each runway.
ATC Procedures:
- ATC shall provide a minimum of 1,000ft vertical or minimum of 3.0NM radar separation until each aircraft intercepts each localizer course and then aircraft at the higher altitude intercepts glide path.
- ATC shall continue radar monitoring even after aircraft is switched to TWR frequency and instruct aircraft as prescribed below on the frequency when necessary.
- ATC shall instruct aircraft to return to the correct final approach course when aircraft are observed to over-shoot or to continue on a track which will penetrate NTZ, and instruct aircraft on the adjacent final approach course to avoid the deviating aircraft when an aircraft is observed penetrating NTZ.
ATC shall use the following Phraseology:
- Instruction to return to the correct localizer course
- “TURN LEFT/RIGHT AND RETURN TO THE LOCALIZER COURSE.”
- Instruction to avoid the deviating aircraft
- “TRAFFIC ALERT, [repeat aircraft identification], TURN LEFT/RIGHT IMMEDIATELY, HEADING [number], CLIMB AND MAINTAIN [altitude].”
- ATC shall terminate radar monitor when visual separation is applied by ATC, but shall not advise the aircraft that radar monitoring is terminated.
¶ 2.5 Simultaneous Independent LDA Approached (SILA) (RJTT)
An Approach Controller shall be online for these procedures.
Applicable instrument approach procedures for SILA:
- LDA W RWY22 (with VPT), LDA W RWY23 (with VPT), LDA Z RWY22 (with VPT), LDA Z RWY23 (with VPT), LDA X RWY22 (with VPT), and LDA X RWY23 (with VPT)
(VPT stands for Visual maneuver with Prescribed Track)
Aircraft shall be advised that SILA are in force. This information may be provided through the ATIS broadcasts. Example :"Simultaneous LDA approaches to RWY22 and RWY23 are in progress."
SILA may be cleared when the following conditions are met. However, SILA shall not be applied under certain adverse weather conditions which might affect safe operations (e.g. windshear on the final approach course, etc.):
- No Transgression Zone (NTZ) 610m wide is established equidistant between localizer courses
ATC Procedures:
- Aircraft shall be provided a minimum of 1,000ft vertical separation or a minimum of 3NM radar separation until intercepting localizer course.
- ATC shall continue radar monitoring even after aircraft is switched to TWR frequency and instruct aircraft as prescribed below on the frequency when necessary.
- Aircraft observed to overshoot the turn-on or continue on a track which will penetrate the NTZ will be instructed to return to the correct localizer course. If a deviating aircraft fails to respond to such instructions or is observed penetrating the NTZ, the aircraft on the adjacent localizer course shall be instructed to avoid the deviating aircraft.
- When going around, pilots should report ATC as soon as practicable, and proceed in accordance with the go around procedure described on the chart until receiving ATC instructions.
ATC shall use the following Phraseology:
- Instruction to return to the correct localizer course
- “TURN LEFT/RIGHT AND RETURN TO THE LOCALIZER COURSE.”
- Instruction to avoid the deviating aircraft
- “TRAFFIC ALERT, [repeat aircraft identification], TURN LEFT/RIGHT IMMEDIATELY, HEADING [number], CLIMB AND MAINTAIN [altitude].”
- ATC shall terminate radar monitor when visual separation is applied by ATC, but shall not advise the aircraft that radar monitoring is terminated.
¶ 2.6 Simultaneous Independent RNP Approached (SIRA) (RJTT)
An Approach Controller shall be online for these procedures.
Applicable instrument approach procedures for SIRA:
- RNP RWY16L, RNP RWY16R
Aircraft shall be advised that SILA are in force. This information may be provided through the ATIS broadcasts. Example :“Simultaneous RNP approaches to RWY16L and RWY16R are in progress.”
SIRA may be cleared when the following conditions are met. However, SIRA shall not be applied under certain adverse weather conditions which might affect safe operations (e.g. windshear on the final approach course, etc.):
- No Transgression Zone (NTZ) 610m wide is established equidistant between localizer courses
ATC Procedures:
- Aircraft shall be provided a minimum of 1,000ft vertical separation or a minimum of 3NM radar separation until intercepting the localizer course.
- ATC shall continue radar monitoring even after aircraft is switched to TWR frequency and instruct aircraft as prescribed below on the frequency when necessary.
- Aircraft observed to overshoot the turn-on or continue on a track which will penetrate the NTZ will be instructed to return to the correct localizer course. If a deviating aircraft fails to respond to such instructions or is observed penetrating the NTZ, the aircraft on the adjacent localizer course shall be instructed to avoid the deviating aircraft.
- When going around, pilots should report ATC as soon as practicable, and proceed in accordance with the go around procedure described on the chart until receiving ATC instructions.
ATC shall use the following Phraseology:
- Instruction to return to the correct localizer course
- “TURN LEFT/RIGHT AND RETURN TO THE LOCALIZER COURSE.”
- Instruction to avoid the deviating aircraft
- “TRAFFIC ALERT, [repeat aircraft identification], TURN LEFT/RIGHT IMMEDIATELY, HEADING [number], CLIMB AND MAINTAIN [altitude].”
- ATC shall terminate radar monitor when visual separation is applied by ATC, but shall not advise the aircraft that radar monitoring is terminated.
¶ 2.7 Simultaneous Parallel Independent Departures (SPID) (RJAA)
SPID will be conducted for the aircraft flying RNAV1 SID on the adjacent runway RWY34L/34R or RWY16L/16R.
Aircraft shall be advised that SPID are in force. This information may be provided through ATIS broadcasts, “Simultaneous parallel departures (from runway [number] left and right are) in progress.”
SPID, where radar separation minima between aircraft on the adjacent straight-out departure courses are not prescribed, will be conducted when the following conditions are met. However, SPID shall not be applied under certain adverse weather conditions which might affect safe operations (e.g. windshear, strong winds, etc.):
- Departure No Transgression Zone (DNTZ) 610m (2000ft) wide is established equidistant between initial straight-out segments of departure courses.
- The aircraft is flying an RNAV1 SID
ATC Procedures:
- ATC shall monitor both aircrafts to ensure aircraft does not deviate from the required path during the initial straight-out climb.
ATC Phraseology:
- To verify that the pilot has loaded the correct SID into their FMS, before take-off clearance is given ATC shall say “VERIFY INITIAL WAYPOINT [initial fix].” during the takeoff clearance, which requires the pilot to validate with: “RNAV TO [initial fix], RUNWAY [number], CLEARED FOR TAKE OFF.” If the initial Fix of the SID loaded into the FMS does not satisfy the verification, pilots shall not take off and advise ATC until alternative instructions are given.
- Aircraft observed to continue on a track which will penetrate DNTZ will be instructed to head to avoid aircraft on the adjacent departure course. If the deviating aircraft fails to respond ATC will instruct the adjacent aircraft to deviate.
- “TRAFFIC ALERT, [repeat aircraft identification], TURN LEFT/RIGHT IMMEDIATELY, HEADING [number], (CLIMB AND) MAINTAIN [altitude].”
The Initial Fixes on RNAV SIDs associated with each runway:
|
RUNWAY |
INITIAL FIX |
|
34L |
ARIES (ASTRA*) |
|
34R |
BOXER |
|
16L |
BEAMS |
|
16R |
ASPEN |
*Only for PEDLA [number] DEPARTURE
¶ Aerodromes
Find RJAA and RJTT here : Haneda (RJTT) - Narita (RJAA)
¶ A.1 RJTE Tateyama (Mil)
RJTE Tateyama, is a military airbase outside the city of Tateyama in the Chiba Prefecture.
|
Information |
|
|
ICAO |
RJTE |
|
IATA |
- |
|
Aerodrome Name |
Tateyama |
|
Time Zone Conversion |
UTC +9 |
|
Coordinates |
345915N / 1394955E |
|
Direction and distance from (City) |
1.6nm WSW of Tateyama Railway Station |
|
Altitude / Temperature reference |
10ft / - |
|
MAG VAR/ Annual change |
- |
|
ATS Services |
(Not on IVAO) Tateyama Tower (126.2MHz) |
|
Permitted traffic types |
IFR/VFR |
|
Runway |
09 / 27 |
|
Local Regulations |
APP provided by Tokyo APP |
|
Remarks |
Military aerodrome |
|
RJTE - Standard Instrument Departures |
||
|
Final Fix |
SID |
Runway |
|
TATEYAMA |
TATEYAMA REVERSAL 3 |
09 / 27 |
|
RJTE - Standard Terminal Arrival |
||
|
Final Route Fix |
IAP |
STAR |
|
SAPIM |
TACAN A |
nil |
¶ A.4 RJTK Kisarazu (Mil)
RJTK Kisarazu, is a military air field, north of Kisarazu in the Chiba Prefecture
|
Information |
|
|
ICAO |
RJTK |
|
IATA |
- |
|
Aerodrome Name |
Kisarazu |
|
Time Zone Conversion |
UTC +9 |
|
Coordinates |
352342N / 1395447E |
|
Direction and distance from (City) |
1.2nm NNW from Kisarazu |
|
Altitude / Temperature reference |
10ft / - |
|
MAG VAR/ Annual change |
|
|
ATS Services |
RJTK_TWR Kisarazu Tower (236.8MHz) |
|
Permitted traffic types |
IFR / VFR |
|
Runway |
02 / 20 (1830 x 45) |
|
Local Regulations |
APP provided by Tokyo APP |
|
Remarks |
Military aerodrome |
|
RJTK - Standard Terminal Arrival |
|||
|
Final Fix |
SID |
Runway |
|
|
KOSKA |
KOSKA 1 |
02 |
|
|
TSUGA |
TSUGA 2 |
02 / 20 |
|
|
RJTK - Standard Terminal Arrival |
|||
|
Final Route Fix |
IAP |
STAR |
|
|
TATEYAMA |
TACAN RWY02 |
TATEYAM |
|
¶ A.3 RJTL Shimofusa
RJTL Shimofusa, is a military air base, east of Matsudo in the Chiba Prefecture
|
Information |
|
|
ICAO |
RJTL |
|
IATA |
- |
|
Aerodrome Name |
Shimofusa |
|
Time Zone Conversion |
UTC +9 |
|
Coordinates |
354756N / 1400044E |
|
Direction and distance from (City) |
5.4NM E MATSUDO |
|
Altitude / Temperature reference |
96FT/ - |
|
MAG VAR/ Annual change |
- |
|
ATS Services |
RJTL_TWR Shimofusa Tower (325.4MHz) RJTL_GND Shimofusa Ground (228.2MHz) |
|
Permitted traffic types |
IFR / VFR |
|
Runway |
01 / 19 (2250×45) |
|
Local Regulations |
- |
|
Remarks |
Military Airbase |
|
RJTL - Standard Terminal Arrival |
|||
|
Final Fix |
SID |
Runway |
|
|
Utsunomiya |
UTSUNOMIYA ONE |
01 / 19 |
|
|
OMIYA |
WEST 5 |
||
|
TSUGA |
TSUGA 4 |
||
|
KOGAR |
KOGAR 2 |
||
|
RJTL - Standard Terminal Arrival |
|||
|
Final Route Fix |
IAP |
STAR |
|
|
TOHNE |
ILS Z / LOC Z RWY 19 ILS Y / LOC Y RWY 19 |
19 |
|
¶ A.4 RJTI Tokyo Heliport
RJTE Tateyama, is a military airbase outside the city of Tateyama in Chiba Prefecture.
|
Information |
|
|
ICAO |
RJTI |
|
IATA |
- |
|
Heliport Name |
Tokyo Heliport |
|
Time Zone Conversion |
UTC +9 |
|
Coordinates |
353810N / 1395022E |
|
Direction and distance from (City) |
- |
|
Altitude / Temperature reference |
16FT / - |
|
MAG VAR/ Annual change |
8° W(2025) / 2.4’W |
|
ATS Services |
(Not on IVAO) Koto Flight Service (122.7MHz) |
|
Permitted traffic types |
VFR |
|
Runway |
nil |
|
Remarks |
|