Date: 201606
Local time of day: 1201-1800
Location: ZID.ARTCC, IN
Light: Daylight
Aircraft: Widebody; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Cruise
Airspace: Class A ZID
ATC / advisory: Center ZID
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Distraction; Situational Awareness; Training / Qualification; Workload
Anomaly: ATC Issue All Types; Airspace Violation All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Provided Assistance
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: I walked into the area and was told by the supervisor to plug in with a developmental so the supervisor could perform a certification check ride. I asked if I would need to do anything or be plugged in just for the record; and I was told I wouldn't need to say or do anything. I did monitor the position while the developmental was working; but I had never trained this developmental. We started into a busy and complex sector. Shortly into the session; the adjacent area violated the SOP and caused a couple traffic conflicts in the process. I began to discuss this with the supervisor; and we examined that situation. As that happened; the traffic developed further. I saw the developmental was getting behind; so I started working through a scan with him and prompting him to take certain actions such as switching aircraft that were already out of the airspace and turn aircraft that had been on headings far too long. The developmental uses a far different preferences setting than I do; so it made it extra difficult to work through it.  As I was scanning; I observed Aircraft X about a mile into Sector 66's airspace and flashing a handoff.  I pointed to it on the scope which brought it to the attention of the supervisor and the developmental at the same time. Fortunately; the D-side (also a developmental) had noticed it just as Aircraft X was crossing the boundary. He had already quickly initiated the handoff and dialed into Sector 66 to verbally hand off the aircraft. The Sector 66 controller was mid-transmission and apparently busy; so he did not answer immediately. The Sector 66 controller apologized; accepted the handoff; and told us not to worry about it. I also want to note there were constant loud drilling noises in the background for the entire session which thoroughly distracted all the controllers in the area.In the center; unlike the terminals where I previously worked; supervisors are not certified on most positions. This means there are three people plugged into a radar sector to certify a developmental. It adds potential distraction and a situation where everyone seemingly assumes someone else has taken action to do something. I think the supervisor should have waited for a day when the developmental's trainer was present to do the certification check ride. That trainer would be familiar with the habits and visual appearance of the scope.I would say I was fully responsible for the sector at the time as the OJTI of record. However; I have no way of communicating with other sectors. There is a developmental sitting at the scope with a supervisor next to him. I'm in a tertiary spot in the background where I can't access equipment or anything other than my headset key. It may be better for the supervisor to just monitor from another scope and let the responsible party be in the mix.




Synopsis: ZID Controller reported having to plug in with an unfamiliar Developmental during a checkride on a position the Supervisor was not checked out on. An airspace violation ensued when a handoff was not accepted until a phone call was made with the aircraft in the other sector's airspace.