PDA

View Full Version : Asiana crash at SFO.


Montague S
7th July 2013, 05:42 AM
hopefully no fatalities...

http://www.usatoday.com/story/travel/news/2013/07/06/airline-crash-san-francisco/2495099/

https://path.com/p/1lwrZb

Jim M
7th July 2013, 05:51 AM
News still filtering through. I have read reports that the tail may have come off!

Reports of people with burns but please let there be no fatalities.

Aircraft was a Boeing 777 Asiana 214 from Seoul.

Jim

Jim M
7th July 2013, 06:04 AM
Reports now saying that all 303 onboard are accounted for. Thank God.

Jim

Sarah C
7th July 2013, 06:41 AM
Wow, just wow. Looks like everyone survived. The pictures are surreal

Craig Lindsay
7th July 2013, 07:27 AM
From the pictures on channel 9 it looks like its come in to low cause theres a debris field from the sea wall onwards.

David Ramsay
7th July 2013, 07:31 AM
Live video (http://statter911.com/2013/07/06/boeing-777-crash-landing-with-fire-at-san-francisco-airport-flight-from-seoul/)

Sarah C
7th July 2013, 07:56 AM
Now updated to 2 dead and about 60 injured

The pictures at the end if the runway seem to suggest they came in too low. Weather certainly not an issue - a nice clear day at SFO

Ian Garton
7th July 2013, 08:17 AM
HL7742 by the looks of it

Justin L
7th July 2013, 08:26 AM
1895

Wow. It's amazing so many survived.

Mick F
7th July 2013, 10:01 AM
Just throwing this out there, but has there been any reports on whether the aircraft lost power prior to landing? (thinking British Airways 777 crash a few years ago).

Mick

Grahame Hutchison
7th July 2013, 10:25 AM
This aircraft was a regular visitor (http://www.16right.com/ACARS.php?Regno=HL7742&Flightno=&ACARSdate=&submit=Search) to Sydney up until 10/06/2011.

Looks like it landed very short, clipping the rock wall, although some eye witnesses said the approcah looked abnormal also.

Montague S
7th July 2013, 11:42 AM
just heard a clip on Live ATC from the approach and you can clearly hear the captain call the tower telling them they have a problem, actually, he just calls out "we have a problem".

Mick F
7th July 2013, 12:42 PM
Cheers Monty.

Interesting. I'm not one for speculation normally, but this just smells of another 777 power loss after a long flight in cold temps.

Mick

Robert S
7th July 2013, 01:06 PM
Fair few eyewitness accounts floating around but many seem seriously questionable. There's one from someone who says he was seated in the middle of the plane, not at the back, but then he's giving a detailed account of what he "saw" happening at the back. You know, through all the toilets and galleys and while strapped to his forward-facing seat.

It does seem like the landing gear clipped the seawall and collapsed.

The photo of people walking away toting large carry-on luggage is bizarre but not exactly surprising.

Sarah C
7th July 2013, 01:38 PM
Every evacuation seems to have people with bags and now people taking photos on their phones

Thomas Collins
7th July 2013, 01:48 PM
Asiana use the PW engine. BA use the RR.

The decent profile for the approach seems steep, then flattened out.

I read that Asiana pilots are obsessed with smooth landings and typically flatten out the approach for a smoother flare/touchdown.

The ILS was also not operational I am told - PAPI being the only glide-slope reference.

Possibly undershot the threshold and in an attempt to arrest, over-rotated and hit the tail into the ground, causing it to detach.

Radi K
7th July 2013, 01:54 PM
Thomas, both GP & PAPI was NOTAM'd out I thought? Sadly looks like he landed short. Pilot error or technical problem - time will tell. The weather was perfect, clear skies and calm winds.

The UA B747 holding short would have ***** themselves I'd say.

Interesting graphic from the approach the day before and the day of the accident.

https://pbs.twimg.com/media/BOhIDCWCUAApHFV.jpg:large

Sarah C
7th July 2013, 02:18 PM
I can only imagine what the crew of that UA 747 were thinking.

SFO is one of the most popular spotting airports in the US. Given how nice the day was and being a weekend, it would have been interesting to see how many were out there and witnessed it. Any photos taken will be crucial in the investigation - this is another reason why spotters are actually good for airports, not a danger.

Robert S
7th July 2013, 04:13 PM
Every evacuation seems to have people with bags and now people taking photos on their phones

To be fair, the person who tweeted that was a fair distance from the aircraft and also notably refused media requests, later saying he only sent that out to let people know that he was OK (and to a lesser extent, that a large number of people seemed to be largely OK).

On the face of it, compared to the average person, I think he acted relatively thoughtfully and not unreasonably.

Sarah C
7th July 2013, 05:05 PM
It is not a criticism of them taking photos - it is just interesting that people think that as soon as they get out, that the danger is over.

Jason H
7th July 2013, 05:45 PM
I can only imagine what the crew of that UA 747 were thinking.

I heard the ATC recording and they reported "two or three people that are moving and apparently survived" on the ground near the threshold and they needed attention. That must have been quite a sight for them.

Montague S
7th July 2013, 06:44 PM
http://www.youtube.com/watch?v=8kBLM-6dUGs

here is the recording..

Jacob L
7th July 2013, 07:36 PM
The ILS may have something to do with it???

Wasn't Asiana rated up there with one of the safest airlines in the world.

My condolences to the families who lost loved ones.

Jacob

Radi K
7th July 2013, 07:54 PM
I heard the ATC recording and they reported "two or three people that are moving and apparently survived" on the ground near the threshold and they needed attention. That must have been quite a sight for them.

Do you think the people they saw were thrown from the aircraft during the "skid" or was this post evacuation?

As you can see the aicraft was quite a distance from the "numbers"

http://avherald.com/img/asiana_b772_hl7742_san_francisco_130706_6.jpg

This pic also shows the damage to the sea wall. Very obvious early touchdown! - don't send these guys to Saint Marteen! :eek:

http://avherald.com/img/asiana_b772_hl7742_san_francisco_130706_7.jpg

Radi K
8th July 2013, 06:50 AM
In the current live NTSB news conference they have advised the aircraft stalled on approach. No mechanical problems.

VREF was 137kts in Flap 30. Was cleared for visual approach RWY 28L.

7 seconds before touchdown a pilot called low speed and stick shaker activated, thrust was idle during late stages of descent. About 1.5 seconds before impact they called go-around and thrust increased but it was too late.

Sadly looks like pilot error.

All based on CVR and FDR. Basically it sounds like THY 737 in Amsterdam.

Rod Sloan
8th July 2013, 07:21 AM
Crash video (http://edition.cnn.com/video/data/2.0/video/us/2013/07/07/vo-plane-sf-plane-crash-on-cam.courtesy-fred-hayes.html)

Mick F
8th July 2013, 08:19 AM
Thanks for that update Radi. Puts to bed my thoughts then.

Mick

Philip Argy
8th July 2013, 08:27 AM
Apparently some NAV aids at SFO were inoperative, including glideslope. Sounds like that could be a key factor.

Grahame Hutchison
8th July 2013, 09:19 AM
I heard that the ILS was not operating on Runway 28L, however the PAPI was.

New video (http://video.news.com.au/2395960796/Amateur-footage-of-San-Francisco-plane-crash)of the actual impact has emerged and can be seen on news.com.au (the end of the skid on the dirt is dramatic).

Greg McDonald
8th July 2013, 12:02 PM
Reports that it's a possibility that one of the victims of this may have actually been killed by a rescue vehicle.

Mick F
8th July 2013, 12:05 PM
Phil,
Having an ILS out should not be a factor at all. If a pilot can't make a visual approach, then they've got some serious lack of flying ability issues.

Mick

Mike_S
8th July 2013, 01:58 PM
What Happened to Asiana Airlines Flight 214? (http://flyingprofessors.net/what-happened-to-asiana-airlines-flight-214-2/)

Only conjecture based upon fairly limited data available, but still an interesting analysis nonetheless

Deni G
8th July 2013, 06:08 PM
Asiana Airlines revealed the pilot in charge of landing the Boeing 777 that crash-landed at San Francisco's airport was training for the long-range plane and that it was his first flight to the airport with the jet
The pilot had 43 hours of experience of flying the 777, a spokesperson for the airline revealed. His co-pilot, Lee Jeong-Min had 3,200 hours of flying experience aboard a 777 and was in the cockpit with Kang-Kook when disaster struck.


The crew tried to increase its speed and abort its landing just seconds before it hit the seawall in front of the airport runway
Recordings show crew had no concerns before landing then tried to 'go around' 1.5 seconds before impact

The airport's Glide Path system, which is designed to avoid runway misses in a variety of weather, was switched off

Grahame Hutchison
9th July 2013, 09:21 AM
The give a little balance to the "43 hours at the controls of a B777" story.

From Air Transport World ...


According to information provided by Seoul-based Asiana (http://atwonline.com/safety/asiana-no-mechanical-problems-777-involved-fatal-sfo-crash) to media, the pilot at the controls was Gang-Guk Lee, a veteran Asiana flight deck crew member who was in the midst of making the transition to flying the 777. Lee had accumulated more than 9,700 hours of total flight time, including on the 747, but had just 43 hours on the 777 and was still going through a formal “familiarization” period in which he was required to be paired with more experienced 777 pilots.

Gang-Guk Lee had landed at SFO before in other aircraft, including the 747, and he had landed the 777 already at, among other airports, London Heathrow and Los Angeles International. Allowing an experienced pilot who has landed a 747 at SFO and a 777 at Heathrow and LAX to land a 777 at SFO does not sound out of line at all.

Trevor Sinclair
10th July 2013, 04:37 PM
Here's another interesting read from a First Officer' view: http://www.curacaochronicle.com/aviation/email-from-a-united-crew-holding-short-of-the-runway-as-the-asiana-b-777-approached/

Montague S
10th July 2013, 05:05 PM
http://www.ntsb.gov/investigations/2013/asiana214/asiana214.html

all the updated info from probably the most reliable source.

Cliff Cook
11th July 2013, 05:08 PM
Good evening,

Sorry to send my message very late, so look at a picture of stricken Asiana Ailines with other Asiana Airlines B777 landing behind it on page 13 in today's SMH newspaper.

Regards,

Cliff Cook.

Philip Argy
11th July 2013, 05:50 PM
With all of the caveats that have to go with sparse information, this extract from the commentary cited by Mike at http://www.yssyforum.net/board/showpost.php?p=83709&postcount=32 seems to me the most plausible primary cause of the crash:


However, when being vectored for an approach and the aircraft is too high, an easy way to recover is to set a lower altitude, select FLCH, speed brake etc. this give a high rate of descent, and as long as the pilot has the G/S armed the aircraft will capture it. The G/S acts as a safety net.

In this case, the aircraft did not level out, and we know the GS was not active


I understand that FLCH (level change) mode is the only one in which auto throttle doesn't 'wake up' to provide emergency thrust when the glideslope is off. That so-called 'FLCH trap' seems to have caught out an inexperienced 777 pilot and his instructor.

Chris B.
12th July 2013, 11:22 AM
Phil,

You're close regarding FLCH but more information is needed. Flight Level Change is a function of speed (really has nothing to do with the fact that the glideslope was inoperative). Which means that the pitch of the aircraft is changed to reach that targeted speed. Using FLCH on descent the autothrottle operates in THR (Thrust) to maintain the descent rate required by the pitch mode. Once the thrust setting is achieved the mode changes to HOLD (thrust lever autothrottle servos are inhibited and the pilot can set thrust levers manually) this is why in FLCH or TOGA (which I wont go into now) the autothrottles don't 'wake up' as you put it.

Now to use FLCH for a descent a lower altitude must be set. I'm not sure what the crew set as an altitude but once the selected altitude is reached the autothrottle mode will change from HOLD to SPD (Speed - the autothrottle system is now commanding thrust to achieve the required speed) and normal system protection is restored. If they set an altitude of 0' then HOLD would still have been the current mode as they hadn't reached the selected altitude yet. Unfortunately FLCH and TOGA below 100' RA (Radio Altitude) on approach the autothrottle will not automatically activate the stall protection. For this reason Boeing do not recommend the use of FLCH for approaches past the final approach fix.

Even if the glideslope is inoperative the aircraft is still capable of many of the other non precision approaches available at SFO, and with the appropriate pitch mode (V/S - vertical speed, FPA - Flight Path Angle, or VNAV - Vertical Navigation) the stall protection would have been activated.

So yes the 'FLCH trap' did catch them out but I believe it was more a case of misunderstanding the use of certain autopilot system controls as the aircraft performed exactly as it was meant to.

Of course we will wait for the official report on the accident on what modes the crew were operating in, but I hope I provided a more educated post on the use of FLCH rather than a simplified 'easy way to recover is to set a lower altitude, use speedbrake etc' answer as what was quoted in your post.

Philip Argy
12th July 2013, 12:22 PM
The NTSB will give us all the gory detail probably in about a year but I reckon with the talent on this board we have nailed it 99% well enough to be confident in expressing a view about WHAT most likely happened as distinct from WHY that happened or was allowed to happen.

Mick F
12th July 2013, 09:33 PM
I am a very big believer in automation. I love it. Use it to its full potential nearly every day at work.

However.... I also know when automation is simply not suitable. One of the very big keys to effective automation management, is to be 5 steps ahead of the computers at all times. The old saying, "What's it doing? What's it going to do? What have I told it to do?". If you're trying to play catchup and its all going pear shaped, then either one of two things have to happen. Either you put yourself in a position where you can slow it all down and catch up again, or you simply get rid of it all and go back to basics.

Looking at a few of the comments around the aviation world so far, it appears the crew forgot the simple and most basic of things - Fly the aircraft.

Mick

Greg M
13th July 2013, 09:00 AM
Poor fact checking by the media....

http://www.liveleak.com/view?i=563_1373664708

Someone Pranked San Francisco TV Station Into Reporting Fabricated Names Of Asiana Pilots

Grahame Hutchison
13th July 2013, 11:01 AM
"Don't ever let an airplane take you someplace where your brain hasn't arrived at, at least a couple of minutes earlier", may have some relevance here.

Sarah C
13th July 2013, 01:15 PM
A third passenger has passed away from her injuries.

Thomas Collins
13th July 2013, 03:00 PM
Poor fact checking by the media....

http://www.liveleak.com/view?i=563_1373664708

Well this is ridiculous. How that could have passed through to broadcasting is beyond embarrassing.

And the fact they quoted the NTSB verified the names...

I'm sure they did...

Mark B
13th July 2013, 04:28 PM
Well this is ridiculous. How that could have passed through to broadcasting is beyond embarrassing.

And the fact they quoted the NTSB verified the names...

I'm sure they did...

Well, this is what the NTSB had to say (see http://www.ntsb.gov/news/2013/130712.html)

NTSB statement on erroneous confirmation of crew names
July 12

The National Transportation Safety Board apologizes for inaccurate and offensive names that were mistakenly confirmed as those of the pilots of Asiana flight 214, which crashed at San Francisco International Airport on July 6.

Earlier today, in response to an inquiry from a media outlet, a summer intern acted outside the scope of his authority when he erroneously confirmed the names of the flight crew on the aircraft.

Thomas Collins
13th July 2013, 05:15 PM
Wow - that is amazing... I would not have thought...

A McLaughlin
15th July 2013, 12:20 PM
A comment from someone on LinkedIn today...

"The crew was so far behind that airplane that, nearly a week after the crash, they're not injured yet."

Geoff Br
17th July 2013, 01:38 PM
I love the quote above on Linkedin....
Saw this today in FlightGlobal...Brings up some interesting questions, especially about auto throttles...

http://www.flightglobal.com/news/articles/analysis-asiana-crash-to-reopen-sensitive-questions-on-etiquette-automation-388157/?cmpid=NLC|FGFG|FGFIN-2013-0716-GLOB

LES B
17th July 2013, 08:35 PM
Wonder what the results would have been if it had been a 787 in the same position?

Stephen Brown
29th July 2013, 09:18 AM
Poor fact checking by the media....

http://www.liveleak.com/view?i=563_1373664708

Someone Pranked San Francisco TV Station Into Reporting Fabricated Names Of Asiana Pilots

Looks like the South Koreans have played the card back they were dealt...

http://slothed.com/2013/07/23/korean-news-station-pokes-fun-at-ktvu-with-fake-american-pilot-names-after-southwest-airlines-landing-gear-failure/

Bradley Porter
29th July 2013, 04:56 PM
Difference being that at least the Southwest Pilots were a victim of mechanical failure and not of their own failings !

Fred C
29th July 2013, 06:53 PM
I think the Southwest pilots may have been victims of trying to land nose gear first. That tends to lead to mechanical failure though.

Geoff Br
7th August 2013, 11:06 AM
I think the Southwest pilots may have been victims of trying to land nose gear first. That tends to lead to mechanical failure though.
I see that the FAA have banned visual approaches to KSFO 28 left and right...
http://www.flightglobal.com/news/articles/faa-bans-visual-approaches-by-foreign-airlines-at-san-francisco-airport-388850/?cmpid=NLC|FGFG|FGFIN-2013-0806-GLOB

Don't 'foreign' pilots practice vasi/papi these days in real life and/or in the simulator?? This was and is still working at KSFO.