Professional Documents
Culture Documents
HUMAN FACTORS IN
AVIATION
BY P MAHERE
A good day, or a bad day at the office …
Depending on your perspective
A good day at the office!
Glossary of Terms
(FITTING THE MAN TO THE JOB AND THE JOB TO THE MAN)
INTRODUCTION TO HF.
Human factors
• This chapter examines the relationship
between human factors and incidents largely
in terms of human error and “ Murphy’s Law”
(i.e. if it can happen, one day it will).
• It is best known in the context of aircraft
cockpit design and Crew Resource
Management (CRM)
• Or ergonomics
• It can be described as fitting the man to the
job and the job to the man.
Its attributes
• Human physiology, psychology (including
perception, cognition, memory, social
interaction, error, etc.);
• Work place design
• Environmental conditions
• Human machine interface
• Anthropometrics (the scientific study of
measurements of the human body)
Who does Human Factors?
• Multi-Disciplinary HF Specialists
• Some:
1. Psychologists
2. Engineers
3. Doctors
4. Kinesiologists
5. Retrained Subject Matter Experts … Yes, it is
possible to retrain engineers (pilots and doctors)
6. Scientists
HF’s contribution to Aviation
accidents (IATA 1975)
70%
Flight crew, ATC,
Aircraft design,
Maintenance human failure, etc
1986 study of accident causes.
Cause/major contributory factor % of accidents
1. Pilot deviated from basic operational procedures 33
2. Inadequate cross-check by second crew member 26
3. Design faults 13
4. Maintenance & inspection deficiencies 12
5. Absence of approach guidance 10
6. Captain ignored crew inputs 10
7. Air traffic control failures or errors 9
8. Improper crew response during abnormal conditions 9
9. Insufficient or incorrect weather information 8
10. Runaways hazards 7
11. ATC/crew communication deficiencies 6
12. Improper decision to land 6
13. It is apparent that maintenance & inspection deficiencies are a major contributory factor
to accidents , hence the need for human factors training for maintenance personnel.
Goal of human factors training
• To provide practical Human factors guidance
based on issues concerned with aircraft
maintenance and inspection.
• To show how human capabilities and
limitations can influence task performance
and safety within the maintenance and
inspection environments
What is not Human Factors?
• “Just applied common sense”
• Training people to accommodate poor design
• Blaming the user - “Pilot error”
• Designers projecting their skills onto users - If
it’s easy for the designer it must be easy for
the end user
• Human Resources
THE ICAO SHELL MODEL
Origins
It can be helpful to use a model to aid in the understanding of human factors, or as
a framework around which human factors issues can be structured.
SHEL model
The SHEL model is a theoretical framework developed by Edwards
in 1972. The model places the person as the focus of interest of
the discipline "Human Factors". However, humans are not
independent and unrelated elements in the system but interact
with other elements. Therefore, the main interest of "Human
Factors" also expands to the interrelations between that person
and other elements in the system: software, hardware, and the
environment.
The SHEL model thus takes its name as an acronym of its
constituent elements (Software, Hardware, Environment,
Liveware). Nowadays, the model is practically "lost" in time and
buried in academic history.
It, however, survives in its offspring, the SHELL model.
THE ICAO SHELL MODEL
SHELL model
The SHELL model was proposed by Hawkins in 1975 (see Hawkins &
Orlady, 19931) as a modified version of the SHEL model. Hawkins
introduced a further "liveware" element to the original model in order to
represent group processes (or the interface liveware-liveware). The model
acronym thus reflect the extra element (Software, Hardware, Environment,
Liveware, Liveware). Hawkins also presented the model in graphical form,
with the main operator (one of the "liveware" elements) in the center of the
model, interacting with the remaining four elements, which are placed as
outer elements. This graphical representation enhanced the central concept
of the model: the human (operator) in interaction with those other elements
in the system. Notice that the focus of the model is on this central human
operator and his interactions (referred to as interfaces), not on the outer
elements per se.
THE ICAO SHELL MODEL
Hardware
Environment
Software
Liveware
Liveware
The critical focus of the model is the human participant, or liveware, the most
critical as well as the most flexible component in the system. The edges of this
block are not simple and straight, and so the other components of the system
must be carefully matched to them if stress in the system and eventual
breakdown are to be avoided.
However, of all the dimensions in the model, this is the one which is least
predictable and most susceptible to the effects of internal (hunger, fatigue,
motivation, etc.) and external (temperature, light, noise, workload, etc.) changes.
Human Error is often seen as the negative consequence of the liveware
dimension in this interactive system. Sometimes, two simplistic alternatives are
proposed in addressing error: there is no point in trying to remove errors from
human performance, they are independent of training; or, humans are error prone
systems, therefore they should be removed from decision making in risky
situations and replaced by computer controlled devices. Neither of these
alternatives are particularly helpful in managing errors.
Liveware-Liveware
(the intertface between people and other people)
Software is the collective term which refers to all the laws, rules,
regulations, orders, standard operating procedures, customs and
conventions and the normal way in which things are done. Increasingly,
software also refers to the computer-based programmes developed to
operate the automated systems.
In order to achieve a safe, effective operation between the liveware and
software it is important to ensure that the software, particularly if it
concerns rules and procedures, is capable of being implemented. Also
attention needs to be shown with phraseologies which are error prone,
confusing or too complex. More intangible are difficulties in symbology
and the conceptual design of systems
Liveware-hardware
The interface between people and hardware