Showing posts with label Accident. Show all posts
Showing posts with label Accident. Show all posts

Video of Asiana crash shows plane cart-wheeling after impact

by Devesh Agarwal

A dramatic video recently released by the United States National Transportation Safety Board (NTSB), of the crash of Asiana Airlines Boeing 777 HL7742 performing flight OZ-214 at San Francisco airport shows the plane cart-wheeling after it impacted the sea-wall of the runway.



Update December 13, 2013

Another video of the incident.
Read more »

ATR 72-600 suffers first fatal crash

by Devesh Agarwal

Lao Airline ATR72-600. Photo courtesy ATR.
Airbus joint-venture subsidiary ATR (Aerei da Trasporto Regionale or Avions de transport régional) suffered the first fatal crash of the ATR 72-600 aircraft it manufactures.

The airframer confirmed that an ATR 72-600 operated by Lao Airlines as flight QV301 from capital Vientiane to Pakse crashed at around 16:00 (09:00 UTC) near Pakse (Laos).

All 44 passengers and 5 crew members on board perished.

The aircraft, registered RDPL-34233, was MSN (Manufacturing Serial Number) 1071, was delivered from the production line in March 2013.

At this time, the circumstances of the accident are still to be determined. Official sources of Lao Airlines declared that “the aircraft ran into extreme bad weather conditions and was reportedly crashed into the Mekong river. There were no news of survivors at this time”.

The Laos' Authorities will lead the investigation. In line with the ICAO (International Civil Aviation Organization) Annex 13 convention, ATR will provide full assistance and the French Bureau d'Enquêtes et Analyses (BEA), safety investigation authority representing the country of the aircraft manufacturer will join the investigation.

The ATR 72-600 is a 68-to-74-seat twin turboprop engine aircraft which is the most recent variant of the ATR72-500 being operated around the world, including India;s Jet Airways group.

For more information on the accident, visit avherald.
Read more »

Singapore Airline's passengers suffer consequences of IndiGo accident

by Devesh Agarwal

Its Friday, the 13th, and many a frequent flyer will sympathise with the bad-luck of the passengers on Singapore Airlines flight SQ503 from Bangalore to Singapore earlier this morning.

The inbound flight SQ502 from Singapore scheduled to arrive at Bangalore around 10pm, was diverted to Chennai due to the runway closure at Bengaluru International Airport following the accident of IndiGo airline flight 6E-125 around 8pm last night.

The in-bound passengers waited and finally the runway at Bangalore was opened around 11pm. SQ502 finally arrived in Bangalore around 2am early this morning.

The return flight SQ503, left around 3am, about four hours behind schedule. The crew realised that they would exceed their Flight Duty Time Limit (FDTL). Hurried parleys were made with headquarters, and a decision was taken to divert to Bangkok. In the mean time, a stand-by crew was flown from Singapore to Bangkok to crew SQ503 back to Singapore.

The aircraft was on the ground in Bangkok for less than a hour, and SQ503 finally arrived in Singapore at 1pm, seven hours behind schedule.

Image courtesy Google maps.
All I can do is shake my head and sympathise with the passengers, but at the same time, give credit to the crew for thinking up of a solution.

If they had continued even to Kuala Lumpur, they would be in breach of the regulations.

Had they stayed back in Bangalore, the earliest a replacement crew could come would be on the morning SilkAir flight. This would mean the SQ503 flight would reach Singapore only around 5:30pm, and connections to the US west coast would be missed.

Already the existing delay meant that the morning connections to the United States, Asia, and Australia were missed. The Bangkok diversion allow the airline to try and make up some of the connections in the evening. However, considering this is the weekend, the airline staff in Singapore has their work cut out for them.

What are your thoughts? Share your frequent flyer gaffs via a comment.

Read more »

Bangalore airport shut down as IndiGo flight veers off runway

by Devesh Agarwal
IndiGo Airbus A320 VT-IGV at Bengaluru International Airport. Photo copyright Vedant Agarwal. Used with permission.
At approximately 20:10 (14:40Z), an IndiGo Airbus A320-232 registration VT-IGV performing flight 6E-125 from New Delhi to Bangalore, with 110 passengers and six crew (two pilots, four cabin crew), veered off the runway 27 while attempting to land at Bengaluru International Airport (BIA) during heavy rains and cross-winds.

The aircraft damaged five runway lights and suffered burst tyres, finally stopping near taxiway Foxtrot, and blocking the sole runway 09/27. There were no injuries.

All flight operations at the airport were suspended till repairs to the aircraft were carried out and it was towed to the apron. Flight operations resumed almost three hours later at 22:55 (17:25Z).

A number of flights both domestic and international were diverted to neighbouring airports like Chennai.

The airline released this statement
IndiGo flight 6E–125 from Delhi to Bengaluru, while landing on runway 27 at the Bengaluru airport at 20:10 pm, landed to the right of the center line, while experiencing heavy rains upon landing. The aircraft veered to the right and contacted 5 runway edge lights which led to deflation of the right main tyres. The aircraft was controlled and was taxied off the runway onto taxi track ‘’Foxtrot” and stopped.

All 110 passengers and six crew on board are safe with no injuries reported and have been de-planed safely from the aircraft to the terminal.

As per the operating procedure, the aircraft will be grounded for maintenance work. The matter has been reported to the DGCA and the safety department of IndiGo and DGCA will inquire further into the matter at the earliest.

At IndiGo, we are committed to passenger comfort, and safety is our highest priority. Hence, there can be absolutely no compromise on safety.
In April 2009, in a very similar incident, a Kingfisher Airlines Airbus A320-232 VT-KFT also veered off runway 27 in heavy rain and winds, and damaged runway lights. (Read that story here). At that time the runway was shut for less than 55 minutes. A shut down of three hours with the aircraft stopping on the taxiway suggests significantly more damage to the aircraft than IndiGo is claiming.
Read more »

Videos: All the NTSB media briefings on the crash of UPS Airbus A300-600F at Birmingham, Alabama, USA

The United States National Transportation Safety Board which is investigating the fatal crash of a UPS flight 5X-1354, an Airbus A300-600 aircraft registration N155UP at Birmingham, Alabama, USA, on August 14, 2013, held four briefings for the media. Below are the videos of the briefings all together for your continuous viewing.
UPS Airbus A300-600F freighter registration N162UP approaches Boston Logan Airport in rainy weather






For an in-depth report of the crash, we recommend Simon Hradecky's Aviation Herald.
Read more »

BREAKING: Asiana Airlines 777 crash lands at San Francisco International Airport

[Last updated on 04:30 UTC]
by Vinay Bhaskara and Devesh Agarwal

Asiana 777-200ER Image Credit: Wikimedia
Earlier today, Asiana Airlines Flight 214 with service from Seoul Incheon Airport to San Francisco crash landed on arrival at San Francisco.

The flight was carrying 291 passengers and 16 crew members. Latest reports put the death toll at two.

Initial reports are that the aircraft had just touched down around 11:20 am local time, when the empennage was sheared off rear of the aft pressure bulkhead of the 777, and the tail, gear, and engine of the plane separated. The plane turned around nearly 180 degrees and came to a stop to the right of the runway facing eastwards. Photos show debris before runway 28L; implying that the aircraft hit the ground before making it over the runway. Passengers were evacuated before the aircraft caught fire. The National Transportation Safety Board [NTSB] has been dispatched to the scene to investigate.

Image of the crash from news outlet KTVU
The aircraft is a Boeing 777-200ER with registration HL7742. The aircraft, with line number MSN-29171 is powered by 2 Pratt&Whitney 4090 engines and is configured with either 296 or 300 seats on board and was delivered on March 7th, 2006. Asiana Airlines operates 9 Boeing 777-200ER aircraft in 6 different configurations.

291 passengers (19 business, 272 economy) and 16 crew members were on board, reports are that all  of the 307 passengers are accounted for. According to the San Francisco fire department, 2 people have been reported dead, with 230 injuries of some sort. However, in situations such as this crash, the numbers in terms of passengers According to Asiana Airlines, the passengers on board “were comprised of 77 Korean citizens, 141 Chinese citizens, 61 US citizens, 1 Japanese citizen.”

Asiana's official press release related to the incident can be found here. San Francisco International Airport has been updating the media constantly with intermittent press conferences as it can release information.

The incident is the first fatal incident involving passengers and a Boeing 777. The last (and only other) major crash of a Boeing 777 aircraft occurred on January 17, 2008, when British Airways Flight 38 crashed on arrival at London Heathrow after flying in from Beijing. However, on September 5th, 2001, a ground fire broke out on a British Airways 777-236 at Denver, and one re-fueling operative was killed.

Asiana flight 214 is the first airline crash on US soil since Colgan Airlines flight 3407 on February 12, 2009, which killed 49 passengers on a Bombardier Dash 8 aircraft. The last mainline crash in the United States occurred on November 12, 2001, when American Airlines Flight 587, an Airbus A300 crashed at New York's JFK International Airport, killing 265 (260 passengers, 5 on the ground)

The following picture from passenger David Eun shows passengers disembarking the aircraft, and the fuselage appears to be intact, though burning.

The following videos were taken by a passenger at San Francisco Airport




Videos credit to @360kid

The ATC feed can be heard here on the LiveATC site archive. Asiana 214 is given a landing clearance to runway 28L around 21m20s into the recording. The crash occurs around 22m02s. Shouting can be heard in the background of the tower controller's transmission at the time of the crash.

Image via Ben Sandilands showing emergency response
The airline put out a statement around 2130 UTC
The following information has been confirmed.

Asiana Airlines flight OZ214 (Aircraft Registration HL7742) departed Incheon International Airport on July 6, 2013 at 16:35 (Korea time) bound for San Francisco. Only July 6, 2013 at 11:28 (Local time) an accident occurred as OZ214 was making a landing on San Francisco International Airport's runway 28.

There were a total of 291 passengers (19 business class, 272 travel class) and 16 cabin crew aboard. The majority of the passengers were comprised of 77 Korean citizens, 141 Chinese citizens, 61 US citizens, 1 Japanese citizen, etc. for a total of 291 people.

Asiana Airlines is currently investigating the specific cause of the incident as well as any injuries that may have been sustained to passengers as a result. Asiana Airlines will continue to cooperate fully with the investigation of all associated government agencies and to facilitate this cooperation has established an emergency response center at its headquarters.

At this point no additional information has been confirmed. New developments will be announced as more information becomes available.

*For further information regarding OZ213/214, please contact 02-2669-4015 (for overseas calls : 82-2-2669-4015).
Read more »

Opinion: DGCA fiasco highlights need to resolve conflicts of interests in civil aviation ministry

The abrupt removal of India's chief civil aviation regulator, the Director General of Civil Aviation, Mr. E.K. Bharat Bhushan, earlier this month, once again brings forth the cross-workings within the ministry of civil aviation, caused by contradictory roles, many of which are driven by political agendas, and the urgent need to re-structure this mammoth ministry to correct the malaise.

Indian civil aviation minister Ajit Singh. PIB Photo.
Mr. Bharat Bhushan, an Indian Administrative Service (IAS) officer of the 1979 batch from Kerala, who took over the role of DGCA from Mr. Syed Nasim Ahmad Zaidi in December 2010. He enjoys the highest levels of respect for his integrity, ethics and generally apolitical decision making.

The reasons behind his sudden dismissal have fuelled speculation on the reasons. Within aviation industry circles, there is a strong sense of certainty that Bharat Bhushan was done in, partially due to a political turf war between the ministry and the Prime Minister's Office (PMO), and in large part due to his strong ethical stand on a variety of issues plaguing the industry.

During his tenure Bharat Bhushan brought in stringent measures to prevent airlines and the DGCA itself, from compromising on safety. He prosecuted a variety of flying schools and government officials in the fake pilots scam, and took on two holy cows, Air India and Kingfisher Airlines. He has repeated told both the financially plagued carriers to shape up and pay employees overdue salaries saying that safety could be adversely affected by a demotivated staff.

Post his departure, news reports have appeared showing his purported note to his successor Prashant Sukul that he had prepared for taking action against cash-strapped Kingfisher Airlines on safety grounds. The cat has been set amongst the pigeons with the ministry saying it cannot find the note and will ask Bhushan for the note.

This wrangling is nothing new. The civil aviation is a behemoth with many departments and entities under it, most of which, have contradictory roles and by the very nature of their function, work at cross purposes to each other. Even in Utopian conditions it is impossible make all these roles co-exist within one ministry and still perform true to their charter, and at optimal levels, and this is the Government of India, one not highly rated on governance.

The ministry itself is a policy maker, but also an airport operator through Airports Authority of India (AAI), and airline operator through Air India (AI). Within AAI, there are airport operations and a monopoly air traffic control, navigation, and communications system which is used for further cross-subsidy.

Global competitiveness have forced aviation operations to operate on extremely high levels of efficiency, not the forte of any government. This naturally demands some concessions for government run operations, and the Indian airline industry is already sick thanks to skewed policies designed to protect AAI and AI.

In its natural role, the ministry is a promoter of air travel which requires easing of regulation, but via the DGCA it is also the regulator and in most cases, also the investigator. You will observe that I have deliberately left out the role of enforcer or prosecutor. The most basic rules of administration demand a separation of policy formulation, operation, regulation, audit, investigation, and enforcement. In all publicly listed companies there is always a separate audit committee within the Board of Directors.

Yet ministry officials are routinely shifted across roles. Let us take the current acting DGCA Mr. Sukul. He is a Joint Secretary in the ministry. In addition to the regulator, auditor, enforcer role at DGCA, Mr. Sukul is also a member of the board of Air India, an airline, the DGCA has to regulate, audit, and enforce the rules on. Similarly, the joint DGCA Mr. Anil Srivastava, is also the Chairman and Managing Director of state owned helicopter operator, Pawan Hans Helicopters. These are conflicts of interest at the most basic level. We have to be delusional not to expect compromises being forced on these and other officials within the ministry.

On these obvious conflicts of interest, the civil aviation ministry seems to be a law unto itself. It has ignored calls from no less a body, than the Appointments Committee of the Cabinet, which is the government's apex body for high level bureaucratic appointments, and headed by the Prime Minister, which had asked the ministry to relieve Anil Srivastava from his leadership of Pawan Hans to resolve the blatant conflict of interest.

A lot of this cross working was exposed in the report on the crash of Air India Express Boeing 737-800 VT-AXV at Mangalore Bajpe airport in 2010.

Despite significant short-comings none of the ministry controlled entities were faulted. AAI, the airport operator, which did not construct frangible buildings at the runway, as required at every major airport in India, nor the DCGA, which conducts the inspections, and ensures these facilities before approval, were both let off with the gentlest of slaps on the wrist, for not performing their duties.

The question before us, is what caused these officers to under-perform? Which of these four C's is most plausible? (in)competence? callousness? corruption? conflict (of interest)?

It is imperative that Indian aviation be protected. Various entities within the ministry need to be made truly independent and taken out of its control.

The recommendation, in the crash report, for an independent investigative board, remains a distant dream. The board may come one day, but we can be certain, that a truly independent board, not reporting within, controlled by, and therefore subservient to the civil aviation ministry, and its political shenanigans, will never be implemented.
Read more »

Mumbai airport commences trials of automated ATC departure clearance system

The congested Air Traffic Control (ATC) system at Mumbai airport is under-going a major leap forward with trials of the SITA Departure Clearance System (DCL) through Data Link Communication (DLC).
The Datalink Control and Display Unit (DCDU) the pilot interface for CPDLC messages. Image courtesy Wikipedia.
The Airports Authority of India (AAI) which manages civilian ATC operations across most of India, has begun has begun trial operations of Data Link Communication for pre-departure clearance. This new system is expected to significantly reduce workload of ATC controllers by automating the transmission of routine information like clearance delivery, Automatic Terminal Information Service (ATIS), meteorological (weather etc.) information (VOLMET) etc.  The system is supplied by SITA and its components at Mumbai are :
  1. PDC (Pre Departure Clearance delivery) through data link using ACARS (Aircraft Communications Addressing and Reporting System) capability.
  2. Centralised d-ATIS
  3. d-VOLMET
however, initially only the automated PDC system will be operated.
Read this SITA PDF document for more information on this technology.
Pre-departure clearance is an authorisation issued by ATC to a pilot regarding the runway to be used, route to be flown right from take-off to destination, including use of SIDs (Standard Instrument Departure), and cruising level that the aircraft is expected to maintain. The PDC system can be extended to include taxi information i.e. the route the aircraft is expected to take from its parking bay to the runway.

At present, pilots obtain their PDCs from the ATC through voice radio communication. The pilots then read back the entire clearance to confirm correct receipt of the PDC. (See and hear this clearance delivery at Long Beach airport in Los Angeles). This is a time consuming exercise leading to increased communication workload, along with having the potential of misunderstanding.

In the new system the pilot requests pre-departure clearance using the Flight Management Computer (FMC) in the cockpit. The request is transmitted via data-link to the air traffic controller (ATCO), who then selects the appropriate clearance sends the PDC back to the aircraft at the press of a button, again via an ACARS data link. At the aircraft, the PDC can be printed out.

Getting the information both on screen and print saves on both the radio chatter and time for both the controller and the pilot, and eliminates human errors enhancing safety and operational efficiency. For the passenger this translates to quick departures as pilots do not have to wait in a queue for obtaining clearance.

Image courtesy Wikipedia. 
In case you are wondering on the importance of clear communications between the pilot and controller, the worst accident in the history of aviation occurred on the ground, due to mis-understanding and mis-communication. 583 people died when a KLM 747 collided in to a Pan Am 747 at Los Rodeos Airport, Tenerife.

See a 84 minute video on this incident at the end of this article.

Kingfisher and IndiGo to benefit most
This system is dependent on the aircraft having the data link capability. Bangalore Aviation contacted the major domestic airlines to determine their fleet capability.

Air India confirmed that their wide body fleet i.e. Boeing 747-400 and Boeing 777-200LR and 777-300ER fleet is fully equipped up to a higher level of data link called CPDLC (Controller Pilot Data Link Communication) which is part of FANS. However their narrow body fleet Boeing 737-800 of Air India Express, and Airbus A319/A320/A321 of the erstwhile Indian Airlines is not equipped with any data link capability.

Kingfisher confirmed their Airbus A320/A319/A321 fleet is equipped to receive PDCs via ACARS. Their ATR-72 "are also capable of receiving PDC messages, when ACARS is activated."

Jet Airways, SpiceJet and IndiGo did not respond to our requests.


IndiGo advertises its use of ACARS, so it is safe to assume their aircraft will have the ability to benefit from this system. Airline sources indicated that SpiceJet aircraft are not equipped with data link, and technical airport sources indicated that narrow body aircraft at Jet Airways and Jet Airways Konnect may not have data link capability. It is not clear if Jet's wide-body aircraft are data link capable.

In addition to Mumbai, such Data Link Departure Clearance (DLC) systems are also being deployed at Delhi, Kolkata, Chennai, Bangalore and Hyderabad airports.

Sources at Bangalore Airport informed that the DLC system is already built-in to their Selex air traffic control equipment from the time of its delivery almost five years ago. It is awaiting activation pending some software updates from the manufacturer and a green light from the AAI operated ATC.

Read more »

127 feared dead as Bhoja Airlines Boeing 737 crashes near Islamabad Pakistan

All 127 people, 118 passengers and nine crew, on board a Bhoja Air flight are feared dead in a crash near the national capital of Islamabad in Pakistan. Bhoja flight B4-213 had departed from the commercial capital of Pakistan, Karachi.

There was severe weather in the area of the crash. The aircraft last made contact around 18:20 local (13:20Z) and reportedly crashed at 18:40 local in a residential area around Hussain Abad village near Rawalpindi, 5nm from Islamabad airport

Rescue teams have been dispatched to the scene.

Bhoja Air has commenced operations just a few days ago. The aircraft, The aircraft was Boeing 737-236 advanced, registration AP-BKD, line number 635, was built in 1980, had its first flight on February 13, 1980. The aircraft was delivered to British Airways as G-BGDD on February 23, 1980. It was delivered to Bhoja Air, February 24, 2012.

This is the second crash in less than two years. In July 2010, an Airbus A321 operated by Airblue crashed into hills overlooking Islamabad, killing 152 people on board.
Read more »

Feature: Major plane accidents in the 100 years of Indian civil aviation - Part 2

Continuing our series of major scheduled civil aviation accidents with fatalities in the 100 years of Indian civil aviation. Yesterday we covered till the year 1952, today we continue forward till 1957.

The early 1950's were a torrid time for Indian aviation from a safety perspective, and 1953 continued the high rates of accidents in India. The war surplus Douglas DC3/C-47 Dakota continued to remain the main stay of the civil aviation fleet as well as the crashes. The newly created Indian Airlines Corporation which was formed in 1953, by nationalising seven private airlines, inherited a fleet of 99 aircraft including 74 Douglas DC-3 Dakotas, 12 Vickers Vikings, 3 Douglas DC-4s and various smaller types from the seven airlines that made it up. However, 1953 also saw the first crash of a jetliner in India.

On March 14, 1953, a Convair CV-240 AP-AEG of Orient Airways with 11 passengers and 5 crew, on a flight from New Delhi Safdarjang to Dhaka, East Pakistan, crashed in to mountain after the pilot descended in poor visibility to determine his location visually. All aboard died.

On April 14, 1953, a cargo Douglas DC3/C-47 Dakota VT-AUG of Airways India with 3 crew, disintegrated mid-air in the Khasi hills of Meghalaya on a flight from Guwahati to Calcutta. Structural failure was suspected. All aboard died.

Just a fortnight later, on May 2, 1953, about 16:30 (4:30pm) India witnessed the first crash of a jetliner, when a De Havilland DH-106 Comet-1 G-ALVY of British Overseas Airways Corporation (which subsequently became British Airways) with 37 passengers and 6 crew, burst in to flames soon after take-off from Calcutta Dum Dum on a flight to New Delhi. Structural failure was suspected. All aboard died.

In immediate succession, on May 9, 1953, a Douglas DC3/C-47 Dakota VT-AUD of Air India with 13 passengers and 5 crew crashed just five minutes after take-off from Delhi Safdarjang airport bound for Ahmedabad. The cause is suspected to have been caused by an in-experienced pilot who over-banked the aircraft in to a turn and flew it in to the ground. All aboard died.

On December 12, 1953, a Douglas DC3/C-47 Dakota VT-CHF of the newly created Indian Airlines with 10 passengers and 4 crew crashed soon after take-off from Nagpur, in very similar circumstances to the Delhi crash. A false engine fire indication panicked the flight crew who over-banked the aircraft at too low a speed and too low an altitude in their haste to return to the airport and flew the aircraft into the ground. Only one person, a crew member, survived the crash.

1954, began on an ironical note. On February 25, 1954, in an attempt to understand the reasons behind the Nagpur crash, Indian Airlines attempted a test flight to re-create the incident using one of its Douglas DC3/C-47 Dakota VT-ATU near Delhi with 3 crew on-board. During the test flight, this aircraft too crashed, killing all aboard.

On April 30, 1954, a Douglas DC3/C-47 Dakota VT-DEM of Darbhanga Aviation with 8 passengers and 3 crew crashed soon after take-off from Calcutta, when its left engine caught fire and the plane stalled. Two passengers and all three crew perished.

On January 21, 1955, a cargo Douglas DC3/C-47 Dakota VT-COZ of Indian Airlines with 3 crew had a CFIT (controlled flight into terrain) crash while approaching Guwahati airport during foggy conditions. No one survived.

On February 2, 1955, a Douglas DC3/C-47 Dakota VT-CVB of Indian Airlines with 6 passengers and 4 crew crashed soon after take-off from Nagpur at around 04:00 (4am). Again the flight crew was blamed for over-banking the aircraft causing it to fly into the ground. All aboard were killed.

On April 11, 1955, Air India had its first experience with terrorism. Its Lockheed L-749A Constellation registration VT-DEP and named Kashmir Princess 11 passengers and 8 crew was the victim of a time-bomb near the Natuna islands in the south China sea, on a flight from Hong Kong Kai Tak airport to Jakarta, Indonesia. The target of the assassination was the Chinese Premier, Zhou Enlai, who changed his travel plans at the last moment and was not on-board. Only 3 crew members survived the crash. All passengers mainly journalists, to the Asia-Afro Bandung Conference perished. The captain of the plane, D.K. Jatar who perished in the crash, later along with Co-Captain M.C Dixit and flight engineer Anant Karnik, became the first civilians to be awarded the Ashoka Chakra for "most conspicuous bravery, daring and self-sacrifice".

On March 21, 1956, a Douglas DC3/C-47 Dakota VT-CGN of Indian Airlines with 18 passengers and 3 crew crashed while landing at Tezpur, in the North East. Two passengers were killed and the aircraft hull was written-off.

On March 31, 1956, a cargo Douglas DC3/C-47 Dakota VT-DCM of National Air Operators with 3 crew crashed about 30 miles from Bagdogra. An overloaded aircraft flying in to turbulent weather was the suspect cause. All aboard were killed.

On May 15, 1956, a Douglas DC3/C-47 Dakota VT-DBA of Indian Airlines with 30 passengers and 3 crew over-ran the runway at Kathmandu, Nepal. 14 passengers and one person on the ground were killed. This was the first crash of the domestic carrier in a foreign country.

On October 19, 1956, a cargo Douglas DC3/C-47 Dakota VT-DGK of Indian Airlines with 3 crew crashed while repeatedly attempting to land in poor visibility at Agartala. All aboard were killed.

On March 13, 1957, a Douglas DC3/C-47 Dakota VT-CFB of Indian Airlines with 2 crew crashed at Kingsway camp near Delhi during a training flight for a captain. Both crew and 3 persons on the ground died.

On May 15, 1957, a cargo Douglas DC3/C-47 Dakota VT-AUV of Indian Airlines with 3 crew crashed soon after taking off from Silchar in a severe thunderstorm. One crew member perished.

On August 20, 1957, a cargo Douglas DC3/C-53 VT-ARH of Indamer with 8 crew stalled and crashed in to mountains while dropping relief supplies in Assam. All members were killed.

On September 1, 1957, the first case of a two aircraft collision occurred in India, when a Handley Page HP.81 Hermes G-AKFP of Airwork Ltd., with 58 passengers and 6 crew on a special flight from the United Kingdom to Singapore via Delhi and Calcutta, landed on the wrong runway at Calcutta Dum Dum, and crashed in to a cargo Douglas DC3/C-47 Dakota VT-AUA of Indian Airlines with 4 crew. All aboard the Hermes survived while the 4 crew aboard the Dakota died. The captain of the Hermes was found responsible for the accident. Both aircraft were written-off.

The saga continues next week.
Read more »

Feature: Major plane accidents in the 100 years of Indian civil aviation - Part 1

Yesterday we focussed on the highlights of the last 100 years of Indian civil aviation. Today we focus on the tragedies.

We are listing the major scheduled commercial civil aviation accidents with fatalities that have occurred to Indian carriers or within the geographic confines of India. Military, non-scheduled, and private/business jet/charter aircraft are excluded or the list will be too long. For a full list of accidents in India please visit the Aviation Safety Network which has been a valuable source of information for this article along with other sources like Wikipedia and Simon Hradecky at Aviation Herald which along with ASN, I consider as one of the finest websites for all aviation incident related news.

This list is by no means exhaustive, and if you are aware of any accidents that have been missed, please do help us spread the information via a comment.

Part 1 (till 1952)

The early days of Indian aviation were dominated by war related accidents and incidents of military aircraft during World War II.

The earliest recorded crash with fatalities was soon after independence on December 27, 1947, when a Douglas DC-3 Dakota VT-AUG of Air India crashed at Korangi Creek in Pakistan on a flight from Karachi to Bombay killing all 19 passengers and 4 crew.

On January 16, 1949, another Douglas DC-3/C-47 Dakota VT-CDZ of Dalmia Jain Airways crashed at Banihal Pass in India while enroute to Srinagar killing all 9 passengers and 4 crew.

On July 12, 1949, in the worst accident of the Constellation aircraft, at the time, a KLM Royal Dutch Airlines Lockheed L-749 Constellation PH-TDF from flight from Jakarta to Amsterdam via Delhi and Bombay, with 34 passengers and 11 crew, was flown in to a hill side (a situation today called CFIT - Controlled Flight Into Terrain) while on approach to Bombay Santa Cruz airport (today known as Mumbai Chhatrapati Shivaji International Airport). All aboard perished.

On July 17, 1950, near Pathankot, Punjab, the port wing of a Douglas DC-3/C-47 Dakota VT-ATS of Indian National Airways failed in turbulence during a flight from New Delhi Safdarjang airport to Srinagar. All 18 passengers and 4 crew lost their lives.

On November 3, 1950, the first accident of an Indian carrier outside the sub-continent. An Air India Lockheed L-749 Constellation VT-CQP with 40 passengers and 8 crew had a CFIT (controlled flight into terrain) when it was flown in to the side of Mont Blanc in France at an elevation of 15,000 feet, while performing flight AI-245 from Bombay to London via Cairo and Geneva. The plane and the bodies were located only after 2 days.

Just a month later, on December 13, 1950, in another case of CFIT, a Douglas DC-3/C-47 Dakota VT-CFK of Air India was flown in to the side of Kotagiri, the highest peak in the Nilgiri mountain range on a flight from Bombay to Coimbatore. All 17 passengers and 4 crew were killed.

On July 12, 1951, a Douglas DC-3/C-47 Dakota VT-CHT of cargo operator Indamer crashed about 50km NW of Tezpur. The 3 crew aboard were killed.

On September 15, 1951, a Douglas DC-3/C-47 Dakota VT-CCA of Air India with 23 passengers and 4 crew lost control while taking off from Bangalore HAL airport bound for Trivandrum. The cause was attributed as "lost control and crashed when attempting to take off with the autopilot engaged". 1 crew member was killed. The hull was damaged beyond repair and written off.

On November 21, 1951, a Douglas DC-3/C-47 Dakota VT-AUO of Deccan Airways with 13 passengers and 4 crew crashed in to trees while attempting to land in poor visibility at Calcutta Dum Dum airport on a flight from Bombay Santa Cruz via Nagpur. The lone survivor was a passenger, Mr. C.N. Mehta. Read the Indian Express newspaper of the day here.

A month later, on December 31, 1951, a Douglas DC-3/C-47 Dakota VT-COA of Kalinga Airlines performing a cargo flight crashed in to trees when climbing out of Calcutta Dum Dum airport. The 3 crew aboard were killed.

On February 19, 1952, a Douglas DC-3/C-47 Dakota VT-AXE of Deccan Airways with 12 passengers and 4 crew crashed in to trees while attempting to land at night at Nagpur. One passenger and two crew perished. The cause was attributed to pilot error due to a wrong altimeter setting. [Note: the VT-AXx series of registration is now currently used by Air India Express.]

On April 10, 1952, a cargo Douglas DC-3/C-47 Dakota VT-DFN of Kalinga Airlines with 4 crew crashed at Agartala in north east India, while attempting an emergency landing following an engine failure. All aboard were killed.

On April 30, 1952, a Douglas DC-3/C-47 Dakota VT-AUN of Deccan Airways with 5 passengers and 4 crew crashed while approaching New Delhi Safdarjung airport on a flight from Madras. All aboard were killed. The cause was attributed to fuel starvation of the port engine due a fuel imbalance during a steep turn causing the pilot to lose control.

On October 22, 1952, a cargo Douglas DC-3/C-47 Dakota AP-AAZ of Orient Airways with 3 crew on a flight from Dhaka, East Pakistan to Karachi, Pakistan, crashed while attempting a forced landing at Jamshedpur (the home of Tata Steel). One crew member died in the accident. The aircraft hull was a total loss.

The torrid decade in Indian Aviation will continue tomorrow. Stay tuned for Part 2.
Read more »

Full DGCA investigation report of Kingfisher Airlines VT-KAC crash at Mumbai

In follow-up to our story yesterday about the "serious incident" [read crash] of the Kingfisher Airlines ATR-72-500 VT-KAC at Mumbai on November 10, 2009, and thanks to well wishers, Bangalore Aviation has obtained a copy of the final investigation report by the Directorate General of Civil Aviation. It can be read here.


The synopsis in the front of the report, and the findings on the last two pages of the report give a quick overview. Simon Hradecky of The Aviation Herald has done an excellent analysis of the report and we strongly recommend reading it.

The Mint newspaper continues with the feeling in Indian aviation circles that rules were circumvented to classify this accident as a "serious incident" to keep an accident free record in 2009 for Indian civil aviation. In its report, the paper claims
This finding is a deviation from DGCA rules, according to an official of the regulator and Mohan Ranganathan, a Chennai-based safety expert and member of the government-established Civil Aviation Safety Advisory Council.

The assessment will keep 2009 as an accident-free year for India’s civil aviation sector, said a DGCA official, requesting anonymity.
Read more »

DGCA withdraws report on Kingfisher plane crash-cover-up or shoddy investigation?

Post the Air India Express crash at Mangalore, there have been calls across the country for greater transparency within the administration, policy, regulatory, and investigative units of India's civil aviation system.

With the exception of the famous incident involving President Pratibha Patil's helicopters in a near-miss with an Air India aircraft at Mumbai, with a view to increasing transparency, for the first time, India's regulator and investigator the Directorate General of Civil Aviation put up investigation reports on its website which did not involve the loss of life. One was regarding the crash of a Kingfisher Airlines ATR-72-500 aircraft VT-KAC at Mumbai on November 10, 2009, the other was concerning the sudden loss of altitude of an Air India Express Boeing 737-800 aircraft VT-AXJ en-route from Dubai, UAE to Pune, India on May 26 this year.

Yet, before most media in India could react, the DGCA pulled the Kingfisher report of its website. Luckily, the Indian Express reported most of the pertinent parts of the report. As per the Indian Express the DGCA has faulted the crew of the airline and ATC officials.
In its report, the DGCA says that the crew was not qualified to fly into the Mumbai airport during the shortened runway operations as the commander had not been a ‘training captain’. The crew did not take a decision to ‘go around’, despite an unstabilised approach at the time of landing. It adds that there was a breakdown in the ‘crew resource management’ as the commander —a 47-year-old veteran — did not conduct the correct briefing at Mumbai and Bhavnagar and the 34-year-old co-pilot, who was making her first landing on the shortened runway at Mumbai, did not offer the correct feedback to ‘go around’ at a crucial juncture. It has called on the airline to impart corrective training to the crew. DGCA has also pulled up the ATC for not warning the Kingfisher commander that a previous Air India flight had aquaplaned. Aquaplaning is a phenomenon when there is a thin film of water between the aircraft tyres and the runway, which reduces friction. The report says that the ATC officer had admitted to the DGCA team that he had not understood the word ‘aquaplane’, and not passed on the information to the Kingfisher commander.
The very next day, the Times of India reported about the withdrawal of the Kingfisher report, suggesting the report was withdrawn due to excessive technical faults and incorrect information. The paper also suggests that the Kingfisher "incident" was not classified, by thye DGCA, in contravention of ICAO rules an "accident", despite a significant damage to the aircraft hull. The Times of India report goes on to suggest that this was done to benefit Kingfisher Airlines which would have had to pay higher insurance premiums if it had suffered an "accident".

The Air India Express VT-AXJ report can be read here in PDF format. The report concludes the dive and loss of altitude occurred due to the incorrect handling of the flight control column by the co-pilot in automated mode and his lack of knowledge on how to correct the situation.
Read more »

HAL Chetak helicopter crashes, pilots survive, aircraft badly damaged

A Hindustan Aeronautics Ltd. (HAL) Chetak helicopter registration VT-EIV belonging to the HAL Rotary Wing Academy crashed earlier this morning around 0900 (0330Z) while performing a training flight at the HAL airport in Bangalore, India.
Image courtesy Wikipedia
Bangalore Aviation understands the aircraft was just commencing a routine training flight, and had lifted just about 15 ft in the air when it suffered a suspected tail-rotor failure and crashed back on the ground along the taxiway. The airport operations have been ceased but the airport main runway is functional.

The trainer is a retired Indian armed forces pilot Air Cmde. ROJ Assey, and the trainee is Capt. Virendra Singh of the Indian Army. Both pilots sustained orthopaedic injuries but have survived the crash. They have been taken to hospital for treatment. Hindustan Aeronautics is rendering all assistance.

The aircraft is badly damaged and could be a complete write-off.

The Chetak is the Indian version (SA-315B) of the venerable Aérospatiale Alouette III. It is a single-engine, light utility helicopter recognised for its mountain rescue capabilities and adaptability. Originally developed by Sud Aviation it is made in India by the state-owned Hindustan Aeronautics Ltd as the Chetak, which is a workhorse of the Indian Army and Indian Navy.

VT-EIV had a construction number AH-280 and was built around May 1984. The accident has been reported to India's Directorate General of Civil Aviation and will be investigated by them.
Read more »

Air India Mangalore accident highlights need for an independent accidents investigator

Ever since the unfortunate crash of Air India Express' Boeing 737-800 VT-AXV at Mangalore Bajpe, I have been inundated by requests across the world to comment and even speculate about the crash and possible causes.

Over the last few days we see all kinds of high energy stories in the media, be it speculating on reasons for the crash, or making a mountain out of a molehill. In a headlong rush for TRPs TV channels made a huge issue about the “miraculous escape” due to the runway incursion by IndiGo airlines at Mumbai.

By their measure, I have "miraculously escaped" at least eight times during my last 20 years of flying. May be I am on my ninth and last life, but I wouldn’t bet on it.

As a responsible aviation analyst, I have always advocated shunning speculation on reasons for air accidents. It does great dis-service to the families of the victims, the memories of the lost, and to efforts of those who remain.

Accidents are almost never a case of one single reason or major failure, but rather a chain of several minor reasons or failures. Only a proper investigation will lead to the true cause. The two black boxes have been recovered. Preliminary analysis of the Cockpit Voice Recorder and Digital Flight Data Recorder are only two weeks away. Let us wait for the full truth.

While we are waiting, let us bow our heads in memory of those who perished one year ago on the night of May 31, 2009, in the crash of Air France AF-447. A crash where the two black boxes have still not yet been recovered, and cause still undetermined, despite the hundreds of millions of dollars and countless hours already spent, and efforts that are still underway.

I am confident in Indian aviation and firmly believe it is the safest means of transport. This is the first fatal crash of Air India since the 1985 Kanishka bombing.

However, there seems to be this paranoia about secrecy at various Ministries responsible for transportation be it Civil Aviation, Railways, or Shipping. If we recall major transportation accidents over the last one year. Very little information has been publicly disclosed as to the reasons for the accidents and virtually no information is available on the much more important corrective action required and taken. Just as we have forgotten AF-447 these other accidents no longer feature in our memory.

It is time India has an independent investigating body like the US National Transportation Safety Board (NTSB) or the UK Air Accidents Investigations Board (AAIB) or the Canadian Transportation Accident Investigation and Safety Board (TSB) or the Australian Transport Safety Bureau (ATSB). These agencies are completely independent of the regulators like the US Federal Aviation Administration or UK Civil Aviation Authority, policy makers and service providers. These boards investigate accidents and publicly disclose causal information along with suggested corrective action.

In India I do not know who the regulator and inspector is for rail and shipping, but at least for the air we have the Directorate General of Civil Aviation, however air accident investigations are also under the DGCA.

The DGCA is a fine organisation, and I can personally attest to the upstanding nature and integrity of Dr. Zaidi. However, a separation between investigation and regulation is a must. If the investigation reveals, requires and justifies it; an investigator has to be able to criticise a regulator (DGCA) or even a policy maker (Ministry) and require changes.

Something the current system just does not provide for or do.
Read more »

Former Inspector General Denzil Keelor slams Mangalore airport

The recent crash of the Air India Express Boeing 737-800 VT-AXV at Mangalore Bajpe airport continues to grab headlines.

Numerous analytical reports can be found in the newspapers both national and regional. With the short-comings in the design of the runway at Mangalore, many reports are questioning the independence of the regulator, the Directorate General of Civil Aviation when it comes to airport operator Airports Authority of India and the airline Air India. Along with the DGCA, the Ministry of Civil Aviation also controls the AAI and Air India.

In a hard hitting interview with the Deccan Herald newspaper Air Marshal Denzil Keelor retired Inspector General in-charge of Inspection and Flight Safety of Indian Air Force who served as Adviser to the Ministry of Civil Aviation and Chief Flight Inspector and set up the Flight Inspection department in the DGCA, has slammed the powers that are.

The interview worth a read, can be found here.

Also on the same page is an interview with Air Marshal S Y Savur who was Commander-in-Chief, Southern Air Command and a pilot in the Air Force VIP squadron flying the Boeing 737. The interview focusses on the flying aspects of the ill-fated flight.
Read more »

Air India Express Boeing 737-800 crashes at Mangalore Bajpe airport

One of the latest Boeing 737-800 aircraft in low cost carrier Air India Express' (AIX) fleet, VT-AXV, performing flight IX-812 from Dubai, United Arab Emirates to Mangalore Bajpe, India overshot the runway early this morning while attempting to land, and crashed at 06:10 local (00:40Z) into a wooded valley near Kenjar village about ten km NE of Mangalore airport.

Initial reports indicate the aircraft hit the airport fence while attempting a go-around after the overshoot.

As per airport authorities, the plane was carrying 166 passengers including 137 adults, 19 children and 4 infants, and six crew members on board. The plane was in control of First Officer Harbinder Singh Ahluwalia. Both the crew are well experienced in general and at Mangalore Bajpe airport.

Village residents have rescued eight passengers who have been rushed to hospitals. Loss of life is expected to be heavy.

The aircraft is one of the latest entrants in the AIX fleet, having entered service in January 2008. Mangalore airport is plagued by hilly terrain and the airport has a table top runway. Emergency vehicles had a torrid time reaching the relatively inaccessible crash site.

A Help Desk has been set up at the Mangalore airport. The contact numbers are +91 (824) 222-0422 and 201-0167. At Delhi the numbers are +91 (11) 2565-6196 and 2560-3101.

Incidentally, news channels are showing the flight number as IX-892. The correct flight number is IX-812.

The DGCA has launched an investigation.

This Times of India site has a video report of the incident and the Wall Street Journal has released a picture of the crash site.

Update 1 - 18:00 IST (12:30Z)

As usual there is the usual and macabre speculation on the reasons behind the crash. It is much to premature to conclude the cause of the crash. Efforts should be made to locate and determine the information on the digital flight data recorder and the cockpit voice recorder, the "black boxes".

All ideas are being thrown around - the pilot was foreign (forget the fact he is well experienced and has an excellent reputation amongst the Indian pilot community), the topography is dangerous (yes the airport is more challenging to land at, but there are many similar airport across the world).

Instead of indulging in wasteful speculation, let us keep a sane head, and pray for those who lost their lives in this tragedy. Times of India has published a list of passengers here.
Read more »