Visit Captain Sim web site  
  Welcome, Guest. Please Login or Register

 

Page Index Toggle Pages: [1] 2 3  Send TopicPrint
 25 777 Crash (Read 29250 times)
Weston
Full Member
*
Offline



Posts: 181
Location: KMCO
Joined: Jul 25th, 2012
Gender: Male
777 Crash
Jul 6th, 2013 at 9:08pm
Print Post  
  

Back to top
 
IP Logged
 
LOLcakes
Full Member
*
Offline



Posts: 155
Location: Sydney, AU
Joined: Jan 27th, 2012
Re: 777 Crash
Reply #1 - Jul 7th, 2013 at 2:23am
Print Post  
The 777's first fatal accident in over 18 years of service  Sad
  

Back to top
 
IP Logged
 
Weston
Full Member
*
Offline



Posts: 181
Location: KMCO
Joined: Jul 25th, 2012
Gender: Male
Re: 777 Crash
Reply #2 - Jul 7th, 2013 at 4:34am
Print Post  
It was human error not the airplane that is good
  

Back to top
 
IP Logged
 
tjh876
Full Member
*
Offline



Posts: 90
Location: New Jersey, USA
Joined: Jul 10th, 2011
Gender: Male
Re: 777 Crash
Reply #3 - Jul 7th, 2013 at 5:23am
Print Post  
Weston wrote on Jul 7th, 2013 at 4:34am:
It was human error not the airplane that is good


I don't want to sound rude, but lets not jump to conclusions yet. I do lean the same way though. In my honest opinion, there were two issues with that approach, one of them that they either stalled or were just too low, and that they were really right, at least looking at the debris field.

I thought I'd cover some of the things I've heard and my thoughts on them. First off, some news organizations already obtained ATC tapes which are readily available on Youtube, and along with some "experts" have been starting to piece together the series of events. The problem is that clip of ATC on Youtube I've seen CNN use missed a HUGE part of the actual transmissions, where someone assumingly in the background of the tower controlled notices the crash. There are a lot of misleading ideas because of that. What did actually happen according to ATC recordings, the plane crashed, and THEN emergency crews were summoned.

The idea of tired pilots raises another possibility, but that is not the first time that flight has happened, it is quite frequent, along with a flight to LAX under the same flight number, at least according to Flightaware. The idea that the pilots were too tired seems far feteched, especially if I am not mistaken, usually the longest a flight crew can fly in a day is 8 hours (although that is US guidelines if I am not mistaken, and this is not a US airline) which means chances are there was a second flight crew to relieve the first crew. The flight is about 10-11 hours from what I recall looking at.

Now the third and final thing I want to say is that do not rule out mechanical issues. Maintenance among other things could have also played a role. Although it seems there was an issue with pitch and glide slope, there is a chance that something might have lead to that. And they say it was a manual landing, but I do not know where that came from (correct me if I am wrong and missing something). They could have been using ILS for all we know. I think they said that it was a visual approach, but it could have been ILS assisted, and that brought it down.

So it could have been pilot error, just a little too slow and too much pitch, and especially at an airport like San Fran, it can really hurt you. Yet I would wait till we hear about flight data recording stuff, and that won't be long (probably not long till the countless documentaries are made too). It probably is not a repeat of the icing engine performance issue, but it could have been a bird strike that went undetected at the last minute. The only people who know and who will know are the investigators, and the pilot.

Sorry it is a little long, but thought I'd give my thoughts.

-Tom H
  

Back to top
IP Logged
 
frankj76021
New Member
Offline



Posts: 1
Joined: Feb 19th, 2011
Re: 777 Crash
Reply #4 - Jul 7th, 2013 at 8:33am
Print Post  
ILS was inop and there was a NOTAM released. There is also some speculation that the VASI lights were inop as well. Weather clear with 10+ vis/
  
Back to top
 
IP Logged
 
rservice
Beta Team
*
Offline



Posts: 373
Location: Canada
Joined: Apr 17th, 2006
Gender: Male
Re: 777 Crash
Reply #5 - Jul 7th, 2013 at 12:33pm
Print Post  
I also heard that this was a VFR approach. An experienced accident investigator on CNN has opined that this was pilot error , i.e. , the aircraft was below the glide slope, and did not apply power at a sufficient altitude to successfully initiate a go around. Although this opinion is somewhat speculative. and we will have to await black box data for the exact details. It would appear that observer information may confirm this. It is sad that two lives were lost but it could have been much worse.
Ron
  

Back to top
 
IP Logged
 
Fuchs
Full Member
*
Offline



Posts: 46
Joined: Jan 5th, 2010
Re: 777 Crash
Reply #6 - Jul 8th, 2013 at 9:09am
Print Post  
  

Core i7 920 4.5Ghz Watercooled / Asus Rampage II Gene / GTX670 / SSD OCZ Agility 3 120Go / 6Go Corsair XMS3 / FFB2 / G940 / Tir 5 / etc, etc, etc...
Back to top
 
IP Logged
 
LOLcakes
Full Member
*
Offline



Posts: 155
Location: Sydney, AU
Joined: Jan 27th, 2012
Re: 777 Crash
Reply #7 - Jul 8th, 2013 at 11:31am
Print Post  
7 seconds before impact: Speed acknowledged by pilots
4 seconds before impact: Throttle increased to attempt to increase speed
1.5 seconds before impact: Go-Around initiated by pilot

Landing speed was calculated to be 137 knots, actual speed was "significantly less than 137 knots."

Pilot in command was new to the 777 and still in transition phase with approx. 43 hours in the aircraft type.
  

Back to top
 
IP Logged
 
Lost in Isaan
Senior Member
*
Offline



Posts: 325
Location: Udon Thani, THAILAND
Joined: Dec 11th, 2009
Re: 777 Crash
Reply #8 - Jul 8th, 2013 at 12:03pm
Print Post  
We armchair pilots do not have the right to speculate NOR should we. I've seen most all the footage and all I can say is the B777 is the MOST sturdy aircraft I've seen to date. To come to rest after that with so few casualties is nothing less than amazing. I also refer to Heathrow!. AND as with that incident we still cannot eliminate fuel (iceing) contamination or what ever.
  

Regards Bruce

This message has been sent from my 1977 Apple II using 2 Hinze bake bean cans and piano wire!
Back to top
 
IP Logged
 
rservice
Beta Team
*
Offline



Posts: 373
Location: Canada
Joined: Apr 17th, 2006
Gender: Male
Re: 777 Crash
Reply #9 - Jul 8th, 2013 at 12:17pm
Print Post  
I wonder what Lou's opinion is at this early stage , also can the engines spool up if there is fuel starvation, i.e. icing of the fuel?
Ron
  

Back to top
 
IP Logged
 
LOU
Beta Team
*
Offline


727,707,747,757,767=
40years of Boeings

Posts: 1614
Location: Central PA, USA
Joined: Mar 3rd, 2010
Gender: Male
Re: 777 Crash
Reply #10 - Jul 8th, 2013 at 7:14pm
Print Post  
I have to agree with Bruce of Lost in Isaan:

The 777 is truly a sturdy built aircraft. The amount of structure that remained at zero motion was remarkable.



The following is speculation

Here is a printout from a site that records flights from radar information.
http://flightaware.com/live/flight/AAR214/history/20130706/0730Z/RKSI/KSFO/track...




Interesting data here.  Less than 2 min to landing, he was at 169 kts/194 mph passing 1400', vertical speed 1380 fpm down.  Descent rate remains at 1300 fpm or more until 600' above the ground with decreasing airspeed.  Airspeed continues to decay to below normal as descent rate decreases to a more normal value.  Looks like the nose is coming up but without power increase.  Then at 100' above the ground (water) airspeed is down to 109kts, looks like a big pitch up at low airspeed.  Likely they were in a stall condition prior to touchdown.  Fits a classic high unstabilized visual descent with an pitch overcorrection near the ground with little to no power increase leading to a stall.  Just my opinion from the raw data.



I flew a few approaches in the CS 777 to see what it would look like from the cockpit and the ground. I set a landing weight around 400,000# which gave me a Vref of 129 kts. After flying several approaches and doing screen captures of the approach I came up with these two shots.

Here is the plane in landing configuration. I have less than the necessary thrust set to make the speed bleed off to near stall.
The speed in this picture is 108 KTS and a vertical speed of -420 FPM @ 100 feet above the runway, with 10 degrees nose up.
I continued to raise the nose to touchdown where I obtained a pitch angle of almost 15 degrees and in stall buffet the last 50 feet above the TDZE.



Here is a snap of the plane just prior to touchdown.



In this case, I was able to land on the runway in stall buffet and just scrape the aft part of the plane. If I had been just a little lower on this approach the gear and the aft of the plane would have hit short of the runway. It looks like, from the cell phone video and passenger reports, that the plane actually skimmed the water prior to hitting the rock wall.

Now, I have never flown the 777, but the other Boeing planes like the 747 and 767 all have pretty much the same auto-thrust system. The throttles are driven by a slip clutch when A/T is engaged. You can override the throttle movement while the A/T system is still engaged. This is something I would do many times to make small corrections to the speed. Since the plane was high and fast, I wonder if the pilot disengaged the A/T during the descent in order to get the plane down into the slot and then "forgot" to re-engage, or thought they were engaged. He could have just kept his hand on the throttles and held them at idle, but if he moved his hand off the throttles to maybe do something else the throttles would have increased if the speed was below what was dialed in on the glare shield speed window. In any event, I can only guess that the A/T were not on during the last portion of the flight and that resulted in a speed bleed as the nose was slowly raised during the last part of the approach.

BTW, during several of my simulated approaches, I kept the throttles back during the last portion of the approach in order to force the stall around 100 feet above the ground. Each time I got the speed down to around 106 KTS, buffet would occur. If I applied full thrust at that point almost every time the plane would make a successful go-around.

Lou

Uploaded with ImageShack.us
  

Processor: Intel Core i7-4770k @3.5Ghz Memory: 6Gb DDR3 1600mhz Video: NVIDIA GeForce GTX 680 Storage: 256Gb Samsung 840 Pro | 120Gb OCZ Agility 3 | WD Black 640Gb 7200rpm 55" Samsung LED - HDTV for monitor
Back to top
 
IP Logged
 
Weston
Full Member
*
Offline



Posts: 181
Location: KMCO
Joined: Jul 25th, 2012
Gender: Male
Re: 777 Crash
Reply #11 - Jul 9th, 2013 at 12:19am
Print Post  
it was the pilot's first landing in the 777
  

Back to top
 
IP Logged
 
Lost in Isaan
Senior Member
*
Offline



Posts: 325
Location: Udon Thani, THAILAND
Joined: Dec 11th, 2009
Re: 777 Crash
Reply #12 - Jul 9th, 2013 at 12:33am
Print Post  
Thank you for the analysis Lou. Was going to go through the same exercise myself this morning, before doing so I spent quite some time viewing Fred Hayes's video. Looks like they were dragging the tail through (or just over) the water for some 18 seconds or about 10 plane lengths, between 550 and 650 meters, prior to hitting the sea wall.

Going to have an interesting few hours replicating that. Crash detection OFF!
  

Regards Bruce

This message has been sent from my 1977 Apple II using 2 Hinze bake bean cans and piano wire!
Back to top
 
IP Logged
 
LOLcakes
Full Member
*
Offline



Posts: 155
Location: Sydney, AU
Joined: Jan 27th, 2012
Re: 777 Crash
Reply #13 - Jul 9th, 2013 at 1:28am
Print Post  
Weston wrote on Jul 9th, 2013 at 12:19am:
it was the pilot's first landing in the 777


Actually, it was his first landing in San Francisco and I think at that time the ILS and PAPI were inop too.
  

Back to top
 
IP Logged
 
LOU
Beta Team
*
Offline


727,707,747,757,767=
40years of Boeings

Posts: 1614
Location: Central PA, USA
Joined: Mar 3rd, 2010
Gender: Male
Re: 777 Crash
Reply #14 - Jul 9th, 2013 at 1:58am
Print Post  
To set the record straight, this is how training and qualifying go in the airlines today.

If you are already a qualified line captain, or even a new pilot to the operating certificate the training will generally follow this way.

First, you will go through several weeks of ground school and pass a written test.
Second, you will have an oral exam in all the systems and procedures pertaining to the aircraft and the operation.
Third, you will get a specified numbers in both a systems trainer called a CPT or cockpit procedures trainer.
Fourth, you will go through a number of hours in a six axis motion flight simulator that will include all parts of the normal, abnormal and emergency flight procedures that will end with a full check ride and a LOFT (line oriented flight training). If you pass all of this you receive your rating in the plane. The only thing left to do is get a specific number of hours of flying with a line flight instructor/check airman which on international types of flying would be at least two round trips and end with a line check ride.

These are the minimum things that need to be accomplished, if a pilot needed more time, it could be given.

It has no bearing as to whether this was his first landing in the real plane or if this was his first time in KSFO. Only very different airports such as high altitude or restricted terrain like PARO or La Paz would you get a check pilot to go along on your first time flying there. KSFO is a very ordinary large airport.

Even with the ILS G/S inop, the pilots could have built the approach in the computer and flown it with computer guidance.

I just have to wonder what the check pilot was doing through out the whole approach. Sure, you have to let the "student" make some mistakes to see if they will correct them, but once you get into the low regime that freedom will have to stop and the check pilot takeover. As a pilot for TWA and American, the rule was that the plane MUST be configured for landing before 1,000 feet on the approach. At 500 feet the non flying pilot (NFP) would call out speed & rate of sink. For example: The NFP would announce - 500' speed 137, sink 700. If the sink rate exceeded 1,000 FPM a go-around was required. The computer at 500 feet will call "sink rate" at around 1,500 FPM.

In this case the sink rate was not a problem, but the speed bleed was legion. To have the reference bug set at 137 KTS and see the airspeed needle at 106 KTS is beyond my understanding. What was the check pilot doing?

I think the Chairwomen of the NTSB, Deborah Hersman is very smart and in due time we will see just what happened.

At TWA our motto was "Fly Aggressively Safe."
  

Processor: Intel Core i7-4770k @3.5Ghz Memory: 6Gb DDR3 1600mhz Video: NVIDIA GeForce GTX 680 Storage: 256Gb Samsung 840 Pro | 120Gb OCZ Agility 3 | WD Black 640Gb 7200rpm 55" Samsung LED - HDTV for monitor
Back to top
 
IP Logged
 
Page Index Toggle Pages: [1] 2 3 
Send TopicPrint
 
  « Board Index ‹ Board  ^Top