Connect with us

Regulations & Safety

Cargo Plane Crash at Hong Kong Airport Kills Two Security Staff

Wreckage of a Boeing 747 cargo plane recovered after crash at Hong Kong Airport, with investigation underway into wet-lease operations and safety.

Published

on

Wreckage Recovered in Hong Kong After Fatal Cargo Plane Crash

In the aftermath of a tragic incident at Hong Kong International Airport, recovery teams have successfully salvaged the main wreckage of a Cargo-Aircraft that crashed into the sea. The event, which resulted in the deaths of two ground personnel, has initiated a comprehensive international investigation. The recovery of the aircraft’s fuselage is a critical milestone, providing investigators with the physical evidence needed to piece together the final moments of the flight and determine the cause of the Accident.

The crash is a somber mark on the otherwise strong safety record of Hong Kong International Airport, one of the world’s busiest transport hubs. It represents only the second fatal incident since the airport commenced operations in 1998. As authorities from multiple nations collaborate, the air cargo industry watches closely, with particular attention on the nature of wet-lease agreements and operational safety protocols under challenging conditions. The focus now shifts from recovery to a meticulous analysis of the retrieved components, including the flight recorders, which hold key data about the aircraft’s performance and the crew’s actions.

The Incident: A Timeline of Events

The incident occurred in the early hours of Monday, October 20, 2025. At approximately 3:50 AM local time, a Boeing 747-400 freighter, operating as Emirates flight EK9788 from Dubai, was landing at Hong Kong International Airport. During the landing sequence, the aircraft veered off the runway, skidded through a perimeter fence, and ultimately plunged into the surrounding sea. The impact was catastrophic, as the plane collided with a patrol car occupied by two airport security personnel.

While the four crew members aboard the aircraft survived the crash and were subsequently hospitalized, the two individuals in the patrol car were fatally injured. The deceased were identified as a 41-year-old security officer, Mr. Ho, and a 30-year-old security supervisor, Mr. Chan. Both were employees of the Aviation Security Company Limited and were reported to be the primary breadwinners for their families, leaving behind grieving spouses and young children.

The aircraft involved was a 32-year-old Boeing Converted Freighter operated by ACT Airlines, a Turkish cargo carrier. The flight was conducted under a wet-lease agreement for Emirates SkyCargo. This type of arrangement means that the lessor, ACT Airlines, provides the aircraft, crew, maintenance, and insurance (ACMI) to the lessee, Emirates. At the time of the incident, the flight was not carrying any cargo. Airports officials later confirmed that weather and runway conditions met the required standards for landing.

Steven Yiu, the airport authority’s executive director for airport operations, stated that weather and runway conditions met standards at the time of the crash. He also noted that the plane is not supposed to turn towards the sea.

Recovery and Investigation

The salvage operation began almost immediately, with the north runway of the airport being temporarily closed. A significant breakthrough occurred on Friday, October 24, 2025, when teams recovered the aircraft’s tail section along with the crucial flight data recorder (FDR) and cockpit voice recorder (CVR). These “black boxes” are vital for any air accident investigation, as they contain detailed information about the flight’s parameters and audio from the cockpit.

The operation culminated on Sunday, October 26, 2025, with the recovery of the main fuselage from the water. This complex and challenging task marks a pivotal point in the investigation, allowing experts to conduct a thorough physical examination of the aircraft’s structure and systems. The Hong Kong Air Accident Investigation Authority (AAIA) is leading the inquiry, with support from international bodies. Representatives from the U.S. National Transportation Safety Board (NTSB), Turkey’s Transport Safety Investigation Center, and the aircraft Manufacturers, Boeing, are all assisting in the process.

With the wreckage and flight recorders secured, the investigation now enters a new phase of detailed analysis. The data from the recorders is undergoing preliminary examination, and a preliminary report from the AAIA is expected within a month. The findings will be scrutinized by the aviation industry to understand the contributing factors and implement any necessary changes to prevent a recurrence. The incident also brings wet-leasing practices under review, as the investigation will likely delve into the operational and oversight responsibilities shared between the aircraft operator and the lessee.

Conclusion: The Path Forward

The successful recovery of the Boeing 747 wreckage from the waters off Hong Kong International Airport closes a difficult chapter of search and salvage, but opens a critical one of investigation and analysis. The human cost of this tragedy, with the loss of two dedicated ground staff, underscores the imperative for a thorough and transparent inquiry. The collaborative effort between authorities from Hong Kong, the United States, and Turkey highlights the global nature of aviation safety and the shared commitment to understanding the causes of such incidents.

As investigators analyze the flight recorders and examine the physical evidence, the aviation community awaits the findings that will emerge. The preliminary report will provide the first official insights into the sequence of events that led to the crash. Beyond determining the cause, the outcome of this investigation will have broader implications, potentially influencing safety protocols, runway management, and the regulatory framework surrounding wet-lease operations in the global air cargo sector. The ultimate goal is to learn from this tragic event to enhance the safety of air travel for everyone.

FAQ

Question: What happened at Hong Kong International Airport?
Answer: On October 20, 2025, a Boeing 747 cargo plane operated by ACT Airlines veered off the runway upon landing, crashing into the sea and hitting a patrol car. The two occupants of the car, both airport security staff, were killed.

Question: Who was operating the aircraft?
Answer: The aircraft was operated by ACT Airlines, a Turkish cargo carrier. It was flying on behalf of Emirates SkyCargo under a wet-lease agreement, where ACT Airlines provided the aircraft, crew, maintenance, and insurance.

Question: What is the current status of the investigation?
Answer: The main wreckage, flight data recorder, and cockpit voice recorder have all been recovered. The Hong Kong Air Accident Investigation Authority (AAIA) is leading the investigation with international assistance, and a preliminary report is expected within a month.

Sources

Photo Credit: X

Continue Reading
Click to comment

Leave a Reply

Regulations & Safety

FAA Mandates Inspections for Converted Boeing 747-400 Freighters Over Fire Risk

FAA requires immediate inspections on Boeing 747-400 freighters converted by Israel Aerospace Industries due to fire hazards from oxygen hose and wiring issues.

Published

on

This article is based on an official directive from the Federal Aviation Administration (FAA) and related industry data.

FAA Mandates Immediate Inspections for Converted Boeing 747-400 Freighters Over Fire Risk

The Federal Aviation Administration (FAA) has issued an immediate Airworthiness Directive (AD 2026-08-06) for a specific subset of converted Boeing 747-400 freighters due to a severe fire hazard. Published on April 22, 2026, the rule mandates inspections prior to any subsequent flights after its effective date of May 7, 2026.

The directive specifically targets passenger aircraft converted to freighters by Israel Aerospace Industries (IAI). Factory-built Boeing 747-400F aircraft are not affected by this mandate. According to the FAA document, the issue stems from a ruptured crew oxygen hose and electrical arcing caused by chafing against an adjacent cargo-aircraft loading system wire harness.

Due to the severe risk of fire and the potential loss of crew oxygen supply, the FAA bypassed standard public comment periods to adopt this emergency mandate, which was originally identified by Israeli aviation authorities.

The Root Cause and Safety Risks

The safety concern was initially flagged by the Civil Aviation Authority of Israel (CAAI), the primary aviation authority overseeing IAI’s conversion programs. Maintenance crews discovered a ruptured flexible crew oxygen bottle hose (Boeing P/N 96431-2) alongside heat and arcing damage on an adjacent ANCRA Cargo Loading System wire harness (P/N W9914-301-12) near station (STA) 680 of the aircraft.

The CAAI determined that incorrect installation during the passenger-to-freighter conversion process led to the oxygen hose chafing against the wire harness.

Immediate Fire Hazard

The combination of a leaking oxygen supply line and electrical arcing presents a critical safety threat. If left unaddressed, sparks from the chafed wiring could ignite in the oxygen-rich environment. This creates a severe fire hazard while simultaneously depriving the flight crew of their emergency oxygen supply.

Regulatory Action and Compliance Requirements

The FAA’s April 2026 directive serves as the U.S. regulatory adoption of the CAAI’s Emergency Airworthiness Directive (AD ISR I-35-26-01-01), which was issued on January 1, 2026. Operators of the affected aircraft must conduct detailed visual inspections to check for wear, chafing, or arcing damage.

Furthermore, mechanics are required to verify a minimum clearance of two inches between the crew oxygen bottle flexible hose and adjacent wire harnesses, in accordance with Israel Aerospace Industries Ltd. Service Bulletin 366-35-157, dated January 2026.

Accelerated Timeline

Due to the severity of the risk, the FAA bypassed the standard Notice of Proposed Rulemaking (NPRM). The agency requires that inspections and necessary repairs be completed on a highly accelerated schedule.

…before further flight…

According to the FAA directive, this strict compliance window takes effect immediately following the May 7, 2026, effective date. The FAA is allowing a single special ferry flight to a maintenance facility, provided a preliminary check shows no existing signs of wear or chafing. Retroactive public comments on the rule will be accepted until June 8, 2026.

Fleet Implications and Industry Impact

It is crucial to note that this directive does not affect factory-built Boeing 747-400F aircraft. It is strictly isolated to airframes converted under FAA Supplemental Type Certificates (STC) ST01676SE or ST01706SE, known as the IAI/Bedek Special Freighter program.

Industry estimates indicate that approximately 29 Boeing 747-400s were converted under this specific program. While the fleet size is relatively small, these aircraft are operated by several global airlines and leasing companies. Known operators include Atlas Air, One Air (UK), Aerotranscargo, Terra Avia, ROMCargo Airlines, and Saudia Cargo.

AirPro News analysis

At AirPro News, we assess that while the immediate compliance mandate will cause temporary groundings for the affected operators, the long-term supply-chain disruption will likely be minimal. Aviation maintenance data suggests that the required physical fix, adjusting the clearance to the mandated two inches and replacing any damaged hoses or wires, is a straightforward procedure.

Furthermore, this incident highlights the efficacy of the global aviation safety network. A localized maintenance discovery in Israel swiftly translated into a worldwide protective mandate, demonstrating how international regulatory bodies collaborate to protect flight crews and the public.

Frequently Asked Questions (FAQ)

  • Are all Boeing 747-400 freighters affected? No. Only passenger aircraft converted to freighters by Israel Aerospace Industries (IAI) under specific STCs are affected. Factory-built freighters are exempt.
  • What is the deadline for compliance? Operators must comply before further flight after the directive’s effective date of May 7, 2026.
  • What exactly needs to be fixed? Mechanics must inspect for chafing and ensure a minimum clearance of two inches between the crew oxygen hose and the cargo loading system wire harness.

Sources: Federal Aviation Administration (FAA) Document Number 2026-07808

Photo Credit: Rob Finlayson

Continue Reading

Regulations & Safety

SWISS A330 Engine Fire Triggers Emergency Evacuation in Delhi

SWISS flight LX 147 aborted takeoff at Delhi after left engine fire. Six passengers injured during evacuation; runway briefly closed.

Published

on

This article summarizes reporting by Times of India and Saurabh Sinha.

SWISS A330 Evacuated in Delhi Following Engine Fire

A SWISS International Air Lines flight bound for Zurich was forced to abort its takeoff and evacuate passengers on the runway at Delhi’s Indira Gandhi International Airport (IGIA) early Sunday morning following an engine fire. According to reporting by the Times of India and journalist Saurabh Sinha, the incident resulted in the hospitalization of six passengers who sustained injuries during the emergency evacuation.

The aircraft, a widebody Airbus A330, experienced a severe failure in its number one engine during the takeoff roll, prompting the flight crew to initiate a high-speed rejected takeoff. As reported by the Times of India, the sudden engine issue and subsequent fire scare led to a full emergency declaration at India’s busiest aviation hub, temporarily halting operations on the affected runway.

Details of the Rejected Takeoff

Flight LX 147 was scheduled to operate a routine long-haul sector from New Delhi to Zurich on Sunday, April 26, 2026. According to the Times of India, the Airbus A330-300, registered as HB-JHK, was accelerating down Runway 28 at approximately 1:08 a.m. local time when the left engine suffered a critical malfunction.

Flight tracking data from Flightradar24, cited in the original reporting by Saurabh Sinha, indicates that the aircraft had reached a speed of 104 knots when the engine failure occurred. The flight crew immediately aborted the takeoff procedure, applying maximum braking and reverse thrust on the operational engine to bring the heavy aircraft to a safe halt on the runway before ordering an emergency evacuation.

The sudden deceleration and the presence of smoke and fire on the left side of the aircraft created a highly stressful environment for the occupants. The Times of India reports that there were 232 passengers on board the flight, including four infants, alongside the operating flight crew.

Emergency Evacuation and Passenger Injuries

With smoke and fire reported near the left engine, the captain ordered an immediate evacuation. The crew deployed the aircraft’s emergency escape slides to facilitate a rapid egress.

During the high-stakes evacuation, several occupants sustained injuries. According to Saurabh Sinha’s reporting, six passengers were transported to Medanta Hospital for medical evaluation and treatment. Injuries during slide evacuations are common, often resulting from the steep angle of descent and passengers colliding at the bottom of the slide.

In a public statement released following the incident and quoted by the Times of India, the airline confirmed the sequence of events and the crew’s decision-making process.

“The crew rejected the takeoff and, following an assessment of the situation, decided as a precaution to evacuate the aircraft,” SWISS stated.

The airline further noted that local teams were immediately deployed to assist stranded passengers. SWISS confirmed that they were working intensively to arrange hotel accommodations and rebooking options for those affected by the aborted flight. Furthermore, the airline announced that technical specialists would be dispatched to Delhi to inspect the damaged Airbus A330 and investigate the root cause of the engine failure.

Airport Response and Operational Impact

The aborted takeoff triggered an immediate and massive response from the airport’s rescue and firefighting services. A full emergency was declared at IGIA, with multiple fire tenders dispatched to Runway 28 to secure the aircraft, extinguish any remaining fire, and assist with the passenger evacuation process.

According to supplementary reporting by The Tribune, the fire department was alerted to a full hydraulic emergency, prompting a rapid deployment of emergency vehicles to the tarmac. The Times of India noted that Runway 28 was temporarily closed to allow emergency crews to manage the scene, treat the injured, and safely tow the disabled Airbus A330 from the active runway area.

Despite the closure of Runway 28, Delhi Airport officials released a statement confirming that overall airport operations remained largely unaffected, with air traffic being routed to the airport’s other available runways.

AirPro News analysis

We note that high-speed rejected takeoffs (RTOs) are among the most critical and demanding maneuvers in commercial aviation. At 104 knots, the SWISS Airbus A330 was traveling at a significant velocity, though we assess it was likely still below V1, the critical decision speed at which a takeoff can no longer be safely aborted. The successful deceleration of the heavy widebody aircraft underscores the rigorous simulator training flight crews undergo for engine-out scenarios during the takeoff roll.

Evacuation injuries, such as the six hospitalizations reported in this incident, are unfortunately a standard risk when deploying emergency slides. The steep angle of widebody aircraft slides, combined with the urgency and panic of a fire-related evacuation, frequently results in minor to moderate injuries. However, we believe the swift and decisive actions of the SWISS flight crew undoubtedly prevented a more severe outcome by ensuring all 232 passengers exited the potentially compromised airframe within the mandated 90-second safety margin.

Furthermore, the dispatch of SWISS technical specialists to Delhi highlights the seriousness of uncontained or fire-producing engine failures. We expect investigators will likely focus on the engine’s maintenance history, potential foreign object debris (FOD) ingestion, and the performance of the aircraft’s internal fire suppression systems.

Frequently Asked Questions

What flight was involved in the Delhi airport incident?
The incident involved SWISS International Air Lines flight LX 147, which was operating a scheduled passenger service from New Delhi (DEL) to Zurich (ZRH) on April 26, 2026.

What caused the emergency evacuation?
The Airbus A330 experienced a severe engine failure and subsequent fire on its number one (left) engine during the takeoff roll, prompting the crew to abort the takeoff and evacuate the aircraft.

How fast was the aircraft traveling when the takeoff was aborted?
According to flight tracking data cited by the Times of India, the aircraft had reached a speed of 104 knots when the engine failure occurred.

Were there any injuries during the incident?
Yes. According to reporting by the Times of India, six passengers were hospitalized with injuries sustained during the emergency slide evacuation.

Did the incident close Delhi Airport?
While Runway 28 was closed to handle the emergency and remove the disabled aircraft, Delhi Airport officials stated that overall airport operations remained unaffected.

Sources

Sources: Times of India

Photo Credit: X

Continue Reading

Regulations & Safety

Florida Law Limits Use of ADS-B Data for Airport Fees

Florida’s Senate Bill 422 bans airports from using ADS-B data to charge fees to general aviation pilots, effective July 2026.

Published

on

This article features original AirPro News reporting and analysis based on primary legislative documents.

Florida Governor Ron DeSantis has officially signed Senate Bill 422 into law, establishing new restrictions on how airports within the state can utilize Automatic Dependent Surveillance-Broadcast (ADS-B) data. According to reporting by AVweb, the governor signed the legislation on April 23, 2026, preventing airports from using this safety-critical tracking information to assess and collect fees from general aviation pilots.

Taking effect on July 1, 2026, we view this measure as a major legislative win for aviation privacy and general aviation advocates. By prohibiting the use of ADS-B data as an automated billing mechanism, Florida lawmakers aim to ensure the technology remains dedicated to its primary purpose: enhancing airspace safety and situational awareness.

According to the enrolled bill text published by the Florida Legislature, the new regulations specifically target automated toll-style collections for light aircraft conducting standard operations, such as touch-and-go landings, or simply transiting local airspace.

Key Provisions of Senate Bill 422

Weight and Operational Limits

The protections outlined in SB 422 are specifically tailored to general aviation. The legislative text restricts ADS-B fee collection for aircraft with a gross weight of 12,499 pounds or less. Furthermore, these protections apply to aircraft operating under standard Federal Aviation Administration (FAA) rules, ensuring that private pilots and small flight schools are shielded from automated tracking fees.

Restricted Fee Scenarios

The legislation explicitly outlines the circumstances under which airports are barred from monetizing ADS-B data. Whether the data originates from ADS-B In or ADS-B Out systems, airports cannot use it to calculate, generate, or collect charges from aircraft owners or operators in two specific scenarios.

First, the prohibition applies when a fee would be assessed for a departure or a landing. This explicitly includes touch-and-go landings, which are a fundamental component of flight training. Second, airports cannot charge fees based simply on an aircraft entering a specified radius of the facility’s airspace.

“An airport may not use information broadcast or collected by automatic dependent surveillance-broadcast systems… as a means for calculating, generating, and collecting fees from aircraft owners or operators who operate aircraft within the geographic boundaries of this state,”

the enrolled bill states.

The Broader Push for Aviation Privacy

AirPro News analysis

In our assessment, the enactment of SB 422 in Florida highlights a growing national consensus against the monetization of aviation safety data. ADS-B technology was mandated by the FAA to modernize the national airspace system, providing air traffic controllers and pilots with highly accurate GPS-based positioning to prevent midair collisions. We believe it was never intended to function as a digital cash register for local airport authorities.

Florida’s legislative action aligns with broader industry efforts to protect pilot privacy. In May 2025, Montana became the first state to ban the collection of ADS-B-based fees from most general aviation pilots, according to reporting by GlobalAir.com. Meanwhile, at the federal level, the proposed Pilot and Aircraft Privacy Act (PAPA) has been gaining momentum in Congress. As noted by GlobalAir.com, that federal legislation seeks to prohibit the use of aircraft identification data for profit without explicit permission from the owner or operator.

Aviation advocacy groups have consistently argued that using ADS-B for billing purposes could create perverse incentives, potentially discouraging pilots from utilizing the safety technology to its fullest extent. By passing SB 422, we observe that Florida has reinforced the principle that safety systems should remain strictly focused on safety.

Frequently Asked Questions (FAQ)

What is ADS-B?

Automatic Dependent Surveillance-Broadcast (ADS-B) is an advanced aviation surveillance technology. According to the Florida bill text, it combines an aircraft’s positioning source, avionics, and ground infrastructure to broadcast data such as GPS location, altitude, and ground speed to air traffic control and other aircraft.

When does the new Florida law take effect?

Senate Bill 422 officially takes effect on July 1, 2026.

Which aircraft are protected under SB 422?

The law applies to aircraft with a gross weight of 12,499 pounds or less operating under FAA rules.

Sources

Photo Credit: Miami Airport

Continue Reading
Every coffee directly supports the work behind the headlines.

Support AirPro News!

Advertisement

Follow Us

newsletter

Latest

Categories

Tags

Every coffee directly supports the work behind the headlines.

Support AirPro News!

Popular News