EJA265 was operating from KBZN to KMSN on 2026-08-24. SkyMeter detected a long landing rollout at Dane County Regional Truax Field (KMSN) on runway 03 at 02:50 UTC. Trace data at the event: 859 ft AGL, 0 kt GS. Approach stability score: 74/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 4 kt wind, 2 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)- HAZARDS6/4893 2026-08-13 13:00Z – 2026-08-28 03:00Z SFC–9,000 ft
43NM E HOT SPRINGS, SD, Thursday, August 13, 2026 through Friday, August 28, 2026 UTC
View FAA NOTAM → - HAZARDS6/6723 2026-08-20 14:00Z – 2026-09-03 04:00Z SFC–9,000 ft
16NM E BIG TIMBER, MT, Thursday, August 20, 2026 through Thursday, September 3, 2026 UTC
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
- 0 kt ground speed
- 0 fpm vertical
- Approach stability 74/100
- 4 kt wind
- 2 kt crosswind component
- 16,093 m visibility
- KMSN 041653Z 17013G19KT 10SM FEW110 FEW160 BKN250 24/21 A2995 RMK AO2 LTG DSNT W RAE01 TSE08 SLP137 P0000 T02440206
Flight context
- EJA265
- CL60
- KBZN → KMSN
- 2026-08-24 02:50 UTC
- KMSN runway 03
All events on this flight
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