Diversion — EJA471

KTPA · 19R

2025-10-22 15:09 UTC· KPBI → KLAL· 130R LLC, SISK ALBERT WILSON, BERG CHARLES, BROWN GEORGE GARVIN · E55P

▶ Replay 📊 Analyse

EJA471 (130r) was operating from KPBI to KVDF (Tampa Executive Airport) on 2025-10-22. SkyMeter detected a diversion to Tampa International Airport (KTPA) on runway 19R at 15:09 UTC. Peak cruise altitude FL190, turnaround area near Glades, US. Approach stability score: 32/100. Scores below 50 occur on under 10% of approaches at this runway and indicate the v2 scorer flagged the approach as highly anomalous (three or more gates exceeded the runway's P90 envelope simultaneously). METAR at the time reported 5 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 19R
  • 11 ft AGL at event
  • 120 kt ground speed
  • 0 fpm vertical
  • Approach stability 32/100
  • 5 kt wind
  • 0 kt crosswind component
  • 16,093 m visibility
  • KTPA 080930Z AUTO 05003KT 10SM OVC013 24/23 A2984 RMK T02400230 MADISHF

Flight context

  • EJA471
  • 130r
  • E55P
  • KPBI → KLAL
  • 2025-10-22 15:09 UTC
  • KTPA runway 19R

All events on this flight

Diversion 15:09:04 UTC · KTPA runway 19R · 11 ft AGL · 120 kt GS
Long landing rollout 15:09:04 UTC · KLAL runway 05 · 42 ft AGL · 4 kt GS
Diversion 15:09:04 UTC · KLAL runway 05 · 141 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· KTPA