Originally posted by BoeingBobby
View Post
Announcement
Collapse
No announcement yet.
Air Canada pulls a Hans Solo
Collapse
X
-
Congratulations, BB. I always enjoy your contributions and hope you will remain here.
Leave a comment:
-
Originally posted by Evan View PostYou're joking right?
And descending in the clouds towards something that is ALWAYS hard is a different level of risk than miss identifying really dim blue lights from really dim white lights.
And, let me restate two things: Bobbies objection to a potentially distracting TOPMS
and
Evan wants one MORE system when magenta lines are available.
Leave a comment:
-
Originally posted by 3WE View PostStrikes me as complicated and I have seen MANY airliner approaches where you may not be lined up until VERY late.
Besides, what's that special thingie that works much like a VOR?
Or that crazy histogram-adjusted pink line depiction...
Do we need any MORE things distracting pilots, WHEN IN FACT they had TOTALLY ADEQUATE situational awareness?
What's that crazy dial/tape thing called altimeter? Why do we need GPWS again? Oh right, human factors...
I think a runway track deviation warning using EGWPS that gives a warning in ground proximity wouldn't be a bad idea.
It would have prevented this almost total disaster.
Leave a comment:
-
Originally posted by Evan View PostI do wonder why lateral deviations are not part of it. Ground Proximity Warning is really Non-Runway Proximity Warning.
Besides, what's that special thingie that works much like a VOR?
Or that crazy histogram-adjusted pink line depiction...
Do we need any MORE things distracting pilots, WHEN IN FACT they had TOTALLY ADEQUATE situational awareness?
Leave a comment:
-
Originally posted by Schwartz View PostI don't think so. When humans are trained in routine, the brain will strongly gravitate to strive for the same conditions even when there are warnings that something is different. There is a much higher gap/difference required to snap the brain out of an habitual pattern. In this case, it sounds to me like there was enough deviations from the norm they picked up themselves combined with the radio warning that they snapped out of the trap and aborted at the last minute. 59 feet is pretty low... how tall is the tail of a large plane?
I can give so many examples where habit and routine + a belief in what I expect to be a certain way, completely blind me to problems staring me straight in the face. The brain has a lot of processing designed to save us from having to apply active energy to think all the time.
The pilot sounded tired on the radio to me.
Having only one controller doing 3 jobs also a factor, that one has come up before. The controller had equipment to verify the landing aircrafts alignment.
I like the "where is this guy going" that should be added to GPWS verbatim.
Leave a comment:
-
I'll steal a comment from AVHerald: "We'll never come close to understanding and preventing occurences [sic] like this if we simply write it off as "stupid"."
It is pretty clear their confirmation bias overrode all of the other indicators like lights on the runway, the wrong colour landing lights etc.
Several interesting notes:
- they decided to around on their own prior to the tower coming to the party.
- they passed just behind the first plane, and were right in front of the second plane when that plane turned on their lights after the first plane gave warning on the radio (so either the lights, or the radio warning triggered the go-around)
- from the description, diagram, and photos they advanced the thrust levers right in front of the second plane so they would have been lowest awfully close to the tail of the second plane.
This was a LOT closer than was implied early on.
Leave a comment:
-
More info from the same link:
- The incident pilots advanced the thrust levers when the airplane was about 85 feet above ground level. Flight data recorder data indicate the airplane was over the taxiway at this time. About 2.5 seconds after advancing the thrust levers, the minimum altitude recorded on the FDR was 59 feet above ground level.
- Both pilots said, in post-incident interviews, they believed the lighted runway on their left was 28L and that they were lined up for 28R. They also stated that they did not recall seeing aircraft on taxiway C but that something did not look right to them.
As a reference, the tail of a 787-9 is 55.5 ft high (UA001, the 1st airplane in the line on the taxiway, is normally done with a 787-9)
Leave a comment:
-
Originally posted by Quench View Post[ATTACH=CONFIG]8161[/ATTACH]
Quite inexplicable.
I can give so many examples where habit and routine + a belief in what I expect to be a certain way, completely blind me to problems staring me straight in the face. The brain has a lot of processing designed to save us from having to apply active energy to think all the time.
Leave a comment:
-
From:https://www.ntsb.gov/news/press-rele...r20170802.aspx
Runway 28L was closed to accommodate construction; its approach and runway lights were turned off, and a 20.5-ft-wide lighted flashing X (runway closure marker) was placed at the threshold. Runway and approach lighting for runway 28R were on and set to default settings, which included a 2,400-foot approach lighting system, a precision approach path indicator, touchdown zone lights (white), runway centerline lights (white at the approach end), runway threshold lights (green), and runway edge lights (white at the approach end).
Quite inexplicable.
edit:- Automatic Terminal Information Service Q was current and included an advisory that runway 28L was closed and that its approach lighting system was out of service.
Leave a comment:
-
Originally posted by Vnav View PostJust something to think about...relatively dark...assume that 28R was the left parallel and TXY C was the right parallel...
The ATIS almost always said for folks to use caution to avoid mixing up 12L and 13. The tower would ask aircraft if they were familiar with 13.
Bottom line- it's something of a challenge and we seem to have these recurring incidents...lots of fodder for parlour talk, BUT conversely, I imagine this has been studied and beaten to death by true experts.
Since you have us "thinking", I will restate my one genuine thought- it seems to me that "we" dim the runaway lights too much. I know there's valid reasons for the dimness, but given that you occasionally land into severe sunrises and sunsets, it shouldn't kill you to deal with brighter runway lights.
That and a simple cross check of a magenta line or something...
Leave a comment:
-
Originally posted by Gabriel View PostYes. IF they were using it (they were in a visual approach). Anyway, since the plane is intact, you will also have the QAR which has much more and much better info (but is not crash/fire worthy).
There are two areas of concern in preventing dynamic multipath interference with ILS:
Critical Area: The ILS critical area is an area of defined dimensions about the localizer or glide path antenna, such that aircraft and other vehicles within the area cause out-of-tolerance disturbances to the ILS signals-in-space from the limit of the coverage to a distance of 3.7 km (2NM) from the landing threshold.
Sensitive Area: The ILS sensitive area is an area of defined dimensions about the localizer or glide path antenna, such that aircraft and other vehicles within the area cause out-of-tolerance disturbances to the ILS signals-in-space from a distance of 3.7 km (2NM) from the landing threshold to the point at which the ILS signal is no longer required for the intended operation.
I just can't imagine how they could ignore the approach lighting on final, unless I consider Vnav's theory...
Anyway, you might find this interesting:
http://www.icasc.co/sites/faa/uploads/documents/resources/15th_int_flight_inspection_symposium/ils_critical_sensitive.pdf
Leave a comment:
-
Report when SFO is visual.
SFO is DUS minus...
Local time, thats the topic where I always stop to write.. But let me try the world clock.
DUS 0736 local.
JFK 0136 local.
and SFO is JFK minus 3 ? .. the date changes, damn!
JFK minus 1 .. 0041 -- minus 2 2341 and -- minus 3 2241 (Tue July 11th).
SFO then should be 2241 (July 11th) at this very moment.
Thus, SFO is DUS minus .. 9? So, DUS 2155 is .. daylight in the bay. Yes, schedules do not change that much.
And why did I do that calculation? Not for photos of a LH-B744..
For Gabe. You can assume that LH 454 pilots have daylight. But with a four engined jet, it remains interesting enough, with all instrument frequencies turned off:
Leave a comment:
Leave a comment: