A 787 at 106 knots. A jet crossing in front of it.

United 530 and United 152 at LAX: the runway incursion that forced a 106-knot rejected takeoff

A United A321neo landed on LAX's outer north runway, read back "hold short of 24 left", and rolled across it while a United 787 bound for Hong Kong was accelerating down that runway. Work it from the tower's seat, decode the radio as it happens, and make the call yourself.

What happened

On Monday, March 2, 2026, at about 11:49 a.m. local time, United 530, an Airbus A321neo arriving from Chicago, landed on LAX runway 24R and was told to hold short of runway 24L. The crew read the instruction back. About 24 seconds later, by ADS-B data, the A321neo crossed 24L while United 152, a Boeing 787-9 bound for Hong Kong, was on its takeoff roll on that runway. The tower told United 530 "no delay" and cancelled United 152's takeoff clearance; the 787 rejected its takeoff from 106 knots of ground speed and was down to taxi speed long before it reached the spot where the A321neo crossed. No injuries were reported, and the ground controller advised United 530 of a possible pilot deviation.

Incident facts
Date and timeMon 2 Mar 2026, 19:49Z (11:49 PST)
AirportLos Angeles International (LAX), west flow, wind 220° at 12 kt (tower audio)
Aircraft 1United 530 (UAL530), Airbus A321neo, from Chicago O'Hare, landed runway 24R
Aircraft 2United 152 heavy (UAL152), Boeing 787-9, to Hong Kong, departing runway 24L
Top speed106 kt ground speed at 19:49:36–38Z, then rejected (ADS-B)
Gap at the crossingAbout 0.74 nm (4,500 ft) along the runway when UAL530 crossed the 24L centreline at 19:49:41Z (our ADS-B analysis)
ControllerLAX Tower, north side
OutcomeTakeoff clearance cancelled, rejected takeoff, hot brakes, no injuries reported; possible pilot deviation advised to UAL530
United 530Airbus A321neo · landed 24R · told to hold short of 24L
United 152 heavyBoeing 787-9 · departing 24L · to Hong Kong
LAX TowerThe north-side local controller working both runways
Scroll to run the clock
LAX TWR · NORTH19:48:20Z
CONTROLLER INSTINCTS0 / 2
19:48:20Z The setup

How LAX's north runways work

It's late Monday morning and LAX is in west flow: everyone lands and departs toward the ocean. On the north side, the outer runway, 24R, takes arrivals and the inner one, 24L, takes departures. Every jet that lands on 24R has to cross 24L to reach the terminals.

These are the same two runways Delta 958 departed from in our Delta 958 near miss breakdown. That one went wrong in the air; this one goes wrong on the ground. Runway 24L is also where the November 7, 2026 Air France 28 near miss began.

Why it's tight

The FAA says 24R and 24L are only about 700 feet apart, with about 300 feet between their hold-short lines and no taxiway in between. Turn off 24R and the next runway arrives almost at once.

19:48:53Z Cleared for takeoff
Tower · to United 152

"United 152 heavy, wind 220 at 12, RNAV [fix], runway 24 left, cleared for takeoff."

You're cleared to take off on 24L and fly your published departure.

United 152

"Cleared for takeoff 24 left, RNAV [fix], United 152 heavy."

The 787 sits at the east end of 24L, at the right of the scope. United 530 has just touched down on 24R, the runway to its north, and is slowing down.

Read the scope

This is a ground picture, not a radar picture, drawn from each jet's ADS-B position. United 152 (blue) is at the east end of 24L; United 530 (amber) is rolling west along 24R.

19:49:04Z Turn off when you can
Tower · to United 530

"United 530, any exit is approved now, hold short of 24 left. Thanks for the help."

Leave the runway wherever suits you, but stop before 24L.

No readback is heard on the published recording. Eleven seconds later the controller says it again.

19:49:15Z The instruction

What does "hold short" mean?

Tower · to United 530

"United 530, hold short of runway 24 left."

United 530

"Hold short of 24 left, United 530."

We'll stop before 24L.

The rule

"Hold short" means stop before the yellow holding position markings and go no further. Controllers must get a readback of every runway hold-short instruction, and here they got a clean one.

What the data shows

ADS-B puts United 530 at about 42 knots of ground speed during that readback, still turning off 24R toward 24L.

19:49:28Z Rolling

United 152 started rolling at about 19:49:13 and passes 70 knots at 19:49:27. Meanwhile the controller clears another United jet to land on 24L behind it.

Tower · to United 1164

"United 1164, wind 220 at 12, runway 24 left, cleared to land."

United 1164

"24 left, cleared to land, United 1164. Anything in front of us at all?"

How it fits together

On a busy day the tower lands one jet behind a departure that's already rolling. It works because the departure will be gone long before the arrival gets to the runway.

Freeze frame

One of these jets is about to be somewhere it was told not to go. Which one? Tap it on the scope or pick below.

United 530 is the dot on the left, between the two runways. United 152 is the dot on the right, accelerating down 24L toward it.

Your call

The A321neo is rolling onto 24L. The 787 is past 90 knots on the same runway and closing. What do you say?

19:49:36Z Two calls, two seconds

What is a rejected takeoff?

Tower · to United 530

"United 530, no delay!"

Get across, now.

Tower · to United 152

"United 152 heavy, cancel takeoff clearance."

Stop the takeoff.

A rejected takeoff is the crew abandoning a takeoff already under way: thrust to idle, maximum braking, spoilers and reversers. It's the crew's decision, made in seconds, and it gets harder and hotter the faster the jet is going.

What the data shows

United 152's ADS-B ground speed peaks at 106 knots at 19:49:36–38, then falls: 99 knots at 19:49:40 and 46 knots at 19:49:56. The video's audio and radar are synced by hand, so we can't say to the second whether the crew began stopping before or after the call.

19:49:41Z The crossing

How close did the planes get?

United 152

"United 152, we are aborting."

At about 19:49:41, United 530's reported position crosses the 24L centreline. United 152 is then about 0.74 nautical miles (4,500 feet) back down the same runway, already slowing through about 90 knots.

Read the number carefully

ADS-B reports one point on each airframe, from its GPS antenna. The A321neo's tail trails that point, so part of the jet was still over the runway for a few seconds after the dot crossed. The gap is our calculation from the positions, not an official figure.

19:49:44Z Telling them
Tower · to United 530

"United 530, instructions were to hold short, and you were [fix] past the hold short. Turn left on Echo."

You were told to stop before 24L. Turn left on taxiway E.

United 530

"Left on Echo, United 530."

The A321neo is now south of 24L, turning east. On the data it turns left from a southerly heading to 084° by 19:50:20.

Say it while it's fresh

The controller states plainly what the instruction was, then gives the next one. No argument on frequency, just the fact and a taxi route.

19:49:54Z The jet behind
Tower · to United 1164

"United 1164, cancel approach clearance, go around, maintain 2,000."

Tower · to United 152

"United 152 heavy, you can roll down the runway. Do you need any assistance?"

United 152

"Negative on the assistance, we'll roll down to the end of the runway, United 152."

With a 787 now slowing on 24L, the arrival cleared to land there can't. The controller sends it around, then gives the 787 the rest of the runway.

19:50:45Z Rolling past

A minute after the crossing, United 152 rolls past the spot where United 530 crossed, at about 32 knots. By then the A321neo is about 450 feet south of the runway centreline on taxiway E.

Why it ended this way

The crossing took place more than a mile down the runway from where the 787 started. A rejected takeoff from just over 100 knots had the 787 down to about 33 knots by 19:50:09, long before it got there.

19:52:41Z Hot brakes
United 152 · to Ground

"Our brakes are getting pretty hot. Would you mind sending somebody over to help check on that, please?"

We stopped hard. Can someone look at our brakes?

United 152 rolled to the west end of 24L, turned off, and came to a stop on taxiway Y (Yankee) by 19:51:54. The ground controller called City Ops to check it. A few minutes later the crew asked to wait about five more minutes before taxiing, because the brakes would heat up again as they moved.

Where the energy goes

Stopping a heavy jet from 100-plus knots turns its speed into heat in the brakes. That's why crews park and let them cool after a high-speed rejected takeoff, and why fire crews or ops often come to look.

19:55:20Z The phone number

What is a Brasher warning?

South Ground · to United 530

"United 530, be advised, possible pilot deviation. Advise ready to copy down a phone number."

This will be looked into. Write down this number and call us.

Pilots dread this one

That scripted line is a Brasher warning, named after an NTSB case. Controllers give it so the crew knows the FAA may follow up, and can write down what happened while it's fresh. It is the start of a review, not its result.

Takeaways

What this one teaches

Three things a tower controller does on every runway crossing, and why each one mattered here.

Watch

A readback isn't a stop

United 530 read back the hold short perfectly and kept rolling. A clean readback is a promise; only watching the jet shows whether it stops.

Act

Clear the runway, stop the roll

Two short calls in two seconds: "no delay" to the jet in the way, "cancel takeoff clearance" to the jet on the roll.

Follow through

The runway behind matters too

With 24L blocked, the jet cleared to land on it had to go around, and the 787 needed the rest of the runway to stop.

SectorLive

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
Play free in your browser
Questions

United 530 and United 152 at LAX: common questions

How close did United 530 and United 152 get?

By our analysis of Flightradar24 ADS-B data, United 530's reported position crossed the centreline of runway 24L at about 19:49:41Z. United 152 was then about 0.74 nautical miles (roughly 4,500 feet) back down the same runway, already slowing from its top speed. These are calculated from ADS-B positions, not an official finding.

How fast was United 152 going when it rejected the takeoff?

Flightradar24 ADS-B shows a top ground speed of 106 knots at 19:49:36 to 19:49:38Z, then the speed falls: 99 knots at 19:49:40Z and 46 knots at 19:49:56Z. Press reports from One Mile at a Time and Simple Flying give the same 106-knot figure from Flightradar24.

Who was at fault?

On frequency, United 530 read back an instruction to hold short of runway 24L, and the tower then told the crew they had been told to hold short. Ground controllers later advised the crew of a possible pilot deviation. That's the controller's first report, not a finding. We have not found an FAA or NTSB report on this event.

What does "possible pilot deviation" mean?

The controller believes the pilots did not follow a clearance or instruction. Saying it on frequency, with a phone number to call, is the scripted notification known as a Brasher warning. It tells the crew the FAA may follow up.

Why do aircraft landing on 24R at LAX have to stop so quickly?

The FAA's SAFO 26003 says runways 24R and 24L are about 700 feet apart centreline to centreline, with about 300 feet between their holding position markings and no taxiway between them. An arrival turning off 24R has very little room to stop before it reaches 24L.

Was anyone hurt?

No injuries were reported. On frequency the 787 crew reported hot brakes and waited on the taxiway for them to cool. Press reports say the aircraft returned to the gate and left for Hong Kong about eight hours late.

Full transcript

Every word on frequency

LAX Tower and Ground, 19:48:53Z to 19:55:57Z
19:48:53ZLAX TowerUnited 152 heavy, wind 220 at 12, RNAV [fix], runway 24 left, cleared for takeoff.
19:48:58ZUnited 152Cleared for takeoff 24 left, RNAV [fix], United 152 heavy.
19:49:04ZLAX TowerUnited 530, any exit is approved now, hold short of 24 left. Thanks for the help.
19:49:15ZLAX TowerUnited 530, hold short of runway 24 left.
19:49:17ZUnited 530Hold short of 24 left, United 530.
19:49:23ZUnited 1164Tower, United 1164.
19:49:28ZLAX TowerUnited 1164, wind 220 at 12, runway 24 left, cleared to land.
19:49:31ZUnited 116424 left, cleared to land, United 1164. Anything in front of us at all?
19:49:34ZLAX TowerThere's a Dreamliner departing.
19:49:36ZLAX TowerUnited 530, no delay!
19:49:37ZLAX TowerUnited 152 heavy, cancel takeoff clearance.
19:49:41ZUnited 152United 152, we are aborting.
19:49:44ZLAX TowerUnited 530, instructions were to hold short, and you were [fix] past the hold short. Turn left on Echo.
19:49:50ZUnited 530Left on Echo, United 530.
19:49:54ZLAX TowerUnited 1164, cancel approach clearance, go around, maintain 2,000.
19:50:00ZUnited 1164On the go, 2,000, United 1164.
19:50:04ZLAX TowerUnited 152 heavy, you can roll down the runway. Do you need any assistance?
19:50:08ZUnited 152Negative on the assistance, we'll roll down to the end of the runway, United 152.
19:50:13ZLAX TowerUnited 1164, go around, maintain 2,000.
19:50:16ZUnited 1164On the go, 2,000, United 1164.
19:51:28ZLAX North GroundUnited 152 heavy, LA Ground, say intentions.
19:51:33ZUnited 152Yeah, we'd like to come to a stop here on Yankee for a minute.
19:51:40ZLAX North GroundUnited 152 heavy, that's fine. Stop there and [fix] let me know.
19:51:43ZUnited 152Wilco, thank you.
19:51:48ZUnited 530Ground, United 530, on Echo for 72 Alpha.
19:52:00ZLAX North GroundUnited 530, LA Ground.
19:52:08ZUnited 530We're on Echo for 72 Alpha, United 530.
19:52:16ZLAX North GroundAmeric- correction, United 530, follow American via the south route.
19:52:18ZUnited 530Follow American via the south route, United 530.
19:52:33ZUnited 152Ground, United 152.
19:52:36ZLAX North GroundUnited 152 heavy, go ahead.
19:52:41ZUnited 152Our brakes are getting pretty hot. Would you mind sending somebody over to help check on that, please?
19:52:55ZLAX North GroundCity Ops, LA Ground.
19:53:01ZCity OpsGround, City Ops.
19:53:09ZLAX North GroundCity Ops, the United 152 that had a reject-, canceled takeoff clearance, they're on Yankee, they're having hot brakes. Maybe you guys want to check them, they're abeam gate 413.
19:53:41ZUnited 530Ground, United 530, entering the south complex.
19:54:20ZLAX South GroundUnited 530, Los Angeles Ground, taxi via Bravo, Charlie 6 to parking.
19:54:59ZUnited 530Bravo, Charlie 6 to parking, United 530.
19:55:17ZUnited 530Go for United 530.
19:55:20ZLAX South GroundUnited 530, be advised, possible pilot deviation. Advise ready to copy down a phone number.
19:55:23ZUnited 530United 530, ready to copy.
19:55:26ZLAX South GroundUnited 530, advise you contact Los Angeles Tower on [phone number].
19:55:35ZUnited 530[number], United 530.
19:55:41ZLAX North GroundUnited 152 heavy, do you know how long it's going to be, or do you need any more assistance from City Ops?
19:55:49ZUnited 152We don't need any more assistance. The brakes are cooling, but before we taxi back we'd like about five minutes before we start moving, because they're going to heat back up again as we taxi back.
19:55:57ZLAX North GroundAll right, thank you. Yeah, take as long as you need, let me know.

Radio audio was recorded by LiveATC.net and published by VASAviation. The published video is edited and skips some quiet stretches; times are from the video's own clock and may be off by a second or two. Aircraft positions are ADS-B data from Flightradar24. The scope above is our own drawing of that data. Transmissions are transcribed from the recording and may differ slightly from the audio; [fix] marks words we could not make out.

Evidence and references

Sources

Incident audio and flight data

  • VASAviation: NEAR TRAGEDY | United Plane Crossed Takeoff Runway Without Permission!, published March 7, 2026. The published ATC recording (LiveATC.net audio) used for our transcript and call times. This is a third-party publication of the radio audio, not an FAA release.
  • Flightradar24. The replay, speeds and distances use ADS-B positions for UAL530 and UAL152 on March 2, 2026, retrieved from the Flightradar24 API. This provider link is not a permanent archive of those flight tracks; the distances and timing are our analysis, not an official finding.
  • One Mile at a Time: United Jet Enters Occupied LAX Runway, Ben Schlappig, March 7, 2026. Press report: the flights, aircraft types, local time, the 106-knot Flightradar24 figure, hot brakes, the return to the gate, the roughly eight-hour delay, and a separate United 787 evacuation on the south side the same day.
  • Simple Flying: 106-Knot Rejected Takeoff at LAX, March 8, 2026. Press report: the same sequence, no injuries, and the delayed departure.

Primary FAA references

These FAA links explain procedures and the airport's layout; they are not incident investigation records. We have not verified an incident-specific FAA statement or NTSB investigation record for this event as of November 17, 2026. This breakdown is an educational reconstruction from the published audio and ADS-B data, not an official finding of cause or fault. The linked FAA pages are maintained online and may change.