TfrPenetration — GPD853

2026-05-22 22:19 UTC· TVPX ARS INC TRUSTEE· PC12

▶ Replay 📊 Analyse

GPD853 (Tvpx ARS) was inbound to KTEB on 2026-05-22. SkyMeter detected a tfrpenetration at 22:19 UTC. Trace data at the event: 2272 ft AGL, 131 kt GS. Approach stability score: 60/100. Scores in this band occur on roughly 10-15% of approaches at this runway, with multiple gates outside the per-runway envelope. METAR at the time reported 6 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)
  • VIP6/2114 2026-05-22 17:45Z – 2026-05-22 21:45Z SFC–17,999 ft

    SUFFERN, NY, Friday, May 22, 2026 Local

    View FAA NOTAM →
  • VIP6/2115 2026-05-22 17:45Z – 2026-05-22 21:45Z SFC–17,999 ft

    SUFFERN, NY, Friday, May 22, 2026 Local

    View FAA NOTAM →
  • VIP6/2122 2026-05-22 20:30Z – 2026-05-24 23:00Z SFC–17,999 ft

    Bedminster, NJ, Friday, May 22, 2026 through Sunday, May 24, 2026 Local

    View FAA NOTAM →
  • VIP6/2125 2026-05-22 20:30Z – 2026-05-24 23:00Z SFC–17,999 ft

    Bedminster, NJ, Friday, May 22, 2026 through Sunday, May 24, 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

  • 2272 ft AGL at event
  • 131 kt ground speed
  • 0 fpm vertical
  • Approach stability 60/100
  • 6 kt wind
  • 4 kt crosswind component

Flight context

  • GPD853
  • Tvpx ARS
  • PC12
  • 2026-05-22 22:19 UTC

All events on this flight

TfrPenetration 22:19:20 UTC · · 2,272 ft AGL · 131 kt GS
TfrPenetration 22:19:20 UTC · · 2,272 ft AGL · 131 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