Diversion — EJA263

KMIA · 08L

2026-04-23 21:09 UTC· KTEB → KMIA· BRODER TRANSPORT LLC, ARMBRESTER BRADFORD K, CEGG LLC, SENSKE CH· CL60

▶ Replay 📊 Analyse

EJA263 (Broder Transport) was operating from KTEB to KRDU (Raleigh Durham International Airport) on 2026-04-23. SkyMeter detected a diversion to Miami International Airport (KMIA) on runway 08L at 21:09 UTC. Peak cruise altitude FL411, turnaround area near Sneads Ferry, US. Approach stability score: 81/100. Scores in this band are observed on roughly 25% of approaches at this runway: one or more gates outside the per-runway tightest envelope, but still inside the typical operating range. METAR at the time reported 10 kt wind, 16,093 m visibility. Detection algorithm and known limitations: see SkyMeter methodology.

Active FAA TFR during this flight

Source: FAA TFR archive (hourly snapshot)
  • SECURITY5/2809 2025-10-20 12:00Z – 2026-10-20 12:00Z SFC–2,000 ft

    Palm Beach, FL, Monday, October 20, 2025 through Tuesday, October 20, 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 08L
  • 8 ft AGL at event
  • 120 kt ground speed
  • 0 fpm vertical
  • Approach stability 81/100
  • 10 kt wind
  • 0 kt crosswind component
  • 16,093 m visibility
  • KMIA 201253Z 00000KT 10SM -RA SCT024 BKN034 BKN110 BKN250 26/23 A2993 RMK AO2 RAB33 SLP134 CB DSNT SE MOV N P0000 T02560228 $

Flight context

  • EJA263
  • Broder Transport
  • CL60
  • KTEB → KMIA
  • 2026-04-23 21:09 UTC
  • KMIA runway 08L

All events on this flight

Diversion 21:09:52 UTC · KMIA runway 08L · 8 ft AGL · 120 kt GS
Diversion 21:09:52 UTC · KMIA runway 08L · 8 ft AGL · 120 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· KMIA