recommended reading

Lithium ion battery short circuited in first 787 Dreamliner fire

National Transportation Safety Board engineer Matt Fox examines parts from the battery involved in the  787 fire in Boston.

National Transportation Safety Board engineer Matt Fox examines parts from the battery involved in the 787 fire in Boston. // NTSB

This story has been updated.

The National Transportation Safety Board has determined lithium ion batteries on a Japan Airlines Boeing 787 Dreamliner that caught fire on Jan. 7 at Boston’s Logan Airport experienced short circuits and a “thermal runaway” -- a rapid, uncontrolled increase in temperature, NTSB Chairwoman Deborah A.P. Hersman told reporters at the agency’s Washington headquarters today.

Hersman said such events “should not happen” on an aircraft that incorporated multiple systems to protect against fires. Boeing and aviation regulators worldwide grounded the 787 fleet after another aircraft operated by All Nippon Airlines made an emergency landing on Jan. 16 after experiencing what Hersman called a battery “smoke event,” not a fire.

Hersman said aircraft should never experience such events, particularly two on the same type of aircraft in two weeks.

"This is a very serious air safety concern,” Hersman said, referring to the battery problems. 

NTSB  examined the main battery pack, manufactured by GS Yuasa of Kyoto,  from the JAL 787 using a number of advanced scanning tools, including computed tomography (CT scan), and determined three of the eight cells showed signs of thermal runaway and different rates of short circuit damage; another cell showed high current damage.

Joseph Kolly, NTSB director of research and engineering, said the thermal runaway in the JAL 787 batteries could have been caused by short circuits or by “collateral damage from a neighboring cell.”

NTSB investigators are working around the clock in Washington and Japan to determine the cause of the 787 battery problems, in partnership with the Japan Transportation Safety Board, the FAA and Boeing, Hersman said. The Naval Surface Warfare Center, Carderock Division, in West Bethesda, Md., which has worked with lithium ion batteries since the 1970s, has provide “invaluable” assistance, Hersman said, but provided no further details.

NTSB has compared the charred battery recovered with what Hersman called an “exemplar” battery and has downloaded data from numerous 787 onboard systems, including the flight data recorder, or black box. The investigation is far from complete, however.

Hersman said investigators will examine not only the battery, but the globally sourced electrical power system Boeing chose to use instead of traditional hydraulic systems in an effort to reduce weight. NTSB is working to find out why the JAL battery caught fire “when so many protections were built-in,” Hersman said.

Thales, headquartered in a Paris suburb, has a contract for the 787’s electrical power conversion system. GS Yuasa supplies batteries to Thales subcontractor Securaplane, which manufactures the lithium ion auxiliary power unit and battery charger for the aircraft. Securaplane is a Tucson, Ariz.-based subsidiary of U.K.-based Meggiit PLC. NTSB is looking at this entire system to help determine the cause of the battery fire, Hersman said.

The system should have the ability to detect, mitigate and shut down batteries before a fire starts, Hersman said.

NTSB also will examine FAA’s certification process for the Dreamliner’s lithium ion batteries. In November 2007, FAA granted Boeing permission to operate the 787 under “special conditions,” which acknowledged the known flammability of lithium ion batteries.

“Design of the lithium ion batteries must preclude the occurrence of self sustaining, uncontrolled increases in temperature or pressure,” according to the conditions.

Hersman declined to say when NTSB might finish its investigation.

Threatwatch Alert

Thousands of cyber attacks occur each day

See the latest threats


Close [ x ] More from Nextgov

Thank you for subscribing to newsletters from
We think these reports might interest you:

  • It’s Time for the Federal Government to Embrace Wireless and Mobility

    The United States has turned a corner on the adoption of mobile phones, tablets and other smart devices, outpacing traditional desktop and laptop sales by a wide margin. This issue brief discusses the state of wireless and mobility in federal government and outlines why now is the time to embrace these technologies in government.

  • Featured Content from RSA Conference: Dissed by NIST

    Learn more about the latest draft of the U.S. National Institute of Standards and Technology guidance document on authentication and lifecycle management.

  • A New Security Architecture for Federal Networks

    Federal government networks are under constant attack, and the number of those attacks is increasing. This issue brief discusses today's threats and a new model for the future.

  • Going Agile:Revolutionizing Federal Digital Services Delivery

    Here’s one indication that times have changed: Harriet Tubman is going to be the next face of the twenty dollar bill. Another sign of change? The way in which the federal government arrived at that decision.

  • Software-Defined Networking

    So many demands are being placed on federal information technology networks, which must handle vast amounts of data, accommodate voice and video, and cope with a multitude of highly connected devices while keeping government information secure from cyber threats. This issue brief discusses the state of SDN in the federal government and the path forward.

  • The New IP: Moving Government Agencies Toward the Network of The Future

    Federal IT managers are looking to modernize legacy network infrastructures that are taxed by growing demands from mobile devices, video, vast amounts of data, and more. This issue brief discusses the federal government network landscape, as well as market, financial force drivers for network modernization.


When you download a report, your information may be shared with the underwriters of that document.