{"id":145237,"date":"2026-06-08T03:06:00","date_gmt":"2026-06-07T21:36:00","guid":{"rendered":"https:\/\/aviationa2z.com\/?p=145237"},"modified":"2026-06-08T02:05:04","modified_gmt":"2026-06-07T20:35:04","slug":"united-777-makes-emergency-landing-at-san-francisco","status":"publish","type":"post","link":"https:\/\/aviationa2z.com\/index.php\/2026\/06\/08\/united-777-makes-emergency-landing-at-san-francisco\/","title":{"rendered":"United 777 Pilots Makes Emergency Landing at San Francisco"},"content":{"rendered":"\n

CHICAGO-<\/strong> A United Airlines (UA)<\/a> Boeing 777-200 operating flight UA1805 from Denver International Airport (DEN) to Honolulu Daniel K. Inouye International Airport (HNL) reported a security threat over the Pacific Ocean and turned back toward California. The crew declared an emergency and diverted to San Francisco International Airport (SFO).<\/p>\n\n\n\n

The flight crew described a threat level one situation in the cabin while the aircraft was about 100 miles west of San Francisco. Before landing, the pilots dumped fuel to reduce the aircraft’s weight and then landed safely on runway 28 Left at San Francisco International Airport (SFO).<\/p>\n\n\n\n

\"United
Photo: Cl\u00e9ment Alloing<\/figcaption><\/figure>\n\n\n\n

United 777 Returns After Cabin Security Threat<\/h2>\n\n\n\n

United Airlines flight UA1805 departed Denver for Honolulu as a routine long-haul Pacific service. The aircraft involved was a Boeing 777-200<\/a>, registration N210UA<\/strong>.<\/p>\n\n\n\n

About 100 miles west of San Francisco, the flight crew contacted air traffic control and reported what they described as a security level one situation in the cabin. The pilots confirmed that the cockpit was secure and that they were working with the flight attendants to understand the situation.<\/p>\n\n\n\n

Roughly ten minutes later, the crew declared an emergency. They confirmed the threat level remained at one and requested a return to San Francisco<\/a> rather than continuing across the Pacific to Hawaii.<\/p>\n\n\n\n

\"United
Photo: Cado Photo<\/figcaption><\/figure>\n\n\n\n

Cockpit and Cabin Status During the Event<\/h2>\n\n\n\n

Throughout the communications, the flight crew maintained that the cockpit was secure. When controllers asked whether the security threat itself was contained, the crew confirmed it was.<\/p>\n\n\n\n

Controllers later relayed a request from supervisors to verify the passenger’s condition. The crew confirmed the passenger<\/a> was not physically restrained but was compliant. The flight reported 360 persons on board.<\/p>\n\n\n\n

Air traffic control also asked the crew to forward specific details of the disruption, including whether the passenger had become physical so that the information could be passed to the relevant authorities on the ground.<\/p>\n\n\n\n

\"United
Photo: Cl\u00e9ment Alloing<\/figcaption><\/figure>\n\n\n\n

Fuel Dump and Controlled Descent<\/h2>\n\n\n\n

Because the Boeing 777-200<\/a> had departed with a heavy fuel load for the long Pacific crossing, the crew needed to reduce weight before landing. The pilots advised controllers they would dump fuel for several minutes.<\/p>\n\n\n\n

Controllers cleared the aircraft to dump fuel at the crew’s discretion and issued a box pattern to keep the aircraft clear of other traffic for about ten minutes.<\/p>\n\n\n\n

Broadcasts were sent to nearby aircraft warning of fuel dumping in progress, first near flight level 370 and later while descending from flight level 340 to flight level 270, northwest of the area.<\/p>\n\n\n\n

\n