Air Canada Flight 759

Last updated

Air Canada Flight 759
Airbus A320-211 Air Canada C-FKCK 18 November 2019.jpg
C-FKCK, the aircraft involved in the near-miss, in November 2019
Incident
DateJuly 7, 2017 (2017-07-07)
SummaryNear collision on final approach at night
Site San Francisco International Airport, California, United States
37°36′58″N122°21′34″W / 37.61611°N 122.35944°W / 37.61611; -122.35944
Aircraft
Aircraft type Airbus A320-211
Operator Air Canada
IATA flight No.AC759
ICAO flight No.ACA759
Call signAIR CANADA 759
Registration C-FKCK
Flight origin Toronto Pearson International Airport, Mississauga, Ontario, Canada
Destination San Francisco International Airport, San Francisco, California, United States
Occupants140
Passengers135
Crew5
Fatalities0
Injuries0
Survivors140

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).

Contents

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.

Incident

Diagram of Runway 28R and Taxiway C at SFO. AC759 mistakenly lined up to land on Taxiway C, shown with the dotted blue line, instead of Runway 28R, shown with the dashed white line, before being ordered to abort the landing. AC759 SFO.svg
Diagram of Runway 28R and Taxiway C at SFO. AC759 mistakenly lined up to land on Taxiway C, shown with the dotted blue line, instead of Runway 28R, shown with the dashed white line, before being ordered to abort the landing.

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]

Afterwards, the pilot of UA001 radioed the tower saying, "Air Canada flew directly over us," and the air traffic controller responded, "Yeah, I saw that, guys." [1] During the first approach, AC759 flew for 1⁄4 mile (400 m) over Taxiway C, descended to an altitude as low as 81 feet (25 m) and approached as close as 29 feet (8.8 m) laterally to the four airplanes waiting on Taxiway C before being ordered to abort the landing. [11] [14] [15] According to the flight data recorder, the pilots advanced the thrust levers when the airplane was 85 feet (26 m) above the ground. The airplane descended as low as 59 feet (18 m), approximately 2.5 seconds after the thrust levers had been advanced. [7] 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 (UAL 863) on the taxiway. [15] There was also less than 10 to 20 feet (3 to 6 m) separation between the bottom of the Air Canada aircraft and the tail of the Philippine Airlines A340. [16]

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]

Aircraft

The aircraft flying AC759 that night was C-FKCK, an Airbus A320-200. [11] [18] The aircraft was 24.5 years old on the day of the incident, first flying in December 1992.[ citation needed ]

N29961 Boeing 787-9 United (33239793633).jpg
N29961, the Boeing 787-9 involved as UA Flight 1
RP-C3441 NGO 2017.jpg
RP-C3441, the Airbus A340-300 involved as PR Flight 115
N13954 - Boeing 787-9 Dreamliner - United Airlines Los Angeles International - October 3, 2015.jpg
N13954, the Boeing 787-9 involved as UA Flight 863
N62895 United Airlines Boeing 737-924(ER) March 8, 2017 Tomas Del Coro.jpg
N62895, the Boeing 737-900ER involved as UA Flight 1118
Aircraft and flights involved in the incident [15] [19]
AirlineFlight #AircraftCapacity Registration OriginDestination
Air Canada ACA 759 Airbus A320-200 146C-FKCK Toronto San Francisco
United Airlines UAL 1 Boeing 787-9 252N29961San Francisco Singapore
Philippine Airlines PAL 115 Airbus A340-300 254RP-C3441 Manila
United AirlinesUAL 863Boeing 787-9252N13954 Sydney
United AirlinesUAL 1118 Boeing 737-900ER 179N62895 Cancún

Investigation

The incident was not considered reportable under then-current federal regulations, [20] 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. [21] 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. [22]

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). [23] 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] [24] 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. [21]

Final stages

In a September 25, 2018, board meeting, the NTSB cited as probable cause the pilots mistaking taxiway C for runway 28R due to overlooking the closure of runway 28L in the NOTAM report. Contributing factors included not taking advantage of the ILS, which was not in use by the flight crew, in the flight management system (FMS) visual approach; and pilot fatigue. The crew's body clock was at the Toronto 03:00 Eastern Time: the first officer had no significant rest for 12 h, and the captain for 19 h – he would not have been able to fly under US pilot fatigue rules. Transport Canada planned to bring its pilot rest rules in line with international standards later in 2018. [25] New regulations were announced in December 2018, closer to international standards but criticized as substandard by the Air Canada Pilots Association. [26]

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. [25]

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. [25]

The NTSB published their final report in September 2018; five recommendations were made. [16]

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. [27]

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). [28] [29]

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". [30]

Aftermath

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". [31]

See also

Related Research Articles

<span class="mw-page-title-main">San Francisco International Airport</span> Airport in San Mateo County, California, United States

San Francisco International Airport is the primary international airport serving the San Francisco Bay Area in the U.S. state of California. It is located in an unincorporated area of San Mateo County, and is about 12 miles southeast of San Francisco.

<span class="mw-page-title-main">Santa Barbara Municipal Airport</span> Municipal airport in Goleta, California, United States

Santa Barbara Municipal Airport is 7 miles west of downtown Santa Barbara, California, United States. The airfield covers 948 acres (384 ha) of land and has three runways.

<span class="mw-page-title-main">1991 Los Angeles runway collision</span> 1991 runway collision between two airplanes

On the evening of Friday, February 1, 1991, USAir Flight 1493, a Boeing 737-300, collided with SkyWest Airlines Flight 5569, a Fairchild Swearingen Metroliner turboprop aircraft, upon landing at Los Angeles International Airport (LAX). As Flight 1493 was on final approach, the local controller was distracted, though air traffic was not heavy at LAX, by a series of abnormalities, including a misplaced flight progress strip and an aircraft that had inadvertently switched off the tower frequency. The SkyWest flight was told to taxi into takeoff position, while the USAir flight was landing on the same runway.

<span class="mw-page-title-main">Billings Logan International Airport</span> Public airport in Billings, Montana, United States

Billings Logan International Airport is in the western United States, two miles northwest of downtown Billings, in Yellowstone County, Montana. It is the fourth busiest airport in Montana, having been surpassed in recent years by Bozeman, Missoula, and Flathead County (Kalispell) in number of annual enplanements. Owned by the city of Billings, the airport is on top of the Rims, a 500-foot (150 m) cliff overlooking the downtown core, and covers 2,500 acres of land.

<span class="mw-page-title-main">Pan Am Flight 845</span> 1971 aviation accident in California, United States

Pan Am Flight 845 was a scheduled international passenger flight between Los Angeles and Tokyo, with an intermediate stop at San Francisco. The flight was operated by a Boeing 747 registered N747PA and named Clipper America.

<span class="mw-page-title-main">JetBlue Flight 292</span> 2005 aviation incident

JetBlue Flight 292 was a scheduled flight from Bob Hope Airport in Burbank, California, to John F. Kennedy International Airport in New York City. On September 21, 2005, Captain Scott Burke executed an emergency landing in the Airbus A320-232 at Los Angeles International Airport after the nose gear jammed in an abnormal position. No one was injured.

<span class="mw-page-title-main">Southwest Airlines Flight 1248</span> 2005 aviation accident

Southwest Airlines Flight 1248 was a scheduled passenger flight from Baltimore, Maryland, to Chicago, Illinois, continuing on to Salt Lake City, Utah, and then to Las Vegas, Nevada. On December 8, 2005, the airplane slid off a runway at Midway Airport in Chicago while landing in a snowstorm and crashed into automobile traffic, killing a six-year-old boy.

<span class="mw-page-title-main">Montgomery-Gibbs Executive Airport</span> Airport in San Diego, California

Montgomery-Gibbs Executive Airport is a public airport in San Diego, California, United States, six miles (10 km) north of downtown San Diego. The airport covers 456 acres (185 ha) and has three runways, one public helipad, and two private helipads. The runways are 28R/10L and 28L/10R (parallel) and 5/23.

<span class="mw-page-title-main">Treasure Coast International Airport</span> Airport in Florida, U.S.

Treasure Coast International Airport is a public airport located three miles (5 km) northwest of the central business district of Fort Pierce, a city in St. Lucie County, Florida, United States. It is owned by the St. Lucie Board of County Commissioners.

<span class="mw-page-title-main">2007 San Francisco International Airport runway incursion</span> Aircraft incident in Northern California in 2007

The 2007 San Francisco International Airport runway incursion occurred around 1:36 p.m. PDT on May 26, 2007, when SkyWest Airlines Flight 5741, an Embraer EMB 120 Brasilia turboprop aircraft, nearly collided with Republic Airways Flight 4912, an Embraer 170 Regional Jet, at the intersection of Runways 1L and 28R at San Francisco International Airport (SFO).

<span class="mw-page-title-main">FedEx Express Flight 14</span> 1997 plane crash in Newark, New Jersey, U.S.

FedEx Express Flight 14 was a scheduled cargo flight from Singapore to Newark, New Jersey, via Malaysia, Taiwan, and Alaska. On July 31, 1997, the aircraft flying this route crashed during landing on its final segment at Newark International Airport (EWR), inverting and catching fire, injuring all five people on board.

<span class="mw-page-title-main">Japan Air Lines Flight 2</span> 1968 injury-free water landing in San Francisco Bay

Japan Air Lines Flight 2 was a scheduled passenger flight on November 22, 1968. The plane was a new Douglas DC-8-62 named Shiga (志賀), flying from Tokyo International Airport (Haneda) to San Francisco International Airport (SFO). Due to heavy fog and other factors, captain Kohei Asoh mistakenly ditched the plane near Coyote Point in the shallow waters of San Francisco Bay, two and a half miles short of the runway. All 107 people on board survived the accident without any injuries.

Aero Valley Airport is a privately owned, public use airport 3 nautical miles (5.6 km) northwest of Roanoke, in Denton County, Texas, United States.

<span class="mw-page-title-main">Continental Airlines Flight 1404</span> 2008 aviation accident

Continental Airlines Flight 1404 was a Continental Airlines domestic flight from Denver International Airport in Denver, Colorado, to George Bush Intercontinental Airport in Houston, Texas. On the evening of December 20, 2008, the flight crashed while taking off from Denver, resulting in two critical injuries, 36 noncritical injuries, and a hull loss of the Boeing 737-524 aircraft.

<span class="mw-page-title-main">1990 Wayne County Airport runway collision</span> Collision of two Northwest Airlines jetliners at Detroit Metropolitan Wayne County Airport

On December 3, 1990, two Northwest Airlines jetliners collided at Detroit Metropolitan Wayne County Airport. Flight 1482, a scheduled Douglas DC-9-14 operating from Detroit to Pittsburgh International Airport, taxied by mistake onto an active runway in dense fog and was hit by a departing Boeing 727 operating as Flight 299 to Memphis International Airport. One member of the crew and seven passengers of the DC-9 were killed.

<span class="mw-page-title-main">Continental Airlines Flight 1883</span> 2006 aviation incident

Continental Airlines Flight 1883 was a Boeing 757 that mistakenly landed on a taxiway at Newark Liberty International Airport on the evening of October 28, 2006. There were no reported injuries or damage, but the narrowly averted disaster was investigated by the National Transportation Safety Board, and caused the Federal Aviation Administration to reevaluate and modify air and ground safety procedures at and around Newark Airport.

<span class="mw-page-title-main">United Express Flight 6291</span> 1994 plane crash in Ohio, United States

United Express Flight 6291 was a regularly scheduled United Express flight from Dulles International Airport near Washington, D.C. to Port Columbus International Airport in Columbus, Ohio. It was a service operated by Atlantic Coast Airlines on behalf of United Express.

<span class="mw-page-title-main">Asiana Airlines Flight 214</span> Transpacific flight that crashed on July 6, 2013

Asiana Airlines Flight 214 was a scheduled transpacific passenger flight originating from Incheon International Airport near Seoul, South Korea. On the morning of July 6, 2013, the Boeing 777-200ER operating the flight crashed on final approach into San Francisco International Airport in the United States. Of the 307 people on board, 3 died; another 187 were injured, 49 of them seriously. Among the seriously injured were four flight attendants who were thrown onto the runway while still strapped in their seats when the tail section broke off after striking the seawall short of the runway. It was the first fatal crash of a Boeing 777 since the aircraft type entered service in 1995.

<span class="mw-page-title-main">FedEx Express Flight 630</span> 2006 aviation accident

FedEx Express Flight 630 was a regular scheduled cargo flight from Seattle-Tacoma International Airport to Memphis International Airport, Memphis, Tennessee. On July 28, 2006, the McDonnell Douglas MD-10-10F operating the flight, crashed upon landing due to a landing gear failure. The main left undercarriage collapsed seven seconds after touchdown causing the MD-10 to roll off the runway out of control. The aircraft finally came to a stop near taxiway M4 and caught fire. The fire consumed the wing and port engine and the crash and evacuation left everyone onboard injured.

References

  1. 1 2 3 4 5 6 7 Gafni, Matthias (July 10, 2017). "Exclusive: SFO near miss might have triggered 'greatest aviation disaster in history'". San Jose Mercury News. Retrieved July 18, 2017.
  2. 1 2 3 4 Gafni, Matthias (July 11, 2017). "SFO near-miss: Air Canada flight got 'extremely close' to planes on taxiway, pilot on ground alerted tower, averted disaster". San Jose Mercury News. Retrieved July 18, 2017.
  3. 1 2 3 4 5 Levenson, Eric; Chan, Stella; Hassan, Carma; Ostrower, Jon (July 11, 2017). "Air Canada plane nearly lands on a crowded taxiway at San Francisco airport". CNN. Retrieved July 18, 2017.
  4. 1 2 3 4 Spurr, Ben; Howells, Laura (July 11, 2017). "'Close to the greatest aviation disaster in history:' Air Canada pilot almost lands on busy taxiway". The Star. Retrieved July 18, 2017.
  5. ↑ Dangerfield, Katie (July 11, 2017). "Air Canada plane almost lands on crowded taxiway at San Francisco airport". Global News Canada. Retrieved July 18, 2017.
  6. 1 2 3 Gafni, Matthias (July 12, 2017). "'11 seconds to impact': Expert calculates how close SFO near-miss was to disaster". San Jose Mercury News. Retrieved July 18, 2017.
  7. 1 2 3 4 5 6 7 "NTSB Issues Investigative Update on San Francisco Airport Near Miss" (Press release). National transportation Safety Board. August 2, 2017. Retrieved August 3, 2017.
  8. ↑ Croft, John (August 4, 2017). "NTSB: SFO Runway Lighting Confused Air Canada Pilots". Aviation Daily. Retrieved August 16, 2017.
  9. ↑ Rapoport, Geoff (August 5, 2017). "Air Canada Flight Misses By Four Feet". AVweb. Retrieved August 16, 2017.
  10. 1 2 3 Gafni, Matthias (July 21, 2017). "SFO close call: Air Canada pilot was not using guidance system, source says". San Jose Mercury News. Retrieved July 22, 2017.
  11. 1 2 3 4 Gafni, Matthias (July 13, 2017). "Officials: Air Canada plane flew for a quarter-mile over taxiway before anyone noticed". San Jose Mercury News. Retrieved July 18, 2017.
  12. 1 2 3 4 5 6 "Landing Approach to Taxiway at San Francisco International Airport". National Transportation Safety Board. August 2, 2017. Retrieved August 3, 2017.
  13. ↑ Tucker, Jill (August 17, 2017). "Changes made at SFO after Air Canada jet's close call". San Francisco Chronicle. Retrieved August 18, 2017.
  14. ↑ Croft, John (July 14, 2017). "TSB: Air Canada A320 Overflew Four Aircraft". Aviation Daily. Retrieved August 16, 2017.
  15. 1 2 3 4 Gafni, Matthias (July 17, 2017). "NTSB: Air Canada close-call at SFO was even worse than first reported". San Jose Mercury News. Retrieved July 18, 2017.
  16. 1 2 "Taxiway Overflight Air Canada Flight 759 Airbus A320-211, C-FKCK San Francisco, California, July 7 2017" (PDF). National Transportation Safety Board. September 25, 2018.
  17. ↑ Schofield, Adrian (January 12, 2012). "FAA Extends Surveillance System To Nine Airports". Aviation Week. Archived from the original on July 29, 2017. Retrieved July 22, 2017.
  18. 1 2 Occurrence No.: A17F0159 (Report). Transportation Safety Board of Canada, ASIS. July 11, 2017. Retrieved July 18, 2017.
  19. ↑ Air Canada A320 nearly lands on taxiway! Close Call at SFO on YouTube
  20. ↑ 49 CFR 830.5
  21. 1 2 Gafni, Matthias (August 9, 2017). "'Critical' evidence in near air-disaster at SFO erased". San Jose Mercury News. Retrieved August 16, 2017.
  22. ↑ "NTSB Identification: DCA17IA148". National Transportation Safety Board. July 2017. Retrieved July 19, 2017.
  23. ↑ Riva, Nicole (July 11, 2017). "Air Canada plane avoids disaster in San Francisco". Canadian Broadcasting Corporation . Retrieved July 18, 2017.
  24. ↑ 787 Airplane Characteristics for Airport Planning (PDF) (Report). Boeing Commercial Airplanes. December 2015. Retrieved August 3, 2017. Document Number D6-58333, Revision L
  25. 1 2 3 Ghim-Lay Yeo (September 25, 2018). "Pilot error behind Air Canada A320 near-miss at San Francisco". FlightGlobal .
  26. ↑ Harris, Kathleen; Thibedeau, Hannah (December 12, 2018). "'Profoundly disappointed': Pilots call new safety rules to address flight fatigue 'substandard'". CBC News . Retrieved December 19, 2018.
  27. ↑ David Koenig (October 12, 2018). "Safety officials want faster reporting of aviation incidents". The Associated Press.
  28. ↑ William Tuccio (November 8, 2018). "Opinion: When A Near-Accident Requires Deeper Investigation". Aviation Week & Space Technology .
  29. ↑ Hradecky, Simon (December 29, 2015). "Incident: Alaska B739 at Seattle on Dec 19th 2015, landed on taxiway". The Aviation Herald .
  30. ↑ Freed, Jamie (April 28, 2021). "'Bunch of garbage': Campaign to ease pilot overload from antiquated safety warnings". Reuters. Retrieved June 15, 2022.
  31. ↑ Jon Hemmerdinger (August 17, 2017). "FAA changes San Francisco landing procedures after A320 near miss". Flightglobal.

Further reading

This page is based on this Wikipedia article
Text is available under the CC BY-SA 4.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.