France seeks help with Airbus A330 crash search

http://www.reuters.com/article/latestCrisis/idUSLV89335

NTSB calls for new air traffic rules over Hudson River

http://edition.cnn.com/2009/US/08/27/hudson.river.air.rules/index.html

Air France Crash Team Fails to Find AF447 Black Box

http://www.bloomberg.com/apps/news?pid=20601087&sid=aejQUbngJ2d0

Air France 'black box' hunt ends

http://news.bbc.co.uk/2/hi/europe/8212569.stm

2 Air Traffic Workers Suspended in Inquiry on Hudson River Crash

http://www.nytimes.com/2009/08/14/nyregion/14controller.html

Skies over Hudson have seen many close calls

http://www.philly.com/inquirer/world_us/20090814_Skies_over_Hudson_have_seen_many_close_calls.html

FAA pressed for immediate restrictions on NYC airspace

http://www.newsday.com/long-island/faa-pressed-for-immediate-restrictions-on-nyc-airspace-1.1365267

Flyers may have lost their bearings

http://www.theaustralian.news.com.au/story/0,25197,25922039-5013404,00.html

Pilots debate midair warning systems

http://www.usatoday.com/news/nation/2009-08-11-air-collision_N.htm

Officials Demand Tighter Control, or Even a Ban, of Hudson Air Traffic

http://www.nytimes.com/2009/08/11/nyregion/11collide.html?_r=1

Calls to restrict flight corridor over Hudson

http://www.metro.us/us/article/2009/08/10/04/5137-82/index.xml

Fatal midair crash over Hudson raises questions

http://www.usatoday.com/news/nation/2009-08-09-aircollision_N.htm

Nine believed dead in Hudson River crash

http://www.newsday.com/news/nine-believed-dead-in-hudson-river-crash-1.1357113

Plane Hits Control Tower on Thai Island, 1 Dead

http://www.foxnews.com/story/0,2933,536542,00.html?test=latestnews

Status: Preliminary

Date: 04 AUG 2009

Time: ca 14:30

Type: ATR-72

Operator: Bangkok Airways

Registration:

C/n / msn:

First flight:

Crew: Fatalities: 1 / Occupants: 4

Passengers: Fatalities: 0 / Occupants: 68

Total: Fatalities: 1 / Occupants: 72

Airplane damage: Substantial

Location: Koh Samui Airport (Thailand)

Phase: Landing (LDG)

Nature: Domestic Scheduled Passenger

Departure airport: Krabi Airport (KBV/VTSG), Thailand

Destination airport: Koh Samui Airport (USM/VTSM), Thailand

Flightnumber: 266

Narrative:

A Bangkok Airways ATR-72 passenger plane was substantially damaged when it skidded off the runway at Koh Samui.

METAR about the time of the accident (07:30 UTC):

VTSG 040700Z 32005KT 9000 SCT020 BKN300 30/23 Q1008/A2977 RWY 32 INFO I=

VTSG 040800Z 32004KT 9000 SCT020 BKN300 28/25 Q1007/A2975 RWY 32 INFO J=

Airbus Offers to Pay for Extended Crash Search

http://www.nytimes.com/2009/07/31/world/europe/31plane.html?_r=1

More Cockpit Conversation from Flight 3407 Released

http://www.publicbroadcasting.net/wbfo/news.newsmain/article/0/0/1535081/WBFO.News/More.Cockpit.Conversation.from.Flight.3407.Released

AF Flight 447: French Prosecutor Opens Judicial Investigation For Manslaughter

http://luckybogey.wordpress.com/2009/06/05/af-flight-447-french-prosecutor-opens-judicial-investigation-for-manslaughter/

Plane Crash Leaves 168 Dead in Iran

http://www.nytimes.com/2009/07/16/world/middleeast/16plane.html?hpw

Air France pilots blame safety agencies for crash of Flight 447

http://www.timesonline.co.uk/tol/news/world/europe/article6675343.ece

AF447: Loss of contact opens rift between Brazil and Senegal

Initial details of the handover of Air France flight AF447 from Brazil to Senegal have opened a rift between the two states, as investigators attempt to establish how long the Airbus A330 was out of contact before a formal emergency alert was declared. Preliminary findings into the loss of the AF447 indicate that, after the jet failed to respond to radio calls shortly before leaving Brazilian airspace, several hours elapsed while controllers in 10 different flight information regions tried to determine the aircraft's position.

Circumstances of the loss - close to the Brazil-Senegal oceanic airspace boundary, where responsibility for the flight is handed over - have made the transfer issue a sensitive matter. France's Bureau d'Enquetes et d'Analyses (BEA) states that the flight "was not transferred" between Brazil's Atlantico and Senegal's Dakar oceanic centres. This has been backed by West African air navigation service ASECNA.

But the Brazilian air force says it wants to "eliminate doubts" about the procedures followed. It has publicly issued an audio segment of the moment the Atlantico controller co-ordinated transfer of AF447 to Dakar, when the A330 was estimating reaching the Brazil-Senegal airspace boundary - the waypoint designated TASIL - at 02:20UTC. Only changes in excess of 3min to this estimated time would have required further co-ordination with Dakar. But the estimate was never revised because the Atlantico controller could not raise AF447 after the last radio contact at 01:35UTC.

As a result, argues the air force, Dakar "theoretically" assumed control of the aircraft at 02:20UTC. But in a statement ASECNA claims the "onus" was on the Atlantico controller to call his counterpart at Dakar centre to confirm the aircraft's arrival at the airspace boundary. "This formality was not performed," it says, and the aircraft did not contact Dakar to "signal its presence".

ASECNA rejects as "totally unfounded" the Brazilian suggestion that aircraft can be assumed to have entered Dakar airspace if the Dakar centre does not warn otherwise. But BEA's interim report into the crash highlights a September 2008 agreement between the Atlantico and Dakar centres which was in force at the time of the crash.

This states that air crews must contact the receiving sector controller 5min before the airspace boundary, but also that controllers in the receiving sector must inform the exiting sector if they cannot establish contact with an aircraft within 3min of the estimated time of arrival.

BEA warns against drawing early conclusions over the search and rescue situation, stating that its chronology of subsequent air traffic control communications is "still fragmentary".

But the interim report states that Dakar controllers worked with a 'virtual' track of AF447 in the absence of radio contact and a confirmed trajectory. There was no log-on to the Dakar automatic dependent surveillance tracking system. Some 28 minutes after the estimated entry of AF447 into Dakar oceanic airspace, the Dakar controller informed the adjacent centre, Cape Verde Sal, that the aircraft had not yet made contact. More than an hour later, at 03:54UTC, with AF447 running 9min behind the projected time to enter Sal airspace, Sal called Dakar for an update, and was told that AF447 had not contacted Dakar to revise its estimates.Sal informed Dakar at 04:07UTC that it was tracking a second Air France flight, AF459, which had been some 37min behind AF447. This second aircraft failed to raise AF447 on the radio. At 04:21UTC Dakar called Atlantico centre to confirm the whether AF447 had exited Brazilian airspace at TASIL in line with the original estimate.

BEA's partial chronology does not yet include full information from the Atlantico and Sal centres. But the Brazilian air force states that, after Dakar queried AF447's position with Atlantico, the Recife-based Salvaero search and rescue division "initiated necessary actions to start air operations to locate the missing aircraft" at 05:20UTC. By this time Air France was also trying to confirm the flight's position and, over a period of about three hours, the carrier and several other control centres - among them Canarias, Santa Maria, Casablanca, Lisboa, Madrid and Brest - exchanged information in a bid to establish the aircraft's whereabouts. At one stage, the BEA chronology shows, the flight was erroneously reported to have been in contact with Moroccan air traffic control.

Air France and Brest centre informed BEA of the situation shortly after 07:41UTC. Madrid centre issued an 'alert' emergency phase at 08:15UTC and Brest launched a 'distress' phase about 20min later.