If you wish to contribute or participate in the discussions about articles you are invited to join SKYbrary as a registered user

Stress

From SKYbrary Wiki
Revision as of 18:01, 25 May 2016 by Editor2 (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Article Information
Category: Human Behaviour Human Behaviour
Content source: SKYbrary About SKYbrary
Content control: SKYbrary About SKYbrary

Description

Stress is a bodily response to a stimulus that disturbs or interferes with the “normal” physiological equilibrium of a person and, in the context of aviation, refers to a state of physical, mental or emotional strain due to some external or internal stimulus.

Understanding the factors that lead to stress, as well as how to cope with stressful situations, can greatly improve a individual's performance. Also, understanding that colleagues may react differently to the same stressor is important and can help you control a situation that can quickly get out of hand if an individual is having a negative reaction.

Accidents & Incidents

Events on the SKYbrary database which list stress as a significant contributory factor:

  • SF34, en-route, near Caltrauna Argentina, 2011 (On 18 May 2011, a Saab 340 crew attempted to continue a climb to their intended cruising level in significant airframe icing conditions at night before belatedly abandoning the attempt and descending to a lower level but one where their aircraft was nevertheless still rapidly accumulating ice. They were unable to recover control after it stalled and a crash into terrain below followed. The Investigation attributed the accident to lack of crew understanding of the importance of both the detection of and timely and appropriate response to both significant rates of airframe ice accumulation and indications of an impending aerodynamic stall.)
  • B735, vicinity Kazan Russia, 2013 (On 17 November 2013, the crew of a Boeing 737-500 failed to establish on the ILS at Kazan after not following the promulgated intermediate approach track due to late awareness of LNAV map shift. A go around was eventually initiated from the unstabilised approach but the crew appeared not to recognise that the autopilot used to fly the approach would automatically disconnect. Non-control followed by inappropriate control led to a high speed descent into terrain less than a minute after go around commencement. The Investigation found that the pilots had not received appropriate training for all-engine go arounds or upset recovery.)
  • FA20, vicinity Narsarsuaq Greenland, 2001 (On 5 August 2001, a Dassault Falcon 20 with an inoperative GPWS making a night approach to Narsarsuaq by visual reference impacted terrain 4.5 nm from the aerodrome. The Investigation noted the original crew intention to fly a non-precision instrument approach and attributed the accident to the failure of the crew to follow applicable procedures or engage in meaningful CRM as well as to deficiencies in the Operator's required procedures which had combined to leave the crew vulnerable to a 'black hole' effect. The effects of fatigue were considered likely to have been contributory.)
  • A320, vicinity Oslo Norway, 2008 (On 19 December 2008, an Aeroflot Airbus A320 descended significantly below its cleared and acknowledged altitude after the crew lost situational awareness at night whilst attempting to establish on the ILS at Oslo from an extreme intercept track after a late runway change and an unchallenged incorrect readback. The Investigation concluded that the response to the EGPWS warning which resulted had been “late and slow” but that the risk of CFIT was “present but not imminent”. The context for the event was considered to have been poor communications between ATC and the aircraft in respect of changes of landing runway.)
  • A320, vicinity Sochi Russia, 2006 (On 3 May 2006, an Airbus 320 crew failed to correctly fly a night IMC go around at Sochi and the aircraft crashed into the sea and was destroyed. The Investigation found that the crew failed to reconfigure the aircraft for the go around and, after having difficulties with the performance of an auto go-around, had disconnected the autopilot. Inappropriate control inputs, including simultaneous (summed) sidestick inputs by both pilots were followed by an EGPWS PULL UP Warning. There was no recovery and about a minute into the go around, a steep descent into the sea at 285 knots occurred.)
  • … further results

Related Articles

Related OGHFA Situational Examples

Situational Example Flight Phase
De-icing and Latent Organisational Factors (OGHFA SE) Take Off
Disorientation During Vectored Go-Around (OGHFA SE) Missed Approach
Fuel Leak and Confirmation Bias (OGHFA SE) Climb, Cruise, Descent
Fuel Starvation, Stress, Fatigue and Nonstandard Phraseology (OGHFA SE) Cruise, Descent
Landing Gear Failure (OGHFA SE) Landing
Takeoff Weight Entry Error and Fatigue (OGHFA SE) Take Off
Unidentified Fire On Board (OGHFA SE) Cruise, Descent, Landing

Related OGHFA Material

Further Reading

EUROCONTROL

Others