FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

JS Air Flight 201

5 Nov 2010 · Near Jinnah International Airport, Karachi, Pakistan

Beechcraft 1900C-1 · Crashed following engine failure at take-off and loss of control

From Jinnah International Airport (KHI) to Bhit Shah airfield, Jamshoro district, Sindh, Pakistan

Report a problem

Event

NTSB case
DCA11WA008
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 · SIB final report 
Event fatalities
21 · all aircraft and ground
Ground fatalities
0
Occupants
21
Survivors
0
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
0 serious · 0 minor (NTSB)
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

Beechcraft 1900C-1

Aircraft type
Beechcraft 1900
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-BJD
Operator
JS Air
Onboard fatalities
21
Route
From Jinnah International Airport (KHI)To Bhit Shah airfield, Jamshoro district, Sindh, Pakistan
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
Initial climb
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
Loss of engine power (partial)
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 › Experience/knowledge
  • Personnel issues › Task performance
  • Personnel issues › Psychological
  • Personnel issues › Miscellaneous
  • Aircraft › Aircraft propeller/rotor

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 5 November 2010, JS Air Flight 201, a Beechcraft 1900 passenger aircraft on a charter service from Karachi to the Bhit Shah gas field in Sindh, Pakistan, crashed near Karachi's Jinnah International Airport, after suffering an engine malfunction at take-off. All 21 people on board were killed.

The investigation by Pakistan's Civil Aviation Authority concluded that the primary cause of the accident was the "inappropriate skill level" of the captain in dealing with the malfunction, and more generally the flight crew's non-adherence to the procedures prescribed by the aircraft manufacturer in such abnormal circumstances.

Accident

The aircraft had been chartered to fly 17 personnel of Italian oil and gas company Eni from Jinnah International Airport in Karachi to the Bhit Shah gas field. Three crew members and one airport security guard were also on board. At 01:55 UTC, the flight crew contacted Karachi Ground for take off. The Karachi Ground Controller replied "copied JS-201 start up approved runway two five left" and this was acknowledged by cockpit crew. The Captain cleared the area towards left side and began start up procedure for Engine No 1.

Following this the crew contacted Karachi Ground requesting taxi instructions which were given. Having received this the pilots conducted the pre-take off checklist. Cockpit Voice Recorder (CVR) data shows that the right engine propeller feathering system was checked as being in manual position. As per procedure, run up checks are supposed to be carried out and the feathering function of both engines is to be checked simultaneously. However, the pilots in this case only checked No 2 engine's feathering mechanism serviceability manually, contrary to the documented procedures.

At 02:03 UTC, the aircraft was cleared for takeoff and left the runway. Shortly thereafter the right engine flamed out, and the airspeed started to decrease slightly. The First Officer then put the failed engine into feathered position. At this stage, it is considered likely that the pilot monitoring (PM) may have observed only partial feathering. Having made the Pilot Flying (PF) aware of this, the PM made further attempts to fully feather engine number two. This both wasted precious time and, despite being authorised by the captain, was contrary to the documented procedures that no remedial action be taken below 400 ft above ground level. Both airmen are recorded discussing the issue pertaining to Engine No 2, despite this the captain goes on to request the First Officer inform Air Traffic Control (ATC) of an engine failure on takeoff, with the failure in the number one engine. This mistake is indicative of a high stress level within the cockpit, and the breaking down of situational awareness.

The air traffic control gave immediate clearance for an emergency return to Karachi, which was acknowledged by the flight crew. This acknowledgment would be the last contact with the stricken aircraft. Cockpit Voice Recorder (CVR) and Flight Data Recorder (FDR) data indicates that, after the last radio message, the captain observed the First Officer moving the feather control for engine number two, asking "What are you doing?" The first officer replied that the engine was not feathered properly. It seems likely that the first officer became fixated on this one goal, removing all other situational awareness and to the exclusion of other tasks. By this point, the speed of the aircraft was 102 kn with increasing pitch attitude and right angle of bank.

On the CVR recording further reduction in engine sound was observed. Flight Data Recorder (FDR) information showed that bank angle continually increased. The high stress levels of both pilots resulted in near overload and loss of situational awareness. This meant that the asymmetrical thrust caused by full power application to the functional number one engine and lack of thrust from number two, went unnoticed and was not corrected. Landing gear remained extended and airspeed continued to bleed off, rapidly approaching stalling speed.

The cockpit voice recorder noted the beginning of continuous stall warning alerts. The captain is recorded calling out Holy verses from the Quran and "Bismillah (In the name of God)". The ground proximity warning alert, "whoop, whoop", could be heard until the end of the recording.

Investigation and cause

Investigation

An inquiry was ordered into the crash. No evidence was found of a bird strike, pilot incapacitation, sabotage, in-flight structural failure or fire.

The investigation started with the examination on the plane's propellers, as evidence from the cockpit voice recorder (CVR) suggested that an engine failure occurred in mid-flight. Investigators retrieved the propeller from the wreckage and stated that the beta valve in the aircraft may have malfunctioned in mid flight. There are two possibilities of beta valve malfunction: mis-rigging after some maintenance work or fair wear and tear during routine service. Unfortunately, the beta system's integrity and rigging status could not be verified because the propeller governor had been completely consumed in the post ground impact fire. However, it was confirmed from the documented history and the engineering staff that there was neither any reported defect related to the beta system nor was there any scheduled or unscheduled maintenance performed in the recent past. Therefore, the only probable cause of occurrence could be fair wear and tear of the beta valve.

However, investigators stated that even if a mid-air engine failure occurred, the pilots still could have returned to the airport safely. If an aircraft had a mid air engine failure in one engine, the plane still could fly. All twin engine aircraft are designed to sustain a safe flight even if one of the engines has failed or is switched off due to any abnormality, provided the emergency handling procedures are correctly followed. Similarly, the Beechcraft 1900C also had the capability to sustain safe flight with single engine operation. This suggests that pilot error may be the main cause of the accident.

Investigators reviewed the CVR data and stated that the pilot may have lacked situational awareness. After experiencing the abnormal engine No 2 operation, at one stage the cockpit crew indicated confusion about the engine No 1 or 2 and subsequently transmitted incorrect information to the ATC Tower that they were experiencing abnormal operation of engine No 1. The first officer was exposed to a serious level of stress and anxiety when he observed the propeller feathering of No 2 (right) engine. The situation was aggravated due to the fact that the auto feathering was selected to "Off" which entailed the cockpit crew to manually manage feathering of the propeller in case of any anomaly. He did communicate to the captain correct information; however, the captain did not register engine No 2 and told him to inform ATC Tower that they were experiencing problem with engine No 1 and FO communicated the same without questioning the captain or correcting himself. He was mentally preoccupied to a level where he could not perform the recommended remedial action. Thus, he did not effectively contribute towards handling of abnormal set of conditions.

Investigators checking the captain's flight history discovered that his performance during simulator training check flights remained consistently below acceptable levels. He was not able to safely handle training scenarios during critical phases of takeoff and post-takeoff, and was only able to achieve satisfactory performance levels with coaching during these mandatory exercises. The final report stated that the captain suffered from "lack of confidence" and also revealed that the captain lacked the required proficiency and skills to independently handle aircraft operations with a single functioning engine during critical phases of flight.

Investigators concluded that the cockpit crew neither discussed nor raised the landing gear after takeoff. The wreckage also confirmed the landing gear were in the extended position at the time of ground impact. The Beechcraft 1900C aircraft has a very low rate of climb with landing gear in extended position due to increased drag while operating with a single engine. Any banking of the aircraft would aggravate the situation and the marginal rate of climb would degrade into a rate of descent, which happened in this particular case.

In December 2015, Pakistan's Safety Investigation Board released their final report stating that the accident was caused by the inability of the captain to handle the abnormal operation of engine No 2 just after takeoff, failure of the cockpit crew to raise the landing gear after experiencing the engine anomaly, and execution of remedial actions by the first officer before the attainment of minimum safe altitude. The crew did not follow standard procedures, lacked situational awareness, displayed poor crew resource management, and handled the anomaly unprofessionally.

Text from the Wikipedia article “JS Air Flight 201” (revision 1356646772, 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

On November 5, 2010, a JS Air Pakistan, a Hawker Beechcraft B-1900, registration AP-BJD, crashed shortly after takeoff from Karachi-Jinnah International Airport (KHI), Karachi, Pakistan. All 17 passengers and 4 crewmembers onboard were fatally injured, and the airplane was destroyed. The charter flight was destined for an oil field in Bhit Shah, Pakistan.

The investigation is being conducted by the Pakistan Safety & Investigation Board, Civil Aviation Authority. The NTSB has appointed an Accredited Representative to assist the investigation under the provisions of ICAO Annex 13 as the Country of Manufacture and Design of the airplane.

All requests for information should be directed to:

Investigation Safety Board Headquarters Civil Aviation Authority Terminal 1, Jinnah International Airport Karachi 75200

Verbatim NTSB factual narrative from the NTSB dataset

Sources

Wikipedia article: JS Air Flight 201
Article
JS Air Flight 201
Revision
1356646772 · 2026-05-29 · retrieved 2026-09-18
Wikidata
Q4055775
Licence
Text CC BY-SA 4.0, by the article's authors; Wikidata CC0; town positions GeoNames (CC BY 4.0)
NTSB record DCA11WA008
Event ID
20101116X32303
Case number
DCA11WA008
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Where each value comes from
Record
Wikipedia article "JS Air Flight 201" (page 29481324, revision 1356646772); merged with NTSB case DCA11WA008 (events / aircraft)
Date
Wikipedia infobox: date; matches the Safety Investigation Board (SIB), Civil Aviation Authority Pakistan (investigation authorised by Ministry of Defence) final report
Place and country
Wikipedia infobox: site
Map position
Wikipedia: Wikipedia article coordinates
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 DCA11WA008
Operation
flight number in the article title
Fatalities
Wikipedia: Wikipedia infobox: aircraft fatalities; matches the Safety Investigation Board (SIB), Civil Aviation Authority Pakistan (investigation authorised by Ministry of Defence) final report
Ground fatalities
Safety Investigation Board (SIB), Civil Aviation Authority Pakistan (investigation authorised by Ministry of Defence) final report
Summary
Wikipedia infobox: summary
Source notes (3)
  • One occurrence in two sources, merged: the Wikipedia article "JS Air Flight 201" and NTSB case DCA11WA008, 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 Safety Investigation Board (SIB), Civil Aviation Authority Pakistan (investigation authorised by Ministry of Defence) final report on 2026-09-18. The report states the same date, fatalities, registration, operator, departure, destination and damage. Taken from the report: ground fatalities. Not checked: place, crash-site coordinates, flight number, aircraft type and type of operation.