Long landing rollout — N222JS

KMSN · 03

2026-07-29 13:44 UTC· KSDF → KSRQ· FLITEACCESS LLC, JS AIR HOLDINGS LLC· F2TH

▶ Replay 📊 Analyse

N222JS (Fliteaccess) was operating from KSDF to KSRQ on 2026-07-29. SkyMeter detected a long landing rollout at Dane County Regional Truax Field (KMSN) on runway 03 at 13:44 UTC. Trace data at the event: 859 ft AGL, 3 kt GS. Approach stability score: 79/100. Scores in this band are observed on roughly 25% of approaches at this runway: one or more gates outside the per-runway tightest envelope, but still inside the typical operating range. METAR at the time reported 3 kt wind, 3 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)
  • SECURITY6/9807 2026-07-29 12:00Z – 2026-08-01 23:59Z SFC–400 ft

    Pell City, AL, Wednesday, July 29, 2026 through Saturday, August 1, 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 03
  • 859 ft AGL at event
  • 3 kt ground speed
  • 0 fpm vertical
  • Approach stability 79/100
  • 3 kt wind
  • 3 kt crosswind component
  • 16,093 m visibility
  • KMSN 162353Z 12006KT 10SM BKN170 BKN250 19/14 A3028 RMK AO2 SLP253 T01940139 10233 20194 55007

Flight context

  • N222JS
  • Fliteaccess
  • F2TH
  • KSDF → KSRQ
  • 2026-07-29 13:44 UTC
  • KMSN runway 03

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· KMSN