American Airlines 737 executes go-around at Reagan National after regional jet enters runway

Quick summary

A runway incursion at Ronald Reagan Washington National Airport (DCA) on July 30, 2026, forced an American Airlines Boeing 737-800 to execute an emergency go-around after a Republic Airways-operated American Eagle regional jet entered an active runway without clearance. The crew of AA4752 apparently misread an air traffic control instruction intended for a nearly identical callsign, AA4702, both operating on the same tower frequency at adjacent runways. No injuries or aircraft damage occurred.

Preliminary evidence points to crew error rather than controller error. The Federal Aviation Administration is expected to open a formal review, and the incident is drawing comparisons to a similar runway incursion at Boston Logan just six weeks earlier.

At approximately 6:55 p.m. Eastern on July 30, an American Airlines Boeing 737-800 on final approach to Runway 1 at DCA spotted an Embraer E175 sitting on the runway ahead and immediately radioed the tower. Controllers responded within seconds, ordering the 737 crew to go around, turn left to heading 280, and climb to 3,000 feet. The go-around was initiated roughly 0.8 miles from the threshold at approximately 320 feet above runway elevation — close enough that the outcome depended entirely on the 737 crew’s alertness and the controller’s speed.

The aircraft that should not have been there was AA4752 (callsign Brickyard 4752), a Republic Airways-operated Embraer 175 bound for Raleigh-Durham. Air traffic control had cleared AA4702 (callsign Brickyard 4702) — a nearly identical identifier — to line up and wait on the adjacent Runway 4. The Brickyard 4752 crew apparently interpreted that clearance as applying to their own aircraft and entered Runway 1 without authorization while AA3101, the arriving 737 from Dallas/Fort Worth, was on short final.

Both regional jets subsequently departed safely. No passengers were injured, and no aircraft sustained damage. The FAA is expected to conduct a formal review; preliminary evidence indicates the cause was crew error rather than a controller mistake.

What the flight data shows

American Airlines Flight 3101 was a Boeing 737-800 (registration N983NN, 172 seats) arriving from Dallas/Fort Worth. The intruding aircraft, AA4752, was an Embraer 175LR (N122HQ, 76 seats, 18.7 years old). AA4702, the jet that received the original clearance, was a second Embraer 175LR (N415YX, 76 seats) waiting on Runway 4 for a departure to New York LaGuardia.

The sequence is straightforward in hindsight: controllers cleared Brickyard 4702 to line up and wait; the Brickyard 4752 crew acknowledged the instruction as if it were theirs and rolled onto Runway 1. The 737 crew spotted the conflict, called it out to the tower, and the go-around was underway before controllers could independently detect the problem. That sequence — pilot sees, pilot calls, controller acts — is exactly how the system is supposed to work, and on this occasion it did.

The NTSB‘s investigation of a January 2023 JFK runway incursion involving American Airlines Flight 106 and Delta Flight 1943 identified flight crew task distraction, tower nondetection of a taxi deviation, and limitations of runway status lights as key contributors — findings that apply with uncomfortable directness to DCA’s operational environment. The NTSB’s JFK incursion investigation concluded that advanced surface detection systems could have alerted controllers in time to cancel the clearance before any aircraft reached the runway.

A separate incursion at Boston Logan on June 20, 2026 — involving intersecting runway clearances between a Delta and an American flight — is already under active NTSB investigation, with a preliminary report filed. Deep Arrival reported that the Boston Logan NTSB preliminary report formally classifies that event as an ongoing incident investigation, which sets a template regulators are likely to apply to the DCA case.

Why callsign confusion at DCA is a structural problem, not a one-off

DCA is not a forgiving airport. Short runways, a river-visual approach corridor, and a dense mix of regional turboprops, narrow-bodies, and the occasional wide-body create an environment where radio discipline has almost no margin for error. Scheduling two departures with near-identical callsigns — Brickyard 4702 and Brickyard 4752 — on the same tower frequency at adjacent runways is the kind of operational overlap that FAA human-factors research has flagged repeatedly as a precursor condition for exactly this type of event.

The fix is not purely technological. Surface detection radar and runway status lights help, but they are backstops. The first line of defense is ensuring that similar-sounding identifiers do not share a frequency during the same departure window. Airlines and their regional partners have scheduling levers to prevent this; the question regulators will ask is whether those levers were used here, and whether written deconfliction policies exist at all.

Reagan National also carries the shadow of the January 2025 midair collision nearby, which triggered a broad review of procedures in the Potomac sector. That scrutiny has not fully resolved, and a second high-visibility surface event within eighteen months will intensify pressure on the FAA to move beyond case-by-case investigations toward systemic fixes — updated phraseology standards, mandatory callsign-similarity checks at scheduling, and expanded surface radar coverage at the airports most exposed to this risk.

What DCA travelers and aviation professionals should do now

No flights were cancelled and DCA is operating normally — but this incident is a live regulatory matter, and the procedural landscape around DCA runway operations may shift as the FAA review progresses.

• Monitor your flight via the airline app, not third-party sites: If the FAA or NTSB issues interim operational guidance affecting DCA runway assignments, American Airlines and American Eagle will reflect any resulting schedule or gate changes in their own systems first. Set push notifications for your booking.
• Do not rebook based on this incident alone: No evidence suggests ongoing elevated risk to passengers at DCA. The go-around worked as designed, and both aircraft departed safely. Rebooking fees are not recoverable on the basis of a resolved safety event with no injuries.
• Aviation professionals: review the NTSB’s JFK and Boston incursion reports: The NTSB’s JFK runway incursion findings and the Boston Logan preliminary report both address the communication and surface-awareness failures most relevant to the DCA event. Incorporating these into crew briefings now, before DCA-specific findings are published, is the practical move.
• Watch for an NTSB docket entry: A case number appearing on the NTSB public docket signals a formal investigation rather than an administrative FAA review. That distinction determines whether safety recommendations will carry regulatory weight.

Watch: The FAA’s response to the Boston Logan June 20 incursion — specifically whether it issues a Safety Alert for Operators (SAFO) on callsign deconfliction — will signal how aggressively the agency plans to address similar-identifier risk across the national airspace system, not just at DCA.

Questions? Answers.