Long landing rollout — LXJ757

KIAG · 28L

2026-08-25 01:18 UTC· LIMC → KIAG· DIRECTIONAL CAPITAL LLC· GLF6

▶ Replay 📊 Analyse

LXJ757 (Directional Capital) was operating from LIMC to KIAG on 2026-08-25. SkyMeter detected a long landing rollout at Niagara Falls International Airport (KIAG) on runway 28L at 01:18 UTC. Trace data at the event: 698 ft AGL, 14 kt GS. METAR at the time reported 9 kt wind, 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)
  • SECURITY6/2790 2026-07-02 22:30Z – 2026-09-15 03:59Z SFC–400 ft

    St. George, ME, Thursday, July 2, 2026 through Monday, September 14, 2026 Local

    View FAA NOTAM →
  • VIP6/7107 2026-08-24 14:30Z – 2026-08-24 18:00Z SFC–4,999 ft

    Bangor, ME, Monday, August 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

  • Runway 28L
  • 698 ft AGL at event
  • 14 kt ground speed
  • 0 fpm vertical
  • 9 kt wind
  • 0 kt crosswind component
  • 16,093 m visibility
  • KIAG 162153Z 01005KT 10SM CLR 24/18 A3028 RMK AO2 SLP250 T02390178 $

Flight context

  • LXJ757
  • Directional Capital
  • GLF6
  • LIMC → KIAG
  • 2026-08-25 01:18 UTC
  • KIAG runway 28L

All events on this flight

Long landing rollout 01:18:02 UTC · KIAG runway 28L · 698 ft AGL · 14 kt GS
Long landing rollout 01:18:02 UTC · KIAG runway 28L · 698 ft AGL · 14 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· KIAG