STEP |
Period |
Remarks |
Trial Operation |
‘17.7.19 1600 ~ ‘18.1.3 1559(UTC) |
1.4.4.5 is not applicable |
Operation |
‘18.1.3 1600(UTC) ~ |
NOTAM will be issued when the schedule is changed. |
Application date and time period:
Application area (sectors, airports, etc.);
Reason for flow control execution;
Expected ATFM Measures
GDP (Ground Delay Program)
GS (Ground Stop)
AFP (Airspace Flow Program)
MIT (Miles In Trail)
MINT (Minutes In Trail)
Re-Route
other necessary information
PHASE | CONTENTS | REMARKS |
STEP1 | COBT/CLDT assign | |
STEP2 | SLOT exchange | within 20minute after assign |
STEP3 | COBT/CLDT finalize |
Flights departing from Incheon FIR: at least 2 hours prior to the estimated off-block time (EOBT); and
Flights entering into Incheon FIR: at least 2 hours prior to entering Incheon FIR
Emergency aircraft (including high-jacked aircraft);
aircraft for mercy or humanitarian operations;
aircraft for medical support operations;
SAR (search and rescue) aircraft;
presidential aircraft;
any other particular aircraft requested by government authorities (including military aircraft)
Daegu, 41059, Republic of Korea
Tel : +82-53-668-0453,0454
Telefax : +82-53-668-0465
E-mail : atcc@korea.kr
AFTN : RKDAZAZX
Operators must obtain operational approval from the State of Registry to conduct RVSM operations.
(Source Document: FAA Interim Guidance (IG) 91-RVSM/JAA TGL #6) Operators must obtain airworthiness and operational approval from the State of Registry or State of the Operator, as appropriate, to conduct RVSM operations. On behalf of the ICAO Asia and Pacific Office, the FAA is maintaining a website (http://www.faa.gov/ats/ato/rvsm1.htm) containing documents and policy for RVSM approval.
(Source Document: IG 91-RVSM/TGL #6, Pacific Minimum Monitoring Requirements) Operators are required to participate in the RVSM aircraft monitoring program. This is an essential element of the RVSM implementation program in that it confirms that the aircraft altitude-keeping performance standard is being met. The PARMO/MAAR will process the results of monitoring. For further information on RVSM monitoring, the PARMO web site can be accessed by accessing the "RVSM Documentation" section of the FAA RVSM website and clicking on the link to the PARMO/MAAR website.
Pilots of aircraft operating in accordance with IFR, when deviate for any reason, 300 feet or more from cleared by ATC unit between FL 290 and FL 410 inclusive within the RVSM airspace prescribed in paragraph 2.1 above shall submit reports using the Attachment A or radio to ATC unit on each occurrence of an altitude deviation. Such shall be submitted independently of "RA reports".
Operators approved by Ministry of Land, Transport and Maritime Affairs shall collect all Large Height Deviation reports referred in paragraph 4.3.3.1.1 and dispatch them as soon as possible to the following address: Air Traffic Management Division, Office of Civil Aviation Ministry of Land, Transport and Maritime Affairs
Tel : +82-44-201-4301
Fax : +82-44-201-5631
PARMO:
Tel: +1-202-863-2175
Fax: +1-202-862-2398
E-mail: monitor@cssiinc.com
MAAR:
Tel: +66-2-287-8154
Fax: +66-2-287-8155
E-mail: maar@aerothai.co.th
two primary altimetry systems;
one automatic altitude-keeping device;
one altitude-alerting device; and
one SSR altitude reporting transponder.
is no longer RVSM compliant due to equipment failure; or
experiences loss of redundancy of altimetry systems; or
encounters turbulence that affects the capability to maintain flight level.
FLAS on A593
SADLI |
0°∼179° |
NIRAT |
Remarks |
FL410 FL370 FL350 FL330 FL270* |
→ → → → → |
FL410 FL370 FL350 FL330 FL270* |
CVSM Level |
SADLI |
180°∼359° |
NIRAT |
Remarks |
FL380 FL360 FL340 FL320 FL260* |
← ← ← ← ← |
FL380 FL360 FL340 FL320 FL260* |
CVSM Level |
FLAS : A586
RUGMA |
0°∼179° |
CJU |
Remarks |
FL380 FL360 FL340 FL320 FL260* |
← ← ← ← ← |
FL380 FL360 FL340 FL320 FL260* |
CVSM Level |
RUGMA |
180°∼359° |
CJU |
Remarks |
FL410 FL370 FL350 FL330 FL270* |
→ → → → → |
FL410 FL370 FL350 FL330 FL270* |
CVSM Level |
FLAS on G203
PSN |
0°∼179° |
KALEK |
Remarks |
FL410 FL390 FL370 FL350 FL330 FL310 FL290 |
→ → → → → → → |
FL410 FL390 FL370 FL350 FL330 FL310 FL290 |
PSN |
180°∼359° |
KALEK |
Remarks |
FL380 FL340 FL300 |
← ← ← |
FL380 FL340 FL300 |
FLAS on G339
PSN |
0°∼179° |
INVOK |
Remarks |
FL410 FL390 FL370 FL350 FL330 FL310 FL290 |
→ → → → → → → |
FL410 FL390 FL370 FL350 FL330 FL310 FL290 |
PSN |
180°∼359° |
INVOK |
Remarks |
FL400 FL360 FL320 |
← ← ← |
FL400 FL360 FL320 |
FLAS on A582
PSN |
0°∼179° |
APELA |
Remarks |
FL410 FL390 FL370 FL350 FL330 FL310 FL290 |
→ → → → → → → |
FL410 FL390 FL370 FL350 FL330 FL310 FL290 |
PSN |
180°∼359° |
APELA |
Remarks |
FL380 FL340 FL300 |
← ← ← |
FL380 FL340 FL300 |
Note. Altitude assignment in RVSM Airspace not listed above will be applied in accordance with the Letter of Agreement between the ACC concerned based on Single Alternate FLOS.
FLIGHT PRIORITY. It should be noted that RVSM approval aircraft will be given priority for level allocation over non-RVSM approval aircraft.
Do not climb or descend at less than the normal rate for the aircraft and
Do not level off at an intermediate level while passing through the RVSM stratum.
The aircraft is being initially delivered to the State of Registry or Operator (see Paragraph 9 for additional details and information); or
The aircraft was formally RVSM approved but has experienced an equipment failure and is being flown to a maintenance facility for repair in order to meet RVSM requirements and/or obtain approval; or
The aircraft is transporting a spare engine mounted under the wing; or
The aircraft is being utilized for mercy or humanitarian purposes; or
State aircraft (those aircraft used in military, custom and police services shall be deemed state aircraft)
Note: These procedures are intended exclusively for the purposes of indicated above and not as a means to circumvent the normal RVSM approval process.
Incheon Air Traffic Control Regional Office(Incheon ACC)
Tel : +82-32-880-0288
Telefax : +82-32-889-5906
Email : g_atcdiv@molit.go.kr
AFS : RKRRZQZX
Weekdays : TGU - APELA
Weekend/holiday : VASLI - APELA
Offset will be initiated as follows;
Incheon ACC will instruct offset 6 NM right of G597/Y697 centerline to all the aircraft bound for Shanghai FIR(bound for DONVO) via ANSIM- AGAVO on G597/Y697, and then Incheon ACC will transfer their air traffic controlling to Dalian ACC.
Offset will be cancelled as follows;
For the aircraft entering Incheon FIR instructed to do offset 6 NM right of G597/Y697 centerline by Dalian ACC, Incheon ACC will instruct them to join Y644 when needed. All aircraft must maintain their original offset status unless otherwise instructed by Incheon ACC.
Offset initiation
(Call Sign) Proceed offset 6miles Right of G597/Y697 Centerline/Track (Significant Point or Time) Until (Significant Point or Time)
Offset cancellation
(Call Sign) Cancel offset (instructions to rejoin cleared flight route or other information)
Eastbound aircraft from KARBU will be applied 3 miles right of G597/Y697/B467/Y437/L512 centerline.
Westbound aircraft from ANDOL will be applied 3 miles right of G597/Y697/B467/Y437/L512 centerline.
Aircraft that lands at RKSI, RKSS will be transferred to Seoul Approach at 10NM northeast of KARBU after being instructed to proceed direct to KARBU.
Aircraft flying from KARBU to ANDOL will be transferred to Tokyo ACC at 10NM southwest of ANDOL after being instructed to proceed direct to ANDOL.
Offset initiation
Call Sign) Proceed offset 3miles Right of Centerline/Track
Offset cancellation
(Call Sign) Cancel Offset Proceed Direct to (Significant Point)
Northeastbound aircraft on Y579 will be applied 3 miles right of Y579 centerline.
Southwestbound aircraft on Y579 will be applied 3 miles right of Y579 centerline.
Aircraft that lands at RKPC(Jeju Airport) will be transferred to Jeju Approach in the state of offset 3NM right of MAKET.
Aircraft that does not land at RKPC will be instructed to proceed direct to CJU at 10NM northeast of MAKET.
Aircraft lands at RKPK(Gimhae Airport) will be transferred to Gimhae Approach in the state of offset 3NM right of TOPAX.
Aircraft that does not land at RKPK will be instructed to proceed direct to TOPAX at 10NM southwest of TOPAX.
Offset initiation
(Call Sign) Proceed Offset 3miles Right of Center Line/Track
Offset cancellation
(Call Sign) Cancel Offset Proceed Direct to (Significant Point)
(Web site : www.molit.go.kr)
Report of an Altitude Deviation of 300 ft or More Between FL 290 and FL 410 |
|
Reporting agency |
|
Location of deviation |
|
Date of occurrence (UTC) |
|
Flight identification and type |
|
Flight level assigned |
|
Observed/reported final level Mode C/Pilot report |
|
Duration at flight level |
|
Other traffic |
|
Crew comments, if any, when noted |
|
Remarks |
|
Report to MOLIT when an altitude deviation of 300 feet or more, including those due to ACAS, turbulence and contingency events. Report to following address: |
|
Air Traffic Management Division, Office of Civil Aviation, Ministry of Land, Infrastructure and Transport Tel : +82-44-201-4301 Fax : +82-44-201-5631 |
CONTINGENCY SCENARIOS.
The following paragraphs summarize pilot actions to mitigate the potential for conflict with other aircraft in certain contingency situations.
* Scenario 1: All automatic altitude control systems fail (e.g., Automatic Altitude Hold).
The Pilot should |
ATC can be expected to |
Initially |
|
Maintain Cleared Flight Level (CFL) |
|
Evaluate the aircraft's capability to maintain altitude through manual control. |
|
Subsequently |
|
Watch for conflicting traffic both visually and by reference to ACAS, if equipped. |
|
If considered necessary, alert nearby aircraft by
|
|
Notify ATC of the failure and intended course of action. Possible courses of action include: |
Obtain pilots intentions, and pass essential traffic information. |
1) maintaining the CFL and route, provided that the aircraft can maintain level. |
1) If the pilot intends to continue in RVSM airspace, assess traffic situation to determine if the aircraft can be accommodated through the provision of lateral, longitudinal, or conventional vertical separation, and if so, apply the appropriate minimum. |
2) requesting ATC clearance to climb above or descend below RVSM airspace if the aircraft cannot maintain CFL and ATC cannot establish lateral, longitudinal or conventional vertical separation. |
2) If the pilot requests clearance to exit RVSM airspace, accommodate expeditiously, if possible. |
3) Notify adjoining ATC facilities/ sectors of the situation. |
* Scenario 2: Loss of redundancy in primary altimetry systems
The Pilot should |
ATC can be expected to |
If the remaining altimetry system is functioning normally, couple that system to the automatic altitude control system, notify ATC of the loss of redundancy and maintain vigilance of altitude keeping. If unable to confirm primary altimeter system accuracy, follow pilot actions listed in the Scenario 3. |
Acknowledge the situation and continue to monitor progress |
* Scenario 3: All primary altimetry systems are considered unreliable or fail
The Pilot should |
ATC can be expected to |
Maintain CFL by reference to the standby altimeter (if the aircraft is so equipped). |
|
Alert nearby aircraft by
|
|
Consider declaring an emergency. Notify ATC of the failure and intended course of action. Possible courses of action include: |
Obtain pilot's intentions, and pass essential traffic information. |
1) maintaining CFL and route provided that ATC can provide lateral, longitudinal or conventional vertical separation. |
1) If the pilot intends to continue in RVSM airspace, assess traffic situation to determine if the aircraft can be accommodated through the provision of lateral, longitudinal, or conventional vertical separation, and if so, apply the appropriate minimum. |
2) requesting ATC clearance to climb above or descend below RVSM airspace if ATC cannot establish adequate separation from other aircraft. |
2) If the pilot requests clearance to exit RVSM airspace, accommodate expeditiously, if possible. |
3) Notify adjoining ATC facilities/sectors of the situation. |
* Scenario 4: The primary altimeters diverge by more than 200 ft (60 m)
The Pilot should |
Attempt to determine the defective system through established trouble-shooting procedures and/or comparing the primary altimeter displace to the standby altimeter (as corrected by the correction cards, if required). |
If the defective system can be determined, couple the functioning altimeter system to the altitude-keeping device. |
If the defective system cannot be determined, follow the guidance in Scenario 3 for failure or unreliable altimeter indications of all primary altimeters. |
* Scenario 5: Turbulence (greater than moderate) which the pilot believes will impact the aircraft's capability to maintain flight level.
The Pilot should |
ATC can be expected to |
Watch for conflicting traffic both visually and by reference to ACAS, if equipped. |
|
Alert nearby aircraft by
|
|
Notify ATC of intended course of action as soon as possible. Possible courses of action include: |
|
1) maintaining CFL and route provided ATC can provide lateral, longitudinal or conventional vertical separation. |
1) Assess traffic situation to determine if the aircraft can be accommodated through the provision of lateral, longitudinal, or conventional vertical separation, and if so, apply the appropriate minimum. |
2) requesting flight level change, if necessary. |
2) If unable to provide adequate separation, advise the pilot of essential traffic information and request pilot's intentions. |
3) Notify adjoining ATC facilities/sectors of the situation. |