United flight UA2364 emergency lands Bradley

United Airlines flight UA2364 diverted to Bradley International Airport in Windsor Locks, Connecticut, on May 20 while operating from Miami to Newark, according to flight-tracking records. FlightAware and Flightradar24 both showed the aircraft as a Boeing 737 MAX 9 and listed the flight as diverted after it left Miami behind schedule. Travel And Tour World separately reported the episode as an emergency landing at Bradley. United had not published a public explanation visible in the sources reviewed. FlightAware showed UA2364 departing Miami International Airport at 3:49 p.m. EDT on Wednesday, May 20, and arriving at Bradley at 8:00 p.m. EDT. The same record showed the aircraft later leaving Bradley at 8:25 p.m. for Newark, with arrival on Thursday, May 21, after a long overnight delay. Flightradar24 listed the same May 20 Miami-to-Newark leg as “Diverted to BDL.” ### Was this flight actually headed to New York, and which airport? UA2364 was headed to Newark Liberty International Airport, not LaGuardia or JFK, according to the flight-tracking records reviewed. Newark is one of the three main New York-area airports, and some secondary reports described the route more broadly as Miami to New York. FlightAware and Flightradar24 both identified the scheduled destination as EWR, the airport code for Newark. (flightaware.com) That distinction matters because Newark was already facing weather-related disruption on May 20. United’s Jetstream operations page posted an “East Coast Thunderstorms” waiver for May 20 affecting EWR along with Baltimore, Washington, LaGuardia and Philadelphia. The FAA’s National Airspace System dashboard was also active on May 21 for current system status. ### What do the records actually show about the diversion? (flightaware.com) FlightAware’s history page showed UA2364 as a Miami-to-Newark flight that was diverted, then continued from Bradley to Newark later the same evening. The record listed the aircraft type as B39M, the code commonly used for the Boeing 737 MAX 9, and showed the Miami departure coming roughly 1 hour and 29 minutes after the scheduled 2:20 p.m. departure. Flightradar24’s history page matched the diversion to BDL and identified the aircraft registration as N37537 for that May 20 leg. (jetstream.united.com) Travel And Tour World described the stop at Bradley as an emergency landing after a major delay on the Miami-New York route. That report was visible in the outlet’s May 21 latest-news listing, but the listing did not provide a cause in the excerpt available through search results. No FAA incident notice or United statement explaining the reason was surfaced in the material reviewed. (flightaware.com) ### How long was the delay? FlightAware showed the Bradley-to-Newark continuation departing at 8:25 p.m. EDT on May 20 and arriving at Newark at 10:29 a.m. EDT on May 21, which it listed as 16 hours and 54 minutes late. The same page showed the original Miami-to-Bradley segment reaching Bradley at 8:00 p.m. EDT. Those records indicate passengers faced a lengthy interruption after the diversion. (travelandtourworld.com) Bradley International’s public arrivals-and-departures page provides live flight-status information, but the page snapshot available during reporting did not include a historical entry for UA2364. Bradley’s main site identifies the airport as being operated by the Connecticut Airport Authority. ### What can be verified, and what remains unclear? The verifiable facts are narrow. (flightaware.com) FlightAware and Flightradar24 both support that UA2364 operated on May 20 from Miami toward Newark, diverted to Bradley, and later continued on to Newark. Travel And Tour World reported the stop as an emergency landing. What remains unclear is the cause. No public statement from United explaining whether the diversion was driven by weather, a mechanical issue, crew constraints or air-traffic conditions was visible in the sources reviewed, and no FAA incident entry tied to UA2364 was found during this reporting. (bradleyairport.com) United’s public flight-status page and travel-alert pages, along with FlightAware, Flightradar24 and any FAA incident postings, are the next places where a formal explanation could appear. (flightaware.com) (united.com)