TfrPenetration — GPD256

2026-06-08 14:14 UTC· TW LEASING LLC· PC12

GPD256 (TW Leasing) was inbound to KTEB on 2026-06-08. SkyMeter detected a tfrpenetration at 14:14 UTC. Trace data at the event: 896 ft AGL, 126 kt GS. Approach stability score: 38/100. Scores below 50 occur on under 10% of approaches at this runway and indicate the v2 scorer flagged the approach as highly anomalous (three or more gates exceeded the runway's P90 envelope simultaneously). METAR at the time reported 5 kt wind, 5 kt crosswind component. Detection algorithm and known limitations: see SkyMeter methodology.

Active FAA TFR during this flight

Source: FAA TFR archive (hourly snapshot)
  • VIP6/5158 2026-06-05 23:30Z – 2026-06-08 23:30Z SFC–17,999 ft

    Bedminster, NJ, Friday, June 5, 2026 through Monday, June 8, 2026 Local

    View FAA NOTAM →
  • VIP6/5160 2026-06-05 23:30Z – 2026-06-08 23:30Z SFC–17,999 ft

    Bedminster, NJ, Friday, June 5, 2026 through Monday, June 8, 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

  • 896 ft AGL at event
  • 126 kt ground speed
  • 0 fpm vertical
  • Approach stability 38/100
  • 5 kt wind
  • 5 kt crosswind component

Flight context

  • GPD256
  • TW Leasing
  • PC12
  • 2026-06-08 14:14 UTC

All events on this flight

TfrPenetration 14:14:17 UTC · · 896 ft AGL · 126 kt GS
Long landing rollout 14:18:19 UTC · KEWR runway 29 · 0 ft AGL · 2 kt GS
Unstable approach 14:14:02 UTC · KTEB runway 01 · 1,111 ft AGL · 128 kt GS
Unstable approach 14:14:02 UTC · KTEB runway 1 · 1,111 ft AGL · 128 kt GS
TfrPenetration 14:14:17 UTC · · 896 ft AGL · 126 kt GS
Unstable approach 14:14:02 UTC · KTEB runway 1 · 1,111 ft AGL · 128 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