Long landing rollout — GPD293

KTEB · 24

2026-06-07 18:12 UTC· BEDFORD PARTNERS LLC· PC12

▶ Replay 📊 Analyse

GPD293 (Bedford Partners) was inbound to KTEB on 2026-06-07. SkyMeter detected a long landing rollout at Teterboro Airport (KTEB) on runway 24 at 18:12 UTC. Trace data at the event: 0 ft AGL, 0 kt GS, 0 fpm vertical. METAR at the time reported 7 kt wind, 7 kt crosswind component, 16,093 m visibility. A long landing rollout is detected when ground deceleration after touchdown is below the per-runway P10 envelope. It is an observational measure of rollout efficiency, not a runway-exit incident. 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

  • Runway 24
  • 0 ft AGL at event
  • 0 kt ground speed
  • 0 fpm vertical
  • 7 kt wind
  • 7 kt crosswind component
  • 16,093 m visibility
  • KTEB 162051Z 17007KT 10SM CLR 26/17 A3027 RMK AO2 SLP249 T02610167 56010

Flight context

  • GPD293
  • Bedford Partners
  • PC12
  • 2026-06-07 18:12 UTC
  • KTEB runway 24

All events on this flight

Long landing rollout 18:12:38 UTC · KTEB runway 24 · 0 ft AGL · 0 kt GS
Long landing rollout 18:12:38 UTC · KTEB runway 24 · 0 ft AGL · 0 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· KTEB