Narrative:

Sector was severely impacted by WX. Flow control was rerouting large amounts of traffic into sector. Sector was becoming unmanageable. Traffic shut off several mins prior to incident from ZID although some aircraft were still being taken by l-side controller. Several aircraft in my sector's airspace without handoff or pointout. I was distracted by several other things and did not notice air carrier X, who was under my control, deviating for WX down into another sector's airspace without handoff being accepted. L-side was distracted by constant calls on handoff lines. Problem was discovered when conflict alert activated between air carrier X and air carrier Y who was being worked by the other sector. I then noticed air carrier Y descending to FL310 so no action was taken on my part.

Google
 

Original NASA ASRS Text

Title: ACR X DEVIATING FOR WX UNCOORDINATED UNAUTHORIZED PENETRATION OF ADJOINING SECTOR AIRSPACE WAS IN CONFLICT WITH ACR Y. OPDEV.

Narrative: SECTOR WAS SEVERELY IMPACTED BY WX. FLOW CTL WAS REROUTING LARGE AMOUNTS OF TFC INTO SECTOR. SECTOR WAS BECOMING UNMANAGEABLE. TFC SHUT OFF SEVERAL MINS PRIOR TO INCIDENT FROM ZID ALTHOUGH SOME ACFT WERE STILL BEING TAKEN BY L-SIDE CTLR. SEVERAL ACFT IN MY SECTOR'S AIRSPACE WITHOUT HDOF OR POINTOUT. I WAS DISTRACTED BY SEVERAL OTHER THINGS AND DID NOT NOTICE ACR X, WHO WAS UNDER MY CTL, DEVIATING FOR WX DOWN INTO ANOTHER SECTOR'S AIRSPACE WITHOUT HDOF BEING ACCEPTED. L-SIDE WAS DISTRACTED BY CONSTANT CALLS ON HDOF LINES. PROBLEM WAS DISCOVERED WHEN CONFLICT ALERT ACTIVATED BTWN ACR X AND ACR Y WHO WAS BEING WORKED BY THE OTHER SECTOR. I THEN NOTICED ACR Y DSNDING TO FL310 SO NO ACTION WAS TAKEN ON MY PART.

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.