ACCIDENT OF
PIA FLIGHT
PK8303
Table of Contents
02
03
Introduction
Importance of
Karachi Airport
Chronological
Order of Events
04
05
06
01
Communication
between Cockpit and
Air Traffic Control
(ATC)
Crash Site Location
& Wreckage Pics
The Crash
Table of Contents
07
08
09
10
Probable Cause
Aviation Safety
Measures
Casualties &Injuries
Rescue Efforts
11
12
13
Improvements in
PIA
Key Lessons
Learned
Changes in
regulations
14
Application in the
Aviation Industry
01
Introduction
•Date: May 22, 2020
•Flight: PIA Flight 8303
•Aircraft: Airbus A320
•Route: Lahore to Karachi (domestic)
•Incident: Crashed during landing near Jinnah International
Airport in Karachi
•Consequences: Loss of lives, significant damage to the
residential area
•Contributing Factors: Human error and technical issues
•Impact: Raised concerns about aviation safety, led to scrutiny
of PIA's operations
02
Importance of Karachi Airport
•Hub: Major hub for Pakistan International Airlines (PIA).
•Population: Karachi, the largest city, central for air
travel.
•Economic Centre: Vital for business and economic
activities.
•International Connectivity: Gateway for global travel.
•Strategic Location: Crucial in the regional aviation
network.
03
Chronological Order of Events
1.May 22, 2020:
1. 12:09 PM: Flight departs from Lahore for Karachi.
2.Approach and Initial Landing Attempt:
1. 1:13 PM: Initiation of approach at Jinnah International Airport in
Karachi.
2. 1:30 PM: First landing attempt; issues arise, leading to a go-around.
3.Communication and Decision Making:
1. 1:37 PM: Pilots communicate with air traffic control (ATC) about
technical issues and report intentions for a second landing attempt.
4.Second Landing Attempt and Tragic Incident:
1. 2:34 PM: Second landing attempt begins.
2. 2:39 PM: Tragic crash occurs in a residential area near Jinnah
International Airport during the second landing attempt.
5.Post-Incident:
1. Ongoing: Investigations into the incident, including analysis of cockpit
voice recorder and flight data recorder data.
04
Communication between Cockpit
and Air Traffic Control (ATC)
1.12:35 PM:
1. Routine communication initiated with Lahore ATC after departure from Lahore.
2.1:13 PM:
1. Approach initiated at Jinnah International Airport in Karachi.
2. ATC clears the aircraft for landing.
3.1:30 PM:
1. First landing attempt; issues arise, leading to a go-around.
2. Pilots communicate with ATC about the decision to abort the landing.
4.1:37 PM:
1. Pilots report technical issues to ATC after the go-around.
2. Indicate intentions for a second landing attempt.
5.2:34 PM:
1. Second landing attempt begins.
6.2:39 PM:
1. Tragic crash occurs during the second landing attempt.
7.Post-Incident:
1. Ongoing investigations focus on analyzing the communication exchanges between
the cockpit and ATC to understand contributing factors to the incident.
05
Crash Site Location &
Wreckage Pics
06
The Crash
●
Initial aborted landing attempt, landing gear not deployed.
●
Failure of both engines.
●
Technical fault forced aircraft to go-around.
●
12 seconds after engine failure mayday emergency declared.
●
Crashed short of runway 25L by about 1340 meters.
●
A slow speed impact with high angle of attack.
●
Runway friction marks indicate ground contact.
●
Engine failure leads to altitude decline.
●
Backup Ram Air Turbine (RAT) deployed.
07
Casualties &
Injuries
●
Out of 99 people on-board 97 fatally injured.
●
2 passengers survived.
●
On the ground, 4 people injured.
●
1 out of these expired later at hospital.
08
Rescue Efforts
●
Special forces and Pakistan Rangers set up a cordon.
●
Airport Rescue and Firefighting (ARFF) Teams deployed.
●
Emergency Medical Services (EMS) deployed.
●
Search and Rescue (SAR) Teams deployed.
09
Probable Cause
●
Ongoing investigation by Pakistan's Aircraft Accident Investigation Board
(AAIB).
●
Landing attempted without the landing gear extended.
●
Aircraft touching down on engines, sparking from high-speed friction with
the runway.
●
Air traffic controller and flight crew actions identified as contributing factors.
●
Pilots preoccupied in a non-operational conversation.
●
Aircraft at 9,800 feet instead of the expected 3,000 feet.
●
Multiple alerts (overspeed, gear unsafe, GPWS) either missed or disregarded
by the flight crew.
10
Aviation Safety
Measures
1. Investigation Insights:
In-depth analysis of incidents provides valuable insights into the root
causes.
2. Identifying Weaknesses:
Incidents highlight weaknesses in procedures, systems, or human
factors.
3. Industry Collaboration:
Shared incident data fosters collaborative efforts for industry-wide
improvements.
4. Technological Advancements:
Incidents drive innovation, leading to the development of safer
technologies.
11
Changes in regulations
Investigations into aviation incidents often result in significant
changes to procedures and regulations. These changes aim to
enhance overall safety within the industry.
1.
2.
Airlines frequently refine their operating procedures based
on investigation findings, while regulatory bodies may
introduce revisions to address identified issues.
Training programs for aviation personnel are updated to
incorporate lessons learned, and communication protocols
are often enhanced to improve information flow.
12
Improvements in PIA
Post-incident, PIA implemented internal reviews,
leading to procedural enhancements, staff training,
and collaboration with regulatory bodies to bolster
overall safety measures.
13
Key Lessons Learned
• The incident provided critical insights into
potential vulnerabilities in operational procedures,
communication protocols, or other facets of
aviation safety.
• Identifying these lessons is crucial for preventing
similar occurrences in the future.
14
Application in the Aviation
Industry
The aviation industry can use these lessons to
instigate proactive measures. This involves
updating and refining safety protocols, conducting
targeted training programs for personnel, investing
in advanced technologies, and fostering a culture of
continuous improvement.
Thank You!
Any Questions?
Team Presentation
NOOR FATIMA
200401009
Muhammad Awais
200401044
M. Aneeb Wadood
200401051