One common definition of CRM can be expressed as the effective management of all available resources available to the operators; including software, hardware and liveware, to achieve the goal of safe flight operations (Jenson, 1995).
Recognition of crew resource management (CRM) is relatively new. This statement is true in comparison to the centenary history of aviation, whereby crew resource management strategies were intentionally implemented and widely accepted just short of thirty years ago, at the onset of the 1980’s
Unfortunately, accumulating events of disastrous air crashes (predominantly in the mid-1960's and 1970's) resulting from primary causes including poor pilot management and the lack of utilising multiple resources available to the crew. These particular causes or insufficiencies consequently served as ''triggers'', bringing to attention the realising significance of CRM, and its need for application in flight crew practices (Murray, n.d.).
Eastern Airlines Flight 401, Everglades (Florida):
Although there are several instances of past aviation accidents which have enhanced the idea of introducing CRM in aircrew operations (i.e. Tenerife 1977 or Portland, Oregano's DC-8 crash in 1978), this discussion will focus on only one key example, namely, the