Return to field — ARR352
KTME · 182026-07-09 16:43 UTC· KTME → KTME· AVALAIR AIRCRAFT MANAGEMENT LLC· C25B
ARR352 (Avalair Aircraft Management) was operating from KTME to KTME (Houston Executive Airport) on 2026-07-09. SkyMeter detected a return to field at Houston Executive Airport (KTME) on runway 18 at 16:43 UTC. Peak cruise altitude FL434, turnaround area near Armstrong, US. 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/4240 2026-03-08 08:00Z – 2026-11-01 07:00Z SFC–180 ft
SAN ANGELO, TX, Sunday, March 8, 2026 through Sunday, November 1, 2026 Local
View FAA NOTAM → - SECURITY6/3954 2026-06-01 00:00Z – 2026-07-20 23:59Z
STILLWATER, OK, Monday, June 1, 2026 through Monday, July 20, 2026 UTC
View FAA NOTAM → - SECURITY6/3996 2026-06-01 00:00Z – 2026-07-20 23:59Z
OKLAHOMA CITY, OK, Monday, June 1, 2026 through Monday, July 20, 2026 UTC
View FAA NOTAM → - SECURITY6/4141 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
Tulsa, OK, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4030 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
AUSTIN, TX, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4025 2026-06-01 05:00Z – 2026-07-21 04:59Z
DENTON, TX, Monday, June 1, 2026 through Tuesday, July 21, 2026 UTC
View FAA NOTAM → - SECURITY6/4022 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
OKLAHOMA CITY, OK, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4019 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
IRVING, TX, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4009 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
FRISCO, TX, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4008 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
FRISCO, TX, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4002 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
FORT WORTH, TX, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4000 2026-06-01 05:00Z – 2026-07-21 04:59Z
MANSFIELD, TX, Monday, June 1, 2026 through Tuesday, July 21, 2026 UTC
View FAA NOTAM → - SECURITY6/3999 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
ARLINGTON, TX, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/3997 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
NORMAN, OK, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/3952 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
Stillwater, OK, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - HAZARDS6/1156 2026-06-28 14:00Z – 2026-07-12 03:00Z SFC–12,500 ft
32NM NW TAOS, NM, Sunday, June 28, 2026 through Sunday, July 12, 2026 UTC
View FAA NOTAM → - HAZARDS6/1169 2026-06-28 14:00Z – 2026-07-12 03:00Z SFC–12,500 ft
32NM NW TAOS, NM, Sunday, June 28, 2026 through Sunday, July 12, 2026 UTC
View FAA NOTAM → - HAZARDS6/1333 2026-06-29 03:06Z – 2026-07-13 04:00Z SFC–17,000 ft
8NM SW LEADVILLE, CO, Monday, June 29, 2026 through Monday, July 13, 2026 UTC
View FAA NOTAM → - HAZARDS6/1416 2026-06-29 14:37Z – 2026-07-14 04:00Z SFC–13,500 ft
15NM NW CAÑON CITY, CO, Monday, June 29, 2026 through Tuesday, July 14, 2026 UTC
View FAA NOTAM → - SECURITY6/6840 2026-06-29 15:07Z – 2026-07-21 04:59Z SFC–400 ft
Mansfield, TX
View FAA NOTAM → - SECURITY6/6842 2026-06-29 15:07Z – 2026-07-21 04:59Z SFC–400 ft
Fort Worth, TX
View FAA NOTAM → - HAZARDS6/1584 2026-06-29 18:38Z – 2026-07-13 04:00Z SFC–12,500 ft
32NM NW TAOS, NM, Monday, June 29, 2026 through Monday, July 13, 2026 UTC
View FAA NOTAM → - HAZARDS6/1594 2026-06-29 18:49Z – 2026-07-13 03:00Z SFC–12,500 ft
32NM NW TAOS, NM, Monday, June 29, 2026 through Monday, July 13, 2026 UTC
View FAA NOTAM → - HAZARDS6/1775 2026-06-30 06:00Z – 2026-07-14 04:00Z SFC–15,000 ft
4NM SW PUEBLO, CO, Tuesday, June 30, 2026 through Tuesday, July 14, 2026 UTC
View FAA NOTAM → - HAZARDS6/2312 2026-07-01 04:00Z – 2026-07-15 04:00Z SFC–14,000 ft
20NM W WALSENBURG, CO, Wednesday, July 1, 2026 through Wednesday, July 15, 2026 UTC
View FAA NOTAM → - SECURITY6/6843 2026-07-01 16:07Z – 2026-07-21 04:59Z SFC–400 ft
Frisco, TX
View FAA NOTAM → - SECURITY6/6844 2026-07-01 16:07Z – 2026-07-21 04:59Z SFC–400 ft
Frisco, TX
View FAA NOTAM → - HAZARDS6/2597 2026-07-02 04:41Z – 2026-07-16 04:00Z SFC–15,000 ft
4NM SW PUEBLO, CO, Thursday, July 2, 2026 through Thursday, July 16, 2026 UTC
View FAA NOTAM → - HAZARDS6/2942 2026-07-05 12:00Z – 2026-07-19 04:00Z SFC–17,000 ft
2NM W LEADVILLE, CO, Sunday, July 5, 2026 through Sunday, July 19, 2026 UTC
View FAA NOTAM → - HAZARDS6/3007 2026-07-06 12:00Z – 2026-07-20 04:00Z SFC–17,000 ft
1NM W LEADVILLE, CO, Monday, July 6, 2026 through Monday, July 20, 2026 UTC
View FAA NOTAM → - HAZARDS6/3274 2026-07-07 00:35Z – 2026-07-20 04:00Z SFC–17,000 ft
1NM W LEADVILLE, CO, Tuesday, July 7, 2026 through Monday, July 20, 2026 UTC
View FAA NOTAM → - HAZARDS6/3801 2026-07-08 01:49Z – 2026-07-23 04:00Z SFC–15,000 ft
1NM W PUEBLO, CO, Wednesday, July 8, 2026 through Thursday, July 23, 2026 UTC
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
- 43478 ft AGL at event
- 439 kt ground speed
- 0 fpm vertical
- 0 kt wind
- 0 kt crosswind component
- 16,093 m visibility
- METAR KTME 300835Z AUTO 00000KT 10SM FEW036 FEW042 25/24 A2988 RMK AO2
Flight context
- ARR352
- Avalair Aircraft Management
- C25B
- KTME → KTME
- 2026-07-09 16:43 UTC
- KTME runway 18
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