Country
code

Haryana

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:

Crash of an Ilyushin II-76TD in Charkhi Dadri: 37 killed

Date & Time: Nov 12, 1996 at 1840 LT
Type of aircraft:
Operator:
Registration:
UN-76435
Flight Phase:
Survivors:
No
Schedule:
Shymkent - New Delhi
MSN:
10234 13428
YOM:
1992
Flight number:
KZA1907
Country:
Region:
Crew on board:
10
Crew fatalities:
Pax on board:
27
Pax fatalities:
Other fatalities:
Total fatalities:
37
Captain / Total flying hours:
9229
Captain / Total hours on type:
1488.00
Copilot / Total flying hours:
6822
Copilot / Total hours on type:
409
Aircraft flight hours:
2643
Circumstances:
The Ilyushin II-76TD departed Shymkent Airport on a regular schedule service (flight KZA1907) to New Delhi-Indira Gandhi, carrying 27 passengers and 10 crew members. Following an uneventful flight, the crew was cleared to start the descent to New Delhi via route G452 and was instructed to maintain FL150. At 1833LT, a Boeing 747-168B operated by Saudi Arabian Airlines (Saudia) departed New Delhi-Indira Gandhi Airport on a flight to Jeddah (flight SV763) with an intermediate stop in Dhahran, carrying 289 passengers and 23 crew members. After takeoff, its crew was instructed to climb to FL140 via the same route G452. For unknown reasons, the Kazair crew continued the descent below FL150 until both aircraft faced each other and collided at 1840LT at FL140, seven minutes after the B747 takeoff. After the collision, both aircraft entered an uncontrolled descent and crashed in an open field located about 3 km Charkhi Dadri, some 80 km west of New Delhi-Indira Gandhi Airport. Both aircraft were destroyed by impact forces and a post crash fire and all 349 occupants in both aircraft were killed.
Probable cause:
It was determined that the collision was the consequence of the failure of the Kazair crew to follow the assigned altitude of 15,000 feet while approaching New Delhi. The crew of the Kazair II-76 was instructed by ATC to continue the descent to Indira Gandhi Airport via the same route G452 but at an altitude of 15,000 feet (14,000 feet for the Saudia B747). For unknown reasons, the Kazair crew continued the descent below FL150 without clearance until both aircraft faced each other and collided. During the minutes preceding the accident, both Kazair and Saudia crew have been informed by ATC about other traffic.
Final Report:

Crash of a Boeing 747-168B in Charkhi Dadri: 312 killed

Date & Time: Nov 12, 1996 at 1840 LT
Type of aircraft:
Operator:
Registration:
HZ-AIH
Flight Phase:
Survivors:
No
Schedule:
New Delhi - Dhahran - Jeddah
MSN:
22748
YOM:
1982
Flight number:
SV763
Country:
Region:
Crew on board:
23
Crew fatalities:
Pax on board:
289
Pax fatalities:
Other fatalities:
Total fatalities:
312
Captain / Total flying hours:
9837
Captain / Total hours on type:
104.00
Copilot / Total flying hours:
7779
Copilot / Total hours on type:
1952
Aircraft flight hours:
40035
Aircraft flight cycles:
14927
Circumstances:
The aircraft departed New Delhi-Indira Gandhi Airport at 1833LT on a flight to Jeddah with an intermediate stop in Dhahran, carrying 289 passengers and 23 crew members. After takeoff, the crew was instructed to climb to FL140 via route G452. Seven minutes after takeoff, while cruising at an altitude of 14,000 feet, the aircraft collided with a Kazakhstan Airlines (Kazair) Ilyushin II-76TD that was descending to New Delhi Airport. Registered UN-76435, it was completing flight KZA1907 from Shymkent with 27 passengers and 10 crew members on board. After the collision, both aircraft entered an uncontrolled descent and crashed in an open field located about 3 km Charkhi Dadri, some 80 km west of New Delhi-Indira Gandhi Airport. Both aircraft were destroyed by impact forces and a post crash fire and all 349 occupants in both aircraft were killed.
Probable cause:
It was determined that the collision was the consequence of the failure of the Kazair crew to follow the assigned altitude of 15,000 feet while approaching New Delhi. The crew of the Kazair II-76 was instructed by ATC to continue the descent to Indira Gandhi Airport via the same route G452 but at an altitude of 15,000 feet (14,000 feet for the Saudia B747). For unknown reasons, the Kazair crew continued the descent below FL150 without clearance until both aircraft faced each other and collided. During the minutes preceding the accident, both Kazair and Saudia crew have been informed by ATC about other traffic.
Final Report:

Crash of a Douglas C-47A-45-DL in Badkhalsa: 8 killed

Date & Time: May 19, 1978 at 1212 LT
Registration:
VT-DEU
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
New Delhi - New Delhi
MSN:
9952
YOM:
1943
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
8
Circumstances:
The airplane was engaged in a calibration flight at New Delhi-Palam Airport on behalf of the Indian Civil Aviation Authority. While cruising at a relative low altitude, the airplane suffered an engine failure. It banked left, lost height and crashed in flames about 40 km north of Palam Airport. All eight occupants were killed.
Probable cause:
In-flight failure of the left engine due to the dysfunction of the fuel pump at a critical stage of flight.

Crash of an Avro 685 York C.1 in Gurgaon: 4 killed

Date & Time: May 25, 1958
Type of aircraft:
Operator:
Registration:
G-AMUV
Flight Type:
Survivors:
Yes
Schedule:
Karachi – New Delhi
MSN:
MW226
YOM:
1946
Location:
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
4
Circumstances:
While approaching New Delhi-Palam Airport on a cargo flight from Karachi, the crew reported an engine fire. The captain realized it would not be possible to reach the airport so he decided to attempt an emergency landing in Gurgaon, about 15 km south of the capital city airport. The airplane crash landed in a field, slid for dozen yards, struck several obstacles and came to rest in flames. A crew member was rescued while four others were killed. The aircraft was destroyed.
Probable cause:
Failure of the engine number one that caught fire and exploded.

Crash of a Consolidated LB-30 Liberator VIII near Gurgaon: 4 killed

Date & Time: Mar 29, 1946
Operator:
Registration:
EW630
Flight Type:
Survivors:
Yes
Location:
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
4
Circumstances:
Enroute, a fire erupted in the front of the cabin and the crew decided to divert to New Delhi-Safdarjung Airport. On approach, the aircraft on fire went out of control and crashed in a field located east of Gurgaon. Four occupants were killed while both pilots were injured.
Probable cause:
The exact cause of the in-flight fire could not be determined with certainty.

Crash of a Bristol 142 Blenheim I at Ambala AFB

Date & Time: Jul 6, 1940
Type of aircraft:
Operator:
Registration:
L8520
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Ambala - Ambala
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The crew was completing a local training flight at Ambala AFB. During the takeoff roll, a tyre burst. The pilot-in-command lost control of the airplane that veered off runway, lost its undercarriage and came to rest. All three crew members evacuated safely and the aircraft was damaged beyond repair.
Probable cause:
Loss of control during takeoff after a tyre burst.