PPRuNe Forums

PPRuNe Forums (https://www.pprune.org/)
-   Australia, New Zealand & the Pacific (https://www.pprune.org/australia-new-zealand-pacific-90/)
-   -   AirAsia issue SYD today? (https://www.pprune.org/australia-new-zealand-pacific/557869-airasia-issue-syd-today.html)

tail wheel 8th Sep 2016 01:54

An interesting article?

https://www.theguardian.com/australi...vigation-error

And ATSB Report:

http://www.atsb.gov.au/media/5771318...-029_final.pdf

That perhaps sounds similar to the occurrence which is the topic of this thread???

Oh, well, I guess everyone can have a bad day, not just LCC's?? :E :E

Biggles_in_Oz 8th Sep 2016 02:06

"In summary, it is likely that the disparity between the standby compass and the primary heading indications was not identified due to a combination of the:
• method of crosschecking the heading indications by use of the word ‘Check’ instead of verbalising the actual indication
• reduced prominence of the standby compass compared to the primary heading indications
• instrument panel check not being fully carried out during pre-flight in accordance with the FCOM, as the incorrect mode was selected on the NDs."


After lining-up they also didn't notice the >30 degree discrepancy between the indicated heading of 193'M and that they were on runway 16.

CurtainTwitcher 8th Sep 2016 02:13


After lining-up they also didn't notice the >30 degree discrepancy between the indicated heading of 193'M and that they were on runway 16.
From the report page 24

Recorded data indicated the captain had PLAN mode selected on his ND until after pushback and just prior to engine start. This precluded the ADIRS IRS align check being carried out in accordance with the FCOM. The FO had NAV or ARC mode selected on his ND for most of the pre-flight and then PLAN mode prior to pushback until engine start.

Based on the selected ND modes it is likely that the data integrity checks detailed in the pre-flight and taxi procedures were either omitted or conducted with the ND selected to an inappropriate mode and/or range that concealed the aircraft’s positional error.

The recorded data also indicated that the FO selected plan mode and every available ND range during the line-up/take-off roll. This may indicate that the FO was attempting to interpret an unusual display on the ND associated with the positional error.
The FO probably realised something serious was wrong with this picture...

compressor stall 8th Sep 2016 03:13

Tailwheel - it's not so much the bad day they had. Bad days and mistakes can happen to anyone.

It's what these guys did airborne to make it worse ....

Willie Nelson 10th Sep 2016 12:13

It can be very difficult to read through the politically correct unemotional language of the ATSB report and try to understand what indications the crew saw that may have led them to be suspicious prior to departure that all was not as it should be.

What is telling though on page 23


"It is likely that a message associated with failure of the GPS integrity check did appear on the engine warning display but the crew did not recall seeing one."
(They're talking about an ECAM caution here prior to takeoff, possibly more than one.)

Then the FO went trundling down the runway scrolling though the range selector on the ND while taking off.

A critical mind can infer the level of non normal awareness that the crew might have had.

The ATSB report, to my knowledge, does not go in to any detail about the relationship between the crew and and the associated command gradient that may have contributed to the incident. That seems like a wasted opportunity not only for them but for the rest of us too.

C441 11th Sep 2016 02:37

What I find alarming is that after take-off, flying a SID with a reasonably significant right turn away from a parallel runway, the crew didn't question the fact that they were turning left. :eek:
Didn't something as fundamental as that at least encourage them to at worst, not turn left or was their situational awareness that corrupted?

snoop doggy dog 11th Sep 2016 02:42

Not good... :(
 
Unknowingly put themselves into 'alternate law' and once gear was down (gravity extension due turning ADIRS 1 + 3 off), into 'direct law' by intentionally turning off the ADR part!

IMHO, the FO was clueless in what he had done/ was doing and the Captain of similar ilk. What was wrong with a radar vectored, raw data approach back into Sydney after reviewing the initial situation? That's right, they went into the wrong fault diagnosis and further compounded the situation! Airbus pilots I work with, understand what was initially done is wrong.

Great. Now 'Everyone can Fly!' The Air Asia accident in Indonesia wasn't that long ago and due to unknowingly putting themselves into a diabolical situation. The travelling public doesn't understand the gravity of what second rate Airlines can potentially do.

Why are pilot's paid better at some Airlines and not others? Answer is, that better paying Airlines expect their safety and training standards' to be upheld by their pilot's, thus maintaining their better reputations.

Anyone can have a bad day out? Even more so, if they do not understand the aircraft they are flying!

Willie Nelson 11th Sep 2016 13:12

Snoop,

I'm not sure there is a strong link between pay and skills. I think it is clear that these pilots had no place in their respective seats but the question that is significant to me is how did they get to this position if that was the case.

I believe the check and training department has a lot to answer here as well as these poor souls.

As for the FO inexplicably switching off the ADIRU rotary selectors, it would be interesting to find out what the captain was thinking when he asked him to 'reset nav'


All times are GMT. The time now is 11:51.


Copyright © 2024 MH Sub I, LLC dba Internet Brands. All rights reserved. Use of this site indicates your consent to the Terms of Use.