Diversion — EJM67
KTYQ · 182026-07-25 22:08 UTC· KPDK → KTYQ· RK-492 LEASING LLC, RSD III LLC· FA50
EJM67 (Rk-492 Leasing) was operating from KPDK to KPDK (DeKalb Peachtree Airport) on 2026-07-25. SkyMeter detected a diversion to Indianapolis Executive Airport (KTYQ) on runway 18 at 22:08 UTC. Peak cruise altitude FL362, turnaround area near Cumberland County, US. Approach stability score: 65/100. Scores in this band occur on roughly 10-15% of approaches at this runway, with multiple gates outside the per-runway envelope. METAR at the time reported 5 kt wind, 3 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/7851 2026-07-23 17:00Z – 2026-07-27 04:59Z SFC–400 ft
Westfield, IN, Thursday, July 23, 2026 through Sunday, July 26, 2026 Local
View FAA NOTAM → - UAS PUBLIC GATHERING6/6521 2026-07-23 21:30Z – 2026-07-26 04:00Z SFC–400 ft
cincinnati, OH, Thursday, July 23, 2026 through Sunday, July 26, 2026 UTC
View FAA NOTAM → - SECURITY6/8361 2026-07-24 13:00Z – 2026-07-27 04:59Z SFC–400 ft
Westfield, IN, Friday, July 24, 2026 through Sunday, July 26, 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
- 922 ft AGL at event
- 120 kt ground speed
- 0 fpm vertical
- Approach stability 65/100
- 5 kt wind
- 3 kt crosswind component
- 16,093 m visibility
- METAR KTYQ 152315Z AUTO 20004KT 10SM CLR 30/21 A3011 RMK AO2 T02950208
Flight context
- EJM67
- Rk-492 Leasing
- FA50
- KPDK → KTYQ
- 2026-07-25 22:08 UTC
- KTYQ runway 18
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