Long landing rollout — TSC239
CYUL · 24R2026-04-23 02:39 UTC· Air Transat A T Inc.· A321
TSC239 (Air Transat A T) was inbound to CYUL on 2026-04-23. SkyMeter detected a long landing rollout at Montreal / Pierre Elliott Trudeau International Airport (CYUL) on runway 24R at 02:39 UTC. Trace data at the event: 104 ft AGL, 12 kt GS, 0 fpm vertical. METAR at the time reported 4 kt wind, 2 kt crosswind component, 48,280 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/2809 2025-10-20 12:00Z – 2026-10-20 12:00Z SFC–2,000 ft
Palm Beach, FL, Monday, October 20, 2025 through Tuesday, October 20, 2026 Local
View FAA NOTAM → - SECURITY5/2811 2025-10-20 12:00Z – 2026-10-20 12:00Z SFC–1,000 ft
NEW YORK, NY, Monday, October 20, 2025 through Tuesday, October 20, 2026 Local
View FAA NOTAM → - SECURITY5/2858 2025-12-26 04:59Z – 2026-07-02 03:59Z SFC–1,000 ft
OCHOPPEE, FL, Thursday, December 25, 2025 through Wednesday, July 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 24R
- 104 ft AGL at event
- 12 kt ground speed
- 0 fpm vertical
- 4 kt wind
- 2 kt crosswind component
- 48,280 m visibility
- CYUL 211400Z 04008KT 30SM FEW030 BKN250 11/04 A3027 RMK CU1CI6 CU TR SLP254
Flight context
- TSC239
- Air Transat A T
- A321
- 2026-04-23 02:39 UTC
- CYUL runway 24R
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