{"id":152478,"date":"2026-08-01T22:35:00","date_gmt":"2026-08-01T17:05:00","guid":{"rendered":"https:\/\/aviationa2z.com\/?p=152478"},"modified":"2026-08-01T21:31:28","modified_gmt":"2026-08-01T16:01:28","slug":"american-airlines-737-go-around-after-republic-jet-enters-wrong-runway","status":"publish","type":"post","link":"https:\/\/aviationa2z.com\/index.php\/2026\/08\/01\/american-airlines-737-go-around-after-republic-jet-enters-wrong-runway\/","title":{"rendered":"American Airlines 737 Pilots Go-Around After Republic Jet Enters Wrong Runway at DCA"},"content":{"rendered":"\n

WASHINGTON, D.C.-<\/strong> American Airlines (AA)<\/a> and Republic Airways were involved in a runway incursion at Ronald Reagan Washington National Airport (DCA) on July 30, after one regional jet mistakenly entered an active runway, forcing an arriving American Airlines (AA) Boeing 737 to perform a go-around.<\/p>\n\n\n\n

The incident involved two Republic Airways-operated American Eagle flights with nearly identical callsigns departing Washington National Airport (DCA), while American Airlines (AA) Flight 3101 was on final approach from Dallas\/Fort Worth International Airport (DFW)<\/a>. No injuries or damage were reported, but the event is expected to receive regulatory scrutiny.<\/p>\n\n\n\n

\"American
Photo : \tRichard Silagi | Wikimedia Commons | https:\/\/commons.wikimedia.org\/wiki\/File:American_Eagle_(Compass_Airlines)_Embraer_E175_N215NN_at_SFO_April_2017.jpg<\/figcaption><\/figure>\n\n\n\n

Similar Callsigns Trigger Runway Incursion<\/h2>\n\n\n\n

The incident occurred at approximately 6:55 p.m. Eastern on Thursday, July 30, 2026, when two Republic Airways-operated American Eagle flights were preparing for departure from adjacent runways at Washington National Airport, ViewfromtheWing<\/a> flagged.<\/p>\n\n\n\n

The aircraft involved were:<\/p>\n\n\n\n

Flight<\/th>Route<\/th>Operator<\/th>Assigned Runway<\/th><\/tr><\/thead>
AA4702<\/td>Washington (DCA) to New York LaGuardia (LGA)<\/td>Republic Airways<\/td>Runway 4<\/td><\/tr>
AA4752<\/td>Washington (DCA) to Raleigh-Durham (RDU)<\/td>Republic Airways<\/td>Runway 1<\/td><\/tr>
AA3101<\/td>Dallas\/Fort Worth (DFW) to Washington (DCA)<\/td>American Airlines<\/td>Landing on Runway 1<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Air traffic control instructed Brickyard 4702<\/strong>, the callsign for AA4702, to line up and wait on Runway 4 while traffic departed and landed on Runway 1.<\/p>\n\n\n\n

Instead, the crew of Brickyard 4752<\/strong> apparently believed the clearance was intended for them. The aircraft entered Runway 1 without authorization while American Airlines Flight 3101 was on short final.<\/p>\n\n\n\n

The Boeing 737<\/a> crew immediately alerted the tower after spotting the Embraer E175 on the runway.<\/p>\n\n\n\n

The pilot transmitted:<\/p>\n\n\n\n

\n

“Tower, there’s an airplane on Runway 1.”<\/p>\n<\/blockquote>\n\n\n\n

Recognizing the conflict, controllers immediately instructed American 3101 to abandon the landing.<\/p>\n\n\n\n

The flight was instructed to execute a go-around, turn left to a heading of 280 degrees, and climb to 3,000 feet.<\/p>\n\n\n\n

\"American
Photo: Cado Photo<\/figcaption><\/figure>\n\n\n\n

Air Traffic Control Audio Explains the Confusion<\/h2>\n\n\n\n

Recorded tower communications indicate that controllers issued only one line-up-and-wait clearance.<\/p>\n\n\n\n

The relevant exchanges included:<\/p>\n\n\n\n