Narrative:

Aircraft involved air carrier X (level FL310) and air carrier Y (climbing to FL330). Ny center and cle center were in swap routing for last 4 hours, however, clear flow control never advised areas involved of the swap. Air carrier Y climbing eastbound on J146 toward etg VORTAC and air carrier X was rted psb J61 northwest over etg VORTAC. New york center had received an utm (unsuccessful transmission message) concerning air carrier X 28 mins prior to the error but never forwarding the information. My center attempted to handoff air carrier X to clear but due to the utm, clear had no information on air carrier X so radar associate took radar contact and manually entered the flight plan. Coordination with radar controller was incomplete. Radar associate had been off the control room floor for the previous 9 weeks. Air carrier X destination was msp, which in cle center is J60 (due east). However new york had rted him J61 due to swap. No coordination. Causes. Swap route not coordination (there are 8 swap rtes from lga direct msp). Radar associate not current or proficient. Tmu did not coordination WX routing. Error occurred less than 9 mi (approximately 1 min) into cle center airspace. Utm message ignored in new york. Callback conversation with reporter revealed the following information. Reporter stated type's of aircraft large transport, medium large transport. Sep was 4.1 mi and 100' above FL290. Reporter said conflict alert activated but not in time. Situation with ZNY flow is they implement swap rtes (there are 8 different rtes) however they do not inform ZOB which route the aircraft are going to be on. Air carrier X made a turn on a swap route which he did not expect. Air carrier X and Y were climbing to assigned altitude.

Related reports:

Google
 

Original NASA ASRS Text

Title: ACR X HAD LESS THAN STANDARD SEPARATION FROM ACR . SYSTEM ERROR. SITUATION: ARTCC ARTCC INTERFAC COORD ZNY DOES NOT INFORM ZOB WHICH SWAP ROUTES ACFT ARE ON. ZOB FLOW CTLR TECHNIQUE COM.

Narrative: ACFT INVOLVED ACR X (LEVEL FL310) AND ACR Y (CLBING TO FL330). NY CTR AND CLE CTR WERE IN SWAP RTING FOR LAST 4 HRS, HOWEVER, CLR FLOW CTL NEVER ADVISED AREAS INVOLVED OF THE SWAP. ACR Y CLBING EBND ON J146 TOWARD ETG VORTAC AND ACR X WAS RTED PSB J61 NW OVER ETG VORTAC. NEW YORK CTR HAD RECEIVED AN UTM (UNSUCCESSFUL XMISSION MESSAGE) CONCERNING ACR X 28 MINS PRIOR TO THE ERROR BUT NEVER FORWARDING THE INFO. MY CTR ATTEMPTED TO HDOF ACR X TO CLR BUT DUE TO THE UTM, CLR HAD NO INFO ON ACR X SO RADAR ASSOCIATE TOOK RADAR CONTACT AND MANUALLY ENTERED THE FLT PLAN. COORD WITH RADAR CTLR WAS INCOMPLETE. RADAR ASSOCIATE HAD BEEN OFF THE CTL ROOM FLOOR FOR THE PREVIOUS 9 WKS. ACR X DEST WAS MSP, WHICH IN CLE CTR IS J60 (DUE E). HOWEVER NEW YORK HAD RTED HIM J61 DUE TO SWAP. NO COORD. CAUSES. SWAP RTE NOT COORD (THERE ARE 8 SWAP RTES FROM LGA DIRECT MSP). RADAR ASSOCIATE NOT CURRENT OR PROFICIENT. TMU DID NOT COORD WX RTING. ERROR OCCURRED LESS THAN 9 MI (APPROX 1 MIN) INTO CLE CTR AIRSPACE. UTM MESSAGE IGNORED IN NEW YORK. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO. RPTR STATED TYPE'S OF ACFT LGT, MLG. SEP WAS 4.1 MI AND 100' ABOVE FL290. RPTR SAID CONFLICT ALERT ACTIVATED BUT NOT IN TIME. SITUATION WITH ZNY FLOW IS THEY IMPLEMENT SWAP RTES (THERE ARE 8 DIFFERENT RTES) HOWEVER THEY DO NOT INFORM ZOB WHICH RTE THE ACFT ARE GOING TO BE ON. ACR X MADE A TURN ON A SWAP RTE WHICH HE DID NOT EXPECT. ACR X AND Y WERE CLBING TO ASSIGNED ALT.

Data retrieved from NASA's ASRS site as of July 2007 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.