AVIATION
ACCIDENTS
AND
INCIDENTS
ROSS APTED
KEGWORTH AIR DISASTER
Scene of the disaster – wreckage on M1 motorway near Kegworth
WHAT HAPPENED
On 8th January 1989 British midland flight 92 crashed while
undertaking an emergency landing.
Crashed site : M1 embankment near the village of Kegworth.
The Boeing 737 -400 aircraft was severely damaged 79 of the
of the 126 people aboard the plane survived.


An investigation was carried out by the Air Accidents
Investigation Branch (AAIB).
(Air Accidents Investigation Branch, 1989)
AAIB INVESTIGATION
Events of the crash
1. During the ascent of the aircraft to its cruising altitude of
   35,000 feet metal fatigue occurred on the fan blades in
   the left engine.


           Due to the engine
  design not being able to
  withstand vibrations caused
  by operation above 25, 000
  feet and a high power
  setting.



                                       Boeing 737–400 Engine
AAIB INVESTIGATION
2. Fan blade broke off causing decrease in power and
   increase in vibrations. This caused the left engine to
   produced a jet of flames.


3. Smoke flooded into the cabin. Captain shut down the
   engine on the right.


4. Smell of smoke and vibrations reduced.


5. Crew diverted to Midlands Airport. Left engine completely
   failed during the descent of the emergency landing
AAIB INVESTIGATION
Causes of the Crash
The flight crew shut down the right engine(which was
functioning correctly – could have sustained aircraft)
       In response to the left engine being damaged(blade
       fracture.)
The left engine then completely failed due to increases stress
during approach to land.
The wrong engine was shut down.
Primary cause: Human error
Secondary cause: technical failure
CONTRIBUTING
FACTORS
Inadequate knowledge of the aircraft
Flight crew observed smoke in the cabin.
Believed they could not trust the Vibration sensors. Was true
of the old Boeing 737 but not the new 737-400.


   Indicates the state of the engines.
Fell back on general knowledge of aircraft which was wrong.
Thought that bleed air(pressure and heating) was taken from
the right engine.
In fact the air conditioning systems utilized both engines in
the new model.
BOEING 737 (OLD)


   Right engine




                  Key
                        - bleed air via air
                          conditioning
BOEING 737-400
(NEW)


 Right engine   Left engine




                          Key
                                - bleed air via air
                                  conditioning
CONTRIBUTING
FACTORS
In adequate training
The combination of violent engine vibrations and the smell of
smoke while climbing to covered attitude was not covered in
training.
Two separate protocols existed for each event but not in
conjunction.


No simulation training for engine failure of this kind, or what to
do if the situations fall out of bounds of standard procedures.


Differences in the Boeing 737 and 737-400 were not adequately
taught.
WHY THE MISTAKE
WAS NOT FOUND
By chance the the smoke dissipated and the vibrations
reduced – this was actually due to standard procedure
reducing fuel flow to both the engines.


Pilots did not communicate with the cabin crew who had
visual confirmation of which engine was damaged.


Immediate division to Midlands airport create a high cabin
workload this resulted in incorrect review procedure after the
right engine was shut down.
Insufficient
                     knowledge
                      of aircraft




          Right          In
Crash
        engine was   adequate
        shut down     training




                                    Improper
                     Left engine     design
                        failed       testing
ACADEMIC
LITERATURE
On a Wing and a Prayer? Exploring the Human Components of
Technological Failure
(Smith, 2000)


Key points
Exploring the role of human error in complex technical systems.
Case study Kegworth
Thesis – Import to not only focus on individual but social and
managerial framework in which the exist.
Conclusion – With fly – by –wire system on the rise it is ever
more import to look at the organization as a
whole and not just focus on individual aspects.
QANTAS FLIGHT 72
Qantas A330-303 - the type of aircraft that the incident occurred on
WHAT HAPPENED
On the 7th October 2008 Qantas Flight 72 made an
emergency landing due to in flight accident.
 A series of in uncommand pitch down maneuvers were
initiated resulting in crew and passenger injury.


An investigation was carried out by The Australian Transport
Safety Bureau (ATSB).
(Australian Transport Safety Bureau )
ATSB INVESTIGATION
Events of the accident
1. At cruising altitude one of the Air Data Inertial Reference
   Unit stated to providing incorrect values know as spikes
   to flight systems.


       Air Data Inertial Reference Unit(ADIRU) –provides air
data   such as air speed, altitude and angle of attack the
       pilots flight instruments.


2. The autopilot disconnect an warning were triggered.
3. Aircraft rapidly pitched down unprompted. Due to the
   flight control primary computer the angle of attack spike.
ATSB INVESTIGATION
4. Sudden forces cause severe injuries to the aircrafts
   occupants.
5. A second pitch down occurred moments later.
6. Pilots switch to manual operation a sent a Mayday
   distress.
7. Flight was diverted to Learmonth, Western Australia
ATSB INVESTIGATION
Cause of the accident
flight control primary computer
Is a “full-authority” flight control system. Get its flight data
from the ADIRU’s. 3 ADIRU for error resistance and
redundancy.
If all 3 ADIRU are consistent the and average of ADIRU1 and
ADIRU2 is used.
If ADIRU1 or ADIRU2 are not consistent then a memorized
value is used for 1.2s.
Fault occurred when there was multiple spikes 1.2s apart.
ATSB INVESTIGATION
ADIRU data-spike
ADIRU entered a failure mode in which it was sending invalid
data to flight system but marking it as being valid.


No warning that the unit had failed was trigged.


Hardware bug – the CPU module of the unit would inexpiably
combined the parameter for value with the label for another
parameter.
AIRBUS VS BOEING
Airbus philosophy - safety will be reduced by removing
human error
= giving the computer more control.


Boeing philosophy - safety will be reduced by removing the
complexities between the interactions of humans and
technology.
= give pilot unlimited control but make it easier to interact
with the computer.
AAIB BULLETIN- INCIDENT
Boeing 747- the type of aircraft that the incident occurred on
SERIOUS INCIDENT
Serious incident involving a Boeing 757-21B found in the
June 2012 bulletin.
(Air Accidents Investigation Branch, 2012)


AAIB Bulletin – A monthly notice of accidents and serous
                                    incident.


What happened:
The Aircraft lost power to its left AC electrical bus, causing
the failure many flight instruments.
BACKGROUND
1.    Mid-flight the “L AC BUS OFF” and “L GEN OFF” warning
      lights triggered indicating a power failure.
2.    Multiple flight instruments failed.
3.    Commander carried out the drill for power loss in the left
      generator.
4.    Bus reset and power temporally restored
5.    Power went off again this time accompanied with thin
      smoke on flight deck.
6.    MAYDAY was sent and aircraft was diverted to nearest
      airport.


     Only effect on passengers was that they had to
                    catch a new flight.
AAIB INVESTIGATION
Found that be a corroded crimp
terminal at the D1114J connector
which is part of the left power
generation system.


Procedure
Split into previous and post incident
maintenance actions
Still focuses on crew actions             Broken D1114j connector


Standardized format for bulletins – focus on primary sources of
information little root cause analysis.
REFERENCES
Air Accidents Investigation Branch. (2012). June 2012
Bulletin. Aldershot: Air Accidents Investigation Branch.
Air Accidents Investigation Branch. (1989). Report on the
Accident to Boeing 737-400 G-OBME near Kegworth,
Leicesterhire on 8 Janury 1989. Aldershot: Air Accidents
Investigation Branch.
Australian Transport Safety Bureau. (2008). In-flight upset
154 km west of Learmonth, WA 7 October 2008 VH-QPA
Airbus A330-303. Canberra: Australian Transport Safety
Bureau.
Smith, D. (2000). On a wing and a prayer? Exploring the
human components of technological failure. Syst. Res. , 543–
559.

More Related Content

PPTX
Air accident
PPT
CRM pilot tranning
PPTX
Aircraft accident investigation ppt
PDF
Boeing 737 Max Accidents
PDF
Connors.J_The engines of pratt whitney a technical history.pdf
PPT
Engines.ppt
PPT
Cyber bullying powerpoint
PDF
مؤشرات الأداء الرئيسية: تعريفها وآلياتها.
Air accident
CRM pilot tranning
Aircraft accident investigation ppt
Boeing 737 Max Accidents
Connors.J_The engines of pratt whitney a technical history.pdf
Engines.ppt
Cyber bullying powerpoint
مؤشرات الأداء الرئيسية: تعريفها وآلياتها.

What's hot (20)

PPTX
Air crash investigation
PPTX
Causes of Airplane Accidents
PPT
Types of aircraft presentation
PPTX
Crew Resource Management
PPTX
Aircraft landing gear
PPTX
Aircraft Systems and Instruments
PPT
Aviation disasters due to mechanical failures
PDF
Human factors in Aviation
PPTX
LANDING GEAR
PDF
Human Factors Training in Aviation
PPTX
Ramp safety
PPTX
Human factors for crew&members
PPTX
Crew Resource Management : General
PPTX
Airside Hazards And Risks
PPT
airside operation 3
PPT
Aviation security -_chpt1
PPTX
Fly by wire ppt pa1
PPTX
AVIATION PPT (RAHUL GUPTA)
DOCX
Landing Gear
Air crash investigation
Causes of Airplane Accidents
Types of aircraft presentation
Crew Resource Management
Aircraft landing gear
Aircraft Systems and Instruments
Aviation disasters due to mechanical failures
Human factors in Aviation
LANDING GEAR
Human Factors Training in Aviation
Ramp safety
Human factors for crew&members
Crew Resource Management : General
Airside Hazards And Risks
airside operation 3
Aviation security -_chpt1
Fly by wire ppt pa1
AVIATION PPT (RAHUL GUPTA)
Landing Gear
Ad

Viewers also liked (20)

PPT
Top 10 Causes of FATAL General Aviation Accidents
PPTX
Air crash investigation
PDF
Aircraft structure pp
PPTX
Cream analysis of the Kegworth Air Disaster
PPTX
Fault Tree - Kegworth
PPT
Presentation On Aviation
PPTX
Indian Aviation Industry 2011
PPT
Indian Aviation Industry
PPTX
Itt presentation (indian aviation industry case study)
PPT
Aviation Industry
PPTX
Software project failure in new zealand – what’s killing us and what we can d...
PDF
MMAE545-Final Report-Analysis of Aircraft Wing
PPTX
Challenges for aviation industry in india
DOCX
Introduction to the aviation industry
PPT
Culture & air crashes3
PPTX
Make power out of your waste heat - Organic Rankine Cycle
PPTX
Indian Aviation Industry analysis
PDF
Project of Aircraft Structure Failure
PDF
Yield management in the airline industry
 
PPTX
Airline industry ppt
Top 10 Causes of FATAL General Aviation Accidents
Air crash investigation
Aircraft structure pp
Cream analysis of the Kegworth Air Disaster
Fault Tree - Kegworth
Presentation On Aviation
Indian Aviation Industry 2011
Indian Aviation Industry
Itt presentation (indian aviation industry case study)
Aviation Industry
Software project failure in new zealand – what’s killing us and what we can d...
MMAE545-Final Report-Analysis of Aircraft Wing
Challenges for aviation industry in india
Introduction to the aviation industry
Culture & air crashes3
Make power out of your waste heat - Organic Rankine Cycle
Indian Aviation Industry analysis
Project of Aircraft Structure Failure
Yield management in the airline industry
 
Airline industry ppt
Ad

Similar to Aviation accidents and incidents (20)

PPTX
Kegworth Air Disaster
PPTX
What Do You Do When The Pilots Shut Down The Wrong Engine?
PDF
FAA Risk Management
PPTX
Korean Air Cargo Crash
PDF
Poor UI design can
PPTX
Human Factor Study Case
PPT
Consequences of Errors in Aviation
DOCX
HUMAN FACTORS REPORT STUDY CASES
PDF
Various_CAT_VarVarious_CAT_03-ious_CAT_03-0Various_CAT_03-3-22.pdf
PPTX
PPTX
How Did A Flyable Plane Crash in Just Over Four Minutes?
PPTX
How Did A Flyable Plane Crash in Just Over Four Minutes?
PPTX
What Do You Do When The Pilots Shut Down The Wrong Engine?
PPTX
The Presentation of Plane Crash Incidents
PPTX
Aircraft Accident Investigation on American Airline 587 crash
PDF
Is your aircraft talking to you? Listen!
DOCX
PDF
Zonk Airlines Incident
PDF
WELCOME [Autosaved].pptghjhhhjjjjjjiiiygg
PDF
Avlite System_White Paper_Runway_Closures_FINAL
Kegworth Air Disaster
What Do You Do When The Pilots Shut Down The Wrong Engine?
FAA Risk Management
Korean Air Cargo Crash
Poor UI design can
Human Factor Study Case
Consequences of Errors in Aviation
HUMAN FACTORS REPORT STUDY CASES
Various_CAT_VarVarious_CAT_03-ious_CAT_03-0Various_CAT_03-3-22.pdf
How Did A Flyable Plane Crash in Just Over Four Minutes?
How Did A Flyable Plane Crash in Just Over Four Minutes?
What Do You Do When The Pilots Shut Down The Wrong Engine?
The Presentation of Plane Crash Incidents
Aircraft Accident Investigation on American Airline 587 crash
Is your aircraft talking to you? Listen!
Zonk Airlines Incident
WELCOME [Autosaved].pptghjhhhjjjjjjiiiygg
Avlite System_White Paper_Runway_Closures_FINAL

More from stargate1280 (8)

PPTX
FRAM Analysis - Kegworth
PPTX
Overview of Systemic Modeling Approaches
PPTX
Overview of Systemic Modeling Approaches
PPTX
Summary of Selected Accident Modeling Papers
PPTX
Summary of Selected Accident Modeling Papers
PPTX
Overview modeling approches part 1
PPTX
Columbia and Challenger
PPTX
2010 Flash Crash
FRAM Analysis - Kegworth
Overview of Systemic Modeling Approaches
Overview of Systemic Modeling Approaches
Summary of Selected Accident Modeling Papers
Summary of Selected Accident Modeling Papers
Overview modeling approches part 1
Columbia and Challenger
2010 Flash Crash

Recently uploaded (20)

PPTX
Build automations faster and more reliably with UiPath ScreenPlay
PDF
LMS bot: enhanced learning management systems for improved student learning e...
PDF
Rapid Prototyping: A lecture on prototyping techniques for interface design
PDF
Data Virtualization in Action: Scaling APIs and Apps with FME
PDF
AI.gov: A Trojan Horse in the Age of Artificial Intelligence
PDF
Transform-Your-Supply-Chain-with-AI-Driven-Quality-Engineering.pdf
PDF
SaaS reusability assessment using machine learning techniques
PDF
“The Future of Visual AI: Efficient Multimodal Intelligence,” a Keynote Prese...
PDF
Co-training pseudo-labeling for text classification with support vector machi...
PDF
A symptom-driven medical diagnosis support model based on machine learning te...
PDF
substrate PowerPoint Presentation basic one
PDF
Connector Corner: Transform Unstructured Documents with Agentic Automation
PDF
Human Computer Interaction Miterm Lesson
PPTX
MuleSoft-Compete-Deck for midddleware integrations
PDF
Planning-an-Audit-A-How-To-Guide-Checklist-WP.pdf
PDF
The AI Revolution in Customer Service - 2025
PDF
Transform-Your-Factory-with-AI-Driven-Quality-Engineering.pdf
PDF
Ensemble model-based arrhythmia classification with local interpretable model...
PDF
EIS-Webinar-Regulated-Industries-2025-08.pdf
PDF
Early detection and classification of bone marrow changes in lumbar vertebrae...
Build automations faster and more reliably with UiPath ScreenPlay
LMS bot: enhanced learning management systems for improved student learning e...
Rapid Prototyping: A lecture on prototyping techniques for interface design
Data Virtualization in Action: Scaling APIs and Apps with FME
AI.gov: A Trojan Horse in the Age of Artificial Intelligence
Transform-Your-Supply-Chain-with-AI-Driven-Quality-Engineering.pdf
SaaS reusability assessment using machine learning techniques
“The Future of Visual AI: Efficient Multimodal Intelligence,” a Keynote Prese...
Co-training pseudo-labeling for text classification with support vector machi...
A symptom-driven medical diagnosis support model based on machine learning te...
substrate PowerPoint Presentation basic one
Connector Corner: Transform Unstructured Documents with Agentic Automation
Human Computer Interaction Miterm Lesson
MuleSoft-Compete-Deck for midddleware integrations
Planning-an-Audit-A-How-To-Guide-Checklist-WP.pdf
The AI Revolution in Customer Service - 2025
Transform-Your-Factory-with-AI-Driven-Quality-Engineering.pdf
Ensemble model-based arrhythmia classification with local interpretable model...
EIS-Webinar-Regulated-Industries-2025-08.pdf
Early detection and classification of bone marrow changes in lumbar vertebrae...

Aviation accidents and incidents

  • 2. KEGWORTH AIR DISASTER Scene of the disaster – wreckage on M1 motorway near Kegworth
  • 3. WHAT HAPPENED On 8th January 1989 British midland flight 92 crashed while undertaking an emergency landing. Crashed site : M1 embankment near the village of Kegworth. The Boeing 737 -400 aircraft was severely damaged 79 of the of the 126 people aboard the plane survived. An investigation was carried out by the Air Accidents Investigation Branch (AAIB). (Air Accidents Investigation Branch, 1989)
  • 4. AAIB INVESTIGATION Events of the crash 1. During the ascent of the aircraft to its cruising altitude of 35,000 feet metal fatigue occurred on the fan blades in the left engine. Due to the engine design not being able to withstand vibrations caused by operation above 25, 000 feet and a high power setting. Boeing 737–400 Engine
  • 5. AAIB INVESTIGATION 2. Fan blade broke off causing decrease in power and increase in vibrations. This caused the left engine to produced a jet of flames. 3. Smoke flooded into the cabin. Captain shut down the engine on the right. 4. Smell of smoke and vibrations reduced. 5. Crew diverted to Midlands Airport. Left engine completely failed during the descent of the emergency landing
  • 6. AAIB INVESTIGATION Causes of the Crash The flight crew shut down the right engine(which was functioning correctly – could have sustained aircraft) In response to the left engine being damaged(blade fracture.) The left engine then completely failed due to increases stress during approach to land. The wrong engine was shut down. Primary cause: Human error Secondary cause: technical failure
  • 7. CONTRIBUTING FACTORS Inadequate knowledge of the aircraft Flight crew observed smoke in the cabin. Believed they could not trust the Vibration sensors. Was true of the old Boeing 737 but not the new 737-400. Indicates the state of the engines. Fell back on general knowledge of aircraft which was wrong. Thought that bleed air(pressure and heating) was taken from the right engine. In fact the air conditioning systems utilized both engines in the new model.
  • 8. BOEING 737 (OLD) Right engine Key - bleed air via air conditioning
  • 9. BOEING 737-400 (NEW) Right engine Left engine Key - bleed air via air conditioning
  • 10. CONTRIBUTING FACTORS In adequate training The combination of violent engine vibrations and the smell of smoke while climbing to covered attitude was not covered in training. Two separate protocols existed for each event but not in conjunction. No simulation training for engine failure of this kind, or what to do if the situations fall out of bounds of standard procedures. Differences in the Boeing 737 and 737-400 were not adequately taught.
  • 11. WHY THE MISTAKE WAS NOT FOUND By chance the the smoke dissipated and the vibrations reduced – this was actually due to standard procedure reducing fuel flow to both the engines. Pilots did not communicate with the cabin crew who had visual confirmation of which engine was damaged. Immediate division to Midlands airport create a high cabin workload this resulted in incorrect review procedure after the right engine was shut down.
  • 12. Insufficient knowledge of aircraft Right In Crash engine was adequate shut down training Improper Left engine design failed testing
  • 13. ACADEMIC LITERATURE On a Wing and a Prayer? Exploring the Human Components of Technological Failure (Smith, 2000) Key points Exploring the role of human error in complex technical systems. Case study Kegworth Thesis – Import to not only focus on individual but social and managerial framework in which the exist. Conclusion – With fly – by –wire system on the rise it is ever more import to look at the organization as a whole and not just focus on individual aspects.
  • 14. QANTAS FLIGHT 72 Qantas A330-303 - the type of aircraft that the incident occurred on
  • 15. WHAT HAPPENED On the 7th October 2008 Qantas Flight 72 made an emergency landing due to in flight accident. A series of in uncommand pitch down maneuvers were initiated resulting in crew and passenger injury. An investigation was carried out by The Australian Transport Safety Bureau (ATSB). (Australian Transport Safety Bureau )
  • 16. ATSB INVESTIGATION Events of the accident 1. At cruising altitude one of the Air Data Inertial Reference Unit stated to providing incorrect values know as spikes to flight systems. Air Data Inertial Reference Unit(ADIRU) –provides air data such as air speed, altitude and angle of attack the pilots flight instruments. 2. The autopilot disconnect an warning were triggered. 3. Aircraft rapidly pitched down unprompted. Due to the flight control primary computer the angle of attack spike.
  • 17. ATSB INVESTIGATION 4. Sudden forces cause severe injuries to the aircrafts occupants. 5. A second pitch down occurred moments later. 6. Pilots switch to manual operation a sent a Mayday distress. 7. Flight was diverted to Learmonth, Western Australia
  • 18. ATSB INVESTIGATION Cause of the accident flight control primary computer Is a “full-authority” flight control system. Get its flight data from the ADIRU’s. 3 ADIRU for error resistance and redundancy. If all 3 ADIRU are consistent the and average of ADIRU1 and ADIRU2 is used. If ADIRU1 or ADIRU2 are not consistent then a memorized value is used for 1.2s. Fault occurred when there was multiple spikes 1.2s apart.
  • 19. ATSB INVESTIGATION ADIRU data-spike ADIRU entered a failure mode in which it was sending invalid data to flight system but marking it as being valid. No warning that the unit had failed was trigged. Hardware bug – the CPU module of the unit would inexpiably combined the parameter for value with the label for another parameter.
  • 20. AIRBUS VS BOEING Airbus philosophy - safety will be reduced by removing human error = giving the computer more control. Boeing philosophy - safety will be reduced by removing the complexities between the interactions of humans and technology. = give pilot unlimited control but make it easier to interact with the computer.
  • 21. AAIB BULLETIN- INCIDENT Boeing 747- the type of aircraft that the incident occurred on
  • 22. SERIOUS INCIDENT Serious incident involving a Boeing 757-21B found in the June 2012 bulletin. (Air Accidents Investigation Branch, 2012) AAIB Bulletin – A monthly notice of accidents and serous incident. What happened: The Aircraft lost power to its left AC electrical bus, causing the failure many flight instruments.
  • 23. BACKGROUND 1. Mid-flight the “L AC BUS OFF” and “L GEN OFF” warning lights triggered indicating a power failure. 2. Multiple flight instruments failed. 3. Commander carried out the drill for power loss in the left generator. 4. Bus reset and power temporally restored 5. Power went off again this time accompanied with thin smoke on flight deck. 6. MAYDAY was sent and aircraft was diverted to nearest airport. Only effect on passengers was that they had to catch a new flight.
  • 24. AAIB INVESTIGATION Found that be a corroded crimp terminal at the D1114J connector which is part of the left power generation system. Procedure Split into previous and post incident maintenance actions Still focuses on crew actions Broken D1114j connector Standardized format for bulletins – focus on primary sources of information little root cause analysis.
  • 25. REFERENCES Air Accidents Investigation Branch. (2012). June 2012 Bulletin. Aldershot: Air Accidents Investigation Branch. Air Accidents Investigation Branch. (1989). Report on the Accident to Boeing 737-400 G-OBME near Kegworth, Leicesterhire on 8 Janury 1989. Aldershot: Air Accidents Investigation Branch. Australian Transport Safety Bureau. (2008). In-flight upset 154 km west of Learmonth, WA 7 October 2008 VH-QPA Airbus A330-303. Canberra: Australian Transport Safety Bureau. Smith, D. (2000). On a wing and a prayer? Exploring the human components of technological failure. Syst. Res. , 543– 559.