PDA

View Full Version : Thai 777 EGPWS Event - Melbourne


AJ
01-22-2008, 09:24 AM
The ATSB has released a preliminary report into HS-TJW's EGPWS event whilst trying to conduct a non-precision approach to Runway 16.

Amazingly the approach was flown in FLCH (Flight Level Change) mode instead of one of two Boeing approved methods (VNAV or V/S).

2 factors saved the day. Breaking clear of cloud and the EGPWS!

http://www.atsb.gov.au/publications/investigation_reports/2007/AAIR/pdf/aair200706727_prelim.PDF

Chris Kilroy
01-22-2008, 02:01 PM
Amazingly the approach was flown in FLCH (Flight Level Change) mode ...

Oh my!

flyboy2548m
01-22-2008, 02:23 PM
Amazingly the approach was flown in FLCH (Flight Level Change) mode instead of one of two Boeing approved methods (VNAV or V/S).



On our airplane the FLCH mode is called speed mode and is also prohibited during approaches. That being said, had they been in V/S mode they would have had the same problem as V/S would have flown them right into the ground, if left unchecked, same as FLCH would have. VNAV would not have, but I don't know if either 777 FCOM or Thai FCOM permits the use of VNAV on approaches.

The main problem here is that the crew failed to monitor the altitude, not what mode they were in, although the mode didn't help.

MCM
01-22-2008, 03:26 PM
Pretty easy mistake to make AJ!



Intention I'm sure was to conduct a VNAV approach, but when they realised they were high they went FLCH to get back oin the profile, but when they hit the profile they for whatever reason forgot to select VNAV.



I guess thats a pretty good reason for a change in the ALT window selection procedure.... ;)

DeskFlyer
01-23-2008, 03:36 AM
Jeebus!

I flew MEL-BKK on 4th November but it was operated by TJV.

Never heard a thing about this.

DF

reubee
01-25-2008, 06:34 AM
<TABLE cellSpacing=1 cellPadding=7 width=415 border=1><TBODY><TR><TD vAlign=top width="50%" height=12>Aircraft model






</TD><TD vAlign=top width="50%" height=12>Boeing 777-2D7






</TD></TR><TR><TD vAlign=center width="50%" height=23>Serial number






</TD><TD vAlign=center width="50%" height=23>34591






</TD></TR><TR><TD vAlign=center width="50%" height=23>Date of manufacture






</TD><TD vAlign=center width="50%" height=23>11 October 2007






</TD></TR><TR><TD vAlign=center width="50%" height=23>Certificate of Registration






</TD><TD vAlign=center width="50%" height=23>Valid, issued 29 October 2007






</TD></TR><TR><TD vAlign=center width="50%" height=23>Certificate of Airworthiness






</TD><TD vAlign=center width="50%" height=23>Valid, issued 29 October 2007






</TD></TR><TR><TD vAlign=bottom width="50%" height=19>Total airframe hours and cycles






</TD><TD vAlign=bottom width="50%" height=19>51 hours, 5 cycles






</TD></TR></TBODY></TABLE>





Out of curiousity, given at least one of these cycles was the delivery flight, how many flights will an aircraft typically have before it enteres service