Назад

Fatigue Risk Management for Pilots and Controllers

TELCAP aviation English topic about fatigue, circadian rhythms, duty limits, reporting and operational risk management.

Fatigue as an operational hazard

This topic supports TELCAP speaking practice. It is not a confirmed list item for a 2026 examination. Fatigue is a physiological state that reduces mental or physical performance. In aviation it can slow reaction, weaken attention, impair memory and make decision-making less flexible.

Pilots and air traffic controllers work around the clock. Night duties, early starts, time-zone changes and irregular schedules can conflict with the body’s normal sleep rhythm. A person may be legally within a duty limit and still experience significant fatigue because of poor sleep, illness, personal stress or several demanding duties in sequence.

Fatigue should therefore be managed as a safety risk, not treated only as an individual failure to sleep enough.

Sleep pressure and circadian rhythm

Two biological processes influence alertness. Sleep pressure grows during time awake and reduces after sufficient sleep. The circadian rhythm creates daily periods of higher and lower alertness. The lowest alertness commonly occurs during the biological night, even when a person slept before duty.

An overnight flight or control shift can therefore be difficult for two reasons: the person has been awake for many hours and the body is promoting sleep. Crossing time zones creates further misalignment because local time and biological time differ.

Short sleep opportunities do not always provide full recovery. Noise, unfamiliar accommodation and the need to travel between work and rest reduce effective sleep time.

Effects on performance

Fatigue can produce missed radio calls, incomplete checklists, calculation errors and slow recognition of a changing situation. A tired person may focus on one task and fail to monitor the wider picture.

Communication can become shorter but less precise. Pilots may accept a clearance without checking whether it matches the flight plan. Controllers may overlook an incorrect readback or delay coordination. Memory lapses can cause a task to be started but not completed.

One dangerous feature is that people do not always assess their own impairment accurately. Confidence may remain high while performance has already declined.

Prescriptive limits

Duty-time and rest rules create a basic protective framework. They limit how long personnel may work and define minimum rest. These limits are necessary, but they cannot represent every operational condition.

The same duty length may create different risk depending on start time, previous sleep, workload and number of sectors. A delayed flight can move a duty into a more difficult circadian period. A controller may face an unexpected traffic surge near the end of a shift.

Operators must not use maximum legal limits as normal planning targets for every schedule. A compliant roster can still produce repeated fatigue reports.

Fatigue Risk Management Systems

A Fatigue Risk Management System, or FRMS, uses operational data and scientific principles to identify and control fatigue risk. It can include roster analysis, fatigue reports, sleep studies, scheduling rules, education and monitoring of safety events.

FRMS does not remove personal responsibility. Personnel should use rest opportunities and report when they are unfit. At the same time, an organisation must provide realistic schedules and avoid blaming individuals for predictable fatigue created by the system.

Data should be reviewed for patterns. Repeated reports on one duty sequence may show that the schedule needs modification. A single report may not prove a general problem, but it should still receive a fair operational assessment.

Reporting fatigue

Personnel need a clear method to report fatigue before, during and after duty. A report should describe sleep obtained, duty timing, workload and observed performance effects. Medical or private details should be protected appropriately.

Fear of punishment discourages reporting and hides risk. A just culture distinguishes between honest fatigue disclosure and deliberate misuse of the system. Managers should investigate the schedule and conditions rather than assume weak motivation.

If a pilot or controller believes performance is unsafe, early notification gives the organisation more options. A replacement, delayed report time or additional break may be possible before operations are affected.

Operational mitigations

Mitigations include protected rest, controlled rest where approved, strategic breaks, workload sharing and schedule changes. Bright light, caffeine and activity can temporarily improve alertness, but they do not replace sleep.

In the cockpit, clear task sharing and strict checklist use become especially important during circadian lows. Crews can verbalise threats during the briefing and monitor each other for missed actions.

In air traffic control, sector opening, traffic restrictions or relief by another controller may reduce workload. A fatigued controller should not be left alone with increasing complexity because traffic numbers initially appear low.

Commuting and personal factors

Rest rules usually protect time away from duty, but personnel also spend time commuting, eating and managing family responsibilities. A long commute can reduce actual sleep. Individuals should consider this when choosing travel arrangements.

Alcohol, some medicines, illness and sleep disorders can worsen fatigue. Persistent excessive sleepiness requires medical assessment. Education should explain these factors without encouraging self-diagnosis.

Healthy sleep habits support recovery: a dark quiet room, consistent routines where possible and reduced interruption. However, personal techniques cannot compensate indefinitely for a poor roster.

Communication during a fatigue-related problem

If fatigue affects operational capability, communication should be direct. A pilot can state “unable due crew fatigue” when a further duty extension is unsafe. A controller can request relief before performance deteriorates.

Managers may face commercial pressure, but safety decisions require realistic alternatives. Continuing an operation with an impaired crew can create far greater disruption than an early delay or cancellation.

After an event, investigators should consider fatigue alongside training, equipment, procedures and workload. It should not be used as a convenient explanation without evidence.

Building a healthy safety culture

Effective fatigue management combines rules, science, operational data and personal responsibility. Success is not measured by zero fatigue reports. A reporting system that produces no reports may indicate fear or disbelief rather than perfect schedules.

Pilots and controllers need enough vocabulary to explain how fatigue developed, what performance effects occurred and which mitigation would help. Professional discussion avoids moral judgement and concentrates on measurable operational risk.

Key vocabulary

  • fatigue — reduced performance caused by insufficient rest or prolonged activity
  • circadian rhythm — biological cycle influencing sleep and alertness
  • sleep pressure — increasing need for sleep during time awake
  • duty limit — maximum permitted period of work
  • rest period — protected time intended for recovery
  • fatigue risk management system (FRMS) — data-based system for controlling fatigue risk
  • controlled rest — planned short sleep under an approved procedure
  • circadian low — period of naturally reduced alertness
  • fitness for duty — ability to perform work safely
  • just culture — fair treatment encouraging safety reporting

Discussion questions

  1. Why can a legal duty still create unsafe fatigue?
  2. What information should be included in a fatigue report?
  3. How does fatigue affect pilot-controller communication?
  4. Which mitigations improve alertness but do not replace sleep?
  5. Why might zero fatigue reports be a warning sign?
  6. How should an organisation respond to repeated reports about one roster?

Sources and further reading