A cleveland center (ZOB) controller reports of a loss of separation attributed to severe weather avo...

Attributes
ACN	1277417
Time
Date	201507
Local Time Of Day	0001-0600
Place
Locale Reference	ZOB.ARTCC
State Reference	OH
Environment
Light	Night
Aircraft 1
Make Model Name	Medium Large Transport
Operating Under FAR Part	Part 121
Flight Phase	Climb
Flight Plan	IFR
Aircraft 2
Make Model Name	Large Transport
Operating Under FAR Part	Part 121
Flight Phase	Climb
Flight Plan	IFR
Person 1
Function	Enroute
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Time Certified In Pos 1 (yrs) 3
Events
Anomaly	ATC Issue All Types Airspace Violation All Types Conflict Airborne Conflict Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types

Narrative:

I was working R-47 and we had been seeing severe weather avoidance plan (swap) routes all day coming out of chicago center (ZAU) (right into the weather like usual). The usual swap route is otens..anewa..ape. I received the handoff from G-89 on aircraft X climbing to FL330. This swap route that aircraft X was flying was otens..rod; cutting off the back side of my westbound aircraft Y at FL320. I would imagine that sector G-36 did not receive a pointout on aircraft X since if they had; they should have referenced aircraft Y as traffic. I turned aircraft X back to the left and stopped the aircraft's climb to try to avoid losing standard separation. After I was comfortable with the separation; I turned aircraft X back on course and climbed the aircraft.swap routes need to be consistent. Also; when there is not a swap route program in place; aircraft need to not be filed for those swap routes. Airspace and routes are designed for a reason and need to be followed unless otherwise coordinated.

Original NASA ASRS Text

Title: A Cleveland Center (ZOB) Controller reports of a loss of separation attributed to Severe Weather Avoidance Plan SWAP0 and aircraft not being pointed out correctly.

Narrative: I was working R-47 and we had been seeing Severe Weather Avoidance Plan (SWAP) routes all day coming out of Chicago Center (ZAU) (right into the weather like usual). The usual SWAP route is OTENS..ANEWA..APE. I received the handoff from G-89 on Aircraft X climbing to FL330. This SWAP route that Aircraft X was flying was OTENS..ROD; cutting off the back side of my westbound Aircraft Y at FL320. I would imagine that sector G-36 did not receive a pointout on Aircraft X since if they had; they should have referenced Aircraft Y as traffic. I turned Aircraft X back to the left and stopped the aircraft's climb to try to avoid losing standard separation. After I was comfortable with the separation; I turned Aircraft X back on course and climbed the aircraft.SWAP routes need to be consistent. Also; when there is not a SWAP route program in place; aircraft need to not be filed for those SWAP routes. Airspace and routes are designed for a reason and need to be followed unless otherwise coordinated.

Data retrieved from NASA's ASRS site 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.

A cleveland center (ZOB) controller reports of a loss of separation attributed to severe weather avoidance plan SWAP0 and aircraft not being pointed out correctly.