Delta 5415 at LaGuardia: how a Phenom took off without clearance in front of an arriving jet
A NetJets Phenom 300 told to line up and wait on runway 13 read back a takeoff clearance that isn't on the recording and started rolling, as a Delta Connection CRJ900 came down to land on runway 22, which crosses it. Work it from the tower's frequency, decode every call, and see how close it came on the ADS-B data.
What happened
On Wednesday, October 7, 2026, at about 3:56 p.m. local time, Endeavor Air 5415, a Delta Connection CRJ900 from Omaha, was on short final for LaGuardia's runway 22 when ExecJet 398, a NetJets Embraer Phenom 300 bound for Teterboro, began its takeoff roll on runway 13, which crosses runway 22. The tower had told ExecJet 398 to line up and wait. The FAA says the jet departed without air traffic control authorization. The CRJ900 went around from about 150 feet and passed over the runway intersection seconds after the Phenom rolled through it. Our ADS-B reconstruction puts them about 410 feet apart horizontally at that moment. Nobody was hurt, the controller reported a possible pilot deviation, and the FAA is investigating.
| Date and time | Wed 7 Oct 2026, 19:56Z (15:56 EDT) |
|---|---|
| Airport | LaGuardia (LGA), landing runway 22, departing runway 13; wind 160° at 14 kt (19:55Z METAR) |
| Aircraft 1 | Endeavor 5415 (EDV5415), Bombardier CRJ900, flying as Delta Connection 5415, Omaha to LaGuardia, landing runway 22 |
| Aircraft 2 | ExecJet 398 (EJA398), NetJets Embraer Phenom 300, LaGuardia to Teterboro, departing runway 13 |
| Closest point | About 410 ft horizontally at 19:56:28Z, the Phenom on the runway at 100 kt and the CRJ900 reporting 225 ft (our ADS-B reconstruction, not an official figure). ABC7, citing Flightradar24: about 1,000 ft. |
| Controller | LaGuardia Tower (local control) |
| Outcome | Go-around, no injuries reported; possible pilot deviation reported on frequency; FAA investigating |
How LaGuardia's crossing runways work
LaGuardia has only two runways, and they cross in an X: 4/22 runs northeast to southwest, 13/31 runs northwest to southeast. On this Wednesday afternoon the wind is from the south-southeast at about 14 knots, and the tower is landing on 22 and departing on 13.
Every departure on 13 rolls straight through the spot where arrivals on 22 touch down. The tower keeps them apart with timing: a departure doesn't start rolling until the arrival ahead has passed the intersection or is clear.
A United 737 has just been cleared for takeoff on 13. The NetJets Phenom is next.
"ExecJet 398, LaGuardia Tower, runway 1-3, line up and wait, traffic 3 miles final 2-2."
Pull onto runway 13 and stop. There's a jet 3 miles out for the crossing runway.
"1-3, line up and wait, ExecJet 398."
The FAA's pilot manual says it in so many words: line up and wait is not an authorization to take off. The crew waits on the runway for a separate "cleared for takeoff."
Who was meant to go first?
"Brickyard 4569, LaGuardia Tower, good afternoon. Runway 2-2, cleared to land, wind 1-9-0 at 1-3. Number 2 following a CRJ-900 on a mile and a half final. Traffic in position runway 1-3 will depart prior to your arrival."
You can land on 22. You're behind the CRJ900 that's almost here, and the jet sitting on 13 will go before you.
That call spells out the sequence. The amber CRJ900, Endeavor 5415, lands first. Then the Phenom on 13 goes, ahead of the next arrival, Republic's Brickyard 4569.
- EDV5415
- Endeavor Air's callsign, flying as Delta Connection 5415
- 008
- Altitude in hundreds of feet: about 800 ft
- 13
- Ground speed in tens of knots: about 130 kt
- CRJ9
- Aircraft type: Bombardier CRJ900
"Brickyard 4513, LaGuardia Tower, good afternoon, runway 2-2, cleared to land, wind 1-8-0 at 1-3. Traffic in position runway 1-3 will depart prior to your arrival. You're number 3 following a CRJ, correction, an E170, 3 and a half miles ahead."
Same plan for the jet behind: you can land, and the one on 13 goes before you.
Busy afternoon. The controller is talking to arrivals two and three, while the Phenom sits on runway 13 and Endeavor 5415 drops through 400 feet.
Where it went wrong: "Roger that, cleared for takeoff"
"Roger that, cleared for takeoff runway 1-3, for ExecJet 398."
We're cleared to go on 13. (On the recording, the tower's last call was a landing clearance for Brickyard 4513.)
Nothing on the published recording clears ExecJet 398 for takeoff. Its readback comes straight after a call to a different airplane, the kind of moment when a crew primed to hear "cleared" can hear it in someone else's clearance. Why it happened is for the FAA's review to say.
ExecJet 398 thinks it's cleared to roll. Which airplane is about to cross its path? Tap it on the scope or pick below.
The Phenom is waiting at the near end of runway 13. Runway 22 crosses it about 1,200 feet ahead of its nose.
"And cleared to land for Brickyard 4513."
Republic's readback follows the Phenom's within seconds. Then the frequency goes quiet for about 20 seconds. No one on the recording answers "cleared for takeoff, ExecJet 398."
Readbacks exist so a controller can catch a wrong one. Controllers are required to listen to them and correct mistakes, but a readback squeezed in next to another airplane's call is easy to miss. Whether the tower heard this one, the published audio can't tell us.
The Phenom is rolling on 13, already past 30 knots. Endeavor 5415 is about 150 feet up, 2,400 feet from the intersection. Which move keeps them apart?
How close did the planes get?
The Phenom rolled through the intersection at about 19:56:27Z, still on the ground at roughly 95 knots. Endeavor 5415 passed over it about two seconds later, climbing through about 250 feet.
At 19:56:28Z our reconstruction has them about 410 feet apart horizontally, with the CRJ900 reporting 225 feet and the Phenom on the runway at 100 knots. ABC7, citing Flightradar24, reported about 1,000 feet.
No official figure has been published. Our numbers come from Flightradar24's ADS-B reports: the CRJ900 reported every 7 to 9 seconds here, so we interpolate between reports, and ADS-B altitude is pressure altitude, not height above the runway. Treat them as close estimates, not measurements.
"That guy is going around."
The Phenom lifts off at about 19:56:31Z and climbs southeast. The CRJ900 climbs out southwest over runway 22. The gap meter reads the moment both are flying: 0.25 nm at 19:56:33Z, and opening fast as the two tracks fan apart.
Who was at fault?
"ExecJet 398, I believe you were never cleared for takeoff, sir. You were cleared to line up and wait."
"No, I believe we got the cleared for takeoff. And we were told that the United was ahead, wake turbulence and everything."
We think we were cleared, and we remember a wake turbulence warning about the United ahead.
"Negative. I never said anything about wake turbulence."
The FAA has said ExecJet 398 departed without air traffic control authorization. It has not published a finding on why, and the crew disputed it on frequency. That's where the record stands.
"Endeavor 5415, fly runway heading, climb and maintain 2,000."
Keep going straight ahead and level off at 2,000 feet.
"Runway heading, 2,000, 5415."
Seconds later the tower raises the CRJ900 to 3,000 feet and sends it to New York Departure on 127.3 to be vectored back around. It landed on its second try at 20:09Z.
A go-around jet is suddenly a departure nobody planned for. The tower gives it a heading and an altitude straight away, then hands it to the radar controller to bring it back into line.
What is a Brasher warning?
"ExecJet 398, possible pilot deviation, advise ready to copy a phone number."
This will be looked into. Write down this number and call us.
"[Phone number] for ExecJet 398. And check your tapes on that, please, and we'll do the same."
That scripted line is a Brasher warning, named after an NTSB case. It tells the crew the FAA may follow up, so they can write down what happened while it's fresh. It is the controller's report, not a verdict.
"We will. Contact Departure, good day."
From the line-up call to the handoff took under three minutes. The part that mattered, from the readback to the go-around, took about 20 seconds.
What this one teaches
Three habits that keep crossing-runway airports safe, and why each one mattered here.
A readback is a question
"Cleared for takeoff" from an airplane you told to wait should stop everything. Readbacks only work if someone catches the wrong one.
Line up and wait means wait
The FAA says it plainly: it is not a takeoff clearance. If a crew isn't sure the clearance was theirs, asking costs five seconds.
Go around early
The CRJ900 crew stopped descending at about 150 feet and climbed away. A go-around is always available, and it worked here.
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
Delta 5415 LaGuardia near miss: common questions
How close did Delta 5415 and the NetJets jet get?
No official separation figure has been published. Our reconstruction from Flightradar24 ADS-B data puts them about 410 feet apart horizontally at 19:56:28Z, with the Phenom still on runway 13 at 100 knots and the CRJ900 reporting 225 feet as it climbed away over the runway intersection. ABC7, citing Flightradar24, reported about 1,000 feet.
Was the NetJets jet cleared for takeoff?
The FAA said ExecJet 398 departed on an intersecting runway without air traffic control authorization. On the published recording, the tower told ExecJet 398 to line up and wait on runway 13, and no takeoff clearance to it can be heard. The crew read back a takeoff clearance right after a landing clearance meant for another flight, and later told the tower they believed they had been cleared.
Who was at fault?
The FAA is investigating and has not published a finding or a severity rating. The controller reported a possible pilot deviation on frequency, which is the controller's first report, not a conclusion. The crew disputed it on frequency and asked the tower to check the tapes.
What does "line up and wait" mean?
It tells a pilot to taxi onto the departure runway, line up and stop there. The FAA's Aeronautical Information Manual says line up and wait is not an authorization to take off. The pilot needs a separate "cleared for takeoff" call.
Why did Delta 5415 go around?
Delta said the crew "initiated a go-around to ensure safe spacing with a departing aircraft on a nearby runway." ADS-B shows the CRJ900 stop descending at about 150 feet and start climbing at 19:56:26Z, as the Phenom accelerated toward the intersection.
Is this the same as the May 2025 LaGuardia near miss?
No. This page covers October 7, 2026: Endeavor Air flight 5415, flying as Delta Connection, and NetJets flight ExecJet 398. The May 2025 LaGuardia close call involved different flights.
Was anyone hurt?
No injuries were reported. The CRJ900 landed at LaGuardia at 20:09Z, about 12 minutes after the go-around, and the Phenom flew on to Teterboro.
Every word on frequency
LaGuardia Tower, 19:54:58Z to 19:57:41Z
| 19:54:58Z | LaGuardia Tower | United 1504, traffic 3 miles final for runway 22, runway 13, cleared for takeoff. Wind 190 at 12 gusts 16. |
|---|---|---|
| 19:55:01Z | United 1504 | Cleared for takeoff 13, United 1504. |
| 19:55:05Z | LaGuardia Tower | ExecJet 398, LaGuardia Tower, runway 13, line up and wait, traffic 3 miles final 22. |
| 19:55:08Z | ExecJet 398 | 13, line up and wait, ExecJet 398. |
| 19:55:16Z | Brickyard 4569 | LaGuardia Tower, Brickyard 4569, ILS 22. |
| 19:55:19Z | LaGuardia Tower | Brickyard 4569, LaGuardia Tower, good afternoon. Runway 22, cleared to land, wind 190 at 13. Number 2 following a CRJ-900 on a mile and a half final. Traffic in position runway 13 will depart prior to your arrival. |
| 19:55:29Z | Brickyard 4569 | Runway 22, cleared to land, Brickyard 4569. |
| 19:55:46Z | LaGuardia Tower | United 1504, contact Departure. |
| 19:55:49Z | United 1504 | Over to Departure, United 1504, good day. |
| 19:55:51Z | Brickyard 4513 | Tower, Brickyard 4513, visual 22. |
| 19:55:54Z | LaGuardia Tower | Brickyard 4513, LaGuardia Tower, good afternoon, runway 22, cleared to land, wind 180 at 13. Traffic in position runway 13 will depart prior to your arrival. You're number 3 following a CRJ, correction, an E170, 3 and a half miles ahead. |
| 19:56:04Z | ExecJet 398 | Roger that, cleared for takeoff runway 13, for ExecJet 398. |
| 19:56:10Z | Brickyard 4513 | And cleared to land for Brickyard 4513. |
| 19:56:31Z | LaGuardia Tower | [In the background] That guy is going around. |
| 19:56:37Z | LaGuardia Tower | ExecJet 398, I believe you were never cleared for takeoff, sir. You were cleared to line up and wait. |
| 19:56:43Z | ExecJet 398 | No, I believe we got the cleared for takeoff. And we were told that the United was ahead, wake turbulence and everything. |
| 19:56:52Z | LaGuardia Tower | Negative. I never said anything about wake turbulence. |
| 19:56:55Z | LaGuardia Tower | Endeavor 5415, fly runway heading, climb and maintain 2,000. [Unclear, sounds like "no traffic overhead."] |
| 19:56:59Z | Endeavor 5415 | Runway heading, 2,000, 5415. |
| 19:57:01Z | LaGuardia Tower | Endeavor 5415, fly runway heading, climb and maintain 3,000. |
| 19:57:04Z | Endeavor 5415 | Climbing 3,000, 5415. |
| 19:57:07Z | LaGuardia Tower | Endeavor 5415, contact Departure 127.3. |
| 19:57:10Z | Endeavor 5415 | 127.3, 5415. |
| 19:57:12Z | LaGuardia Tower | ExecJet 398, contact New York Departure 120.4. Actually, before you go… |
| 19:57:24Z | LaGuardia Tower | ExecJet 398, possible pilot deviation, advise ready to copy a phone number. |
| 19:57:27Z | ExecJet 398 | Go ahead. |
| 19:57:29Z | ExecJet 398 | [Phone number] for ExecJet 398. And check your tapes on that, please, and we'll do the same. |
| 19:57:41Z | LaGuardia Tower | We will. Contact Departure, good day. |
Radio audio was recorded by ATC.com and published by VASAviation. Aircraft positions are ADS-B data from Flightradar24. The scope above is our own drawing of that data. Our transcript was checked against the recording's captions and on-screen subtitles and may differ slightly from the audio. Times to 19:56:49Z are read from the video's radar clock; later times are estimated from the video's running time. A phone number read on frequency is left out.
Sources
Incident audio, statements and flight data
- VASAviation: NEAR TRAGEDY | Business Jet Taking Off without Clearance!, published October 16, 2026. The published LaGuardia Tower recording used for our transcript, with audio from ATC.com. This is a third-party publication of the radio audio, not an FAA report.
- Local 12: Runway close call: Delta flight aborts landing after unauthorized business jet departure, October 15, 2026. Quotes the FAA's statement that the Endeavor Air Flight 5415 crew performed a go-around after ExecJet Flight 398 departed on an intersecting runway without air traffic control authorization, and that the FAA is investigating.
- AVweb: Business Jet Takes Off Without Clearance At LaGuardia, October 14, 2026. Reports Delta's statement to ABC7 that the crew initiated a go-around, and ABC7's Flightradar24-based figure of about 1,000 feet.
- Simple Flying: Delta LaGuardia aborted landing near miss with a private jet, October 15, 2026. Reports the runways (22 and 13), the flights' origin and destination, and the radio exchange.
- Flightradar24. The replay and closest-approach calculation use Flightradar24 API ADS-B positions for EDV5415 and EJA398 on October 7, 2026, and its flight summary for the CRJ900's landing time. This provider link is not a permanent archive of those flight tracks; the distances and timing are our analysis, not an official separation finding.
- Runway positions are from OpenStreetMap (pavement ends) and the wind from the 19:55Z KLGA weather report shown in the published video.
Primary FAA procedure references
- Aeronautical Information Manual, paragraph 5-2-5: Line Up and Wait (LUAW). States that line up and wait is not an authorization to take off.
- FAA Order JO 7110.65, paragraph 3-9-4: Line Up and Wait (LUAW). The tower's procedures for holding a departure in position on the runway.
- FAA Order JO 7110.65, paragraph 3-9-8: Intersecting Runway/Intersecting Flight Path Operations. When a departure may begin its takeoff roll with traffic on a crossing runway.
- FAA Order JO 7110.65, paragraph 2-4-3: Pilot Acknowledgment/Read Back. The controller's duty to check readbacks and correct errors.
- FAA Order JO 7110.65, paragraph 2-1-27: Possible Pilot Deviation Notification. The prescribed notification and the FAA's explanation of the term Brasher warning.
These FAA links explain procedures; they are not incident investigation records and do not establish cause or fault. The FAA statement above was reported by news outlets; we have not found it published on faa.gov, and we have not found an NTSB investigation record or an FAA report or severity rating for this event as of November 17, 2026. This breakdown is an educational reconstruction from the published audio, public statements and ADS-B data, not an official finding. The linked FAA pages are maintained online and may change; they describe current procedures, which we believe match those in force on October 7, 2026.