2026 Go-Arounds at Toronto Pearson: Community Evidence Log Rolling year
TL;DR – What this page shows
These tables show go-arounds detected and recorded by community members, not an official or exhaustive list. They are a documented sample that demonstrates frequency, patterns, and noise/safety impacts from Pearson operations.
Go-arounds are standard safety manoeuvres, but frequent go-arounds can signal deeper problems: congestion, runway conflicts, and chronic noise over the same communities.
The goal is to provide an independent, verifiable sample of go-around events—enough to show how often these high-workload moments occur, which runways and communities are affected, and how this compares to the “nothing to see here” narrative residents are often given.
What are go-arounds?
A go-around is when a pilot abandons a landing at the last moment and climbs away instead of touching down. You may see or hear it as an aircraft that seems about to land, then suddenly powers up, climbs, and “goes around” for another try.
Go-arounds are a standard safety procedure and are part of normal airline operations. Pilots are trained to initiate a go-around whenever something about the approach, the runway, or nearby traffic does not look or feel safe enough to continue the landing.
Common reasons include:
- Unstable approach (too fast, too high, not properly lined up)
- Sudden change in wind or visibility
- An aircraft, vehicle, or animal still on the runway
- Air traffic control spacing issues with other aircraft
- Technical or cockpit concerns that make a conservative decision safer
Why track them?
It is important to be clear:
Not every go-around is a “near miss” or a narrowly avoided collision.
Most are pilots and controllers doing the right thing—choosing a conservative option rather than forcing a marginal landing.
However, go-arounds still matter for several reasons:
- They usually happen at low altitude, when everyone’s workload is high and there is less room for error.
- They can reflect underlying problems: congestion, runway occupancy, aggressive scheduling, or procedure design.
- They create additional noise and fuel burn over the communities below.
- In some cases, the same conditions that trigger a go-around (poor spacing, runway conflicts, confusion on frequency) could, if not managed correctly, lead to serious incidents or tragedy.
By documenting every recorded go-around at Toronto Pearson—date, time, runway, aircraft type, and where possible a radar screenshot—this project is not claiming that each event was unsafe on its own. Instead, it:
- Shows how often these high-workload, high-risk moments occur,
- Helps identify patterns (time of day, runway, traffic configuration), and
- Provides an independent evidence base for communities, regulators, and investigators to ask whether current traffic levels and procedures are as safe and responsible as they should be.
How to read the go-around tables
Each row in the tables below represents one recorded go-around event at Toronto Pearson in 2026. These are the columns you’ll see:
- Event # – A simple counter for that month (Event 1, 2, 3…).
- Date/Time (Local) – When the go-around occurred, shown in local time.
- Dep/Arr – Whether the aircraft was departing (D) or arriving (A) (blank if unknown).
- Aircraft Type – The aircraft model (e.g., B38M, A320, GL5T).
- Runway – The runway in use at the time (e.g., 05, 06R, 23, 24L).
- Screenshot – Link to a radar screenshot.
For broader issues with how Pearson’s noise and complaints are recorded, see our page on Noise Monitoring Failures & Data Integrity at Toronto Pearson Airport .
Go-arounds are normal safety manoeuvres. But when they cluster and recur month after month, they can also reflect systemic strain: compressed arrival “banks,” runway congestion, or procedural design that concentrates traffic over the same communities with little margin for disruption.
- Safety workload: Go-arounds occur at low altitude in busy airspace—high workload for crews and ATC.
- Community impact: A go-around is a high-thrust climb, adding avoidable noise and emissions to already over-exposed neighbourhoods.
This log is a community-held record intended to support oversight, pattern analysis, and public accountability.
2026 Monthly Frequency (Community-Detected Go-Arounds)
JAN–DECTotal go-arounds recorded by community observers. Additional months will be populated as the record grows.
2026 Go-Around Tables
This is a rolling log. New months will be added as community records are compiled.
January 2026 – Community-Detected Go-Arounds
Click “View” to open each radar screenshot.
| Event # | Date/Time (Local) | Dep/Arr | Aircraft Type | Runway | Screenshot |
|---|---|---|---|---|---|
| 1 | 2026-01-03T07:07:31 | A | A21N | 24L | View |
| 2 | 2026-01-03T21:07:30 | A | E75L | 23 | View |
| 3 | 2026-01-03T23:21:31 | A | B738 | 24L | View |
| 4 | 2026-01-04T19:58:01 | A | A321 | 24R | View |
| 5 | 2026-01-05T10:31:00 | A | A319 | 15L | View |
| 6 | 2026-01-05T16:24:02 | A | A320 | 24L | View |
| 7 | 2026-01-08T20:29:32 | A | B738 | 06R | View |
| 8 | 2026-01-08T21:21:01 | A | B738 | 06R | View |
| 9 | 2026-01-08T21:23:01 | A | E295 | 06R | View |
| 10 | 2026-01-09T04:22:00 | A | B752 | 05 | View |
| 11 | 2026-01-09T15:06:00 | A | E145 | 24R | View |
| 12 | 2026-01-09T15:07:08 | A | A21N | 24R | View |
| 13 | 2026-01-09T15:08:31 | A | BCS3 | 24R | View |
| 14 | 2026-01-09T15:18:01 | A | CRJ9 | 24R | View |
| 15 | 2026-01-09T15:20:01 | A | CL60 | 24R | View |
| 16 | 2026-01-09T15:26:31 | A | BCS3 | 24R | View |
| 17 | 2026-01-09T16:12:02 | A | E295 | 23 | View |
| 18 | 2026-01-09T16:21:32 | A | A333 | 23 | View |
| 19 | 2026-01-09T16:30:31 | A | GL5T | 24L | View |
| 20 | 2026-01-09T16:41:31 | A | B738 | 24R | View |
| 21 | 2026-01-10T13:16:01 | A | A321 | 24L | View |
| 22 | 2026-01-10T18:51:31 | A | CRJ7 | 06R | View |
| 23 | 2026-01-11T00:08:30 | A | B38M | 24L | View |
| 24 | 2026-01-11T21:46:00 | A | E295 | 06R | View |
| 25 | 2026-01-14T20:26:31 | A | B38M | 06R | View |
| 26 | 2026-01-14T23:31:32 | A | B738 | 33L | View |
| 27 | 2026-01-14T23:59:03 | A | CRJ9 | 33R | View |
| 28 | 2026-01-15T00:23:02 | A | B38M | 33L | View |
| 29 | 2026-01-15T06:28:32 | A | B38M | 06L | View |
| 30 | 2026-01-15T12:46:00 | A | B748 | 33R | View |
| 31 | 2026-01-15T19:06:32 | A | A321 | 24L | View |
| 32 | 2026-01-16T19:21:31 | A | B38M | 24R | View |
| 33 | 2026-01-16T21:12:01 | A | A321 | 24R | View |
| 34 | 2026-01-17T20:10:01 | A | A320 | 24L | View |
| 35 | 2026-01-18T17:17:30 | A | E145 | 06R | View |
| 36 | 2026-01-18T19:52:03 | A | B38M | 24R | View |
| 37 | 2026-01-19T12:46:31 | A | B38M | 15R | View |
| 38 | 2026-01-19T12:49:30 | A | A320 | 23 | View |
| 39 | 2026-01-19T13:26:31 | A | E295 | 15R | View |
| 40 | 2026-01-19T23:53:31 | A | A321 | 24R | View |
| 41 | 2026-01-20T07:30:31 | A | A319 | 15R | View |
| 42 | 2026-01-21T11:36:31 | A | DH8D | 24R | View |
| 43 | 2026-01-21T19:43:01 | A | A319 | 24R | View |
| 44 | 2026-01-22T14:35:32 | A | B38M | 24R | View |
| 45 | 2026-01-22T15:25:02 | A | B763 | 24R | View |
| 46 | 2026-01-22T15:46:00 | A | B38M | 24L | View |
| 47 | 2026-01-22T15:51:31 | A | C25B | 24L | View |
| 48 | 2026-01-23T00:25:31 | A | B38M | 24L | View |
| 49 | 2026-01-23T10:31:01 | A | A321 | 24R | View |
| 50 | 2026-01-23T15:38:30 | A | CRJ9 | 06R | View |
| 51 | 2026-01-23T15:47:30 | A | A359 | 06R | View |
| 52 | 2026-01-23T17:36:03 | A | B38M | 24L | View |
| 53 | 2026-01-25T16:31:32 | A | B38M | 24R | View |
| 54 | 2026-01-25T16:49:01 | A | E75L | 24L | View |
| 55 | 2026-01-26T09:17:02 | A | GL5T | 06L | View |
| 56 | 2026-01-27T18:00:31 | A | B38M | 24L | View |
| 57 | 2026-01-29T02:16:32 | A | A320 | 15R | View |
| 58 | 2026-01-29T17:02:00 | A | B38M | 06R | View |
| 59 | 2026-01-29T18:12:31 | A | BCS3 | 06L | View |
| 60 | 2026-01-29T19:01:02 | A | A333 | 05 | View |
February 2026 – Community-Detected Go-Arounds
Click “View” to open each radar screenshot.
| Event # | Date/Time (Local) | Dep/Arr | Aircraft Type | Runway | Screenshot |
|---|---|---|---|---|---|
| 1 | 2026-02-03T12:11:02 | A | CRJ9 | 24R | View |
| 2 | 2026-02-03T12:46:12 | A | E170 | 24R | View |
| 3 | 2026-02-03T12:49:31 | A | CRJ9 | 24R | View |
| 4 | 2026-02-03T21:13:32 | A | A359 | 24R | View |
| 5 | 2026-02-06T07:17:31 | A | B38M | 23 | View |
| 6 | 2026-02-06T18:34:30 | A | A321 | 24L | View |
| 7 | 2026-02-06T18:42:31 | A | B737 | 24L | View |
| 8 | 2026-02-06T20:07:32 | A | B38M | 33L | View |
| 9 | 2026-02-06T20:23:00 | A | CRJ9 | 15R | View |
| 10 | 2026-02-06T21:06:31 | A | A321 | 15R | View |
| 11 | 2026-02-06T21:47:02 | A | B738 | 33L | View |
| 12 | 2026-02-06T22:09:01 | A | B38M | 15R | View |
| 13 | 2026-02-06T23:58:32 | A | B738 | 33L | View |
| 14 | 2026-02-09T07:16:03 | A | BCS3 | 5 | View |
| 15 | 2026-02-11T15:57:30 | A | E295 | 06R | View |
| 16 | 2026-02-11T19:50:02 | A | B77W | 06R | View |
| 17 | 2026-02-12T16:10:02 | A | C56X | 5 | View |
| 18 | 2026-02-13T20:16:33 | A | B789 | 23 | View |
| 19 | 2026-02-17T19:37:32 | A | A321 | 24L | View |
| 20 | 2026-02-17T21:00:00 | A | B738 | 5 | View |
| 21 | 2026-02-18T21:29:02 | A | B738 | 5 | View |
| 22 | 2026-02-19T15:38:32 | A | CRJ9 | 06R | View |
| 23 | 2026-02-20T20:48:01 | A | B38M | 24R | View |
| 24 | 2026-02-20T22:30:00 | A | BCS3 | 24R | View |
| 25 | 2026-02-21T21:57:31 | A | B38M | 06R | View |
| 26 | 2026-02-22T12:58:30 | A | E295 | 23 | View |
| 27 | 2026-02-23T17:15:31 | A | BCS3 | 06R | View |
| 28 | 2026-02-23T19:25:00 | A | B190 | 06R | View |
| 29 | 2026-02-23T21:01:02 | A | B38M | 06R | View |
| 30 | 2026-02-24T12:06:00 | A | B737 | 24L | View |
| 31 | 2026-02-24T20:26:31 | A | B738 | 24R | View |
| 32 | 2026-02-25T15:44:30 | A | A320 | 23 | View |
| 33 | 2026-02-25T15:52:00 | A | B789 | 23 | View |
| 34 | 2026-02-28T16:26:31 | A | E295 | 24R | View |
| 35 | 2026-02-28T20:19:02 | A | B38M | 24R | View |
March 2026 – Community-Detected Go-Arounds
Coming soon.
Pearson Accountability Alliance
Independent Environmental & Public Health Research for Toronto Pearson Communities.