Narrative:

I did not put a departure message in on aircraft abcd. He subsequently entered ZDV's airspace without coordination. ZDV controller noticed limited data block and called me. It was human error on my part. I acknowledged the aircraft off the ground at gri. On runway heading climbing to 4000 ft I saw limited data block. I checked for traffic there was none. I cleared him on course climbing to FL230. (Top of my altitude stratum.) I did not depart him. I feel a contributing factor was the fact from 1990-1998 we were an all high altitude area (FL240 and above). In 1998 we changed to a high/low confign. Since then we have had a large amount of errors where an old (1990-1998) low altitude controller had an error on new high altitude sector, or in my case, an old high altitude controller had an error on low altitude.

Google
 

Original NASA ASRS Text

Title: RPTR STATES THAT ACFT X ENTERED ZDV'S AIRSPACE WITHOUT PRIOR COORD.

Narrative: I DID NOT PUT A DEP MESSAGE IN ON ACFT ABCD. HE SUBSEQUENTLY ENTERED ZDV'S AIRSPACE WITHOUT COORD. ZDV CTLR NOTICED LIMITED DATA BLOCK AND CALLED ME. IT WAS HUMAN ERROR ON MY PART. I ACKNOWLEDGED THE ACFT OFF THE GND AT GRI. ON RWY HEADING CLBING TO 4000 FT I SAW LIMITED DATA BLOCK. I CHKED FOR TFC THERE WAS NONE. I CLRED HIM ON COURSE CLBING TO FL230. (TOP OF MY ALT STRATUM.) I DID NOT DEPART HIM. I FEEL A CONTRIBUTING FACTOR WAS THE FACT FROM 1990-1998 WE WERE AN ALL HIGH ALT AREA (FL240 AND ABOVE). IN 1998 WE CHANGED TO A HIGH/LOW CONFIGN. SINCE THEN WE HAVE HAD A LARGE AMOUNT OF ERRORS WHERE AN OLD (1990-1998) LOW ALT CTLR HAD AN ERROR ON NEW HIGH ALT SECTOR, OR IN MY CASE, AN OLD HIGH ALT CTLR HAD AN ERROR ON LOW 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.