Pakistan International Airlines Flight 8303
Airbus A320-214 · Crashed due to pilot error after dual engine failure following belly landing and go-around
From Allama Iqbal International Airport (LHE) to Jinnah International Airport (KHI)
Event
- NTSB case
- DCA20WA108
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Final · AAIB final report, 20 Apr 2023
- Event fatalities
- 98 · all aircraft and ground
- Ground fatalities
- 1
- Occupants
- 99
- Survivors
- 2
- InjuriesFatal: death within 30 days. Serious: over 48 hours in hospital within a week, most broken bones, severe bleeding, nerve or organ damage, or serious burns. Minor: anything less. Glossary
- 5 · 3 on the ground
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- Airline
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Not recorded
Airbus A320-214
- Flight
- PK8303
- Aircraft type
- Airbus A320
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- AP-BLD
- Operator
- Pakistan International Airlines
- Onboard fatalities
- 97
- Route
- From Allama Iqbal International Airport (LHE)To Jinnah International Airport (KHI)
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Non-U.S., Commercial
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Approach
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Unknown or undetermined
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Personnel issues › Task performance
- Personnel issues › Action/decision
- Personnel issues › Miscellaneous
From the investigation findings the Wikipedia article reports, sorted into the NTSB's cause areas with AI assistance.
Approximate · Coordinates from the Wikipedia article; not checked against an investigation report.
From the Wikipedia article
On 22 May 2020, Pakistan International Airlines Flight 8303, a scheduled domestic passenger flight from Lahore to Karachi, crashed while on approach to Jinnah International Airport, killing 97 out of the 99 people on board as well as an additional person on the ground. The aircraft, an Airbus A320 with 91 passengers and 8 crew members on board, was on an unstable approach to Jinnah International Airport, with an excessively high airspeed and altitude. The aircraft subsequently belly landed nearly half-way down the airport runway before the flight crew conducted a go-around. During the go-around, both engines started to fail due to damage sustained during the belly landing. Whilst attempting to land back on the runway, the aircraft lost airspeed and crashed into buildings in Model Colony. All 8 crew members and 89 out of the 91 passengers on board were killed by the impact and post-crash fire. One person who was inside the buildings died ten days after the crash due to burn injuries.
The investigation, conducted by the Aircraft Accident Investigation Board of Pakistan, determined that both the captain and first officer made multiple errors over an extended period during both the approach and landing. The crew lacked crew resource management, which led to unsafe flight operations and a lack of adherence to standard operating procedures. The investigators determined that the crew's actions resulted in the aircraft being significantly above the required glide slope approach path for the runway. The flight crew disregarded air traffic control instructions and continued an unstable approach. The improper position of the approach path and the configuration of the aircraft then caused the autopilot to disengage. In response to the high descent rate and numerous warnings from the ground proximity warning system, the first officer raised the landing gear and speed brakes in an attempt to go around. He did not verbalise his actions to the captain, nor did he follow up with the proper go-around procedure. The captain continued with the landing, and the aircraft contacted the surface of the runway multiple times. This resulted in severe damage to the engines, which led to a failure of both engines and electrical generators as the aircraft then climbed away from the runway. The crew were now attempting to return to the airport, but with damaged engines and at a critical altitude, the plane was simply too low and too slow to go around for a successful landing. The aircraft continued to lose airspeed before crashing into a row of buildings 4,410 ft from the threshold of the runway.
Flight operations
During the flight, the investigation found that the crew displayed disregard to several safety regulations. During cruise, the CVR revealed that the flight crew engaged in casual conversation, especially about the COVID-19 pandemic. Conversations not relevant to the safety of the flight are not allowed below 10,000 ft (the sterile cockpit rule), but the flight crew continued to converse in violation of the rule. The required approach briefing was never conducted. The AAIB determined that their conversations also resulted in a failure to verbalize changes to the flight mode annunciator (FMA) and the temporary loss of radio contact.
The AAIB deemed that the crew demonstrated a lack of situational awareness and crew resource management (CRM) several times during the descent. The crew did not notice the two indications of the holding pattern at SABEN: one on the navigation display and one on the multi-function control and display unit. The AAIB determined that this resulted in their failure to notice the indicated track miles was greater than the amount the aircraft flew. The investigation also stated that crew was overconfident and complacent as they did not communicate or crosscheck with each other with the position of the aircraft.
The AAIB determined that the crew did not follow standard operating procedures (SOPs), which showed when they engaged open descent mode on final approach despite it being prohibited during that phase of flight. When ATC told the flight about their position, the crew disregarded their suggestions of taking an orbit and continued with the unstable approach. The investigators found that the crew failed to properly consider their options, which was in violations of SOPs, and were focused in on the approach without considering their altitude, showing a lack of situational awareness. When the autopilot disconnected due to excessive nose down pitch, the CVR indicated that crew failed to verbalize the master caution warning or the FMA caution, and did not establish who was in control of the aircraft. Despite the required procedure after a GPWS activation being to initiate a terrain escape manoeuvre to climb away from the terrain, the recorders showed that the crew failed to do so after the GPWS activated. The AAIB deemed this to be demonstrating their lack of situational awareness in relation to the position of the aircraft.
After First Officer Azam raised the landing gear and speed brakes, the CVR showed that he did not communicate his action with Captain Gul, who remained insistent on landing the aircraft. Neither recorder showed the crew acknowledging the master caution warnings after the extension of the flaps, the "landing gear not down" ECAM warning, or them conducting an orbit at the instruction of ATC. Despite being on an unstabilized approach, the CVR recorded no callouts about the aircraft's position, a violation of SOPs according to the AAIB. Gul assuming control over the aircraft without any callouts showed improper CRM as the CVR showed there was no conversation about who was actually in control of the flight.
During the landing attempt, full reverse thrust was selected on both engines despite the aircraft still being airborne, against SOPs. The flight crew then initiated a go-around despite being on the ground for 18 seconds. This was against standard procedure, which dictates that flight crews must not go-around after reverse thrust selection. The AAIB deemed that the crew demonstrated poor airmanship by deciding to go-around after the engine two fire warning rather than trying to stop on the runway. After the go-around, the investigators determined that the crew failed to properly discuss the gear-up landing or a second approach to Runway 25L, demonstrating a lack of situational awareness. The lack of situational awareness was also shown when the DFDR recorded the crew reducing power to the still functional engine two rather than the failing engine one.
Flight crew performance
The investigation highlighted several factors in relation to the performance of the flight crew and their past in aviation. Captain Gul had a history of excessive flight hours; an analysis of his flying hours between 2017 and 2019 showed that he flew 33% more than the average for all other PIA A320 captains and he was issued a notice by the Pakistan Civil Aviation Authority (PCAA) about exceeding duty time limitations. In 2014, he was considered for a supervisory position on ATR aircraft but was not recommended due to lack of technical knowledge and general awareness. An analysis of Gul's flights in the twelve months prior to the accident showed multiple high-speed approaches, excessively high approaches, high rates of descent, long flare distances, GPWS warnings, a lack of go-arounds, and unstabilized approaches. As part of the investigation, an aviation psychologist wrote, "He was of bossy nature, firm, dominant and overbearing. He had below average intelligence. He [tended] to have little regard for the authority. He had low mechanical comprehension with low comprehension of space relations. His level of stress tolerance was also quite inadequate." During Gul's first psychiatric evaluation, he was not recommended for a cadet pilot position by the panel at PIA. Subsequently, he got declared fit for cadet pilot by five other psychiatrists. The PIA psychiatric panel initially denied Gul's application, but after he filed a petition to the Wafaqi Mohtasib, they sided with him and he was declared fit.
First Officer Azam also had difficulties in his past. During initial simulator checks on ATR aircraft in July 2014, he passed with three "satisfactory with briefing" remarks on engine failure after V1, emergency procedures, and procedure execution and adherence. Later during his initial line check in December, he passed with two more satisfactory with briefing remarks. As a result, he was placed under supervision by a Pakistan Civil Aviation Authority (PCAA) inspector the next year which withheld his promotion to an A320 first officer in February 2016.
The AAIB determined that the flight crew failed to adhere to standard operating procedures and apply proper crew resources management. They listed Gul's history of having problems with approaches as a finding related to flight operations and the crash.
As the crash occurred during the Islamic holy month of Ramadan, the AAIB conducted tests and research to discover whether fasting might have impaired the flight crew's performance. During Ramadan, Muslims abstain from eating or drinking from sunrise to sunset. Fasting can affect the normal human day-night routine, circadian rhythms, levels of hydration, and blood sugar levels. PCAA regulations state that pilots shall not fly while under the effects of fasting. The AAIB conducted two studies in flight simulators in relation to the effects of fasting: one to study the performance of dehydrated pilots against a control group; and one to compare the performance of pilots with low blood sugar levels against pilots with excessive blood alcohol levels, pilots exposed to excessive noise, and a control group. For the first study, results showed that dehydrated pilots had worse flight performance and spatial cognition compared to properly hydrated pilots. For the second study, results showed that pilots with low blood sugar levels deviated the most from a set vertical axis, horizontal axis, and airspeed, followed by pilots with excessive blood alcohol levels. The flight crew on Flight 8303 were likely fasting during flight; the CVR showed that a flight attendant offered them snacks, but they refused the offer. The AAIB concluded that the judgment of the flight crew was likely impaired due to the effects of fasting, although they did not determine the full extent of the consequences of this impairment. Additionally, manuals at PIA did not make it clear what the regulations on fasting were at the airline.
Investigation and cause
Investigation
The investigation was conducted by Aircraft Accident Investigation Board of Pakistan (AAIB). Airbus stated they would be providing assistance to the French Bureau of Enquiry and Analysis for Civil Aviation Safety (BEA) who would be helping with the investigation. Subsequently, an 11-member Airbus team visited the crash site on 26 May. The aircraft's DFDR and CVR were recovered from the accident site and flown to France to be analyzed by the BEA.
Final report and recommendations
On 25 February 2024, the AAIB released their final report. They determined the following "primary causes" for the accident:
As "contributing causes", they listed:
The AAIB issued five recommendations to PIA and seven recommendations to the PCAA. Among them included recommendations to effectively implement FOQA programmes into the SMS at PIA, review CRM programmes, ensure compliance of SOPs, and more specific regulations and oversight on fasting.
Text from the Wikipedia article “Pakistan International Airlines Flight 8303” (revision 1374183330, retrieved 2026-09-18) by its authors, under CC BY-SA 4.0. Extracted as plain text: references, tables, images and some sections are left out. Read the article
NTSB narrative
The government of Pakistan has notified the NTSB of an accident involving an AIRBUS A320 with CFM56 engines that occurred on May 22, 2020. The NTSB has appointed a U.S. Accredited Representative to assist the government of Pakistan's investigation under the provisions of ICAO Annex 13.All investigative information will be released by the government of Pakistan.
Verbatim NTSB factual narrative from the NTSB dataset
Sources
Wikipedia article: Pakistan International Airlines Flight 8303
- Revision
- 1374183330 · 2026-09-10 · retrieved 2026-09-18
- Wikidata
- Q95092655
- Licence
- Text CC BY-SA 4.0, by the article's authors; Wikidata CC0; town positions GeoNames (CC BY 4.0)
NTSB record DCA20WA108
- Event ID
- 20200522X82856
- Case number
- DCA20WA108
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Where each value comes from
- Record
- Wikipedia article "Pakistan International Airlines Flight 8303" (page 64032862, revision 1374183330); merged with NTSB case DCA20WA108 (events / aircraft)
- Date
- Wikipedia infobox: date; matches the Aircraft Accident Investigation Board (AAIB), Pakistan final report
- Place and country
- Wikipedia infobox: site
- Map position
- Wikipedia: Wikipedia article coordinates; matches the Aircraft Accident Investigation Board (AAIB), Pakistan final report
- Aircraft, operator and route
- Wikipedia infobox: aircraft type, registration, operator, origin and destination; route airports from the linked airport articles' Wikidata codes (OurAirports); gaps and aircraft details from NTSB record DCA20WA108
- Operation
- airline flight number in the infobox
- Fatalities
- Wikipedia: Wikipedia infobox: total_fatalities; matches the Aircraft Accident Investigation Board (AAIB), Pakistan final report
- Ground fatalities
- Wikipedia: Wikipedia infobox: ground fatalities; matches the Aircraft Accident Investigation Board (AAIB), Pakistan final report
- Summary
- Wikipedia infobox: summary
Source notes (3)
- One occurrence in two sources, merged: the Wikipedia article "Pakistan International Airlines Flight 8303" and NTSB case DCA20WA108, matched by the same aircraft registration and date. For this event outside the United States Wikipedia's values are used where the two differ; each value names its source.
- No bulk values were replaced by the NTSB case API.
- Checked against the Aircraft Accident Investigation Board (AAIB), Pakistan final report (2023-04-20) on 2026-09-18. The report states the same date, crash-site coordinates, flight number, ground fatalities, fatalities, registration, operator, departure, destination and damage. Not checked: place, aircraft type and type of operation.