Long landing rollout — PTR2280
CYTZ · 082026-07-19 13:52 UTC· CYHZ → CYTZ· Porter Airlines Inc.· DH8D
PTR2280 (Porter Airlines) was operating from CYHZ to CYTZ on 2026-07-19. SkyMeter detected a long landing rollout at Billy Bishop Toronto City Centre Airport (CYTZ) on runway 08 at 13:52 UTC. Trace data at the event: 239 ft AGL, 0 kt GS, 0 fpm vertical. Approach stability score: 67/100. Scores in this band occur on roughly 10-15% of approaches at this runway, with multiple gates outside the per-runway envelope. METAR at the time reported 8 kt wind, 8 kt crosswind component, 14,484 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 →
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 08
- 239 ft AGL at event
- 0 kt ground speed
- 0 fpm vertical
- Approach stability 67/100
- 8 kt wind
- 8 kt crosswind component
- 14,484 m visibility
- CYTZ 172150Z AUTO 22003KT 170V230 9SM OVC049 20/19 A3013 RMK SLP205 DENSITY ALT 700FT
Flight context
- PTR2280
- Porter Airlines
- DH8D
- CYHZ → CYTZ
- 2026-07-19 13:52 UTC
- CYTZ runway 08
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