TfrPenetration — QAF5

2026-07-05 02:59 UTC· KLAS KLAX· GA7C

QAF5 was operating from KLAS to KLAX on 2026-07-05. SkyMeter detected a tfrpenetration at 02:59 UTC. Trace data at the event: 2096 ft AGL, 4 kt GS. METAR at the time reported 5 kt wind, 2 kt crosswind component. Detection algorithm and known limitations: see SkyMeter methodology.

Active FAA TFR during this flight

Source: FAA TFR archive (hourly snapshot)
  • SECURITY6/4189 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft

    Los Angeles, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • UAS PUBLIC GATHERING6/0753 2026-07-02 14:00Z – 2026-07-06 04:00Z SFC–400 ft

    Los Angeles, CA, Thursday, July 2, 2026 through Monday, July 6, 2026 UTC

    View FAA NOTAM →
  • UAS PUBLIC GATHERING6/1486 2026-07-04 14:00Z – 2026-07-06 04:00Z SFC–400 ft

    Los Angeles, CA, Saturday, July 4, 2026 through Monday, July 6, 2026 UTC

    View FAA NOTAM →
  • SECURITY6/2841 2026-07-05 02:00Z – 2026-07-05 09:00Z SFC–1,000 ft

    Las Vegas, NV, Saturday, July 4, 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

  • 2096 ft AGL at event
  • 4 kt ground speed
  • 0 fpm vertical
  • 5 kt wind
  • 2 kt crosswind component

Flight context

  • QAF5
  • GA7C
  • KLAS → KLAX
  • 2026-07-05 02:59 UTC

All events on this flight

TfrPenetration 02:59:48 UTC · · 2,096 ft AGL · 4 kt GS
TfrPenetration 02:59:48 UTC · · 2,096 ft AGL · 4 kt GS
TfrPenetration 02:59:48 UTC · · 2,096 ft AGL · 4 kt GS
TfrPenetration 02:59:48 UTC · · 2,096 ft AGL · 4 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