A United Airlines Boeing 777-200 taxied across an active runway at Daniel K. Inouye International Airport in Honolulu on January 23, 2023, without clearance from air traffic control, while a Kamaka Air Cessna 208B was landing on that same strip. No injuries resulted, but the close call added to a string of runway conflicts that drew national attention from federal investigators and prompted direct testimony before Congress about the persistent danger of runway incursions at busy U.S. airports.
How a Boeing 777 ended up on an occupied runway at HNL
The sequence began when United Flight 384, operating a Boeing 777-200, touched down on Runway 4R at Honolulu’s main commercial airport. After landing, the crew taxied the widebody jet across the parallel Runway 4L. At that moment, Kamaka Air Flight 145, a Cessna 208B turboprop, was on short final to land on 4L. The United crew had not received clearance to enter or cross that runway, according to the NTSB preliminary report on incident DCA23LA133.
Federal air traffic rules are explicit on this point. FAA Order JO 7110.65, the standard reference for controller procedures, requires that any aircraft receive a specific verbal clearance before entering a runway surface. A pilot who crosses without that clearance commits what the FAA classifies as a pilot deviation, a category that covers unauthorized movements on the airfield. The FAA’s own safety databases have cataloged the Honolulu event as such a deviation, aligning with the NTSB’s determination that the Boeing 777 crossed an active runway while another aircraft was landing.
Honolulu’s airport layout plays a role in how such errors occur. Runways 4R and 4L run parallel, and aircraft landing on one must cross the other to reach terminal gates on the south side of the field. The FAA publishes a hot-spot diagram for HNL that flags the intersection zone between these parallel runways as a known risk area where confusion about crossing clearances has historically led to errors. That geometry means every arrival on 4R creates a potential conflict point with traffic on 4L, and vice versa. The risk is built into the airport’s physical design, not just into any single crew’s decision-making.
In the January 2023 incident, that structural vulnerability aligned with a breakdown in cockpit discipline. The NTSB’s preliminary findings indicate that air traffic control had issued landing and taxi instructions but had not cleared United 384 to cross Runway 4L. Standard phraseology would have required a separate, explicit crossing clearance. The fact that the Boeing 777 proceeded anyway suggests either a misheard instruction, a mistaken assumption that a crossing was implied, or a lapse in monitoring the aircraft’s position relative to the runway environment.
Federal investigators and Congress focused on a pattern
The Honolulu crossing did not happen in isolation. The NTSB issued preliminary reports on multiple runway incursions from 2023, including the HNL event, signaling that the board viewed such incidents as part of a broader safety concern rather than a series of one-off mistakes. In subsequent public communications, NTSB Chair Jennifer Homendy placed the Honolulu case alongside other serious close calls to illustrate the persistence of runway-incursion risk across the national airspace system.
Homendy later told lawmakers that recent incursions underscored systemic vulnerabilities in airport surface operations, emphasizing that the absence of a collision did not mean the system was performing acceptably. Her testimony referenced the Honolulu incident as one example of how a single missed clearance or misunderstanding can quickly erode safety margins when aircraft are operating in close proximity.
The board’s broader messaging has reinforced that theme. In a separate public communication, the NTSB described how a string of runway incursions in 2023 and 2024 prompted renewed calls for technology, training, and procedural changes to reduce the likelihood of aircraft ending up on the same piece of pavement at the same time. In a June 2024 update, the agency highlighted these recent close calls as evidence that runway safety remains a high-priority issue demanding sustained attention from regulators, airlines, and airports.
The FAA’s internal safety reporting captured the same data points. Both the NTSB and the FAA recorded the same date, location, and event type for the HNL crossing, providing independent confirmation from two separate federal agencies. That dual documentation matters because it shows the event was not quietly filed away but entered the formal safety record through multiple channels. For investigators and policymakers, the consistency across databases strengthens the case that the incident should be treated as a representative example of a broader category of risk.
Homendy’s comments to Congress carried particular weight because they framed the problem as systemic rather than episodic. A single unauthorized crossing at a mid-Pacific airport might seem minor in the absence of a collision. But the NTSB’s decision to investigate and then cite the event in testimony reflected a judgment that the conditions producing such conflicts are recurring and widespread. Runway incursions have long appeared on the board’s lists of priority safety issues, and the 2023 cluster of events gave that concern fresh urgency.
Unanswered questions about the Honolulu crossing
Several pieces of evidence that would explain exactly how the unauthorized crossing happened have not appeared in publicly available records. The full air traffic control audio transcript and controller statements from the event are not part of the public NTSB docket as of the most recent available documentation. Without that audio, it is not possible to determine whether the United 384 crew misunderstood a controller instruction, anticipated a clearance that had not yet been issued, or simply lost situational awareness during the taxi.
Pilot deviation statements from the United 384 crew also have not been released in primary records. Those statements would typically describe the crew’s understanding of their clearance status at the moment they entered Runway 4L. Absent that narrative, analysts are left to infer from circumstantial evidence: the timing of radio calls described in the preliminary report, the standard operating procedures used by the airline, and the known complexity of the runway layout at HNL. Each of those factors can inform hypotheses, but they do not substitute for direct accounts from the pilots involved.
The exact separation distance between the Boeing 777 and the Kamaka Air Cessna at the closest point of conflict appears only in summary form in the preliminary report, leaving the precise margin of safety unclear. Investigators typically reconstruct these details using radar data, flight data recorders, and visual observations, but those granular measurements have not been made public. As a result, outside experts cannot definitively categorize the event’s severity beyond acknowledging that both aircraft occupied the same runway environment at overlapping times.
There are also open questions about contributing factors on the ground. The public record does not yet provide a detailed account of lighting conditions, signage visibility, or any concurrent construction that might have affected taxiway markings or pilot cues on the night of the incident. Similarly, controller workload and staffing levels in the tower at the time of the crossing have not been disclosed. Those variables matter because they can shape how quickly a controller notices a deviation and how effectively they can intervene to prevent a collision.
The hypothesis that HNL’s parallel-runway geometry creates a measurable spike in pilot-deviation probability during peak traffic banks is plausible given the airport’s hot-spot designation, but the public record does not yet contain the granular data needed to test it rigorously. Arrival rates, deviation frequencies by time of day, and controller workload metrics for Honolulu would be essential to determine whether the layout produces a disproportionate share of close calls compared with airports of similar size and complexity.
For now, the Honolulu incident stands as a vivid case study in how a single missed clearance can intersect with an inherently challenging airfield design to produce a serious runway incursion. The NTSB’s preliminary findings, subsequent public statements, and congressional testimony all point to the same conclusion: preventing similar events will require more than admonishing an individual crew. It will demand sustained attention to airport geometry, cockpit and tower communication practices, and the technological tools available to warn both pilots and controllers when an aircraft moves toward a runway it has not been cleared to enter.
More from Morning Overview
*This article was researched with the help of AI, with human editors creating the final content.
