Return to field — N52HR

N52HR (Barracuda Aviation) had departed KTME on 2026-05-20. SkyMeter detected a return to field at Houston Executive Airport (KTME) at 11:31 UTC. Peak cruise altitude FL426, turnaround area near Tulia, US. METAR at the time reported 0 kt wind, 16,093 m visibility. Detection algorithm and known limitations: see SkyMeter methodology.

• 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 →
• HAZARDS6/0618 2026-05-15 13:00Z – 2026-05-28 04:00Z SFC–13,500 ft

  22NM NE RUIDOSO, NM, Friday, May 15, 2026 through Thursday, May 28, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/0887 2026-05-16 18:37Z – 2026-05-30 04:00Z SFC–10,500 ft

  19NM SW TUCUMCARI, NM, Saturday, May 16, 2026 through Saturday, May 30, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1015 2026-05-18 00:28Z – 2026-06-01 04:00Z SFC–15,500 ft

  22NM NE RUIDOSO, NM, Monday, May 18, 2026 through Monday, June 1, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1358 2026-05-19 00:52Z – 2026-06-02 02:00Z SFC–10,000 ft

  5NM S CAMPO, CO, Tuesday, May 19, 2026 through Tuesday, June 2, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1337 2026-05-19 01:30Z – 2026-05-21 01:30Z SFC–6,000 ft

  9NM NW ASHLAND, KS, Tuesday, May 19, 2026 through Thursday, May 21, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1338 2026-05-19 01:30Z – 2026-05-21 01:30Z SFC–6,000 ft

  4NM SE MEADE, KS, Tuesday, May 19, 2026 through Thursday, May 21, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1626 2026-05-19 22:38Z – 2026-06-02 04:00Z SFC–15,500 ft

  22NM NE RUIDOSO, NM, Tuesday, May 19, 2026 through Tuesday, June 2, 2026 UTC

  View FAA NOTAM →
• SECURITY6/1676 2026-05-20 12:00Z – 2026-05-24 23:00Z SFC–400 ft

  McKinney, TX, Wednesday, May 20, 2026 through Sunday, May 24, 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.

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