• Hey, guest user. Hope you're enjoying NeoGAF! Have you considered registering for an account? Come join us and add your take to the daily discourse.

Air Canada pilot nearly lands on SFO International taxiway, mistook it as runway

oneils

Member
Anyways, this is what the approach to 28R looks like at night:

QkvHzdC.png


The column of green lights to the right indicate a taxiway. I don't know how the pilot could have thought he was aligned with the runway.

Haven't read all the comments yet, but some are claiming that the approach lights for 28r weren't on that night creating the confusion.

Edit: and that 28l was darkened. Weird.
 

MrKaepora

Member
If it wasn't for the pilot on the ground and the quick reaction from the ATC in giving the warning this could be a major disaster.
 

Korey

Member
What's up with this fucking pilot though?

He noticed there were a bunch of planes on the runway, shrugs, and attempts to land on them?
 
What's up with this fucking pilot though?

He noticed there were a bunch of planes on the runway, shrugs, and attempts to land on them?


This is what confuses me, too. Shouldn't the response have been sth. like "Um... tower, there is sth. on the runway, possibly planes, I'm aborting, please tell me what the fuck is going on..."
 

FrankCanada97

Roughly the size of a baaaaaarge
The National Transportation Safety Board released an update on their investigation:

https://ntsb.gov/news/press-releases/Pages/pr20170802.aspx


Air Canada flight 759, an Airbus A320, was cleared to land on runway 28R at San Francisco International Airport, but the airplane lined up on parallel taxiway C, which had four airplanes on it awaiting takeoff clearance. Air Canada flight 759 descended below 100 feet above the ground and initiated a go-around after overflying the first airplane on taxiway C.

The following facts are included in the investigative update:

- The captain was the pilot flying ACA759, and the first officer was the pilot monitoring. Both pilots held Canadian airline transport pilot certificates.
- 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).
- 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.
- 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.
- Lights for taxiway C were also on and set to default settings that included centerline lights (green) along its length. Default settings also included edge lights (blue) and centerline lights (green) illuminating the transition or stub taxiways from the runway to the taxiway.

This investigative update does not provide probable cause for the incident and does not contain analysis of information collected thus far in the NTSB's ongoing investigation. As such, no conclusions regarding the cause of the incident should be made from this preliminary information.

blobid0_1501696596232.jpg
 

KHarvey16

Member
Yeah 28L being closed makes sense of this whole thing. It's easy to see how it happened if they weren't paying attention to the advisory or forgot. Still no excuse but it's much easier to understand.
 

XiaNaphryz

LATIN, MATRIPEDICABUS, DO YOU SPEAK IT
Yeah 28L being closed makes sense of this whole thing. It's easy to see how it happened if they weren't paying attention to the advisory or forgot. Still no excuse but it's much easier to understand.

Sure, but runway center lights are always white. Taxiway lighitng isn't.

The National Transportation Safety Board released an update on their investigation:

https://ntsb.gov/news/press-releases/Pages/pr20170802.aspx




blobid0_1501696596232.jpg

There's more info on the full report link:

https://ntsb.gov/investigations/Pages/DCA17IA148.aspx

The incident airplane's cockpit voice recorder had been overwritten, so NTSB investigators did not have that data.
 

FrankCanada97

Roughly the size of a baaaaaarge
That's too bad about the CVR. I guess the plane returned to Toronto and the data was overwritten on the flight back.
 

Lamel

Banned
Ah having the other runway closed makes it seem a lot more plausible that this could happen. Still unacceptable of course, but the situation makes much more sense. Especially after the ATC recording where the pilot states that he sees multiple lights standing on the "runway".
 

Moongazer

Member
They also stated that they did not recall seeing aircraft on taxiway C but that something did not look right to them.
There is no way in hell they didn't see those planes. Not just that something seemed "off" you know like landing on a runway full of planes and killing hundreds of people. I hope they never fly another plane again.
 

Akuun

Looking for meaning in GAF
Christ. Glad no one was hurt.

Time for a round of retraining on the pilots, I guess.
 

FrankCanada97

Roughly the size of a baaaaaarge
There is no way in hell they didn't see those planes. Not just that something seemed "off" you know like landing on a runway full of planes and killing hundreds of people. I hope they never fly another plane again.

It's not that they didn't see anything, they saw lights on what they thought was the runway and raised this point with the tower. These pilots will probably go through some remedial training and be back on the job. There are pilots that actually have landed on taxiways and still kept their jobs.
 
There is no way in hell they didn't see those planes. Not just that something seemed "off" you know like landing on a runway full of planes and killing hundreds of people. I hope they never fly another plane again.

Why? They just learned this lesson the hardest way possible. I am absolutely sure those 2 will check dozens of times before landing a plane ever again.
 
There is no way in hell they didn't see those planes. Not just that something seemed "off" you know like landing on a runway full of planes and killing hundreds of people. I hope they never fly another plane again.
Earlier the point was raised you don't want to fire pilots for incidents like this, since that would lead to them trying to cover up their faults instead of working with the investigation and getting to the bottom of why it happened and how this can be prevented in the future when similar circumstances occur.

For example, now that it is seen that they made the error because of a closed runway, new protocols might be installed to make sure pilots are 100% aware of that when starting landing and not mix up runways.
 

Trouble

Banned
Christ. Glad no one was hurt.

Time for a round of retraining on the pilots, I guess.

The captain should never be allowed to fly again, IMO. This wasn't a trivial mistake and he almost got a lot of people killed. The FO might be worthy of a second chance, but he fucked up big time, too.
 

MJPIA

Member
If I had to guess at this point I'd say this was likely a case of lack of sleep and a big case of confirmation bias which has lead to quite a few accidents in the past.
The pilot is lined up for what he assumes is the runway and sees lights on it and queries the tower which responds and tells him there's no one on the runway and he's clear to land.
Which is true since there are no planes on the runway but the pilot isn't lined up on that, he's heading for the taxiway.
So despite clear evidence of something being wrong because he thought he was lined up for the runway and the tower confirmed said runway was clear he discarded visual evidence that what he was landing on wasn't clear and went to land anyways leading to this event.
But even then its pretty hard to ignore visual evidence right in front of you and that's a big lapse in judgement especially since the flight officer was in the cockpit as well and didn't catch it either so considering the time of this flight I'm inclined to say sleep or lack of it was involved which impaired judgement.


Once the investigation is finished we'll probably be seeing new regulations come from this and I wouldn't be surprised if airlines are already rolling out training videos and memos for their pilots already.
 
Top Bottom