Landing Incident @ SFO

Status
Not open for further replies.
drunkenbeagle said:
Who knows.

1) sudden loss of power
2) bad data from flightaware
3) misjudged visual and screwed the pooch
4) a million other things we haven't thought of.

I don't know. I sent a text to XYZ about some crew from ABC that I thought was being stupid JKY, after I thought about it for a while, 'cause I don't know. I waited for hindsight to say "yeah, that was pretty stupid, so why don't I talk to some people that know more than me."
Click to expand...

It's looking like # 2 and a-netters will solve this. :)
 
flyingbum said:
CNN bashing update:

"The horizontal stabilizers are the parts on the tail that go side to side."
Click to expand...

The lead singer of, "A flock of seagulls", had those made of his hair. He too was aerodynamic to a point. YouTube can confirm this.

Actually, now that I think about it, maybe he was a 60's era Beechcraft.
 
Cherokee_Cruiser said:
adfsf.jpg
Click to expand...

That is nice but you never answered my question.
 
With the amount of parks and spotting locations along the bay, I'm surprised there isn't a YouTube video on the landing. Or even pictures on short final. Maybe it will start coming out soon.
 
What question? You are using values that may or may not be accurate, therefore I can't address them. 1320fpm? Really? Not even my airplane can tell me if if I'm doing 1320 fpm down. It'll tell me 1.3 or 1.4. Flightaware is the new FDR? If it is, I'll address it. But since it is NOT, I cannot comment on a random value published online.
 
Cherokee_Cruiser said:
What question? You are using values that may or may not be accurate, therefore I can't address them. 1320fpm? Really? Not even my airplane can tell me if if I'm doing 1320 fpm down. It'll tell me 1.3 or 1.4. Flightaware is the new FDR? If it is, I'll address it. But since it is NOT, I cannot comment on a random value published online.
Click to expand...


Where did I crucify the crew was my question...
 
juxtapilot said:
Interesting in that ATC recording someone yells "Go Around" several times.. It's kind of blocked by the cessna, though not at all his fault. I wonder if that was the UAL 885 crew watching this from the end of the runway...?
Click to expand...
Hard to tell, but I think that was SKW for the parallel announcing his intentions.

Just my take.

~Fx
 
Seggy said:
Where did I crucify the crew was my question...
Click to expand...

The implication is there. Repeating the 1320fpm at 600feet. You're implying a high descent rate at that altitude, which may or may not be true. The implication is there for an unstable approach and therefore faulting the pilots.
 
Cherokee_Troll, I haven't seen any crucifixion in either words or implication from Seggy. He's merely provided data. That data (if accurate) could indicate a whole host of possible reasons for the crash, and many of them have nothing to do with crucifying the crew.

As usual, you're just looking to stir up trouble.
 
z987k said:
Based on my experience with the exact people that were flying this, I'd say you're going to win this bet. I'd also bet that a bunch of the current and former AMFers could make our own 12 page thread on times and things Koreans have done to try and kill us. Mind you these are not students. Fully certificated pilots, and they went back home to fly Boeings and Airbi.
I'm pretty sure JayAre has at least a few stories. I know I do, and I only flew with them for about 6 months.
I guess I shouldn't be throwing the pilots under the bus, but based on past experience that is the conclusion I would jump to.
Click to expand...

Quoted for truthiness
 
Cherokee_Cruiser said:
The implication is there. Repeating the 1320fpm at 600feet. You're implying a high descent rate at that altitude, which may or may not be true. The implication is there for an unstable approach and therefore faulting the pilots.
Click to expand...

Seggy did not say that. He posted their numbers, and warned not to trust them (which none of use do)
 
Status
Not open for further replies.
Back
Top