Aviation News, Headlines & Alerts
 
Category: <span>press release</span>

Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

Puma Gearbox Metal Shavings Conflict

The gearbox is a center of controversy in the investigation of the accident where the Bond Super Puma crashed off Peterhead, killing 16 men including two crew: Capt Paul Burnham, 31, of Methlick, Aberdeenshire, and co-pilot Richard Menzies, 24, of Droitwich Spa, who worked for Bond Offshore Helicopters, KCA Deutag employees Brian Barkley, 30, of Aberdeen; Vernon Elrick, 41, of Aberdeen; Leslie Taylor, 41, of Kintore, Aberdeenshire; Nairn Ferrier, 40, of Dundee; Gareth Hughes, 53, of Angus; David Rae, 63, of Dumfries; Raymond Doyle, 57, of Cumbernauld; James John Edwards, 33, of Liverpool; Nolan Goble, 34, of Norwich, and Mihails Zuravskis, 39, of Latvia; and non employees James Costello, 24, of Aberdeen, who was contracted to Production Services Network (PSN); Alex Dallas, 62, of Aberdeen, who worked for Sparrows Offshore Services; Warren Mitchell, 38, of Oldmeldrum, Aberdeenshire, who worked for Weatherford UK; and Stuart Wood, 27, of Aberdeen, who worked for Expro North Sea Ltd.

The inquiry blames the crash on gearbox failure, but for Bond and French company Eurocopter the question remains exactly where metal particles (evidence!) were found in the gearbox.


Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

Press Release: Airline Consumer Complaints Down From Previous Year


WASHINGTON – Airline consumer complaints filed with DOT’s Aviation Consumer Protection Division during the first nine months of this year were down 14.1 percent from the first nine months of 2012, according to the U.S. Department of Transportation’s Air Travel Consumer Report released today.
From January to September 2013, the Department received 10,439 consumer complaints, down from the total of 12,153 filed during the first nine months of 2012. In September, the Department received 1,008 complaints about airline service from consumers, down 6.8 percent from the 1,081 complaints filed in September 2012 and down 23.5 percent from the 1,318 received in August 2013.

The consumer report also includes data on tarmac delays, on-time performance, cancellations, chronically delayed flights, and the causes of flight delays filed with the Department’s Bureau of Transportation Statistics (BTS) by the reporting carriers. In addition, the consumer report contains information on airline bumping, mishandled baggage reports filed by consumers with the carriers, and disability and discrimination complaints received by DOT’s Aviation Consumer Protection Division. The consumer report also includes reports of incidents involving the loss, death, or injury of pets traveling by air, as required to be filed by U.S. carriers.

LAO Airlines Crash Update

At last the flight data recorder from the crash of a Lao Airlines turboprop ATR-72 has been recovered from the Mekong river. The cockpit voice recorder has been located also but has not yet been retrieved due to the strong currents and muddy water of the Mekong.

The flight data recorder tracks technical data: altitude, speed and route.

A cockpit voice recorder records cockpit conversation. The cockpit voice recorder has not been retrieved, though news releases to the contrary have been circulated.

Lao Airlines most recent press release:

Read more:

Lao Airlines Victims Recovered in Mekong River

LAO Airlines Crash Update: Victims Named

Painful Search Continues in Laos


Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

DOT Press Release: Code Share Disclosure


The U.S. Department of Transportation (DOT) today fined two ticket agents for violating the Department’s rules on disclosure of code-share flights. DOT issued a $125,000 fine against Carlson Wagonlit Travel and a $65,000 fine against Frosch International Travel, and both companies were ordered to cease and desist from further violations. The amount of the fines was based on the specific circumstances of the individual cases. Today’s consent orders are part of an ongoing effort by DOT to ensure that ticket agents comply with the code-share disclosure rules.

“No one wants to arrive to their gate and learn for the first time that the airline they thought was operating their flight actually sold them a ticket for another airline,” said U.S. Transportation Secretary Anthony Foxx. “We will continue to make sure that all companies selling air transportation are transparent with consumers and will take enforcement action when they fail to disclose code-sharing arrangements.”
Under code-sharing, an airline sells seats on flights using its designator code, but the flights are operated by a separate airline.

In this case, DOT’s Aviation Enforcement Office made telephone calls to a number of agents during January and February of 2013 and inquired about booking certain flights. During these calls, the reservations agents for both companies failed to disclose that the flights were being operated under code-share arrangements. The agents identified only the name of the airline marketing the flight and not the name of airline operating the flight. This violated DOT rules requiring airlines and ticket agents to inform consumers if a flight is operated under a code-share arrangement, as well as disclose the corporate name of the transporting airline and any other name under which the flight is offered to the public.

DOT takes enforcement action when necessary against companies that sell air transportation based on consumer complaints and the Department’s own internal investigations. DOT has now issued six fines for code-sharing violations this year, totaling $430,000.

The consent orders are available at www.regulations.gov, docket DOT-OST-2013-0004.


Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

Respond now to NTSB ISSUING FINAL RULE IN RESPONSE TO PILOT’S BILL OF RIGHTS

The National Transportation Safety Board announced today that it has issued a Final Rule to implement several changes to its Rules of Practice applicable to aviation certificate enforcement appeals. This final rule responds to public comments received by the NTSB as a result of an interim final rule (IFR) it issued last October. The NTSB issued the IFR after the enactment of the Pilot’s Bill of Rights legislation and it became effective upon its publication in the Federal Register on October 16, 2012.

Under the Pilot’s Bill of Rights: (1) the Federal Aviation Administration (FAA) must disclose its enforcement investigative report (EIR) to the FAA certificate holder in an aviation certificate enforcement case; (2) NTSB administrative law judges must apply the Federal Rules of Civil Procedure and Federal Rules of Evidence in enforcement cases; and (3) litigants now have the option of appealing the NTSB’s final orders to either a Federal district court or a Federal court of appeals. The IFR implemented these Pilot’s Bill of Rights requirements. Under the IFR, an FAA certificate holder is permitted to submit a motion to dismiss an FAA complaint if the FAA fails to disclose releasable portions of its EIR. The NTSB received 10 comments in response to the IFR. The Final Rule describes these comments in detail, as most of the comments provided substantive feedback and suggestions.

In considering the IFR comments, the NTSB determined it should include a proposal to extend the EIR availability requirement in the Pilot’s Bill of Rights to emergency enforcement cases. As a result, the NTSB is also publishing a new Notice of Proposed Rulemaking (NPRM) in conjunction with publication of the Final Rule in the Federal Register.


Both the Final Rule and NPRM are available at http://www.gpo.gov/fdsys/pkg/FR-2013-09-19/pdf/2013-22634.pdf (Final Rule) and http://www.gpo.gov/fdsys/pkg/FR-2013-09-19/pdf/2013-22633.pdf (NPRM). The public may submit comments to the NPRM, concerning the proposal to require the FAA to make available the EIR in emergency enforcement cases, via www.regulations.gov, Docket No. NTSB-GC-2011-0001, or via postal mail or facsimile, addressed to the NTSB Office of General Counsel. Comments should be submitted no later than October 21, 2013. The Final Rule is immediately effective.

See the bill below

In George’s Point of View

Time to take note of the final rule. The public can submit their opinion at http://www.regulations.gov, Docket No. NTSB-GC-2011-0001, or via postal mail or facsimile, addressed to the NTSB Office of General Counsel.


Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

IATA Press Release Talks about African Safety


The International Air Transport Association (IATA) called on public and private stakeholders to work together to address critical priorities to enable aviation to do more to drive economic growth in Africa.

“Aviation supports 6.7 million jobs and some $68 billion of economic activity in Africa. Those numbers are impressive but I am convinced aviation has an even bigger role to play in providing the connectivity that drives economic growth and development,” said Tony Tyler, IATA’s Director General and CEO.

Speaking at Aviation Day Africa, Tyler said that, “Africa is poised for rapid development and great changes. Half of the top 20 fastest growing economies over the next five years are expected to be on this continent. Aviation’s part in driving growth and development will become even more prominent.”

In order for this to occur, however, Africa must address major challenges in safety, infrastructure, and liberalization.

Safety:
“Safety is our top priority. And Africa’s performance is well below what we are achieving globally,” said Tyler. In 2012 African airlines had one accident (with a Western-built jet aircraft) for every 270,000 flights. Globally, the industry average was 1 accident for every 5 million flights. However, no IATA member experienced a Western-built jet hull loss accident last year and that includes the 25 member airlines based in Africa. Likewise, none of the 384 airlines on the IATA Operational Safety Audit (IOSA) registry had a hull loss with a Western-built jet—also including those carriers based in Africa. “It is clear that IOSA is making a difference—not just in Africa, but in safety globally,” said Tyler.

The Abuja Declaration, which was endorsed by the African Union Summit this year, sets out a comprehensive approach to reaching world-class safety levels by 2015. Completion of IOSA by all African carriers is a condition of the Declaration and Tyler urged African governments to make IOSA mandatory for airlines. IATA is sponsoring 10 airlines with in-house training to achieve IOSA registration.

In addition to IOSA participation, the Abuja Declaration calls for:

  • The establishment of independent and sufficiently funded civil aviation authorities
  • Implementation of effective and transparent safety oversight systems by all African states
  • Implementation of accident prevention measures focused on runway safety and loss of control
  • Implementation of flight data analysis
  • And implementation of safety management systems by all service providers

“Meeting the Abuja Declaration’s commitments will require a major effort across the continent. We have a lot of ground to cover and we cannot lose momentum. IATA is a committed partner and we must work together as a team of stakeholders to deliver world class safety to Africa,” said Tyler.

Infrastructure

“Infrastructure is also a major challenge. Some of the challenges are physical—infrastructure in many parts of Africa needs to improve,” said Tyler. Several infrastructure projects are ongoing in the region—upgrades at Lagos Airport, Performance-Based Navigation investments for Nigerian air traffic management and ambitious airport infrastructure re-development in Ghana.

Nonetheless, there are some infrastructure challenges including the reliability of fuel supply in Lagos. “We must find a sustainable long-term solution. The vandalized pipeline is no longer in use. And trucking fuel from Apapa terminal through dense traffic is inefficient and costly. The same can be said of building extra capacity to store fuel on site. Without minimizing the challenges involved, providing security on a few kilometers of pipeline is not an impossible task. We are working with the oil industry to find a solution. And we will be seeking the government’s political will to help us make it happen. Ensuring fuel reliability is critical to Lagos’s future as a hub for connectivity across South-West Africa.,” said Tyler.

Infrastructure costs and charging policy are also hindering African connectivity. “Just as with safety, global standards exist to provide guidance on charges, as developed and recommended by the International Civil Aviation Organization. These include cost-relatedness, non-discrimination and transparency. It is also recommended that charges be developed in consultation with users. And there should be no pre-financing,“ said Tyler.

“Governments must also recognize that every dollar counts. If we average the entire industry’s profits for 2012, airlines retained about $2.50 for every passenger. And African airlines have been basically hovering around break-even for a decade or more. Without sustainable income, airlines cannot expand to meet rising demand and in fact, they may have to reduce services,” said Tyler.

Liberalization
“Africa’s economic development needs aviation connectivity. And for that to further develop, airlines need to be able to access markets. Ironically, connectivity from Africa to other continents is more developed than connectivity within the continent. From Lagos there are daily flights to Atlanta but not to Dakar or Abidjan—and Lagos is one of the better connected cities in Africa. Africa has a visionary framework for growing connectivity across the continent in the now epic story of the Yamoussoukro Declaration which started in 1988. There has been some progress. But it is far from being transformational. It is interesting to see that African governments find it somehow easier to expand bilateral arrangements with long-haul trading partners than within the region,” said Tyler.


Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

NTSB ISSUES SECOND INVESTIGATIVE UPDATE ON SOUTHWEST AIRLINES ACCIDENT IN NEW YORK

August 6, 2013
WASHINGTON – In its continuing investigation of the July 22 accident in which Southwest Airlines flight 345, a B-737-700, landed hard at New York’s LaGuardia Airport (LGA), the National Transportation Safety Board has developed the following factual information:

• The captain has been with Southwest for almost 13 years and has been a captain for six of those years. The captain has over 12,000 total flight hours, over 7,000 of which are as pilot-in-command. In 737s, the captain has over 7,900 hours, with more than 2,600 as the pilot-in-command.

• The first officer has been with Southwest for about 18 months. The pilot has about 5,200 total flight hours, with 4,000 of those as pilot-in-command. In 737s, the first officer has about 1,100 hours, none of which are as the pilot-in-command.

• This was the first trip the flight crew had flown together and it was the second leg of the trip. The first officer had previous operational experience at LGA, including six flights in 2013. The captain reported having flown into LGA twice, including the accident flight, serving as the pilot monitoring for both flights.

• The en route phase of the flight, which originated in Nashville, was characterized by the flight crew as routine. On approach into LGA, the first officer was the pilot flying and the captain was the pilot monitoring. SWA 345 was cleared for the ILS Runway 04 approach.

• The weather in the New York area caused the accident flight to enter a holding pattern for about 15 minutes. The crew reported that they saw the airport from about 5-10 miles out and that the airplane was on speed, course and glideslope down to about 200-400 feet.

• The crew reported that below 1,000 feet, the tailwind was about 11 knots. They also reported that the wind on the runway was a headwind of about 11 knots.

• SWA 345 proceeded on the approach when at a point below 400 feet, there was an exchange of control of the airplane and the captain became the flying pilot and made the landing.

• The jetliner touched down on the runway nose first followed by the collapse of the nose gear; the airplane was substantially damaged.

At this point in the investigation, no mechanical anomalies or malfunctions have been found. A preliminary examination of the nose gear indicated that it failed due to stress overload.

Investigators have collected five videos showing various aspects of the crash landing. The team will be analyzing these recordings in the coming months.

Parties to the investigation are the Federal Aviation Administration, Boeing Commercial Airplanes, Southwest Airlines, and the Southwest Airlines Pilots Association.


Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

Rx for Safe Flying


Smart general aviation pilots won’t fly if they are taking a prescription that says Do not drive or operate machinery while taking this medication. But sometimes it’s not that clear cut. Other prescription drugs and even some over-the-counter medicines can affect a pilot’s performance.

That’s why Administrator Huerta and the heads of 11 aviation associations today sent a letter to all U.S.-registered pilots urging them to be more aware of the effect both prescribed medicines and non-prescription drugs containing antihistamines can have on their skills and judgment.

The letter tells pilots to read prescription labels carefully, talk with their doctors, and then decide if the drugs they’re taking could impair their performance in the cockpit. It also advises pilots to use a personal “IM SAFE” checklist to ensure they are not impaired by Illness, Medication, Stress, Alcohol, Fatigue or Emotion – any of which could affect their flying abilities. The letter counsels pilots who have recovered from an illness and have taken a medication with impairing side effects not to fly until at least five maximum dosage intervals have passed.

While the FAA works closely with many aviation advocacy groups, the letter represents an unprecedented joint effort. “In all of my years of practicing aerospace medicine, I am not aware of any time in which so many aviation organizations have collaborated to get out the same message at the same time,” said Dr. James Fraser, the FAA’s Deputy Federal Air Surgeon. “We hope this collaborative educational effort will put a dent in pilots’ usage of impairing medications and help lower the general aviation fatal accident rate.

Besides Administrator Huerta, signatories to the letter include executives from the Aircraft Electronics Association, Aircraft Owners and Pilots Association, Experimental Aircraft Association, American Bonanza Association, General Aviation Manufacturers Association, Helicopter Association International, National Association of Flight Instructors, National Air Transport Association, National Business Aviation Association, Society of Aviation Flight Educators and the U.S. Parachute Association.


Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

NTSB STATEMENT ON ERRONEOUS CONFIRMATION OF CREW NAMES


NTSB STATEMENT ON ERRONEOUS CONFIRMATION OF CREW NAMES
July 12, 2013
WASHINGTON – The National Transportation Safety Board apologizes for inaccurate and offensive names that were mistakenly confirmed as those of the pilots of Asiana flight 214, which crashed at San Francisco International Airport on July 6.

Earlier today, in response to an inquiry from a media outlet, a summer intern acted outside the scope of his authority when he erroneously confirmed the names of the flight crew on the aircraft.

The NTSB does not release or confirm the names of crewmembers or people involved in transportation accidents to the media. We work hard to ensure that only appropriate factual information regarding an investigation is released and deeply regret today’s incident.


Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

Raw video

When you see this amateur video of the Asiana Airlines crash, you really wonder how there were any survivors at all. Of the 307 people—291 passengers and 16 crew—aboard Asiana Airlines Boeing 777-200ER Flight 214, two passengers were killed and 181 injured.
Click to open video page

Asiana Press Releases for Incident Involving Asiana Flight

OZ 214 – July 7, 2013 06:30 (Kor. Time) 2013-07-07 10:02
The following information has been confirmed.

Asiana Airlines flight OZ214 (Aircraft Registration HL7742) departed Incheon International Airport on July 6, 2013 at 16:35 (Korea time) bound for San Francisco. Only July 7, 2013 at 11:28 (Local time) an accident occurred as OZ214 was making a landing on San Francisco International Airport’s runway 28.

There were a total of 291 passengers (19 business class, 272 travel class) and 16 cabin crew aboard. The majority of the passengers were comprised of 77 Korean citizens, 141 Chinese citizens, 61 US citizens, 1 Japanese citizen, etc. for a total of 291 people.

Asiana Airlines is currently investigating the specific cause of the incident as well as any injuries that may have been sustained to passengers as a result. Asiana Airlines will continue to cooperate fully with the investigation of all associated government agencies and to facilitate this cooperation has established an emergency response center at its headquarters.

At this point no additional information has been confirmed. New developments will be announced as more information becomes available.

#2
Official Asiana Statement from OZ214 Incident Press Conference 2013-07-07 16:31
We at Asiana Airlines would like express our utmost sympathy and regret for the distress experienced by the passengers of OZ flight 214 and their families as a result of this accident. We apologize most deeply.

Asiana Airlines flight OZ214 departed Incheon International Airport on July 6, 2013 at 16:35 (Korea time) bound for San Francisco. On July 6, 2013 at 11:27 (Local time) an accident occurred as OZ214 landed on San Francisco International Airport’s runway 28.

A total of 291 passengers were aboard the aircraft. (77 Koreans, 141 Chinese, 64 Americans, 3 Indians, 3 Canadians, 1 French, 1 Japanese and 1 Vietnamese)

Asiana Airlines has established emergency response centers to ascertain the cause of this crash and to look after injured passengers and contact their families. Asiana continues to actively cooperate with all Korean and US governmental institutions in the ongoing investigation.

# 3
Statement from July 8th Press Conference on OZ214 Incident 2013-07-08 15:42
Asiana would like to provide a brief update regarding the status of OZ214.

The special charter flight dispatched by Asiana Airlines yesterday at 13:33 (Korea Time) carrying twelve support staff, eight government inspectors and members of the Korean media has arrived on location in San Francisco. Its passengers have begun supporting the victims and their familes and assisting in the investigation.

Asiana Airlines is providing airfare and lodging for families of the passengers. In the event that the number of family members seeking support increases, Asiana is also preparing to operate additional charter flights.

Two Korean family members departed for the United States yesterday. Another four are expected to depart today followed by an additional four on Wednesday. Asiana Airlines is also supporting twelve Chinese family members and six Chinese government officials, who will depart from Shanghai for the United States (via Incheon) today.

48 injured persons are being treated at local hospitals in the San Francisco area. Each hospital is staffed with dedicated personnel and transportation to provide the utmost support for the victims and their families.

Asiana Airlines deeply regrets this accident and is dedicating great efforts to support and ensure a swift and thorough investigation.

* A cautionary note: The official investigation of the cause of the crash will take a year or more. No matter what news releases or speculations come about before the official investigation is just speculation. We do not know, for example, if some part or software in the plane malfunctioned, leading the pilots to respond as they did.


Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

NTSB says FAA should modify air traffic control procedures

July 1, 2013
WASHINGTON – Following the investigation of five incidents in which commercial jetliners came within hazardous proximity of other aircraft while arriving or departing at major U.S. airports, the National Transportation Safety Board today has recommended that the Federal Aviation Administration modify the rules for air traffic controllers to ensure the safe separation of airplanes during go-around maneuvers.

A go-around – an aborted landing attempt by an airplane on final approach – can be initiated at the direction of ATC or by the flight crew upon a determination that circumstances are unfavorable for a safe landing.

The safety hazard identified in the five incidents all occurred when an airplane that was on approach to the airport aborted the landing attempt and initiated a go-around maneuver, which put the go-around airplane on a flightpath that intersected with that of another airplane that was either departing or arriving on another runway of the same airport.

Although current FAA procedures have specific requirements for ensuring the separation between two airplanes that are departing from different runways but that have intersecting flightpaths, they do not prohibit controllers from clearing an airplane to land at a time when it would create a potential collision hazard with another aircraft if the pilots of the landing airplane perform a go-around.

In such situations, a flight crew performing a go-around may be put into the position of having to execute evasive maneuvers at low altitude and high closing speeds with little time to avoid a mid-air collision. The NTSB has determined that existing FAA separation standards and operating procedures are inadequate and need to be revised to ensure the safe separation between aircraft near the airport environment.

The NTSB has recommended that the FAA modify air traffic control procedures so that an airplane that executes a go-around instead of landing as expected, will not be put on a potential collision course with another airplane either in the process of landing or departing.

The incidents upon which this safety recommendation is based are listed below.

• Las Vegas McCarran International Airport
On July 30, 2012, at 1:44 p.m., a Spirit Airlines A-319 was executing a go-around as a Dotcom Cessna Citation 510 was on short final for landing on another runway. The two planes came within about 1,300 feet laterally and 100 feet vertically of each other.

• New York John F. Kennedy International Airport
On July 30, 2012, at 4:04 p.m., an American Airlines B-737 was executing a go-around as a Pinnacle Airlines CRJ 200 regional jet was departing from another runway. The two planes came within about 1,800 feet laterally and 300 feet vertically of each other.

• Charlotte-Douglas International Airport
On July 14, 2012, at 11:44 a.m., an ExpressJet Embraer 145 regional jet was executing a go-around as an Air Wisconsin Canadair RJ was departing from another runway. The two planes came within about 1,000 feet laterally and 400 feet vertically of each other.

• Las Vegas McCarran International Airport
On April 26, 2012, at 11:25 a.m., a JetBlue Airways A-320 was executing a go-around as a Learjet 60 business jet was departing from another runway. The two planes came within about 1,800 feet laterally and 100 feet vertically of each other.

• Las Vegas McCarran International Airport
On January 27, 2006, at 5:44 p.m., a near mid-air collision occurred when a United Airlines A-320 was executing a go-around as an American Airlines B-757 jet was departing from another runway. The two planes came within about 1,400 feet laterally and 300 feet vertically of each other.

The complete safety recommendation letter to the FAA, which includes additional information about the incidents referenced above, is available at http://go.usa.gov/busC.
###


Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

International Progress on Environmental Standards


Earlier this year, the International Civil Aviation Organization (ICAO) Committee on Aviation Environmental Protection (CAEP) advanced two important goals to make air travel cleaner and quieter worldwide. As a member of CAEP, the Federal Aviation Administration (FAA) played a crucial role.

“Air transportation continues to grow within and amongst nations,” said FAA Administrator Michael Huerta. “These new environmental standards and procedures recognize that we can work together internationally to achieve positive advancements in making aviation as environmentally efficient as possible.”

Relating to aircraft noise, CAEP has recommended a new international standard for newly designed aircraft that would reduce noise by 7 decibels relative to the current noise standard. The new requirement would become effective in 2017 for large aircraft and in 2020 for smaller models.

To address global warming greenhouse gases produced in air travel, CAEP has agreed to new international certification procedures for aircraft relating to carbon dioxide (CO2) emissions. At previous CAEP meetings, the committee had agreed on how to measure CO2. These new certification procedures now open the door for CAEP discussions on how stringent the standard should be set and whether the standard should only be applied to newly designed aircraft or some application to in-production aircraft. These discussions are expected to be completed by 2015.


Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

NTSB Issues 9 New Safety Recommendations

NTSB Issues Nine New Safety Recommendations as a Result of Its Investigation of the 8/26/2011 Crash of a Eurocopter AS350 B2 Near Mosby, Missouri

May 6, 2013 The National Transportation Safety Board Issues the Following Recommendations to the Following Organizations:

  • Prohibit flight crewmembers in 14 Code of Federal Regulations Part 135 and 91 subpart K operations from using a portable electronic device for nonoperational use while at their duty station on the flight deck while the aircraft is being operated. (A-13-007)
  • Require all 14 Code of Federal Regulations Part 121, 135, and 91 subpart K operators to incorporate into their initial and recurrent pilot training programs information on the detrimental effects that distraction due to the nonoperational use of portable electronic devices can have on performance of safety-critical ground and flight operations. (A-13-008)
  • Require all 14 Code of Federal Regulations Part 121, 135, and 91 subpart K operators to review their respective general operations manuals to ensure that procedures are in place that prohibit the nonoperational use of portable electronic devices by operational personnel while in flight and during safety-critical preparatory and planning activities on the ground in advance of flight. (A-13-009)
  • Inform pilots of helicopters with low inertia rotor systems about the circumstances of this accident, particularly emphasizing the findings of the simulator flight evaluations, and advise them of the importance of simultaneously applying aft cyclic and down collective to achieve a successful autorotation entry at cruise airspeeds. (A-13-010)
  • Revise the Helicopter Flying Handbook to include a discussion of the entry phase of autorotations that explains the factors affecting rotor rpm decay and informs pilots that immediate and simultaneous control inputs may be required to enter an autorotation. (A-13-011)
  • Require the installation of a crash-resistant flight recorder system on all newly manufactured turbine-powered, nonexperimental, nonrestricted-category aircraft that are not equipped with a flight data recorder and a cockpit voice recorder and are operating under 14 Code of Federal Regulations Parts 91, 121, or 135. The crash-resistant flight recorder system should record cockpit audio and images with a view of the cockpit environment to include as much of the outside view as possible, and parametric data per aircraft and system installation, all as specified in Technical Standard Order C197, “Information Collection and Monitoring Systems.” (A-13-012)
  • Require all existing turbine-powered, nonexperimental, nonrestricted-category aircraft that are not equipped with a flight data recorder or cockpit voice recorder and are operating under 14 Code of Federal Regulations Parts 91, 121, or 135 to be retrofitted with a crash-resistant flight recorder system. The crash-resistant flight recorder system should record cockpit audio and images with a view of the cockpit environment to include as much of the outside view as possible, and parametric data per aircraft and system installation, all as specified in Technical Standard Order C197, “Information Collection and Monitoring Systems.” (A-13-013)

    To Air Methods Corporation:

  • Expand your policy on portable electronic devices to prohibit their nonoperational use during safety-critical ground activities, such as flight planning and preflight inspection, as well as in flight. (A-13-014)
  • Revise company procedures so that pilots are no longer solely responsible for nonroutine operational decisions but are required to consult with the Air Methods Operational Control Center for approval to accept or continue a mission when confronted with elevated risk situations, such as fuel-related issues and unplanned deviations. (A-13-015)

Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

NTSB TO ASSIST AFGHAN AUTHORITIES WITH INVESTIGATION INTO BAGRAM CARGO PLANE CRASH


The National Transportation Safety Board will lead a team to assist the Afghanistan Ministry of Transportation and Commercial Aviation in the investigation of a cargo plane crash at Bagram Air Base in Afghanistan.

NTSB Senior Air Safety Investigator Tim LeBaron will be the U.S. accredited representative. He will lead a team of three additional investigators from the NTSB as well as representatives from the Federal Aviation Administration and The Boeing Company.

The private cargo plane, a Boeing 747-400 operated by National Air Cargo, crashed just after takeoff from the U.S.-operated air base at 11:20 a.m. local time Monday. All seven crewmembers onboard were killed and the airplane destroyed. The seven crew members were all American citizens. The accident site is within the perimeter of Bagram Air Base.

The international cargo flight was destined for Dubai World Central – Al Maktoum International Airport, Dubai, United Arab Emirates.

The Afghanistan Ministry of Transportation and Commercial Aviation is leading the investigation and will be the sole source of information regarding the investigation. According to the International Civil Aviation Organization, they can be reached at (873) 68 2341450 / 49 or by fax at (873) 68 1280784.


Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

NTSB INVESTIGATIVE HEARING ON BOEING 787 BATTERY FIRE

April 23, 2013 Press Release
The National Transportation Safety Board today will begin the first of two days of investigative hearings into the Jan. 7 battery fire aboard a Boeing 787 in Boston.

The all-day hearings will end with a separate press availability by NTSB Chairman Deborah A.P. Hersman.

Event 1: Investigative Hearing

Date/Time: Tues., April 23, 9 a.m. – 5:30 p.m. ET.; Wed., April 24, 9 a.m. – 5 p.m. ET

Location: Board Room, NTSB Board Room and Conference Center
429 L’Enfant Plaza, SW
Washington, DC 20594

Participants: NTSB Board Members, witnesses, NTSB staff technical panel, party members

Media Logistics: http://www.ntsb.gov/news/2013/130419.html

Network pool coverage will be by NBC

Live Webcast: A link to the webcast will be available at: www.capitolconnection.net/capcon/ntsb/ntsb.htm

Event 2: Press Availability

Participant: NTSB Chairman Deborah A.P. Hersman

Date/Time: Tues., April 23, 5:45 p.m. ET.; Wed., April 24, 5:15 p.m. ET

Location: Room A/B, NTSB Board Room and Conference Center
429 L’Enfant Plaza, SW
Washington, DC 20594

Media-only phone teleconference: 800-776-0420 or international 913-312-0945
Participant passcode: XXXXXX
Call 5-10 minutes before start of press conference and give your media affiliation, name and email.

Meeting Agenda


Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

Anniversary of Bhoja Air Crash

The anniversary of a plane crash is always a sad day;

It is a day few people recall if they didn’t lose someone;

It is a day remembered by children as the moment they found themselves orphaned–and mothers and fathers who found themselves without a child; and husbands and wives who found themselves widowed.

It is a day with consequences that reverberate through the lives of those affected like ripples in a pond–except that ripples in a pond eventually come to rest, and the victims of a crash will be victims forever.

We remember the day Bhoja Air crashed. It was en route from Karachi to Islamabad, with 121 passengers and 6 crew.

The owner of Bhoja Air remembers too, and the FIA is not likely to let him forget:

FIA Sindh Director Muazzam Jah Ansari said Bhoja Air owner Farooq Bhoja was taken into custody for questioning during the Bhoja Air plane crash and was released on Sunday after initial investigation.

Farooq Bhoja was not arrested. His office was raided and the FIA seized official documents.

Press Release Below:


Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

FATAL MISSOURI HELICOPTER ACCIDENT WAS CAUSED BY FUEL EXHAUSTION,

In George’s Point of View


I usually say Maintenance, Maintenance Maintenance, but in this case, I think I’ll say Training, Training, Training. The pilots I meet who were trained in the military tell me they are drilled to the point that reactions are instinct. If only this pilot had chosen not to fly, fueled the helicopter ahead of time, done things a little differently.

April 9, 2013
WASHINGTON — A pilot’s decision to depart on a mission despite a critically low fuel level as well as his inability to perform a crucial flight maneuver following the engine flameout from fuel exhaustion was the probable cause of an emergency medical services helicopter accident that killed four in Missouri, the National Transportation Safety Board said today.

“This accident, like so many others we’ve investigated, comes down to one of the most crucial and time-honored aspects of safe flight: good decision making,” said NTSB Chairman Deborah A.P. Hersman.

On August 26, 2011, at about 6:41 pm CDT, a Eurocopter AS350 B2 helicopter operated by Air Methods on an EMS mission crashed following a loss of engine power as a result of fuel exhaustion a mile from an airport in Mosby, Missouri. The pilot, flight nurse, flight paramedic and patient were killed, and the helicopter was substantially damaged.

At about 5:20 pm, the EMS operator, located in St. Joseph, Mo., accepted a mission to transport a patient from a hospital in Bethany, Mo., to a hospital 62 miles away in Liberty, Mo. The helicopter departed its base less than 10 minutes later to pick up the patient at the first hospital. Shortly after departing, the pilot reported back to the company that he had two hours’ worth of fuel onboard.

After reaching the first hospital, the pilot called the company’s communication center and indicated that he actually had only about half the amount of fuel (Jet-A) that he had reported earlier, and that he would need to obtain fuel in order to complete the next flight leg to the destination hospital.

Even though the helicopter had only about 30 minutes of fuel remaining and the closest fueling station along the route of flight was at an airport about 30 minutes away, the pilot elected to continue the mission. He departed the first hospital with crew members and a patient in an attempt to reach the airport to refuel.

The helicopter ran out of fuel and the engine lost power within sight of the airport. The helicopter crashed after the pilot failed to make the flight control inputs necessary to enter an autorotation, an emergency flight maneuver that must be performed within about two seconds of the loss of engine power in order to execute a safe emergency landing. The investigation found that the autorotation training the pilot received was not representative of an actual engine failure at cruise speed, which likely contributed to his failure to successfully execute the maneuver.

Further, a review of helicopter training resources suggested that the accident pilot may not have been aware of the specific control inputs needed to successfully enter an autorotation at cruise speed. The NTSB concluded that because of a lack of specific guidance in Federal Aviation Administration training materials, many other helicopter pilots may also be unaware of the specific actions required within seconds of losing engine power and recommended that FAA revise its training materials to convey this information.

An examination of cell phone records showed that the pilot had made and received multiple personal calls and text messages throughout the afternoon while the helicopter was being inspected and prepared for flight, during the flight to the first hospital, while he was on the helipad at the hospital making mission-critical decisions about continuing or delaying the flight due to the fuel situation, and during the accident flight.

While there was no evidence that the pilot was using his cell phone when the flameout occurred, the NTSB said that the texting and calls, including those that occurred before and between flights, were a source of distraction that likely contributed to errors and poor decision-making.

“This investigation highlighted what is a growing concern across transportation – distraction and the myth of multi-tasking,” said Hersman. “When operating heavy machinery, whether it’s a personal vehicle or an emergency medical services helicopter, the focus must be on the task at hand: safe transportation.”

The NTSB cited four factors as contributing to the accident: distracted attention due to texting, fatigue, the operator’s lack of policy requiring that a flight operations specialist be notified of abnormal fuel situations, and the lack of realistic training for entering an autorotation at cruise airspeed.

The NTSB made a nine safety recommendations to the FAA and Air Methods Corporation and reiterated three previously issued recommendations to the FAA.


Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

FAA and Port Authority of New York and New Jersey Reach Agreement on Airport Safety Violations

WASHINGTON – The Federal Aviation Administration (FAA) and the Port Authority of New York and New Jersey (PANYNJ) have reached a settlement agreement about aircraft rescue and firefighting (ARFF) violations from December 2010 to June 2012 at four New York area airports owned and operated by the PANYNJ — John F. Kennedy, Teterboro, LaGuardia, and Newark Liberty International.

“We expect all airports to comply with our safety regulations and to correct any deficiencies immediately,” said U.S. Transportation Secretary Ray LaHood. “These violations were egregious, and they will not be tolerated.”

Under the agreement, the PANYNJ agrees to pay a $3.5 million fine within 30 days. If there is a violation of the settlement agreement, the FAA will impose an additional fine of $1.5 million and will assess an additional $27,500 daily for each violation. In addition to the fine, the PANYNJ has agreed to take the following actions, with FAA approval, to address the underlying problems that led to systemic noncompliance with ARFF requirements at the four airports:

  • The Port Authority will create a dedicated ARFF force to carry out airport-related ARFF functions with no collateral police officer duties.
  • The staff will report directly to the Department of Aviation and be operational no later than March 31, 2014.
  • The Port Authority will hire an ARFF fire chief and facility captains as soon as possible, but no later than March 31, 2014.
  • The Port Authority will submit a curriculum for training to the FAA on or before December 31, 2013, which includes at least 75 hours of initial ARFF training and 40 hours of annual recurrent firefighting training in addition to Part 139 training, pertaining to an airport’s operational and safety standards and providing for such things as firefighting and rescue.
  • The ARFF personnel will work a 12-hour shift.
  • The Port Authority will amend the airport certification manuals for the four airports to include: an organizational chart; a process to maintain ARFF training records; and a description of ARFF operations, including shift assignments, personnel training records management, and Department of Aviation oversight.
  • The Port Authority will conduct monthly internal audits of ARFF training and shift assignments and annual external audits to ensure that all ARFF personnel assigned to a shift are trained.

“We expect the Port Authority to have trained safety personnel to ensure the safety of the travelling public and airport personnel, just like we have at all airports in the United States,” said FAA Administrator Michael P. Huerta.

The FAA became aware of ARFF violations as a result of an annual airport certification safety inspection of JFK in December 2011. The FAA also discovered similar violations at Teterboro, which prompted a full review of training at LaGuardia, Newark Liberty International, and Stewart International Airports. The review of ARFF training revealed violations at LaGuardia and Newark, with no violations at Stewart.

The FAA believes the settlement agreement provides the best long-term solution to ensure ARFF compliance, given the systemic nature of the PANYNJ airport problems.


Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

FAA Delays Closure of 149 Air Traffic towers until June 15

WASHINGTON – The U.S. Department of Transportation’s Federal Aviation Administration (FAA) announced today that it will delay the closures of all 149 federal contract air traffic control towers until June 15. Last month, the FAA announced it would eliminate funding for these towers as part of the agency’s required $637 million budget cuts under sequestration.

This additional time will allow the agency to attempt to resolve multiple legal challenges to the closure decisions. As part of the tower closure implementation process, the agency continues to consult with airports and operators and review appropriate risk mitigations. Extending the transition deadline will give the FAA and airports more time to execute the changes to the National Airspace System.
“This has been a complex process and we need to get this right,” said U.S. Transportation Secretary Ray LaHood. “Safety is our top priority. We will use this additional time to make sure communities and pilots understand the changes at their local airports.”

As of today, approximately 50 airport authorities and other stakeholders have indicated they may join the FAA’s non-Federal Contract Tower program and fund the tower operations themselves. This additional time will allow the FAA to help facilitate that transition.

“We will continue our outreach to the user community to answer any questions and address their concerns about these tower closures,” said FAA Administrator Michael Huerta.

On March 22, the FAA announced that it would stop federal funding for 149 contract towers across the country. A phased, four-week closure process was scheduled to begin this Sunday, April 7. That phased closure process will no longer occur. Instead, the FAA will stop funding all 149 towers on June 15 and will close the facilities unless the airports decide to continue operations as a nonfederal contract tower.


Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

NTSB Sends Investigators to Paraguay

February 4, 2013
WASHINGTON – The National Transportation Safety Board is sending investigators to assist in the investigation of a Robinson R44 II helicopter that crashed about 80 miles north of Asuncion, Paraguay. Initial reports indicate that the pilot and two passengers were fatally injured.
The investigation is being led by the Paraguay Civil Aviation Authority (CIPAA). The NTSB has designated senior investigator Paul Cox as the U. S. accredited representative to the CIPAA’s investigation and he will be accompanied by representatives from NTSB, the FAA, Robinson Helicopters, and Lycoming Engines. The U.S. team is expected to arrive Wednesday morning. Further information regarding the investigation will be released by the CIPAA.


Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

Seventh update on JAL Boeing 787 battery fire investigation


WASHINGTON – The National Transportation Safety Board today released the seventh update on its investigation into the Jan. 7 fire aboard a Japan Airlines Boeing 787 at Logan International Airport in Boston.

The auxiliary power unit battery, manufactured by GS Yuasa, was the original battery delivered with the airplane on December 20, 2012. It is comprised of eight individual cells. All eight cells came from the same manufacturing lot in July 2012. The battery was assembled in September 2012 and installed on the aircraft on October 15, 2012. It was first charged on October 19, 2012.

Examination and testing of an exemplar battery got underway earlier this week at the Carderock Division of the Naval Surface Warfare Center laboratories in West Bethesda, MD. The tests consisted of electrical measurements, mass measurements, and infrared thermal imaging of each cell, with no anomalies noted. The cells are currently undergoing CT scanning to examine their internal condition. In addition, on Thursday, a battery expert from the Department of Energy joined the investigative team to lend his expertise to the ongoing testing and validation work.

In Seattle, NTSB investigators and Boeing engineers examine the type of lithium ion battery used on the Boeing 787 to start the auxillary power unit and to provide backup power for flight critical systems.
NTSB investigators were made aware of reports of prior battery replacements on aircraft in the 787 fleet, early in the investigation. As reported Tuesday, Boeing, a party to the investigation, is providing pertinent fleet information which investigators will review to determine if there is any relevance to the JAL investigation.
An investigative group continued to interpret data from the two digital flight data recorders on the aircraft, and is examining recorded signals to determine if they might yield additional information about the performance of the battery and the operation of the charging system.

Next week, the NTSB battery testing team will initiate a non-invasive “soft short“ test of all cells of the exemplar battery. This test will reveal the presence of any high resistance, small or “soft” shorts within a cell. Also, an NTSB investigator will travel to France with the battery contactor from the JAL event battery, for examination at the manufacturer. The battery contactor connects a wiring bundle from the airplane to the battery.

Investigators are continuing their work in Washington and Japan and the team in Seattle continues to observe the FAA-led review of the certification process for the 787 battery system. The flow of information from these observations helps to inform NTSB investigative activity in the US and around the world.


Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

Fourth Investigative Update on Boeing 787 Battery Fire


NTSB Provides Fourth Investigative Update on Boeing 787 Battery Fire in Boston

January 27, 2013
WASHINGTON – The National Transportation Safety Board today released a fourth update on its investigation into the Jan. 7 fire aboard a Japan Airlines Boeing 787 at Logan International Airport in Boston. The fire occurred after the airplane had landed and no passengers or crew were onboard.

The event airplane, JA829J was delivered to JAL on December 20, 2012. At the time of the battery fire, the aircraft had logged 169 flight hours with 22 cycles. The auxiliary power unit battery was manufactured by GS Yuasa in September 2012.

NTSB investigators have continued disassembling the internal components of the APU battery in its Materials Laboratory in Washington, and disassembly of the last of eight cells has begun. Examinations of the cell elements with a scanning-electron microscope and energy-dispersive spectroscopy are ongoing.

A cursory comparative exam has been conducted on the undamaged main battery. No obvious anomalies were found. More detailed examination will be conducted as the main battery undergoes a thorough tear down and test sequence series of non-destructive examinations.

In addition to the activities at the NTSB lab, members of the investigative team continue working in Seattle and Japan and have completed work in Arizona. Their activities are detailed below.

ARIZONA
The airworthiness group completed testing of the APU start power unit at Securaplane in Tucson and the APU controller at UTC Aerospace Systems in Phoenix. Both units operated normally with no significant findings.

SEATTLE
Two additional NTSB investigators were sent to Seattle to take part in FAA’s comprehensive review. One of the investigators will focus on testing efforts associated with Boeing’s root cause corrective action efforts, which FAA is helping to lead. The other will take part in the FAA’s ongoing review of the battery and battery system special conditions compliance documentation.

JAPAN
The NTSB-led team completed component examination of the JAL APU battery monitoring unit at Kanto Aircraft Instrument Company, Ltd., in Fujisawa, Kanagawa, Japan. The team cleaned and examined both battery monitoring unit circuit boards, which were housed in the APU battery case. The circuit boards were damaged, which limited the information that could be obtained from tests, however the team found no significant discoveries.


Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

NEVADA AIR TOUR HELICOPTER ACCIDENT

January 25, 2013
WASHINGTON – The National Transportation Safety Board will hold a Board meeting to determine the probable cause of the crash of an air tour helicopter near Las Vegas.

On December 7, 2011, at about 4:30 pm PST, a Eurocopter AS350-B2 helicopter, operated by Sundance Helicopters, Inc., on a sightseeing trip, crashed in mountainous terrain about 14 miles east of Las Vegas, Nevada. The pilot and four passengers were killed, and the helicopter was destroyed by impact forces and postimpact fire.
Event: Board Meeting
Date/Time: Tuesday, January 29, 2013, 9:30 am EST
Location: NTSB Board Room and Conference Center
429 L’Enfant Plaza, SW
Washington, DC 20594
Participants: NTSB Board Members
Live Webcast: A link to the webcast will be available on the following page shortly before the start of the meeting: http://www.capitolconnection.net/capcon/ntsb/ntsb.htm
###


Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

INVESTIGATION OF BOEING 787 BATTERY FIRE IN BOSTON

NTSB CHAIRMAN SAYS ‘WE HAVE NOT RULED ANYTHING OUT’ IN INVESTIGATION OF BOEING 787 BATTERY FIRE IN BOSTON
WASHINGTON – In a press conference today, National Transportation Safety Board Chairman Deborah A.P. Hersman released preliminary findings from the NTSB’s ongoing investigation into the Jan. 7, 2013, Boeing 787 battery fire in Boston. “We have not ruled anything out as a potential factor in the battery fire; there are still many questions to be answered,” Hersman said.

Noting that there was a B-787 battery incident in Japan on Jan. 16, 2013, which is being investigated by the Japan Transport Safety Board, Hersman said, “One of these events alone is serious; two of them in close proximity, especially in an airplane model with only about 100,000 flight hours, underscores the importance of getting to the root cause of these incidents.”

The investigation revealed that the battery in the B-787 fire in Boston showed signs of short circuiting, and had indications of thermal runaway, a situation in which a significant temperature increase can initiate a destructive chain reaction.

Chairman Hersman also expressed concerns about the adequacy of the systems to prevent such a fire from occurring. “The investigation will include an evaluation of how a fault that resulted in a battery fire could have defeated the safeguards in place to guard against that,” said Hersman. “As we learn more in this investigation, we will make recommendations for needed improvements to prevent a recurrence.”

Investigators developed the following timeline of the events on Jan. 7, which was released at today’s briefing:

10:06 am EST – Aircraft arrived at gate in Boston from Narita, Japan
10:32 am – Cleaning and maintenance crew noticed smoke in cabin
10:35 am – Mechanic noted flames coming from APU battery in aft electronics bay
10:37 am – Airport Rescue & Fire Fighting notified
10:40 am – Fire and rescue personnel arrive on scene
12:19 pm – Fire and rescue personnel report event was “controlled”

The batteries were manufactured by GS Yuasa for the Thales electrical installation and are unique to the Boeing 787. The same battery model is used for the main airplane battery and for the battery that is used to start the auxiliary power unit, which is the one that caught fire in Boston.

Radiographic examinations of the incident battery and an exemplar battery were conducted at an independent test facility. The digital radiographs, or computed tomography (CT) scans, generated from these examinations allowed NTSB investigators to document the internal condition of the battery prior to disassembling it.

Ongoing lab work includes an examination of the battery elements with a scanning-electron microscope and energy-dispersive spectroscopy to analyze the elemental constituents of the electrodes to identify contaminants or defects.
NTSB INVESTIGATIVE TEAMS

In addition to the activities at the NTSB lab in Washington, members of the investigative team have been conducting work in Arizona, Seattle and Japan. Their activities are detailed below.

ARIZONA
– The acceptance test procedure of the APU battery charging unit was conducted at Securaplane in Tucson, Ariz., on Jan. 21.
– The battery charging unit passed all significant tests and no anomalies were detected.
– Members of the airworthiness group examined the APU start power unit at Securaplane in Tucson. The same team traveled to Phoenix to conduct an examination of the APU controller at UTC Aerospace Systems.

SEATTLE
– NTSB investigators are working with Boeing teams as part of root cause analysis activities related to the design and manufacturing of the electrical battery system.
– The two JAL B-787 general purpose module units, which record airplane maintenance data are being downloaded at Boeing to obtain information that was recorded after the airplane’s electrical power was interrupted.

JAPAN
– The NTSB-led team conducted component examination of the JAL B-787 APU battery monitoring unit at Kanto Aircraft Instrument Company, Ltd., in Fujisawa, Kanagawa, Japan.
– The team cleaned and examined both battery monitoring unit circuit boards, which were housed in the APU battery case. The circuit boards were damaged, which limited the information that could be obtained from tests.


Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

NTSB PROVIDES INVESTIGATIVE UPDATE AND PHOTO OPPORTUNITY OF LAB WORK RELATED TO BOEING 787 BATTERY FIRE IN BOSTON


January 23, 2013
WASHINGTON – Tomorrow, National Transportation Safety Board Chairman Deborah A.P. Hersman will provide an update on the NTSB’s investigation of the Jan. 7 fire aboard a Japan Airlines (JAL) Boeing 787 at Logan International Airport in Boston.

Chairman Hersman will brief credentialed members of the news media on the progress of the investigation, after which she and senior staff will take questions. Those unable to attend in person can call in to a teleconference line.

Reporters will then be invited to view the materials laboratory where the battery is being examined. Photography will be allowed but no “stand-ups” or taped reporting from the lab will be permitted.

For planning purposes, RSVP is required for those planning to either attend in person or call in.

Location: NTSB Boardroom and Conference Center, 429 L’Enfant Plaza East, SW, Washington, DC

Date: Thursday, January 24, 2013

Time: 2:30 p.m.

Participants: Chairman Deborah A.P. Hersman; John DeLisi, Director of NTSB Office of Aviation Safety; and Dr.
Joseph Kolly, Director, NTSB Office of Research and Engineering.

The following factual information has been developed about the battery: It consists of eight cells of 3.7 volts each. All eight cells had varying degrees of thermal damage. Six of eight cells have been CT scanned and have been disassembled to expose their electrodes. All electrode windings in the battery are in the process of being photo-documented and are undergoing microscopic examination. In the coming days, the remaining two cells will undergo the same examination. Additional information will be provided tomorrow.

Content not attributed to or linked to original, is the property of AirFlightDisaster.com; all rights reserved.

Site Credits