Diversion — UAL1875

KDTW · 04L

2026-07-27 18:33 UTC· KEWR → KDTW· UNITED AIRLINES INC· B739

▶ Replay 📊 Analyse

UAL1875 (United Airlines) was operating from KEWR to KORD (Chicago O'Hare International Airport) on 2026-07-27. SkyMeter detected a diversion to Detroit Metropolitan Wayne County Airport (KDTW) on runway 04L at 18:33 UTC. Peak cruise altitude FL352, turnaround area near Chautauqua, US. Approach stability score: 89/100. Scores in this band are observed on roughly 50% of approaches at this runway and represent the centerline of normal operations. METAR at the time reported 11 kt wind, 6 kt crosswind component, 6,437 m visibility. Detection algorithm and known limitations: see SkyMeter methodology.

Active FAA TFR during this flight

Source: FAA TFR archive (hourly snapshot)
  • SECURITY6/8486 2026-07-27 15:00Z – 2026-07-27 22:30Z SFC–2,000 ft

    Pontiac, MI, Monday, July 27, 2026 Local

    View FAA NOTAM →
  • VIP6/8367 2026-07-27 16:45Z – 2026-07-27 21:15Z SFC–17,999 ft

    Milford, MI, Monday, July 27, 2026 Local

    View FAA NOTAM →

SkyMeter cross-referenced this flight against FAA-published TFRs that were active during its window and within its geographic bounding box. Overlap doesn't necessarily mean violation — the aircraft may have been outside the TFR’s precise polygon or flying under air-traffic-control coordination.

Pilot review data

  • Runway 04L
  • 642 ft AGL at event
  • 120 kt ground speed
  • 0 fpm vertical
  • Approach stability 89/100
  • 11 kt wind
  • 6 kt crosswind component
  • 6,437 m visibility
  • KDTW 172253Z 03006KT 4SM BR OVC006 19/18 A3019 RMK AO2 RAE13 SLP220 P0000 T01940178

Flight context

  • UAL1875
  • United Airlines
  • B739
  • KEWR → KDTW
  • 2026-07-27 18:33 UTC
  • KDTW runway 04L

All events on this flight

Diversion 18:33:52 UTC · KDTW runway 04L · 642 ft AGL · 120 kt GS
Diversion 18:33:52 UTC · KDTW runway 22R · 0 ft AGL · 0 kt GS

Automated analysis. Events shown on this page (such as go-around, unstable approach, or runway events) are heuristic classifications produced by algorithms from publicly broadcast ADS-B data. They are intended to surface flights of interest for further review — they are not findings of fact, and they do not determine pilot fault, regulatory compliance, or the cause of any occurrence. Coverage gaps and sensor noise can affect accuracy. Only the relevant civil aviation authority or accident investigation body can make official determinations. How we detect events · Dispute or correct this data

SkyMeter · trace data observed via ADS-B· KDTW