Republic 4736 at LaGuardia: how a takeoff was aborted with United 2657 still on the runway
Just after midnight, LaGuardia Tower cleared a regional jet to take off on runway 13 while a United 737 was still taxiing along the same runway, on a different frequency. Follow the radio from both controllers, call by call, and see what the ADS-B record does and doesn't show.
What happened
On Tuesday, May 6, 2025, at about 12:35 a.m. local time, LaGuardia Tower cleared Brickyard 4736, a Republic Airways Embraer 175 flying as American Eagle 4736 to Buffalo, for takeoff on runway 13. United 2657, a Boeing 737-800 that had just landed on runway 4, was still taxiing along runway 13 toward the terminal. The tower shouted "stop," and the Republic crew rejected the takeoff at about 105 knots, according to The Aviation Herald. Flightradar24's analysis, as reported by CNN and ABC, put the jets almost a quarter mile apart when Republic began braking. On frequency the controller apologized: "I thought United had cleared well before that." The FAA and NTSB said they were investigating.
| Date and time | Tue 6 May 2025, about 04:35Z (about 12:35 a.m. EDT, per the FAA) |
|---|---|
| Airport | New York LaGuardia (LGA), landing runway 4, departing runway 13, wind 070° at 9 kt (tower, on frequency) |
| Aircraft 1 | Brickyard 4736 (RPA4736), Republic Airways Embraer 175, flying as American Eagle 4736 to Buffalo, departing runway 13 |
| Aircraft 2 | United 2657 (UAL2657), Boeing 737-800 from Houston, landed runway 4 at about 04:31Z (ADS-B), then taxiing along runway 13 |
| Closest point | Almost a quarter mile (0.27 mi) when Republic braked, per Flightradar24's analysis as reported by CNN and ABC. Our ADS-B data has no positions for the roll |
| Speed | About 105 kt groundspeed at the rejection (The Aviation Herald) |
| Controllers | LaGuardia Tower (runway 13) and LaGuardia Ground (United, after it left the tower frequency) |
| Outcome | Rejected takeoff, no collision; flight canceled; FAA and NTSB investigating (announced May 19, 2025) |
LaGuardia after midnight
It's 12:26 a.m. in New York. United 2657, a 737 from Houston, is on the ILS to runway 4, about 15 miles southwest at 3,850 feet. At the terminal, Brickyard 4736, a Republic Embraer flying as American Eagle to Buffalo, is just leaving the Terminal B ramp. Reports say it was already running about three hours late.
- UAL2657
- Callsign
- 039
- Altitude in hundreds of feet: about 3,900 ft
- 19
- Ground speed in tens of knots: about 190 kt
- B738
- Aircraft type: Boeing 737-800
Two runways that cross
LaGuardia has just two runways, 4/22 and 13/31, each 7,002 feet long, and they cross near the north side of the field. Tonight arrivals land on runway 4 and departures roll on runway 13, toward the southeast, past the terminals.
The grey dot by the terminal is Brickyard 4736's last ADS-B report in the Flightradar24 data we used, at 04:26:09Z, moving at 8 knots. After this the record is empty until the jet was back at a gate.
With only two runways, LaGuardia uses its runways as taxi routes too. A jet that lands on 4 can be told to turn onto runway 13 and taxi along it toward the gates. That's normal here, but the runway has to be empty before anyone takes off on it.
United comes down the ILS to runway 4
United is about 7 miles out at 2,150 feet. The tower is landing a stream on runway 4. In the audio, each arrival is cleared to land with a reminder: "traffic departs 13."
When two runways cross, a departure on one and an arrival on the other must not meet at the intersection. The tower times them, and tells each pilot about the other so nobody is surprised.
425 feet, about 1.7 miles from the end of runway 4. The weather is wet: a Spirit crew checking in a few minutes later reports moderate rain on the approach.
Where the ADS-B data stops
Flightradar24 logs United's landing at 04:31:01Z, at the start of runway 4. Its next position is on the terminal ramp almost nine minutes later. Brickyard 4736's record is just as empty: nothing between leaving the ramp and returning to it.
So the scope stops here. We won't draw where the two jets went next, because nothing in the data says. The rest of the story comes from the radio, below. Even VASAviation's own animation loses Brickyard's ADS-B signal during the roll.
Four minutes on two frequencies
The published recording mixes LaGuardia Tower and LaGuardia Ground. United talks to the tower, then to ground. Brickyard 4736 talks to the tower. The two crews never share a frequency. The video is edited and carries no clock, so the calls are in order but not timed.
"United 2657, Uniform, Romeo, hold short of 1-3, stay with me."
Turn off on taxiways U and R, stop before runway 13, and stay on my frequency.
"Uniform, Romeo, hold short of 1-3, 2657."
United is put on runway 13
"United 2657, you're gonna turn left onto runway 1-3 and then taxi down 1-3, go to Ground point 7."
Get on runway 13, taxi along it, and switch to the ground controller.
"Okay, left turn on runway 1-3 and over to Ground point 7, United 2657."
The tower controller owns the active runways. FAA rules say permission to taxi along an active runway comes from the tower, on the tower frequency. That's what happened here. Then United left the tower's frequency while it was still on the tower's runway.
"Brickyard 4736, monitor Tower, good night."
"Ground, United 2657 is taxiing runway 1-3."
"United 2657, you could actually make this quick right turn at Sierra, and then a left turn on Papa, Bravo, Kilo, Alpha, Lane 7."
Leave the runway at taxiway S, then follow the taxiways to the ramp.
"We'll make the left turn here… Papa, Bravo, Kilo, Alpha to Lane 7, United…"
United is now talking to Ground. Brickyard is listening to the Tower. Each crew hears only its own controller, so neither hears what the other is being told.
"Brickyard 4736, Tower, if you're ready, line up runway 1-3, traffic lands runway 4."
Get on runway 13 and wait. Someone is landing on the crossing runway.
"Runway 1-3, line up and wait, Brickyard 4736."
The tower puts a departure on the runway when takeoff is close but can't be cleared yet. The traffic it mentions here is an arrival on runway 4. It says nothing about United, which the tower has already handed to Ground.
"Looks like you passed it. United 2657, I want to take you down to Lima and then right turn Alpha, Lane 7."
You missed the turn. Keep going down the runway to taxiway L instead.
"Lima and Lane 7, 2657."
United just missed its exit and will stay on runway 13 longer. Brickyard is lined up at the far end, listening to the Tower. What has to happen before Brickyard can roll?
How did a takeoff get cleared with a jet on the runway?
"United 2657, after Lima did you want us to turn right on Bravo or Alpha to Lane 7?"
"United 2657, it's gonna be a right turn [Alpha] to Lane 7."
"Brickyard 4736, runway 1-3, cleared for takeoff."
Go. (Spirit 1940 checks in on the same frequency at the same moment, over the top of this call.)
"Cleared for takeoff runway 1-3, Brickyard 4736."
United is still asking Ground about its turn off runway 13 when the tower clears Brickyard to take off on it. The controller's own words a minute later: "I thought United had cleared well before that." Why the tower thought so is for the investigators; the audio doesn't say.
Brickyard is accelerating down runway 13 toward United. Spirit 1940 is talking on your frequency. What do you do?
"Okay, number 3, standing by landing clearance, and we got moderate rain during the previous approach. How is it looking now?"
"Brickyard 4736, stop!"
Said once under Spirit's transmission, then again in the clear.
"United 2657, expedite off, please."
"We're expediting, 2657."
The FAA's scripted phrase is "cancel takeoff clearance," with a reason, and once a jet is rolling it may be cancelled only for safety. The controller here used one word, twice: stop.
How close did the planes get?
"Brickyard 4736, stopped, rejected takeoff 1-3."
"Brickyard 4736, sorry about that. I thought United had cleared well before that. Just stay there for a moment, and I gotta get the other United out of the way and we'll get you off the runway."
Flightradar24's analysis, as reported by CNN and ABC, put the jets almost a quarter mile apart (0.27 miles) when Republic began braking. The Aviation Herald reported the Embraer rejected at about 105 knots groundspeed. The Flightradar24 track data we used has no positions for the roll, so we can't check either number ourselves.
Who was at fault?
"Tower, Brickyard 4736, we are gonna be exiting here. We're gonna go back to the gate."
"Brickyard 4736, affirmative, I'll get you there in a second. Just got a lot of traffic off your right hand side there that's gotta move."
On the record so far: the tower controller cleared the takeoff and apologized on frequency, saying he thought United had already cleared. That's his remark in the moment, not a finding. The FAA and the NTSB said on May 19, 2025 that they were investigating. Commentators at One Mile at a Time and View from the Wing pointed to LaGuardia's practice of handing jets to Ground while they're still taxiing on a runway; that's their analysis, not an official one.
What this one teaches
Three habits a tower controller leans on, and why each one mattered here.
A runway is clear when you see it clear
"I thought United had cleared" is the trap: a plan in your head is not the runway in front of you. Check the runway before every takeoff clearance.
Two frequencies, one runway
United was on Ground while still on the tower's runway, and its exit changed. When a plan changes on someone else's runway, the owner of that runway has to hear about it.
Short words when it counts
The first "stop" was stepped on by another transmission. The controller said it again, and the crew stopped. In a hurry, the shortest call that works is the right one.
Try your hand at air traffic control.
Sit at a real radar position in Southern California, with real runways, real procedures and live traffic, and AI controllers in every other seat. It runs in your browser, free.
- Keep jets 3 miles or 1,000 feet apart
- Climb departures and turn them onto their routes
- Hand them off cleanly to the next controller
LaGuardia rejected takeoff: common questions
How close did Republic 4736 and United 2657 get?
News reports citing Flightradar24's analysis put the two jets almost a quarter mile apart (0.27 miles) when Republic 4736 began braking. The Aviation Herald reported the Embraer rejected the takeoff at about 105 knots groundspeed. The Flightradar24 track data we used has no positions for either jet during the takeoff roll, so we could not measure the gap ourselves.
Why was United 2657 on runway 13?
United 2657 had landed on runway 4. In the published audio, the tower told it to turn left onto runway 13, taxi down 13 and switch to the ground controller. The ground controller then said it had passed its exit and sent it farther down runway 13 to taxiway Lima.
Who was at fault?
On frequency, the tower controller told the Republic crew, "sorry about that, I thought United had cleared well before that." That's the controller's own remark, not a finding. The FAA and NTSB said on May 19, 2025 that they were investigating; we have not verified a published finding.
What does "Brickyard" mean?
Brickyard is Republic Airways' radio callsign. Republic flew this trip, from LaGuardia to Buffalo, for American Airlines as American Eagle 4736, so on the radio it was Brickyard 4736 and in ADS-B data it was RPA4736.
Was anyone hurt?
There was no collision. One passenger on the Republic jet told NBC News she went to the emergency room the next day with neck pain and a numb arm and was diagnosed with a pinched nerve. The Aviation Herald reported that the jet returned to the gate and the flight was canceled.
What is a rejected takeoff?
A rejected takeoff is when the crew abandons a takeoff already underway and brakes to a stop on the runway. Above 100 knots it is a hard, high-energy stop, which is why one passenger compared it to a car accident and why the brakes are checked afterwards.
Every word on frequency
LaGuardia Tower and Ground, in order (times are positions in the VASAviation video)
| 0:12 | Tower | United 2657, Uniform, Romeo, hold short of 13, stay with me. |
|---|---|---|
| 0:17 | United 2657 | Uniform, Romeo, hold short of 13, 2657. |
| 0:22 | Endeavor 4990 | Good evening Tower, Endeavor 4990, [fix] for ILS 4. |
| 0:28 | Tower | Endeavor 4990, LaGuardia Tower. Base reported at 250 feet. Wind 070 at 9, runway 4, cleared to land. Traffic departs 13. |
| 0:34 | Endeavor 4990 | Cleared to land runway 4, Endeavor 4990. |
| 0:38 | Frontier 3288 | LaGuardia, good evening, Frontier Flight 3288 with you, ILS 4. |
| 0:44 | Tower | Frontier Flight 3288, LaGuardia Tower, you're number 4. You're following an RJ about 5 miles in trail. Base reported at 250 feet. Wind 070 at 9, runway 4, cleared to land. Traffic will depart 13. |
| 0:54 | Frontier 3288 | Cleared to land runway 4, Frontier Flight 3288. |
| 1:05 | Tower | United 2657, you're gonna turn left onto runway 13 and then taxi down 13, go to Ground point 7. |
| 1:13 | United 2657 | Okay, left turn on runway 13 and over to Ground point 7, United 2657. |
| 1:20 | Ground | Brickyard 4736, monitor Tower, good night. |
| 1:25 | Brickyard 4736 | Monitor Tower, Brickyard 4736. |
| 1:27 | Ground | United 975, monitor Tower, good night. |
| 1:34 | United 2657 | Ground, United 2657 is taxiing runway 13. |
| 1:39 | Ground | United 2657, you could actually make this quick right turn at Sierra, and then a left turn on Papa, Bravo, Kilo, Alpha, Lane 7. |
| 1:51 | United 2657 | We'll make the left turn here… Papa, Bravo, Kilo, Alpha to Lane 7, United [cut off]. |
| 2:04 | Tower | Brickyard 4736, Tower, if you're ready, line up runway 13, traffic lands runway 4. |
| 2:08 | Brickyard 4736 | Runway 13, line up and wait, Brickyard 4736. |
| 2:16 | Ground | Looks like you passed it. United 2657, I want to take you down to Lima and then right turn Alpha, Lane 7. |
| 2:24 | United 2657 | Lima and Lane 7, 2657. |
| 2:30 | Tower | JetBlue 472, right turn on Papa, join Bravo, Ground point 7. Good night. |
| 2:34 | JetBlue 472 | Papa, Ground point 7, thanks, JetBlue 472. |
| 2:41 | United 2657 | United 2657, after Lima did you want us to turn right on Bravo or Alpha to Lane 7? |
| 2:46 | Ground | United 2657, it's gonna be a right turn [Alpha] to Lane 7. |
| 2:50 | United 2657 | Right turn Alpha to Lane 7, thanks, 2657. |
| 2:53 | Tower | Brickyard 4736, runway 13, cleared for takeoff. [Spirit 1940 transmits at the same time: "Tower, good evening again, Spirit 1940 with you, ILS 04."] |
| 2:58 | Brickyard 4736 | Cleared for takeoff runway 13, Brickyard 4736. |
| 3:04 | Spirit 1940 | Tower, good evening, Spirit 1940 with you, ILS 4. |
| 3:08 | Tower | Spirit 1940, Tower, number 3 following Frontier about 4.5 ahead. Winds are 060 at 9 [cut off]. |
| 3:17 | Spirit 1940 | Okay, number 3, standing by landing clearance, and we got moderate rain during the previous approach. How is it looking now? [The tower's "Brickyard 4736, stop!" is heard underneath.] |
| 3:24 | Tower | Brickyard 4736, stop! |
| 3:26 | Ground | United 2657, expedite off, please. |
| 3:29 | United 2657 | We're expediting, 2657. |
| 3:31 | Brickyard 4736 | Brickyard 4736, stopped, rejected takeoff 13. |
| 3:35 | Tower | Brickyard 4736, sorry about that. I thought United had cleared well before that. Just stay there for a moment, and I gotta get the other United out of the way and we'll get you off the runway. |
| 3:46 | Brickyard 4736 | We'll hold, Brickyard 4736. |
| 3:51 | Brickyard 4736 | Tower, Brickyard 4736, we are gonna be exiting here. We're gonna go back to the gate. |
| 3:58 | Tower | Brickyard 4736, affirmative, I'll get you there in a second. Just got a lot of traffic off your right hand side there that's gotta move. |
| 4:05 | Brickyard 4736 | Alright, copy, we're holding on runway 13, Brickyard 4736. |
| 4:11 | Tower | Brickyard 4736, you can continue, turn right at taxiway Lima and then right turn on Alpha behind the Delta RJ9 that's ahead and to your right. |
| 4:20 | Brickyard 4736 | Alright, Lima, Alpha, and then behind the Delta RJ9 to our right, Brickyard 4736. |
Radio audio was recorded by LiveATC.net and published by VASAviation, who edited Tower and Ground together and shortened the gaps. Our transcript follows that video, checked against its captions; [brackets] mark words we couldn't make out or that were cut off. Aircraft positions on the scope are ADS-B data from Flightradar24, drawn by us.
Sources
Incident audio and flight data
- VASAviation: NEAR DISASTER at LaGuardia, published May 17, 2025. The published Tower and Ground recording (audio from LiveATC.net) used for our transcript. A third-party publication of the radio, not an FAA release.
- Flightradar24. The scope uses Flightradar24 ADS-B positions for UAL2657 (landing 04:31:01Z) and RPA4736 (last ramp report 04:26:09Z) on May 6, 2025. The data holds no positions for either jet during the taxi on runway 13 or the takeoff roll. This provider link is not an archive of those tracks.
- CNN, May 19, 2025. The FAA's statement (controller canceled the takeoff clearance around 12:35 a.m. because United 2657 was taxiing on the same runway), FAA and NTSB confirmation of investigations, United's passenger count, and Flightradar24's "almost a quarter mile" analysis.
- ABC7 New York, May 19, 2025. The Brickyard callsign, the time, and the 0.27-mile figure attributed to Flightradar24.
- NBC News / Associated Press, May 20, 2025. The passenger's account and diagnosis, and the ground and tower controllers working on different frequencies.
- The Aviation Herald via AeroInside. Registrations (N115HQ, N37252), United's landing on runway 4, about 105 knots at the rejection, and the canceled flight.
- One Mile at a Time, May 17, 2025 and View from the Wing. Commentary on the tower and ground split and the three-hour delay. Their analysis, not an official finding.
- AirNav: KLGA. FAA runway end coordinates and lengths used to draw runways 4/22 and 13/31.
Primary FAA procedure references
- FAA Order JO 7110.65, paragraph 3-1-3: Use of Active Runways. The local (tower) controller's responsibility for the active runway, and how taxiing along an active runway is authorized.
- FAA Order JO 7110.65, paragraph 3-1-4: Coordination Between Local and Ground Controllers. What tower and ground controllers must tell each other.
- FAA Order JO 7110.65, paragraph 3-9-4: Line Up and Wait. When and how a departure is put on the runway to wait.
- FAA Order JO 7110.65, paragraph 3-9-11: Cancellation of Takeoff Clearance. The prescribed phraseology, and the rule that a rolling takeoff is cancelled only for safety.
These FAA links explain procedures; they are not incident investigation records. The FAA and NTSB confirmed investigations through news outlets on May 19, 2025, but as of November 17, 2026 we have not verified an NTSB case record, preliminary or final report, or FAA report for this event. This breakdown is an educational reconstruction from the published audio, news reports and ADS-B data, not an official finding of cause or fault. The linked FAA pages are maintained online and reflect the current edition, which may differ from the one in force on May 6, 2025.