TfrPenetration — N7628

2026-06-15 22:49 UTC· KLAX → KSJC· GA7C

▶ Replay 📊 Analyse

N7628 was operating from KLAX to KSJC on 2026-06-15. SkyMeter detected a tfrpenetration at 22:49 UTC. Trace data at the event: 268 ft AGL, 155 kt GS, 0 fpm vertical. METAR at the time reported 10 kt wind, 10 kt crosswind component. Detection algorithm and known limitations: see SkyMeter methodology.

Active FAA TFR during this flight

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

    San Jose, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/4054 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft

    San Jose, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/4192 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft

    Santa Barbara, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/4197 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft

    GOLETA, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/7934 2026-06-15 22:00Z – 2026-06-16 07:01Z SFC–3,000 ft

    Los Angeles, CA, Monday, June 15, 2026 through Tuesday, June 16, 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

  • 268 ft AGL at event
  • 155 kt ground speed
  • 0 fpm vertical
  • 10 kt wind
  • 10 kt crosswind component

Flight context

  • N7628
  • GA7C
  • KLAX → KSJC
  • 2026-06-15 22:49 UTC

All events on this flight

TfrPenetration 22:49:26 UTC · · 268 ft AGL · 155 kt GS
TfrPenetration 22:49:26 UTC · · 268 ft AGL · 155 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