If you wish to contribute or participate in the discussions about articles you are invited to join SKYbrary as a registered user
Fatigue is the general term used to describe physical and/or mental weariness which extends beyond normal tiredness.
Physical fatigue concerns the inability to exert force with ones muscles to the degree that would be expected. It may be an overall tiredness of the whole body, or be confined to particular muscle groups. Physical fatigue most commonly results from physical exercise or loss of sleep. Physical fatigue often leads to mental fatigue.
Mental fatigue, which may include sleepiness, concerns a general decrease of attention and ability to perform complex, or even quite simple tasks with customary efficiency. Mental fatigue often results from loss or interruption of the normal sleep pattern and is therefore of great concern to pilots and ATCOs, who are frequently required to work early in the morning or at night.
Sleep patterns are naturally associated with the body's circadian rhythms. Shift patterns and transit across time zones can interrupt circadian rhythms so that, for example, it may be difficult for flight crew or pilots on duty in the early hours of the morning or flight crew operating long-haul routes through multiple time zones to achieve satisfactory rest prior to commencing duty.
It is important to note that people are not the best evaluators of their own alertness state. They are often sleepier than they report.
There are three types of fatigue: transient, cumulative, and circadian:
- Transient fatigue is acute fatigue brought on by extreme sleep restriction or extended hours awake within 1 or 2 days.
- Cumulative fatigue is fatigue brought on by repeated mild sleep restriction or extended hours awake across a series of days.
- Circadian fatigue refers to the reduced performance during nighttime hours, particularly during an individual’s “window of circadian low” (WOCL) (typically between 2:00 a.m. and 05:59 a.m.).
Researches show that the accumulation of "sleep debt", e.g. by having an hour less of sleep for several consecutive days needs a series of days with more-than-usual sleep for a person to fully recover from cumulative fatigue.
Fatigue usually results in impaired standards of operation with increased likeliness of error. For example:
- Increased reaction time;
- Reduced attentiveness;
- Impaired memory; and,
- Withdrawn mood.
In a pilot, fatigue may manifest itself by:
- Inaccurate flying;
- Missed radio calls;
- Symptoms of equipment malfunctions being missed;
- Routine tasks being performed inaccurately or even forgotten; and, in extreme cases,
- Falling asleep - either a short "micro-sleep" or for a longer period.
In an ATCO, fatigue may result in:
- Poor decision making;
- Slow reaction to changing situation;
- Failure to notice an impending confliction;
- Loss of situational awareness;
- Circadian adaptation, i.e. adjustment of the body internal clock (e.g. due to the shift pattern, jet lag, etc.)
- Length of previous rest period;
- Time on duty;
- Time awake prior to duty (duties that start in the evening are more likely to cause fatigue than those beginning at e.g. 8 a.m.)
- Sleep/nap opportunities (during the duty but also at layover destinations)
- Physical conditions (temperature, airlessness, noise, comfort, etc.);
- Workload (high or low);
- Emotional stress (in family life or at work);
- Lifestyle (including sleeping, eating, drinking and smoking habits) and fitness; and,
- Ensure that work schedules, including consecutive shift-working patterns, are constructed so as to have the least possible impact on off duty - and, if applicable, on duty rest.
- Seek to provide optimum working conditions;
- Use Crew Resource Management or Team Resource Management training to promote awareness to fatigue and sleep issues.
- Establish a Fatigue Risk Management System (FRMS), either as a part of the Safety Management System (SMS) or as a standalone system. An effective FRMS is data-driven and routinely collects and analyzes information and reports related to crew alertness as well as operational flight performance data. Computer models can be used to predict average performance capability from sleep/wake history and normal circadian rhythms.
Pilots and ATCOs
Adopt personal strategies which are likely to decrease the effects of fatigue such as the following:
- Planning activities, meals, rest and sleep patterns during off-duty periods;
- Making the most of permitted rest breaks, including naps;
- Advising colleagues if one detects feeling drowsy;
- Alerting colleagues if they appear to be becoming drowsy.
- Pilot Workload
- Controller Workload
- Fatigue Management: Guidance for Air Traffic Controllers and Air Traffic Engineers
Accidents & Incidents
Events in the SKYbrary database which include fatigue as a contributory factor:
- H25B, vicinity Akron OH USA, 2015 (On 10 November 2015, the crew of an HS 125 lost control of their aircraft during an unstabilised non-precision approach to Akron when descent was continued below Minimum Descent Altitude without the prescribed visual reference. The airspeed decayed significantly below minimum safe so that a low level aerodynamic stall resulted from which recovery was not achieved. All nine occupants died when it hit an apartment block but nobody on the ground was injured. The Investigation faulted crew flight management and its context - a dysfunctional Operator and inadequate FAA oversight of both its pilot training programme and flight operations.)
- A306, vicinity Birmingham AL USA, 2013 (On 14 August 2013, a UPS Airbus A300-600 crashed short of the runway at Birmingham Alabama on a night IMC non-precision approach after the crew failed to go around at 1000ft aal when unstabilised and then continued descent below MDA until terrain impact. The Investigation attributed the accident to the individually poor performance of both pilots, to performance deficiencies previously-exhibited in recurrent training by the Captain and to the First Officer's failure to call in fatigued and unfit to fly after mis-managing her off duty time. A Video was produced by NTSB to further highlight human factors aspects.)
- B772, San Francisco CA USA, 2013 (On 6 July 2013, an Asiana Boeing 777-200 descended below the visual glidepath on short finals at San Francisco after the pilots failed to notice that their actions had reduced thrust to idle. Upon late recognition that the aircraft was too low and slow, they were unable to recover before the aircraft hit the sea wall and the tail detached. Control was lost and the fuselage eventually hit the ground. A few occupants were ejected at impact but most managed to evacuate subsequently and before fire took hold. The Probable Cause of the accident was determined to be the mismanagement of the aircraft by the pilots.)
- A319, London Heathrow UK, 2013 (On 24 May 2013 the fan cowl doors on both engines of an Airbus A319 detached as it took off from London Heathrow. Their un-latched status after a routine maintenance input had gone undetected. Extensive structural and system damage resulted and a fire which could not be extinguished until the aircraft was back on the ground began in one engine. Many previously-recorded cases of fan cowl door loss were noted but none involving such significant collateral damage. Safety Recommendations were made on aircraft type certification in general, A320-family aircraft modification, maintenance fatigue risk management and aircrew procedures and training.)
- Vehicles / B722, Hamilton ON Canada, 2013 (On 19 March 2013 a Boeing 727 freighter was cleared to take off on a runway occupied by two snow clearance vehicles. The subsequent cancellation of the take off clearance was not received but a successful high speed rejected take off was accomplished on sight of the vehicles before their position was reached. The Investigation attributed the occurrence to the controller's failure to 'notice' the runway blocked indicator on his display and to his non-standard use of R/T communications. The late sighting of the vehicles by the aircraft crew was due to the elevated runway mid section.)
- A321, Hurghada Egypt, 2013 (On 28 February 2013, the initial night landing attempt of a Ural Airlines Airbus A321 at Hurghada was mishandled in benign conditions resulting in a tail strike due to over-rotation. The Investigation noted that a stabilised approach had been flown by the First Officer but found that the prescribed recovery from the effects of a misjudged touchdown had not then been followed. It was also concluded that communication between the two pilots had been poor and that the aircraft commander's monitoring role had been ineffective. The possibility of the effects of fatigue was noted.)
- B738, en-route, south south west of Brisbane Australia, 2013 (On 25 February 2013, a Boeing 737-800 about to commence descent from FL390 began to climb. By the time the crew recognised the cause and began to correct the deviation - their unintended selection of a inappropriate mode - the cleared level had been exceeded by 900 feet. During the recovery, a deviation from track occurred because the crew believed the autopilot had been re-engaged when it had not. The Investigation noted the failure to detect either error until flight path deviation occurred and attributed this to non-compliance with various operator procedures related to checking and confirmation of crew actions.)
- SW4, Sanikiluaq Nunavut Canada, 2012 (On 22 December 2012, the crew of a Swearingen SA227 attempting a landing, following an unstabilised non-precision approach at Sanikiluaq at night with questionable alternate availability in marginal weather conditions, ignored GPWS PULL UP Warnings, then failed in their attempt to transition into a low go around and the aircraft crashed into terrain beyond the runway. One occupant – an unrestrained infant – was killed and the aircraft was destroyed. The Investigation faulted crew performance, the operator and the regulator and reiterated that lap-held infants were vulnerable in crash impacts.)
- SF34, vicinity Newcastle New South Wales Australia, 2012 (On 8 November 2012, the crew of a Saab 340 advised destination ATC at Newcastle in daylight hours that they were 'visual' and were so cleared. The aircraft was then observed to turn towards the lights of an industrial complex 6nm from the airport and descend and ATC intervened to provide guidance to final approach. Investigation found that the experienced Captain was guiding the First Officer, who had gained his professional licence 10 months earlier, towards what he had mistaken for the runway. Descent, perceived by the Captain as on 'finals', continued to 680 feet agl before a climb commenced.)
- CRJ7, Lorient France, 2012 (On 16 October 2012, a Brit Air Bombardier CRJ 700 landed long on a wet runway at Lorient and overran the runway. The aircraft sustained significant damage but none of the occupants were injured. The Investigation attributed the accident to poor decision making by the crew whilst shoeing signs of complacency and fatigue and failing to maintain a sterile flight deck or go around when the approach became unstable. A context of deficiencies at the airport and at the Operator was also detailed and it was concluded that aquaplaning had occurred.)
- DH8C, vicinity Abu Dhabi UAE, 2012 (On 9 September 2012, the crew of a DHC8-300 climbing out of Abu Dhabi declared a PAN and returned after visual evidence of the right engine overheating were seen from the passenger cabin. The Investigation found that the observed signs of engine distress were due to hot gas exiting through the cavity left by non-replacement of one of the two sets of igniters on the engine after a pressure wash carried out overnight prior to the flight and that the left engine was similarly affected. The context for the error was identified as a dysfunctional maintenance organisation at the Operator.)
- C500, vicinity Santiago Spain, 2012 (On 2 August 2012, a Cessna 500 positioning back to base after completing an emergency medical team transfer operation earlier in the night crashed one mile short of the runway at Santiago in landing configuration after being cleared to make an ILS approach. The Investigation concluded that the approach was unstabilised, had been flown without following the ILS GS and that the crew had used DME distance from the VOR near the crash position rather than the ILS DME. Fog was present in and around the airport.)
- … further results
- Fatigue and Sleep Management Brochure;
- Personal Strategies for Decreasing the Effects of Fatigue in Air Traffic Control;
- Aircrew Fatigue: A Review of Research Undertaken on Behalf of the UK Civil Aviation Authority.
- EASA Flight Time Limitations (FTL) - Q&A, Aug 2015.
- Advisory Circular 120-100: Basics of Aviation Fatigue, June 2010
- FAA Advisory Circular 117-3: Fitness for Duty, October 2012
- IATA Fatigue Risk Management Guide for Airline Operators, 2nd edition, 2015
- Fighting Pilot Fatigue, video by Boeing’s Fatigue Risk Management team in partnership with Delta airlines to portray the effects of fatigue on pilots. It describes technologies in the flight deck that can monitor and prevent fatigue-related events.
- Operator's Manual: Human Factors in Aviation Maintenance, FAA, 2014.
- Safety Behaviours: Human Factors Resource Guide for Engineers, CASA (Australia), 2013. Chapter 5 describes the causes and impacts of fatigue, and strategies to manage it (for maintenance personnel).
- Human Performance and Fatigue Research for Controllers, Gawron et al., 2011.
- FAA Fact Sheet – Sleep Apnea in Aviation, Feb 2015.
- Coping with long range flying. Recommendations for crew rest and alertness., Airbus, Cabon, P., et al., Nov 1995.
- Fatigue and Alertness Management in Aviation
- Being Prepared for the Outbound Flight - Checklist
- Being Prepared for the Return Flight in Eastward Rotations - Checklist
- Being Prepared for the Return Flight in North and South Rotations - Checklist
- Being Prepared for the Return Flight in Westward Rotations - Checklist