Long landing rollout — ROU1776

ROU1776 (Air Canada) was operating from CYYC to KCDW on 2026-06-29. SkyMeter detected a long landing rollout at Essex County Airport (KCDW) on runway 22 at 17:00 UTC. Trace data at the event: 0 ft AGL, 13 kt GS, 0 fpm vertical. Approach stability score: 37/100. Scores below 50 occur on under 10% of approaches at this runway and indicate the v2 scorer flagged the approach as highly anomalous (three or more gates exceeded the runway's P90 envelope simultaneously). METAR at the time reported 3 kt wind, 1 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.

• SECURITY6/4348 2026-03-08 07:00Z – 2026-11-01 06:59Z SFC–2,400 ft

  GRAND FORKS AFB, ND, Sunday, March 8, 2026 through Sunday, November 1, 2026 Local

  View FAA NOTAM →
• SECURITY6/4167 2026-06-01 06:00Z – 2026-07-21 05:59Z SFC–400 ft

  Salt Lake City, UT, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/6851 2026-06-13 04:01Z – 2026-07-12 03:59Z SFC–1,000 ft

  Harrison, NJ, Saturday, June 13, 2026 through Saturday, July 11, 2026 Local

  View FAA NOTAM →
• SECURITY6/7801 2026-06-15 04:00Z – 2026-07-07 03:29Z SFC–400 ft

  Whippany, NJ, Monday, June 15, 2026 through Monday, July 6, 2026 Local

  View FAA NOTAM →
• HAZARDS6/9461 2026-06-21 12:00Z – 2026-07-04 04:00Z SFC–10,500 ft

  3.5NM SW SALT LAKE CITY, UT, Sunday, June 21, 2026 through Saturday, July 4, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9504 2026-06-21 14:14Z – 2026-07-05 15:00Z SFC–10,500 ft

  10NM NE OGDEN, UT, Sunday, June 21, 2026 through Sunday, July 5, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9555 2026-06-22 12:00Z – 2026-07-04 04:00Z SFC–10,500 ft

  3.5NM SW SALT LAKE CITY, UT, Monday, June 22, 2026 through Saturday, July 4, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9562 2026-06-22 12:00Z – 2026-07-04 04:00Z SFC–10,500 ft

  29NM NW TOOELE, UT, Monday, June 22, 2026 through Saturday, July 4, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9582 2026-06-22 13:04Z – 2026-07-05 15:00Z SFC–10,500 ft

  29NM NW TOOELE, UT, Monday, June 22, 2026 through Sunday, July 5, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9592 2026-06-22 13:29Z – 2026-07-05 15:00Z SFC–10,500 ft

  3.5NM SW SALT LAKE CITY, UT, Monday, June 22, 2026 through Sunday, July 5, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9834 2026-06-22 19:21Z – 2026-07-05 15:00Z SFC–10,500 ft

  4NM SW SALT LAKE CITY, UT, Monday, June 22, 2026 through Sunday, July 5, 2026 UTC

  View FAA NOTAM →
• SECURITY6/9462 2026-06-24 04:00Z – 2026-07-21 03:29Z SFC–400 ft

  Montclair, NJ, Wednesday, June 24, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• HAZARDS6/0276 2026-06-24 15:00Z – 2026-07-07 04:00Z SFC–10,500 ft

  4NM SW SALT LAKE CITY, UT, Wednesday, June 24, 2026 through Tuesday, July 7, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/0613 2026-06-25 13:00Z – 2026-07-08 03:00Z SFC–14,500 ft

  27NM SW JACKSON, WY, Thursday, June 25, 2026 through Wednesday, July 8, 2026 UTC

  View FAA NOTAM →
• SECURITY6/9464 2026-06-28 04:00Z – 2026-07-02 03:29Z SFC–400 ft

  Parsippany-Troy Hills, NJ, Sunday, June 28, 2026 through Wednesday, July 1, 2026 Local

  View FAA NOTAM →
• HAZARDS6/1011 2026-06-29 16:30Z – 2026-06-29 18:30Z SFC–4,500 ft

  KEEWATIN, MN, Monday, June 29, 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.

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