PDA

View Full Version : SQ Incident?


nick charles
20th Feb 2008, 03:46
Anyone hear the strong rumour about an EGPWS incident at Lahore involving an SQ aircraft recently? The rumour mentions 300' AGL!

tomrosie
20th Feb 2008, 09:45
yep. Got a false glide path signal which automatics didn't capture so appartently he went down on v/s. Was 500' agl with 5 miles to run!

OzExpat
20th Feb 2008, 10:39
Hmmm... so much for ignoring a GP check eh? :eek:

Capn Bloggs
20th Feb 2008, 12:11
Hmmm... so much for ignoring a GP check eh?
That happens at the OM, still .9nm away...:E

The KIWIs did a similar thing at an island with a dodgy GP.

That's why ALL ILS's should have a DME - take note, Airservices Australia.:=

Dream Land
20th Feb 2008, 12:44
That happens at the OM, still .9nm away...Right, so the aircraft should have been no lower than platform altitude for one more mile, right? Please explain. :confused:

TotalBeginner
20th Feb 2008, 13:38
If you're cleared for an ILS approach and discover that the G/S is inop, can you just revert to a LLZ/DME without clearance?

uncle dickie
20th Feb 2008, 15:37
TB

The answer is yes, you can; you will set a new higher DA/DH and use the advisory check distances against altitude/ height.

Notify ATC of the lack of glidepath. If the fault is on the ground, the Tower will have received a warning of the failure.

Pugilistic Animus
20th Feb 2008, 17:38
My SQ 777 that I personally own:p, has never had any problems with the gs receiver---but then again it's only 15" long and with an AUW of about 0.3 Kg:}

Raredata
20th Feb 2008, 18:58
Not a bad idea to always brief GS out minimum I always thought

Casper
20th Feb 2008, 19:56
The rumour that I heard made no mention of a false G/S signal. It just said that the crew descended too early because they weren't aware of the G/S intercept being closer to the field due the airport elevation. Also heard that they ignored the EGPWS warnings for a considerable time.

safetypee
20th Feb 2008, 20:29
Capn Bloggs Re GS check – “That happens at the OM …”
The primary purpose of markers / fix (or distance) checks during an approach is to determine the ‘acceptability’ of the vertical approach path / confirm your location with respect to that path. For safety, where a check involves altitude and distance, the altitude must take priority – it’s the early contact with ground that you wish to avoid, not the determination of distance to the airfield.

Dream Land states the required safety defence, check the altitude first and do not descend below it until the appropriate ‘fix’. In the specific case of an ILS I would suggest a climb, then determine the cause of the discrepancy – don’t trouble shoot at minimum altitudes, and don’t continue with an alternative procedure by assuming that the LOC (and your position relative to the airport) is correct – climb, check, rebrief, and recommence the approach. Beware the unexpected / unexplained; if the EGPWS alerts / warns - climb.

uncle dickie, you probably meant the above, but stating the check correctly (altitude vs distance tables) might aid correct use as well as recalling the check from memory, thus avoiding any complacency / omission of routine actions and checks.

Safety examples ‘EPGWS events and analysis’. ( www.icao.int/fsix/_Library%5CTAWS%20Saves%20plus%20add.pdf)
Also see ‘Thai Air B777 Melbourne NDB approach’. (www.pprune.org/forums/showthread.php?t=312341&page=5)

ACMS
20th Feb 2008, 23:33
I don't think the Air New Zealand crew got anywhere near 500' AGL. They realised quite early on that the GS was wrong.

Capn Bloggs
21st Feb 2008, 01:20
I don't think the Air New Zealand crew got anywhere near 500' AGL. They realised quite early on that the GS was wrong.

"Approximately 6 miles from the runway threshold a missed approach was carried out from an altitude of about 400 feet."

from here:

http://www.icao.int/icao/en/ro/apac/cnsmet_sg6/wp39.pdf

To all, out of interest, does your company have a SOP glideslope check that uses the DME at say 10DME (or the distance when the ILS starts) as opposed to the Outer Marker?

Brian Abraham
21st Feb 2008, 03:03
I don't think the Air New Zealand crew got anywhere near 500' AGL. They realised quite early on that the GS was wrong.

From the official report

Minimum height during the go-around was 340 ft PA (384 ft RA). This was at approximately 5½ miles from the threshold of the runway

CDRW
21st Feb 2008, 03:33
I think the rumour has a alot of foundation and has given the chaps on the 4th floor quite a shock, not only in how it happened but what happened after the event!!

hetfield
21st Feb 2008, 06:59
To all, out of interest, does your company have a SOP glideslope check that uses the DME at say 10DME (or the distance when the ILS starts) as opposed to the Outer Marker?

Yes, that's SOP in our cmpny.

Q: Aren't SQ Aeroplanes equipped with Enhanced GPWS, showing contour layers?

422
23rd Feb 2008, 11:12
Heard about SQ declaring emergency landing into DME.

Anyone has info on that?

Ular
23rd Feb 2008, 14:40
I was on the plane
9V-SYI
http://aviaforum.ru/attachment.php?attachmentid=41702&d=1203758692

After landing captain told by announcement about engine malfunction. He shut both engines after landing. Taxi to gate by tow car.

The 777 is still in DME. Another plane from SIN to take passengers expected to be arrived at DME about 8 p.m. local.

maxho
23rd Feb 2008, 15:39
Crew reported problems with #2 engine on initial descent through FL260, no emergency declared, landed at UUDD without incident.

Merlinrabbi
24th Feb 2008, 11:28
Anyone knows what happened to this 777 ?

It was a schedule flight from SIN - PER, but according to www.singaporeair.com it made a un-schedule stop in CGK for an hour.

Comoman
24th Feb 2008, 11:59
My mother was on the flight and I've just picked her up from Perth airport.

She said one hour out of Sin cabin crew service was stopped. The captain said something along the lines of the electronics are over heating and they're going to dump fuel and go to Jakarta. The mother commented upon landing no reverse thrust or spoilers (she travels quite often and was on the wing) and seemed to float upon landing.

Approx four hours later left Jakarta for Perth.

It was a Boeing 777-200

PK-KAR
24th Feb 2008, 16:14
I missed seeing the aircraft, it wasn't there when I went to the airport... I didn't know anything about it until I came back... but the info I got on it was that someone mentioned an LCD problem on the flight displays... :hmm:

Propellor
26th Feb 2008, 07:36
To revert to the original posting - what happened in Lahore that made a SQ B-777 descent to less than 500 feet more than 5 miles out?
Someone mentioned that it a miscalculation with the airfield elevation - that should account for about 700 feet (712 to be precise) of the 2800 that is the 'Platform Altitude'. I do not understand where the airfield elevation would come into the picture, but for some folks in SQ, it seems it did.
I wish the Safety boards there could let the rest of the world know the whats and the whys, so that the errors are not repeated by them as well as others.
But then, they would need to the find time for this, away from shielding SQ's ETOPS after 3 IFSDs in 2 weeks.

CDRW
26th Feb 2008, 11:36
Prop - heard that he ADDED the 700 feet to his calculation instead of taking it off!! That's now 1400 feet in error. I know it seems hard to believe. How the co-pilot didn't pick it up is also a mystery. It's also the 19+ seconds of GPWS that has their (managements) attention.

Propellor
26th Feb 2008, 14:48
19+ secs of the GPWS!!!!
I cannot believe that they considered the elevation for the maintenence of the intermediate altitude!
Sacking the pilots would be the simplest and stupidest thing that the management could do (akin to shooting the messenger): what they should be doing is holding a thorough inquiry of the ills in the training, checking and line audits that would let such incidents pass.
It is better to have a realistic and true measure of the the ills than the sugar coating that covers all what is bitter.

twitchy
26th Feb 2008, 20:20
Hey guys do you all still remember in good old days it was insisted that, In the tewrminal area descend to MSA and then to IAF altitude and always try and capture the G/S from below. This was one way to avoid the capture of false G/S. If the G/S is showing fly up, never descend below one's Initial app. altitude. Integrity of the G/S signal could be verified in time. Otherwise, by following the track dist. on finals versus height check and changing to G/S out minma, one could complete the approach.

Lahore elevation app. 750' was hazy as usual but what these guy in the SQ
B777 were doing with 3 radio altimeters indicating RA, 2 FMC telling them the dist. to go(this is subject to if no ILS/VOR DME present at OPLA on that day) before the EGPWS warning came. Its very difficult for any one to figure out why they kept descending below the G/S intercept alt. when tower seems to have conirmed to them that G/S was operating normal as per remot indications in TWR. I believe these guys ignored the "Pull Up" warning also for a considerable amout of time on so called final approach with no visual clues........... God bless another CFIT averted in time:(:(:(. Just a sheer good luck for these guys and every one else on board.

Molokai
26th Feb 2008, 20:46
There are a lot of pilots flying shiny new jets who have simply forgotten basic GP/DTG cross checks, awareness of false glide slopes etc. That's the problem with multi crew licencees progressing to wide bodies with very little handling experience. Give a few years of daily multi sector flights on a trusty classic B737 classic taking off and landing in various marginal airfields and all the basics will be deeply ingrained in one's hard drive...this all become very useful later when one gets command of a jet.

alf5071h
27th Feb 2008, 00:36
IIRC one of the incidents in ‘EPGWS events and analysis’ (www.icao.int/fsix/_Library%5CTAWS%20Saves%20plus%20add.pdf) occurred in India; does anyone have a link to the Lahore approach chart that can be used to see if there are any similarities?

Propeller, I have posted comments on the use of ‘an intermediate altitude’ in http://www.pprune.org/forums/showthread.php?t=312341&page=3. I agree with your implication that an immediate climb is required without thought of why the warning has occurred, why an error has occurred, or where the aircraft might be; these can be considered later at a safe altitude or on the ground after flight.

I also agree that an in-depth investigation is required, preferably by the national authority so that we might all learn from the event. However, I wonder if the national culture, or indeed the operator’s culture will permit identification of the ‘interesting’ contributions to the crew’s error.

A training / operational issue is that many pilots do not appreciate the amount by which EGPWS has been improved over GPWS. I am mildly irritated in this respect by the continuing use of GPWS as a generic term for the Enhanced system - no blame ascribed. The use of incorrect terminology can contribute to misunderstandings and incorrect use of systems. In this instance TAWS is the generic term, but “Enhanced GPWS” (EGPWS) means much more - that the aircraft is fitted with a highly reliable system which leaves no doubt at all about the validity of any warning.

Molokai, I agree with your points. One of the common sources of error in the use of modern technology for non-precision approaches is the use of pressure altitude. A simple mistake in altimeter pressure setting can affect both the instrument displays and VNAV path calculations, thus the crew have no immediate means of checking for an error. Similarly altitude miscalculation can induce errors, but if the pressure setting was correct, then someone should have detected the error with the basic crosschecks as you indicate. Thus the problem might be with the procedures / checking process, or even the altimeter setting procedure / crosschecking and subsequent monitoring of the critical parameters during the approach.

Dream Land
27th Feb 2008, 04:06
maxho, you appear to have the wrong link, the incident linked has nothing to do with GPWS. :confused:

London's Control
27th Feb 2008, 04:21
He was talking about the UUDD one :)

422
29th Feb 2008, 06:04
Another engine failure ex-BKK.

Not details yet, but looks like the trend of bad servicing is prompting CAAS to jump on SQ and SIAEC.

Casper
5th Mar 2008, 21:47
One of the 777's got to 300ft AGL about 10 nm from Lahore. Three GPWS warnings were received before the Capt. took any action and commenced a missed approach. Unfortunately the Glide Slope then came into view and the guy then tried to capture it off the missed approach leading to a further balls up.

SIA are worried because, throughout the whole proceedings (including 19 secs of EGPWS warnings), not one word of caution or help came from the F/O. Sound familiar ??
-----------------------------------------------------------------------
The above came from inside the SQ camp.

Dream Land
6th Mar 2008, 03:58
Yep, Stanstead airport, a smoking hole, KAL and don't forget the 74 in KUL from the ATC phraseology snafu. "Descend to/two four hundred" :ugh::ugh:

parabellum
6th Mar 2008, 10:39
Only just spotted this post:


Not details yet, but looks like the trend of bad servicing is prompting CAAS to jump on SQ and SIAEC.

422, please enlighten us about this 'trend of bad servicing'.