ASN logo
ASN Wikibase Occurrence # 196616
Last updated: 22 August 2017
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information.

Date:07-JUL-2017
Time:23:57
Type:Silhouette image of generic A320 model; specific model in this crash may look slightly different
Airbus A320-211
Owner/operator:Air Canada
Registration: C-FKCK
C/n / msn: 0265
Fatalities:Fatalities: 0 / Occupants:
Other fatalities:0
Airplane damage: None
Category:Serious incident
Location:San Fransisco International Airport, CA (SFO/KSFO) -   United States of America
Phase: Approach
Nature:International Scheduled Passenger
Departure airport:YYZ
Destination airport:SFO
Investigating agency: NTSB
Narrative:
On July 7, 2017, about 23:56 local time, Air Canada flight AC759, an Airbus A320, C-FKCK, was cleared to land on runway 28R at San Francisco International Airport (SFO), California, but instead lined up on parallel taxiway C, where four aircraft were awaiting takeoff clearance.
At 23:55:46, when AC759 was about 0.7 mile from the landing threshold and about 300 ft above ground level (agl), the flight crew contacted the ATC tower, mentioned seeing lights on the runway, and requested confirmation that the flight was cleared to land.
At 23:55:52, the airplane flew too far right of course to be observed by the local controller’s ASDE-X/ASSC and was not visible on the ASDE-X/ASSC display for about 12 seconds.
Four seconds later, when AC759 was about 0.3 mile from the landing threshold, the local controller confirmed and recleared AC759 to land on runway 28R.
The flight crew of the first airplane in queue on taxiway C (UA1) transmitted statements regarding AC759, one of which mentioned the alignment of AC759 with the taxiway while AC759 was on short final. The flight crew of the second airplane in queue on taxiway C switched on their airplane’s landing lights as the incident airplane approached.
The incident pilots advanced the thrust levers when the airplane was about 85 ft agl. FDR data indicate that the airplane was over the taxiway at this time, approaching the vicinity of taxiway W.
At 23:56:04, AC759 reappeared on the local controller’s ASDE-X/ASSC display as it passed over the first airplane positioned on taxiway C. About 2.5 seconds after advancing the thrust levers, the minimum altitude recorded on the FDR was 59 ft agl.
At 23:56:10, the local controller directed AC759 to go around. The airplane had already begun to climb at this point.

At the time of the incident, 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. Construction on runway 28L was part of a project that started on February 21, 2017, and notices to airmen were issued to alert operators of its operational status. The closure was also mentioned on the ATIS.
In postincident interviews, both incident pilots stated that, during their first approach, 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.

The aircraft lined up on taxiway C were:
1. UA1 SFO-SIN, Boeing 787-9 Dreamliner, N29961
2. PR115 SFO-MNL Airbus A340-313, RP-C3441
3. UA863 SFO-SYD, Boeing 787-9 Dreamliner, N13954
4. UA1118 SFO-MCO, Boeing 737-924ER N62895

Weather reported at the time of the incident (23:57 LT July 7 / 05:56Z, July 8):
KSFO 080556Z 29012KT 10SM CLR 17/09 A2993 RMK AO2 SLP135 T01720094 10244 20172 51010

Sources:

1. https://ntsb.gov/investigations/Pages/DCA17IA148.aspx
2. https://flightaware.com/live/flight/ACA759/history/20170708/0055Z/CYYZ/KSFO
3. http://www.cbc.ca/news/canada/air-canada-sfo-taxiway-1.4198946
4. https://www.flightradar24.com/data/flights/ac759#e01544b
5. http://www.mercurynews.com/2017/07/10/exclusive-sfo-near-miss-might-have-triggered-greatest-aviation-disaster-in-history/


Images:



Revision history:

Date/timeContributorUpdates
11-Jul-2017 19:11 uski Added
11-Jul-2017 19:15 harro Updated [Aircraft type, Registration, Cn, Location, Phase, Nature, Source, Narrative]
11-Jul-2017 19:38 harro Updated [Time, Source, Embed code, Narrative]
11-Jul-2017 19:44 harro Updated [Embed code, Narrative, Photo, ]
02-Aug-2017 19:46 harro Updated [Source, Narrative, Photo, ]

Corrections or additions? ... Edit this accident description