{"id":164472,"date":"2026-11-14T19:04:00","date_gmt":"2026-11-14T13:34:00","guid":{"rendered":"https:\/\/aviationa2z.com\/?p=164472"},"modified":"2026-11-14T14:34:30","modified_gmt":"2026-11-14T09:04:30","slug":"antonov-an-124-loses-fuselage-part-during-takeoff-in-japan-forcing-runway-closure","status":"publish","type":"post","link":"https:\/\/aviationa2z.com\/index.php\/2026\/11\/14\/antonov-an-124-loses-fuselage-part-during-takeoff-in-japan-forcing-runway-closure\/","title":{"rendered":"Antonov An-124 Loses Fuselage Part During Takeoff in Japan, Forcing Runway Closure"},"content":{"rendered":"\n

NAGOYA\u2013<\/strong> An Antonov Airlines An-124 cargo<\/a> aircraft lost a part during takeoff from Chubu Centrair International Airport (NGO)<\/a> on November 10, 2026, forcing airport authorities to temporarily close the runway. The aircraft, registered UR-82007, was departing for Clark International Airport (CRK) in the Philippines when the debris fell onto the runway shortly after liftoff.<\/p>\n\n\n\n

The Antonov An-124 continued its journey and landed safely in the Philippines approximately five hours later. However, the incident has drawn attention because another Antonov Airlines An-124 experienced a separate fire-related incident at the same Japanese airport less than three weeks earlier, raising questions about the operator’s recent operations at Nagoya.<\/p>\n\n\n\n

\"\"
Photo: Md Shaifuzzaman Ayon | Wikimedia Commons\nhttps:\/\/commons.wikimedia.org\/wiki\/File:UR-82008_-_Antonov_An-124-100M_Ruslan_-_Antonov_Design_Bureau_-_VGHS.jpg<\/figcaption><\/figure>\n\n\n\n

An-124 Loses Part During Takeoff in Japan<\/h2>\n\n\n\n

The aircraft was operating flight ADB357F when it departed Chubu Centrair International Airport at approximately 4:03 p.m. local time. As it climbed away from Runway 36, a part separated from the aircraft and fell onto the runway area.<\/p>\n\n\n\n

The exact identity of the missing component has not been officially established. Initial reports and footage circulated online, with some social media users suggesting that the missing section came from the aircraft’s fuselage. However, this description has not been independently confirmed.<\/p>\n\n\n\n

The aircraft continued towards Clark International Airport without returning to Nagoya. Flight-tracking information indicates that it completed the journey in approximately four hours and 50 minutes, landing safely on Runway 02.<\/p>\n\n\n\n

No injuries were reported in connection with the incident. The safe continuation of the flight allowed the aircraft to reach its destination, although the cause of the component separation remains unclear.<\/p>\n\n\n\n

\"\"
Photo: Aaron Headley | WIkimedia Commons\nhttps:\/\/commons.wikimedia.org\/wiki\/File:Aerial_photograph_of_Chubu_International_Airport_at_Nagoya_(2226165201).jpg<\/figcaption><\/figure>\n\n\n\n

Nagoya Runway Closure After Aircraft Debris<\/h2>\n\n\n\n

The incident also affected airport operations at Chubu Centrair International Airport, which operates from an artificial island in Ise Bay. Authorities temporarily closed its 3,500-meter runway for approximately 50 minutes to locate and remove the fallen debris.<\/p>\n\n\n\n

Runway inspections are important after such incidents because foreign object debris can damage aircraft during takeoff and landing. Even relatively small objects can create serious safety risks if they remain on an active runway.<\/p>\n\n\n\n

The temporary closure affected airport operations while ground personnel dealt with the debris. Reports indicated that the runway reopened after the inspection and clearance work was completed.<\/p>\n\n\n\n

The incident has been reported by several aviation news outlets, while further information about the aircraft component and the circumstances surrounding its separation remains limited. Antonov Airlines had not provided a detailed public explanation in the available reports.<\/p>\n\n\n\n

\"\"
Photo: Wikimedia Commons<\/figcaption><\/figure>\n\n\n\n

Second An-124 Incident At Nagoya Airport<\/h2>\n\n\n\n

The November 10 occurrence follows another incident involving an Antonov Airlines An-124 at Nagoya on October 22. That aircraft, registered UR-82029, experienced an auxiliary power unit (APU) fire while landing after arriving from Fairbanks International Airport (FAI) in Alaska.<\/p>\n\n\n\n

Airport personnel quickly extinguished the fire, and the aircraft stopped safely at its parking position. The runway was temporarily closed for approximately 15 minutes before normal operations resumed.<\/p>\n\n\n\n

The fire affected the aircraft’s APU, which supplies electrical power and other services when the main engines are not providing them. UR-82029 returned to service the following day, according to aircraft tracking and fleet records, Simple Flying<\/a> reported.<\/p>\n\n\n\n

Both incidents involved different An-124 aircraft, and there is no confirmed evidence linking their causes. Nevertheless, their occurrence at the same airport within three weeks has brought additional attention to Antonov Airlines’ operations in Japan.<\/p>\n\n\n\n

Antonov Airlines operates the An-124, one of the world’s largest production cargo aircraft. UR-82007 is among its older aircraft, with fleet records listing an age of approximately 40 years. <\/p>\n\n\n\n

The aircraft’s condition and the reason for the latest incident remain subjects of interest as further information becomes available.<\/p>\n\n\n\n

Stay tuned with us. Further, follow us on social media for the latest updates.<\/p>\n\n\n\n

Join us on\u00a0Telegram Group\u00a0<\/a>for the Latest Aviation Updates. Subsequently, follow us on\u00a0Google News<\/a><\/p>\n\n\n\n

\n
Canadian Authorities Seize the Russian Antonov An-124 at Toronto Airport<\/a><\/blockquote>