SR22
Air Traffic Control Fully Certified
Communication Breakdown; Situational Awareness
ATC Issue All Types; Airspace Violation All Types; Deviation / Discrepancy - Procedural Published Material / Policy
General None Reported / Taken
Human Factors; Procedure
I was working X RADAR position. I was working a SR22 in level flight at nine thousand feet 21 miles southeast of XYZ VORTAC. The aircraft was just crossing the sector boundary into my airspace. The previous sector RADAR Controller called me to advise that the MOA had gone active 2 minutes prior. The area had not been scheduled in the URET and therefore did not appear automatically on the scope when it went active. The aircraft was in the northeast corner of the MOA and I issued a heading to clear the area the quickest way. The aircraft exited the area approximately 2 minutes later. The person that initially takes the request to schedule the MOA (the Center Management Advisory Council); or the area supervisor; should be responsible for inputting the schedule into the URET. This has been an ongoing and consistent problem and is DANGEROUS!
Enroute Controller described an airspace entry event when timely information regarding the MOA was not available in the URET system.