Alaska 294 at Newark: how a 737 went around over a FedEx 777 on intersecting runways
On a gusty March night, Newark Tower cleared a FedEx 777 to land on runway 29 and an Alaska 737 MAX 9 to land behind it on runway 22L, two runways that cross. Seconds from touchdown, the Alaska jet was told to go around, and it climbed away over the FedEx. Follow both finals on our replay of the ADS-B data and decode the radio as it happens.
What happened
On Tuesday, March 17, 2026, at about 8:17 p.m. local time, Alaska Airlines 294, a Boeing 737 MAX 9 from Portland, was on short final for Newark runway 22L when the tower told it to go around. FedEx 721, a Boeing 777 freighter from Memphis, was landing at the same moment on runway 29, which crosses 22L. The FAA said the go-around was issued because FedEx had been cleared to land on the intersecting runway. The Alaska jet climbed away over the FedEx; ABC News reported preliminary Flightradar24 data showing about 300 to 325 feet between them. Both landed safely, and the NTSB opened an investigation.
| Date and time | Tue 17 Mar 2026, 20:17 EDT (Wed 18 Mar, 00:17Z), night |
|---|---|
| Airport | Newark Liberty International (EWR), landing 22L and 29; wind 260° at 16 kt, gusts 22 (NTSB, 20:00 observation) |
| Aircraft 1 | Alaska 294 (ASA294), Boeing 737 MAX 9, N738AL, Portland to Newark, runway 22L |
| Aircraft 2 | FedEx 721 heavy (FDX721), Boeing 777 freighter, N853FD, Memphis to Newark, runway 29 |
| Closest point | No official figure yet. Reported: 300 to 325 ft vertically (preliminary Flightradar24 data, per ABC News). Our ADS-B feed has no positions for either jet after 00:16:39Z. |
| Controllers | Newark Approach (N90), then Newark Tower |
| Outcome | Alaska 294 went around and landed on a later approach; no injuries or damage (NTSB). NTSB Class 4 investigation OPS26LA027 |
How Newark's crossing runways work
It's 8:09 on a Tuesday night in New Jersey, and a gusty wind is blowing from the west. Newark has two long parallel runways, 4L/22R and 4R/22L, and a shorter one, 11/29, that runs east to west across their north end.
With a strong westerly, some arrivals land on runway 29, more nearly into the wind, while others land on 22L. Both come in from the north-east, and their paths meet over the corner of the airport.
Runway 22L's pavement runs north past its landing threshold and crosses runway 29 just inside 29's threshold. An airplane on final for 22L flies right over runway 29 in the last few hundred feet of its descent.
Alaska from the west, FedEx just ahead of it
The amber target is Alaska 294, a 737 MAX 9 inbound from Portland. The blue one is FedEx 721, a 777 freighter from Memphis, about 7 miles to the east and a little lower. Newark Approach is steering both onto long finals from the north.
The dashed lines show each runway's final approach course: amber for 22L, blue for 29.
- ASA294
- Callsign: Alaska 294
- 049
- Altitude in hundreds of feet: 4,900 ft
- B39M
- Aircraft type: Boeing 737 MAX 9
- B77L
- Aircraft type code FedEx's 777 freighter broadcasts
"Alaska 294, you're gonna look for traffic landing runway 2-9, at 12 o'clock and 5 miles, southbound, a heavy 7-7-7 at 3[,000]."
There's a big FedEx jet ahead of you, going to the crossing runway. Look for it.
The Alaska crew's reply is clipped in the recording. Only "…Alaska 294" survives.
What is visual separation?
"Alaska 294, maintain visual separation with them, turn right heading 1-6-0."
You keep yourself clear of that FedEx by eye. Turn right to 160.
Normally a radar controller keeps jets 3 miles or 1,000 feet apart. With visual separation, the pilot takes that job for this one pair. It lets two arrivals fly closer than radar rules allow, which is how a busy airport lands more traffic.
On our ADS-B data they're 5.2 nm apart here, 800 feet apart in height.
"FedEx 721 heavy, cleared for the [RNAV approach] runway 2-9, 170 to [fix], tower on 18.3."
You're cleared for the satellite approach to runway 29. Hold 170 knots to the fix, then call the tower on 118.3.
"Heavy" marks a jet over 300,000 pounds. Its wake is stronger, so controllers add warnings and space behind it.
"Alaska 294, 2 miles from GIMEE, turn right heading 1-9-0, maintain 2,500 until established on the localizer, cleared for the ILS 22L approach."
Turn onto the final for 22L and follow the landing beam down.
Both jets are now on finals that converge on the north-east corner of the airport. FedEx is about 3.5 miles ahead and 800 feet lower.
"FedEx 721 heavy, Newark Tower, wind 2-9-0 at 10, runway 2-9, cleared to land. Caution wake turbulence, in trail of a heavy Airbus 350."
Runway 29 is yours. There's a big Airbus ahead of you, so watch for its wake.
A landing clearance is a promise that the runway will be clear. On crossing runways, the tower has to keep that promise for both runways at once.
"FedEx 721 heavy, you're number 3 in sequence, traffic will be arriving runway 22L behind you. You might see 'em off your right when you're coming in."
There's a jet landing on the crossing runway after you. You may spot it on your right.
The FAA's controller handbook requires the tower to give traffic information to each aircraft using intersecting runways. FedEx just got its half.
Both are headed for the same corner of the airport. Which one should get there first? Tap it on the scope or pick below.
The lines out of each target show where it'll be in one minute. Watch where they point.
"Alaska 294, Newark Tower, wind 2-9-0 at 8, runway 22L, cleared to land. Reduce to final approach speed. You're number 3 in sequence. Traffic, heavy 7-7-7 arriving runway 2-9 prior to you, caution wake turbulence."
You can land on 22L. A big 777 lands on the crossing runway just before you, so watch for its wake.
"All right, cleared to land 22L, Alaska 294."
On paper the plan is simple: FedEx lands and rolls through the crossing, then Alaska passes overhead and lands behind it.
You're the tower. What must be true before Alaska crosses runway 29's threshold?
How close did the planes get?
Our Flightradar24 ADS-B feed stops here. Alaska's last position, at 00:16:28Z, has it at 875 feet, about 2.7 nm from the crossing. FedEx's, at 00:16:39Z, has it at 475 feet, about 1.6 nm from runway 29. At 00:16:28Z they were about 2.4 nm apart and about 300 feet apart in height. Neither jet shows up again in the feed until Alaska climbs out south of the airport at 00:17:58Z.
So we can't measure the closest point ourselves. What has been published:
Official: none yet. The NTSB has not released a closest-approach figure.
Reported: 300 to 325 feet between them, from preliminary Flightradar24 data (ABC News).
In the video: VASAviation's radar overlay, built from Airplanes.Live ADS-B, shows about 0.2 nm and 200 feet at 00:17:21Z.
What is a go-around?
"Alaska 294, Newark Tower, runway, correction, go around."
Don't land. Climb away now.
"Going around, Alaska 294."
A go-around is an aborted landing. The FAA calls it a routine safety procedure, and crews practise it constantly. ABC News, citing the audio and Flightradar24 data, put Alaska about 150 feet up when the call came. The FAA said the controller ordered it because FedEx had been cleared to land on the intersecting runway.
The scope holds at 00:16:26Z, the last moment our feed has both jets; the radio continues.
"Alaska 294, you'll fly runway heading, maintain [altitude]."
"Left on Uniform and we'll contact Ground point 8. You got it, nice job."
Turning off the runway and switching to the ground controller. Thanks.
Our data picks Alaska up again at 00:17:58Z, climbing through 1,175 feet south of the field. Departure took it from there, and Flightradar24 shows it landing at about 00:37Z.
Who was at fault?
No one has been found at fault. The NTSB opened a Class 4 investigation, case OPS26LA027. It says it won't issue a preliminary report and will release a final report when the investigation ends. The FAA is also investigating.
Alaska said its flight was cleared to land and then told to go around, "which our pilots are highly trained for." FedEx said its crew followed ATC instructions and landed safely.
The final report should answer the timing questions the public data can't: where each jet was when the go-around was issued, and how close they really came.
What this one teaches
Three things a tower controller juggles every time two runways cross.
Crossing runways run on seconds
The second arrival can't cross the first one's runway until the first has passed the crossing or will stop short of it. That gap has to be built miles out.
Tell both pilots
The tower gave each crew the other's runway and position. If something goes wrong, both know where to look.
The go-around is the safety valve
When the timing won't work, "go around" fixes it. The earlier it's said, the more room everyone has.
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
Alaska 294 and FedEx 721: common questions
How close did Alaska 294 and FedEx 721 get?
No official figure has been published. ABC News reported that preliminary Flightradar24 data showed the Alaska 737 passing 300 to 325 feet above the FedEx 777. The VASAviation video's radar overlay shows about 0.2 nautical miles and 200 feet at 00:17:21Z. The Flightradar24 API data we used has no positions for either jet between 00:16:39Z and the go-around, so we could not measure the closest point ourselves.
Why did Alaska 294 go around?
The FAA said the tower controller told Alaska 294 to go around because FedEx 721 had been cleared to land on an intersecting runway. Alaska was cleared to land on runway 22L and FedEx on runway 29, and the two runways cross at the north-east corner of the airport.
Who was at fault?
No one has been found at fault. The NTSB opened a Class 4 investigation, case OPS26LA027, and said it will issue a final report but no preliminary report. The FAA is also investigating. Alaska said its flight was cleared to land and then told to go around; FedEx said its crew followed ATC instructions.
What is a go-around?
A go-around is an aborted landing: the crew adds power, climbs away and comes back for another approach. The FAA calls it a routine safety procedure. Controllers issue one whenever the runway or the airspace ahead will not be clear in time.
Do Newark's runways 22L and 29 cross?
Yes. The north end of runway 4R/22L crosses runway 11/29 close to the runway 29 threshold, so an airplane on final for 22L passes over runway 29 shortly before it reaches 22L's landing threshold. The NTSB's estimated location for this event falls on that crossing.
What is visual separation?
When a pilot reports another aircraft in sight and is told to maintain visual separation, the pilot keeps clear by eye instead of the controller keeping 3 miles or 1,000 feet between them. Newark Approach told Alaska 294 to maintain visual separation with the FedEx 777 about five minutes before the go-around.
Was anyone hurt?
No. The NTSB lists no injuries and no damage to either airplane. Alaska 294 carried 181 people (175 passengers and 6 crew) and FedEx 721 carried 2 crew. Both landed safely, Alaska on its second approach.
Every word on frequency
Newark Approach and Newark Tower, 00:05:59Z to 00:18:14Z
| 00:05:59Z | Newark Approach | FedEx 721 heavy, turn right heading 100. |
|---|---|---|
| 00:06:02Z | FedEx 721 | FedEx 721, heading 100. |
| 00:06:57Z | Newark Approach | Alaska 294, turn right heading 090. |
| 00:06:59Z | Alaska 294 | 090, Alaska 294. |
| 00:07:25Z | Newark Approach | FedEx 721 heavy, reduce speed to 190. |
| 00:07:28Z | FedEx 721 | FedEx 721, speed 190. |
| 00:07:30Z | Newark Approach | Alaska 294, reduce speed to 190. |
| 00:07:32Z | Alaska 294 | 190, Alaska 294. |
| 00:11:39Z | Newark Approach | Alaska 294, you're gonna look for traffic landing runway 29, at 12 o'clock and 5 miles, southbound, a heavy 777 at 3[,000]. |
| 00:11:47Z | Alaska 294 | [clipped] Alaska 294. |
| 00:11:49Z | Newark Approach | Alaska 294, maintain visual separation with them, turn right heading 160. |
| 00:11:54Z | Alaska 294 | Heading 160, Alaska 294. |
| 00:12:03Z | Newark Approach | FedEx 721 heavy, cleared for the [RNAV approach] runway 29, 170 to [fix], tower on 18.3. |
| 00:12:15Z | FedEx 721 | FedEx 721, cleared for the [RNAV approach], 170 to [fix], tower is 18.3. |
| 00:12:27Z | Newark Approach | [United] 1076, turn 15 degrees to the left and speed 180, please. |
| 00:12:37Z | Newark Approach | United 1076, 15 left, speed 180. |
| 00:12:43Z | United 1076 | 15 left, speed 180, United 1076. |
| 00:12:49Z | Newark Approach | Alaska 294, descend and maintain 2,500. |
| 00:12:55Z | Alaska 294 | 2,500, Alaska 294. |
| 00:13:44Z | Newark Approach | Alaska 294, 2 miles from GIMEE, turn right heading 190, maintain 2,500 until established on the localizer, cleared for the ILS 22L approach, and reduce to your final approach speed. |
| 00:14:02Z | Alaska 294 | 190, [number] until established, cleared ILS 22L, Alaska 294. |
| 00:14:10Z | FedEx 721 | Tower, FedEx 721, [fix]. |
| 00:14:13Z | Newark Tower | FedEx 721 heavy, Newark Tower, wind 290 at 10, runway 29, cleared to land. Caution wake turbulence, in trail of a heavy Airbus 350. |
| 00:14:22Z | FedEx 721 | Cleared to land runway 29, FedEx 721. |
| 00:14:30Z | Newark Approach | Alaska 294, all the way back on the speed for me, please, and the tower's 18.3. |
| 00:14:35Z | Alaska 294 | Going to tower, good night, Alaska 294. |
| 00:14:39Z | Newark Tower | FedEx 721 heavy, you're number 3 in sequence, traffic will be arriving runway 22L behind you. You might see 'em off your right when you're coming in. |
| 00:14:52Z | Alaska 294 | Tower, Alaska 294, ILS 22L. |
| 00:14:54Z | Newark Tower | United 2175, wind 290 at 8, runway 22R at M, cleared for takeoff. |
| 00:14:59Z | United 2175 | Cleared for takeoff 22R at M, United 2175. |
| 00:15:04Z | Newark Tower | Brickyard 3613, contact New York Departure. |
| 00:15:06Z | Brickyard 3613 | Departure, Brickyard 3613, see ya. |
| 00:15:10Z | Alaska 294 | Tower, Alaska 294, ILS 22L. |
| 00:15:13Z | Newark Tower | Alaska 294, Newark Tower, wind 290 at 8, runway 22L, cleared to land. Reduce to final approach speed. You're number 3 in sequence. Traffic, heavy 777 arriving runway 29 prior to you, caution wake turbulence. |
| 00:15:24Z | Alaska 294 | All right, cleared to land 22L, Alaska 294. |
| 00:17:15Z | Newark Tower | Alaska 294, Newark Tower, runway, correction, go around. |
| 00:17:18Z | Alaska 294 | Going around, Alaska 294. |
| 00:17:23Z | Newark Tower | Alaska 294, you'll fly runway heading, maintain [altitude]. |
| 00:17:26Z | Alaska 294 | Runway heading, 2,000, Alaska 294. |
| 00:17:32Z | United 1076 | Tower, United 1076, [RNAV approach] 29. |
| 00:17:41Z | Newark Tower | Alaska 294, contact Newark Departure. |
| 00:17:44Z | Alaska 294 | Departure, Alaska 294. |
| 00:17:47Z | Alaska 294 | Got that freq, 294? |
| 00:17:50Z | Newark Tower | 119.2. |
| 00:17:55Z | Newark Tower | FedEx 721 heavy, left turn onto Uniform and contact Ground point 8. |
| 00:17:59Z | FedEx 721 | Left on Uniform and we'll contact Ground point 8. You got it, nice job. |
| 00:18:09Z | Newark Tower | United 1076, Newark Tower, wind 300 at 10, gusts 15, runway 29, cleared to land. |
| 00:18:14Z | United 1076 | 29, cleared to land, United 1076. |
Radio audio was recorded by LiveATC.net and published by VASAviation, which trims some unrelated calls. Aircraft positions are ADS-B data from Flightradar24. The scope above is our own drawing of that data. Times are approximate: they come from the radar clock in the published video, whose radar replay is sped up in places. Unclear words are in [brackets], and the transcript may differ slightly from the audio.
Sources
Incident records, audio and flight data
- NTSB Aviation Investigation Notification, OPS26LA027. The NTSB's case record: date and time (20:17 local), both aircraft and registrations, weather, people aboard, no injuries or damage, and the estimated location. It says this Class 4 investigation will have no preliminary report and a final report at its conclusion. Checked November 17, 2026; no final report had been published.
- Associated Press via Anchorage Daily News, March 19, 2026. The FAA's account of why the go-around was issued, the NTSB's description that the 737 overflew the 777, and the airlines' statements.
- ABC7 New York, March 19, 2026. The reported 300 to 325 feet from preliminary Flightradar24 data, and the roughly 150-foot height at the go-around call. These are news reports, not official findings.
- VASAviation: CLOSE CALL at Newark, published March 20, 2026. The published LiveATC recording used for our transcript, and the radar overlay (from Airplanes.Live ADS-B) showing about 0.2 nm and 200 feet. This is a third-party publication, not an FAA release.
- Flightradar24. Our replay uses Flightradar24 ADS-B positions for ASA294 and FDX721 exported through its API. The feed has no positions for either jet from 00:16:39Z until Alaska reappears at 00:17:58Z, so the scope stops there. Its altitudes are pressure altitudes, not corrected for Newark's altimeter setting. The provider homepage is not an archive of these tracks, and the distances on this page are our analysis, not an official separation finding.
- OpenStreetMap. Runway outlines for the scope, including the north end of 4R/22L where it crosses 11/29.
Primary FAA procedure references
- FAA Order JO 7110.65, paragraph 3-10-4: Intersecting Runway/Intersecting Flight Path Operations. The traffic information and separation the tower must give arrivals to intersecting runways.
- FAA Order JO 7110.65, paragraph 7-2-1: Visual Separation. When and how controllers may use visual separation, including pilot-applied visual separation.
These FAA links explain procedures; they are not incident investigation records and do not establish cause or fault. The NTSB's final report has not been published as of November 17, 2026. This breakdown is an educational reconstruction from the published audio, news reports and ADS-B data. The linked FAA pages are maintained online and may change.