FIRST SCHEDULE
AIR TRAFFIC SERVICES AIRSPACE CLASSES-SERVICES PROVIDED AND FLIGHT REQUIREMENTS
| Class | Type of Flight | Separation provided | Service provided | speed limitation | Radio Communication requirement | Subject to an ATC clearance |
|---|
| A | IFR only | All aircraft | Air traffic control service | Not applicable | Continuous two way | Yes |
| B IFRVFR | All aircraft | Air traffic control service | Not applicable | Continuous two way | Yes |
| All aircraft | Air traffic control service | Not applicable | Continuous two way | Yes |
| C IFR | VFR from IFR | 1)Air traffic control service for separation from IFR | Not applicable | Continuous two way | Yes |
| VFR | VRF from IFR | 2) VFR/VFR traffic information (and traffic avoidance advice on request | 250 kt IAS below 3050 m (10 000ft) AMSL | Continuous two way | Yes |
| D | IFR | IFR from IFR | Air traffic control service, traffic information about VFR flights (and traffic avoidance on request) | 250 kt IAS below 3050 m (10 000ft) AMSL | Continuous two way | Yes |
| | VFR | Nil | IFR/VFR and VFR/VFR traffic Information(and traffic avoidance advice on request | 250 kt IAS below 3050 m (10 000ft) AMSL | Continuous two way | Yes |
| E | IFR | IFR from IFR | Air traffic control service and as far as practical traffic information about VFR flights | 250 kt IAS below 3050 m (10 000ft) AMSL | Continuous two way | Yes |
| | VFR | nil | Traffic information as far as practical | 250 kt IAS below 3050 m (10 000ft) AMSL | No | No |
| F | IFR | IFR from IFR as far as practical | Air traffic advisory service, flight information serviceflight information service | 250 kt IAS below 3050 m (10 000ft) AMSL | Continuous two way | No |
| | VFR | Nil | flight information service | 250 kt IAS below 3050 m (10 000ft) AMSL | No | No |
| | IFR | Nil | flight information service | 250 kt IAS below 3050 m (10 000ft) AMSL | Continuous two way | No |
| G | VFR | Nil | flight information service | 250 kt IAS below 3050 m (10 000ft) AMSL | No | No |
| When the height of the transition altitude is lower than 3 050 m 10 003 It) AMSL FL 103 should be used in lieu of 100005 | |
SECOND SCHEDULE
PRINCIPLES GOVERNING THE IDENTIFICATION OF NAVIGATION SPECIFICATIONS AND THE IDENTIFICATION OF ATS ROUTES OTHER THAN STANDARD DEPARTURE AND ARRIVAL ROUTES
1. Designators for ATS routes and navigation specifications.
1.1The purpose of a system of route designators and navigation specifications applicable to specified ATS route segments, routes or area is to allow both pilots and ATS, taking into account automation requirements—(a)to make unambiguous reference to anyATS route without the need to resort to the use of geographical coordinates or other means in order to describe it;(b)to relate an ATS route to a specific vertical structure of the airspace, as applicable;(c)to indicate a required level of navigation performance accuracy, when operating along an ATS route or within a specified area; and(d)to indicate that a route is used primarily or exclusively by certain types of aircraft.Note I— Specifications governing the publication of navigation specifications are given in the Civil Aviation (Aeronautical Charts) Regulations 2017, the Civil Aviation(Aeronautical Information Services) Regulations 2017Note 2 - In relation to this part and for flight planning purposes, a prescribed navigation specification is not considered an integral part of the ATS route designator.1.2In order to meet this purpose, the designation system shall—(a)permit the identification of any ATS route in a simple and unique manner;(c)be usable by both ground and airborne automation systems;(d)permit utmost brevity in operational use; and(e)provide sufficient possibility of extension to cater for any future requirements without the need for fundamental changes.1.3Controlled, advisory and uncontrolled ATS routes, with the exception of standard arrival and departure routes, shall therefore be identified as specified hereafter.2. Composition of designator
2.1The ATS route designator shall consist of a basic designator supplemented, if necessary, by—(a)one prefix as prescribed in 2.3; and(b)one additional letter as prescribed in2.4.2.1.1The number of characters required to compose the designator shall not exceed six characters.2.12The number of characters required to compose the designator should, possible, be kept to a maximum of five characters.2.2The basic designator shall consist of one letter of the alphabet followed by a number from I to 999.2.2.1Selection of the letter shall be made from those listed hereunder—(a)A ,B ,G R for routes which form part of the regional networks of ATS routes and are not area navigation routes;(b)L,M ,N ,P for area navigation routes which form part of the regional networks of ATS routes;(c)H, J, V. W for routes which do not form part of the regional networks of ATS routes and are not area navigation routes;(d)Q, T, Y, Z for area navigation routes which do not form part of the regional networks of ATS routes.2.3Where applicable, one supplementary letter shall be added as a prefix to the basic designator in accordance with the following—(a)K to indicate a low-level route established for use primarily by helicopters;(b)U to indicate that the route or portion thereof is established in the upper airspace;(c)S to indicate a route established exclusively for use by supersonic aircraft during acceleration, deceleration and while in supersonic flight.2.4When prescribed by the appropriate ANSP or on the basis of regional a navigation agreements, a supplementary letter may be added after the basic designator air the ATS route in question in order to indicate the type of service provided in accordanc with thefollowirig—(a)the letter F to indicate that on the route or portion thereof advisory service only is provided;(b)the letter G to indicate that on the route or portion thereof flight information service only is provided.Note 1. - Due to limitations in the display equipment on board aircraft, the supplementary letters "F" or "G" may not be displayed to the pilot.Note 2. - Implementation of a route or a portion thereof as controlled route, advisory route or flight information route is indicated in aeronautical charts and aeronautical information publications in accordance with the provisions in these Regulations.3. Assignment of basic designators
3.1Basic ATS route designators shall be assigned in accordance with the following principles.3.1.1The same basic designator shall be assigned to a main trunk route throughout it entire length, irrespective of terminal control areas, States or regions traversed.Note. - This is of particular importance where automated ATS data processing and computerized airborne navigation equipment is used.3.1.2Where two or more trunk routes have a common segment, the segment in question shall be assigned each of the designators of the routes concerned, except where this would present difficulties in the provision of air traffic service, in which case, by common agreement, one designator only shall be assigned.3.1.3A basic designator assigned to one route shall not be assigned to any other route3.1.4States' requirements for designators shall be notified to the Regional Offices of ICAO for coordination.4. Use of designators in communications
4.1In printed communications, the designator shall be expressed at all times by not less than two and not more than six characters.4.2In voice communications, the basic letter of a designator shall be spoken in accordance with the ICAO spelling alphabet.4.3Where the prefixes K,U or S specified 2 .3 are used, they shall, invoice communications, be spoken as follows—K - KOPTER U - UPPERS - SUPERSONICThe word "kopter" shall be pronounced as in the word helicopter" and the words "upper" and "supersonic" as in the English language.4.4Where the letters "F" or "G" specified in 2.4 are used, the flight crew should not be required to use them in voice communications.THIRD SCHEDULE
PRINCIPLES GOVERNING THE IDENTIFICATION OF STANDARD DEPARTURE AND ARRIVAL ROUTES AND ASSOCIATED PROCEDURES
1. Designators for standard departure and arrival routes and associated procedures
Note. —In the following text the term "route" is used in the meaning of "route and associated procedures".1.1The system of designators shall—(a)permit the identification of each route in a simple and unambiguous manner;(b)make a clear distinction between—(i)departure routes and arrival routes;(ii)departure or arrival routes and other ATS routes;(iii)routes requiring navigation by reference to ground based radio aids or self-contained airborne aids, and routes requiring navigation by visual reference to the ground;(c)be compatible with ATS and aircraft data processing and display requirements;(d)be of utmost brevity in its operational application;(f)provide sufficient possibility for extension to cater for any future requirements without the need for fundamental changes.1.2Each route shall be identified by a plain language designator and a corresponding coded designator.1.3The designators shall, in voice communications, be easily recognizable as relating to a standard departure or arrival route and shall not create any difficulties in pronunciation for pilots and ATS personnel.2. Composition of designators
2.1Plain language designator2.1.1The plain language designator of a standard departure or arrival route shall consist of—(a)a basic indicator; followed by(b)a validity indicator; followed by(c)a route indicator, where required; followed by(d)the word "departure" or "arrival"; followed by(e)the word "visual", if the route has been established for use by aircraft operating in accordance with the visual flight rules(VFR).2.1.2The basic indicator shall be the name or name-code of the significant point where a standard departure route terminates or a standard arrival route begins.2.1.3The validity indicator shall be a number from 1 to 9.2.1.4The route indicator shall be one letter of the alphabet. The letters "I" and "0" shall not be used.2.2Coded designatorThe coded designator of a standard departure or arrival route, instrument or visual, shall consist of—(a)the coded designator or name-code of the significant point described in (2.1.1 a) ; followed by(b)the validity indicator in (2.1.1 b);(c)followed by the route indicator in (2.1.1 c), where required.Note. - Limitations in the display equipment on board aircraft may require shortening oft/ic basic indicator, if that indicator is a five-letter name-code, e.g.KODAP. The mnannerin which such an indicator is shortened is left to the discretion of operators.3. Assignment of designators
3.1Each route shall be assigned a separate designator.3.2To distinguish between two or more routes which relate to the same significant point (and therefore are assigned the same basic indicator), a separate route indicator as described in 2.1.4 shall be assigned to each route.4. Assignment of validity indicators
4.1A validity indicator shall be assigned to each route to identify the route which is currently in effect.4.2The first validity indicator to be assigned shall be the number "1".4.3Whenever a route is amended, a new validity indicator, consisting of the next higher number, shall be assigned. The number "9" shall be followed by the number "I"5. Examples of plain language and coded designators
5.1Example 1: Standard departure route —instrument—(a)Plain language BRECONONEdesignator:DEPARTURE(b)Coded designator: BCN I5.1.1 Meaning: The designator identifies a standard instrument departure route which terminates at the significant point BRECON (basic indicator). BRECON is a radio navigation5.2Example 2: Standard arrival route —instrument:| (a) Plain language: | KODAPTWOALPHA | designator: |
| ARRIVAL | | |
| (b) Coded designator: | KODAP 2A | |
5.2.1Meaning: This designator identifies a standard instrument arrival route which begins at the significant point KODAP (basic indicator). KODAP is a significant point not marked by the site of a radio navigation facility and therefore assigned a five-letter name-code in accordance withAppendix 2. The validity indicator TWO (2) signifies that a change has been made from the previous version ONE (l)to the now (2).The route indicator ALPHA identifies one of several routes established with reference to KODAP and is a specific character assigned to this route.5.3Example 3: Standard departure route —visual:| (a) Plain language: | ADOLAFIVEBRAVO | Designator: |
| DEPARTURE VISUAL | | |
| (b) Coded designator: | ADOLA SB | |
5.3.1 Meaning: This designator identifies a standard departure route for controlled VFR flights which terminates at ADOLA, a significant point not marked by the site of a radio navigation facility. The validity indicator FIVE (5) signifies that a change has been made from the previous version FOUR (4) to the now effective version FIVE(S).The route indicator BRAVO(A)identifies one of several routes established with reference to ADOLA.6. Composition of designators for MLS/RNAV approach procedures
6.1Plain language designator6.1.1The plain language designator of an MLS/RNAV approach procedure shall consist of—(b)a basic indicator; followed by(c)a validity indicator; followed by(d)a route indicator; followed by(e)the word"approach"; followed by(f)the designator of the runway for which the procedure is designed.6.1.2The basic indicator shall be the name or name-code of the significant point where the approach procedure begins.6.1.3The validity indicator shall be a number from I to 9.6.1.4The route indicator shall be one letter of the alphabet. The letters "I" and "0" shall not be used.6.1.5The designator of the runway shall be in accordance with the Civil Aviation (Aerodromes Designs and Operations) Regulations, as amended6.2Coded designator6.2.1The coded designator of an MLS/RNAV approach procedure shall consist of(b)the coded designator or name-code of the significant point described in 6.1.1 b);followed by(c)the validity indicator in 6.1.1 c); followed by(d)the route indicator in 6.1.1 d); followed by(e)the runway designator in 6.1.lf).6.3Assignment of designators6.3.1The assignment of designators for MLS!RNAV approach procedures shall be in accordance with paragraph 3. Procedures having identical tracks but different flight profiles shall be assigned separate route indicators.6.3.2The route indicator letter for MLS/RNAV approach procedures shall be assigned uniquely to all approaches at an airport until all the letters have been used. Only then shall the route indicator letter be repeated. The use of the same route indicator for two routes usingthe same MLS ground facility shall not be permitted.6.3.3The assignment of validity indicator for approach procedures shall be in accordance with paragraph 4.6.4Example of plain language and coded designators(a)Plain language MLS HAPPYONEALPHA designator:APPROACHRUN WAY(b)Coded designator: MLS HAPPY 1 AI8LMeaning: The designator identifies an MLS/RNAV approach procedure which begins at the significant point HAPPY (basic indicator). HAPPY is a significant point not marked by the site of a radio navigation facility and therefore assigned a five-letter name-code in accordance with Appendix 2. The validity indicator ONE (I) signifies that either the original version of the route is still in effect or a change has been made from the previous version NINE to the now effective version ONE (I). The route indicator ALPHA (A) identifies one of several routes established with reference to HAPPY and is a specific character assigned to this route.7. Use of designators in communications
7.1In voice communications, only the plain language designator shall be used.Note— For the purpose of identification of routes, the words "departure", "arrival" and "visual" described in 2.1.1 d) and 2.1.1 e) are considered to be an integral elementof the plain language designator.7.2In printed or coded communications, only the coded designator shall be used.8. Display of routes and procedures to air traffic control
8.1A detailed description of each currently effective standard departure or arrival route or approach procedure, including the plain language designator and the coded designator, shall be displayed at the working positions at which the routes or procedures are assigned to aircraft as part of an ATC clearance, or are otherwise of relevance in the provision of air traffic control services.8.2Whenever possible, a graphic portrayal of the routes/ procedures shall also be displayed.FOURTH SCHEDULE
PRINCIPLES GOVERNING THE ESTABLISHMENT AND IDENTIFICATION OF SIGNIFICANT POINTS
1. Establishment of significant points
1.1Significant points should, whenever possible, be established with reference to groundbased or space-based radio navigation aids, preferably VHF or higher frequency aids.1.2Where such ground-based or space-based radio navigation aids do not exist, significant points shall be established at locations which can be determined by self- contained airborne navigation aids, or, where navigation by visual reference to the ground is to be effected, by visual observation. Specific points may be designated as "transfer of control" points by agreement between adjacent air traffic control units or control positions concerned.2. Designators for significant points marked by the site of a radio navigation aid
2.1Plain language name for significant points marked by the site of a radio navigation aid.2.1.1Whenever practicable, significant points shall be named with reference to an identifiable and preferably prominent geographical location.2.1.2In selecting a name for the significant point, care shall be taken to ensure that the following conditions are met—(a)the name shall not create difficulties in pronunciation for pilots or ATS personnel when speaking in the language used in ATS communications. Where the name of a geographical location in the national language selected for designating a significant point gives rise to difficulties in pronunciation, an abbreviated or contracted version of this name, which retains as much of its geographical significance as possible, shall be selected;Example: FUERSTENFELDBRUCK = FURSTY(b)the name shall be easily recognizable in voice communications and shall be free of ambiguity with those of other significant points in the same general area .Inaddition ,the name shall not create confusion with respect to other communications exchanged between air traffic services and pilots;(c)the name should, if possible, consist of at least six letters and form two syllables and preferably not more than three;(d)the selected name shall be the same for both the significant point and the radio navigation aid marking it.2.2Composition of coded designators for significant points marked by the site of a radio navigation aid.2.2.1The coded designator shall be the same as the radio identification of the radio navigation aid. It shall be so composed, if possible, as to facilitate association with the name of the point in plain language.2.2.2Coded designators shall not be duplicated within 1 100 km (600 NM) of the location of the radio navigation aid concerned, except as noted hereunder.Note. - When two radio navigation aids operating in different bands of the frequency spectrum are situated at the same location, their radio identi:fications are normally the same.2.3States' requirements for coded designators shall be notified to the Regional Offices of ICAO for coordination.3. Designators for significant points not marked by the site of a radio navigation aid
3.1Where a significant point is required at a position not marked by the site of a radio navigation aid, and is used for ATC purposes, it shall be designated by a unique five- letter pronounceable "name-code "This name-code designator then serves as the name as well as the coded designator of the significant point.Note. - The principles governing the use of alphanumeric name-codes in support of RNAV SIDs, STARs and instrument approach procedures are detailed in the Civil Aviation (Construction of Visual and instrument Flight Procedures) Regulations as amended3.2The name-code designator shall be selected so as to avoid any difficulties in pronunciation by pilots or ATS personnel when speaking in the language used in ATS communicationsExamples: ADOLA, KODAP3.3The name-code designator shall be easily recognizable invoice communications and shall be free of ambiguity with those used for other significant points in the same general area.3.4The unique five-letter pronounceable name- code designator assigned to a significant point shall not be assigned to any other significant point. When there is a need to relocate a significant point, a new name-code designator shall be chosen. In cases when a State wishes to keep the allocation of specific name-codes for reuse at a different location, such name-codes shall not be used until after a period of at least six months.3.5States' requirements for unique five-letter pronounceable name-code designators shall be notified to the Regional Offices of ICAO for coordination.3.6In areas where no system of fixed routes is established or where the routes followed by aircraft vary depending on operational considerations, significant points shall be determined and reported in terms of World Geodetic System-1984(WGS-84. )geographical coordinates, except that permanently established significant points serving as exit and/or entry points into such areas shall be designated in accordance with the applicable provisions in 2 or 3.4. Use of designators in communications
4.1Normally the name selected in accordance with 2 or 3 shall be used to refer to the significant point in voice communications. If the plain language name for a significant point marked by the site of a radio navigation aid selected in accordance with2.1 is not used, it shall be replaced by the coded designator which, in voice communications, shall be spoken in accordance with the ICAO spelling alphabet.4.2In printed and coded communications, only the coded designator or the selected namecode shall be used to refer to a significant point.5. Significant points used for reporting purposes
5.1In order to permit ATS to obtain information regarding the progress of aircraft in flight, selected significant points may need to be designated as reporting points.5.2In establishing such points, consideration shall be given to the following factors—(a)the type of air traffic services provided;(b)the amount of traffic normally encountered;(c)the accuracy with which aircraft are capable of adhering to the current flight plan;(d)the speed of the aircraft;(e)the separation minima applied;(f)the complexity of the airspace structure;(g)the control methods employed;(h)the start or end of significant phases of a flight (climb, descent, change of direction, etc.);(i)transfer of control procedures;(j)safety and search and rescue aspects:(k)the cockpit and air-ground communication workload.5.3Reporting points shall be established either as "compulsory" or as"on-request".5.4In establishing "compulsory" reporting points the following principles shall apply—(a)compulsory reporting points shall be limited to the minimum necessary for the routine provision of information to air traffic services units on the progress of aircraft inflight, bearing in mind the need to keep cockpit and controller work load and air-ground communications load to a minimum;(b)the availability of a radio navigation aid at a location should not necessarily determine its designation as a compulsory reporting point;(c)compulsory reporting points should not necessarily be established at flight information region or control area boundaries.5.5"On-request" reporting points may be established in relation to the requirements of air traffic services for additional position reports when traffic conditions so demand.5.6The designation of compulsory and on- request reporting points shall be reviewed regularly with a view to keeping the requirements for routine position reporting to the minimum necessary to ensure efficient air traffic services.5.7Routine reporting over compulsory reporting points should not systematically be made mandatory for all flights in all circumstances. In applying this principle, particular attention shall be given to the following—(a)high-speed, high- flying air craft should not be required to make routine position reports over all reporting points established as compulsory for low-speed, low-flying aircraft;(b)aircraft transiting through a terminal control area should not be required to make routine position reports as frequently as arriving and departing aircraft.5.8In areas where the above principles regarding the establishment of reporting points would not be practicable, a reporting system with reference to meridians of longitude or parallels of latitude expressed in whole degrees may be established.FIFTH SCHEDULE
AERONAUTICAL DATA QUALITY REQUIREMENTS
Table 1— Latitude and longitude Note 1. -. Graphical illustrations of obstacle data collection surfaces and criteria used to identi:fy obstacles in the defined areas are illustrated in the Civil Aviation (Aeronautical Information Services) Regulations as amended.Note 2. - in those portions of Area 2 where flight operations are prohibited due to veryhigh terrain or other local restrictions and/or regulations, obstacle data are to be collected in accordance with the Area I numerical requirements specified in the Civil Aviation (Aeronautical Information Services) Regulations as amendedTable 2. Elevation/altitude/height| Elevation Altitude height | Accuracy Data type | integrity classification |
|---|
| Threshold crossing height (Reference datum height)precision approach | 0.5 mCalculated | critical |
| Obstacle clearance altitude height (OCA)H) | as specified in PANS-OPS(Doc 8168) | essential |
| Obstacles in Area 1 (the entire State territtory)elevations | 30 msurveyed | routine |
| Obstacles in Area 2 (the part outside theaerodrome/heliport boundary) | 3msurveyed | essential |
| Distance measuring equipment (DME). elevation | 30 m (100 ft)surveyed | essential |
| Instrument approach procedures altitudes | as specified in PANS-OPS (Doc 8168) | essential |
| Minimum altitudes | 50M claculated | routine |
Table 3: Declination and magnetic variation| Decimination variation | Accuracy Data type | Integrity classification |
|---|
| VHF NAVAID station declination used forTechnical line-up | 1 degree surveyed | essential |
| NDB NAVAID magnetic variatION | 1 degree surveyed | routine |
Table 4. Bearing| Bearing | Accuracy Data Type | Integrity Classification |
|---|
| Airway segments | 110 degreecalculated | routine |
| Bearing used for the formation of an en-route and of a terminal fix | 110 degreecalculated | routine |
| Terminal anival departure route segments | 110 degreecalculated | routine |
| Bearing used for the formation of an instrument approach procedure fix | 110 degreecalculated | essential |
Table 5. length/distance/dimension| Length distance dimension | Accuracy Data type | Integrity classification |
|---|
| Airway segments length | 1 10kmcalculated | routine |
| Distance used for the formation of an en-route fix | 1 10kmcalculated | routine |
| Terminal arrival departure route segments length | 1 10kmcalculated | essential |
| Distance used for the formation of a terminal and instrument approach procedure fix | 1 10kmcalculated | essential |
SIXTH SCHEDULE
RESPONSIBILITIES BY THE AUTHORITY CONCERNING AN INSTRUMENT FLIGHT PROCEDURE DESIGN SERVICE
1. The Air Traffic Service provider shall—(a)provide an instrument flight procedure design service;(b)agree with one or more Air Traffic Service providers to provide a joint service; or(c)delegate the provision of the service to external agencies.2. In all cases in paragraph I above, the Authority concerned shall approve and remain responsible for all instrument flight procedures for aerodromes and airspace under its authority.3. Instrument flight procedures shall be designed in accordance with design criteria approved by the Authority.4. The Authority shall ensure that an instrument flight procedure design service provider intending to design an instrument flight procedure for aerodromes or airspace under its authority meets the requirements established by Authority's regulatory framework.Note.—Guidance material for regulatory framework for the oversight of instrument flight procedure design service is contained in the JCAOManual on the Development of a Regulatory Framework for Instrument Flight Procedure Design Service 5. The Authority shall ensure that an instrument flight procedure design service provider utilizes a quality management system at each stage of the instrument flight procedure design process.Note. - This requirement can be met by means of a qualiti' assurance methodology, such as that described in PANS-uPS (Doc 8168), Volume II, Part I, Section 2, Chapter 4- Quality Assurance. Guidance for implementing such a methodology is contained in The Quality Assurance Manual for Flight Procedure Design (ICAO Doc 9906).//6. The Authority shall ensure that maintenance and periodic review of instrument flight procedures for aerodromes and airspace under its authority are conducted.7. The Authority shall establish an interval for periodic review of instrument flight procedures not exceeding five years.Note. - Guidance on mnaintenance and periodic review is contained in the Quality Assurance 2040SEVENTH SCHEDULE
PRESCRIPTIVE FATIGUE MANAGEMENT REGULATIONS
Note. —Guidance on the development and implimentation of prescriptive fatigue management regularions is contained in the Manual for the Oversight of Fatigue ManagementApproaches (ICAO Doc9966).1. The Authority shall establish prescriptive limitation regulations that take into account acute and cumulative fatigue, circadian factors and the type of work being undertaken. These regulations shall identify—(a)the maximum—(i)number of hours in any duty period;(ii)number of consecutive workdays;(iv)number of hours worked in a defined period; and time-in-position;(b)the minimum—(i)duration of non-duty periods;(ii)number of non-duty days required in a defined period and(ii)duration of breaks between periods of time-in-position in a duty period.2. The Authority shall require the air traffic services provider identifies a process for assigning unscheduled duties that allows air traffic controllers to avoid extended periods of being awake.3. The processes established by the Authority in accordance with Regulation 35(5) c) and d) to allow variations from I a) and b) above shall include the provision of—(a)the reason for the need to deviate;(b)the extent of the deviation;(c)the date and time of enactment of the deviation; and(d)a safety case, outlining mitigations, to support the deviation.EIGHTH SCHEDULE
Note. - Guidance on the development and implementation of FRMS regulations is contained in the Manual for the Oversight of Fatigue Management Approaches (ICAO Doc 9966).The Authority shall require that an FRMS contain, at a minimum—2. FRMS policy and documentation
1.1FRMS policy1.1.1The air traffic services provider shall define its FRMS policy, with all elements of the FRMS clearly identified.(a)define the scope of FRMS operations;(b)reflect the shared responsibility of management, air traffic controllers, and other involved personnel;(c)clearly state the safety objectives of the FRMS;(d)be signed by the accountable executive of the organization;(e)be communicated, with visible endorsement, to all the relevant areas and levels of the organization;(f)declare management commitment to effective safety reporting;(g)declare management commitment to the provision of adequate resources for the FRMS;(h)declare management commitment to continuous improvement of the FRMS;(i)require that clear lines of accountability for management, air traffic controllers, and all other involved personnel are identified; and(j)require periodic reviews to ensure it remains relevant and appropriate.Note. - Effective safert reporting is described in the Safety Management Manual (SMM) (Doc 9859).1.2FRMS documentationAn air traffic services provider shall develop and keep current FRMS documentation that describes and records—(a)FRMS policy and objectives;(b)FRMS processes and procedures;(c)accountabilities, responsibilities and authorities for these processes and procedures;(d)mechanisms for on going involvement of management,air traffic controllers ,an dall other involved personnel;(e)FRMS training programmes, training requirements and attendance records;(f)Scheduled and actual duty and non-duty periods and break periods between times in position in a duty period with significant deviations and reasons for deviations noted; andNote.— Significant deviations are described in the Manual for the Oversight of Fatigue Management Approaches (Doc 9966).(g)FRMS outputs including findings from collected data, recommendations, and actions taken.3. Fatigue risk management processes
2.1identification of fatigue-related hazardsNote.— Provisions on the protection of safety information are contained in the Civil Aviation (Safrtv Management) Regulations as amended.An air traffic services provider shall develop and maintain three fundamental and documented processes for fatigue hazard identification:2.1.1Predictive.The predictive process shall identify fatigue hazards by examining airtraffic controller scheduling and taking into account factors known to affect sleep and fatigue and their effects on performance. Methods of examination may include but are not limited to—(a)air traffic services or industry operational experience and data collected on similar types of operations or from other industries with shift work or 24- houroperations;(b)evidence-based scheduling practices; and(c)bio-mathematical models.(d)Proactive. The proactive process shall identify fatigue hazards within current air traffic services operations. Methods of examination may include but are not limited to:(i)self-reporting of fatigue risks;(iii)relevant air traffic controller performance data;(iv)available safety databases and scientific studies;(v)tracking and analysis of differences in planned and actual worked times; and(vi)observations during normal operations or special evaluations.(e)Reactive There active process shall identify the contribution of fatigue hazards to reports and events associated with potential negative safety consequences in order to determine how the impact of fatigue could have been minimized .At a minimum,the process may be triggered by any of the following—(ii)confidential reports;2.2Fatigue-related risk assessment2.2.1An air traffic services provider shall develop and implement risk assessment procedures that determine when the associated risks require mitigation.2.2.2The risk assessment procedures shall review identified fatigue hazard sand link them to—(a)operational processes;(c)possible consequences; and(d)the effectiveness of existing preventive controls and recovery measures.2.3Risk mitigationAn air traffic services provider shall develop and implement fatigue risk mitigation procedures that—(a)select the appropriate mitigation strategies;(b)implement the mitigation strategies; and(c)monitor the strategies' implementation and effectiveness.2.3FRMS safety assurance processesThe air traffic services provider shall develop and maintain FRMS safety assurance processes to—(a)provide for continuous FRMS performance monitoring, analysis of trends, and measurement(b)to validate the effectiveness of the fatigue safety risk controls. The sources of data may include, but are not limited to- hazard reporting and investigations;audits and surveys; and reviews and fatigue studies (both internal and external);(c)provide a formal process for the management of change .This shall include but is not limited to—(i)identification of changes in the operational environment that may affect the FRMS;(ii)identification of changes within the organization that may affect the FRMS;and(iii)consideration of available tools which could be used to maintain or improve FRMS performance prior to implementing changes; and(d)provide for the continuous improvement of the FRMS. This shall include but is not limited to—(i)the elimination and/or modification of preventive controls and recovery measures that have had unintended consequences or that are no longer needed due to changes in the operational or organizational environment;(ii)routine evaluations of facilities, equipment, documentation and procedures; and(iii)the determination of the need to introduce new processes and procedures to mitigate emerging fatigue-related risks.2.4FRMS promotion processesFRMS promotion processes support the ongoing development of the FRMS, the continuous improvement of its overall performance, and attainment of optimum safety levels. The following shall be established and implemented by the air traffic service provider as part of its FRMS—(a)training programmes to ensure competency commensurate with the roles and responsibilities of management, air traffic controllers, and all other involved personnel under the planned FRMS; and(b)an effective FRMS communication plan that—(i)explains FRMS policies, procedures and responsibilities to all relevant stakeholders;and(ii)describes communication channels used to gather and disseminate FRM S-related information.NINTH SCHEDULE
TRANSFER OF CONTROL
1. DIVISION OF RESPONSIBILITY FOR CONTROL BETWEEN AIR TRAFFIC CONTROL UNITS
1.1.1GeneralThe appropriate ATS authority shall designate the area of responsibility for each air traffic control (ATC) unit and, when applicable, for individual control sectors within an ATC unit. Where there is more than one ATC working position within a unit or sector, the duties and responsibilities of the individual working positions shall be defined.1.1.2Between a unit providing aerodrome control service and a unit providing approach control service1.1.2.1Except for flights which are provided aerodrome control service only, the control of arriving and departing controlled flights shall be divided between units providing aerodrome control service and units providing approach control service as follows:1.1.2.1.1 Arriving aircraft. Control of an arriving aircraft shall be transferred from the unit providing approach control service to the unit providing aerodrome control service when the aircraft—(a)is in the vicinity of the aerodrome, and(i)it is considered that approach and landing will be completed in visual reference to the ground, or(ii)has reached uninterrupted visual meteorological conditions, or(b)is at a prescribed point or level, oras specified in letters of agreement or ATS unit instructions.1.1.2.1.2Transfer of communications to the aerodrome controller should be effected at such a point, level or time that clearance to land or alternative instructions, as well as information on essential local traffic, can be issued in a timely manner.Note - Even though there is an approach control unit, control of certain flights may be transfrrred directly from an ACC to an aerodronie control tower and vice versa, by prior arrangement between the units concerned for the relevant part of approach control service to he provided by the ACC or the aerodrome control tower, as applicable.1.2.1.3 Departing aircraft Control of a departing aircraft shall be transferred from the unit providing aerodrome control service to the unit providing approach control service:(a)when visual meteorological conditions prevail in the vicinity of the aerodrome—(i)prior to the time the aircraft leaves the vicinity of the aerodrome,(ii)prior to the aircraft entering instrument meteorological conditions, or(ii)when the aircraft is at a prescribed point or level, as specified in letters of agreement or ATS unit instructions;(b)when instrument meteorological conditions prevail at the aerodrome:(i)immediately after the aircraft is airborne; or(ii)when the aircraft is at a prescribed point or level, as specified in letters of agreement or local instructions.Note.— See Note following 1.1.2.1.2.1.3 Between a unit providing approach control service and a unit providing area control service1.1.3.1When area control service and approach control service are not provided by the same air traffic control unit, responsibility for controlled flights shall rest with the unit providing area control service except that a unit providing approach control service shall be responsible for the control of—(a)arriving aircraft that have been released to it by the ACC;(b)departing aircraft until such aircraft are released to the ACC.1.1.3.2A unit providing approach control service shall assume control of arriving aircraft, provided such aircraft have been released to it, upon arrival of the aircraft at the point, level or time agreed for transfer of control, and shall maintain control during approach to the aerodrome.1.1.4Between two units providing area control serviceThe responsibility for the control of an aircraft shall be transferred from a unit providing area control service in a control area to the unit providing area control service in an adjacent control area at the time of crossing the common control area boundary as estimated by the ACC having control of the aircraft or at such other point, level or time as has been agreed between the two units.1.1.5 Between control sectors/positions within the same air traffic control unitThe responsibility for the control of an aircraft shall be transferred from one control sector/position to another control sector/position within the same ATC unit at a point, level or time, as specified in local instructions.1.1.6Transfer of control Where an ATS surveillance service is being provided1.1.6.1 Where an ATS surveillance service is being provided, transfer of control should be effected, whenever practicable, so as to enable the uninterrupted provision of the ATS surveillance service.1.1.6.2Where SSR and/or ADS-B and/or MLAT is used and the display of position indications with associated labels is provided for, transfer of control of aircraft between adjacent control positions or between adjacent ATC units may be effected without prior coordination, provided that—(a)updated flight plan information on the aircraft about to be transferred, including the discrete assigned SSR code or, with respect to Mode S and ADS-B, the aircraft identification, is provided to the accepting controller prior to transfer;(b)the ATS surveillance system coverage provided to the accepting controller is such that the aircraft concerned is presented on the situation display before the transfer is effected and is identified on, but preferably before, receipt of the initial call;(c)when the controllers are not physically adjacent, two-way direct speech facilities, which permit communications to be established instantaneously, are available between them at all times;Note. - "Instantaneous" refers to connnunicaticns which effective/v provide for immediate access between controllers.(d)the transfer point or points and all other c*nditions of application, such as direction of flight, specified levels, transfer of communication points, and especially an agreed minimum separation between aircraft, including that applicable to succeeding aircraft on the same route, about to be transferred as observed on the situation display, have been made the subject of specific instructions (for intra-unit transfer) or of a specific letter of agreement between two adjacent ATC units;(e)the instructions or letter of agreement specify explicitly that the application of this type of transfer of control may be terminated at any time by the accepting controller, normally with an agreed advance notice;(f)the accepting controller is informed of any level, speed or vectoring instructions given to the aircraft prior to its transfer and which modify its anticipated flight progress at the point of transfer.1.1.6.3The minimum agreed separation between aircraft about to be transferred (1.1.6.2 d) refers) and the advance notice (1.1.6.2 e) refers) shall be determined taking into account all relevant technical, operational and other circumstances.If circumstances arise in which these agreed conditions can no longer be satisfied, controllers shall revert to the procedure in 1.1.6.4 until the situation is resolved.1.1.6.4Where primary radar is being used, and where another type of ATS surveillance system is employed but the provisions of 1.1.6.2 are not applied, the transfer of control of aircraft between adjacent control positions or between two adjacent ATS units may be effected, provided that—(a)identification has been transferred to or has been established directly by the accepting controller;(b)when the controllers are not physically adjacent, two-way direct-speech facilities between them are at all times available which permit communications to be established instantaneously;(c)separation from other controlled flights conforms to the minima authorized for use during transfer of control between the sectors or units concerned;(d)the accepting controller is informed of any level, speed or vectoring instructions applicable to the aircraft at the point of transfer;(e)radio communication with the aircraft is retained by the transferring controller until the accepting controller has agreed to assume responsibility for providing the ATS surveillance service to the aircraft. Thereafter, the aircraft should be instructed to change over to the appropriate channel and from that point is the responsibility of the accepting controller.1.2Co-ordination of transfer1.2.1Responsibility for control of an aircraft shall not be transferred from one air traffic control unit to another without the consent of the accepting control unit, which shall be obtained in accordance with 1.2.2, 1.2.2.1, 1.2.2.2 and 1.2.3.1.2.2The transferring control unit shall communicate to the accepting control unit the appropriate parts of the current flight plan and any control information pertinent to the transfer requested.1.2.2.1Where transfer of control is to be effected using radar or ADS-B data, the control information pertinent to the transfer shall include information regarding the position and, if required, the track and speed of the aircraft, as observed by radar or ADS-B immediately prior to the transfer.1.2.2.2Where transfer of control is to be effected using ADS-C data, the control information pertinent to the transfer shall include the four-dimensional position and other information as necessary.1.2.3The accepting control unit shall—(a)indicate its ability to accept control of the aircraft on the terms specified by the transferring control unit, unless by prior agreement between the two units concerned, the absence of any such indication is understood to signify acceptance of the terms specified, or indicate any necessary changes thereto; and(b)specify any other information or clearance for a subsequent portion of the flight, which it requires the aircraft to have at the time of transfer.1.2.4The accepting control unit shall notify the transferring control unit when it has established two-way voice and/or data link communications with and assumed control of the aircraft concerned, unless otherwise specified by agreement between the two control units concerned.1.2.5Applicable coordination procedures, including transfer of control points, shall be specified in letters of agreement and ATS unit instructions as appropriate.