June 12, 2018

Incident at MONTREAL CENTRE / ACC DE MONTRÉAL (ATM - NAVAIDS/radar)

A Radar Data Processing System (RDPS) failure occurred between 2052Z and 2123Z, causing a loss of the mosaic radar display. The operational impact involved ground stops at Montreal/Pierre Elliott Trudeau International, QC (CYUL), Ottawa/Macdonald?Cartier International, ON (CYOW), Quebec City/Jean Lesage International, QC (CYQB), Montreal/Mirabel International, QC (CYMX) and Montreal/Saint-Hubert Longueuil, QC (CYHU) between 2101Z and 2128Z, causing several waiting patterns and delays on the ground that lasted approximately 15 to 20 minutes.

November 23, 2016

Incident at BRISAY PAL (ATM - inaccurate aeronautical information)

The Brisay radar (AY/R8) was out of service due to the radar data processing system (RDPS) registration alarms that caused the loss of accurate 5 NM separation in comparison with adjacent radar sources. Minimal impact on operations.

October 4, 2015

Incident at GREATER MONCTON ROMEO LEBLANC INTERNATIONAL AIRPORT (ATM - NAVAIDS/radar)

Moncton Area Control Centre (ACC) lost all external radar for 15 minutes when the telecommunication (TELCO) provider, Allstream, was conducting routine maintenance. QX, JT, YT, YR, ZV, QB, CA, and BU radar failed on Radar Data Processing System Re-host (RDPS-R).

February 24, 2013

Incident at QUÉBEC / JEAN LESAGE INTL QC (CYQB) (ATM - NAVAIDS/radar)

Following a number of errors in the data contained in the Radar Data Processing System (RDPS-R) due to snow on the radome, the radar at Québec/Jean-Lesage (CYQB) lost its ability to apply 3 NM separations from 2300Z on February 24 to 1545Z on February 27. There were minor delays to arrivals and departures due to increased separation. The National Operations Centre (NOC) was notified.

February 26, 2013

Incident at MONTRÉAL INTL (MIRABEL) QC (CYMX) (ATM - NAVAIDS/radar)

Following a number of errors in the data contained in the Radar Data Processing System (RDPS-R) due to snow on the radome, the radar at Mirabel (CYMX) lost its ability to apply 3 NM separations from 2100Z on February 26 to 1427Z on February 27. There was no impact on the radar at Montréal (CYUL). The National Operations Centre (NOC) was notified.

January 30, 2013

Incident at OTTAWA / MACDONALD-CARTIER INTL ON (CYOW) (ATM - NAVAIDS/radar)

Following a number of errors in the data contained in RDPS-R. The Ottawa RADAR lost its capability to operate with a 3 nm spacing between aircraft between 1800z and 1947z. Over this period, spacing of 5 nm was applied by the Ottawa RADAR, Minimal operational impact. ------------- Suite à des erreurs de registrations dans RDPS-R, perte de certification du radar d'Ottawa pour l'espacement de 3nm de 1800z à 1942z. Pendant cette période de temps, l'espacement appliqué par le Terminal d'Ottawa a été de 5nm. Impact minimal.

April 28, 2012

Incident at YQM Flight Information Region (ATM - other)

After completing the weekly FDP switch over, it was identified that the RDPS link and the CAATS strip production were not working. Recovery procedures were started and the system returned to normal operation at 1050Z. There was no impact on the operation.

August 18, 2009

Incident at MONTRÉAL / PIERRE ELLIOTT TRUDEAU INTL QC (CYUL) (ATM - other)

Le système de traitement des données radar (RDPS) a été hors de service au centre de contrôle (CCR) de Montréal de 1234Z à 1238Z. Impact: délais mineurs en raison de la mise en place d'arrêts au sol aux aéroports de Montréal/Trudeau (CYUL) et d'Ottawa (CYOW). Le centre national de l'exploitation (NOC) a été avisé.*** ** *** The Radar Data Processing System was offline at the Montreal ACC from 1234Z to 1238Z. Impact: minor delays due to ground stops at the Montreal/Trudeau (CYUL) and Ottawa (CYOW) airports. The National Operations Centre was notified.

August 25, 2008

Incident at EDMONTON INTL AB (CYEG) (ATM - NAVAIDS/radar)

Edmonton ACC had a RDPS (Radar Data Processing System) failure at 0235z. At 0335z, RDPS was running as was NFDPS, (National Flight Data Processing System) however NFDPS was not interacting with RDPS. At 0345z both systems were interacting on a limited basis. By 0415z all flight plans were back in the system. At 0822z a restore was carried out by the DSC (Data System Co-ordinator) and by 0825z all systems were functioning normally.

November 4, 2008

Incident at GREATER MONCTON ROMEO LEBLANC INTERNATIONAL AIRPORT (ATM - NAVAIDS/radar)

The Moncton Flight Information Region experienced a dual Radar Data Processing System (RDPS) failure of short duration, 19:20-19:30 AST, approximately. Adjacent units/NOC were informed with no special handling requirements requested. The Nav Canada Auxiliary Radar Display System (NARDS) operated normally. There was no impact on operations.

December 29, 2006

Incident at MONTRÉAL / PIERRE ELLIOTT TRUDEAU INTL QC (CYUL) (ATM - other)

The radar data processing system (RDPS) was out of service from 2028Z to 2045Z. The BRAVO side of the system had overloaded, and data could not be transferred to the ALPHA side. The systeme was reset manually. The area control centre used the NAV CANADA auxiliary radar display system (NARDS) during the outage. *** *** *** Le système de traitement des données radar (RDPS) a été hors service de 2028Z à 2045Z. Le côté BRAVO du système ayant été surchargé, le transfert des données vers le côté ALPHA n'a pu être effectué. Le système a été réinitialisé manuellement. Le centre de contrôle a utilisé le système auxiliaire d'affichage radar (NARDS) durant la panne.

February 17, 2007

Incident at TORONTO / LESTER B. PEARSON INTL ON (CYYZ) (ATM - other)

UPDATE Supplemental information received from T.S.B. Initial Notification (#A07O0051): The NAV CANADA Radar Data Processing System (RDPS) at the Toronto Area Control Centre (ACC) rejected a flight plan for Skyservice Airlines flight SSV5073. A controller used the "quick file" option to enter a flight plan into the system for SSV5073. The quick file defaulted to an aircraft type of an Airbus A-320 aircraft when, in fact, the aircraft was a Boeing B-757 aircraft. For wake turbulence separation purposes, the Boeing B-757 is considered to be a "Heavy" aircraft for following aircraft and the A-320 is considered to be a "Medium" aircraft. This resulted in inappropriate wake separation (four (4) miles versus five (5) miles) being applied on the downwind into Toronto (LBPIA). Ops. impact -- unknown.
RDPS rejected a flight plan for Skyservice flight SSV5073 a Boeing 757 landingToronto (LBPIA) (CYYZ). At 2328Z a controller used the quick file to enter a flight plan into the RSit system for SSV5073. The quick file defaulted to an aircraft type A320 when in fact the aircraft was a B752. This resulted in inappropriate wake separation being applied on the downwind into Toronto. The Britt Airways, Inc. (d/b/a Continental Express/Air Mike Express (Houston, TX)) flight BTA2592, an Embraer 145, was landing CYYZ from Newark (Liberty) International Airport, NJ (U.S.A.) (KEWR).

March 20, 2007

Incident at EDMONTON INTL AB (CYEG) (ATM - NAVAIDS/radar)

From 1522z to 1527z there was a total RDPS - R failure in the Edmonton ACC. NARDS backup feed worked normal. TOC investigating. Minimal operational impact

February 17, 2007

Incident at Gander ANS Building (ATM - operations)

At 08:02, the Commissionaire and TCO found under floor detectors 135,136,137 were indicating red. These detectors are located in a line in front of the RDPS. A haze was detected in the room but it did not smell like smoke. It smelled and looked like steam. At 08:20, the fire alarm lights began flashing. Controllers and IFSS were informed of a possible fire. At 08:21, an announcement was made to all areas of the building for non-essential personnel to evacuate immediately. At 08:25, the Gander fire department arrived on site. They noticed the steam and smell and began their investigation. At 08:26, operational personnel still working (both ATC and FSS), determined that a possible faulty air conditioner unit set off the fire alarm. At 08:35, the fire alarm activated. All air conditioning units were shut off. The equipment room was becoming hot. At 08:45, the fire department could not locate any fire or smoke. After discussing the situation with the shift manager, FSS supervisor and the commissionaire, the fire department decided to leave. At 09:05, the air conditioner unit # 3, behind the RDPS, had a Freon fitting leaking, At 10:53, the air conditioning contractor was working on AC UNIT # 3 repair. Fire alarm panel detectors D136,D148 AND M289 are disabled until the repairs are completed. Nil TSB

December 2, 2006

Incident at MONTRÉAL / PIERRE ELLIOTT TRUDEAU INTL QC (CYUL) (ATM - other)

The radar data processing system (RDPS) was out of service from 2330Z until 2345Z. There was no impact on ATC operations. A NAV CANADA investigation is underway.

July 25, 2006

Incident at MONTRÉAL / PIERRE ELLIOTT TRUDEAU INTL QC (CYUL) (ATM - other)

The RSiT radar screens shut down between 0619Z and 0624Z. The auxiliary radar display (NARDS) was used as a backup during this period. The radar data processing system (RDPS) was on simplex between 0619Z and 0719Z. The flight data processing system (FDPS) was on simplex between 0619Z and 0738Z.

June 24, 2006

Incident at MONTRÉAL / PIERRE ELLIOTT TRUDEAU INTL QC (CYUL) (ATM - other)

The RDPS was out of service around 1328Z. The system was rebooted around 1335Z as a test and nothing appeared on the screens until 1348Z. No aircraft in flight experienced any delays. Departures from Quebec City (CYQB), Ottawa (CYOW) and Dorval (CYUL) were staggered in order to ensure a safe level of traffic.

June 25, 2006

Incident at MONTRÉAL / PIERRE ELLIOTT TRUDEAU INTL QC (CYUL) (ATM - other)

The link between NFDPS and RDPS was out of service from 0929Z to 1004Z. Limited impact due to the time of the outage.

May 13, 2006

Incident at Centre de contrôle de Montréal (ATM - other)

The connection between NFDPS and RDPS was out of service between 2136z and 2239z, resulting in 15 to 20 minute delays for two private aircraft taking off from Dorval (CYUL).

March 29, 2006

Incident at MONTRÉAL / PIERRE ELLIOTT TRUDEAU INTL QC (CYUL) (ATM - other)

The RDPS was in simplex mode (no redundancy) from 1401Z to 0111Z. No impact on ATC operations. The NOC was notified.

Incident at MONTRÉAL / PIERRE ELLIOTT TRUDEAU INTL QC (CYUL) (ATM - other)

The RDPS was out of service from 1345Z to 1401Z. Limited impact.

September 9, 2006

Incident at VANCOUVER INTL BC (CYVR) (ATM - NAVAIDS/radar)

UPDATE from ANS & Airspace: No further action required.
The Vancouver Radar at Sea Island failed at approximately 0330Z. The SUPU tripped to bypass, and at the same time the site lost both ADU's feeding azimuth reference data to the Vacncouver ACC. RDPS-R would not accept the corrupt data until the ADU's were brought back on line, at which time radar service was put back online into RDPS-R at approximately 0340Z. The impact to Vancouver Terminal operations was minimal due to Victoria (CYYJ) radar coverage mosaiicing.

July 18, 2006

Incident at VANCOUVER INTL BC (CYVR) (ATM - NAVAIDS/radar)

UPDATE from ANS & Airspace: No further action required.
At approximately 21:20Z at Vancouver OSAF-A showed all displays indicating red for failure. Claxons sounded to indicate same. Dual RDP failure resulted in transitioning to NARDS Direct feed and subsequent Cold Start of RDPS-R and trouble shooting requiring the use of NARDS Direct feed starting at 21:20 for a period of about 75 min. This failure did not have any impact on the air traffic being controlled during that time.

March 23, 2006

Incident at SANDSPIT BC (CYZP) (ATM - NAVAIDS/radar)

UPDATE from ANS & Airspace: The Cumshew(CU) Radar PARROT was jumping outside of its window in azimuth. Range was ok. At this time it is believed that this is not an equipment problem. A heavy rainstorm, with gusty winds, had just passed through the area. The temperature was about +6C at the airport. Considering the higher elevation of the PARROT site, and that the radar site is on top of a mountain, it is believed that this condition was caused by a momentary ice build up on either the radar radome or the PARROT antenna. At approximately 1950Z, the VR ATM technologists noted that the PARROT was missing/jumping in azimuth. They started monitoring the PARROT closely. The SSR channels were swapped. The PARROT was moving in azimuth by about .5 of a degree. About 1 hour later the CU radar was offlined from RDPS due to lack of confidence in the radar data. Anchorage also offline the CU radar into their display system. At 2234Z the PARROT returned normally into its box on its own. No further actior required at this time and AN will continue to montor the serviceablity of the Cumshew Radar.
The Cumbshew Radar at Sandspit failed at 2058Z due to an unexplained shift in azimuth. The radar returned to service at 2234Z. All agencies notified.

March 5, 2006

Incident at Toronto ACC (ATM - NAVAIDS/radar)

NAV CANADA staff at Toronto ACC reported that the Radar Data Processing System (RDPS) failed while maintenance was being performed on the Supplementary Power Unit (SUPU). Traffic volume throughout the Toronto FIR was very light at the time and the impact on operations was minimal (no delays were incurred). The RDPS was fully restored at 0915Z.

February 19, 2006

Incident at TORONTO / LESTER B. PEARSON INTL ON (CYYZ) (ATM - other)

From the AOR: ?RDPS channels "A" and "B" both failed requiring the ACC to use NARDS for 20 minutes until RSiT restored at 0500Z.?

March 9, 2006

Incident at EDMONTON INTL AB (CYEG) (ATM - NAVAIDS/radar)

UPDATE ANS and Airspace forwarded the following technical note from Nav Canada: "RDPS was displaying many dual discrete codes in radar airspace overlapping with Calgary radar. RDPS was not getting the North Time Alignment Messages (TAM) from the Calgary radar. At 1552 RDPS reported YC missing North TAM. The error message was not cleared until permission was given to take suggested corrective action taken at 1626. DSC asked for SSR channel swaps on EG and YC sources. XH, OD, KA and XE radar sources were also off-lined. RDPs swapped. None of the above actions had any effect. The Calgary radar source was off-lined and then on-lined, causing a re-sync of the YC radar within RDPS. Problem was corrected. RDPS Technical Bulletin 51 RDPS Dual Target Resolution documents a long standing problem that occasionally occurs in RDPS. "
A radar anomaly occurred at Edmonton ACC when multiple dual discrete codes appeared in both Calgary and Edmonton TCUs. Departure releases were suspended for a short period of time while airborne traffic continued normal operations. Once system reliability was confirmed, departures releases were reinstated with restrictions until the anomaly was totally rectified and continued reliability was confirmed. Normal operations resumed after 45 minutes at 1635Z. There was a significant impact on ATC operations and departure delays were extended.

January 16, 2005

Incident at Centre de contrôle de Montréal (ATM - other)

The link between two Nav Canada systems (NFDPS and RDPS) was down between 0714z and 0751z. The incident had no repercussions.

March 1, 2005

Incident at VANCOUVER INTL BC (CYVR) (ATS operating irregularity, ATM - NAVAIDS/radar)

Update from ANS&A: No further action required.
At 21:13:30Z and again at 21:31:00Z Vancouver ACC experienced a sudden simultaneous loss of three Radars, at Victoria, Cumshewa and Wallensteen. RDPS reported sudden overloads consistant with ECM. DND MARPAC had no knowledge of active jamming at this time but JTIDS exercises had been authorized for the HMCS Algonquin in Esquimalt Harbour daily 1400 - 2350 Z Feb 28 to March 7th 2005.

February 10, 2005

Incident at VANCOUVER INTL BC (CYVR) (ATM - other)

Update from Aerodrome Safety: No further action required.
Dual channel RDPS failure. Cold start, Operation transitioned to NARDS. RDPS/RSIT back at 0049, flightplans restored shortly after. Delays experienced were minimal.

September 3, 2005

Incident at TORONTO / LESTER B. PEARSON INTL ON (CYYZ) (ATS operating irregularity, ATM - NAVAIDS/radar)

At 1958Z, the Toronto ACC RDPS (Radar Display Processing System) channel A failed. The backup channel B was stabilized at 2031Z. Ops. impact -- several aircraft were delayed during that time as a groundstop and extra in-trail spacing for Toronto FIR traffic was required.

September 2, 2005

Incident at Toronto ACC (ATS operating irregularity, ATM - NAVAIDS/radar)

At approximately 1755Z, Toronto ATOS noted NFDP errors occurring. By 1800Z, it was apparent that there was a communications problem between RDPS and NFDPS (which was manifested as a link failure). Sectors were warned that code assignment would be unreliable. On-going troubleshooting by DSC did not reveal the problem. NFDPS hotstarts were not effective. The active radar data processor (RDPB) failed at 1824Z, with RDPA taking over. Without a determination of the problem between NFDPS and RDPS, there were concerns that RDPA would fail as well and sectors were so advised. After the change in RDP channels, a hotstart of NFDPS re-established the link between the systems. The systems appeared stable and Technical Operations advised that diagnostics indicated a hardware fault on RDPB. After approximately 15 minutes of stable operation, normal operations - with a single RDPS channel - were resumed at 1900Z. Ops. impact -- some departures were delayed up to 20 minutes, as flight plan data was not readily available. Generally, delays were minor. A Snowbird practice session scheduled for 1830Z in Terminal airspace was cancelled.

May 11, 2005

Incident at TORONTO / LESTER B. PEARSON INTL ON (CYYZ) (Other operational incident, ATS operating irregularity, ATM - other, ATM - NAVAIDS/radar)

NAV CANADA staff at Toronto ACC advised that there was a dual RDPS failure and the resulting NFDPS failure for approximately 10 minutes caused five (5) aircraft to be delayed less than 10 minutes. NARDS remained reliable in the direct feed mode. The system was restored by 0055Z. A NAV CANADA investigation is underway.

February 3, 2005

Incident at TORONTO / LESTER B. PEARSON INTL ON (CYYZ) (ATS operating irregularity, ATM - NAVAIDS/radar)

NAV CANADA staff at Toronto ACC reported that there was a dual RDPS failure at 0439Z. The operation switched to the NARDS back-up system. NARDS was isolated at 0520Z to maintain the integrity of the flight plans. A crash dump on RDP-A was initiated and RDP-B came online 0558Z. NARDS was re-connected to RDPS at 0630Z. The crash dump was completed on the ancillary interfaces at 0640Z. Dual RDPS was operational at 0642Z. No traffic management initiatives needed to be implemented and there was no operational impact on traffic. Normal operations resumed.

July 25, 2005

Incident at WINNIPEG / JAMES ARMSTRONG RICHARDSON INTL MB (CYWG) (ATM - other)

At approximately 1215Z, the ATOS supervisor at Winnipeg ACC reported that Centre- stored flight plans were not being processed by NFDPS. An attempt to rectify the situation caused a failure of NFDPS-RDPS link. Both systems were back in service two hours later at 1415Z. Cleanup and reloading data by ATOS continued until 1500Z. Winnipeg Tower advised 12 departures were delayed 10 minutes or less and many went VFR. Four aircraft were delayed in excess of 20 minutes: JZA 8470, CRJ WG-OW; CAV 7511, SF34 WG-TH; CAV 7543, SF34 WG-TH and PAG 207, SW4, WG-GO.

March 2, 2005

Incident at WINNIPEG / JAMES ARMSTRONG RICHARDSON INTL MB (CYWG) (ATM - other)

Winnipeg ACC experienced a National Flight Data Processing System (NFDPS) failure. At 1348Z an Radar Data Processing System (RDPS) cold start was initiated as it appeared RDPS was having problems processing data from NFDPS. After completion of the RDPS cold start, the problem persisted. At 1507Z it was noted that the NFDPS RSX printer was out of paper. At 1522Z after a NFDPS hot start the system returned to normal. Between 1400Z and 1545Z, numerous aircraft departing Winnipeg were delayed with the longest delay of just over 1 hour to ACA 295. Aircraft departing other airports in the FIR experienced minor delays up to 10 minutes.

February 27, 2005

Incident at WINNIPEG / JAMES ARMSTRONG RICHARDSON INTL MB (CYWG) (ATM - other)

Routine cold start of RDPS started at 1400Z. Incomplete file transfer from the DMS to RDP occurred, requiring 2nd cold start. The system was fully intact at 1505Z. Three a/c awaiting departure from Winnipeg encountered 5 to 20 minute delays. Nil impact to a/c already en route.

October 14, 2004

Incident at MONTRÉAL / PIERRE ELLIOTT TRUDEAU INTL QC (CYUL) (ATM - other, ATM - operations)

À 0620Z, dans la salle des opération du centre de contrôle régional de Montréal (YUL CCR), tous les équipements et systèmes branchés au SUPU sont tombés en panne. A 0625Z: retour de l'électricité. A 0627Z: retour du lien avec VSCS. A 0645Z: RDPS fonctionnel sur un Canal. A 0730Z: NFDPS et FDPN fonctionnels. A 0750Z: OIDS/R fonctionnel. L'impact a été négligeable pour les usagers à cause de l'heure de l'évènement.At 0620Z, all equipment and systems plugged into the static uninterruptible power unit (SUPU) failed in the operations room at the Montréal area control centre (CYUL ACC). At 0625Z, the electricity was restored. At 0627Z, the link to the voice switching and control system (VSCS) was returned. At 0645Z the radar data processing system (RDPS) was working on one channel. At 0730Z the national flight data processing system (NFDPS) and the flight data planning network (FDPN) were working. At 0750Z the operational information display system (OIDS-R) was working. The impact was negligible for the users due to the time of the occurrence.

September 18, 2004

Incident at VANCOUVER INTL BC (CYVR) (Other operational incident, ATS operating irregularity, ATM - other)

Update from ANS&A: Nav Canada will conduct an investigation into this incident.
The Automatic Weather Distribution System (AWDS)computer is a focal point within the ACC where weather information from diverse sources is collected and forwarded to OIDS. It is a ""single point of failure"" risk as there is no alternate data path and no built-in redundancy. At approximately 18/1105Z the VRACC (Richmond) AWDS power- supply failed, resulting in a loss of data to OIDS. After 1200Z OIDS deleted the stale weather sequences, but continued to send stale altimeters to RDPS until those two systems were manually disconnected at the OIDS I/O server. Manual weather gathering and distribution procedures were implemented. System restored at 1900Z. No operational user impact.

February 2, 2004

Incident at VANCOUVER INTL BC (CYVR) (Other operational incident, ATM - other)

Update from ANS&A: No further action required.
RDPS main processor failed at 2257z, for 2 minutes. Both systems back at 2310z. One departure delayed for two minutes.

October 14, 2004

Incident at EDMONTON INTL AB (CYEG) (ATM - other, ATM - NAVAIDS/radar)

UPDATE ANS and Airspace reported that Radar Data Analysis playback indicated no loss of the radar target when viewing the YMM radar source. Investigation revealed that due to weather, air traffic was not flying normal routes, therefore this anomaly was not discovered in the past. The RDPS tile set was optimized to improve coverage in this area and a new adaptation was loaded the next day.
At 0159Z, JZA 8171, a DHC-8, was 30 NM southeast of Fort McMurray climbing through FL 190 when the aircraft target was no longer presented at the Edmonton ACC McMurray Controller's RSIT display. The target re-appeared as the aircraft climbed through FL 240. A few moments later in the same vicinity, WJA 144, a B737, also disappeared from the radar display and re-appeared in a similar manner.

July 21, 2004

Incident at WINNIPEG / JAMES ARMSTRONG RICHARDSON INTL MB (CYWG) (ATM - other)

At approximately 1805Z, the Winnipeg Area Control Centre RDPS 'A' system failed and 'B' system did not come on line. At 1815Z, restrictions to departures within the Winnipeg FIR were commenced, followed shortly by restrictions for a proposed departures outside the Winnipeg FIR and destined to enter Winnipeg air space. After 2 cold starts, at 1905Z RDPS 'A' failed again but 'B' came on line. At approximately 1920Z, the restrictions on departures within the FIR were lifted to allow 5 minutes between departures off all airports and Winnipeg (5 minutes same direction). Shortly after this, restrictions for departures outside the FIR and destined for the Winnipeg FIR were lifted to allow 5 minutes between departures. At 2145Z, when the RDPS system had proven stable, all 5 minute delays were cancelled. The RDPS system was swapped from 'B' to 'A' at 0412Z and 11 hours later at 0500Z, the system was running dual channel.

July 9, 2004

Incident at EDMONTON INTL AB (CYEG) (ATM - NAVAIDS/radar)

At 0137Z the main side of RDPS started to fail and took the secondary side with it. Both sides were off line for 4 minutes. Both processors were reloaded and normal service was restored at 0141Z. Groundstop at both Edmonton and Calgary airports were initiated and then cancelled when service was restored.
UPDATE ANS and Airspace reported that the Edmonton ACC Radar Data Processing System failed for 4 minutes. Internal contingency plans were initiated. The system was restored and there have been no further occurrences.

June 9, 2004

Incident at WINNIPEG / JAMES ARMSTRONG RICHARDSON INTL MB (CYWG) (ATM - NAVAIDS/radar)

The Winnipeg ACC experienced an RDPS (Radar Data Processing System) failure at 2248Z. After re-loading both systems, RDPS was returned to use at 2333Z. No impact on traffic.

December 16, 2003

Incident at MONTRÉAL / PIERRE ELLIOTT TRUDEAU INTL QC (CYUL) (ATM - other)

Suite à l`installation durant la nuit d`une nouvelle version du logiciel de traitement des données radar (RDPS), les symboles de juridiction des contrôleurs (CJS) n`apparaissaient pas sur les bons secteurs de l`unité de contrôle terminal de Dorval (YUL TCU), Granby ainsi que de l`Ouest. Les contrôleurs ont dû se faire des transferts explicites. Le système de validation des départs successifs (VDS) a été arrêté à CYUL, causant quelques délais à certains usagers. Following the installation of a new version of the radar data processing system (RDPS) software during the night, the controller jurisdiction symbols (CJS) did not appear in the correct sectors of the Dorval terminal control unit (YUL TCU), Granby and West. The controllers had to do explicit transfers. The successive departure validation system was shut down at CYUL, causing delays for some users.

April 30, 2003

Incident at VANCOUVER INTL BC (CYVR) (ATM - other)

At approx 1325z the Shift manager at the Vancouver ACC was made aware that flight progress strips were not being produced. DSC advised that although everything in the computer room appeared to be in the green with no failure indications, there were no strips being produced for the operation. There is limited Tech Ops support in the ACC until 1400z. Problem was narrowed down to the RDPS interface unit that handles the data flow between NFDPS and RDPS. Service was restored approx 1540z. Transborder flights out of BC were impacted up to 10 minutes due to the lack of flight data transfer, but for most traffic internal to Vancouver ACC, delays were kept minimal except for departure delays for YVR which reached up to 40 minutes by 1500 (0800). Service was restored at 1540z and the operation back to normal by 1630z.

April 3, 2003

Incident at VANCOUVER INTL BC (CYVR) (ATS operating irregularity, ATM - other, ATM - inaccurate aeronautical information)

1344z Primary NFDPS system failed. Standby had a known fault with the RDPS interface and as a result, codes had to be manually obtained and many flight progress strips,hand written. Arrival delays were minimal, and for 171 YVR departures, delays reached 30 minutes, averaging 10 minutes. 2325Z Throughout the day numerous failures of the remaining system were experienced and recovered from until the power supply was successfully replaced and the system restored.

September 28, 2003

Incident at TORONTO / LESTER B. PEARSON INTL ON (CYYZ) (ATM - NAVAIDS/radar)

At approximately 2055Z, Toronto ACC experienced a dual RDPS failure. NARDS functioned normally. (new paragraph) Groundstops were issued and all traffic initially routed around Toronto CTA. At about 2115Z limited Toronto departures were released, with a GDP for arrivals issued. (new paragraph) The initial RDPS cold start failed to transfer flight plans smoothly and a second cold start was initiated. RDPS was functional again, with flight plan data, at approximately 2130Z. The system was observed to be stable for about 15 minutes and a transition to normal operations initiated at about 2150Z.

July 24, 2003

Incident at TORONTO / LESTER B. PEARSON INTL ON (CYYZ) (ATM - NAVAIDS/radar)

At the Toronto LBPI Airport (CYYZ), a dual RDPS (Radar Data Processing System) failure occurred. A reload was conducted and the system was restored in dual mode at about 1405Z. The backup radar system operated normally during the failure. Some small impact to air traffic but not readily quantifieable.

June 24, 2003

Incident at TORONTO / LESTER B. PEARSON INTL ON (CYYZ) (ATM - NAVAIDS/radar)

The NAV Canada facility at the Toronto LBPI Airport experienced a full dual channel Radar Data Processing System (RDPS) failure. Data recovery and cold start was required on both channels. The facility resumed single channel operation at approximately 1205Z and full dual channel operation at 1245Z. Approximately 400 flight plans were involved. There were minimal air delays. However a ground stop was implemented from 1110Z to 1120Z, delaying departures. The full data correlation was complete by 1320Z.

More...