Exclusive: SFO near miss might have triggered ‘greatest aviation disaster in history’
#617
Suspended
Join Date: Oct 2006
Location: Atherton, CA
Programs: UA 1K, AA EXP; Owner, Green Bay Packers
Posts: 21,690
The ATC not recognizing that the jet didn't show up where expected on his radar likely contributed to not recognizing the danger sooner and calling for the go-around sooner. It's an error that contributed, but of much less importance than the pilot error.
#618
Join Date: Sep 2000
Location: OGG, YYC
Programs: AA, AC
Posts: 3,697
My understanding of the cockpit voice recorder limitation (based on this thread) is that it loops back over itself after 30 minutes and this was the result of privacy concerns brought up by the Air Canada Pilots Association. Also, as I understand it, this is not a hardware limitation of the CVR.
In this case, privacy shouldn't be a concern as cockpit conversations during critical phases of flight must be sterile, and after the aircraft had landed, one would guess that by the time the aircraft lands on the runway and it gets to the gate and parked, that the majority of the 30 minutes would already have disappeared.
If my understanding is correct, it seems incredibly silly to me that Air Canada management would allow for a 30 minute max in the first place. Is this an industry norm or is Air Canada outside the line of best fit?
In this case, privacy shouldn't be a concern as cockpit conversations during critical phases of flight must be sterile, and after the aircraft had landed, one would guess that by the time the aircraft lands on the runway and it gets to the gate and parked, that the majority of the 30 minutes would already have disappeared.
If my understanding is correct, it seems incredibly silly to me that Air Canada management would allow for a 30 minute max in the first place. Is this an industry norm or is Air Canada outside the line of best fit?
The trigger for the CVR recording to end is the shutdown of the last engine. It continues to record for a period after shutdown (an additional 5 or 10 minutes, IIRC).
#619
A FlyerTalk Posting Legend
Join Date: May 2002
Location: YEG
Programs: HH Silver
Posts: 56,449
https://www.forbes.com/sites/christi.../#2e0ef8c439e5
In its investigation into the Air Canada flight that came thisclose to triggering a multi airliner pile-up at San Francisco Airport last month, American safety authorities will try to determine why the Airbus A320 was over a crowded taxiway instead of an open runway awaiting the plane’s arrival.
But the National Transportation Safety Board should also examine why Air Canada didn’t notify authorities that Flight 759 flew within feet of creating a chain-reaction disaster of historic proportions.
This is not just a procedural question. Air Canada’s silence allowed the recording from the cockpit voice recorder to be taped over by subsequent flights. The CVR contained information critical to the investigation.
“It’s not clear whether there has been an attempt to cover up an incident,” said Jim Hall, the former chairman of the NTSB and now a safety consultant in private practice.
In its investigation into the Air Canada flight that came thisclose to triggering a multi airliner pile-up at San Francisco Airport last month, American safety authorities will try to determine why the Airbus A320 was over a crowded taxiway instead of an open runway awaiting the plane’s arrival.
But the National Transportation Safety Board should also examine why Air Canada didn’t notify authorities that Flight 759 flew within feet of creating a chain-reaction disaster of historic proportions.
This is not just a procedural question. Air Canada’s silence allowed the recording from the cockpit voice recorder to be taped over by subsequent flights. The CVR contained information critical to the investigation.
“It’s not clear whether there has been an attempt to cover up an incident,” said Jim Hall, the former chairman of the NTSB and now a safety consultant in private practice.
#621
A FlyerTalk Posting Legend
Join Date: May 2002
Location: YEG
Programs: HH Silver
Posts: 56,449
#624
Join Date: Dec 2014
Location: YVR
Programs: Bottom feeder Star Gold
Posts: 2,652
Originally Posted by After Burner
But I'd be much less concerned about stupid CVR limitations than I would about airlines operating 1980s technology passenger airliners that allow a pilot to line up with and almost land on a taxiway.
Originally Posted by Admiral Ackbar
In this (and 90% of everything else about this incident ) we agree. As I stated earlier, I hope the $$$ saved were worth it.
#625
Join Date: Dec 2011
Location: YYZ
Programs: AC SEMM / HH Diamond
Posts: 3,167
No argument from me on the 30 minute limit. It's utterly absurd.
Another question is: what is the effect of pulling the breaker? I talked to an A320 pilot this morning who told me there is, in fact, a CVR breaker in the cockpit. I asked what effect pulling it would have. The answer I got was "Hmm, I don't know." Possibly pulling the breaker will cause all data to be lost (??)
Apparently the manual doesn't provide much information about the CVR.
Another question is: what is the effect of pulling the breaker? I talked to an A320 pilot this morning who told me there is, in fact, a CVR breaker in the cockpit. I asked what effect pulling it would have. The answer I got was "Hmm, I don't know." Possibly pulling the breaker will cause all data to be lost (??)
Apparently the manual doesn't provide much information about the CVR.
Besides, what if the subsequent landing attempt is also ... ahem ... a "hard landing"?
If we want to secure the CVR data better (and I agree we do), then the way to achieve that is not by turning it off mid-flight.
#626
Join Date: May 2012
Location: BKK/SIN/YYZ/YUL
Programs: DL, AC, Bonvoy, Accor, Hilton
Posts: 2,922
Please direct me to the part of the NTSB statement where this was stated.
I am looking at the statement from updated August 2 and do not see mention of this description. https://ntsb.gov/investigations/Pages/DCA17IA148.aspx
Was this a supplemental statement? I don't understand how this could not be a reportable event, as the aircraft nearly crashed into several other aircraft. I certainly am open to education in this regard if I am misunderstanding something here.
What I do see is the news release of August 2 which suggests the pilot(s) had a significant role in this event https://www.ntsb.gov/news/press-rele...r20170802.aspx
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.
If I go into armchair expert mode, if it looks and sounds like pilot error, then chances are it most likely is pilot error. However, I am waiting for the results of the full investigation, before going into flatbed expert mode.
#627
Join Date: Sep 2005
Location: YYC
Programs: AC SE100*1MM; Spire Ambassador
Posts: 1,341
https://www.forbes.com/sites/christi.../#4dc994d23845
From this Forbes article, it says that Keith Holloway, NTSB spokesman, said that the airlines was not required to report this incident, purely based on the NTSB regulations.
From this Forbes article, it says that Keith Holloway, NTSB spokesman, said that the airlines was not required to report this incident, purely based on the NTSB regulations.
#628
Join Date: Dec 2011
Location: YYZ
Programs: AC SEMM / HH Diamond
Posts: 3,167
What? Where? When did the NTSB say this was "not a reportable event?"
Please direct me to the part of the NTSB statement where this was stated.
I am looking at the statement from updated August 2 and do not see mention of this description. https://ntsb.gov/investigations/Pages/DCA17IA148.aspx
Was this a supplemental statement? I don't understand how this could not be a reportable event, as the aircraft nearly crashed into several other aircraft. I certainly am open to education in this regard if I am misunderstanding something here.
Please direct me to the part of the NTSB statement where this was stated.
I am looking at the statement from updated August 2 and do not see mention of this description. https://ntsb.gov/investigations/Pages/DCA17IA148.aspx
Was this a supplemental statement? I don't understand how this could not be a reportable event, as the aircraft nearly crashed into several other aircraft. I certainly am open to education in this regard if I am misunderstanding something here.
Keith Holloway, a spokesman for the NTSB referenced the federal regulations in explaining, “the operator was not required to make a report to the NTSB.”
830.5 Immediate notification.
The operator of any civil aircraft ... shall immediately, and by the most expeditious means available, notify the nearest National Transportation Safety Board (NTSB) office, when:
(a) An aircraft accident or any of the following listed serious incidents occur:
(12) Any event in which an operator, when operating an airplane as an air carrier at a public-use airport on land:
(i) Lands or departs on a taxiway, incorrect runway, or other area not designed as a runway; or
(ii) Experiences a runway incursion that requires the operator or the crew of another aircraft or vehicle to take immediate corrective action to avoid a collision.
The operator of any civil aircraft ... shall immediately, and by the most expeditious means available, notify the nearest National Transportation Safety Board (NTSB) office, when:
(a) An aircraft accident or any of the following listed serious incidents occur:
(12) Any event in which an operator, when operating an airplane as an air carrier at a public-use airport on land:
(i) Lands or departs on a taxiway, incorrect runway, or other area not designed as a runway; or
(ii) Experiences a runway incursion that requires the operator or the crew of another aircraft or vehicle to take immediate corrective action to avoid a collision.
Let me go & grab a bowl of popcorn before everyone starts to debate this interpretation.
#629
Join Date: Sep 2000
Location: OGG, YYC
Programs: AA, AC
Posts: 3,697
What? Where? When did the NTSB say this was "not a reportable event?"
Please direct me to the part of the NTSB statement where this was stated.
I am looking at the statement from updated August 2 and do not see mention of this description. https://ntsb.gov/investigations/Pages/DCA17IA148.aspx
Was this a supplemental statement? I don't understand how this could not be a reportable event, as the aircraft nearly crashed into several other aircraft. I certainly am open to education in this regard if I am misunderstanding something here.
What I do see is the news release of August 2 which suggests the pilot(s) had a significant role in this event https://www.ntsb.gov/news/press-rele...r20170802.aspx
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.
If I go into armchair expert mode, if it looks and sounds like pilot error, then chances are it most likely is pilot error. However, I am waiting for the results of the full investigation, before going into flatbed expert mode.
Please direct me to the part of the NTSB statement where this was stated.
I am looking at the statement from updated August 2 and do not see mention of this description. https://ntsb.gov/investigations/Pages/DCA17IA148.aspx
Was this a supplemental statement? I don't understand how this could not be a reportable event, as the aircraft nearly crashed into several other aircraft. I certainly am open to education in this regard if I am misunderstanding something here.
What I do see is the news release of August 2 which suggests the pilot(s) had a significant role in this event https://www.ntsb.gov/news/press-rele...r20170802.aspx
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.
If I go into armchair expert mode, if it looks and sounds like pilot error, then chances are it most likely is pilot error. However, I am waiting for the results of the full investigation, before going into flatbed expert mode.
I hunted through the regs myself, shortly after this occurred, and couldn't find anything specifying that this type of occurrence must be reported. So believe it or not it does appear that there is no regulatory reporting requirement.
From this Forbes article, it says that Keith Holloway, NTSB spokesman, said that the airlines was not required to report this incident, purely based on the NTSB regulations.
#630
Join Date: Sep 2000
Location: OGG, YYC
Programs: AA, AC
Posts: 3,697
Gentlemen, there is nothing about "1980s technology airliners" that "allow" a pilot to misalign a landing path. Precision approaches have been flown long before the earliest A320s were introduced, but I'd venture in this event that all reference was focused outside the front windows. Visual approaches are subject to the same human errors today as they were since Kitty Hawk days. Without having to dole out millions for the latest gee-whiz avionics suite, there are plenty of redundant navigation tools aboard every aircraft in AC's fleet to enable situationally aware pilots to land exactly where intended.
More up-to-date technology would clearly show the aircraft not being aligned with the runway even if the ILS had not been set up. But as you suggested, 100% of their attention may well have been out the window rather than on the instruments. The problem I have with that notion is that the final fix in the FMS 28R approach (F101D) places them exactly on the localizer, exactly lined up with a tunnel of unmistakable approach lights. That's what they would've seen out the window. They actually would have had to have banked the aircraft substantially to the right to line up with the taxiway.
Did they think those approach lights in front of them were for 28L? If so, that would mean they didn't brief/understand the FMS28R approach and missed the NOTAM, the ATIS, and NORCAL transmissions that reported 28L as closed.