TfrPenetration — N200NP
2026-06-13 22:58 UTC· KSJC → ?· RHYS VINEYARDS LLC· PC12
N200NP (Rhys Vineyards) had departed KSJC on 2026-06-13. SkyMeter detected a tfrpenetration at 22:58 UTC. Trace data at the event: 352 ft AGL, 101 kt GS, 0 fpm vertical. METAR at the time reported 4 kt wind, 4 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/7618 2026-06-13 16:00Z – 2026-06-14 01:00Z SFC–3,000 ft
San Francisco, CA, Saturday, June 13, 2026 through Saturday, June 13, 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
- 352 ft AGL at event
- 101 kt ground speed
- 0 fpm vertical
- 4 kt wind
- 4 kt crosswind component
Flight context
- N200NP
- Rhys Vineyards
- PC12
- 2026-06-13 22:58 UTC
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