Carrier

  • | | | | |

    Santa Cruz Flight Emergency


    Click to view full size photo at Airliners.net
    Contact photographer Roger Cannegieter

    What: AeroSur Boeing 727-200 en route from Santa Cruz to Miami,FL
    Where: Cochabamba Bolivia
    When: Feb 16th 2010
    Who: 87 passengers
    Why: While en route, the plane developed electrical problems and had to put down in Cochabamba. After overnighting in hotels, passengers will be flown back to Santa Cruz, and then on to Miami. No details have been released about the plane, as far as we know.

  • | | | |

    Mexicana Flight Diverts to Merida


    Pictured: A Mexicana Link Canadair CL-600-2B19 Regional Jet CRJ-200ER
    Click to view full size photo at Airliners.net
    Contact photographer Jose Lopez

    What: Mexicana Link Canadair CRJ-200 en route from Cancun to Puebla
    Where: Merida
    When: Feb 15 2010
    Who: 37 passengers
    Why: While en route, during the flight the windshield developed cracks. The flight diverted to Merida Mexico and made a safe landing.

  • | | | |

    Milan: Easyjet Smoke Emergency


    Pictured: An EasyJet Airline Airbus A319-111
    Click to view full size photo at Airliners.net
    Contact photographer Paolo Migliavacca

    What: Easyjet Airbus A319-100 en route from Milan to Brindisi
    Where: Milan
    When: Feb 14th 2010
    Why: While en route, the control panel of the cockpit began emitting smoke. Landing in oxygen masks, the flight crew returned to Milan and made a safe landing. Passengers were provided a replacement craft.

  • | | | |

    Birdstrike Sends Spirit Airbus Back to Hollywood Fla


    Click to view full size photo at Airliners.net
    Contact photographer Alberto Riva

    What: Spirit Airlines Airbus A321-200 en route from Fort Lauderdale to New York
    Where: Fort Lauderdale
    When: Feb 15 2010
    Who: 229 aboard
    Why: On departure, the Spirit Airlines Airbus struck a bird reportedly the size of a turkey just below the windshield. 36 minutes after departure, and after dumping fuel,
    the flight returned to Ft. Lauderdale for an inspection. No one was injured. No indication was made of another bird striking the aircraft. Although emergency vehicles were on standby, plane operations appeared to be normal. Passengers were provided an alternative flight within 4 hours.

  • | | | | | |

    Mexicana Airbus Emergency Diversion to St. Louis


    Click to view full size photo at Airliners.net
    Contact photographer Stefan Heymanns

    What: Mexicana Airbus A320-200 en route from Guadalajara to Chicago O’Hare,IL
    Where: St. Louis
    When: Feb 12 2010
    Who: 115 passengers
    Why: While en route, cabin pressure was disrupted. The crew descended to a lower altitude and landed safely in St. Louis.

    George’s Point of View

    Maintenance! Maintenance! Maintenance!

  • | | |

    Ethiopian Airlines Flight 409 Recovery Numbers fluctuate

    In a Fri Feb 12 release, Earthtimes says Lebanon announced 45 bodies had been retrieved and their DNA identified them as passengers of Ethiopian Airlines Flight 409. 83 passengers and seven crew (or 82 passengers and 8 crew?) died in the 4 minute flight from Beirut international airport into the Mediterranean. However as we can not confirm that number anywhere, we believe the confirmed dna-identified deaths are of a much smaller number.

    U.S. National Transportation Safety Board (NTSB), the French Bureau d’Enquêtes et d’Analyses pour la Sécurité de l’Aviation Civile and Boeing are participating in the investigation.

  • | | | |

    Runway Incursion at Schiphol


    Pictured: A KLM – Royal Dutch AirlinesBoeing 737-306 taking off from Amsterdam – Schiphol
    Click to view full size photo at Airliners.net
    Contact photographer Fred Willemsen

    What: KLM Boeing 737-300 en route from Amsterdam to Warsaw
    Where: Amsterdam
    When: Feb 10 2010
    Why: After being cleared to take off on one runway, the flight actually took off from the taxiway. No incident ensued, and the flight continued to its destination.

    Amsterdam Schiphol airport is reportedly supposed to be a confusing airport which recently changed its runway markings; and at the time of incident, it was sunset, and had supposedly snowed, which may have obscured the yellow taxiway/white runway distinctions, although there was good visibility. Hopefully the investigation will be used to make negotiating the runways safer.

    http://www.nu.nl/algemeen/2182654/vliegtuig-steeg-taxibaan.html

  • | | |

    India: ATR Engine Failure in Bhopal


    Pictured: A Jet Airways ATR ATR-72-500 (ATR-72-212A) filmed in Mumbai
    Click to view full size photo at Airliners.net
    Contact photographer Petr Popelar

    What: Jet Airways Aerospatiale ATR-72-500 en route from Bhopal to Indore
    Where: Bhopal
    When: Feb 11th 2010
    Who: 60 passengers 4 crew
    Why: After takeoff, the right engine failed. The flight returned to Bhopal, and landed hard causing a flat. Otherwise there were no problems recorded and no one was injured, although the closed runway disrupted scheduling for a while.

  • | | | |

    Emergency Landing in Monterrey


    Click to view full size photo at Airliners.net
    Contact photographer Ricardo Morales

    What: Mexicana Click Fokker 100 en route from Mexico City to NEW LAREDO
    Where: Monterrey
    When: Feb 11 2010
    Who: 96 passengers (one site reports 29 passengers and 4 crew)
    Why: The Mexicana Click made an emergency landing in Monterrey when it developed a fault in the undercarriage. It apparently made a safe landing, with no emergencies although it appear one individual may have been suffering from hysteria. Rescue crews were on hand. Other flights were cancelled.

  • | | | | | |

    Borneo Emergency Landing


    Click to view full size photo at Airliners.net
    Contact photographer

    What: Trigana Air Service Aerospatiale ATR-42-300 en route from Berau to Samarinda Indonesia
    Where: East Kalimantan, Borneo
    When: Feb 11th 2010
    Who: 46 passengers and 5 crew
    Why: While en route, the plane suffered engine failure in one of its turboprops. The pilot had diverted to Balikpapan but could not reach the airport, and was forced to land in a rice field near Bone village. The plane was feared missing after losing contact with ATC. One individual had a broken leg but no other serious injuries were reported. No other details have been released regarding the retrieval of the passengers.

  • | | |

    Update: Ethiopian Crash Cockpit Voice Recorder Found/not found


    Click to view full size photo at Airliners.net
    Contact photographer Alastair T. Gardiner

    In an announcement hauntingly similar to the initial release of 7 survivors (who were later confirmed as 22 dead), the cockpit voice recorder was reportedly found…but later reported to be missing the memory unit.

    Ethiopia Airlines release is below and denies recovery of the CVR.
    ET Flight 409 Accident Update 9 – 10 February, 2010

    Ethiopian Airlines would like to express its position on the latest speculative reports released on the cause of the accident on ET-409, 25 January.

    As a member of the investigation team, Ethiopian Airlines strictly adheres to the ICAO annex 13 regulation, in which it is mandated to refrain from any inconclusive comments on the process of investigation.

    The investigation is still in its early stage and the CVR (Cockpit Voice Recorder) and the aircraft wreckage are not yet retrieved for analysis, it is therefore, too early to conclude the cause of the accident. Ethiopian Airlines does not rule out all possible causes including the possibility of sabotage until the final outcome of the investigation is known.

    Ethiopian Airlines would continue to cooperate with the investigation team to complete the process in accordance with the ICAO regulation and reveal the truth.

    We share the pain and sorrow of the families of our crew and dear passengers who have lost their lives in the accident.

    What: Ethiopian Airlines Boeing 737 en route from Beirut to Addis Ababa
    Where: 2 miles west of the coastal village of Na’ameh.
    When: Jan 25 2010
    Who: 7 crew 83 passengers
    Why: Shortly after taking off in stormy weather and heavy lightning, Lebanese ATC lost contact. The plane disappeared from radar 45 minutes after leaving Beirut. Witnesses on the coast saw the plane as it crashed into the sea. So far 9 bodies have been found by members of the Lebanese army

  • | | |

    Austrian Airlines Smoke in Cockpit


    Click to view full size photo at Airliners.net
    Contact Damian Leśniak

    What: Austrian Airlines de Havilland Dash 8-400 en route from Vienna Austria to Iasi Romania
    Where: Iasi
    When: Feb 10th 2010
    Who: 27 passengers and 4 crew
    Why: After reporting smoke in the cockpit, the crew made a safe landing wearing oxygen masks, landing ten minutes early in Iasi. The cause of the smoke is under investigation. Newspapers reported a fire had broken out in the cockpit and that passengers disembarked without injury, without noting if slides were used, or if they deplaned on to the tarmac. The plane will not be making the scheduled flight to Vienna but will be in maintenance.

    With the early arrival however…one cannot help but picture the investigator inquiring…”What? The flight is early? That we really have to look in to…”

  • Southwest Airlines Contests Being Out of Compliance

    More than 100,000 Southwest Airlines flights conducted in 44 airplanes appear to be out of compliance. FAA inspectors are looking into allegations of improper fuselage repairs. Inspectors believe mechanics may have inadequately reinforced the aircraft frame while installing new skin panels replacing frayed stressed areas. Southwest is federally responsible for repairs even when they are contracted out. This is not related to last years when Southwest used unapproved parts on 82 airplanes.

    Aviation Technical Services in Everett, WA skin panel replacement procedures were performed without Federal approval.

    Southwest said, “All of our maintenance operations promote aviation safety by working in coordination with the FAA, equipment manufacturers and aircraft maintenance organizations in every effort to ensure that our fleet is maintained in accordance with applicable regulations and is aligned with best practice in the industry”

  • | | | | |

    Pakistan: Runway Excursion


    Click to view full size photo at Airliners.net
    Contact photographer Asuspine

    What: Shaheen Air International Boeing 737-200 en route from Abu Dhabi to Peshawar
    Where: Peshawar
    When: Feb 8th 2010
    Who: 112 passengers
    Why: While landing on a wet runway, the Shaheen Air flight either hydroplaned or experienced a “technical fault.” If the plane had hydroplaned off the end of the runway instead of veering off the side, it could have impacted the traffic like the Congonhas crash. Instead we have a minor muddy runway excursion.

    No on one was injured. An airline spokesman said “It was tremendously heavy rain and the aircraft skidded off the runway” but others say it was not raining that much. The plane may return to service this week.


    View Peshawar International Airport in a larger map

  • | | | | | |

    American Airlines Emergency Landing in Phoenix


    Click to view full size photo at Airliners.net
    Contact photographer Ivan Voukadinov – BGspotters

    What: American Airlines McDonnell Douglas MD-83 en route from San Diego CA to Chicago
    Where: Phoenix
    When: Feb 9th 2010
    Why: While en route, on board indicators detected a hydraulic leak. The flight diverted to Phoenix AZ where it made a safe landing. Passengers were provided alternative flights.

    Another American Airlines maintenance issue?

  • | |

    American Airlines: Under the Eye

    American Airlines will be stinging from harsh criticism from federal supervisors regarding maintenance issues and facing MD-80 related civil penalties from $10 million to $20 million. (In 2008, American was ordered to ground its MD-80 fleet. See letter pasted below:)

    Watch the news for the DOT’s upcoming report of AMR maintenance failures. From soup to nuts, from engines to deferred maintenance, to unqualified mechanics. A long standing review of aviation maintenance by the NTSB is directed toward problems in providing adequate maintenance for general aviation.

    Federal Aviation Administration Report to U.S. Secretary of Transportation Mary E. Peters on American Airlines MD-80 Groundings

    EXECUTIVE SUMMARY

    This is the Federal Aviation Administration’s response to a request by US Transportation Secretary Mary E. Peters to document events leading up to, during and after the grounding of the MD 80 fleet of 367 aircraft by American Airlines on April 8, 2008, resulting in the cancellation of thousands of flights and tremendous inconvenience for hundreds of thousands of airline passengers.

    American Airlines grounded its MD80 fleet after being informed by FAA inspectors from the Southwest Region Flight Standards Division that inspections had revealed 16 aircraft were not in compliance with FAA AD 2006-15-15, which relates to clamping, bundling and sheathing of electrical wiring that surrounds the auxiliary hydraulic pump in the MD 80 aircraft. These findings were made during an audit conducted to verify airline compliance with various airworthiness directives. During the first phase of the audit – March 13 to March 28 – inspectors found aircraft at American that were not in compliance with AD-2006 15-15 and American grounded some aircraft and advised the FAA it would take corrective action. On April 8, as part of Phase II of the audit, FAA inspectors intended to verify that American had completed the corrective action and found, instead, aircraft in noncompliance.

    Prior to this audit, there was no requirement for the FAA to inspect the aircraft for this AD. The deadline for AD compliance was March 5, and it is the responsibility of the carrier to effectively perform the work as outlined in the AD. The carrier’s maintenance plan is audited regularly and American certified that the work had been done. American never applied for an Alternate Means of Compliance (AMOC)–a well-established procedure known throughout industry–or indicated they were having difficultly complying with the specific AD.

    This report details the timeline of FAA actions related to inspection of American Airlines aircraft as part of a special emphasis audit, the audit results at American, subsequent activities including the finding of non-compliance by the FAA and the grounding of the fleet by American. Also, as directed by Secretary Peters, the report contains a look at what, if anything, could have been done differently, and what can be done in the future to try to eliminate a similar circumstance while still maintaining the highest aircraft safety standards in the world.

    Overall Findings

    American Airlines did not perform adequate or sufficient work in response to AD 2006 -15-15 on its MD-80 fleet. The workmanship accomplished in response to this AD was unacceptable.
    Materials used to take the required corrective action were other than specified.
    The safety goal of the AD was not accomplished because the risk of chaffing, arcing and sparking — the very elements targeted by the AD — were not sufficiently addressed.
    American Airlines created an Engineering Change Order (ECO) to guide their mechanics in accomplishing the work of AD. There may have been confusion in the directives of the ECO that were in conflict with the AD.
    In summary, American failed to take opportunities available before March 5, 2008, to inspect, repair, and accomplish the AD, as required. As with any AD, the FAA established a compliance “threshold,” based on an engineering assessment of when action should be taken to detect or prevent the unsafe condition. The 18 months allowed in the AD was the time period deemed acceptable to accomplish the corrective actions, based on a risk analysis. This AD was designed to prevent ignition or possible fire or explosion near a fuel tank. While such an explosion is a “low probability” event, if it occurs, it has high consequences, according to the risk analysis. American, because of its large MD-80 fleet, had worked with Boeing in the development of the associated service bulletins (SB) and was aware of the needed corrective actions three and a half years before the end of the compliance period in March 2008. If American had properly accomplished the AD by the March deadline, or again on March 25-26 when problems were identified, the April grounding would not have been necessary.

    There was never any type of agreement—formal or informal—between the FAA and American Airlines to let the aircraft in question operate past the deadline established in the AD, as suggested by the Wall Street Journal article dated May 2. There is no “informal” path to operating in non-compliance with AD’s–the airline must demonstrate compliance.

    Background

    Often safety measures are developed as a result of lessons learned from major accidents or tragedies. The regulatory mission of the FAA encompasses learning from the past to proactively intervene in the potential issues of the future. Following the TWA 800 accident over Long Island in 1996, FAA and industry undertook a detailed analysis to determine potential ignition sources that may lead to a fuel tank explosion. Boeing identified wire bundles in the wheel well of the MD-80, which pass in close proximity to the fuel tank and where fuel vapors may be present, as creating a potential risk. To address this risk, Boeing developed specific service bulletins.

    After the Swissair 111 accident in September 1998 involving an MD-11, both the FAA and industry learned a great deal about wiring and the related safety issues. In January 1999, the National Transportation Safety Board issued a recommendation addressing the inspection and examination of wiring on MD-11 airplanes. The examinations were for loose wire connections, inconsistent wire routings, broken bonding wires, small wire bend radii, and chafed and cracked wire insulation. The inspections revealed chafed and cut wires; damaged, cracked, or chafed wires; and inconsistencies in the routing of wires and wire bundles.

    These findings, following the TWA 800 accident, added even more urgency to the elimination of possible ignition sources near fuel tanks.

    Boeing issued SB MD 80-29A070 in August 2004 and revised that SB in July 2005 as a result of reports from operators involving three instances of electrically shorted wires in the right wheel well and evidence of arcing on the auxiliary hydraulic pump power cables. One incident resulted in a fire in the wheel well. Investigation revealed damage to the power cables caused by structural chafing. Analysis also determined the need for extra protection on the harness where it came in close proximity to the center fuel tank. If not corrected, there is a possibility of electrical arcing and/or shorted wires which could result in a wheel well fire and/or hazard to the adjacent fuel tank.

    As a result, the FAA began to review Boeing SBs associated with arcing and sparking and reassessed safety concerns including SB MD 80-29A070. We determined that the issue addressed in the SB was critical and warranted an AD. AD 2006 15-15, issued in July 2006 required a one-time general visual inspection for chafing, or signs of arcing, of the wire bundle for the auxiliary hydraulic pump and required completion of all applicable corrective actions before further flight after the inspection. The corrective actions included:

    Installation of protective sleeving on the auxiliary hydraulic pump wire harness.
    Correction of the routing and clamping of the auxiliary hydraulic pump wire harness and airfoil ice protection system overheat sensor connector wire.
    Replacement of an existing connector “backshell” with a 90-degree version.
    Adding snap tubing on a portion of the wire harness.
    All of these interventions were tailored to secure the wire bundle in place, eliminate risk of chafing and sparking, and keep the wires out of close proximity to other moving parts to eliminate risk of interference.

    The compliance time was set at 18 months from the effective date of the AD, which was September 5, 2006. The 18-month compliance period is based on the manufacturer’s assessment of potential risk occurring as a result of any chafing or misrouted wire bundles. That 18-month period to comply ended on March 5, 2008.

    The stated purpose of the AD was:

    To prevent shorted wires or arcing at the auxiliary hydraulic pump, which could result in loss of auxiliary hydraulic power, or a fire in the wheel well of the airplane; and to reduce the potential of an ignition source adjacent to the fuel tanks, which, in combination with flammable fuel vapors, could result in a fuel tank explosion and consequent loss of the airplane.

    As the industry’s largest MD-80 operator, American was aware of the AD’s requirements years in advance of the AD’s actual issuance as the company worked with Boeing on SB MD80-29A070. This AD first addressed the wire harness issue. Subsequently, American issued internal maintenance directives known as Engineering Change Orders (ECO). An ECO is American’s means of taking an SB or AD, among other things, and converting it into the work instructions for their aircraft maintenance technicians. The ECO also ensures and documents compliance. Boeing issued a revision to the SB, and American revised its ECOs accordingly, even before the FAA issued the actual AD on September 5, 2006.

    Following the issuance of AD 2006-15-15, compliance with the corrective actions in the SB became mandatory, and all operators had 18 months to comply with the requirements of the AD. From the time American worked with Boeing on the original SBs, American had well over three and a half years to inspect and reconfigure fully, as necessary, its MD-80 fleet. If for any reason during the 18 months American found it couldn’t comply or had a different solution for compliance, it could have requested an Alternative Methods of Compliance (AMOC) for the AD, a process available to any airline.

    Timeline of Inspections and Groundings

    On March 13, 2008, the Director of the Flight Standards Service issued Notice 8900.36, Special Emphasis Validation of Airworthiness Directives Oversight. This notice provided instructions for completing a two-phase special emphasis inspection to validate the FAA’s oversight of air carrier compliance with ADs. Phase I instructed aviation safety inspectors (ASI) with oversight responsibility for Title 14 Code of Federal Regulations (14 CFR) part 121 air carriers to identify ten ADs for each aircraft fleet operated by the air carrier. In addition, they were to inspect the appropriate paperwork, for at least one aircraft for each of the ADs selected, to determine whether the air carrier had complied with the AD. Then, they were to perform a visual inspection of the aircraft, at their discretion, to verify the air carrier’s compliance with the AD. Inspectors completed Phase I on March 28, 2008.

    AD 2006-15-15, which affected 5 U.S. airlines (including American) and 535 MD-80 series aircraft, was one of the 10 ADs selected for the Phase I compliance review for operators with MD-80 fleets. American operates the bulk of the MD-80 fleet with 367 aircraft.

    On March 25 – 26, 2008, FAA inspectors notified American that they had concerns with American’s compliance with AD 2006-15-15 on ten aircraft being worked on at American’s maintenance base in Tulsa, Oklahoma. In all four areas highlighted in the Boeing SB, inspectors found instances of incorrect use of nylon tie wraps, incorrect installations of snap tubes, incorrect securing of clamps, clamps not installed at all, no or improper or no wrappings installed, and more importantly, instances of chafing between wire bundles and other surfaces. These were serious and unacceptable failures. In some cases, clamps were loose with the potential to dislodge, becoming free-floating projectiles. American chose to immediately ground a portion of its MD-80 fleet. As a result of FAA’s findings, the airline purportedly re-inspected its entire MD-80 fleet—supposedly identifying and repairing all aircraft not in compliance. (See attachment 1 for depictions of these problems and what a correct repair should look like.)

    Based upon the results of American’s fleet wide inspection, American requested, and was granted, an AMOC by the Los Angeles Aircraft Certification Office (ACO). American’s AMOC surprisingly only requested approval to use an alternative type of safety wire and no other modifications to the requirements of the AD. Because of the limited AMOC request, and American’s assurances that each aircraft returned to service would comply with the AD, the revelations of the subsequent inspections were totally unexpected.

    About two weeks later, beginning on Monday, April 7, and into Tuesday, April 8, 2008, FAA inspectors examined 17 aircraft at DFW International Airport to determine if American was in compliance with the AD and AMOC. Sixteen of 17 MD-80 aircraft inspected were found to be in noncompliance with the AD. The FAA immediately communicated these findings to American. Based upon the FAA inspections, neither compliance nor airworthiness of American’s MD-80 fleet could be assured in the opinion of the FAA. (See attachment 2 for examples of the types of issues inspectors found.) American agreed that, based upon these FAA findings, compliance could no longer be assumed, and American chose to cease operating its entire MD-80 fleet because the aircraft were not in compliance with the requirements of AD 2006-15-15.

    Beginning on the evening of April 8 through the morning of April 9, 2008, the Los Angeles ACO, Boeing, American, Southwest Region Flight Standards Division, and the AMR Certificate Management Office held teleconferences to address American’s request for an additional AMOC. Boeing and American proposed to address immediately only six items in the AD that they deemed to affect “safety-of-flight.” Under this scenario, American would be allowed to continue to operate an additional 60 days in order to come into full compliance with the AD.

    The principal avionics and maintenance inspectors did not support an extension of time to allow the carrier to attain full compliance with the AD because of safety-of-flight concerns. The photographs in attachment 2 are representative of the discrepancies found with American’s MD-80s. At this point, American had failed to demonstrate its ability to comply with the AD on several occasions, resulting in FAA’s decision to inspect 100% of the aircraft before they were returned to service. Had the AMOC been issued, and in order to provide the necessary level of assurance, FAA inspectors would have had to inspect each aircraft twice, once after the six safety-of-flight items were addressed and again after the additional requirements of the AD were met. A time extension without FAA inspection of each aircraft would have assumed that American would properly accomplish the six safety-of-flight items—an assumption not justified by American’s previous failures to perform the work properly.

    Why was the magnitude so great?

    The magnitude of the groundings, specifically beginning April 8, 2008, was due to the fact that MD-80 aircraft account for nearly 50 percent of American’s total number of aircraft, constituting well over 40 percent of its daily flights. The time required for American to return the MD-80s to service was, however, solely within its control. Depending upon the configuration of the aircraft, Boeing estimated that it would take as little as 2 hours to complete the AD to as much as 12.5 hours per aircraft. The FAA had inspectors available throughout the country to review aircraft as they completed their inspections and repairs. This was the result of constant coordination between the FAA and the airline.

    As the American maintenance crews completed the work on an aircraft, certifying that it was fully compliant with the AD, an FAA inspector reviewed the work in accordance with the AD, as well as general aircraft airworthiness requirements. These inspections were limited to the area affected by the AD.

    From April 8 – 12, 2008, American presented 351 aircraft to FAA inspectors, who initially found 207 aircraft not compliant with the AD. This represents a 70 percent failure rate. Each of these 207 aircraft required additional work before being accepted as in compliance and returned to service.

    During this time period, there were instances where FAA inspectors waited for hours for an aircraft to be ready for inspection. Also, onsite reports from inspectors included instances of parts shortages, as well as American personnel shortages, that were needed to inspect or repair aircraft. By April 12, 2008, all aircraft were found to be in compliance with AD 2006-15-15.

    Conclusion

    While it may be argued that any one of the discrepancies — or non-compliance issues — may not pose an immediate safety risk, the aggregate findings of the workmanship quality raised the specter of a cumulative safety risk. Left uncorrected, the workmanship errors would have increased the odds that one or more of American’s large MD-80 fleet would have experienced arcing, smoke, or fire–problems that have caused serious incidents and fatal accidents in the past.

    Despite the alleged ambiguity of the wiring AD, other carriers flying MD-80 models did not have significant problems complying with its provisions. But it also is fair to say that while American experienced issues responding to this particular airworthiness directive, there is no reason to suspect the overall quality of American’s maintenance program. During the audit FAA reviewed 59 additional airworthiness directives and American was able to demonstrate compliance. In addition, FAA regularly performs surveillance of American’s maintenance program.

    The American situation reinforces the need for the FAA to review the AD process, and even more important, for air carriers to follow ADs precisely. Carriers also must adhere to the provisions of the Enhanced Airworthiness program for Airplane Systems (EAPAS) rule, the premise of which is that wiring systems must be properly designed, installed and maintained to avoid catastrophic results.

    In answer to the question “What could have been done to prevent the extreme impact to the flying public,” American Airlines could have done the work properly in the allotted time or applied for a comprehensive AMOC earlier in the process and also resolved discrepancies involving safety of flight (e.g., chafing).

    Follow-up Actions

    The FAA has formed a joint industry/Government task force to review the AD process, starting with AD 2006-15-15. The task force will look into how the affected airlines developed the mechanics’ work instructions and how the airlines could have managed this AD better, as well as FAA’s process for developing this specific AD. After completing that effort, the task force will look at the overall FAA process for developing ADs, how we communicate critical AD information to operators, and what, if any, procedures need to be changed to improve this process.

    We will also increase our efforts on training and educating the industry regarding the importance of wiring in light of our SFAR 88 (Fuel Tank Safety), Aging Aircraft, and Enhanced Airworthiness Programs for Aircraft Systems (EAPAS) rules.

    American Airlines intends to create a process to prototype its work on an AD on one aircraft and have the work reviewed by FAA inspectors. Two other airlines have already begun a similar process.

    As steward of the nation’s aviation system, it is incumbent on the FAA to ensure the safety and efficiency of the system for the flying public. This situation with American Airlines that caused so much stress and disorder to the public was truly regrettable. We pledge, Madame Secretary, to continue to improve our oversight, reporting and communication with all in our industry, so the system can maximize efficiency with no cost to safety.

  • | | | |

    Delta Flight Cancelled


    Pictured: A Delta Connection (Freedom Airlines)Embraer EMB-145LR (ERJ-145LR) over Fort Lauderdale – Hollywood International
    Click to view full size photo at Airliners.net
    Contact photographer Roel Van Der Velpen – MST-Aviation

    What: Delta/Freedom Airlines Embraer ERJ-145 en route from Charleston to Cincinnati Kentucky
    Where: Yeager Airport in Charleston West Virginia
    When: Feb 8 2010
    Who: 46 passengers and three crew
    Why: The pilot aborted takeoff possibly over flat tires, though the reason the pilot aborted is still a matter of question. (After the high speed runway skid, two tires are definitely blown.) There was damage to the to right main gear tires, and also some wing damage, supposedly from rubber projectile. The flight skidded several hundred feet and rolled to a stop about 500 feet from the runway’s end. Passengers debarked without incident; and maintenance crews are working on getting the plane towed. Several flights have been cancelled due to the runway closure.

  • | | | |

    Russia: Aborted Take off


    Click to view full size photo at Airliners.net
    Contact photographer Dmitry Belov

    What: Yakutia Airlines Antonov AN-24 en route from Yakutsk to Olekminsk Russia
    Where: Yakutsk
    When: Feb 4 2010
    Who: 38 passengers and 4 crew
    Why: On takeoff, the left engine failed. The pilot aborted the takeoff, and with the gear retracted, the plane skid along the runway on its belly, incurring damage on its lower fuselage, left wing, propeller, and engine.

    Passengers evacuated with no injuries reported. The left engine was on fire though, but was successfully extinguished.

  • | | | | |

    Smoke causes British Airways Diversion to Dusseldorf


    Click to view full size photo at Airliners.net
    Contact photographer Ole Simon

    What: British Airways Airbus A320-200 en route from Budapest to London
    Where: Dusseldorf
    When: Feb 3 2010
    Why: While en route, a smoke detector went off. The crew diverted the plane to Dusseldorf and made a safe landing. Passengers evacuated safely. The flight was cancelled, and passengers were rebooked on a Lufthansa flight. The cancellation was called a precautionary measure.

  • | | |

    American Airlines MD-82 Emergency Landing


    Pictured: An American Airlines McDonnell Douglas MD-82 taking off from LAX
    Click to view full size photo at Airliners.net
    Contact photographer Niklas Åhman

    What: American Airlines McDonnell Douglas MD-82 en route from San Diego,CA to Dallas Ft. Worth,TX
    Where: San Diego
    When: Feb 3rd 2010
    Who: 106 passengers and 5 crew
    Why: After takeoff, the right engine experienced a couple of compressor stalls, resulting in a couple of loud explosive-sounding bangs. The crew decided to return to San Diego where they made a safe landing. The flight was cancelled, passengers rebooked.

  • | | | | | |

    Turku Finland: SAS CRJ Engine Shut Down


    Click to view full size photo at Airliners.net
    Contact photographer Shaun Simpson

    What: SAS Scandinavian Airlines/ Cimber Air Canadair CRJ-100 en route from Turku Finland to Copenhagen Denmark
    Where: Turku
    When: Feb 4 2010
    Who: 43 passengers and 3 crew
    Why: After takeoff, the plane developed a problem with the left engine and it was shut down. The crew returned the plane to the Turku airport and made a safe landing.

  • | | | | | |

    Aerolineas MD-83 Diverts to Santiago


    Click to view full size photo at Airliners.net
    Contact photographer DAD – Baires Aviation Photography

    What: Aerolineas Argentinas McDonnell Douglas MD-83 en route from Buenos Aires to Jujuy Argentina
    Where: Santiago Argentina
    When: Feb 4 2010
    Who: 45 passengers
    Why: While en route, the plane developed cabin pressure problems and diverted to Santiago where it made a safe landing. Passengers were provided a flight to Santiago.