Skip to content
View in the app

A better way to browse. Learn more.

BluegrassPreps.com

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Boeing 777 Plane Crashes in San Francisco upon landing.

Featured Replies

All things considered, that's not bad

No, and I am guessing they were not the pilots, just a guess by the video.

 

But, to AF41's comment, they said that the fire started a few minutes after the plane stopped and that is why you see most of the top part of the plane burnt and gone. But as someone mentioned earlier, and I agree, it looks like the pilot came in too low, for whatever reason I don't know, but I am sure that the NTSB will fill us in within the next few days.

  • Replies 36
  • Views 4.2k
  • Created
  • Last Reply

Look like it came in over the water - standard for SFO - and was too low. its a long straight approach over the bay on that runway.

 

This 'appears' to be pilot error or instrument failure and not any type of engine or airframe failure.

History of flight.

 

Flight Track Log ? AAR214 ? 06-Jul-2013 ? RKSI / ICN - KSFO ? FlightAware

 

Approach speed for 777 is supposed be around 149 kts. This plane was below that on approach at 600 ft. at 141 kts. It dropped to 123 kts at 300 ft. That is getting near the stall speed at 300 ft.

 

The pilot may have simply stalled on approach due to lack of speed.

 

Sad that there were deaths in any case.

Heard early on in the reports yesterday that there were no distress calls from the aircraft. If that remains true, and given the info BGC provided, I think it was an error by the pilot and not an issue with the plane.

Pilot error. Lets hope no one was impaired.

 

And maybe some tower instruction error. It was way too high early in the approach and it looks like they tried to correct it aggressively (1,300 ft/min is a sharp drop near the end of final and is not good at all). Probably needed to go around with a new approach. My guess would be the pilot reduced flaps and cut the speed to get rid of the lift and get down fast. But then he did not flaps back down in time and had lost too much speed. The result - basically a classic stall.

 

100' feet shorter and this would have been a complete disaster. 100' longer and its a non-event.

 

I am not a pilot but I did this landing at SFO over 20 times in 2008 - mostly in 737s. Its usually a very long, smooth approach at constant speed and decent. The only activity during the long final approach is about 3 or so flap extensions on the way down. When you are sitting in the emergency row over the wings, my usual spot, you hear the flap motor every time they adjust them in a 737.

  • Author

That video was really cool, toward the end where the computer said something like final call out at 200, was that the last chance they had to pull up and not land if something were to have happened on the runway or something. Also why did the computer call the pilot a retard twice, I thought it looked like a solid approach and landing.

That video was really cool' date=' toward the end where the computer said something like final call out at 200, was that the last chance they had to pull up and not land if something were to have happened on the runway or something. Also why did the computer call the pilot a retard twice, I thought it looked like a solid approach and landing.[/quote']

 

It just wanted them to slow down a tad.

Some eyewitness accounts are saying that there should have only been one death, that the second death was due to a rescue vehicle running over the girl.

anyone see the video today of the full crash from the other side of the bay. Looks like the plane was just too low and landed to early, pretty wicked spins n such after the tail was sheared off.

I am betting that someone is going to get fired after confirming these names...[video=youtube_share;hSRnNC5s3Jw]

Archived

This topic is now archived and is closed to further replies.

Recently Browsing 0

  • No registered users viewing this page.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.