Showing posts with label Flight Safety. Show all posts
Showing posts with label Flight Safety. Show all posts

India succesfully addresses ICAO's safety concerns

by BA Staff

The Press Information Bureau, Government of India reports, The International Civil Aviation Organization (ICAO) validation team submitted its report and recommendations to ICAO headquarters for the review by the ICAO SSC Validation Committee. ICAO has conveyed that corrective action taken by India have successfully addressed and resolved two Significant Safety Concerns (SSC) relating to airworthiness and operations. Consequent to this decision, the Safety Concerns have been resolved and India no longer figures amongst the States with SSC on the ICAO website.

International Civil Aviation Organization (ICAO), during the ICAO Coordinated Validation Mission of India in December 2012, had identified two Significant Safety Concerns (SSC) relating to airworthiness and operations. The concern on airworthiness related to approval of major modifications and repairs carried out on foreign manufactured aircraft and registered in India while the concern on operations related to the procedure for grant of Air Operator Permit to non-scheduled operators and flight documentation system of scheduled airlines.

DGCA prepared a Corrective Action Plan (CAP) in January, 2013 to address the concerns and submitted the same to ICAO for their acceptance. On acceptance by ICAO, DGCA initiated action to implement the CAP to address both the Safety Concerns. Regular updates were provided to ICAO on the progress made on CAP implementation.

In June 2013, on completing substantial work, DGCA requested ICAO to send a Validation Team to assess the implementation of the CAP for resolving the SSC. A three member ICAO Team visited India from 19th to 23rd August, 2013 for the validation of the CAP implementation. During the visit, the team examined all documentary evidences at DGCA Headquarters and Regional Offices at Delhi and Mumbai. As part of the Validation process, the team also visited organizations to ascertain the safety oversight capability of DGCA with respect to implementation of CAP.
Read more »

Ryanair discontinues legal actions against Belfast Telegraph

Ryanair has dropped legal proceedings against the Belfast Telegraph after the paper issue an apology to the carrier about a number of false claims made in an article posted on the Telegraph website on August 6th. Find the details below.

19th August 2013

RYANAIR WELCOMES BELFAST TELEGRAPH APOLOGY

Ryanair, Europe’s only ultra-low cost carrier (ULCC), today (19 Aug) welcomed an apology issued by the Belfast Telegraph arising from its publication of an article two weeks ago on its website (6 Aug) which made a number of false claims about Ryanair’s fuel policy and safety.

Ryanair initiated legal proceedings against the Belfast Telegraph last Friday (16 Aug), as well as Channel 4 Dispatches, The Daily Mail Online and the Daily Mirror. Within hours of the proceedings being issued, the Belfast Telegraph issued an apology and accepted that Ryanair’s pilots are free to carry as much fuel as they wish to, that Ryanair fully complies with EU fuel regulation, and also the IAA’s confirmation that Ryanair’s safety is “on a par with the safest airlines in Europe”.

In light of this apology, Ryanair will discontinue its legal action against the Belfast Telegraph, but will continue to pursue its defamation cases against Channel 4 Dispatches, The Daily Mail Online and the Daily Mirror.

Ryanair’s Robin Kiely said:

“We welcome the Belfast Telegraph’s apology and its acceptance that Ryanair’s pilots are free to carry as much fuel as they wish, that Ryanair fully complies with EU fuel regulation, and the IAA’s confirmation that Ryanair’s safety is “on a par with the safest airlines in Europe”. In the light of this apology we have instructed our lawyers to drop our legal action against the newspaper. 

Ryanair will not allow any newspaper (or group of non-Ryanair pilots) to defame our industry leading 29-year safety, or to impugn the 9,000 aviation professionals whose commitment to safety here in Ryanair on every flight, every day, is absolute.”
Read more »

Opinion: After Ethiopian Airlines incident at Heathrow Airport; 787 remains safe

by Vinay Bhaskara

Last Friday, a pair of incidents occurred with the Boeing 787 Dreamliner. Smoke was observed billowing from an Ethiopian Airlines Boeing 787 parked on the ground at London Heathrow International Airport with no passengers on board, while a Thomson Airways Dreamliner operating between Manchester and Sanford, Florida (SFB) was forced to return to Manchester due to a routine maintenance problem.

Turning first to the Ethiopian 787, the facts are as follow:

Around 16:30 B.S.T, the Ethiopian 787, registration ET-AOP, was observed with smoke billowing throughout the aircraft. Fire response crews at Heathrow rushed to the aircraft and doused it with fire retardant foam from at least 3 vehicles

787 damage at Heathrow Airport - via Sky News
There was significant smoke/fire damage to the carbon fiber reinforced polymer (CFRP) skin of the Ethiopian 787, in the crown of the fuselage just forward of door 4 (the aft door). The damage was in a different location than that caused by the issues with the 787’s lithium-ion batteries that caused the Dreamliner to be grounded worldwide for more than 3 months. In fact, the British Air Accidents Investigation Branch (AAIB) has ruled out a direct causal relationship between the 787’s batteries and/or auxiliary power unit (APU) and the fire damage. The graphic below from Boeing shows that the damage from the 787 batteries occurred in a different location entirely.

Graphic showing location of 787 batteries - Image Credit: Boeing
The 787 was on Fixed Electrical Ground Power (FEGP) at the time of the incident. A report in the Financial Times quoted an Ethiopian Airlines source as stating that a problem had been observed in the aircraft’s air-conditioning system, and that “sparks were observed,” but this report has not been corroborated anywhere else. The 787’s aft ceiling contains Remote Data Concentrators (RDCs) and Remote Power Distribution Units (RPDUs) with significant amounts of wire, and there is a galley station (but no crew rest) beneath the section of the roof where damage occurred.

The National Transportation Safety Board (NTSB), European Air and Space Agency (EASA), AAIB, Boeing, and Ethiopian are all investigating the incident. The damage represents a massive aircraft on ground (AOG) challenge, and a good testing case for composites repair, which presents its own set of challenges (find more information on composite repair here). The cause of the damage is unknown at this point.

These are the facts we know; full stop.

All of the speculation about design problems with the 787 and maintenance issues is exactly that, speculation.

For their part, Boeing, Ethiopian Airlines, and (importantly) the assorted aviation safety agencies are all treating this as a one-off event. Ethiopian Airlines issued a statement saying that the incident was “unrelated to flight safety.”  Ethiopian is scheduled to take delivery of its 5th 787 this week, and plans to do so as scheduled and keep its entire remaining fleet of Dreamliners operational.

To their credit, the DGCA is taking a similar approach with national carrier Air India’s fleet of 787s. "We are keeping a close watch in the investigations (at Heathrow). We will take a view (on Air India's fleet) only after we receive reports of the inquiry and know the causes behind these incidents," DCGA chief Arun Mishra told the Press Trust of India (PTI). To date, Air India has taken delivery of 7 Dreamliners out of a total order of 27.

Air India should keep its Dreamliner fleet operational
This is the correct tactic. While many in the media, especially (albeit understandably) among the British press, have used this as an opportunity to question the 787’s safety, the fact is that this incident is unrelated to any prior ones on the 787. Aviation is not a perfect process; things can go wrong. And even the best of aircraft have one off issues from time to time (see the recent 777 crash or the Air France A330 crash in 2009). When the safety authorities whose job it is to separate isolated incidents from chronic safety problems are treating the 787 as a safe, airworthy aircraft; you should too.

Every aircraft, especially one with such a large degree of new and advanced technology, will suffer its fair share of teething issues. Remember the A380s wing rib cracks? Or the myriad issues that the 747, 777, 767, A340, and A300 all faced on their respective entries into service (EIS). Give Boeing and other involved parties some time to work out the kinks; because when they do, the 787 is set to revolutionize air travel.

Read more »

Infographic: The Boeing 777 is Safe

by Bangalore Aviation Staff

After the crash of Asiana Flight 214 at San Francisco International airport this past Saturday, a media firestorm erupted around the Boeing 777 aircraft involved in the crash. Fears grew among much of the traveling public and non-aviation media that the 777 was in fact an unsafe aircraft to fly. This is simply not the case. Bangalore Aviation has prepared the following infographic to help allay some of the safety concerns that have arisen around the aircraft.
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 »

2012 was best year in history for airplane safety, but Africa remains a concern as per IATA

The International Air Transport Association (IATA) announced that the 2012 global accident rate for Western-built jets was the lowest in aviation history. The 2012 global Western-built jet accident rate (measured in hull losses* per million flights of Western-built jets) was 0.20, the equivalent of one accident every 5 million flights. This represented a 46% improvement over 2011, when the accident rate was 0.37, or one accident for every 2.7 million flights.

*Editor's note: A hull loss is an accident in which the aircraft is destroyed or substantially damaged and not subsequently repaired for whatever reason including a financial decision by the owner.

No member of IATA, which represents some 240 airlines comprising 84% of global air traffic, recorded a Western-built jet hull loss in 2012.

The safety numbers
  • Close to 3 billion people flew safely on 37.5 million flights (29.8 million by jet, 7.7 million by turboprop)
  • 75 accidents (all aircraft types, Eastern and Western built), down from 92 in 2011
  • 15 fatal accidents (all aircraft types) versus 22 in 2011
  • 6 hull loss accidents involving Western-built jets compared to 11 in 2011 (all losses suffered by non-IATA member operators)
  • 3 fatal hull loss accidents involving Western-built jets, down from 5 in 2011
  • 414 fatalities compared to 486 in 2011
  • Fatality rate slightly increased to 0.08 per million passengers from 0.07 in 2011 based on Western-built jet operations
  • IATA member airlines outperformed the industry average for accidents of all aircraft types (0.71 accidents per million flights compared to 2.01), accounting for 13 of the 75 accidents

IOSA


All 381 airlines on the IATA Operational Safety Audit (IOSA) Registry experienced no Western-built jet hull loss accidents. The total accident rate (all aircraft types) for IOSA registered carriers was 4.3 times better than the rate for non-IOSA carriers (0.96 vs. 4.11).

IOSA is a requirement for all 240+ airlines who are members of IATA. A further 140 non-IATA operators are also on the IOSA registry.


Regional Highlights—Western-built Jet Hull Loss Rates


The following regions outperformed the global Western-built jet hull loss rate of 0.20:
  • Commonwealth of Independent States (CIS) (0.0), Europe (0.15), Middle East and North Africa (0.0), North America (0.0), and North Asia (0.0).
  • The following regions saw their safety performance improve in 2012 compared to 2011: the CIS (from 1.06 to 0.00), Latin America and the Caribbean (from 1.28 to 0.42), Middle East and North Africa (from 2.02 to 0.0) and North America (from 0.10 to 0.0).
  • The following regions saw safety performance decline in 2012 compare to 2011: Africa (from 3.27 to 3.71), Asia-Pacific (from 0.25 to 0.48) and Europe (from 0.0 to 0.15).
  • Latin America and the Caribbean posted a second consecutive year of improvement (0.42 vs. 1.28) but the region’s rate was still higher than the world average.
  • Africa registered a higher rate, from 3.27 in 2011 to 3.71 in 2012, and it is still the worst performer by a large margin.
Safety in Africa


Africa’s Western-built jet hull loss rate showed a higher rate compared to 2011 (3.71 vs. 3.27). The region’s accident rate for all aircraft types more than doubled (12.44 accidents per million flights from 6.17 in 2011), with 13 accidents in 2012 (up from 8 accidents in 2011).

African airlines on the IOSA registry had no accidents.


In May 2012, IATA, with the International Civil Aviation Organization (ICAO) and a host of other organisations, committed to an Africa Strategic Improvement Action Plan aimed at addressing safety deficiencies and strengthening regulatory oversight in the region by 2015. The Plan was endorsed as part of the ‘Abuja Declaration’ by the Ministerial meeting on Aviation Safety and Security of the African Union in July and endorsed at the Assembly of the African Union in January 2013.

Accident Analysis


Runway excursions, in which an aircraft departs a runway during a landing or takeoff, were the most common type of accident in 2012 (28% of total accidents). 82% of runway excursions occur following a stable approach where the aircraft floated beyond the normal touchdown point, or braking devices did not activate in a timely manner, or because directional control was not maintained after landing.

This type of accident continues to present challenges for the industry. Despite an increase in the runway excursion accident rate in 2012, the five-year trend in actual accidents remains downward (2008:28, 2009:23, 2010:20, 2011:17, 2012:21). In 2013, IATA will continue to work with industry partners to support regional runway safety seminars and to update the IATA Runway Excursion Risk Reduction (RERR) toolkit. Furthermore, IOSA now requires that airlines make use of Flight Data Analysis (FDA) programs which can help identify precursors to runway excursions.

Loss of Control In-flight (LOC-I) is not a common accident category, but result in the most fatalities, 43% of all fatal accidents and 60% of all fatalities from 2008-2012. In 2008 there were 14 LOC-I accidents followed by: 2009:9, 2010:10, 2011:8, 2012:6. IATA is working with industry partners to implement a global LOC-I prevention program that will assist operators to understand the factors involved in these events. In addition, this program will provide guidance for an enhanced pilot training and establish a process for feedback into the IATA Training and Qualification Initiative (ITQI). 

Information Sharing


Data sharing is crucial to identifying trends that could indicate a potential safety issue. In 2009, IATA launched the Global Safety Information Center (GSIC). This incorporates operational and safety information fed by seven different databases. These are accident data, operational safety reports, IOSA and IATA Safety Audit for Ground Operations (ISAGO) audit findings, Flight Data eXchange (FDX), an aircraft ground damage database and a new cabin safety operational report database. More than 460 different organizations around the globe are already submitting information to GSIC. Continuing with the work started with GSIC, IATA is introducing the new operational data management initiative, incorporating GSIC and expanding data management into other arenas such as operations and infrastructure.


View 2012 IATA Aviation Safety Performance Report (pdf)
Read more »

Opinion: India's airlines are safe to fly

Over the past week, a serious fight has erupted between India’s aviation regulator the Directorate General of Civil Aviation and the airlines, with a number of serious charges being espoused by the DGCA. In a bluntly worded financial audit that Bangalore Aviation (as well as most of the internet) has acquired, the DGCA lists out several “safety” violations that India’s airlines are supposed to have committed.


The report comes to the conclusion that with regards to Air India Express and Kingfisher, “A reasonable case exists for withdrawal of their AOP [operating certificate], as their financial stress is likely to impinge on safety.” In addition to these two, the rest of India’s airlines were all found to have safety issues, with the DGCA concluding that their financial troubles could also negatively affect the safety of air travel.

Over the past week, the DGCA met with all of the private carriers to discuss their various troubles; and Kingfisher reacted with damage control, stating that it would return to flying a full schedule by 2012, and claiming that its safety violations were overblown. IndiGo reacted with a public and detailed response, while the rest of India’s carriers have yet to weigh in. Despite the sensationalist headlines reported in the Indian media, the DGCA will not be forcing any carriers to shut down.
"We have met all airlines in the past few weeks on the issue of financial stress. Kingfisher was called in today. There is no threat of closing any airline. All airlines are under stress," explained Bharat Bhushan, the DGCA head.
That being said, let’s take a look at the actual report, and assess the validity of the DGCA’s concerns. IndiGo has already detailed its response, so we’ll examine the violations detailed for Air India Express and Kingfisher; the carriers singled out by the report.

Kingfisher:

1. A third of the fleet being grounded is not, in and of itself, cause for safety concern. Simply put, Kingfisher has grounded the aircraft for lack of spares- that suggests compliance with DGCA rules, not an ignorance of safety. Qantas has at times grounded its A380 fleet for safety concerns; yet that carrier is praised for their attention to safety while the DGCA is criticizing Kingfisher for performing a similar act

2. See #1: Kingfisher is short of engines; the fleet is grounded. Would the DGCA prefer that Kingfisher fly these aircraft without engine spares?

3. While the lack of spares obviously has troubling consequences (grounded fleet), Kingfisher is ultimately choosing to ground these planes as opposed to flying them without spares.

4. Cannibalization of parts is not unheard of. For example, in the United States, low cost carrier Allegiant Air has found it more economical to purchase used McDonnell Douglas MD-80s and cannibalize those for parts to maintain their operating fleet of MD-80s.

5. MEL Extensions, which refer to changes in the minimum equipment list (number of aircraft parts) that airlines are required to have on hand at any given time, are common practice around the globe. According to IATA: “Under certain conditions, such as a shortage of parts from manufacturers, or other unforeseen, situations, air operators may be unable to comply with specified repair intervals. This may result in the grounding of aircraft. To preclude that from happening, a MEL Item Repair Interval Extension Program has been instituted that will allow operators, under controlled conditions, to obtain extensions to MEL repair interval.” While it is troubling that Kingfisher is resorting to MEL extensions due to fiduciary difficulty, ultimately, the carrier has not yet resorted to flying without parts.

6. The loss of 24 pilots is potentially serious; India’s fast growing aviation sector is placing increased strain on the country’s (relatively) small pilot base. But 24 pilots is a smaller loss than many of Kingfisher’s rivals. This outflow could have an effect on pilot rest and therefore effectiveness; but is not yet severe enough to affect overall safety

7. Kingfisher not operating a full schedule of flights is irrelevant to a discussion of the airline’s safety; and in our view, the capacity drawdown was as much a business decision as a maintenance one.

8. Most of the employees have not been paid salaries for 2011; relevant only to the extent that disgruntled employees might not be as safety conscious as committed ones; a tenuous connection at best.

Moving on to Air India Express (AIX):


Picture copyright Devesh Agarwal. All rights reserved.
1. FOQA, or flight operations quality assurance is very important with regards to aviation safety; as it measures exceedances of, or a divergence above set flight parameters (e.g. pitch exceeds safe limits at some point during a flight). FOQA exceedances are normal occurrences, to which the US Federal Aviation Administration FAA typically requires carriers to respond by “fixing” the problem, or building in more safeguards against it. From a flight safety perspective, therefore, a failure to take corrective actions for events in June is alarming. Obviously these incidents were not severe, as the DGCA has not yet grounded AIX. But this is perhaps the most valid concern raised by the DGCA against the two airlines we’ve covered. The 14 incidents cannot be judged; if the non-availability is because those flight crew have been fired or have left their job; then there is nothing that AIX could have done. On the other hand, if the carrier has been shielding these employees, then there may be a more serious problem. The increase in FOQA exceedances in 2011 is troubling, but means nothing without context; were the number of incidents per number of flights operated by AIX greater in 2011, or did incidents rise proportionally to the increase in number of flights?

2. The pilot and instructor shortage is an issue insofar as much as it restricts the carrier’s capacity growth. It could lead to a shortage of trained employees and place additional stress on current ones. But the broader trouble has been caused as much by parent Air India as anything, and as such; the blame cannot be laid solely on AIX.

3. #3 goes hand-in-hand with #2; shortage of pilots is not a safety threat unless the carrier attempts to operate more flights than the safe level with a lower level of pilots. The reduced schedules indicate that Air India Express has not committed the aforementioned error.

4. FDTL, or flight and duty time limitations, limit how long an in-flight airline employee (pilots and cabin crew) can be on the clock; mostly flying, transiting, or performing checks. FDTL is typically handled by crew schedulers, and while doing it by hand is tedious, it was performed successfully for years before the onset of computers. Air India too is still on hand-written FDTL, and while this reduces the economics of their crew scheduling and increases the DGCA’s pain in checking compliance, there is nothing inherently wrong in calculating FDTL by hand.

5. And #6 really; training is a tough business; and as long as Jet Airways’ 737-800 simulator has close to 100% commonality with AIX’s, the issue is non-existent. Moreover, the pilots only use the simulators to get a feel for flying the aircraft; the individual airline tendencies are usually learned on actual aircraft.

Based on the analysis I’ve done above, it should become apparent that the DGCA has overstated some of the safety concerns while noting other items that really shouldn’t be concerned. While the report does raise a few valid concerns (AIX’s FOQA adventures being chief among those), its broader conclusion is shoddy. Carriers are facing financial troubles, the DGCA’s thinking goes, and thus are likely to skimp on maintenance and impugn safety.

This is simply not true. Most airline managers understand that public confidence in their carrier’s safety, once lost, can bankrupt the company. A chilling example is the crash of ValuJet flight 592 in the United States in 1995. That accident so frightened the American public, who fled the airline in droves, that ValuJet was forced to change its name to AirTran in an attempt to stave off bankruptcy. Thus while airlines are often seen skimping on things like food, employees, etc., you almost never see airlines attempting to save money on maintenance beyond improvements offered by the manufacturers themselves. In fact, carriers like Kingfisher and AIX have been revealed by this report to have acted in the interests of safety. Rather than over-extend their pilots or fly aircraft without spares, they instead chose to reduce schedules and ground fleets, at great financial loss.

Ultimately the Indian airlines are still safe to fly. The DGCA and a sensationalist Indian press have blown these issues way out of proportion. Problems faced by Kingfisher and AIX are marginal at best; and those two carriers were considered the worst of the bunch. Ultimately, one wouldn’t stop flying American Airlines during their bankruptcy for fear of their safety; and so it should be for Kingfisher and the rest of India’s airlines as well.
Read more »

IndiGo responds to DGCA's charges on "unsafe airlines"

The on-going spat between India's aviation regulator the Directorate General of Civil Aviation and the airlines has been raging for the last few days, which has seen some pretty serious charges come forth from the regulator.

IndiGo, which is believed to be India's only profitable airline at present, has responded to the charges of the DGCA in a statement.
IndiGo response to findings during Financial Surveillance Audit

This is with regards to the recent stories that have been reported in the press based on DGCA’s findings during financial surveillance audit where issues were raised about IndiGo’s safety norms. Safety is a key concern at IndiGo, and as an airline we always cooperate with the DGCA and comply with the regulator’s instructions. IndiGo is the first airline in India to proactively start to implement a Safety Management System (SMS), we follow our training, monitoring and safety procedures meticulously with no exceptions. Also, since its launch IndiGo practices 100% Flight Data Monitoring and follow - up action is immediately taken where required.

Specific to the financial audit and safety review by the DGCA report on airlines, the following is IndiGo’s stance to each of the issues that have been raised:

[DGCA observation]
1) A total of 11 premature engine removals were carried out till October, 2011, out of which three were due to bird hits, which is considered to a large number.

INDIGO’s STANCE
Seven of the above engine removals were in compliance of FAA [Federal Aviation Administration] Airworthiness Directive (AD)*. The deadline to comply with the FAA AD is January, 2013. In fact, IndiGo has pro-actively complied with the FAA AD well ahead of time. Three engines were removed due to discrepancy found post bird hit inspections. One engine was removed due to fracture of lug on Gearbox casing.

*{There is an Airworthiness Directive (AD) 2010-20-07 issued by FAA on the HPC 3-8 drum for IAE V2500-A5 engines. Subsequently DGCA has issued Mandatory Mod DGCA/V2500/12 for complying with this FAA AD. This essentially requires the change of a “Silver coated” nuts between the HPC 3-8 Drum and the 9-12 HPC Drum inside the engine to a “Non-Silver Coated” nut. This AD states that this should be complied on all affected engines by January, 2013. In order to comply with this, the engine has to be removed and sent to the shop. In the IndiGo fleet, this FAA AD was applicable to 45 Engines. IndiGo took a pro-active approach and has complied with this AD on 43 Engines as per FAA AD. Therefore, IndiGo is complying with this Directive well-ahead of the deadline.}

In view of the same, it is noted that the above mentioned engine removals were not because of any performance degradation of propulsion system but for pertinently complying with the AD or damage due to bird hits. Hence, this query stands answered and closed.


2) Scrutiny of the “Snag Reporting Form” of the period Jan-Oct, 2011 reveals that large number of engineering snags have occurred, which are on an average about 250 on monthly basis. In the month of Oct. 2011 itself, a total of 261 snags have been reported for a fleet of 46 aircraft. However, the airline has reported only two incidents to DGCA. Preliminary examinations of the snags reveal that few of the snags are reportable incidents, which have not been reported by the airline.

INDIGO’s STANCE
IndiGo submits a “Daily Defect Report” to the Airworthiness department of DGCA and therefore, there is 100 % reporting of all maintenance actions. Incident reporting at present is being done as per the guidelines of DGCA Air Safety Circular (ASC) 5 of 82. A meeting was held between IndiGo’s and DGCA Air Safety officials on 30th December, 2011, wherein all 261 pilot reported defects were jointly reviewed and following was agreed upon:

a. PIB to be carried out within next 10 working days on following three Pilot reported defects:
  • VT – IEH: ENG # 2 FADEC Alternator, OVSPD protection fault, ENG # FADEC B Fault of 7th October, 2011
  • VT – INE: Engine Vibration of October 22nd, 2011
  • VT – IEC: ADR Disagree of October 25th, 2011
b. IndiGo will constitute an internal committee and prepare case studies for commonly occurring snags such as Vent Avionics Fault, Brake, LGCIU Fault, Door Warnings and Nose wheel vibration. Findings from the case studies shall be submitted by the middle of February, 2012.

In view of the above, the open issue is adequately addressed and closed.


3) As envisaged in Aviation Environmental Circular 1 of 2009, the airline does not have Environmental Cell.

INDIGO’s STANCE

IndiGo has constituted an environmental cell. The members of the Environmental Cell are S.C Gupta, Vice President – Engineering, (Nodal Office), Mukesh, Dy. Chief of Flight Safety, M.S Ahluwalia, Director – Power plant and Contracts, Mr. Aakash Bhatnagar, DGM – Flight Operations.


4) A total of 60 incidents have been reported in 2011(up to Oct.). Out of 60 incidents, investigations of 30 incidents was carried which include 26 Single Page Investigations, which were conducted by the airlines itself without appropriate approval from DGCA. Seven of the Precautionary Landings have also been investigated through single page report.

INDIGO’s STANCE
IndiGo carries out detailed investigations into each incident case. PIB reports for minor incidents were prepared in a DGCA approved Single Page format. However this practice has been since discontinued. In this regard, we treat the issue closed.


5) FOQA record of 100% monitoring could not be verified due to non-availability of proper data.

INDIGO’s STANCE
It is submitted that IndiGo has 100% FOQA records available. This can be checked at any time. In this regard, we treat the issue closed.


6)There were total 35 FDTL exceedances from January to 20th November, 2011, out of which eight were due to midnight landing.

INDIGO’s STANCE
These FDTL’s exceedances occur due to unavoidable circumstances such as weather, traffic congestion and flight diversions. Whenever such instances occur, we provide additional rest to the crew to prevent fatigue and the same have been reported to DGCA on regular basis. None of these were planned FDTL exceedances. The open query stands answered and closed.


7) Shortage of pilot Instructor/Examiners and backlog of trainings

INDIGO’s STANCE
We have consciously “over hired’ pilots, especially highly trained and experienced pilots and Training Captains more than the normal hiring ratios. IndiGo presently has strength of 50 Training Captains, and have an additional 44 number of Training Captains are in process of being hired or qualified as trainers.

In addition to the above 50 Training Captains, IndiGo is presently using DGCA authorized Indian and Expats Training Captains on FAT, Airbus Training captains as part of the support team. Training Captains at location outside India with CAE under exclusive agreement, Training Captains of CTC, UK (DGCA authorized).
Read more »

Video: How to fight laptop computer lithium ion battery fires

In recent years, we have heard about a number fires and subsequent safety recalls on cell phone and laptop batteries most notably of Dell and Apple, but also of Toshiba, Hewlett Packard. Sony, Lenovo/IBM, Hitachi, Fujitsu, Sharp, and Nokia.

On February 7, 2006, about 23:59 eastern standard time (06:59Z), a United Parcel Service
Company (UPS) McDonnell Douglas DC-8-71F, registration N748UP, performing flight 1307, from Hartsfield-Jackson Atlanta International Airport, landed at its destination, Philadelphia International Airport (PHL), Pennsylvania, after a cargo smoke indication in the cockpit. The captain, first officer, and flight engineer evacuated the airplane after landing. The flight crew sustained minor injuries, but the airplane and most of the cargo were destroyed by fire after landing. The probable cause of the fire was suspected to be a load of laptop computers and lithium ion batteries. Download the NTSB report here.

In fighting battery fires, it is key for everyone to recognise the following :
  • The typical laptop battery pack contains six or nine Lithium ion cells.
  • The critical temperature of the cell is about 177 degrees celsius (350 degrees Fahrenheit).
  • Fires and explosion occur in one cell and then spread to the other cells with the heat of the first causing thermal runaway reactions in the adjacent cells.
  • It is important to immediately extinguish the fire using either a water or Halon 1211 fire extinguisher, do not use powder or foam extinguishers
  • It is critical to cool the battery pack down using water, or any non-alcoholic, non-flammable liquid -- soft drinks, soda, juices will suffice which will slow down and eventually stop the thermal runaway reaction.
  • Do not use ice as this will smother the battery and trap the heat. This will continue to fuel the runaway thermal reaction and cause secondary fires and explosions. This is also why foam and powder extinguishers are a strict no-no.
  • Do not attempt to pick up and move a smoking or burning device or remove the battery pack from the device!!! There are chances of a secondary explosion and serious bodily injury may result.
The US Federal Aviation Administration released a training video along with a Safety Alert for Operators (SAFO) about fighting laptop battery fires. This FAA training video might help.



You can download the video from the FAA website. Click on the “Training Videos” link on the lower right of the page. I forewarn that the site is painfully slow.

Hat tip to Simon Hradecky at Aviation Herald for the idea.

Read more »

India risks downgrade by US FAA under IASA program

An audit team of the US Federal Aviation Administration (FAA) is meeting the Directorate General of Civil Aviation (DGCA) in Delhi today. The team will check if India is following the international safety standards set by the International Civil Aviation Organisation (ICAO) under the FAA's International Aviation Safety Assessment (IASA) Program.

During its 2006 audits, ICAO had found several violations of 300 guidelines. Shortage of skilled manpower was the biggest problem, and neither the DGCA, nor its master, the Ministry of Civil Aviation have taken any substantive steps to correct the short-comings. The DGCA reportedly faces a shortfall of 700 adequately qualified staff, one of the pre-requisites to be assessed by the FAA team, and one the FAA has already wanted the DGCA about more than six months ago.

As per reports, in the 2006 ICAO audit, for technical personnel qualification and training, India scored only two out of ten, against a global average of four; for safety oversight functions, India scored four out of ten against the global average of six.

This is going to be a tough time for Naseem Zaidi, India's Director General of Civil Aviation. Failing this assessment will result in a downgrade of India from its Category 1 to a Category 2 status, which will place severe restrictions on Indian carriers operating to the United States; currently Air India and Jet Airways.

Lest India thinks that its special new found friendship with the United States will help, one should look at one of the United States' closest allies, Israel, who was recently downgraded to Category 2.

As per the FAA guidelines
While in Category 2 status, carriers from these countries will be permitted to continue operations at current levels under heightened FAA surveillance. Expansion or changes in services to the United States by such carriers are not permitted while in category 2, although new services will be permitted if operated using aircraft wet-leased from a duly authorized and properly supervised U.S. carrier or a foreign air carrier from a category 1 country that is authorized to serve the United States using its own aircraft.
Facing the imminent threat of the downgrade the DGCA is desperately trying to recruit more staff, and preparing a roadmap to separate the tasks of safety inspections and accident investigations from its regulatory functions. It has even finally come to its senses and mooted a proposal for the formation of an independent agency vested with the responsibility of accident investigations.

The question now remains whether (a) Will the mandarins at the Ministry of Civil Aviation, finally come to their senses and give up their powers? and (b) Is it too little, too late. Will the FAA give India more time and accept India's improvement roadmap plan?

I am very doubtful on both.

Read more about the FAA IASA program.
Read more »

Pilots being targetted by green laser pointers

With the advent of the new 20mW 532nM green laser pointers, a dangerous trend is emerging in the skies.

According the Civil Aviation Authority, at least five attempts have been made to dazzle pilots with laser pointers in the skies over Northern Ireland in the last six months. Unfortunately, this trend is not limited over the skies of Northern Ireland alone.

In a most serious incident, on 4 August, the captain of a Boeing 737 was hit in the eye with a laser as he made his approach to Belfast City Airport. I cannot think of a more delicate posture of the aircraft in its entire flight, a time when the complete concentration and vision of the pilots are needed.

On Halloween night, numerous planes, on approach to the same Belfast city airport, were targeted by green lasers.

The new green laser pointer at 20mW is significantly more powerful than it red laser pointer predecessor. Any person who has the laser beam shone directly towards the eye risks permanent blindness, with assured temporary blindness.

Caroline Evans from the British Airline Pilots Association reflects my view. ""Anyone who is stupid enough [or malicious enough] to do this [shine a laser light in to a pilots eye], should be put behind bars and taught a lesson."

Shining a laser pointer at an aircraft is an offence, endangering the safety of an aircraft, and comes under the Air Navigation Order and carries a custodial sentence. There have been prosecutions in the UK for this offence.

I can only hope that stupid pranksters read this article and realise the deadly game they are playing with innocent passenger and crew lives.
Read more »