Asiana 777 Crash at SFO

Subscribe
5  45  51  52  53  54  55  56  57  58  59  65 
Page 55 of 98
Go to
Back Everything Up
Quote: Has anyone (at NTSB or elsewhere) said exactly what they had loaded into the FMS yet?

I haven't been into SFO in about 7 years but on every visual approach, we always have something loaded in the FMS for reference. If there's an ILS, we'll have that, if no ILS, we'll have the RNAV-GPS approach, if there is one, or perhaps if there is nothing for that runway, then most guys will load the runway/elevation/speed, with another point about 5 miles out with an altitude and speed loaded on the Legs Page, so we have something to look at on the ND, for vertical guidance.

We have heard that the Asians like to use all the automation, all the time, but does SFO have a RNAV-GPS approach to 28L? Did they have that loaded, and were they in LNAV/VNAV until autopilot disconnect at 1,600'?

I agree Timbo. As Jungle and others have pointed out, this accident was an "automation" and CRM issue; not a stick and rudder problem. To those that said they were "tired" after a long flight...bull**.

First of all, all visual approaches must be backed up by some instrument approach procedure. If it's clear and a million and you want to hand fly the approach, go for it. I do it all the time; however, there is something installed in the box for every approach. The 777, like a lot of other FMC systems, allow for the construction of an approach even if the runway doesn't have one installed. We learned that in initial sim training and as part of our type ride or company checkride, a visual approach with NO vertical or lateral guidance must be flown properly. We would "construct" an approach and the 777 software gives one a 3.5 degree glide slope (that can even be a variable) from the end of the runway. It even had a "Chinese glide slope" as we called it, that displays just like an ILS glide slope on a visual approach. It's simple.

In my view, and I've worked with many Asian pilots, there is a over dependance on automation. Some of that is cultural and some of it from their training. It doesn't mean the Korean pilots aren't smart; they are but are trained to use the autopliots/autothrottles to excess. Nuff' said.

This accident was a pilot undergoing IOE with a Check Airman/IOE Instructor who was behind the eight ball for whatever the reason. That will come out of the investigation. What I still can't understand is, and please help me....how this accident happened in an aircraft that has a ton of software to facilitate approaches and landing and is so easy to fly and land.

At a Loss for an explanation.... G'Day Mates
Reply
Quote: This was a CRM issue, not stick and rudder issue. There are plenty of Koreans that have good stick and rudder skills.

I wasn't in the 214 cockpit but clearly there was an atmosphere of keep your mouth shut. The captain got behind the plane and no one said jack $hit. I tell jumpseaters if you see something weird let us know.
Koreans have a history of Cockpit Gradient/CRM deviations...i agree if the below were understood/complied...SFO probably could have been avoided...


COCKPIT RESOURCE MANAGEMENT :

SITUATIONAL AWARENESS : Situational awareness is the accurate
perception of the factors and conditions that affects the aircraft and the flight
crew during a specific period of time. More simply, it is knowing what is going on
around you. There is a direct relationship between situational awareness and
safety. It is a fact that pilots who have higher levels of situational awareness are
safer pilots.

CREW COORDINATION : Perhaps one of the most complex skills acquired by a
pilot after completion of his training is crew coordination. It is not a skill that can
be taught but one that is learnt over a period of time by experience in a two or
three crew cockpit. Crew coordination is the ability to share workload by dividing
tasks so as to reduce work levels in high stress situations.

COMMUNICATION : Flight crew spend much of their time communicating. It is
an essential building block to good cockpit management. If the crew's
communication skill is affected, cockpit performance will be enhanced and a high
level of situational awareness can be achieved and maintained. Ineffective
communication can be disruptive, cause misunderstanding and mistakes and
lead to loss of situational awareness. The consequences can be serious even
disastrous.

DECISION MAKING AND JUDGEMENT(Only for PF) Cockpit decision making
is a logical sequence in order to collect adequate facts, assess alternatives and
implement in a timely manner. During critical phases of flight poor decision
making especially when information and alternatives are reducing, will lead to
actions that have serious consequences. Judgment plays a critical role in the
decision making process.
Reply
Quote: With the recent runway construction there it appears as though the threshold was displaced/relocated approximately 500'-750' down the runway. I wonder if the FMS data that they may have used (if that is) was calculating to the older glide path. If my math is correct that would bring then in approximately 1200'-1500' low. I get how that could possibly throw then off at the last minute trying to stretch the glide path to make the new aiming point.
Your math is not correct.

To make them 1500' low following the older glide path, the threshold would have to be displaced almost 5 miles. How far are you usually away from the runway at 1500'? 3:1 usually gets you, say 5 miles, right?

Even at the extreme of the 750' threshold move you mention, following the old glideslope would only put them 40 feet low.
Reply
Quote: Your math is not correct.

To make them 1500' low following the older glide path, the threshold would have to be displaced almost 5 miles. How far are you usually away from the runway at 1500'? 3:1 usually gets you, say 5 miles, right?

Even at the extreme of the 750' threshold move you mention, following the old glideslope would only put them 40 feet low.
Thanks, kinda rushed the math on that one.
Im just curious if the FMS data showed them on path.

Was the VASI operational or OTS?
Reply
Quote: EDITED

PAPI-4L system set at 2.85 with a 64' TCH (put into service on Jul 2).
The PAPIs were located just about at the top of the *new* 1,000' marker
Quote: Either their lateral accuracy was as bad as their vertical accuracy, or they did swerve right to try to miss the ALS.

Post #263
Quote:
Quote:
Originally Posted by captjns
Better yet... was the PAPI set for a narrow body versus a wide body?
Quote:
Originally Posted by Busdriver320
My .02..
Quote:
Both GS's have been OTS for awhile, relocation of thresholds (several hundred feet of displacement to comply with some sort of clearway/overrun requirement, which is complete)
Quote:
Both PAPI's have been OTS as well, although not sure if they were today but seems unlikely they have been re-aligned as threshold move was only complete last week.
Quote:
Charted visual rec altitudes on both L & R are below actual electronic GS & PAPI paths; actual ILS GS at the "Bridge" is 2000 ft, chart rec's 1800+ for 28R and 1900+ for 28L. Anyone at those altitudes at the Bridge is already low.
Quote:
Barring mechanical failure to produce thrust, I think they got low and had no electronic or visual guidance to help them and it was too late when they realized it. It's clear the tail hit the rip-rap (stone breakwall) at the bay perimeter.
Quote:
Quote:
I can see the scenario now for your next LOFT. Your going to be required by the FAA to demonstrate a visual approach with an inop glide slope, no PAPI, and no vertical NAV .
Quote:
Quote:
Gorgeous day. Cleared for the visual. (Maybe while still on the downwind) No ILS for backup. No VASI. Didn't program, or didn't follow, a VNAV glide path.
Quote:
FAA press release:

Quote:
On July 6, 2013, weather conditions at San Francisco International Airport (SFO) allowed pilots to land by visually lining up for approach before landing—referred to as landing under visual flight rules (VFR).

On June 1, 2013, the FAA issued a notice to airmen (Notam) indicating that the glide slope system was scheduled to be out of service from June 1, 2013 to August 22, 2013 on Runways 28 left and 28 right. The glide slope system, which is not necessary for safe landing at SFO under visual flight rules, was being relocated as part of a runway safety improvement project.
The precision approach path indicator (PAPI) light system, which provides visual guidance information to help a pilot acquire and maintain the correct approach to a runway was operating at the time of the accident. The localizer, or radio frequency system which helps guide aircraft to land on the center line of the runway was operational as well. Neither of these systems is needed to support an approach and landing made under visual flight rules.
The FAA regularly monitors and maintains all of the airport's navigational aids to make sure they are accurate. While the ongoing runway safety project at SFO is underway, the FAA has operational Instrument Landing Systems available on its other runways to allow pilots to make safe instrument landings in low visibility conditions.
From previous posts, and known runway construction, I had assumed that the PAPIs were OTS, but that doesn't seem to have been the case.
It is easy to see that there seemed to be some confusion early on (or at least I was confused), but it has since been widely reported that the PAPIs were operational and the crew said what they were seeing during the approach - - full red right before impact.
Quote: Thanks, kinda rushed the math on that one.
Im just curious if the FMS data showed them on path.

Was the VASI operational or OTS?
Reply
Quote: Thanks, kinda rushed the math on that one.
Im just curious if the FMS data showed them on path.

Was the VASI operational or OTS?
28L has PAPI. I think someone posted here (about a million pages back) that it was full up.
Reply
Quote: Thanks, kinda rushed the math on that one.
Im just curious if the FMS data showed them on path.

Was the VASI operational or OTS?
The 28L threshold was displaced 300' for RSA. The PAPI was operational (there is no VASI), and the GS was NOTAM'd OTS due to the RSA/Lighting and NAVAIDS improvement project. The PAPI is now OTS after being destroyed in the crash.
Reply
Quote: 28L has PAPI. I think someone posted here (about a million pages back) that it was full up.
Thanks, I know there was a little back on forth on whether the subject a few days back. This thread has been a busy one, so I probably missed the answer.

This will be a very interesting case study in the future seeing as its so rare to be able to interview the flight crew after a crash of this magnitude.

Take a look at some of the aircraft interior pictures. It's a miracle as many passengers made it out.
Reply
Quote: or perhaps if there is nothing for that runway, then most guys will load the runway/elevation/speed, with another point about 5 miles out with an altitude and speed loaded on the Legs Page, so we have something to look at on the ND, for vertical guidance.
Both airlines I've worked, we've done the same. Of course just like ANY automation, it's "garbage in=garbage out", etc.

And if there wasn't a displaced threshold or other variables, I wonder if due to the procedures, cultures, and overall mindset of some foreign airlines, I wonder if they even have the liberty to build things with the FMS, even in VMC conditions? As is, they may have a policy of "DON'T EVER TRY TO BUILD YOUR OWN GUIDANCE, IF THE PROCEDURE IS NOT IN THE DATA BASE IT NOT AUTHORIZED".
Reply
Great Photograph
Quote: The PAPIs were located just about at the top of the *new* 1,000' marker
It is easy to see that there seemed to be some confusion early on (or at least I was confused), but it has since been widely reported that the PAPIs were operational and the crew said what they were seeing during the approach - - full red right before impact.
Thanks for posting the photograph of the accident scene Jarhead :-). It really answers and yet begs a few more questions.

I think it's interesting to note that the debris field is to the right of the extended 28L centerline. That in and of itself, is a curious fact. Also, several people posted cell phone camera videos of the accident and the tail was definately in the water prior to impact with the rock wall.

With all the comments about the PAPI, which was operational, displaced thresholds, VASI, etc. let's not forget one undisputed fact. The weather was not a factor and this was a visual approach. We won't know what was transpiring in the cockpit, what interaction the crew had, what was programmed in the FMS or what was being said until the investigation is complete and the entire report released.

Still scratching my head trying to figure this one out.

G'Day
Reply
5  45  51  52  53  54  55  56  57  58  59  65 
Page 55 of 98
Go to