Regulations & Safety
Hong Kong Boeing 747 Runway Excursion Preliminary Report Released
Preliminary report details Boeing 747 freighter runway excursion at Hong Kong Airport, highlighting system failure and ongoing international investigation.
Runway Excursion in Hong Kong: Unpacking the Preliminary Report on the Boeing 747 Freighter Accident
On October 20, 2025, a routine cargo flight concluded in tragedy at Hong Kong International Airport (HKIA). An ACT Airlines Boeing 747-481 BDSF freighter, operating for Emirates SkyCargo, veered off the runway during its landing roll, resulting in the complete loss of the aircraft and the deaths of two security personnel on the ground. The incident immediately prompted an investigation by Hong Kong’s Air Accident Investigation Authority (AAIA), which has now released its preliminary report. This initial document provides the first official, fact-based look into the sequence of events that led to the incident, offering critical data without yet drawing conclusions.
Preliminary reports are a standard and vital part of any major aviation accident investigation. Their purpose is to disseminate factual information to the public and the aviation industry in a timely manner, outlining what is known in the early stages. This transparency helps to manage speculation and provides immediate, verified details from sources like the Flight Data Recorder (FDR) and Cockpit Voice Recorder (CVR). For an industry built on safety and continuous improvement, these early findings are crucial. They lay the groundwork for a deeper analysis that will eventually identify the root causes and contributing factors, leading to safety recommendations aimed at preventing future occurrences.
The accident involves a Boeing 747, an aircraft with a long and storied history. While many passenger airlines have retired the “Queen of the Skies,” hundreds have been converted into freighters, forming the backbone of the global air cargo network. This incident brings renewed focus on the operational and maintenance considerations for these aging, yet indispensable, workhorses of the sky. The investigation’s findings will be closely watched by cargo operators worldwide who rely on similar fleets.
Deconstructing the Incident: Key Findings from the AAIA Report
The preliminary report, designated PLR-2025-04, meticulously lays out the timeline and established facts of the accident involving aircraft TC-ACF. The flight, operating as UAE9788 from Dubai, landed on Runway 07L at approximately 3:52 AM local time. The crew consisted of four members, with the co-pilot designated as the Pilot Flying for the landing. The plan was for a Flap 25 landing utilizing the Autobrake 2 setting. However, the landing roll quickly deviated from the norm.
The Landing Sequence and Loss of Control
According to the report, a critical event occurred shortly after touchdown. As the co-pilot applied reverse thrust to decelerate the aircraft, an “AUTOBRAKES” message appeared on the Engine Indication and Crew Alerting System (EICAS). This alert signaled a disarming of the automated braking system. In response, the captain, who was the Pilot Monitoring, took control of the aircraft. It was at this point that the situation escalated dramatically.
Data recovered from the FDR provides a stark picture of what happened next. The Number 4 engine, instead of providing reverse thrust to slow the aircraft, accelerated to approximately 107% N1 in the forward thrust direction. This asymmetric thrust caused the aircraft to veer sharply to the left, leading it to depart the paved runway surface. Examination of the flight deck after the accident found the Autobrake selector in the “Disarmed” position and the Number 4 engine thrust lever in the full forward position, corroborating the FDR data.
The aircraft’s journey after leaving the runway was destructive. It struck and destroyed various pieces of airport equipment, including meteorological sensors and signage, before crashing through a perimeter fence. The 747 then collided with a stationary security vehicle on a perimeter road, tragically killing the two occupants, before coming to rest in the sea. The impact forces were so severe that the aircraft’s entire tail section separated from the fuselage, and the plane was declared a total loss. All four crew members survived the accident.
The aircraft veered off to the left, resulting in a runway excursion… The aircraft subsequently collided with a stationary security ground vehicle… The impact resulted in the ground vehicle entering the sea. The two security staff in the ground vehicle perished.
Pre-Existing Conditions and Aircraft History
The investigation also looks into the aircraft’s condition before the flight. The report notes that the Boeing 747 was dispatched with two pre-existing issues documented on the Minimum Equipment List (MEL). One was a resolved cockpit indication for the Hydraulic System 1 Reservoir, and the other was an inoperative thrust reverser on the Number 4 engine. The inoperative reverser is a significant detail, as the FDR data later showed that same engine producing high forward thrust during the landing roll.
The aircraft itself, TC-ACF, had a long service history. Manufactured in 1993, it first flew for All Nippon Airways (ANA) as a passenger jet and was famously adorned with a “Pokémon Jet” livery. In 2011, it was converted into a freighter, a common second life for the durable 747 airframe. This history underscores the aircraft’s age and the extensive operational life typical of cargo planes in the modern era.
The Path Forward: A Multi-faceted Investigation
With the preliminary report published, the AAIA’s investigation now enters a more analytical phase. The successful recovery of the CVR and FDR is a critical milestone, as these “black boxes” provide invaluable data on the aircraft’s performance and the crew’s actions in the final moments of the flight. The investigation is being conducted in accordance with international standards set by the International Civil Aviation Organization (ICAO).
This international cooperation is essential for a thorough and impartial investigation. Accredited representatives from several key bodies are participating. These include the Transport Safety Investigation Center (TSIC) of Turkey, representing the state where the aircraft was registered and the airline is based, and the National Transportation Safety Board (NTSB) from the United States, representing the state of the aircraft’s design and manufacture. This collaborative approach ensures that all relevant expertise is brought to bear on the case.
The investigation will now focus on several key areas. Technical analysis will delve deeper into the aircraft’s braking and engine systems, particularly the failure of the autobrake system and the anomalous behavior of the Number 4 engine. Maintenance and engineering records will be scrutinized to understand the aircraft’s service history and the handling of the inoperative thrust reverser. Furthermore, the investigation will examine operational issues, including crew qualifications and experience, as well as human factors and the airline’s Safety Management Systems. The final report will synthesize all these elements to determine the cause and contributing factors, with the ultimate goal of issuing safety recommendations to prevent a similar tragedy.
Concluding Section
The preliminary report on the runway excursion of TC-ACF provides a factual, yet sobering, account of a catastrophic landing failure. It outlines a sequence of events where a disarmed autobrake system was followed by a critical surge of forward thrust from one engine, leading to a complete loss of directional control. While it refrains from assigning cause, the report lays a clear foundation for the next phase of the investigation, highlighting the complex interplay between mechanical systems and human action in the cockpit.
As the global air cargo industry continues to rely heavily on veteran aircraft like the Boeing 747, the findings from this investigation will be of paramount importance. The final report from the AAIA will not only provide closure on this specific incident but will also likely yield crucial safety lessons for operators, maintenance providers, and manufacturers. The goal, as always in aviation, is to learn from tragedy to build a safer future, ensuring the “Queen of the Skies” can continue her vital work without repeating such a devastating event.
FAQ
Question: What is a preliminary accident report?
Answer: A preliminary report is an initial document released by an air accident investigation authority. It provides established factual information from the early stages of an investigation, such as data from flight recorders, but does not include analysis, causes, or conclusions. Its purpose is to inform the public and aviation industry in a timely manner.
Question: What happens next in the investigation?
Answer: Investigators will now conduct a detailed analysis of the collected data, including the CVR and FDR. The investigation will focus on technical systems, maintenance records, operational procedures, and human factors. The AAIA will work with international partners like the NTSB to determine the root causes and contributing factors before publishing a final report with safety recommendations.
Question: Who is investigating the accident?
Answer: The Air Accident Investigation Authority (AAIA) of Hong Kong is leading the investigation. They are supported by accredited representatives from Turkey’s Transport Safety Investigation Center (TSIC) and the United States’ National Transportation Safety Board (NTSB).
Sources: AAIA Preliminary Report PLR-2025-04
Photo Credit: SCMP
Regulations & Safety
US House Passes ALERT Act to Enhance Aviation Safety by 2031
The ALERT Act mandates collision-avoidance tech for aircraft near busy airports and military flights by 2031 after a fatal 2025 midair crash.
This article summarizes reporting by CBS News and journalists Caitlin Yilek and Olivia Rinaldi.
The U.S. House of Representatives overwhelmingly passed the Airspace Location and Enhanced Risk Transparency (ALERT) Act on Tuesday, April 14, 2026. The legislation aims to address critical safety gaps exposed by a tragic midair collision near Washington, D.C., early last year.
According to reporting by CBS News, the bill passed with a sweeping 396 to 10 vote under fast-track rules, which required a two-thirds majority for approval. The legislative push follows the deadliest U.S. plane crash in over two decades, an event that fundamentally shook the aviation industry and prompted intense scrutiny of air traffic control protocols and military flight transparency.
While the House victory marks a significant step forward, the ALERT Act faces a challenging path in the Senate. Lawmakers must now reconcile this new bill with previously stalled legislation, navigating intense pressure from victims’ families, the National Transportation Safety Board (NTSB), and the Pentagon.
The Catalyst for Legislative Action
The January 2025 Tragedy
The urgency behind the ALERT Act stems from the events of January 29, 2025. On that day, American Airlines Flight 5342 collided midair with a U.S. Army UH-60 Black Hawk helicopter near Ronald Reagan Washington National Airport (DCA). Both aircraft crashed into the Potomac River, resulting in the deaths of all 67 people aboard, according to official incident reports.
Subsequent investigations by the NTSB determined that the probable cause of the crash involved poor helicopter route design, inadequate separation requirements, and an overreliance by air traffic controllers on pilots visually spotting other aircraft. A critical technological gap was also identified, the Army helicopter was not broadcasting its location data due to military policy, and the commercial airliner lacked the technology to receive such data.
The Technology Gap: ADS-B Out vs. ADS-B In
At the time of the crash, most commercial planes were equipped with “ADS-B Out,” a system that broadcasts their location to air traffic control. However, they lacked “ADS-B In,” a collision-avoidance technology that allows pilots to receive data about nearby aircraft directly in the cockpit. NTSB Chairwoman Jennifer Homendy stated during the investigation that if Flight 5342 had been equipped with ADS-B In, the tragedy could have been prevented.
Inside the ALERT Act and the Legislative Battle
Key Provisions of H.R. 7613
Introduced by Representatives Sam Graves (R-Mo.) and Rick Larsen (D-Wash.), the ALERT Act of 2026 mandates that all aircraft flying near busy airports install safety instruments capable of receiving location data from nearby traffic. Furthermore, the bill requires military aircraft to install collision-prevention technologies by 2031. However, it includes notable exemptions for fighters, bombers, drones, and other special mission aircraft. The legislation also overhauls helicopter routes near major airports and mandates improvements to air traffic control training.
The ROTOR Act and Pentagon Pushback
The passage of the ALERT Act follows a contentious battle over a competing Senate bill known as the ROTOR Act (S. 2503). In December 2025, the Senate unanimously passed the ROTOR Act, which included stricter mandates for safety technology. However, the Pentagon reversed its initial endorsement of the bill days before a scheduled House vote.
According to legislative records, the Pentagon claimed the ROTOR Act would create significant budgetary burdens and operational security risks. Due to this opposition, the ROTOR Act failed in the House in February 2026 by a vote of 264-133, falling short of the two-thirds majority required under fast-track rules. This defeat deeply angered the families of the crash victims and set the stage for the compromise ALERT Act.
Stakeholder Reactions and Senate Outlook
Families and Safety Advocates Respond
The NTSB, which has recommended ADS-B In technology since 2008, initially criticized early drafts of the ALERT Act. However, after House lawmakers amended the bill, the agency stated that the legislation now adequately addresses its safety recommendations.
Despite the bill’s passage, families of the 67 victims remain highly critical of the compromises made. In a joint statement, the families expressed concern over the military exemptions and the readiness of the mandated systems:
“The collision prevention technologies ALERT relies upon are not market ready and could take years to become widely available.”
The families argue that allowing military flights to continue operating without broadcasting their locations during routine training leaves a dangerous loophole in the airspace.
Senate Resistance
The ALERT Act faces a tough road in the Senate. Senate Commerce Committee Leaders Ted Cruz (R-Texas) and Maria Cantwell (D-Wash.) previously released a bipartisan statement arguing the ALERT Act lacks a clear requirement for the implementation of ADS-B technology. Following the House vote, Senator Cruz reiterated that the Senate’s ROTOR Act remains the superior option, warning that without installation-ready technology, the aviation industry will likely request broad waivers, pressuring Congress to delay compliance.
AirPro News analysis
We observe that the core conflict in this legislative saga centers on balancing national security with civilian airspace safety. The Pentagon’s desire for operational secrecy and budget control directly conflicts with the NTSB’s push for total airspace transparency. The distinction between broadcasting location (ADS-B Out) and receiving it (ADS-B In) is the technical crux of this debate. Until both chambers of Congress can align on strict timelines without excessive loopholes, the aviation industry remains in a state of regulatory uncertainty. The House’s willingness to grant military exemptions through 2031 suggests that a swift compromise with the Senate, which favors the stricter ROTOR Act, will be difficult to achieve.
Frequently Asked Questions
What is the ALERT Act?
The Airspace Location and Enhanced Risk Transparency (ALERT) Act is a House-passed aviation safety bill that mandates the installation of collision-avoidance technology (ADS-B In) for aircraft operating near busy airports and overhauls helicopter routing and air traffic control training.
What is the difference between ADS-B Out and ADS-B In?
ADS-B Out is a technology that broadcasts an aircraft’s location to air traffic controllers and other receivers. ADS-B In allows an aircraft to receive that broadcasted data, giving pilots a real-time view of nearby traffic in their cockpit to prevent collisions.
Why did the previous safety bill, the ROTOR Act, fail?
The ROTOR Act failed in the House in February 2026 after the Pentagon withdrew its support, citing operational security risks and budgetary concerns regarding the strict technology mandates for military aircraft.
Sources: CBS News
Photo Credit: Envato
Regulations & Safety
Emergency Landing of Vintage Plane on Busy Phoenix Street Investigated
A Republic RC-3 Seabee made an emergency landing on a Phoenix street after engine failure; FAA and NTSB investigate with no serious injuries reported.
This article summarizes reporting by 12News and local Phoenix authorities.
A vintage amphibious aircraft made a highly unusual emergency landing on a busy central phoenix street on Sunday afternoon. According to reporting by 12News, the incident occurred near the intersection of 7th Street and Missouri Avenue, bringing traffic to a halt but miraculously resulting in no serious casualties.
Despite descending into a densely populated urban corridor, the pilot successfully avoided vehicles, pedestrians, and surrounding buildings. All three occupants on board the small aircraft walked away with only minor injuries, refusing transportation to a local hospital after being evaluated by emergency crews.
The Federal Aviation Administration (FAA) and the National Transportation Safety Board (NTSB) have launched official investigations into the mid-flight engine failure that prompted the sudden urban landing.
The Incident and Immediate Aftermath
The emergency landing took place at approximately 2:37 p.m. local time on Sunday, April 12, 2026. Flight tracking data and local reports indicate the aircraft experienced severe engine problems mid-flight, forcing the pilot to navigate the plane down into the active traffic lanes of 7th Street.
While the aircraft managed to dodge power lines and civilian vehicles, it did strike a shut-off fire hydrant during the landing sequence. According to the Phoenix Fire Department, this collision ruptured a water main, causing localized flooding that city crews were immediately dispatched to resolve.
Eyewitness and Official Reactions
First responders and bystanders alike expressed shock at the successful outcome of the forced landing in such a bustling area, which is typically crowded with cars, cyclists, and pedestrians.
Captain D.J. Lee of the Phoenix Fire Department described the landing as “100% a miracle” and “remarkable,” crediting the pilot’s extensive experience for avoiding a disaster.
Witnesses on the ground echoed this sentiment. One bystander recounted watching the plane fall in what felt like slow motion, expressing disbelief that the aircraft landed perfectly without injuring anyone on the ground. Another witness who rushed to the scene to check on the occupants noted that everyone appeared completely fine following the impact.
Aircraft Details and Pilot Experience
The aircraft involved in the incident has been identified as a privately-owned Republic RC-3 Seabee, bearing the tail number N6518K. According to historical data from the Smithsonian National Air and Space Museum, the Seabee is a four-seat amphibious plane introduced shortly after World War II, originally designed to operate on both land and water.
Local authorities reported that the flight originated from Hangar Haciendas Airpark, a private residential airpark located in Laveen, southwest of Phoenix.
Decades of Aviation Experience
Authorities highlighted that the pilot possesses 40 years of aviation experience. This extensive background was cited by emergency responders as a critical factor in the successful navigation of the vintage aircraft. The pilot’s ability to find a clear pocket on a busy city street prevented what could have been a catastrophic urban accident.
Ongoing Investigations
Following the crash, authorities closed 7th Street between Missouri Avenue and Coulter Street for several hours. This closure allowed emergency responders to secure the scene, repair the ruptured water main, and permit federal investigators to begin their preliminary assessments.
Both the FAA and the NTSB are actively probing the incident. The NTSB has indicated that a preliminary report detailing the exact circumstances of the engine failure will be released within 30 days.
AirPro News analysis
At AirPro News, we note that emergency landings in densely populated urban environments are exceedingly rare and carry a high risk of mass casualties and infrastructure damage. The successful outcome of this event underscores the paramount importance of rigorous pilot training and situational awareness. Furthermore, the involvement of a vintage post-WWII aircraft like the Republic RC-3 Seabee adds a unique layer of complexity to the upcoming NTSB investigation, as maintenance protocols and parts sourcing for such historical airframes differ significantly from modern general aviation aircraft.
Frequently Asked Questions (FAQ)
Were there any injuries in the Phoenix plane crash?
The three people on board the aircraft sustained minor injuries and were evaluated at the scene, but they refused hospital transport. No pedestrians or drivers on the ground were injured.
What type of plane landed on 7th Street?
The aircraft was a Republic RC-3 Seabee, a vintage four-seat amphibious plane introduced shortly after World War II.
What caused the emergency landing?
Preliminary reports from local authorities indicate the aircraft suffered mid-flight engine problems, forcing the pilot to make an emergency landing. The NTSB is currently investigating the exact cause.
Sources
Photo Credit: X
Regulations & Safety
FAA to Transition to Modern NOTAM Management Service on April 18
FAA will replace the legacy US NOTAM System with the NOTAM Management Service on April 18, improving safety alert infrastructure and ensuring continuous access during the switch.
This article is based on an official press release from NBAA.
The Federal Aviation Administration (FAA) is preparing to shut down its legacy US NOTAM System (USNS) and transition to the modernized NOTAM Management Service (NMS) on Saturday, April 18. The cutover marks a significant milestone in the agency’s ongoing efforts to overhaul the critical safety alert infrastructure used by pilots and air traffic controllers.
Scheduled to take place between midnight and 4 a.m. EDT, the transition is designed to be seamless for the aviation community. According to an official press release from the National Business Aviation Association (NBAA), the FAA has structured the maintenance window to ensure continuous access to vital flight information.
The upgrade follows years of development, which were heavily accelerated after a major system failure in early 2023 highlighted the fragility of the aging USNS architecture.
The April 18 Cutover Process
Maintaining Access During the Transition
During the four-hour maintenance window on April 18, any NOTAMs that were active prior to the shutdown will remain accessible through all normal distribution channels. To ensure operators receive the most accurate and timely information, the FAA recommends utilizing the FNS NOTAM search tool during this period.
Once the clock strikes 4 a.m. EDT, the new system will officially take over. From that point forward, NOTAMs obtained through the FNS page and third-party providers will be routed directly through the NMS. Despite the backend overhaul, the NBAA notes that operators should not notice any immediate differences in how they receive data.
“The cutover and transition are expected to be completely transparent to operators. We don’t anticipate hiccups.”
Addressing Past Vulnerabilities
The 2023 Outage Catalyst
While the FAA has been working to upgrade the NOTAM system for several years, the urgency of the project increased dramatically following a severe system outage in January 2023. That incident grounded morning departures for 90 minutes across the entire National Airspace System, exposing critical vulnerabilities in the legacy framework.
Launched in early 2025, the development of the NMS focused on performance-based solutions rather than just a broad technical overhaul. The FAA actively solicited user feedback to identify and resolve specific pain points within the system.
Future Capabilities and Formatting
Although NOTAMs will continue to be presented in their current, traditional format immediately following the NMS cutover, the new infrastructure lays the groundwork for future improvements. According to the NBAA, the upgraded system offers the capability to eventually present NOTAMs in a more accessible, easier-to-understand layout.
“Ultimately, these changes are for the good of the system, because we need redundancy and resiliency. That is what the NMS provides above all else.”
AirPro News analysis
The transition to the NOTAM Management Service represents a critical shift from reactive patching to proactive infrastructure management for the FAA. The January 2023 ground stop served as a wake-up call for the aviation industry, demonstrating the catastrophic potential of a single point of failure in legacy systems. By prioritizing redundancy and resiliency, the NMS should provide a much-needed safety net. Furthermore, while pilots have long complained about the cryptic and outdated formatting of NOTAMs, establishing a robust backend is the necessary first step before the FAA can roll out the modernized, plain-language layouts that the industry has been requesting for decades.
Frequently Asked Questions
When will the FAA switch to the new NOTAM system?
The transition from the USNS to the new NMS will occur on Saturday, April 18, between midnight and 4 a.m. EDT.
Will pilots lose access to NOTAMs during the transition?
No. According to the FAA, NOTAMs active prior to the maintenance window will remain available via normal distribution channels, and the agency recommends using the FNS NOTAM search tool during the cutover.
Will the format of NOTAMs change on April 18?
Not immediately. NOTAMs will continue to be presented in their current format, but the new NMS infrastructure will allow for easier-to-understand layouts in the future.
Sources
Photo Credit: NBAA
-
Electric Aircraft4 days agoElysian Aircraft Advances E9X Electric Airliner Design for Regional Flights
-
Commercial Aviation3 days agoAvion Express Cuts 15 Aircraft Amid European Aviation Cost Pressures
-
Commercial Aviation2 days agoAirbus Unveils New First Class Concept for A350-1000 Aircraft
-
MRO & Manufacturing7 days agoAero Accessories Expands MRO Services with Miami Acquisitions
-
Regulations & Safety3 days agoJet2 Contractor Seriously Injured After Fall at Manchester Airport