SR22
Air Traffic Control Fully Certified
Distraction; Situational Awareness
ATC Issue All Types; Airspace Violation All Types; Deviation / Discrepancy - Procedural Published Material / Policy
General None Reported / Taken
Human Factors; ATC Equipment / Nav Facility / Buildings; Procedure
A Cessna 441 was on my frequency trying to land VFR at SER; but flew over the field at 3;000 FT and still couldn't see the runway. So I vectored the Cessna 441 southeast of the field about 15 miles for the GPS Runway 32 approach to SER. When I turned the aircraft to the IAF (ZEKAM) he reported the field insight and cancelled 15-18 miles southeast of SER; I questioned his transmission but he insisted that he had the field insight. While this was going on; I took the hand off on SR22 at 8;000 FT. I was still questioning in my head if the Cessna 441 had actually seen SER or another runway close by. The CIC and I were in the process of trying to confirm [that] Cessna 441 landed at SER when SR22 violated Racer A/B MOA at 8;000 FT. The status board was up to date and it showed the Racer A/B going hot. The Racer MOA should be depicted on our low altitude maps; before an aircraft goes through the lateral confines of a Restricted/MOA. I always double check and make sure it is cold; and if it isn't on our maps we tend to forget about it.
Distracted by trying to confirm landing assured or IFR cancellation; a ZID Controller failed to observe a developing MOA airspace incursion.