Long landing rollout — N64MT
KSJC · 30R2026-01-14 00:08 UTC· KDAL → KSJC· WINDTOP INC, REH HOLDINGS LLC· GLEX
N64MT (Windtop) was operating from KDAL to KSJC on 2026-01-14. SkyMeter detected a long landing rollout at Norman Y. Mineta San Jose International Airport (KSJC) on runway 30R at 00:08 UTC. Trace data at the event: 16 ft AGL, 14 kt GS, 0 fpm vertical. METAR at the time reported 2 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)- SECURITY5/0601 2025-11-30 19:00Z – 2026-05-31 18:59Z SFC–400 ft
Los Angeles, CA, Sunday, November 30, 2025 through Sunday, May 31, 2026 Local
View FAA NOTAM → - SECURITY6/0091 2026-01-04 00:01Z – 2026-07-04 23:59Z SFC–500 ft
Coyote Wells, CA, Saturday, January 3, 2026 through Saturday, July 4, 2026 Local
View FAA NOTAM → - SECURITY6/0092 2026-01-04 00:01Z – 2026-07-04 23:59Z SFC–500 ft
CALEXICO, CA, Saturday, January 3, 2026 through Saturday, July 4, 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 30R
- 16 ft AGL at event
- 14 kt ground speed
- 0 fpm vertical
- 2 kt wind
- 2 kt crosswind component
- 16,093 m visibility
- METAR KSJC 262253Z 33010KT 10SM FEW060 FEW080 FEW120 24/11 A2986 RMK AO2 SLP110 T02440106
Flight context
- N64MT
- Windtop
- GLEX
- KDAL → KSJC
- 2026-01-14 00:08 UTC
- KSJC runway 30R
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