Go-around — POE654

POE654 (Porter Airlines (Canada)) was operating from KLAS to CYYZ on 2026-09-02. SkyMeter detected a go-around at Lester B. Pearson International Airport (CYYZ) on runway 05 at 21:32 UTC. Trace data at the event: 1682 ft AGL, 153 kt GS. METAR at the time reported 7 kt wind, 2 kt crosswind component, 24,140 m visibility. A go-around is a discontinued landing approach in which the pilot adds power and climbs back to a safe altitude before re-attempting the approach or proceeding to an alternate. It is a routine safety response, not an emergency, and is taught as the standard reaction to any unstable approach. Detection algorithm and known limitations: see SkyMeter methodology.

• SECURITY6/0708 2026-08-01 00:01Z – 2027-08-01 23:59Z SFC–400 ft

  Goodlettsville, TN, Saturday, August 1, 2026 through Sunday, August 1, 2027 UTC

  View FAA NOTAM →
• HAZARDS6/6954 2026-08-21 14:00Z – 2026-09-04 03:00Z SFC–11,000 ft

  33NM SW POCATELLO, ID, Friday, August 21, 2026 through Friday, September 4, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7092 2026-08-22 13:00Z – 2026-09-04 03:00Z SFC–14,000 ft

  26NM SW PRICE, UT, Saturday, August 22, 2026 through Friday, September 4, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7115 2026-08-22 23:30Z – 2026-09-04 03:00Z SFC–13,000 ft

  41NM E PRICE, UT, Saturday, August 22, 2026 through Friday, September 4, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7347 2026-08-24 13:00Z – 2026-09-07 04:00Z SFC–10,000 ft

  35NM SW PROVO, UT, Monday, August 24, 2026 through Monday, September 7, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7530 2026-08-24 17:00Z – 2026-09-06 03:00Z SFC–10,000 ft

  35NM SW PROVO, UT, Monday, August 24, 2026 through Sunday, September 6, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7463 2026-08-25 12:00Z – 2026-09-08 08:00Z SFC–16,500 ft

  1NM NE OURAY, CO, Tuesday, August 25, 2026 through Tuesday, September 8, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7654 2026-08-25 13:00Z – 2026-09-07 04:00Z SFC–10,000 ft

  35NM SW PROVO, UT, Tuesday, August 25, 2026 through Monday, September 7, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7986 2026-08-25 21:45Z – 2026-09-07 04:00Z SFC–12,000 ft

  32NM SW TOOELE, UT, Tuesday, August 25, 2026 through Monday, September 7, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8502 2026-08-27 14:00Z – 2026-09-09 03:00Z SFC–15,000 ft

  48NM NW TAOS, NM, Thursday, August 27, 2026 through Wednesday, September 9, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8587 2026-08-27 17:45Z – 2026-09-09 03:00Z SFC–8,500 ft

  25NM NW OGDEN, UT, Thursday, August 27, 2026 through Wednesday, September 9, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8775 2026-08-28 14:00Z – 2026-09-09 03:00Z SFC–8,500 ft

  25NM NW OGDEN, UT, Friday, August 28, 2026 through Wednesday, September 9, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8806 2026-08-28 15:04Z – 2026-09-12 03:00Z SFC–15,000 ft

  30NM W TAOS, NM, Friday, August 28, 2026 through Saturday, September 12, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8869 2026-08-28 21:32Z – 2026-09-12 03:00Z SFC–10,000 ft

  18NM SW LOVELAND, CO, Friday, August 28, 2026 through Saturday, September 12, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8870 2026-08-29 14:00Z – 2026-09-12 03:00Z SFC–15,000 ft

  30NM W TAOS, NM, Saturday, August 29, 2026 through Saturday, September 12, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9396 2026-08-31 18:00Z – 2026-09-04 01:30Z SFC–14,000 ft

  Bailey, CO, Monday, August 31, 2026 through Friday, September 4, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9645 2026-08-31 18:00Z – 2026-09-04 01:30Z SFC–14,000 ft

  BAILEY, CO, Monday, August 31, 2026 through Friday, September 4, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9646 2026-08-31 18:00Z – 2026-09-04 01:30Z SFC–14,000 ft

  BAILEY, CO, Monday, August 31, 2026 through Friday, September 4, 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