Business

January 10, 2013

Federal investigators beef up scrutiny of 787 fire

ap-boeing-787Federal safety investigators intensified their scrutiny of a Jan. 7 fire aboard a Boeing 787 as concerned investors sold shares in the aircraft maker for a second day.

Boeing on Jan. 8 confirmed that the fire aboard a Japan Airlines plane appeared to have started in a battery pack for the plane’s auxiliary power unit.

The National Transportation Safety Board described the fire damage to the battery as “severe,” and said it is sending two more investigators to examine the Japan Airlines plane. It also formed investigative groups to look at the plane’s electrical systems as well as the fire response.

Boeing has a lot riding on the 787. The long-range jet promises a smoother travel experience and is 20 percent more fuel efficient than older models. After years of delays, Boeing has now delivered 49 of the planes, with almost 800 more on order.

The Jan. 7 fire happened on the ground at Boston Logan International Airport, with no passengers on board. But in-flight fires can be catastrophic, so the matter is getting close scrutiny by aviation authorities.

Interest is especially high in this fire because of indications that lithium batteries — which generally have not been used on large planes before the 787 — can burn very hot, with fires that are difficult to put out. The NTSB said it took firefighters 40 minutes to put out the fire near the back of the plane.

JAL spokeswoman Carol Anderson said the airline inspected its 787s after the fire. She declined to discuss the results, but noted that no schedule changes were made as a result of the inspections.

United Airlines said it inspected its six 787s overnight. A spokeswoman would not say what the inspections found. The Wall Street Journal reported that the inspections found an improperly installed bundle of wires connected to the same battery that burned on the on the JAL plane.

Electrical problems have been the 787’s nemesis.

Last month, a United Airlines 787 flying from Houston to Newark, N.J., diverted to New Orleans because of an electrical problem with a power distribution panel. Last week, United said it would delay the start of 787 flights from Houston to Lagos, Nigeria because it wanted to “improve the reliability of the aircraft.”

In November 2010, a test flight had to make an emergency landing after an in-flight electrical fire. The fire delayed flight tests for several weeks while Boeing investigated.

Boeing said the Jan. 7 fire appears to be unrelated to previous electrical problems on the 787.

“Nothing that we’ve seen in this case indicates a relationship to any previous 787 power system events,” Boeing said in a prepared statement. Those earlier problems involved power panels elsewhere in a rear bay for electrical equipment. Boeing also said it “would be premature to discuss additional details at this stage” of the investigation.

Boeing said it has shared information about the prior events with the NTSB.

Shares of Chicago-based Boeing have fallen 4.6 percent since the fire was reported. Investors may have been unnerved by the fire after it appeared that the mechanical and manufacturing kinks with the 787 had been worked out.

They may have also reacted to another 787 issue Jan. 8. A different Japan Airlines 787 at Logan had to be towed back to the gate after spilling 40 gallons of jet fuel. The flight was re-scheduled for later in the day. AP

 




All of this week's top headlines to your email every Friday.


 
 

 

Headlines October 20, 2014

News: Navy grounds ‘Top Guns’ - The F/A-18s needs spare parts and in too many cases they’re being taken from brand new jets. This is a risk to national security and pilots’ lives.   Business: Boeing seeks revised schedule for U.S. aerial tanker - Boeing is revising its master schedule for developing the new U.S. Air Force...
 
 

News Briefs October 20, 2014

New military medical team to help with Ebola in U.S. Defense Secretary Chuck Hagel has ordered the military to prepare and train a 30-member medical support team that could provide short-term help to civilian health professionals if there are more Ebola cases in the United States. His spokesman, Rear Adm. John Kirby, says the team...
 
 

Dragon ‘fires up’ for flight

The Air Force and NATO are undergoing a cooperative development effort to upgrade the avionics and cockpit displays of AWACS aircraft belonging to the 552nd Air Control Wing at Tinker Air Force Base, Okla., and the NATO E-3 Sentrys from Geilenkirchen, Germany. The Diminishing Manufacturing Sources Replacement of Avionics for Global Operations and Navigation, otherwise...
 

 
Boeing photographs

Boeing-built X-37B successfully completes third flight

Unmanned spacecraft concludes record-setting 674-day mission   Boeing photograph A third mission of the Boeing-built X-37B Orbital Test Vehicle was completed on Oct. 17, 2014, when it landed and was recovered at Vandenberg...
 
 

Boeing concludes commercial crew space act agreement for CST-100/Atlas V

Boeing has successfully completed the final milestone of its Commercial Crew Integrated Capability Space Act Agreement with NASA. The work and testing completed under the agreement resulted in significant maturation of Boeing’s crew transportation system, including the CST-100 spacecraft and Atlas V rocket. NASA in July approved the Critical Design Review Board milestone for Boeing’...
 
 

AF to release small business research solicitations

The Air Force Small Business Innovation Research and Small Business Technology Transfer program office is set to release its fiscal year 2015 list of topics Oct. 22, on the SBIR/STTR website.  Small businesses and research institutions with expertise to address the topics’ technology challenges are encouraged to submit proposals. During 2014, the Defense Department SBIR...
 




0 Comments


Be the first to comment!


Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>