The AirSafe.com News

↑ Grab this Headline Animator

Showing posts with label incident. Show all posts
Showing posts with label incident. Show all posts

09 January 2013

What's wrong with the 787? - Hard to say for now

Earlier this week on January 7th, a Japan Airlines 787 at Boston's Logan Airport had a fire in the auxiliary power unit (APU) compartment of the aircraft, causing some damage to the aircraft and an injury to a firefighter. There was only a maintenance and cleaning crew on board, no passengers were injured, and as the NTSB photo below shows, there was relatively little fire damage in the APU compartment.


While most APU fires which cause minor damage don't usually merit much in the way of attention by either the news media or the NTSB, this event was different. The NTSB launched an investigation that included representatives from Boeing, FAA, Japan Airlines, and the Japan Transport Safety Board. This kind of involvement by multiple agencies usually happens for either accidents or very serious incidents. This was certainly not an accident as defined by the NTSB, but the NTSB's reaction implies that this is being considered to be a serious event, very likely for at least a couple of reasons:
  • The 787 had a number of prior incidents since entering passenger service last year, including an electrical problem that led to an emergency landing of a United 787 in New Orleans in December 2012, just a month after United began flying this aircraft model.
  • The 787 had a number of development issues that delayed commercial flights for several years.

This fire very likely heightened public attention for the 787 and led to a couple of minor incidents getting a higher than usual amount of national and international media attention. On January 8th, the day after the APU fire at Boston, another Japan Airlines 787, also at Boston, had a minor fuel problem that delayed a flight. About 40 gallons of fuel leaked from the aircraft. This leak was from a vent designed to release fuel rather than from a broken fuel line or some other system malfunction. The plane departed for Japan later that day.

The following day, on Janury 9th, ANA airlines in Japan, which was the first airline to operate the 787, cancelled a flight after the crew received an error message concerning the braking system. These last two events are so minor that the airlines are not required to report them to the FAA, NTSB, or similar civil aviation authorities in other countries.

Why is this happening to the 787?
Boeing's development of the 787 was different in two significant ways from that were a significant departure from previous large passenger jets. The first difference was the extensive use of composite materials for major components of the aircraft structure, and the second was the extensive use of contractors to design and build major aircraft systems, work that previously had been by Boeing.

Neither of these facts explain why these incidents have occurred. While many of the incidents that have occurred have involved the 787 fuel and electrical systems, there is nothing to directly several recent 787 incidents, including the following:

  • An electrical problem that forced the December 2012 emergency landing, along with a related electrical problem found later in another United 787.
  • A grounding of a Qatar 787, also in December 2012, after finding a similar electrical problem.
  • A July 2012 engine failure during a taxi test of newly manufactured 787
  • A December FAA Airworthiness Directive (AD 2012-24-07) requiring 787 operators to inspect part of the engine fuel system for possible improper installations.

What does this mean for passengers?
Unless the NTSB, FAA, Boeing, or the current 787 operators find something significant that may affect the safety of the 787, the recent events, however dramatic, are not a cause for concern. The 787 is a new aircraft model that currently has fewer than 50 aircraft in service, with over a third of the aircraft being delivered only in the past three months, and with six of the eight operators having fewer than six months experience flying this model. The first commercial flight was in October 2011, and Japan Airlines only began flying the aircraft in April 2012.

The recent NTSB investigation may have been launched in part because it is a new model and because there may be useful insights gained from thoroughly investigating incidents such as the Boston APU fire. As operators around the world gain more operational experience with the 787, there will certainly be more incidents. However, unless several of these incidents have one or more causes that are both related and unexpected, there would be real reason to suspect that the 787 has some sort of issue that is exposing passengers and crews to excessive safety risks.

Is it safe to fly on the 787?
If you define safety as an acceptable risk, then the 787 is safe to fly because there is nothing that currently indicates that the 787 has a much greater likelihood of experiencing safety-related problems compared to other large jet airliners. However, that answer may change as a result of the current NTSB investigation or after the airlines flying the 787 gain greater operational experience.


07 January 2010

FAA increases oversight of American Airlines after three landing mishaps

After three American Airlines landing mishaps in December 2009, including two MD80s that experienced wingtip strikes, and a 737 that overran a runway in Jamaica, the FAA announced that it was increasing its oversight of the airline. AirSafe.com's Dr. Todd Curtis was one of the airline safety experts interviewed by National Public Radio for the January 5, 2010 broadcast of the NPR show Morning Edition.
Listen to the interview
Details on 22 December 2009 American Airlines crash in Jamaica
American Airlines plane crashes

30 October 2009

AirSafe.com Survey Results Plus American Airlines 777 Turbulence Event near Tokyo

Survey Results for The Text to Speech Narrator
Since last week's debut of the Macbook's text to speech function as a podcast narrator, many of you responded to the survey about this narrator and have given AirSafe.com some valuable feedback. There were 78 responses, 63 of whome listened to the entire podcast. Of these 63, 10 said would not listen to this narrator again and 12 others were not sure if they would do so again. Most of those who would listen to this narrator again agreed that it would be appropriate for shorter podcasts.

Based on these results, this narrator will likely be used again, mostly for shorter episodes, or to supplement other audio content.

AirSafe.com Visitor Survey
In an earlier survey about what resources visitors use at AirSafe.com, most of the 35 who responded said that they visited multiple AirSafe.com related sites or services, with AirSafeNews.com, Plane-Crash-Videos.net, and the AirSafe.com podcast being the most popular choices.

Roughly half of the respondents have not listened to or viewed one of the podcasts. If you haven't done so yet, I invite you to check out one of the podcast videos that are hosted on YouTube. You can find all of audio and video podcasts are at podcast.airsafe.org

Only a few of the 35 admitted to using any social media resources. Also, when asked what they wanted changed AirSafe.com, the most popular response was adding more photos. A BirdStrikeNews.com article from last month addresses both points to some extent. In Ten Free Social Media Things You Can Do, AirSafe.com provided suggestions for free and easy to use social media tools you can use, as well as an example of tools that are actively used at AirSafe.com. Based on your feedback, some of them will be used on a more regular basis throughout AirSafe.com's network of sites.

By the way, some social media resources are in the right hand column. You can join the email notification list so you can get an email whenever this site is updated. You can also click on the Twitter logo and subscribe to AirSafe.com's Twitter account. If you don't have a Twitter account, you can easily sign up. Also, if you use Google Reader or another kind of RSS reader, you can click on the appropriate link or icon and subscribe that way as well. If you have no idea what RSS is all about, that will be covered in a future article.

American Airline Turbulence Event near Tokyo
Earlier this week, AirSafe.com came across several small article news articles about a turbulence event involving an American Airlines 777 (N777AN), Flight 61, near Tokyo on Monday (26 October 2009). Reportedly, nine passengers were injured and five, including three children, were treated at a local hospital after the aircraft landed. The plane encountered turbulence over the Pacific Ocean, about 70 kilometers (43 miles) southeast of Tokyo's Narita airport. The aircraft landed without further incident about 14 minutes later.

Passengers reported that the airplane had already experienced strong turbulence for about 20 minutes. Also, the 'fasten seatbelt' signs had been on for about 45 minutes before the event. There were 228 passengers and crew members aboard the Boeing 777.

Since this was an event that happened in Japan, and because it did not cause substantial aircraft damage or fatal injuries, it is unlikely that information from this incident will be in the accident and incident databases of the FAA or the NTSB. If you find any additional sources of news about this incident, please leave a comment and a link to that information.

Related Resources
Turbulence Risks
Selected Fatal Turbulence Events
Air Canada Turbulence Event from 2009
Child Restraint Advice from the FAA
TurbulenceForecast.com


Report About Air Canada Turbulence Event from January 2008


27 October 2009

NTSB Update on Northwest A320 Incident Highlights Serious Potential Safety and Security Issues

The NTSB continues to investigate last week's incident where the pilots flying Northwest Airlines Flight 188, an A320 carrying 144 passengers and five crew members, stopped communicating with air traffic control while in cruise and later overshot its destination airport by about 150 miles. The incident was on October 21, and on Monday October 26th, the NTSB released some information about the the flight. The following key events in the flight and the early investigation include a combination of information provided by the NTSB, Delta (which owns Northwest), and others:

- The incident occurred during Northwest Airlines Flight 188, a scheduled domestic airline flight from San Diego, CA to Minneapolis/St. Paul, MN.

- The flight crew stopped communicating with air traffic control while the aircraft was cruising at 37,000 feet.

- The two flight crew members were interviewed separately on Sunday October 25 for a total of about five hours

- Neither pilot has had any previous accident, incident, or violation.

- Neither pilot reported any ongoing medical condition.

- Both pilots stated that they were not fatigued and did not fall asleep or doze during the incident flight.

- Both pilots had a had a 19-hour layover in San Diego just prior to the incident flight.

- Both pilots said there was no heated argument during the incident flight.

- Both stated there was a distraction in the cockpit.

- The pilots said there was a concentrated period of discussion where they did not monitor the airplane or calls from air traffic control even though both stated they heard conversation on the radio. The discussion, which began during cruise, concerned a new flight crew scheduling system that was put in place after Northwest's recent merger with Delta.

- The pilots stated that at cruise altitude they were using cockpit speakers to listen to radio communications rather than their headsets.

- Neither pilot noticed messages that were sent by company dispatchers.

- Each pilot used a personal computer while they discussed the airline crew flight scheduling procedure.

- Delta Airlines, which has already suspended both pilots until the conclusion of the investigation, stated that using laptops or engaging in activity unrelated to the pilots' command of the aircraft during flight is strictly against the airline's flight deck policies and violations of that policy will result in termination.

- Both pilots said that they lost track of time.

- Neither pilot was aware of the airplane's position until a flight attendant called about five minutes before the scheduled landing time and asked about the aircraft's estimated time of arrival. It was at that point that the captain reviewed his instruments and realized that the airplane had passed the destination airport.

- Both pilots said there are no procedures for the flight attendants to check on the pilots during flight.

- When asked by air traffic control about the nature of their problem, they replied "just cockpit distraction" and "dealing with company issues".

- The NTSB planned to interview other company personnel, including the flight attendants, on Monday October 26th. They also plan to anlayze air traffic control communications.

- Preliminary data from the cockpit voice recorder (CVR) revealed that the recording was 30 minutes in length, and that it began during final approach and continued until the aircraft was at the gate, and that cockpit conversation were recorded by the crew's headset microphones (which were not used by the crew during at least part of the flight), but not by the cockpit area microphone. Also, part of the 30 minute recording included some period of time after the incident flight.

- The flight data recorder, which contains data from several hundred aircraft parameters, captured the entire flight, including the portion of flight where there was no radio communication from the flight crew. Investigators are examining the recorded parameters to see if any information regarding crew activity during the portion of flight where radio contact was lost can be obtained.

Issues Suggested by this Event
A number questions remain about this incident, some of which can't be answered by the NTSB, the FAA, or the airlines involved. Most deal with the national security implications of this event.

Potential Safety and Security Issues: Based on earlier reports, the aircraft was out of radio contact for well over an hour and flew over the Minneapolis area without being challenged by military aircraft. While the aircraft did not execute any maneuvers that would have been considered hostile, there were apparently no military aircraft in the air, or any other military assets on the ground to deal with the aircraft if it had been hijacked or otherwise no longer under the command of the flight crew.

Deficient Safety Databases: While some past incidents involving pilots overflying their destination or not responding to radio communications from the ground, there are no legal or regulatory requirements to report these events in publicly available aviation safety databases such as those managed by the NTSB and FAA. As a result, any estimate of the likelihood or frequency of these kinds of events will likely severely underestimate the risk to the public.

Cockpit Voice Recorder Technology: The cockpit voice recorder did not record the portion of the flight where the crew was out of radio contact. While the FAA allows airlines to install recorders with a 30 minute limit, there are models available with a two hour capacity, more than enough to have recorded for the entire time that the crew was not responding to the radio.

Sources for this Article:NTSB, Delta Air Lines, Flightaware.com, CNN

Other Resources
NTSB
Delta Airlines Statement 26 October 2009
NTSB Investigation Update 26 October 2009

25 October 2009

Podcast About the Recent Northwest Airlines A320 Overflight Event and the Delta 767 Landing Incident

The latest episode of the Conversation at AirSafe.com reviews two events from the week of October 19, 2009 that could have become major airline disasters. In Atlanta, a 767 landed on the taxiway instead of the runway, and in Minneapolis an airline crew stopped communicating with the outside world for over an hour while flying past its destination by well over 100 miles.

More detailed descriptions of these two incidents are in the AirSafeNews.com article from 23 October 2009. The podcast that is based on this article, which you will find below, is a bit unusual. Previous episodes of the Conversation at AirSafe.com were hosted by Dr. Todd Curtis. This show features a computer-generated narrator. We ask you to listen to the show and tell us what you think about this narrator.

Northwest Airlines A320 Overflies Airport and Delta 767 Lands on Taxiway by Mistake (4:37)

Evaluation of Text-to-Speech Narration
AirSafeNews.com conducted a survey of this narration by computer generated voice, and you can see the results of the survey in an article published on 30 October 2009.

11 October 2008

Interview with a Passenger on the Qantas A330 Accident Flight of 7 October 2008

This show features an interview with Keesin Ng, a passengers on a Qantas A330 aircraft that experienced a violent in-flight upset during a flight from Singapore to Perth on 7 October 2008. About 75 passengers and crew members were injured during this event, with 14 hospitalized with serious injuries such as fractures and lacerations.

The Australian Transport Safety Bureau, or ATSB, is currently investigating this event, and because of the extent of the injuries on board, the ATSB has classified it as an accident. In a media briefing three days after the accident, the ATSB reported that the Qantas A330-300 aircraft was in level flight at 37,000 feet when the pilots received messages from their aircraft's monitoring system indicating some kind of control system problem.

The aircraft reportedly had a uncommanded climb of about 200 feet, followed by a return back to 37,000 feet. About a minute after returning to cruising altitude, the aircraft abruptly pitched nose-down, to a maximum angle of about 8.4 degrees, and descended about 650 feet in about 20 seconds, before returning to the cruising level.

About 70 seconds later, there was a further nose-down pitch, to a maximum pitch angle of about 3.5 degrees, and the aircraft descended about 400 feet in about 16 seconds. During the first pitch-down event, a number of passengers and crew members were thrown about the cabin, resulting in a range of injuries.

The crew declared an emergency and diverted to Learmonth, landing about 40 minutes after the start of the event.

The interview occurred three days after the event with passenger Keesin Ng, who provides additional details about the in-flight drama. You can hear that interview at the link below:

Interview with Keesin Ng (MP3)


For additional information, including AirSafe.com's initial video and audio podcast about the accident and updates to the ATSB's accident investigation, visit qantas.airsafe.org

08 October 2008

Serious Injuries on a Qantas A330 Flight on 7 October 2008

A Qantas Airbus A330-300, with 303 passengers and 10 crew members on board, was on a scheduled international flight from Singapore to Perth. While in cruise, the aircraft reportedly experienced some type of sudden and unexpected altitude change. The crew issued a mayday call before diverting the aircraft to the airport at Learmonth, near the town of Exmouth, about 1100 kilometers or 680 miles north of its intended destination of Perth.

Overview of the Event


Other Podcast Links
Audio: MP3
Video: iPod/MP4 | WMV | Google Video | YouTube

About 36 passengers and crew members were injured, with over a dozen severe injuries. Reportedly, several occupants were slammed into the ceiling during the event. Most of the injuries were to passengers and crew in the rear of the aircraft, and at least one person was carried off the plane in a stretcher. About 13 of the most seriously injured were flown to Perth by four aircraft from the Royal Flying Doctor Service. One flight attendant was hospitalized with suspected head and spinal injuries. Other serious injuries included fractures, lacerations, and a concussion.

The Australian Transport Safety Bureau has a team of seven investigators currently working on this incident, and it will likely be several days before a preliminary cause is announced, and several months before a final report is issued.

This is the first significant passenger safety event for the A330. Qantas currently has 15 A330 aircraft in its fleet, including 10 of the A330-300 model.

This is the second significant safety event for Qantas this year. On July 25, an exploding oxygen bottle blew a hole in the fuselage of a Qantas 747 en route from Hong Kong to Melbourne, causing a rapid decompression and forcing an emergency landing in Manila. No passengers were injured in that event.

Other significant safety events for Qantas in the last decade include a 2000 event in Rome involving the collapse of a 747 landing gear, and in 1999 a landing overrun in Bangkok severely damaged another Qantas 747.

In August 2008, the Civil Aviation Safety Authority of Australia conducted a review of Qantas safety and found no system-wide safety issues, but did recommend an audit of the airline's maintenance practices, including a full maintenance audit of one aircraft from three of the models flown by Qantas, the 737-400, 747-400, and 767-300. No maintenance audit was ordered for the airline's A330 fleet.

Additional information about this event, including updates or findings from the investigation or from the Qantas maintenance audit, will be available at qantas.airsafe.org.

More Details on this Event
Other AirSafe.com Videos

28 July 2008

Qantas Investigation Update and New Secrets of AirSafe.com Episode

Update to Qantas 747 Rapid Decompression Event on 25 July 2008
Dr. Todd Curtis reviews information from provided by Australian investigators that points to a aircraft systems failure as a possible cause of the explosive decompression event. Also in the podcast, fear of flying expert Capt. Tom Bunn discusses the media's response to this incident.

To hear this podcast, please visit
http://www.airsafe.com/podcasts/show58-qantas2.mp3

For the previous podcast and links to related information, visit
http://www.airsafe.com/podcasts/show56.htm

For Other AirSafe.com podcasts, visit
http://podcast.airsafe.org

Secrets of AirSafe.com: Key Technology Trends and How They Are Used
In this fifth episode of the special series Secrets of AirSafe.com, AirSafe.com creator Dr. Todd Curtis discusses key online technological innovations, including search engines, blogs, and subscription services, that have influenced how AirSafe.com changed over time to accommodate the needs of the audience.

You can hear the podcast at
http://www.airsafe.com/podcasts/show57_secrets5.mp3

The transcript of this podcast is available at
http://www.airsafe.com/podcasts/show57.htm

Information about the special series is available at
http://secrets.airsafe.org

26 July 2008

In-Flight Emergency Involving a Qantas
747-400 Near Manila on 25 July 2008

On 25 July 2008, A Qantas airlines 747-400, with 346 passengers and 19 crew members on board, had an explosive decompression event over the South China Sea about 200 miles from Manila. The crew descended about 20,000 feet and successfully diverted to Manila. None of the passengers or crew were injured. A portion of the fuselage just forward of the wing root was found missing after the aircraft landed.

For information about other significant Qantas safety events, visit
http://www.airsafe.com/events/airlines/qantas.htm

For audio and video podcasts about this event, visit
http://www.airsafe.com/podcasts/show56.htm

You can also use the links below:
Audio: MP3
VideoWMV | iPod/MP4 | YouTube | Google Video

The transcript of this podcast is available at
http://www.airsafe.com/podcasts/show56.htm

For Other AirSafe.com podcasts, visit
http://podcast.airsafe.org

03 March 2008

Lufthansa A320 Has Close Call in Hamburg

On 1 March 2008, a Lufthansa Airbus A320 arriving from Munich was attempting a landing at Hamburg, Germany under high crosswind conditions. The left wingtip struck the ground during the attempt, and the crew successfully executed a go-around. The aircraft landed without further incident. At the time, winds at the airport were gusting up to 49 knots. The left wingtip and winglet were damaged, and there were no injuries to any occupants..

Video of the Event


Photos of Event and the Aircraft Damage




21 February 2008

Investigation Update #3 for the British Airways 777 Crash of 17 January 2008

This is the third update from AirSafe.com on the ongoing investigation into the accident at London's Heathrow Airport involving a British Airways 777. This update is based on information released by the AAIB on 18 February 2008, and focuses on analyses of the fuel system, the engines, and their associated control systems. You can listen to or watch the podcast at the following links:

Audio: MP3 | VideoiPod/MP4 | WMV | Google Video | YouTube

The links below will take you to additional related resources.

Additional Details About this Accident: http://777.airsafe.org
Transcript and Timeline for this Podcast
Other Podcasts

Video of the Podcast