ACA142 (AIR Canada) was operating from CYYC to CYYZ on 2026-09-02. SkyMeter detected a go-around at Lester B. Pearson International Airport (CYYZ) on runway 06R at 20:13 UTC. Trace data at the event: 1102 ft AGL, 160 kt GS. METAR at the time reported 4 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.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- 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 → - HAZARDS6/6599 2026-08-20 13:00Z – 2026-09-03 03:00Z SFC–11,000 ft
21NM SE HAMILTON, MT, Thursday, August 20, 2026 through Thursday, September 3, 2026 UTC
View FAA NOTAM → - HAZARDS6/6723 2026-08-20 14:00Z – 2026-09-03 04:00Z SFC–9,000 ft
16NM E BIG TIMBER, MT, Thursday, August 20, 2026 through Thursday, September 3, 2026 UTC
View FAA NOTAM → - HAZARDS6/7337 2026-08-24 14:00Z – 2026-09-08 03:30Z SFC–10,000 ft
11NM SE HAMILTON, MT, Monday, August 24, 2026 through Tuesday, September 8, 2026 UTC
View FAA NOTAM → - HAZARDS6/7660 2026-08-25 14:00Z – 2026-09-09 03:30Z SFC–12,500 ft
34NM S HAMILTON, MT, Tuesday, August 25, 2026 through Wednesday, September 9, 2026 UTC
View FAA NOTAM → - HAZARDS6/7668 2026-08-25 14:00Z – 2026-09-08 03:30Z SFC–10,000 ft
11NM SE HAMILTON, MT, Tuesday, August 25, 2026 through Tuesday, September 8, 2026 UTC
View FAA NOTAM → - HAZARDS6/8106 2026-08-26 14:00Z – 2026-09-10 03:30Z SFC–12,500 ft
11NM SE HAMILTON, MT, Wednesday, August 26, 2026 through Thursday, September 10, 2026 UTC
View FAA NOTAM → - HAZARDS6/8109 2026-08-26 14:00Z – 2026-09-09 03:30Z SFC–11,000 ft
32NM SE BILLINGS, MT, Wednesday, August 26, 2026 through Wednesday, September 9, 2026 UTC
View FAA NOTAM → - SECURITY6/6998 2026-08-27 11:00Z – 2026-09-08 03:00Z SFC–400 ft
St. Paul, MN, Thursday, August 27, 2026 through Monday, September 7, 2026 Local
View FAA NOTAM → - HAZARDS6/8524 2026-08-27 14:00Z – 2026-09-10 03:30Z SFC–12,500 ft
18NM SE ENNIS, MT, Thursday, August 27, 2026 through Thursday, September 10, 2026 UTC
View FAA NOTAM → - HAZARDS6/8675 2026-08-28 01:00Z – 2026-09-10 04:00Z SFC–13,000 ft
36NM SW BUTTE, MT, Friday, August 28, 2026 through Thursday, September 10, 2026 UTC
View FAA NOTAM → - HAZARDS6/8778 2026-08-28 14:00Z – 2026-09-11 03:00Z SFC–10,000 ft
18NM S DILLON, MT, Friday, August 28, 2026 through Friday, September 11, 2026 UTC
View FAA NOTAM → - HAZARDS6/8900 2026-08-29 14:00Z – 2026-09-12 03:00Z SFC–12,000 ft
46NM E MISSOULA, MT, Saturday, August 29, 2026 through Saturday, September 12, 2026 UTC
View FAA NOTAM → - HAZARDS6/9243 2026-08-30 18:36Z – 2026-09-05 23:59Z SFC–2,000 ft
IRON COUNTY, WI, Sunday, August 30, 2026 through Saturday, September 5, 2026 UTC
View FAA NOTAM → - HAZARDS6/9847 2026-09-01 16:02Z – 2026-09-08 22:00Z SFC–2,000 ft
IRON COUNTY, WI, Tuesday, September 1, 2026 through Tuesday, September 8, 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.
Pilot review data
- Runway 06R
- 1102 ft AGL at event
- 160 kt ground speed
- 0 fpm vertical
- 4 kt wind
- 2 kt crosswind component
- 24,140 m visibility
- CYYZ 161000Z 34004KT 15SM FEW260 18/16 A3020 RMK CI2 SLP229 DENSITY ALT 800FT
Flight context
- ACA142
- AIR Canada
- A321
- CYYC → CYYZ
- 2026-09-02 20:13 UTC
- CYYZ runway 06R
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