FAA Investigates American 787 Crossing That Forced Lufthansa 747 to Stop in Miami

Federal investigators are examining why an American Airlines Boeing 787-8 crossed the assigned taxi route of a Lufthansa Boeing 747-8 at Miami International Airport, forcing the Lufthansa crew to brake to a complete stop before the intersection. No injuries were reported in the November 5, 2026, conflict, and no official cause has been determined.

Lufthansa Flight LH463 was taxiing for a scheduled departure to Frankfurt am Main on Wednesday evening when American Airlines Flight AA1155, which had arrived from Philadelphia, moved across its path. The Lufthansa crew stopped sharply, checked landing-gear system indications for possible brake overheating and later departed after a delay. The Federal Aviation Administration has opened an investigation, while the two airlines are conducting internal safety reviews.

The immediate investigative task is to reconstruct the movements and communications precisely enough to separate what happened from why it happened. The American aircraft had reportedly been instructed to stop at the holding line identified as “Yankee,” allowing the Lufthansa jet to pass. The controller was also reported as saying that AA1155 had made incorrect turns earlier in its taxi. Those details establish important lines of inquiry, but investigators have not assigned responsibility or determined whether the instruction was disregarded, misunderstood or complicated by another operational factor.

Air traffic control recordings can establish the wording, timing and acknowledgment of the instructions. Investigators can compare those transmissions with the location and motion of both aircraft, looking at when each crew received a clearance, when the 787 approached or crossed the holding point and when the 747 began stopping. The timing is central because a correctly worded instruction can still fail as a safety barrier if it is heard late, interpreted differently or associated with the wrong point on a complex taxi route.

Airport surface-surveillance records provide the second major layer of reconstruction. The FAA’s Airport Surface Detection Equipment, Model X combines information from surface radar, multilateration, satellite-based surveillance, flight-plan systems and other sensors. It presents controllers with a continuously updated map of aircraft and vehicle positions on runways and taxiways, and it can issue visual and aural alerts for possible conflicts.

For investigators, those records can provide a common timeline independent of cockpit recollections. Position and identification data can be synchronized with radio transmissions to show how the spacing changed and whether the aircraft movements matched the clearances being issued. That reconstruction can also reveal when the developing conflict became visible to the controller and to each flight crew. The available information does not yet indicate whether an automated alert occurred or what role, if any, the surveillance display played in the response.

The airport environment is another part of the inquiry. Taxiway signs, painted markings and lighting must give crews an unambiguous connection between a verbal instruction and a physical stopping location. Investigators are examining those features in the affected sector of Miami International Airport, along with the clarity of the radio commands. The relevant issue is not merely whether a sign or light existed, but whether the full combination of route geometry, visual cues and controller terminology supported the intended movement at that time.

Cockpit workload after landing is also under review. AA1155 had just completed a flight from Philadelphia, putting its crew in the post-arrival phase of configuring the aircraft, following ground instructions and navigating to its destination on the airport. Investigators will need to determine whether that workload contributed to the route deviations attributed to the controller, without assuming that workload alone explains the crossing.

The Lufthansa crew’s brake and landing-gear checks show the mechanical consequence of the sharp stop even though contact was avoided. A heavy braking event can require crews to verify system indications before continuing, which is why LH463 did not simply resume taxi immediately. The later departure for Frankfurt indicates that the crew completed its checks and continued, but the delay was an operational cost of the conflict.

The FAA and National Transportation Safety Board are reported to be evaluating the control recordings and surface-surveillance data. Those records should allow investigators to test several possible contributing factors against the same timeline: the holding instruction, the American crew’s taxi path, the controller’s awareness, cockpit workload and the visibility and clarity of the designated stopping point. Until that work is complete, the confirmed safety outcome is narrow but consequential two passenger-carrying wide-body aircraft reached conflicting taxi paths, and separation was preserved when the Lufthansa crew stopped before the intersection.

By Thomas Caldwell — AMI’s senior editor for mechanical and mobility engineering, covering vehicle electronics, systems integration, electrification, chassis systems, propulsion, and safety policy.