Crash of a Beechcraft 200 Super King Air in New Delhi: 10 killed

Date & Time: Dec 22, 2015 at 0938 LT
Operator:
Registration:
VT-BSA
Flight Phase:
Survivors:
No
Site:
Schedule:
New Delhi - Ranchi
MSN:
BB-1485
YOM:
1994
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
8
Pax fatalities:
Other fatalities:
Total fatalities:
10
Captain / Total flying hours:
964
Captain / Total hours on type:
764.00
Copilot / Total flying hours:
891
Copilot / Total hours on type:
691
Aircraft flight hours:
4766
Aircraft flight cycles:
2745
Circumstances:
Beechcraft Super King Air B-200 aircraft, VT-BSA belonging to BSF Air Wing was involved in an accident on 22.12.2015 while operating a flight from IGI Airport, New Delhi to Ranchi. The flight was under the command of a CPL holder with another CPL holder as Second-in-Command. There were ten persons on board including two flight crew members. As per the scheduling procedure of the Operator, the flying programme for 22.12.2015 was approved by the ADG (Logistics) on the recommendation of the DIG (Air) for VT-BSA on 21.12.2015. The programme included names of the flight crew along with the following sectors: from Delhi to Ranchi ETD 0800 ETA 1030 and from Ranchi to Delhi ETD 1300 ETA 1600. The task was as per instructions on the subject dated 23rd July 2015. As per the weight & load data sheet there were 8 passengers with 20 Kgs. of baggage in the aft cabin compartment. The actual take-off weight shown was 5668.85 Kgs as against the maximum take-off weight of 5669.9 Kgs. Fuel uplifted was 1085 Kgs. The aircraft was taken out of hangar of the Operator at 0655 hrs on 22.12.2015 and parked outside the hangar for operating the subject flight. At around 0745 hrs, the passengers reached the aircraft who were mainly technical personnel supposed to carry out scheduled maintenance of Mi-17 helicopter of the Operator at Ranchi. They were carrying their personnel baggage along with tools and equipment required for the maintenance. At around 0915 hrs the flight crew contacted ATC Delhi and requested for clearance to operate the flight to Ranchi. The aircraft was cleared to Ranchi via R460 and FL210. Runway in use was given as 28. At 0918 hrs the doors were closed and the flight crew had started carrying out the check list. After the ATC issued taxi clearance, the aircraft had stopped for some time after commencing taxiing. The pilot informed the ATC that they will take 10 minutes delay for further taxi due to some administrative reasons. The taxi clearance was accordingly cancelled. After a halt of about 6 to 7 minutes, the pilot again requested the ATC for taxi clearance and the same was approved by the ATC. Thereafter, the aircraft was given take-off clearance from runway 28. The weather at the time of take-off was: Visibility 800 meters with Winds at 100°/03 knots. Shortly after take-off and attaining a height of approximately 400 feet AGL, the aircraft progressively turned left with simultaneous loss of height. It had taken a turn of approximately 180o and impacted some trees before hitting the outside perimeter road of the airport in a left bank attitude. Thereafter, it impacted 'head on' with the outside boundary wall of the airport. After breaking the outside boundary wall, the wings impacted two trees and the aircraft hit the holding tank of the water treatment plant. The tail portion and part of the fuselage overturned and went into the water tank. There was post impact fire and the portion of the aircraft outside the water tank was destroyed by fire. All passengers and crew received fatal injuries due impact and fire. The ELT was operated at 0410 hours UTC (0940 hours IST). The fire fighting team reached the site and extinguished the fire. The bodies were then recovered from the accident site. 08 bodies were recovered from the holding tank of the water treatment plant and bodies of both pilots were recovered from the heavily burnt portion of the cockpit lying adjacent (outside) to the wall of the holding tank of the water treatment tank.
Probable cause:
The accident was caused due to engagement of the autopilot without selecting the heading mode by the flight crew just after liftoff (before attaining sufficient height) in poor foggy conditions and not taking corrective action to control the progressive increase in left bank; thereby, allowing the aircraft to traverse 180° turn causing the aircraft to lose height in a steep left bank attitude followed by impact with the terrain.
Final Report:

Crash of a Boeing 737-4Y0 in Kabul

Date & Time: May 8, 2014 at 1704 LT
Type of aircraft:
Operator:
Registration:
YA-PIB
Survivors:
Yes
Schedule:
New Delhi – Kaboul
MSN:
26077/2425
YOM:
1993
Flight number:
FG312
Location:
Country:
Region:
Crew on board:
10
Crew fatalities:
Pax on board:
122
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Following an uneventful flight from New Delhi-Indira Gandhi Airport, the crew was cleared for an ILS approach to Kabul Airport Runway 29. On short final, the aircraft entered an area of heavy rain falls. The crew continued the approach and the aircraft landed after the touchdown zone. Unable to stop within the remaining distance, the aircraft overran, lost its undercarriage, collided with the ILS antenna and slid for 285 metres before coming to rest. All 132 occupants evacuated safely and the aircraft was damaged beyond repair.
Probable cause:
It was determined that the crew completed the landing too far down the runway, reducing the landing distance available. The following contributing factors were identified:
- The crew failed to follow SOP's,
- Poor crew recurrent training,
- The thrust reverse systems were activated too late after landing.

Crash of an Airbus A320-231 in Jaipur

Date & Time: Jan 5, 2014 at 2110 LT
Type of aircraft:
Operator:
Registration:
VT-ESH
Survivors:
Yes
Schedule:
Imphal – Guwahati – New Delhi
MSN:
469
YOM:
1994
Flight number:
AI890
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
173
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
8322
Captain / Total hours on type:
5502.00
Copilot / Total flying hours:
2798
Copilot / Total hours on type:
2610
Aircraft flight hours:
55705
Circumstances:
On 05.01.2014, Air India Ltd. Airbus A-320-231 aircraft was scheduled to operate flight AI-889 (Delhi – Guwahati – Imphal) and return flight, AI-890 (Imphal – Guwahati – Delhi). Air India dispatch section at Delhi, which has received the roster of flight crew for the flights, had prepared the operational and ATC flight plans by using FWz flight planning software and taking into account the weight & weather (forecast winds). Same set of flight crew and cabin crew was rostered to operate the four sectors mentioned above. The flight was under Command of an ATPL holder with another ATPL holder as First Officer (FO) and 04 Cabin Crew members. The Commander was CAT III qualified and the FO was CAT I qualified. The FWz plan was prepared for VT-ESL, but later on the aircraft was changed to VT-ESH. As per the pilot in command as both the aircraft have bogie gear type of landing gear and the performance factor is also same for these aircraft, he had accepted the FWz plan of VT-ESL. As per the manager flight dispatch on duty, only first leg i.e. Delhi Guwahati was dispatched. Required fuel figures were informed to the engineering & commercial departments. Pilots were briefed with folders which in addition to flight plans contained current NOTAMs and meteorological information. The relevant information in these documents was highlighted for briefing to the flight crew. For the remaining sectors which were self briefing sectors flight plan and NOTAMs were given to the flight crew. As per the pre flight briefing register, both the crew members have visited the flight dispatch section for briefing and at around 10:40 hrs. IST have signed the dispatch register. The sectors Delhi – Guwahati – Imphal – Guwahati were as per schedule and were uneventful. As per the flight sector report, the transit time at Guwahati prior to Guwahati-Delhi sector was 50 minutes. The aircraft landed at Guwahati from Imphal at 11:15 hrs. UTC and 12.7 tons of fuel was uplifted. The filed alternates for the sector were Lucknow and Jaipur in that order. METARs of Delhi, Lucknow and Jaipur were provided at Guwahati. There was no specific briefing. Flight crew has taken the weather updates of destination and alternates before departure from Guwahati. Lucknow visibility at that time was 2000 meters with temperature and dew point of 18°C & 13°C respectively. The weather at Delhi (11:05 UTC) was RVR as 500 meters for runway 29, general visibility of 150 meters, with both temperature and dew point of 12°C. A speci was issued at 1130 UTC for Jaipur with winds 04 kts. visibility 3000m and haze. There was no significant clouding (NSC), temperature (T) 18°C & dew point (Dp) 13°C, QNH 1013. Pre flight walk around inspection was carried out by the crew at Guwahati and the aircraft was released by an Aircraft Maintenance Engineer which was accepted by the Pilot-in-command. There was no snag or technical problem with the aircraft. There was no component or system released under Minimum Equipment List (MEL). For its last leg, the aircraft departed Guwahati for Delhi at 1205 UTC with 173 passengers on board. The fuel requirement from Guwahati to Delhi with 179 persons on board was 12.2 tonnes. As per the commander of flight, additional 500 kgs of fuel was taken (total on board was 12.7 tonnes) considering the time of arrival in Delhi was that of traffic congestion and because of weather in Delhi. As per the Operational Flight Plan (OFP), there was 10 minutes of arrival delay at the destination. The aircraft was flown on managed speeds. Initially the flight was cleared by ATC for a lower level and was later on cleared to fly at cruising level of 340. The fuel was checked visually on the Flight Management System (FMS) and Fuel Page which was further cross checked with the OFP planned figures by the crew on way points but was not recorded on the Operational Flight Plan. As per the crew, the fuel consumed was marginally higher than planned. The time taken to reach the way points was also noted, which was almost the same as planned figures were. Enroute, there was no briefing about traffic congestion over Delhi by any of the ground stations of AAI. The crew, on reaching overhead Lucknow, has taken Lucknow weather and when the aircraft was in range of ATIS Delhi, Delhi ATIS weather was also copied. The aircraft was not equipped with Aircraft Communications Addressing and Reporting System (ACARS) but was provided with HF/VHF system. As per the flight crew no flight following was provided either by flight dispatch or the IOCC of Air India. Weather updates were not seeked by the crew from the flight dispatch nor were any updates provided by Flight dispatch to the aircraft during the flight except when crew had asked Delhi dispatch about Jaipur visibility before finally making the decision to divert to Jaipur. Flight crew did not seek any update of Delhi or Jaipur weather till the time the aircraft came in contact with Delhi ATC. While in contact with Delhi ATC, the flight was advised to join hold as Delhi visibility Runway 28 RVR had dropped to the lower end of CAT I operations at this point runway 29 was below minima. AI 890 was number 12 in sequence and continued to remain in the holding pattern for the next 20-25 minutes. During this period there was no attempt on the part of flight crew to seek Lucknow weather. Air India Flight dispatch has also not given any advice to the flight about Jaipur or Lucknow weather. The weather (visibility / RVR) reported on Runway 29 was below CAT I conditions so runway was not available for this flight at that moment as the First Officer was only Cat I qualified. As per commander of the flight, they did 03 holds each of 1.5 minutes leg and flew headings 360° and 180° before intercepting the localizer Runway 28 at 35 miles. RVR runway 28 also dropped below Cat. I minimas, therefore the crew discontinued approach and climbed to 8000 feet on runway heading before going on heading 180. As per the Commander, though the 1st planned diversion alternate was Lucknow which had visibility of 2000 m i.e. above minima, but change of diversion to Jaipur was made as after missed approach they were closer to Jaipur and they had inquired about the visibility from Dispatch for Jaipur, which was provided as 2000 m. At this stage the crew did not check complete weather of Jaipur. Minimum diversion fuel to Jaipur was 2.9 tonnes as per FWz CFP. AI-890 commenced diversion to Jaipur with ―Fuel on Board‖ of 3.1 tonnes. As per the Station Manager of Air India at Jaipur Airport, he received a call from their Executive Director, Northern Region at around 2040 hrs. IST on 05.01.2014 that due to Delhi weather, AI 890 had diverted to Jaipur. He then conveyed the same to the airport office and the concerned engineer. The aircraft came in contact with Jaipur for the first time when it was at 68 DME from Jaipur. At that time the crew came to know of the complete weather of Jaipur from ATIS as visibility of 900 m, Dew Point as 13°C, temperature as 13°C, and RVR of 1000m. At 60 miles and passing flight level 138, the crew intimated Jaipur that the aircraft is descending for flight level 100 as cleared by Delhi control, which was acknowledged by Jaipur ATC. The aircraft again informed Jaipur ATC its position at 55 miles, 50 miles and 42 miles from Jaipur which were also acknowledged by Jaipur ATC. During these contacts, weather of Jaipur was neither asked by the crew nor provided by the ATC. When the aircraft was at flight level 83, the crew asked ATC Jaipur to confirm that they can carry out ILS approach for runway 27 via 10 DME arc. While confirming the requested approach, Jaipur ATC has informed all the stations about the weather at that moment as visibility 400 m and RVR 1000 m. When the aircraft was at 30 miles from Jaipur, Jaipur ATC passed weather as visibility 400 m, RVR 1000 m and trend visibility becoming 350 m. The crew was asked to come overhead by Jaipur ATC. At 28 DME from Jaipur, the aircraft was maintaining 6000 feet and on request was cleared by Jaipur ATC to descend to 5000 feet. When the aircraft was at 25 DME, from Jaipur, ATC advised that the weather was deteriorating rapidly and visibility was 400 meters. The crew however intimated the ATC that they were committed to land at Jaipur due fuel. As per the crew the fuel on board at that point of time was 2.6 tonnes (approx.) and approach was commenced for Jaipur with a visibility of 500 m with trend reducing. The aircraft was no. 2 in approach at Jaipur and was cleared for VORDME arc ILS approach runway 27 at 25 nm. Crew had, as per them, checked Ahmedabad distance as 291 nm, with a fuel calculation of 2.7 tonnes and as sufficient fuel was not available for Ahmedabad so did not consider diverting to Ahmedabad at that moment. Crew has also stated that Udaipur watch hours were not available with them, Jodhpur is an Air Force field with restrictions and Delhi was packed so they continued approach to Jaipur knowing that visibility / RVR was rapidly deteriorating. Due to reducing visibility, Jaipur ATC asked all the aircraft inbound for Jaipur to come over head and join JJP hold. The crew of the subject flight asked for the weather which was provided as visibility 400 m & RVR 1000 m though RVR deteriorating to 550 m. The flight from the ―Arrival Route‖ flew the VORDME arc for ILS runway 27. The ATC had transmitted the RVR as 200 m and visibility as 50 m with trend reducing. Another scheduled flight ahead of AI-890 carried out a missed approach and diverted to Ahmedabad. When the aircraft was above MDA (1480 feet AGL), ATC reported RVR 50 m and cleared the aircraft to land subject to minima. Both the flight crew maintained that they had seen the runway lights. ILS approach was performed with dual AP until 200ft RALT. After descending below MDA on auto pilot, the commander disconnected the auto pilot. Captain performed the final approach manually. The aircraft deviated to the left of the runway centre line and touched down on soft ground (in kutcha) on the LH side of the runway. During touchdown and landing roll, the visibility was zero and crew were unable to see any of the reference cues. The crew had heard rumbling sound during landing roll. As per the commander, he did the manual landing as he was not sure if he could do auto-land on a ground facility which is CAT I certified airfield in actual zero visibility. The aircraft continued to roll/ skid on the unpaved surface and during this period the left wing impacted trees causing damage to the left wing. Thereafter aircraft turned right and entered the runway finally coming to a halt on the LH side of runway. There was no fire. ATC Jaipur informed the Airport Manager of the Airline at Jaipur that their flight AI-890 had blocked the runway and also requested them to send equipments / manpower to attend the aircraft and get the aircraft removed. The Station AME of the airline alongwith the Asst Officer (Comm.), who was at the tarmac were instructed by the Station Manager to move to the aircraft. As per the AME, the visibility was almost nil and they could not move without the help of ‗Follow Me‘ Jeep. The ATC was informed to arrange the jeep to escort the personnel upto the aircraft. The AME after reaching the aircraft observed that the no. 1 main wheel of the aircraft had decapped/ damaged and the port side wing was damaged. The fuel remaining on board was 2400 kgs. The disembarkation of passengers was carried out on the runway itself and passengers were sent to the terminal building. Since the aircraft was not in a position to be either taxied or towed to the parking bay, the baggage of passengers was offloaded at the runway itself and sent to the terminal. One passenger suffered minor bruise on the knuckle of his right hand middle finger. He was attended to by the cabin crew in the aircraft and also by the doctor at the airport. Medical check-up of all the crew members including breathanalyser (BA) test was done by the medical officer, M.I. room Jaipur airport. The BA test was negative for all the crew members with a reading of 00.00. Since the aircraft was obstructing the runway, the airport was shut down for any further flight operations till the runway could be cleared. A NOTAM was issued to this effect. The aircraft was towed the next day to parking bay no.5 at terminal-1 by 1200 hrs and was later repositioned on a non-operational remote bay.
Probable cause:
The cause below has been given considering events as a combination of organizational factors and human error.
- The flight crew made an erroneous decision of diverting & continuing to an airfield with reducing visibility.
- The flight crew attempted a manual landing in below minima conditions.
- Lack of operational supervision and desired ground support to flight.
- Internal quality assurance not capturing the hazards which slipped through due complacency.
- Lack of oversight of the flight operations.
Final Report:

Crash of a Raytheon 390 Premier IA in New Delhi

Date & Time: Sep 22, 2012 at 1129 LT
Type of aircraft:
Operator:
Registration:
VT-UPN
Flight Type:
Survivors:
Yes
Schedule:
Lucknow - New Delhi
MSN:
RB-236
YOM:
2008
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The aircraft departed Lucknow Airport in the morning on a flight to New Delhi-Indira Gandhi Airport with a crew of three (two pilot and a cabin crew) and three passengers, among them Shivpal Yadav, Minister by the Uttar Pradesh Government. Following an uneventful flight, the crew completed the approach to runway 27. After touch down, the left main gear collapsed and the aircraft slid on runway for about one km when the right main gear collapsed as well. Out of control, the aircraft veered off runway to the right and came to rest in a grassy area. All six occupants escaped uninjured while the aircraft was damaged beyond repair.

Crash of a Pilatus PC-12/45 in Faridabad: 10 killed

Date & Time: May 25, 2011 at 2243 LT
Type of aircraft:
Operator:
Registration:
VT-ACF
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Patna - New Delhi
MSN:
632
YOM:
2005
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
10
Captain / Total flying hours:
1521
Captain / Total hours on type:
1300.00
Copilot / Total flying hours:
300
Copilot / Total hours on type:
70
Aircraft flight hours:
1483
Circumstances:
M/s Air Charter Services Pvt Ltd. offered their aircraft VT-ACF for operating medical evacuation flight to pick one critically ill patient from Patna on 25/05/2011. The Aircraft took off from Delhi to Patna with two crew members, two doctors and one male nurse. The Flight to Patna was uneventful. The Air Ambulance along with patient and one attendant took off from Patna at 20:31:58 IST, the aircraft during arrival to land at Delhi crashed near Faridabad on a Radial of 145 degree and distance of 15.2 nm at 22:42:32 IST. Aircraft reached Patna at 18:31 IST. Flight Plan for the flight from Patna to Delhi was filed with the ATC at Patna via W45-LLK-R594 at FL260, planned ETD being 22:00 hours IST and EET of 2hours for a planned ETA at VIDP being 24:00 hours IST. The crew took self-briefing of the weather and same “Self Briefing” was recorded on the flight plan submitted at ATC Patna. The passenger manifest submitted at Patna indicated a total of 2 crew and 5 passengers inclusive of the patient. Weather at Patna at the time of departure was 3000m visibility with Haze. Total fuel on board for departure at Delhi was 1516 lts. The preflight/transit inspection of the aircraft at Patna was carried out by the crew as per laid down guidelines. The crew requested for startup at 20:21 IST from Patna ATC and reported airborne at 20:33:43 IST. The aircraft climbed and maintained FL 260 for cruise. On handover from Varanasi Area Control (Radar), the aircraft came in contact with Delhi Area Control (East) Radar at 21:53:40 IST at 120.9 MHz. At 21:53:40 IST aircraft was identified on Radar by squawking code 3313. At 22:02:05 IST the crew requested for left deviation of 10° due to weather, the same was approved by the RSR controller. At 22:05:04 IST the crew informed that they have a critical patient on board and requested for priority landing and ambulance on arrival. The same was approved by the RSR controller. The aircraft was handed over to Approach Control on 126.35 MHz at 22:28:03 IST. At 22:28:18 IST VT-ACF contacted TAR (Terminal Approach Radar) on 126.35 MHz and it was maintaining FL160. At 22:32:22 IST, VT-ACF was asked to continue heading to DPN (VOR) and was cleared to descend to FL110. At 22:36:34 IST, the TAR controller informed VT-ACF about weather on HDG 330°, the crew replied in “Affirmative” and requested for left heading. At 22:38:12 IST, TAR controller gave aircraft left heading 285° which was copied by the aircraft. The aircraft started turning left, passing heading 289, it climbed from FL125 to FL141. At 22:40:32 IST the TAR controller gave 3 calls to VT-ACF. At 22:40:43 IST aircraft transmitted a feeble call “Into bad weather”, at that instance the aircraft had climbed FL 146.Thereafter the aircraft was seen turning right in a very tight turn at a low radar ground speed and loosing height rapidly from FL146 to FL 016. Again at 22:41:32 IST TAR controller gave call to VT-ACF, aircraft transmitted a feeble call “Into bad weather. Thereafter the controller gave repeated calls on both 126.35 MHz and also 121.5 MHz, before the blip on radar became static on a radial of 145 degree at 15.2 nm from DPN VOR at 22:42:32 IST. All attempts to raise contact with the aircraft failed. The TAR controller then informed the duty WSO and also the ATC Tower. At 22:50:00 IST, the tower informed the WSO that they have got a call from the City Fire Brigade confirming that an aircraft has crashed near Faridabad in a congested residential area known as Parvatia Colony. After the accident, local residents of the area and police tried to put off the fire and extricate the bodies from the wreckage of the aircraft.
Probable cause:
The probable cause of the accident could be attributed to departure of the aircraft from controlled flight due to an external weather related phenomenon, mishandling of controls, spatial disorientation or a combination of the three.
Final Report:

Ground accident of an Airbus A300B2-101 in New Delhi

Date & Time: Mar 8, 2002 at 0315 LT
Type of aircraft:
Operator:
Registration:
VT-EFW
Flight Phase:
Flight Type:
Survivors:
Yes
MSN:
111
YOM:
1980
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
A group of five technicians/engineers of the company was preparing the aircraft to be transferred to a hangar for maintenance. After engine startup, the power was reduced to idle after someone inadvertently pulled out the circuit breaker. The aircraft jumped the chocks and started to roll. Since the engine's power was in idle, the brakes and the nosewheel steering system were inoperative. The crew elected to reduce power on the left engine but mistakenly increased the power on the right engine by 90%. This caused the aircraft to rotate 80° when control was lost. The airplane rolled through a perimeter wall, causing the nose gear to collapse. All five occupants escaped uninjured while the aircraft was damaged beyond repair.

Crash of a Beechcraft B200C Super King near Kulu-Bhuntar: 5 killed

Date & Time: Jul 29, 2000 at 1332 LT
Registration:
VT-EIE
Flight Type:
Survivors:
No
Site:
Schedule:
New Delhi – Kulu-Bhuntar
MSN:
BL-63
YOM:
1983
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
5
Captain / Total flying hours:
8340
Captain / Total hours on type:
776.00
Copilot / Total flying hours:
526
Aircraft flight hours:
6243
Aircraft flight cycles:
5646
Circumstances:
The twin engine aircraft departed New Delhi-Indira Gandhi Airport on an ambulance flight to Kulu-Bhuntar, carrying three doctors and two pilots. While descending to Kulu-Bhuntar Airport in IMC conditions, the crew failed to realize his altitude was insufficient when the aircraft struck the slope of a mountain located 20 km from the destination airport. The aircraft was destroyed and all five occupants were killed.
Probable cause:
The pilot descended below minimum sector altitude in Instrument Meteorological Condition in hilly area.
Contributing factors were:
1. ATC Chandigarh contributed to the accident by permitting IFR flight to descend below minimum sector altitude.
2. Inadequate Supervision, Lack of Safety culture and poor pre-flight planning. Factor: Pilot: Non-adherence to standard operating procedure.
Final Report:

Crash of a Boeing 727-243F in Kathmandu: 5 killed

Date & Time: Jul 7, 1999 at 1951 LT
Type of aircraft:
Operator:
Registration:
VT-LCI
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Katmandu – New Delhi – Sharjah
MSN:
22168
YOM:
1981
Flight number:
LCI8533
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
5
Aircraft flight hours:
43000
Aircraft flight cycles:
25000
Circumstances:
The aircraft departed Kathmandu-Tribhuvan Airport on a cargo flight to Sharjah with an intermediate stop in New Delhi, carrying five crew members and a load of 21 tons of woolen carpets. After takeoff from runway 20, the crew continued to climb but failed to realize his altitude was insufficient. The aircraft struck the slope of Mt Champadevi located 11 km southwest of the airport and disintegrated on impact. All five crew members were killed.
Probable cause:
The accident occurred as the crew after take off did not adhere to the published Standard Instrument Departure (SID) procedure for runway 20 at Kathmandu, Nepal.
The following contributory factors were identified:
- Incomplete departure briefing given by P1 while other cockpit activities were in progress,
- The unexpected airspeed decay to V 2 -3 during initial right climbing turn South of the VOR which occurred while P2 was busy with ATC,
- The improper power and climb profile used by P1 after rolling the aircraft out on a southwest heading following the initial airspeed loss,
- The inadequate intra cockpit crew coordination and communication as the aircraft proceeded to and across the KTM VOR 4 DME arc before recommencing a shallow right turn, and
- The incorrect and slow response to the initial and subsequent GPWS activation prior to the collision with the terrain.

Crash of an Antonov AN-32 in New Delhi: 21 killed

Date & Time: Mar 7, 1999 at 0822 LT
Type of aircraft:
Operator:
Registration:
K2673
Flight Type:
Survivors:
No
Site:
Schedule:
Gwalior – New Delhi – Pokhran
MSN:
108
YOM:
1984
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
14
Pax fatalities:
Other fatalities:
Total fatalities:
21
Circumstances:
While descending to New Delhi-Indira Gandhi Airport runway 10, the crew encountered poor visibility due to thick fog and requested ATC assistance. On short final, the crew failed to realize his altitude was insufficient when the aircraft struck successively a concrete water tank and power cables then crashed in the Pappankalan district, about 2,4 km short of runway. The aircraft and a building were destroyed. All 18 occupants were killed as well as three people on the ground.
Probable cause:
The crew was completing the final approach below the minimum safe altitude in reduced visibility due to thick fog.

Crash of a Beechcraft F90 King Air in Bhilainagar: 6 killed

Date & Time: Feb 2, 1998 at 1916 LT
Type of aircraft:
Operator:
Registration:
VT-ELZ
Survivors:
No
Schedule:
New Delhi - Bhilainagar
MSN:
LA-233
YOM:
1985
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
6
Captain / Total flying hours:
7790
Circumstances:
SAIL King Air F90 aircraft VT-ELZ was involved in an accident near Bhilai Airfield on 02-02-98 during private flight from I.G.I. Airport, New Delhi to Bhilai Airfield. The pilot while on direct track to Bhilai at 76 DME from Raipur and FL070 insisted for further descent reporting bad weather. ATC Raipur cleared him for descend to 2,700 feet on QNH of Raipur i.e. below MORA and MSA. On descending the navigation and communication guidance became intermittent and unreliable. Due to severe weather activities the aircraft diverted 40 NMs right of the track. The pilot while steering in the Easterly direction i.e. towards the destination in the darkness on the evening hours flew into rising terrain and collided with a hill resulting into fatal injuries to all the occupants
and post accident fire. Aircraft was completely destroyed. Crash occurred 10 minutes to ETA.
Probable cause:
The aircraft in flight collided with rising terrain when the pilot flew below the height of the hill top during circumnavigating bad weather and attempting to reach destination by maintaining visual contact with ground. Weather, disregard to standard operating procedures and night flying were considered as contributing factors.
Final Report: