The AirSafe.com News

↑ Grab this Headline Animator

Showing posts with label fire. Show all posts
Showing posts with label fire. Show all posts

23 August 2013

Fire danger from Honeywell ELTs may exist on aircraft beyond the 787

After last month's fire involving the emergency locator transmitter (ELT) on a Ethiopian 787 in London, the FAA and other regulatory agencies around the world have ordered that these ELTs be deactivated, inspected, or removed. The ELT on that aircraft was manufactured by Honeywell, which has produced about 6,000 ELTs for use in aircraft around the world.

A recent airworthiness directive from Transport Canada airworthiness directive (AD), which takes effect on 26 August 2013, has gone a step further, requiring that Honeywell ELTs on a variety of aircraft be inspected by the end of 2013. Transport Canada stated that the AD was issued as a precautionary measure to address the possibility of a fire due to wiring installation discrepancies of the ELT system. Depending on the outcome of the AAIB investigation, Transport Canada may revise the AD or mandate additional corrective actions.



Affected aircraft
Previous directives from the UK and US authorities were limited to the 787. This latest Canadian AD covers a much wider range of aircraft, including the Boeing models 717, 727, 737, 747, 757, 767, 777, 787, MD11, MD80 and MD90; and the Airbus models A300, A310, A320, A321, A330, A340 and A380.

Other countries following Canada's lead
The European Aviation Safety Agency (EASA) has also adopted the Canadian AD. According to various media reports, the FAA also plans to issue a similar AD for US-registered aircraft.

Why ELT fires are potentially catastrophic
As was described in some detail in an earlier AirSafeNews.com article on the Ethiopian 787 event, fire caused by an ELT would be particularly worrisome because these devices, unlike other systems such as engines and auxiliary power units, do not come equipped with fire suppression systems, and they are typically located in parts of the aircraft that are inaccessible from the cabin. In the event of an in flight fire, it may not be possible to put out the fire, and it may spread to other parts of the aircraft.

In the event of an onboard fire, typical emergency procedures include landing at the closest suitable airport, but if the fire occurred if the aircraft were far from a a suitable airport, which would be the case for many transatlantic or transpacific flights, passengers and crew could be exposed to large amounts of smoke and fumes for a significant amount of time.

In such a situation, emergency oxygen systems may not have been useful for passengers since these systems are typically designed to supply passenger with a combination of oxygen from the emergency oxygen system and ambient air from the cabin, including any smoke or fumes that are present in the cabin.

26 July 2013

Disturbing implications of the recent 787 fire in London

The recent 787 fire at Heathrow Airport in London appeared at first to be a relatively minor event with a limited impact beyond the aircraft involved. However, when the investigative authority, the Air Accidents Investigation Branch (AAIB) of the UK, released its preliminary report on the event, the recommendations that were made implied that the problem had the potential to be far more serious had it occurred in flight.

Key findings of the AAIB report
The initial AAIB report, stated that the fire damage coincided with the location of the emergency locator transmitter (ELT), and although the AAIB did not state that the ELT was the source of the fire, the aircraft was unpowered at the time of the fire, and no other aircraft systems in the area contained an energy source capable of starting a fire. The ELT is designed to operate without any power from the aircraft's electrical system, and is powered by a set of chemical batteries using a Lithium-Manganese Dioxide (LiMnO2) composition. This kind of battery represents a different technology from the lithium-ion batteries associated with the fires on two different 787 aircraft in January 2013.

What the fire fighters encountered in London
According to the AAIB, when fire fighters entered the aircraft through the front left door (the 787 has four pairs of doors), they encountered thick smoke and had to open at least two other cabin doors to clear the smoke. They were unable to extinguish the fire with a handheld Halon fire extinguisher, and had to forcibly remove a ceiling panel and use water from a fire hose to put out the fire. While this was apparently not an complicated procedure for the fire crews on the ground, it could have been an entirely different situation had this occurred in the air.


Visible external damage to 787 in London

Why a fire in flight would have been much more dangerous
The AAIB investigation is ongoing, and the organization has not identified the ELT as the source of the fire. However, if the ELT turns out to be the source of this particular fire, it raises the very disturbing possibility that this kind of fire could have occurred not just on the ground in an empty aircraft, but also while the aircraft was in the air. This could potentially be a far more serious event in the air for the following reasons:

  • Unlike on the ground, opening one or more doors to evacuate smoke is not an option in flight,
  • While there are handheld fire extinguishers in the cabin that flight attendants can use in an emergency, equipment or other tools suitable for removing ceiling panels are not typically available to cabin crew.
  • While the fire fighters in the London incident had access to water hoses to put out the fire, no such option would be available to an airborne 787.
  • in the event of an onboard fire, typical emergency procedures include landing at the closest suitable airport, but since the 787 often flies on routes that are an hour or more from a suitable airport, passengers and crew could be exposed to large amounts of smoke and fumes for a significant amount of time.
  • Emergency oxygen systems may not have been useful for passengers since these systems are typically designed to supply supplemental oxygen, in other words, passenger would be breathing a combination of oxygen from the emergency oxygen system and ambient air from the cabin, including any smoke or fumes that are present in the cabin.

A nightmare scenario
Simply put, the aforementioned conditions imply that had this event occurred in the middle of a flight, the cabin crew may have been unable to reach the source of the fire, and even if they did, they may not have been able to put the fire out. The aircraft involved in the fire at London's Heathrow airport sustained damage to the composite structure of that airplane's fuselage. Conceivably, if the fire had been allowed to burn for a significant amount of time, a situation that could have occurred had the airplane been inflight, the fire could have led to significant damage to the aircraft's systems, or could have caused the aircraft to lose its structural integrity. Either outcome could have led to the loss of the aircraft and all on board.

An additional twist to this story
While the previous scenario may be disturbing to the average passenger, what may cause additional concerns, especially to aircraft manufacturers and airline operators, is the possible role of the ELT in the fire in London. This is a system that is noteworthy for not being a source problems that could lead to the loss of an airliner. In fact, according to the AAIB, the manufacturer of the ELT involved in the London fire, Honeywell, has produced some 6,000 ELT units of the design used in the Ethiopian 787 involved in the London fire event, and that event is the first incident where the ELT system generated a significant level of heat.

Actions taken to deal with the threat
Following the recommendations of the AAIB, the FAA and other regulatory agencies around the world have ordered that 787 ELTs be deactivated, inspected, or removed. Until the AAIB, Boeing, and Honeywell figure out the role played by the ELT in the London fire, questions will remain as to whether the 787 ELT represents an unexpected and potentially fatal risk to 787 passengers.

18 July 2013

AAIB releases bulletin on 787 fire plus additional 777 crash interviews

On 18 July 2013, the UK's Air Accidents Investigation Branch (AAIB) released a special bulletin related to the 12 July 2013 fire on an Ethiopian Airlines 787 at London's Heathrow airport. The AAIB made two safety recommendations, the first was to advise the FAA to initiate action to have 787 operators deactivate the emergency locator transmitter (ELT), and the second was to have the FAA conduct a safety review of the installation of ELTs in other aircraft where the ELTs are also powered by lithium batteries.

While the AAIB does not have any authority to implement these recommendations, it is very likely that the FAA, Boeing, and all of the 787 operators will respond relatively quickly to the recommendations.

AAIB summary of the fire
The AAIB special bulletin contained the following key information about the events leading up to the fire:

  • The Ethiopian Airlines 787 landed at Heathrow at 0527 hours on 12 July 2013 after an uneventful flight, with no technical problems reported by the crew.

  • After it was towed to a parking area, external power was turned off, and the aircraft was left unpowered.

  • An employee in the air traffic control tower noticed smoke coming from the aircraft at 1534 hours, and fire fighters arrived about one minute later.

  • After a fire crew entered the aircraft, they observed indications of fire above the ceiling panels, and had to move a ceiling panel in order to put out the fire.

  • A later examination revealed extensive heat damage in the rear fuselage in the crown area, just to the left of the centerline, an area which coincided with the location of the ELT.

  • The ELT, which was powered by a set of chemical batteries containing a Lithium-Manganese Dioxide composition, was the only aircraft system in that area that had the potential to initiate a fire when the aircraft was unpowered.

About emergency locator transmitters
ELTs are battery-powered radio transmitters that are carried aboard airliners, other civil aircraft, and most military aircraft. Thay are designed to survive most accidents, and to transmit a signal that can be used by rescue crews and even satellite-based monitors to locate a crash site. The FAA requires the use of ELTs on commercial airliners.

According to the AAIB, the manufacturer of the ELT associated with the recent 787 fire (Honeywell) has produced about 6,000 ELTs for use in a wide range of aircraft, and this the first time the manufacturer has what the AAIB calls a 'thermal event.'

The ELTs used by Boeing in the 787 are all made by Honeywell, and they are powered by a set of five non-rechargeable batteries, each of which is roughly the size of a common household "D" cell battery.

What's next for the 787
There are currently 68 787 aircraft flying with 13 operators around the world. Although the FAA has not made a formal request for airlines to implement the AAIB recommendations, it is likely that Boeing and the airlines will take action relatively quickly. If the recommended actions are taken, in the short term 787s may be flying without ELTs.

While flying without ELTs may make it harder to find an aircraft that has an emergency in an unpopulated area, the FAA can allow airliners to fly for short periods of time without a working ELT, so implementing these AAIB recommendations will likely not cause the FAA to ground the 787. Other regulatory bodies around the world typically follow the actions of the FAA in situations such as this one.


Media interviews with Dr. Todd Curtis about the Asiana 777 crash
The following three interviews with Dr. Curtis were made in the days immediately following the crash of Asiana flight 214

- WGN radio - The Dean Richards show on 8 July 2013
- Bloomberg television interview 8 July 2013

CCTV America 8 July 2013

Additional information

17 July 2013

Update on 787 fire in London plus radio interview on 777 crash

Update on the 12 July 2013 787 fire in London
On 12 July 2013, an Ethiopian Airlines 787 caught fire while parked on an apron at London's Heathrow Airport. There were no passengers on the aircraft at the time of the fire, and no one was injured or killed.

The initial witness and physical evidence shows that this event resulted in smoke throughout the fuselage and extensive heat damage in the upper portion of the rear fuselage. The photo below shows that the fire burned through the top of the fuselage in the rear of the aircraft between the two rear doors and near the base of the vertical fin.


(click to enlarge)

The British Air Accidents Investigation Branch (AAIB) is investigating the fire, and has not yet released any statement about the likely causes of the fire. However, several things are known about the investigation:

  • The aircraft had arrived from Addis Ababa, Ethiopia about nine hours before the fire was discovered.

  • In addition to the AAIB, participants in the investigation include the FAA, NTSB, the Civil Aviation Authority of Ethiopia, Boeing, Ethiopian Airlines, and Honeywell International.

  • Honeywell is the manufacturer of the emergency locator transmitter (ELT) used in the 787.

  • The battery in the ELT is based on a lithium manganese-dioxide technology and not on the lithium-ion technology associated with the batteries that caught fire on two different 787 aircraft in January 2013.

  • The fire was in the rear of the fuselage, and was remote from the areas of the aircraft containing the main battery and the auxiliary power unit batteries, the batteries associated with the grounding of the entire 787 fleet earlier this year.

Dr. Todd Curtis interviewed by eFM radio in South Korea
In the following July 15, 2013 interview on the South Korean eFM radio show Prime Time with Henry Shinn, Dr. Todd Curtis discussed several issues associated with the ongoing investigation into the July 6, 2013 crash of an Asiana 777 in San Francisco, CA, including speculation about the cause of the crash, the role of automated systems in the cockpit, and the NTSB investigative process. Many of the issues raised in this interview included questions about the 777 crash answered in a previous article.

Additional information

13 July 2013

Summary of final two NTSB briefings on Asiana 777 plane crash in San Francisco

On Wednesday, 10 July 2013 and Thursday, 11 July 2013, NTSB conducted their final two press conferences in San Francisco, and covered a variety of issues around the accident, including the operation of the autopilot and autothrottle, damage to the airplane, injuries to the flight attendants, the evacuation of the aircraft, and other initial factual findings from the investigation.

The NTSB emphasized in both of these press conferences that the information was factual in nature, and in many cases had not yet been confirmed or corroborated. For example, statements received from the flight crew still have to be matched up with information from sources such as the cockpit voice recorder (CVR) and the flight data recorder (FDR).

Cockpit automation and its role in the crash
As mentioned in a previous AirSafeNews.com article, use of the autothrottle by the crew to maintain speed was an issue because although the crew was heard on the CVR stating that the target speed was 137 knots, the aircraft was significantly slower than that speed before the crash. In Wednesday's press conference, the NTSB stated that there were five distinct autothrottle modes used in flight, and in the last 2.5 minutes of flight, there were several autothrottle and autopilot modes used.

As explained by the NTSB, the autopilot helps pilots manage pitch, roll, attitude, and heading; while the autothrottle helps to control speed or thrust. The two systems can work together, and the NTSB has to determine, with the help of Boeing, the following:

  • Whether autopilot and autothrottle modes were commanded by the pilots or activated inadvertently,
  • How the various autopilot and autothrottle modes are designed to work, and
  • What are the ways the systems are expected to respond in the various modes.

Comparison to automobile cruise control
NTSB chair Deborah Hersman used an analogy to a much simpler automated system to illustrate the role that an autothrottle plays. Like in an airliner, a car's cruise control can be set to a specific speed, but it is up to the driver to monitor the speed. Also, cruise control may not engage if the car is in a particular mode, for example below a certain speed. While in cruise control, the driver may be allowed to increase or decrease speed within certain limits. Disengaging cruise control can be done by disarming the system or by hitting the car's brake.

Status of the pilots on flight 214
There were a total of four pilots on board, and they consisted of two crews. The first crew consisted of a training captain going through his initial operating experience (IOE) on the 777 and an instructor pilot (IP) who was a training captain. The relief crew consisted of a captain and a first officer (FO) This first crew performed the takeoff from Seoul and flew for several hours before the relief crew took over, and then the first crew flew approximately the last 1.5 hours of the flight.

Shortly before landing, when the aircraft was at around 10,000 feet, the relief FO entered the cockpit and was in the jumpseat for the rest of the flight. The NTSB provided details on the experience of the three pilots in the cockpit:

  • The training captain was in the left seat at was the pilot flying (PF),
  • The training captain had about 9,700 total hours, including about 5,000 as pilot in command (PIC),
  • The PF was hired by Asiana in 1994, and trained in Florida,
  • The PF was rated to fly the 737, A320, 747, and 777, and from 2005-2013 flew the A320, serving as an A320 captain before moving to the 777,
  • The PF was also a ground school and simulator instructor for the A320 and A321
  • The IP was also a 777 captain who served in the South Korean air force for about 10 years before joining Asiana,
  • The PF's IOE was to consist of 60 flight hours and 20 flight legs, and had gone through 10 flight legs and about 35 flight hours at the time of the crash,
  • The IP had about 13,000 flight hours, including about 3,000 in the 777, and 10,000 as a PIC,
  • The IP served as the PIC on flight 214, and was sitting in the right seat,
  • This flight was the first time that the PF and the PIC had flown together, and it was the PIC's first trip as an instructor pilot
  • The relief FO was a former F-5 and F-16 pilot in the South Korean air force, and had about 4,600 total hours, including 900-1,000 hours in the 777,
  • The relief FO had flown to San Francisco five or six times as an observer.

Landing aids in use at the airport
Air traffic control was allowing pilots to operate under visual flight rules (VFR) when flight 214 was approaching the San Francisco airport (SFO), which means that pilots were not required to use the instrument landing systems at the landing runway (28L) or any automated systems on their aircraft. One of the electronic aids that provide aircraft guidance on their glide slope was inoperable, but this had been published for some time and all flight crews using the airport should have been able to see this information. The NTSB has not stated if this crew were aware of this.

A glide slope aid that was in operation at runway 28L were the precision approach path indicator (PAPI) lights, a set of four lights arranged in a horizontal line that provide pilots with a visual indicator of whether the aircraft on the glide slope, above the glide slope, or below the glide slope.

A pilot who is on the glide slope would see two sets of red lights on the left and two sets of white lights on the right. In the example shown here (not from SFO), the three left indicators are red and the right one is white, indicating that the aircraft is slightly below the glide slope. Four red lights would indicate that the aircraft is well beloe the glides slope, and four white lights is an indicator of being well above the glide slope.

Final approach sequence
Over the last two press conferences, the NTSB discussed the following key parts of the final approach:

  • The approach path took the aircraft directly over SFO, followed by a wide teardrop left turn to line up with the runway (see below),

    (click to enlarge)
  • Air traffic control (ATC) called for a maximum airspeed of 180 knots until the aircraft was five miles out,
  • The IP recalled that the aircraft was above the intended glide path at 4,000 feet, and that vertical speed mode was set at 1,500 feet per minute,
  • ATC gave a landing clearance about 1.5 miles from the runway, about 90 seconds prior to the crash,
  • There was a sink rate callout prior to the aircraft reaching 500 feet,
  • At about 500 feet, the FP noted a blinding flash of light directly in front of the aircraft but not on the runway,
  • The FP stated that he looked away into the cockpit, and was able see the cockpit instruments, including the speed tape,
  • There was no mention of the light on the CVR,
  • The FP believes it may have been a sun reflection, and the NTSB is determining if this could have been the case,
  • There was an automated 500 foot callout about 35 seconds before the crash,
  • Shortly after this callout, the landing checklist was completed,
  • At about 34 seconds prior to impact, the IP noted that the aircraft was below the glide path at 500 feet, and speed was at about 134 knots, with three red PAPI lights showing, and told the PF to pull back
  • Autothrottle was armed and set at 137 knots
  • between 500-200 feet, the IP noted that there was a lateral deviation and that the aircraft was low,
  • At 200 feet, the IP noted four red PAPI lights, that the speed tape was hatched (a visual indicator of an impending stall), and that the autothrottle had not maintained speed,
  • There was an automated 200 foot callout 18 seconds before impact,
  • There was an automated 100 foot callout nine seconds before impact,
  • Almost immediately after this 100 foot callout, a crew member mentioned airspeed (the NTSB noted that there were no mentions of speed heard on the CVR between 500-100 feet),
  • About three seconds before impact, there was a call for a go around,
  • The IP established a go around attitude, and went to push the throttles forward manually, but saw that the FP had already done so,
  • A second call made for a go around was made by a different crew member about 1.5 seconds before impact.

Crash sequence

  • The main landing gear hit the sea wall first, followed by the tail section,
  • The main landing gear sheared away from the aircraft as designed, and the wing fuel tanks were not punctured by the gear separation or during the the rest of the crash sequence,
  • Cabin flooring and galley components were found on the chevrons in the runway overrun area between the sea wall and the runway threshold,
  • The initial impact displaced rocks from the sea wall and some of them were distributed several hundred feet along the debris trail (see photo below),

    (click to enlarge)
  • All passenger seats stayed inside the cabin, but three flight attendant seats were ejected onto the runway,
  • Door 4L detached from the aircraft at some point in the crash sequence
  • Six of the 12 flight attendants were interviewed, and they stated that two of the eight escape slides inflated inside the cabin after a secondary impact (from a witness video, it appears that the aircraft rotated almost 360 degrees counter clockwise, with the rear of the cabin rising up at an angle before hitting the ground at the end of the crash sequence),
  • The right engine had detached from the wing, had rotated about 90 degrees counter clockwise, and was laying alongside the fuselage (see photo below).

(click to enlarge)

Post-crash actions and fire

  • After the aircraft came to a stop, the lead flight attendant (who was near door 1L) went to the cockpit for advice, and was advised not to initiate evacuation (see door layout in photo below),

    (click to enlarge)
  • Fire extinguisher switches were pulled for both engines and the auxiliary power unit,
  • The flight crew was able to communicate with the control tower, and the cabin crew was able to use the public address system to communicate to passengers,
  • A flight attendant who was trained as a lead flight attendant was at door 2L, saw fire outside door 2R near row 10 of the aircraft, and sent the other flight attendant at door 2L to the front of the cabin to inform the rest of the crew about the fire and the need to evacuate (in earlier briefings, the NTSB stated that the source of the fire was a ruptured oil tank that leaked fuel onto hot engine parts from the right engine),
  • Passenger evacuation began about 90 seconds after the aircraft came to a stop, escape slides were first deployed from door 2L and then from door 1L, and passengers also escaped from door 3R,
  • The control tower called for emergency vehicles after the aircraft hit the runway, the first vehicle arrived about two minutes after the crash, and extinguishing agent was first applied about three minutes after the crash,
  • Cabin emergency exit lighting came on during the evacuation,
  • There were six flight attendants who were injured and hospitalized: three seated in the rear of the plane who were ejected out onto the runway, another flight attendant in the rear who was injured, and two who were injured by the slides that deployed inside the cabin including one at door 1R and a second at door 2R,
  • The remaining six flight attendants had evacuated most of the passengers by the time the fire had spread to the cabin,
  • Aiport fire crews entered the cabin with a fire hose to help fight the fire,
  • Flight attendants helped to fight the fire with fire extinguishers, and also used the extinguishers to help extract the two flight attendants who were trapped by the two escape slides that deployed inside the cabin.

Cabin damage
Prior to the cabin fire, a firefighter entered door 2L and turned right to walk toward the rear of the cabin, and along the way observed that seats in that section were almost pristine, with minimal damage detectable, and that one could just fluff the pillows to get that section ready for the next flight. As he walked toward the rear, he observed more cabin damage, with a sharp contrast between the front and back of the passenger cabin. The photo below shows the pristine area of the cabin that was later damaged by fire.


(click to enlarge)

The NTSB structures team noted that from the cockpit to rear spar of the center wing box, the cabin floor was structurally sound. Aft from the rear spar to doors 3R and 3L, in the passenger seating compartment, support structure were compromised on the right side (flayed out from the aircraft), but still sound on the left side. Between doors 3 and 4, the floor was canted down at an angle, with damage progressively worse towards the back, and there was no cabin floor behind door 4.

Dr. Curtis and Capt. Tom Bunn discuss the crash
The day after the crash, Dr. Curtis of AirSafe.com and Capt. Tom Bunn of the SOAR fear of flying program, who both spent several hours on the day of the crash on cable news programs providing expert commentary, discussed the media's response to the accident and shared their thoughts on the early reports of the crash.

Additional information
AirSafeNews.com 10 July 2013 article on the role of the autothrottle
AirSafeNews.com 8 July 2013 article on early findings of the crash investigation
Other Asiana plane crashes
Other 777 plane crashes
Accident details from Aviation Safety Network
Wikipedia page on this accident

Photos: Wikipedia, NTSB

19 May 2013

JAL 787 damaged by battery fire apparently needed extensive repairs

After an ANA and JAL 787 aircraft experienced battery fires in January 2013, the entire fleet of 49 aircraft was grounded while the problem was diagnosed and an acceptable plan for fixing returning the aircraft to service was developed. While Boeing did come up with a repair plan that was acceptable to the FAA, it appears that the JAL 787 that experienced a battery fire in Boston had to also go through a very extensive set of repairs before it could return to service.

Electrical system changes
As described in an earlier article, Boeing and the battery manufacturer have made a number of FAA-required changes to the 787, including the installation of a redesigned battery, that the FAA estimated would take about 113 work hours to complete.

Several media outlets, including the BBC and New York Times, reported that during an interview in late April 2013, Larry Loftis, vice president and general manager of the 787 program, stated that the Boeing modification kit would take about five days to install. Given the estimate of 113 work-hours from the FAA, that implies that a small team of maintenance personnel could put the aircraft back in service within that time frame. However, for the JAL aircraft that caught fire in Boston, that has clearly not been the case.

The aircraft has been grounded in Boston since its APU battery caught fire on January 7th, and was still on the ground at least until May 12th, over two weeks after the first updated 787 returned to service. The aircraft was parked outside near one of the airport terminals, and could be easily seen from several public vantage points.

As you can see the photo below, there was a large tent erected next to the 787, presumably associated with the aircraft repair. According to one eyewitness, a second, similarly sized tent, had been recently removed, and had be in place for a number of days.

No public reports of repair efforts
Although the NTSB has an ongoing major investigation associated with the 787 battery fire event, no final report has been published, and the information currently on the NTSB site does not mention any significant damage to the aircraft beyond the structures and systems close the battery that caught fire. Neither Boeing, JAL, or Massport, the organization the manages Boston's Logan Airport, have released any statement to the public about any significant additional aircraft damage.

Share what you know
If you have direct knowledge of what may have been going on with the JAL 787 in Boston, specifically details about any repairs that may have been performed on this grounded 787, please feel free to contact AirSafe.com at feedback.airsafe.com.

30 April 2013

Crash of a National Airlines 747-400 at Bagram Air Base

29 April 2013; National Airlines; 747-400; N949CA; Bagram Air Base, Afghanistan: The aircraft had just departed on a cargo flight to Dubai, UAE when the aircraft entered a stall and crashed near the end of the runway. At one point, the aircraft had rolled to the right in excess of 45 degrees. Although the crew was able to put the wings more or less level, the aircraft impacted the ground at a high vertical speed, and in a slightly nose down attitude. In a video taken of the crash, it appears that the landing gear were at least partially extended at the time of impact.

All seven crew members were killed. Cargo included several vehicles. Although the aircraft was flying in support of coalition forces in Afghanistan, there is not indication that the crash was caused by hostile action.

National Airlines is a US-based all cargo airline. The flight was operating support the coalition forces in Afghanistan, but there is no indication that the aircraft crashed due to hostile action.

According to AirFleets.net, in addition to the accident aircraft, the airline had two other 747–400s, and a 757 aircraft in their inventory. That same site indicated that the aircraft was originally delivered to Air France in 1993, converted to a freighter in 2007, and entered service with National Airlines in 2011.

The747-400 entered service in 1989 and was in production until 2009. While some examples of this model, like the accident aircraft, were converted to freighters from a passenger configuration, other 747–400s were designed as cargo-only aircraft.

This is the fourth fatal crash involving 747–400. The first was an October 2000 crash accident involving Singapore Airlines passenger flight that crashed just after takeoff after striking construction equipment on the runway. The crash killed 79 of the 159 passengers and four of the 20 crew members on the aircraft.

The second fatal crash involved a UPS flight in September 2010 which Crashed shortly after takeoff from Dubai United Arab Emirates. Both crew members were killed. The third was in July 2011 event involving an Asiana airlines 747 – 400 that crashed shortly after catching fire during a flight from Seoul to Shanghai.




Resources
747 Plane Crashes

27 April 2013

787 Dreamliners return to service

More than three months after being grounded by the FAA and by other aviation authorities around the world due to a pair of battery fire incidents, the 787 is flying once again. While US and Japanese investigations into the causes of the fires continue, the FAA has allowed the 787 to return to service once airlines install a number of required changes to the electrical system. These changes would either reduce or eliminate the likelihood of a battery problem, or would reduce the impact of a problem if it were to occur in the future.

Battery system problems
On January 7th of this year, a JAL 787 that was parked at the gate at Boston's Logan Airport had a battery fire in the aft electronics equipment bay. The fire produced a significant amount of smoke, but only a minor amount of damage. At the time, the aircraft had only a maintenance crew on board. Later that month, on January 16th, an ANA 787 experienced a battery fire in the forward electrical equipment bay while in flight, leading to an unscheduled landing and evacuation of passengers and crew by emergency slides.

During the 787 certification process, Boeing estimated that the battery would have an event that would emit smoke roughly once every 10 million flight hours. The two January 2013 battery smoke events occurred after only about 52,000 flight hours for the worldwide 787 fleet, a frequency that was roughly 190 times the predicted rate.

Electrical system changes
Boeing and the battery manufacturer have made a number of FAA-required changes to the electrical system, primarily to the battery systems that uses lithium ion batteries to power aircraft electronics and other aircraft systems like the auxiliary power unit. The changes are meant to prevent similar battery failures, or to contain the effects should they occur in the future:

  • Redesigned lithium ion battery that features a lower operating temperature
  • Addition of a sealed, stainless steel battery enclosure to help contain smoke and heat from a fire
  • Replacement of the battery chargers.
  • Installation of a venting system that would allow any smoke of fumes from a fire to vent outside of the aircraft.
  • An FAA Airworthiness Directive about the required changes estimated that the costs to implement the changes for the six aircraft covered by the AD (United Airlines 787s) would be about $2.8 million.

Return to service
The first operator to return the aircraft to service was Ethiopian Airlines on April 27, 2013. Other carries with grounded 787s will return their aircraft over the next few months, with Air India and United Airlines likely returning their aircraft. Boeing is sending teams around the world to put those changes in place, and any newly delivered aircraft will incorporate these changes.

Battery fire investigations
Both the NTSB and the JTSB continue to investigate the cause of the battery fires in the US and Japan. On April 23-24, 2013, the NTSB held an investigative hearing involving the FAA, Boeing, and the battery manufacturers. While the NTSB concluded that the original battery certification tests were inadequate, there was no determination of the probable cause of the battery fire in Boston. It is likely that it may be several months before the NTSb or the JTSB reach a conclusion about the cause of the fire.

16 February 2013

Video of webinar on 787 battery fire investigation now available

Dr. Todd Curtis of AirSafe.com hosted a 14 February 2013 webinar discussed the January 2013 grounding of the entire 787 fleet after two serious fires on a JAL and ANA 787 involving lithium ion batteries. Dr. Curtis summarized the status of the investigations by the NTSB and JTSB, and explains the process that Boeing and the airlines will go through in order to return the aircraft to service.

Previous AirSafeNews.com Articles
Should passengers fear the 787? - 18 January 2013
FAA orders comprehensive review - 11 January 2013
What's wrong with the 787? - 9 January 2013

For additional information on the 787 investigation, including links to the ongoing investigation of the NTSB, visit 787.airsafe.com.

18 January 2013

Should passengers fear the 787?

Should you be afraid to fly on the 787? If you listen to or read some of the more dramatic stories from some media outlets, the 787 is a flying death trap that should scare the living daylights out of anyone who is even thinking of flying in one.

The FAA and other civil aviation organizations have taken the rare step of grounding an entire fleet of aircraft until a thorough investigation can find the cause of several recent incidents, most notably battery fires that occurred in two different 787 aircraft over the last couple of weeks, including a fire earlier this week that led to the evacuation of the 787 pictured below.


While the investigation continues, more than a few major media outlets are painting a rather dire picture, speculating that there may be serious, even fatal flaws in the aircraft design that could ruin the program, make airlines and passengers abandon the aircraft, and even bankrupt Boeing.

Is all this speculation supported by any facts? It is too early to tell. It could turn out that the worst fear mongering of the most irresponsible media outlets could turn out to be true. Perhaps it could also turn out that there is no serious problem at all, and within a few days the problem will be fixed and the 787 will be flying again.

The reality is that the truth will likely be somewhere between these two extremes, and the if the history of previous introductions of new airline models is any guide, it is very likely that end of the story of the 787 grounding will have an ending that is closer to the more benign extreme.

If you are a concerned future 787 passenger, what should you do? You should pay attention to the unfolding story and make up your own mind on whether you want to fly on a 787. Based on what usually happens in in the world of aircraft development, the story will most likely unfold in the following way:

  • Boeing, the current 787 customers, the FAA, the NTSB, and the Japanese aviation authorities, as well as other relevant parties, will get together and share relevant data about the design, certification, assembly, and operation of the 787.

  • Dozens or perhaps hundreds of the appropriate experts will work together to figure out what went wrong, why it went wrong, and what has to be done to fix the problem.

  • The FAA and Boeing will require that airline operators take a number of specific actions to resolve the key 787 issues, and all of these requirements will be openly shared with the general public.

  • The changes will be made, the aircraft will return to service, and all the relevant parties will follow the 787 very closely to ensure that the changes worked.

  • Sometime in the next few weeks or few months, normal production and service will resume.

My prediction is that as the investigation process moves forward, the media and concerned passengers will pay less and less attention to potential 787 safety issues.

Is this what will happen with the 787? Only time will tell, but if the past is any guide, the scenario laid out here will be the one you will most likely see.





Photo credit: Reuters

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.


24 March 2011

Qantas A330 diverts after cockpit fire

A Qantas Airbus A330-200 (VH-EBL), with 147 passengers and 11 crew members on board, was on a scheduled international flight from Manila to Sydney, and cruising about 420 miles (675 km) northwest of Cairns, Australia on 22 March 2011, when there was a small electrical fire in the cockpit.

According to several media reports, the fire was initially extinguished by an automated fire fighting system. The fire flared up several minutes later, and one of the crew members extinguished it with a fire extinguisher. The crew diverted to Cairns and landed about 50 minutes later. According to a Qantas spokesperson, an electrical fault caused smoke and small flames near the left windscreen. None of those on board were injured.

The Australian Transport Safety Bureau, which is Australia's equivalent to the US National Transportation Safety Board, is investigating this Qantas incident.

Previous A330 cockpit fire event
This is not the first Airbus A330 cockpit fire involving a Qantas aircraft. On 10 June 2009, this JetStar aircraft (JetStar is a subsidiary of Qantas) had a cockpit fire during a flight from Osaka, Japan to Australia's Gold Coast Airport (about 60 miles south of Brisbane).

According to a report from the Australian Transport Safety Bureau, while the aircraft was flying about 427 km southwest of Guam, the flight crew noticed a burning rubber smell on the flight deck. At about that time, two caution messages were displayed to the crew identifying a fault in the right windshield heating. This was followed by a loud bang along with a flash of light, followed by smoke and fire from the bottom right corner of the right windshield. All flight crew donned oxygen masks, and a crew member used a fire extinguisher to extinguish the fire. The aircraft diverted to Guam and landed without incident.

Additional Resources
2008 Qantas A330 event with injuries
Other noteworthy Qantas events
Fatal A330 crashes

Photos: Min Bajunid, Airbus

28 September 2008

Fatal Jet Crash Injures Blink-182 Drummer Travis Barker

Travis Barker, former drummer for the music group Blink-182, Adam Goldstein, more widely known as DJ AM, and two other passengers were in a Learjet 60 aircraft that was on a chartered flight from Columbia, South Carolina to Van Nuys airport in Los Angeles. The crash, which happened shortly before midnight, occurred during takeoff. According to information from the plane's cockpit voice recorder, the crew was attempting to abort the takeoff because of what they thought was a blown tire. The NTSB also reported that accident investigators reviewing the recording heard sounds consistent with a tire blowout.

The crew was unable to stop the aircraft before it departed the runway. The plane struck a series of antennas and lights, crashed through a fence, crossed a nearby highway, and came to rest on an embankment where it burst into flames.

The crash and subsequent fire killed both flight crew members and two of the four passengers. The two survivors, Barker and Goldstein, escaped the aircraft but suffered severe burns. Goldstein is also the former fiance of television personality Nicole Ritchie. Barker and Goldstein had performed at a concert earlier in Columbia, and the two passengers who did not survive were support staff for the artists.

The aircraft was operated by Global Exec Aviation of Long Beach, California. Less than an hour before the accident, the plane had arrived in South Carolina from Teterboro, New Jersey. The FAA and NTSB online incident and accident databases showed no other events involving this aircraft, or the aircraft operator.

The Learjet 60 first flew in 1991 and was certified in 1993. This was the second fatal Learjet 60 crash, with the first occurring in 2002 in Brazil. According to the NTSB, there were six other Learjet 60 accidents and serious incidents, including one during flight testing in 1992. The FAA lists 23 less serious incidents since 1996.

The NTSB has dispatched an 11-member team to investigate this crash. The investigation, including a determination of the probable cause of the accident, will likely take several months to complete.

Additional information about this event, including updates or findings from the NTSB investigation, will be available at blink182.airsafe.org.

Accident Overview



You can also use the links below for the podcast:
AudioMP3
VideoiPod/MP4 | WMV | Google Video | YouTube

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

21 August 2008

Crash of Spanair MD82 on 20 August 2008

The aircraft crashed shortly after takeoff on a scheduled domestic flight from Madrid to Las Palmas in the Canary Islands. Early reports indicated that the left engine experienced a major malfunction during the takeoff. The aircraft was able to get airborne, but the crew set the aircraft down in a area to the right of the departure runway. The aircraft broke up and there was a severe post-crash fire.
http://www.blogger.com/img/gl.link.gif
There were 162 passengers and 10 crew members on board, and 153 of the 172 occupants were killed. Among the passengers were 20 children and two infants. Both infants reportedly survived. Many of the 19 survivors suffered burns, some of them serious.

This was also a code share flight with Lufthansa, and that airline reported that seven of their passengers had transferred to the Spanair flight from a previous Lufthansa flight. , and that airline reported that seven of their passengers were checked in for the flight.

About Spanair
This was the first fatal event for Spanair, the second largest of the five airlines in the SAS Group. The airline began operations in 1988. At the end of June 2008, there were 65 aircraft in the Spanair fleet, averaging 13 years old. The fatal event aircraft was built in 1993.

About the MD80
This was the 15th fatal event involving the MD80 series aircraft. Four fatal events have been in Europe, and four in the US. The aircraft began commercial operations in 1980, with the first fatal event in 1981. This latest crash was the eighth fatal MD80 event since 2000.

For additional information on this crash, including links to related audio and video podcasts and updates on the investigation, visit
http://spanair.airsafe.org.



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

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

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