Evidence Hub 2025 Go-Around Log

2025 Go-Arounds at Toronto Pearson: Community Evidence Log

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,
  • Creates a community-held record that can be compared against the Transportation Safety Board of Canada’s October 15 report — the same report that effectively told Transport Canada to stop looking the other way and act on the risks it already knows about.

Transport Canada has the statutory authority and responsibility to keep both the people flying and the communities on the ground safe. When, after an October 15 TSB report, they still allow this level of concentrated traffic, chronic go-arounds, and relentless noise exposure to continue, they are no longer “unaware.” They are making an active choice to leave people in a situation of ongoing, preventable harm that many residents experience as day-to-day torment.


How to read the go-around tables

Each row in the tables below represents one recorded go-around event at Toronto Pearson in 2025. These are the columns you’ll see:

  • Event # – A simple counter for that month (Event 1, 2, 3…). It’s just an internal ID so we can refer to a specific go-around.
  • Date/Time (Local) – When the go-around occurred, shown in local time. This helps reveal patterns by time of day (overnight, early morning, peak rush, etc.).
  • Dep/Arr – Whether the aircraft was departing (D) or arriving (A). Most go-arounds involve arrivals, but departures can also be affected by traffic or runway conflicts.
  • Aircraft Type – The aircraft model (for example B38M, A320, GL5T). This shows whether events are concentrated in particular aircraft categories.
  • Runway – The runway in use at the time (for example 05, 06R, 23, 24L). This matters for which communities are directly under the flight paths of these events.
  • Screenshot – A link to a radar screenshot captured at or near the time of the go-around. These images give a visual record of aircraft position, track, and surrounding traffic.

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 .

2025 Monthly Frequency (Community-Detected Go-Arounds)

Aug–Dec sample

Total go-arounds recorded by community observers. December shows a sharp jump compared with earlier months, highlighting how workload and routing decisions deteriorated instead of improving through 2025.

52
37
33
44
68
Aug
Sep
Oct
Nov
Dec
SYSTEMIC RISK – NOT RANDOM EVENTS

These go-arounds are not random “one-off safety manoeuvres.” When they cluster month after month, they are a visible symptom of a system that is being pushed beyond its safe operating envelope.

NAV CANADA’s Staffing and Training Collapse

NAV CANADA’s own decisions created a brittle system: controllers were cut, training units were reduced or closed, and recruitment pipelines stalled. Veteran controllers are being stretched across more traffic with less support, while trainees remain stuck in limbo. When the workforce is hollowed out, the margin for error disappears and go-arounds become a routine side-effect of overload.

Pandemic-Era Route Concentration

Instead of rebuilding resilience after the pandemic, NAV CANADA doubled down on concentrated routing: fewer active runways, fewer arrival streams, and highly compressed “arrival banks.” This forces too many aircraft into narrow windows and over the same neighbourhoods, creating the high-workload conflicts that trigger go-arounds in the first place.

GTAA’s Refusal to Match Capacity to Reality

At the same time, GTAA has refused to meaningfully reduce traffic volume or smooth demand. The airport continues to pursue pre-pandemic throughput on a post-pandemic, understaffed ATC system. That is a policy choice, not an accident.

  • Safety erosion: As go-arounds become more frequent, the statistical risk of a serious separation or runway event increases.
  • Community health: Every go-around is a high-thrust climb over populated areas, adding avoidable noise and emissions to neighbourhoods that are already over-exposed.

In other words: the instability shown in these tables is not “just how aviation works.” It is the direct result of NAV CANADA’s staffing and routing decisions, and GTAA’s willingness to keep pushing volume into a system that cannot safely and fairly handle it.


December 2025 – Community-Detected Go-Arounds

Click “View” to open each radar screenshot.

Event #Date/Time (Local)Dep/ArrAircraft TypeRunwayScreenshot
12025-12-01T19:54:02AB77W06RView
22025-12-02T00:01:32AB7385View
32025-12-02T16:03:32AB76306RView
42025-12-02T18:55:31AE29506LView
52025-12-02T19:10:33AB7635View
62025-12-02T20:19:01ACL605View
72025-12-02T22:12:01AA20N24LView
82025-12-03T16:25:01AB78924RView
92025-12-03T23:00:32AA32124RView
102025-12-04T12:34:31AE29506LView
112025-12-05T06:40:02AB38M24RView
122025-12-07T14:37:31AB73806RView
132025-12-08T14:51:01AE17024RView
142025-12-08T17:18:32AE29524RView
152025-12-08T17:21:32AB38M24LView
162025-12-08T17:24:02AB78924LView
172025-12-09T14:40:31AB73824RView
182025-12-09T17:11:30AA32024RView
192025-12-09T17:29:00AB38M24RView
202025-12-09T17:38:31AA32124RView
212025-12-09T18:03:02AE14524LView
222025-12-10T18:28:32AA32033LView
232025-12-10T20:00:32AE29515RView
242025-12-11T14:53:00AB78924RView
252025-12-11T19:24:31AB78924RView
262025-12-12T17:01:31AB38M24LView
272025-12-12T17:05:30ACRJ924LView
282025-12-13T09:42:33AE75S24LView
292025-12-14T10:54:03AB77W24RView
302025-12-14T11:09:00AE29506RView
312025-12-18T20:53:02AA21N15LView
322025-12-19T10:49:32ABCS324RView
332025-12-19T12:35:00AE29524LView
342025-12-19T12:56:00AA32106RView
352025-12-19T15:55:00ACRJ924RView
362025-12-19T20:19:00AB77W24RView
372025-12-20T11:45:01AB77L06RView
382025-12-20T14:18:00AA32124LView
392025-12-20T18:45:01AB38M24LView
402025-12-22T17:29:30AB38M24LView
412025-12-23T11:25:01APC2423View
422025-12-23T11:48:32AE29523View
432025-12-23T11:50:31ACL6023View
442025-12-23T11:53:00AB38M23View
452025-12-23T12:01:02AE29523View
462025-12-26T10:49:00ACRJ915LView
472025-12-26T16:29:32AB77W15LView
482025-12-26T18:08:31AB38M15LView
492025-12-26T19:25:31ABCS306RView
502025-12-27T10:58:31AB77W06RView
512025-12-28T21:46:30AB7385View
522025-12-28T21:54:02AB38M24LView
532025-12-28T23:04:02AB38M06RView
542025-12-28T23:30:01AE29506RView
552025-12-28T23:32:02AE75L24LView
562025-12-29T00:12:32AB38M06RView
572025-12-29T00:58:02AE29506RView
582025-12-29T01:45:02AB38M33RView
592025-12-29T02:50:32AB73806LView
602025-12-29T14:09:02AE29524LView
612025-12-29T14:12:31AB38M24RView
622025-12-29T14:31:30ACRJ924RView
632025-12-29T14:36:01AB78924RView
642025-12-29T14:50:02AA35K06RView
652025-12-29T15:57:30AB78824RView
662025-12-29T16:03:01AE75S24RView
672025-12-29T16:20:02AB38M24RView
682025-12-30T14:14:32ABCS306RView

November 2025 – Community-Detected Go-Arounds

Community recordings submitted by residents.

Event #Date/Time (Local)Dep/ArrAircraft TypeRunwayScreenshot
12025-11-01T21:31:30AB38M24RView
22025-11-02T12:22:32AE17006RView
32025-11-02T12:23:01AE75S06RView
42025-11-02T12:43:31AE29506RView
52025-11-02T20:21:30AB78924LView
62025-11-03T12:18:03AB38M24LView
72025-11-03T21:45:31AE75L24RView
82025-11-03T23:49:01AB38M24LView
92025-11-04T15:59:01AA32123View
102025-11-04T20:02:33AE29524RView
112025-11-05T17:41:32ABCS324RView
122025-11-05T23:44:31AE29524RView
132025-11-06T12:55:31AE29524LView
142025-11-09T18:07:01AB38M15RView
152025-11-10T08:43:00AB77W5View
162025-11-10T16:32:33AC7005View
172025-11-10T23:36:32AB73806RView
182025-11-11T02:12:32AB38M23View
192025-11-11T08:06:00AB38M23View
202025-11-12T18:51:31AB38M06LView
212025-11-13T20:36:03ADH8D24RView
222025-11-14T19:01:31ACRJ95View
232025-11-15T13:51:32AA20N5View
242025-11-15T14:47:00AA3205View
252025-11-15T21:38:00AE29533LView
262025-11-16T19:03:30AB38M23View
272025-11-16T22:19:01AE29524LView
282025-11-17T11:08:00ACRJ906RView
292025-11-17T18:45:31AE29523View
302025-11-17T19:01:30AA31923View
312025-11-20T18:01:31AB73806RView
322025-11-20T19:14:02AA3335View
332025-11-20T19:22:30AB7525View
342025-11-21T20:55:30AA32124RView
352025-11-22T14:57:00AB78906RView
362025-11-23T08:19:30AB38M23View
372025-11-23T16:27:02ACRJ924LView
382025-11-23T16:29:31AE29523View
392025-11-23T19:10:01AE29524LView
402025-11-25T18:17:31AB78906RView
412025-11-28T13:03:31ABCS324RView
422025-11-28T16:42:31ACRJ715RView
432025-11-30T19:45:31ACL3006RView
442025-11-30T20:39:32AA32106LView

October 2025 – Community-Detected Go-Arounds

Verified resident-captured go-arounds.

Event #Date/Time (Local)Dep/ArrAircraft TypeRunwayScreenshot
12025-10-01T16:50:01AGL5T5View
22025-10-01T16:59:31AB38M5View
32025-10-02T16:36:01AA3205View
42025-10-08T16:13:31AA35K15RView
52025-10-08T16:46:02AA32106RView
62025-10-10T00:19:32AA32106LView
72025-10-10T12:41:32AB38M06LView
82025-10-10T23:14:30AE14524RView
92025-10-11T16:09:00ADH8D24LView
102025-10-11T18:49:00AA32106RView
112025-10-12T16:00:01AB76306RView
122025-10-12T21:37:31AE29506RView
132025-10-13T15:26:31AE29506RView
142025-10-13T20:05:01AB38M24LView
152025-10-13T22:09:30AE75L06RView
162025-10-14T06:45:32AB7385View
172025-10-14T06:59:01AB38M06RView
182025-10-14T15:38:02AE75S24LView
192025-10-16T21:43:32AB38M06RView
202025-10-17T08:46:01ACRJ915RView
212025-10-19T20:16:32AB77W24RView
222025-10-19T23:34:30AA32006LView
232025-10-21T21:45:02AB38M06RView
242025-10-24T12:50:30AA33324RView
252025-10-25T13:31:31AB77W24RView
262025-10-25T19:13:00AE29524LView
272025-10-25T21:14:02AA31906RView
282025-10-26T20:02:31AE29524LView
292025-10-26T21:26:30AA21N06RView
302025-10-30T21:26:02AB38M06RView
312025-10-31T14:54:01AB73806RView
322025-10-31T18:56:31AB38M06LView
332025-10-31T20:47:30AE29524LView

September 2025 – Community-Detected Go-Arounds

This table includes missing-screenshot events.

Event #Date/Time (Local)Dep/ArrAircraft TypeRunwayScreenshot
12025-09-01T00:19:00ABCS306RNo screenshot available
22025-09-02T06:36:32AB38M15LNo screenshot available
32025-09-02T15:08:31AE29506RNo screenshot available
42025-09-02T23:01:02ACRJ906RNo screenshot available
52025-09-03T18:11:32AB74424RNo screenshot available
62025-09-03T21:21:30AB77W24RNo screenshot available
72025-09-05T11:47:30ABCS306RNo screenshot available
82025-09-07T13:35:30AGLF423View
92025-09-08T00:06:00AB38M24RView
102025-09-09T19:26:31AE75L24LView
112025-09-10T06:35:32AB38M15RView
122025-09-10T17:50:30AB73824RView
132025-09-12T19:52:32AB38M24LView
142025-09-12T22:28:02AB73824RView
152025-09-14T22:32:31AE29524LView
162025-09-15T20:11:01AE2955View
172025-09-16T06:03:00ACRJ95View
182025-09-16T07:59:31AB7385View
192025-09-16T13:52:02ABCS324LView
202025-09-16T15:14:32AE2955View
212025-09-18T14:33:31AA20N24LView
222025-09-19T15:04:01AE29523View
232025-09-19T15:24:32AA21N15LView
242025-09-19T19:34:00AB38M23View
252025-09-19T20:31:31AB38M06LView
262025-09-21T11:00:02ACRJ906RView
272025-09-22T11:35:31AB38M24RView
282025-09-25T09:50:30AB73724RView
292025-09-25T19:20:31AB38M06RView
302025-09-25T20:29:30AA21N06RView
312025-09-26T05:37:00AE29515RView
322025-09-26T06:53:30AB73824LView
332025-09-26T11:22:02AE75L24RView
342025-09-26T17:18:02AB73823View
352025-09-29T06:39:30AB38M24LView
362025-09-29T06:57:32AB38M24RView
372025-09-29T15:24:31AE29515RView

August 2025 – Community-Detected Go-Arounds

Community-recorded go-arounds during August.

Event #Date/Time (Local)Dep/ArrAircraft TypeRunwayScreenshot
12025-08-01T21:17:01AB38M06RView
22025-08-02T13:59:30AA21N24LView
32025-08-03T12:08:01AB38M06RNo screenshot available
42025-08-03T13:53:02AB78823No screenshot available
52025-08-03T15:21:02ACL3524LNo screenshot available
62025-08-04T09:16:30AB38M24RView
72025-08-05T14:28:31AC25C5View
82025-08-07T00:57:01AB39M5No screenshot available
92025-08-08T11:47:30AB38M06RView
102025-08-08T15:55:32AB38M06RView
112025-08-10T12:38:32AE29506RView
122025-08-10T21:28:32AB73806RView
132025-08-11T05:52:02AA32024LNo screenshot available
142025-08-11T11:30:31AE29533LView
152025-08-12T10:58:32AB77W24RView
162025-08-13T16:02:00AA32124LView
172025-08-13T16:54:30AB78824LView
182025-08-13T17:52:31AB38M06RView
192025-08-14T13:05:30ABCS35View
202025-08-14T15:04:01AA3325No screenshot available
212025-08-14T16:08:01AA35K15RView
222025-08-14T20:44:30AB38M06RView
232025-08-14T20:59:32AB73824LView
242025-08-15T02:09:02ABCS315RView
252025-08-15T13:25:30ABCS324LView
262025-08-15T15:41:31AB73806RView
272025-08-15T17:34:02ACRJ924LView
282025-08-16T14:53:02AE17015RView
292025-08-16T17:31:02AB73824RNo screenshot available
302025-08-19T13:49:01AE5505View
312025-08-19T18:44:32AE29506RNo screenshot available
322025-08-20T03:57:33AB7485No screenshot available
332025-08-21T20:53:00AB73824RView
342025-08-22T11:56:32AB38M06RView
352025-08-24T11:07:30AB77W24RView
362025-08-24T16:06:32AB77W24RView
372025-08-25T16:55:31AA31924RView
382025-08-26T14:19:02AE75S06RView
392025-08-26T15:01:30AA32024LNo screenshot available
402025-08-26T17:35:31AB38M06RView
412025-08-27T22:57:31AB73724LView
422025-08-28T17:52:01AE29524LNo screenshot available
432025-08-28T20:17:00AB77W06RView
442025-08-29T15:45:32AA33224LView
452025-08-30T10:54:30AB38M24LView
462025-08-30T14:54:32AA20N24RView
472025-08-30T15:33:02AB38M23View
482025-08-30T16:02:32AA33324RNo screenshot available
492025-08-30T18:17:33ACRJ924LView
502025-08-31T16:10:31ACRJ724LNo screenshot available
512025-08-31T20:46:31AB38M06RView
522025-08-31T22:57:32AB73806RView


Pearson Accountability Alliance

Independent Environmental & Public Health Research for Toronto Pearson Communities.