Diversion — EJA919

KLFT · 04R

2026-07-05 21:24 UTC· KMCO → KLFT· TUPELO TRAVEL LLC, BOSCACCI GROUP LLC, BOWLIN JOHN D, JOHNSON KR· C68A

▶ Replay 📊 Analyse

EJA919 (Tupelo Travel) was operating from KMCO to KBTR (Baton Rouge Metropolitan Airport) on 2026-07-05. SkyMeter detected a diversion to Lafayette Regional Airport (KLFT) on runway 04R at 21:24 UTC. Peak cruise altitude FL453, turnaround area near Wright, US. METAR at the time reported 7 kt wind, 1 kt crosswind component, 16,093 m visibility. Detection algorithm and known limitations: see SkyMeter methodology.

Active FAA TFR during this flight

Source: FAA TFR archive (hourly snapshot)
  • SECURITY6/4153 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

    Tampa, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/4156 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

    TAMPA, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/7880 2026-07-05 14:07Z – 2026-07-21 03:59Z SFC–400 ft

    Tampa, FL

    View FAA NOTAM →
  • SECURITY6/7881 2026-07-05 14:07Z – 2026-07-21 03:59Z SFC–400 ft

    Tampa, FL

    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 04R
  • 33 ft AGL at event
  • 120 kt ground speed
  • 0 fpm vertical
  • 7 kt wind
  • 1 kt crosswind component
  • 16,093 m visibility
  • KLFT 161753Z VRB06KT 10SM SCT046 SCT070 33/24 A3017 RMK AO2 SLP217 T03280244 10328 20250 58003

Flight context

  • EJA919
  • Tupelo Travel
  • C68A
  • KMCO → KLFT
  • 2026-07-05 21:24 UTC
  • KLFT runway 04R

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· KLFT