Return to field — ACES01
KLUF · 21R2026-07-01 15:49 UTC· KLUF → KLUF· TOP ACES CORP· F16
ACES01 (TOP Aces) had departed KLUF on 2026-07-01. SkyMeter detected a return to field at Luke Air Force Base (KLUF) on runway 21R at 15:49 UTC. Peak cruise altitude FL318, turnaround area near Casa Grande, US. Approach stability score: 30/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 0 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)- SECURITY6/3948 2026-06-01 07:00Z – 2026-07-21 06:59Z
MESA, AZ, Monday, June 1, 2026 through Tuesday, July 21, 2026 UTC
View FAA NOTAM → - SECURITY6/3966 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
Mesa, AZ, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/7079 2026-06-27 01:07Z – 2026-07-21 06:59Z SFC–400 ft
Mesa, AZ
View FAA NOTAM → - SECURITY6/7078 2026-06-27 01:07Z – 2026-07-21 06:59Z SFC–400 ft
Mesa, AZ
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 21R
- 31873 ft AGL at event
- 565 kt ground speed
- 0 fpm vertical
- Approach stability 30/100
- 0 kt wind
- 0 kt crosswind component
- 16,093 m visibility
- KLUF 160955Z AUTO 00000KT 10SM CLR 32/19 A2988 RMK AO2 SLP101 T03190188 $
Flight context
- ACES01
- TOP Aces
- F16
- KLUF → KLUF
- 2026-07-01 15:49 UTC
- KLUF runway 21R
All events on this flight
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