Narrative:

Air carrier X inbound to stl at FL290 violated sector 32's airspace due to lack of handoff by ZAU. I first realized incident occurred when aircraft in question checked on frequency over colie intersection. Air carrier X was asked to reset transponder identify on appropriate discrete beacon code. Simultaneously ZAU initiated handoff to our sector. No other aircraft were involved. A potential factor was aircraft's route of flight--overflew kirksville radar site. When this occurs, beacon is momentarily lost. Complete concentration at all times is required of the controller. When his/her guard is dropped, these problems occur.

Google
 

Original NASA ASRS Text

Title: ACR ENTERED ADJACENT FAC AIRSPACE WITHOUT A HANDOFF.

Narrative: ACR X INBND TO STL AT FL290 VIOLATED SECTOR 32'S AIRSPACE DUE TO LACK OF HDOF BY ZAU. I FIRST REALIZED INCIDENT OCCURRED WHEN ACFT IN QUESTION CHKED ON FREQ OVER COLIE INTXN. ACR X WAS ASKED TO RESET XPONDER IDENT ON APPROPRIATE DISCRETE BEACON CODE. SIMULTANEOUSLY ZAU INITIATED HDOF TO OUR SECTOR. NO OTHER ACFT WERE INVOLVED. A POTENTIAL FACTOR WAS ACFT'S ROUTE OF FLT--OVERFLEW KIRKSVILLE RADAR SITE. WHEN THIS OCCURS, BEACON IS MOMENTARILY LOST. COMPLETE CONCENTRATION AT ALL TIMES IS REQUIRED OF THE CTLR. WHEN HIS/HER GUARD IS DROPPED, THESE PROBS OCCUR.

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