Earlier today an Etihad A330 performed a high speed RTO at YBBN....left some good sized skid marks on the runway....the cause? Invalid Airspeed Data on Captains side. Aircraft came back out, was checked and released around an hour later....

 

Back to the active, took off...and just passing 1000ft called "MAYDAY"....no airspeed indications.

 

Aircraft was vectored out over the bay and offered to dump fuel, and he advised he could not. The aircraft did not have the dump system option (it is an option not taken up by Etihad)

 

After 30 minutes of troubleshooting, aircraft was vectored back in, flying using ground speed readouts.

 

Landed with 6 hours worth of fuel still in the tanks, in the company of fire tenders and inspectors.

 

A few shaken passengers, but all in all, a good ending.

 

Crisis avoided.. thank god

http://flightaware.com/live/flight/ETD473/history/20131121/0155Z/YBBN/WSSS

Interesting, although I doubt the report will see the light of day due to the company involved.

 

I am curios as to how 'all' of the air data sources we're lost, must be more to it... Anyway, good job by the crew, landing near max take off weight in direct law would have been a challenge.

Ouch... Hopefully it gets resolved very soon. I believe that A330 (A6-EYJ) is still in Brisbane. I wonder what they're doing with the passengers though, since there's a full A330 load of them stranded in Brisbane. This service runs daily, but then there's another load of passengers for tomorrow's flight. 

They don't need to wait for Etihad, a lot of pax would have gone on other airlines and this who can wait would wait. Anybody in transit would have been a priority, originating pax have to wait. Here is the article, notice the aircraft type in the video? Love the media. http://www.news.com.au/national/queensland/plane-makes-mayday-call-at-brisbane-airport-sparking-emergency-situation/story-fnii5v6w-1226765362348

 

Sent from my Mobile thing