Air Canada Flight 759
Airbus A320-211 · Near collision on final approach at night
From Toronto Pearson International Airport (YYZ) to San Francisco International Airport (SFO)
Event
- NTSB case
- DCA17IA148
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Incident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- Event fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- Occupants
- 140
- Survivors
- 140
- InjuriesFatal: death within 30 days. Serious: over 48 hours in hospital within a week, most broken bones, severe bleeding, nerve or organ damage, or serious burns. Minor: anything less. Glossary
- 0 serious · 0 minor (NTSB)
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- Airline
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Airbus A320-211
- Flight
- AC759
- Aircraft type
- Airbus A320
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- C-FKCK
- Operator
- Air Canada
- Onboard fatalities
- Unknown
- Route
- From Toronto Pearson International Airport (YYZ), TorontoTo San Francisco International Airport (SFO), San Francisco, CA
- Aircraft age
- About 25 years (built 1992)
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 129: Foreign
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Approach
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Wrong surface or wrong airport
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- None
Cause areas
- Environmental issues › Operating environment
- Personnel issues › Action/decision
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
From the Wikipedia article
On July 7, 2017, an Airbus A320 operating as Air Canada Flight 759 was nearly involved in an accident at San Francisco International Airport in San Mateo County, California, United States. The flight, which originated at Toronto Pearson International Airport, had been cleared by air traffic control to land on runway 28R and was on final approach to land on that runway; however, instead of lining up with the runway, the aircraft had lined up with the parallel taxiway, on which four fully loaded and fuelled passenger airplanes were stopped awaiting takeoff clearance. The flight crew initiated a go-around prior to landing, after which it landed on 28R without further incident. The aircraft on the taxiway departed for their intended destinations without further incident. The subsequent investigation by the National Transportation Safety Board (NTSB) determined that the Air Canada airplane descended to 59 ft above the ground before it began its climb, and that it missed colliding with one of the aircraft on the taxiway by 14 ft.
The NTSB determined the probable cause was the Air Canada flight crew's confusion of the runway with the parallel taxiway, with contributing causes including the crew's failure to use the instrument landing system (ILS), as well as pilot fatigue. A retired pilot stated the runway confusion that almost happened "probably came close to the greatest aviation disaster in history" as five airplanes and potentially over 1,000 passengers were at imminent risk of a disaster greater than the Tenerife airport disaster.
Incident
At 11:46 p.m. local time, Air Canada Flight 759 (AC 759), carrying 135 passengers and 5 crew members, was cleared to land on Runway 28R. The adjacent Runway 28L had been closed at 10 p.m. local time and its lights were off, except for a 20.5 ft lighted flashing "X" at the eastern runway threshold. The captain was flying the aircraft and the first officer was monitoring. The two pilots of AC 759 acknowledged that they mistook runway 28R for 28L and therefore lined up for landing on the parallel taxiway C, even though runways and taxiways are lit with different colours and intensities. Preliminary post-event investigation results noted that Runway 28R and Taxiway C were lit on default settings (in different colours), and the automatic terminal information service broadcast information was current and advised that 28L was closed and unlit. According to preliminary Transportation Board investigation results, as the weather was clear, the pilots of AC 759 were not required to utilize the instrument landing system and relied instead on a visual approach, as typical for the prevailing conditions.
On Taxiway C, four airplanes were queueing for takeoff, three from United Airlines and one from Philippine Airlines. At 11:55:46 p.m. local time, upon spotting aircraft lights approximately 0.7 mi from the runway, the pilot of AC 759 asked the tower if he was clear to land on 28R, to which the air traffic controller responded at 11:55:56 p.m., "There's no one on 28R but you," when AC 759 was approximately 0.3 mi from the runway threshold. The AC 759 pilots "did not recall seeing aircraft on Taxiway C, but something did not look right to them", according to a post-incident interview summary. The pilot of United Airlines Flight 1 (UA 001), the first in line for takeoff, interrupted the radio traffic at 11:56:01 p.m. and asked "Where is this guy going? He's on the taxiway." The crew of Philippine Airlines Flight 115 (PR 115) turned on their landing lights to alert AC 759 they were lined up on the taxiway. Then the captain of AC 759 initiated a go-around, around the same time as the first officer called for a go-around. The air traffic controller ordered AC 759 to abort the landing at 11:56:10 p.m. After AC 759 acknowledged the go-around, the air traffic controller stated, "It looks like you were lined up for Charlie [Taxiway C] there." AC 759 had already started to climb before the go-around order.
Afterwards, the pilot of UA 001 radioed the tower saying, "Air Canada flew directly over us," and the air traffic controller responded, "Yeah, I saw that, guys." During the first approach, AC 759 flew for 1/4 mi over Taxiway C, descended to an altitude as low as 81 ft and approached as close as 29 ft laterally to the four airplanes waiting on Taxiway C before being ordered to abort the landing. According to the flight data recorder, the pilots advanced the thrust levers when the airplane was 85 ft above the ground. The airplane descended as low as 59 ft, approximately 2.5 seconds after the thrust levers had been advanced. There was less than 10 to 20 ft separation between the bottom of the Air Canada aircraft and the tail of the Philippine Airlines Airbus A340 aircraft, which was the second airplane on the taxiway. Following a reconstruction of events, one pilot not involved in the incident noted that had the crew waited five more seconds before pulling up, it would have collided with the third airplane on the taxiway, which was that of United Airlines Flight 863 (UAL 863).
SFO was the first airport in the United States to install an Airport Surface Surveillance Capability (ASSC) system, which should have alerted the tower of a potential conflict between runway and taxiway movements. AC 759 disappeared from the local controller's ASSC display for twelve seconds, between 11:55:52 and 11:56:04 p.m. local time (from shortly after the AC 759 pilot asked for confirmation that 28R was clear, to the time the UA 001 pilot noted that AC 759 was lined up for Taxiway C), as AC 759 was too far off-course from 28R.
AC 759 completed its go-around and landed without incident after the second approach. A single air traffic controller was monitoring ground and tower frequencies, which would typically be handled by two controllers.
Investigation and cause
Investigation
The incident was not considered reportable under then-current federal regulations. However, former NTSB chairman Jim Hall called it "the most significant near-miss we've had in this decade" and urged the NTSB to re-evaluate those reporting requirements. The United States National Transportation Safety Board (NTSB) was informed of the incident on July 9 and took the lead on the investigation with assistance from the Federal Aviation Administration (FAA). The Transportation Safety Board of Canada (TSB) served as a facilitator to convey information between Air Canada and the NTSB. TSB released preliminary information from Occurrence No. A17F0159 on July 11, 2017. NTSB assigned identification number DCA17IA148 to the incident.
A retired pilot stated that SFO requires "precision flying" as the two runways (28R and 28L) are laterally separated by 750 ft, and Taxiway C is separated from 28R by less than 500 ft. Other pilots pointed out that some airlines require all aircraft to use the instrument landing system (ILS) regardless of weather or visibility, which would have led the crew to realize that they were not lined up with runway 28R. Dave Jones, then-California Insurance Commissioner and a passenger on AC759, wrote a letter to Air Canada a week after the incident requesting their cooperation with the investigation.
Preliminary NTSB investigation results from flight data recorder telemetry, released on August 2, 2017, indicate that AC759 reached a minimum altitude of 59 ft above ground level, comparable to the 55 ft tail height of a Boeing 787-9, two of which were on Taxiway C. The cockpit voice recorder had been overwritten before the investigation was launched, as C-FKCK flew three more flights on July 8 before the NTSB was informed of the near-miss on July 9.
Text from the Wikipedia article “Air Canada Flight 759” (revision 1363685019, retrieved 2026-09-18) by its authors, under CC BY-SA 4.0. Extracted as plain text: references, tables, images and some sections are left out. Read the article
NTSB narrative
NTSB investigators traveled in support of this investigation and used data obtained from various sources to prepare this aircraft incident report.
The NTSB's full report is available at http://www.ntsb.gov/investigations/AccidentReports/Pages/AccidentReports.aspx. The Aircraft Incident Report number is NTSB/AIR-18/01.
On July 7, 2017, about 2356 Pacific daylight time, Air Canada flight 759, an Airbus A320-211, Canadian registration C-FKCK, was cleared to land on runway 28R at San Francisco International Airport, San Francisco, California, but instead lined up with parallel taxiway C. Four air carrier airplanes (a Boeing 787, an Airbus A340, another Boeing 787, and a Boeing 737) were on taxiway C awaiting clearance to take off from runway 28R. The incident airplane descended to an altitude of 100 ft above ground level and overflew the first airplane on the taxiway. The incident flight crew initiated a go-around, and the airplane reached a minimum altitude of about 60 ft and overflew the second airplane on the taxiway before starting to climb. None of the 5 flight crewmembers and 135 passengers aboard the incident airplane were injured, and the incident airplane was not damaged. The incident flight was operated by Air Canada under Title 14 Code of Federal Regulations Part 129 as an international scheduled passenger flight from Toronto/Lester B. Pearson International Airport, Toronto, Canada. An instrument flight rules flight plan had been filed. Night visual meteorological conditions prevailed at the time of the incident.
Probable cause
The flight crew's misidentification of taxiway C as the intended landing runway, which resulted from the crewmembers' lack of awareness of the parallel runway closure due to their ineffective review of notice to airmen (NOTAM) information before the flight and during the approach briefing. Contributing to the incident were (1) the flight crew's failure to tune the instrument landing system frequency for backup lateral guidance, expectation bias, fatigue due to circadian disruption and length of continued wakefulness, and breakdowns in crew resource management and (2) Air Canada's ineffective presentation of approach procedure and NOTAM information.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
Wikipedia article: Air Canada Flight 759
- Article
- Air Canada Flight 759
- Revision
- 1363685019 · 2026-07-11 · retrieved 2026-09-18
- Wikidata
- Q33025184
- Licence
- Text CC BY-SA 4.0, by the article's authors; Wikidata CC0; town positions GeoNames (CC BY 4.0)
NTSB record DCA17IA148
- Event ID
- 20170709X81141
- Case number
- DCA17IA148
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Where each value comes from
- Record
- Wikipedia article "Air Canada Flight 759" (page 54530213, revision 1363685019); merged with NTSB case DCA17IA148 (events / aircraft)
- Date
- NTSB record DCA17IA148: NTSB narrative opening date, consistent with the API date and time (local date)
- Place and country
- Wikipedia infobox: site; country from NTSB record DCA17IA148
- Map position
- NTSB record DCA17IA148: NTSB API eventLatitude/eventLongitude
- Aircraft, operator and route
- NTSB record DCA17IA148: aircraft; gaps from Wikipedia infobox: aircraft type, registration, operator, origin and destination; route airports from the linked airport articles' Wikidata codes (OurAirports)
- Operation
- NTSB record DCA17IA148: operated under Part 129: Foreign
- Fatalities
- Wikipedia: Wikipedia infobox: aircraft fatalities (the NTSB record states no total)
- Ground fatalities
- NTSB record DCA17IA148: events.inj_f_grnd
- Summary
- Wikipedia infobox: summary
Source notes (3)
- One occurrence in two sources, merged: the Wikipedia article "Air Canada Flight 759" and NTSB case DCA17IA148, matched by the same aircraft registration and date. For this US event the NTSB's values are used where the two differ; each value names its source.
- Filled from the NTSB case API where the bulk record had no value: local date, investigation status, coordinates, damage. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2017-07-08.