Antonov An-124 Loses Part, Closing Nagoya’s Runway for 50 Minutes

An Antonov Airlines An-124 cargo aircraft lost a part shortly after taking off from Chubu Centrair International Airport in Nagoya on November 10, forcing the airport’s only runway to close for 50 minutes. The jet, registration UR-82007, continued safely to Clark International Airport in the Philippines but had not flown again by the latest available account.

Image Credit to wikimedia.org

The aircraft was operating flight ADB357F when the object fell during departure. Some social-media reports described it as part of the fuselage, but no official identification or explanation for the separation was available. Antonov Airlines was contacted for more information, but no company response was included.

UR-82007 continued along its planned route and landed at Clark just under five hours after leaving Nagoya. That safe arrival stands in contrast to the immediate problem on the ground: material from an aircraft can remain hazardous even when the departing flight shows no apparent difficulty completing its journey.

Why one fallen part stopped airport operations

The Aviation Herald reported that Nagoya’s 3,500-meter Runway 18/36 was closed while crews cleared the debris. Because Chubu Centrair has a single runway, suspending operations there directly removes the airport’s ability to handle normal arrivals and departures until the surface can be inspected and released for use.

The Federal Aviation Administration defines foreign object debris as material in an inappropriate airport location that can injure personnel or damage aircraft. On a runway, even a relatively small object can threaten tires, engines or aircraft mechanisms during the high-speed takeoff and landing phases.

That is why the runway closure was necessary despite UR-82007 flying onward safely. Clearing the visible material is only part of the response; the operating surface must also be checked before subsequent aircraft movements resume. The 50-minute interruption reflects the airport-side consequence of the event, not the condition of the An-124 during its flight to Clark.

The available information does not identify which aircraft assembly lost the part, why it detached or what inspection and repair work may be underway in the Philippines. The aircraft’s lack of further flights after reaching Clark provides an operational status, but not a diagnosis.

A second An-124 incident at Nagoya

The November departure was the second Antonov Airlines An-124 incident at Nagoya in about three weeks. On October 22, another An-124, registration UR-82029, experienced a fire while arriving from Fairbanks, Alaska. Planespotters.net identified the affected component as the auxiliary power unit, while local accounts said the fire was quickly extinguished and the aircraft stopped safely at its parking position.

That earlier event closed the runway for 15 minutes. UR-82029 returned to service the following day, a markedly shorter interruption for the aircraft than the inactivity recorded for UR-82007 after its arrival at Clark.

The two events have different reported circumstances: one involved a fire during arrival, while the other involved an unidentified part falling during departure. No information connects their causes. Their common operational effect was the temporary loss of Nagoya’s sole runway while airport personnel addressed a hazard associated with a large cargo aircraft.

Antonov Airlines has six An-124s at its disposal, according to fleet data cited from Planespotters.net. Their listed average age is 36.3 years, and the 40.4-year-old UR-82007 is the oldest of the six. No cause has been established for the November part loss, however, and the available information does not connect the aircraft’s age to either Nagoya incident.

The next meaningful development will be an identification of the detached component, an explanation of how it separated, or a return-to-flight record for UR-82007. Until then, the confirmed picture remains unusually split: the heavy freighter completed its nearly five-hour flight safely, but the debris it left behind shut Nagoya’s runway for 50 minutes, and the aircraft remained inactive at Clark.

More aerospace and engineering stories, right in your MSN feed.
Follow AMI on MSN

By David Whitaker — Associate editor for AMI’s aerospace and drone systems desk, translating flight systems, aircraft programs, spaceflight, and UAV developments into accessible technical stories.

Leave a Reply