SeanD
Well-Known Member
Indeed there is...And my Pale Ale is empty...Must run to teh fridge...
Dude, when did they start making Sierra Nevada in a can?

Indeed there is...And my Pale Ale is empty...Must run to teh fridge...
Stabilized 500, or more likely 1000 is typical. But flightaware data feeds aren't accurate looking at flights where I have been the one driving in the past, so I wouldn't put much faith into them
Fair enough....But if they are bad, they should be equally bad on different days....?.
Dude, when did they start making Sierra Nevada in a can?![]()
So you are saying a 1320 FPM rate of descent at 600 feet AGL (if the numbers are true) is a normal rate of descent?
CNN bashing update:
"The horizontal stabilizers are the parts on the tail that go side to side."
So a crusty old Ex-Pat Captain said "Hey squints, I bet you can't put it on the numbers."
Sent from my DROID RAZR using Tapatalk 2
So you are saying a 1320 FPM rate of descent at 600 feet AGL (if the numbers are true) is a normal rate of descent?
With ya on the numbers true part- anyone else feel like looking at a few hundred flight aware arrivals into SFO and seeing what they report on short final? The rate of decent is likely inaccurate that low, they don't sample quickly enough (engineer in me speaking)
Different engines, warm weather = no fuel freeze. Dollars to donuts some zero to hero porked it because he can't fly a visual without a glide slope.
That may be true...Serious question though....But at some point shouldnt each flight regardless of the method to get to final, be established on an identical glideslope path before touching down? I would 'think' that could provide some data to compare would it not?
So you are saying a 1320 FPM rate of descent at 600 feet AGL (if the numbers are true) is a normal rate of descent?
Then why on the 5th was the descent rate at 600 feet 720 FPM...?
http://flightaware.com/live/flight/AAR214/history/20130705/0730Z/RKSI/KSFO/tracklog
We will see if these numbers are true.
What I'm saying is I don't know how accurate the flightaware website is and the last thing I'd want is to have other pilot crewmembers crucifying me based on web data that may or may not be accurate. Stop harping on "1320" as if that's an accurate number. We don't know. The NTSB will analyze the FDR and CVR data, and they will spell out exactly what the path of this aircraft was. Until then, it's just speculation.
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."
Then why on the 5th was the descent rate at 600 feet 720 FPM...?
http://flightaware.com/live/flight/AAR214/history/20130705/0730Z/RKSI/KSFO/tracklog
We will see if these numbers are true.
Yep, one would think....