WebTrak Outage Log

A running record of observed outages, frozen updates, missing tracks, stalled timestamps, missing historical replay data, live radar-feed failures, and implausibly low movement totals on Toronto Pearson’s public WebTrak portal.

Status: Draft evidence log. Last updated: July 16, 2026. Additional captures and historical incidents will be added as archived.

TL;DR: When WebTrak fails or under-reports activity, residents lose the ability to independently verify flight activity, runway use, night operations, and unusual events.

Latest update — July 16, 2026

WebTrak displayed a public notice stating “Technical difficulties – live radar feed.” The notice advised that WebTrak was experiencing technical difficulties with the live radar feed, that the vendor was working on restoring live data, and that historical data could still be accessed.

Observed anomaly pattern

Some incidents involve not only frozen displays, but implausibly low or zero hourly movement totals during normal operating periods. Other incidents involve apparent gaps in historical replay data, where the public-facing record does not appear to show aircraft activity across the full period being reviewed. The July 16, 2026 incident involved a GTAA-posted notice acknowledging live radar-feed technical difficulties.

Why this matters

Transparency: WebTrak is presented as a public accountability tool.
Verification: Residents use it to review aircraft activity affecting their communities.
Oversight: Missing data can obstruct review of runway use, night flights, go-arounds, and operational anomalies.

Incident Log

Date	Approx. start	Approx. end	Observation	Evidence	Notes
2026-01-31	~15:00	Unknown	Historical replay appears to stop updating after approximately 15:00. Flight tracks freeze and no new activity is displayed.	Screenshot WT-001	Historical replay mode.
2026-02-24	~07:30	Unknown	Publicly acknowledged WebTrak flight-track outage affecting access to live public flight data.	Supporting record WT-002	Referenced in correspondence to GTAA.
2026-04-15	18:00	Unknown	WebTrak hourly movement display shows only four aircraft movements during the 18:00 hour. This appears materially inconsistent with expected late-afternoon operations at a major international airport and suggests missing or incomplete public data.	Screenshot WT-003	Potential under-reporting window.
2026-04-28	17:00	Unknown	WebTrak hourly movement display shows zero aircraft movements during the 17:00 hour. Given Pearson’s normal operating profile, this strongly suggests a reporting outage or data failure rather than an actual absence of aircraft activity.	Screenshot WT-004	Zero reported movements during a normal operating hour.
2026-06-15	Unknown	Unknown	WebTrak historical replay for June 15, 2026 appears to show missing or incomplete flight-activity data. The flight-by-hour display does not appear to represent a complete daily record, including the overnight / early-morning period.	Screenshot WT-005	Apparent missing historical replay data. PAA requested GTAA explanation, including cause, affected period, restoration status, and public disclosure.
2026-07-16	00:00	Unknown	WebTrak displayed a public notice stating “Technical difficulties – live radar feed.” The notice advised that WebTrak was experiencing technical difficulties with the live radar feed, that the vendor was working on restoring live data, and that historical data could still be accessed.	Screenshot WT-006	GTAA-publicly acknowledged live radar-feed issue. Screenshot captured later on July 16 shows the notice still visible on the public interface.

Note: New incidents are assigned sequential exhibit IDs (WT-001, WT-002, WT-003…).

Context

WebTrak is one of the principal public-facing tools residents can use to review aircraft activity around Toronto Pearson. When it freezes, omits tracks, reports implausibly low totals, fails to display a complete historical replay record, or acknowledges live radar-feed technical difficulties, the public record is weakened even though aircraft operations continue.

This is particularly relevant for reviewing night flights, runway use, concentrated routing, go-arounds, and other operational impacts affecting surrounding communities.

Missing or incomplete WebTrak data also affects residents’ ability to compare public flight-track information against noise-monitoring data, personal observations, complaint records, and other operational evidence.

Related evidence

Separate from WebTrak, Pearson’s Noise Monitoring Terminal network has also shown outages, invalid readings, and reporting failures.

Noise Monitoring at Pearson

Exhibit List

WT-001 — 31 Jan 2026 replay freeze : Historical replay appears to stop updating after approximately 15:00.
WT-002 — 24 Feb 2026 acknowledged outage : Public WebTrak outage referenced in correspondence.
WT-003 — 15 Apr 2026 under-reporting anomaly : Only four aircraft movements shown during the 18:00 hour.
WT-004 — 28 Apr 2026 zero-movement anomaly : Zero aircraft movements shown during the 17:00 hour.
WT-005 — 15 Jun 2026 missing historical replay data : WebTrak historical replay appears to show missing or incomplete flight-activity data for June 15, 2026, including the overnight / early-morning period.
WT-006 — 16 Jul 2026 live radar-feed technical difficulties : WebTrak displayed a GTAA notice stating “Technical difficulties – live radar feed,” advising that the vendor was working on restoring live data while historical data remained accessible.

Method note: Times are approximate and recorded in local time. Incidents are logged when WebTrak stops updating, displays implausibly low movement totals, omits visible activity, shows missing historical replay data, acknowledges live radar-feed technical difficulties, or otherwise appears inconsistent with expected airport operations. Supporting screenshots and records are retained as exhibits.

Pearson Accountability Alliance

Independent Environmental & Public Health Research for Toronto Pearson Communities.