TfrPenetration — QAF5

QAF5 had departed KLAX on 2026-07-02. SkyMeter detected a tfrpenetration at 23:39 UTC. Trace data at the event: 78 ft AGL, 0 kt GS, 0 fpm vertical. METAR at the time reported 8 kt wind, 8 kt crosswind component. Detection algorithm and known limitations: see SkyMeter methodology.

• 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 →
• SECURITY6/7265 2026-06-12 21:07Z – 2026-07-16 06:29Z SFC–400 ft

  Manhattan Beach, CA

  View FAA NOTAM →
• HAZARDS6/9814 2026-06-29 14:00Z – 2026-07-04 02:00Z SFC–200 ft

  LONG BEACH, CA, Monday, June 29, 2026 through Saturday, July 4, 2026 UTC

  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 →
• SECURITY6/1385 2026-07-02 16:00Z – 2026-07-03 01:00Z SFC–3,000 ft

  Los Angeles, CA, Thursday, July 2, 2026 through Thursday, July 2, 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.

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