Diversion — JTL872
KTVL · 182026-06-07 19:51 UTC· KSJC → KTVL· PJBEES ENTERPRISES LLC, AMPLIFY ENTERPRISES LLC· C56X
JTL872 (Pjbees Enterprises) was operating from KSJC to KRNO (Reno Tahoe International Airport) on 2026-06-07. SkyMeter detected a diversion to Lake Tahoe Airport (KTVL) on runway 18 at 19:51 UTC. Peak cruise altitude FL196, turnaround area near Linden, US. METAR at the time reported 6 kt wind, 5 kt crosswind component, 16,093 m visibility. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- SECURITY6/5797 2026-04-03 00:01Z – 2026-09-28 23:59Z SFC–400 ft
SACRAMENTO, CA, Thursday, April 2, 2026 through Monday, September 28, 2026 Local
View FAA NOTAM → - 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/4204 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
Santa Clara, CA, Monday, June 1, 2026 through Monday, July 20, 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
- Runway 18
- 6259 ft AGL at event
- 120 kt ground speed
- 0 fpm vertical
- 6 kt wind
- 5 kt crosswind component
- 16,093 m visibility
- KTVL 200450Z AUTO 22004KT 10SM CLR 09/M01 A3023 RMK T00901010 MADISHF
Flight context
- JTL872
- Pjbees Enterprises
- C56X
- KSJC → KTVL
- 2026-06-07 19:51 UTC
- KTVL runway 18
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