United Airlines Flight 803: Difference between revisions

From Wikipedia, the free encyclopedia

Content deleted Content added


 

 

Line 1: Line 1:

{{Short description|Engine failure incident involving Boeing 777}}

{{Infobox aircraft occurrence

{{Infobox aircraft occurrence

| occurrence_type = Incident

| occurrence_type = Incident


Latest revision as of 15:49, 14 December 2025

Engine failure incident involving Boeing 777

On December 13, 2025, United Airlines Flight 803 a scheduled international passenger flight from Washington Dulles International Airport to Tokyo Haneda suffered a contained engine failure shortly after takeoff, when a section of an engine cowling detached from the aircraft and caught fire.[1] The Boeing 777-224 lost power in one engine, shed debris that ignited a brush fire near a runway, and returned safely to Dulles, where it landed without injuries among the 275 passengers and 15 crew on board at 1:20 pm EST.[2]

United Airlines Flight 803 departed Washington Dulles International Airport on December 13, 2025, bound for Tokyo Haneda, operating a Boeing 777-224, registered as N78004.[3][4] The aircraft involved was delivered to United Airlines in October 1998.[3] Shortly after takeoff, at approximately 12:20 p.m. EST, the crew reported a loss of power in its left engine to air traffic control. During the event, a portion of the engine cowling separated from the aircraft and caught fire after striking the ground near a runway, igniting a small brush fire within the airport perimeter.[4] Due to the aircraft’s long-haul fuel load for the transpacific flight, the crew conducted a fuel dump over parts of northern Virginia while remaining in a holding pattern to reduce the aircraft’s landing weight.[4] The aircraft landed safely at Washington Dulles at approximately 1:20 p.m. EST. The ground fire was extinguished without further incident. No injuries were reported among the 275 passengers and 15 crew members on board.[4] The incident prompted an investigation by the Federal Aviation Administration.[2]

Leave a Comment

Your email address will not be published. Required fields are marked *

Exit mobile version