Skip to content
SkyRosterBook a working session

Regulation · ICAO

The manual behind every state's fatigue rule

Annex 11 tells states to regulate air traffic controller fatigue. It does not tell them how. Doc 9966 is the ICAO manual written to fill that gap: it explains the two ways a state can structure the rule, and what each one obliges the ANSP to do. Here is what it actually covers, and where a European ANSP's own obligation, ATS.OR.320, comes from it.

The document, and what sits around it

Full title
Manual for the Oversight of Fatigue Management Approaches
Reference
ICAO Doc 9966
Publisher
ICAO
Read alongside
Fatigue Management Guide for Air Traffic Service Providers (CANSO/ICAO/IFATCA)
Underlying standard
ICAO Annex 11 to the Convention on International Civil Aviation, Air Traffic Services, 15th Edition (July 2018), §2.28, Appendix 5, Appendix 6

Doc 9966 is one manual in a family that ICAO built around a single set of scientific principles: a guide for airline operators (Annex 6, Part I), a guide for general-aviation operators of large aeroplanes (Annex 6, Part II), and, for air traffic services, the Fatigue Management Guide for Air Traffic Service Providers (CANSO/ICAO/IFATCA), which states explicitly that it "is designed to be read in association with" Doc 9966.

The choice Annex 11 sets up

Two tracks, one binding standard

The binding text is not Doc 9966 itself, it is Annex 11. Doc 9966 is the guidance ICAO points regulators to when they apply it. Annex 11's own notes send the reader to Doc 9966 three separate times: once for fatigue regulations in general, once for the prescriptive limits in Appendix 5, and once for the FRMS requirements in Appendix 6.

2.28.1 States shall establish regulations for the purpose of managing fatigue in the provision of air traffic control services. These regulations shall be based upon scientific principles, knowledge and operational experience, with the aim of ensuring that air traffic controllers perform at an adequate level of alertness. To that aim, States shall establish:

  1. regulations that prescribe scheduling limits in accordance with Appendix 5; and
  2. where authorizing air traffic services providers to use a fatigue risk management system (FRMS) to manage fatigue, FRMS regulations in accordance with Appendix 6.

2.28.2 States shall require that the air traffic services provider, for the purposes of managing its fatigue-related safety risks, establish one of the following: air traffic controller schedules commensurate with the service(s) provided and in compliance with the prescriptive limitation regulations; or an FRMS, in compliance with regulations established by the State, for all or a defined part of its air traffic control services.

§2.28.1–2.28.2, ICAO Annex 11 to the Convention on International Civil Aviation, Air Traffic Services, 15th Edition (July 2018)

The Fatigue Management Guide for Air Traffic Service Providers (CANSO/ICAO/IFATCA) calls these two tracks the prescriptive approach and the FRMS approach · the second is ICAO's performance-based alternative to a fixed table of numbers, evaluated by the outcome the provider can demonstrate rather than by a checklist of limits. It states the distinction plainly:

"FRMS is a special type of safety management system focused on managing the actual fatigue risk in the operations to which it applies (rather than addressing fatigue risk in general, which is the basis of prescriptive limits)."

§1.1.1, Fatigue Management Guide for Air Traffic Service Providers (CANSO/ICAO/IFATCA), p.15

Having an FRMS does not remove the numbers, it changes who sets them and how they are justified: "Having an FRMS still requires having maximum duty times and minimum non-work periods, but these are proposed by the ATS Provider and must be approved by the regulator." Fatigue Management Guide for Air Traffic Service Providers (CANSO/ICAO/IFATCA), §1.1.1, p.15

What changesPrescriptive approachFRMS approach
AimATS Provider manages fatigue risks within the constraints of prescribed limits, using existing SMS processes.ATS Provider identifies its own limits, manages fatigue risks within agreed safety objectives and targets, and monitors them through FRMS processes that may change as experience accumulates.
Where the limits come fromRegulator sets the regulations for prescriptive limits; the limits are outer limits, not targets.ATS Provider identifies maximum work periods and minimum non-work periods for each covered operation; the regulator reviews and approves them.
How fatigue hazards are foundMainly reactive: data collected through existing safety reporting mechanisms, after the fact.Reactive, proactive and predictive processes developed and implemented specifically for FRMS.
Safety assuranceRegulator reviews compliance with the prescriptive limits and the scientific basis of scheduling practice.Regulator reviews and agrees ATS-Provider-identified Safety Performance Indicators, and may require adjustment of the Provider's own limits.

Fatigue Management Guide for Air Traffic Service Providers (CANSO/ICAO/IFATCA), Table 1-1, pp.16–17

What the standard actually requires

Categories, not numbers

Appendix 5 is the text ATS.OR.320 was built to satisfy. Read it and the resemblance to the EU article is not a coincidence, but notice what it does and does not contain.

States 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:

  1. number of hours in any duty period;
  2. number of consecutive work days;
  3. number of hours worked in a defined period; and
  4. time-in-position;

(b) the minimum:

  1. duration of non-duty periods;
  2. number of non-duty days required in a defined period; and
  3. duration of breaks between periods of time-in-position in a duty period.
Appendix 5, §1, ICAO Annex 11 to the Convention on International Civil Aviation, Air Traffic Services, 15th Edition (July 2018)

Seven categories, not seven numbers. Nowhere in Appendix 5 does ICAO write a figure, that is left entirely to the state, the same way ATS.OR.320(a) leaves it to the ANSP. Appendix 5 also requires a documented process for unscheduled duties, "to allow air traffic controllers to avoid extended periods of being awake" Appendix 5, §2, ICAO Annex 11 to the Convention on International Civil Aviation, Air Traffic Services, 15th Edition (July 2018) · the standard's way of covering on-call and standby, which ATS.OR.320's eight elements do not name separately.

Variations, not a second system

A deviation is an exception you have to document, not a fallback rule

Annex 11 lets a State allow variations from its own prescriptive limits, but only for genuinely exceptional circumstances, and only with a documented basis:

"3. The processes established by States … to allow variations from 1 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."

Appendix 5, §3, ICAO Annex 11 to the Convention on International Civil Aviation, Air Traffic Services, 15th Edition (July 2018)

The Fatigue Management Guide for Air Traffic Service Providers (CANSO/ICAO/IFATCA) is explicit that this is not meant to become a second, informal limitation system: "The intent of the ICAO provision is to minimize, not to encourage 'regulation through variations'. It is not intended to offer a quick and easy alternative to an FRMS, when a more comprehensive fatigue risk management approach is required." Fatigue Management Guide for Air Traffic Service Providers (CANSO/ICAO/IFATCA), §4.2

Where the European rule points back to it

ATS.OR.320's own guidance material names Doc 9966 directly

This is not an inference. EASA's own study of the fatigue provisions states it plainly, describing the Guidance Material published alongside ATS.OR.300, ATS.OR.315 and ATS.OR.320:

"In the Guidance Material, reference is made to ICAO Doc 9966 'Manual for the Oversight of Fatigue Management Approaches' (ICAO, 2016), 'EUROCONTROL Study on Shiftwork practices – ATM and related Industries' (EUROCONTROL, 2006) and 'Fatigue and Sleep Management: Personal strategies for decreasing the effects of fatigue in air traffic control' (EUROCONTROL, 2005). Apart from the three documents referred to as Guidance Material, additional supporting material is available including 'Fatigue Management Guide for Air Traffic Service Providers' published by CANSO, ICAO and IFATCA (2016) and CAP 670 Air Traffic Services Safety Requirements published by the CAA UK (2019)."

EASA, Study on the Analysis, Prevention and Management of Air Traffic Controller Fatigue (D-4.C.1), May 2024, p.99

The UK CAA makes the same connection from its own side of the Channel: "ICAO Doc 9966 'Manual for the Oversight of Fatigue Management Approaches', and in particular the 'Fatigue Management Guide for Air Traffic Service Providers' provide useful insights into the critical elements contributing to ATCO fatigue as well as guidance on fatigue management approaches supported by ICAO Standards and Recommended Practices." CAA Policy on Air Traffic Controllers’ Rostering System(s), 2 September 2021, §1.5

In practice: ICAO's Annex 11 sets the two-track choice and the categories; Doc 9966 and its ATS-specific companion explain how to run either track; EASA's ATS.OR.320 and the UK's retained equivalent are how the choice was actually transposed into a rule an ANSP has to satisfy.

Whichever track your regulator chose, the roster still has to be built.

Prescriptive limits or an approved FRMS, SkyRoster enforces the values you configure, not a fixed table of its own. Bring your regulator's numbers and we will show you the rules they become.