Landing In San Francisco Airport

[Charo Lemucchi]

On July 7, 2017, an Airbus A320-211 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 fueled 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.[1][2][3][4] The subsequent investigation by the National Transportation Safety Board (NTSB) determined that the Air Canada airplane descended to 59 feet (18 m) above the ground before it began its climb, and that it missed colliding with one of the aircraft on the taxiway by 14 feet (4.3 m).

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"[2][3][4][5] as five airplanes and potentially over 1,000 passengers were at imminent risk of a disaster greater than the Tenerife airport disaster.

At 11:46 p.m. local time, Air Canada Flight 759, carrying 135 passengers and 5 crew members,[4] 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,[6] except for a 20.5-foot-wide (6.2 m) lighted flashing "X" at the eastern runway threshold.[7] The captain was flying the aircraft and the first officer was monitoring.[7] The two pilots of AC759 acknowledged that they mistook runway 28R for 28L and therefore lined up for landing on the parallel taxiway C,[2][7][8][9] even though runways and taxiways are lit with different colors and intensities.[6] Preliminary post-event investigation results noted that Runway 28R and Taxiway C were lit on default settings (in different colors), and the automatic terminal information service broadcast information was current and advised that 28L was closed and unlit.[7] According to preliminary Transportation Board investigation results, as the weather was clear, the pilots of AC759 were not required to utilize the instrument landing system and relied instead on a visual approach, as typical for the prevailing conditions.[10]

Taxiway C contained four airplanes, three from United Airlines and one from Philippine Airlines, queueing for takeoff.[1] At 11:55:46 p.m. local time, upon spotting aircraft lights approximately 0.7 miles (1.1 km) from the runway, the AC759 pilot 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,"[1][3][11] when AC759 was approximately 0.3 miles (500 m) from the runway threshold.[12] The AC759 pilots "did not recall seeing aircraft on Taxiway C, but something did not look right to them" according to a post-incident interview summary.[7] The crew of Philippine Airlines 115 (PR115) turned on their landing lights to alert AC759 they were lined up on the taxiway.[13][12] The pilot of United Airlines 1 (UA001), 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."[1][3] The air traffic controller then ordered AC759 to abort the landing at 11:56:10 p.m. After AC759 acknowledged the go-around, the air traffic controller stated, "It looks like you were lined up for Charlie [Taxiway C] there."[1][3] AC759 had already started to climb before the go-around order.[12]

SFO was the first airport in the United States to install an Airport Surface Surveillance Capability (ASSC) system,[17] which should have alerted the tower of a potential conflict between runway and taxiway movements.[10] AC759 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 AC759 pilot asked for confirmation that 28R was clear, to the time the UA001 pilot noted that AC759 was lined up for Taxiway C), as AC759 was too far off-course from 28R.[12]

AC759 completed its go-around and landed without incident after the second approach.[1] A single air traffic controller was monitoring ground and tower frequencies, which would typically be handled by two controllers.[10][12]

The incident was not considered reportable under then-current federal regulations,[21] but 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.[22] 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.[4] TSB released preliminary information from Occurrence No. A17F0159 on July 11, 2017.[11][18] NTSB assigned identification number DCA17IA148 to the incident.[23]

A retired pilot stated that SFO requires "precision flying" as the two runways (28R and 28L) are laterally separated by 750 feet (230 m), and Taxiway C is separated from 28R by less than 500 feet (150 m).[24] 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.[2] 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.[6][15]

Preliminary NTSB investigation results from flight data recorder telemetry, released on August 2, 2017, indicate that AC759 reached a minimum altitude of 59 feet (18 m) above ground level, comparable to the 55 ft 10 in (17.02 m) tail height of a Boeing 787-9, two of which were on Taxiway C.[7][25] The cockpit voice recorder had been overwritten before the investigation was launched,[12] as C-FKCK flew three more flights on July 8 before the NTSB was informed of the near-miss on July 9.[22]

The Federal Aviation Administration (FAA) received six recommendations: identifying approaches requiring an unusual manual frequency input; displaying it noticeably on aeronautical charts; reviewing NOTAMs to prioritize and present relevant information; requiring aircraft landing in B or C airspace to alert pilots when not aligned with a runway; modifying airports to alert on collision risks and clearly showing closed runways, as construction lighting on 28L looked like ramp lighting.[26]

Air Canada is simplifying its SFO approach charts and includes SFO-specific training in aircraft simulators, trains its staff to reduce expectation bias, and will retrofit new aircraft like the Airbus A220 and Boeing 737 Max with dual head-up displays to enhance situational awareness in low-visibility, high-risk approaches.[26]

As the pilots were slow to report the incident, the airplane had made another flight and the cockpit voice recording was recorded over. The NTSB has stated that it wants faster incident reporting and considers recommending capturing the last 25 hours, an increase from two hours.[28]

A former NTSB investigator observed deficiencies in the investigation, criticizing the board for avoiding introspection and indicating that it is more reactive than proactive.The report faults Air Canada for reporting too late and erasing the voice record, but notes that the NTSB only requires notification when an aircraft lands or departs on a taxiway, or when a collision is avoided after a runway incursion, and neither happened.It also dismisses a comparable taxiway mishap in Seattle-Tacoma by Alaska Airlines (Flight 27) in December 2015, that was still in the preliminary investigation stage at the time (NTSB assigned identification number DCA16IA036 to the incident).[29][30]

The recommendation to improve the NOTAM system led to an ICAO initiative to reform it. Robert Sumwalt, Chairman of the NTSB, described NOTAMs as "a bunch of garbage that nobody pays any attention to".[31]

Following the incident, in early August the Federal Aviation Administration modified nighttime landing procedures at SFO, forbidding visual approaches at night "when an adjacent parallel runway is closed" and replacing them with instrument approaches, either ILS or satellite-based, and requiring two air traffic controllers in the control tower "until the late-night arrival rush is over".[32]

As of December 2023, Air Canada no longer uses flight number 759 on its Toronto to San Francisco routes, instead using four different flight numbers. Flight number AC737 is used for the morning flight, flight numbers AC741 and AC743 are used for the afternoon flights, and the flight number AC745 is used for the evenings. Additionally, Air Canada uses the Airbus A320 on the morning and evening flights, while the two afternoon flights uses the Boeing 737 MAX.[33][34][35][36]

The flight lost a portion of the landing gear tire during takeoff at approximately 11:35 a.m. PT, according to the San Francisco International Airport. Footage from Cali Planes shows the tire falling off seconds after takeoff.

The tire debris landed in an employee parking lot at the airport. No one was injured and the runway was briefly closed to clear debris, the airport said. At least one car in the parking lot appeared to be damaged following the incident, footage shows.

\"We're grateful to our pilots and flight attendants for their professionalism in managing this situation,\" United said in a statement. \"We're also grateful to our teams on the ground who were waiting with a tug to move the aircraft soon after it landed and to our teams in the airport who assisted customers upon their arrival.\"

c80f0f1006