Diversion — EJA491

KTLH · 18

2026-04-08 16:34 UTC· KPBI → KTLH· FIRST HORIZON BANK, SCHERMER GRANT, MACFIN LLC, WESLEY MARK, MOO· E55P

▶ Replay 📊 Analyse

EJA491 (First Horizon Bank) was operating from KPBI to KVRB (Vero Beach Regional Airport) on 2026-04-08. SkyMeter detected a diversion to Tallahassee Regional Airport (KTLH) on runway 18 at 16:34 UTC. Peak cruise altitude FL373, turnaround area near Ridge Manor, US. Approach stability score: 18/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 13 kt wind, 12 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)
  • 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 18
  • 58 ft AGL at event
  • 120 kt ground speed
  • 0 fpm vertical
  • Approach stability 18/100
  • 13 kt wind
  • 12 kt crosswind component
  • 16,093 m visibility
  • METAR KTLH 231353Z 05007KT 10SM SCT012 BKN032 27/23 A3004 RMK AO2 SLP172 T02720233 $

Flight context

  • EJA491
  • First Horizon Bank
  • E55P
  • KPBI → KTLH
  • 2026-04-08 16:34 UTC
  • KTLH runway 18

All events on this flight

Diversion 16:34:15 UTC · KTLH runway 18 · 58 ft AGL · 120 kt GS
Diversion 16:34:15 UTC · KTLH runway 18 · 58 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· KTLH