Date: 201501
Local time of day: 1201-1800
Location: ZID.ARTCC, IN
Light: Daylight
Aircraft: Small Aircraft
Flight plan: IFR
Flight phase: Cruise
Airspace: Class E ZID
ATC / advisory: Center ZID
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Confusion; Distraction; Human-Machine Interface; Situational Awareness; Troubleshooting
Anomaly: ATC Issue All Types; Airspace Violation All Types; Deviation / Discrepancy - Procedural Clearance; 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: Just as I had taken over the radar position at sector 24; the data block for Aircraft X auto-populated in my airspace without prior coordination.  I asked the previous controller whom I relieved if he had any prior knowledge of the aircraft.  He said he did not.  I contacted Clarksburg approach (CKB) to determine if they had any information about the flight.  They informed me that they had coordinated the aircraft with EKN sector at ZDC (sector W01).  I called W01 to confirm that they were working the aircraft.  They said they were.  When I informed the controller that the aircraft was fully in my airspace without coordination; a radar handoff; or communication transfer the controller seemed surprised.  He stated 'I thought he was in Charleston Approach's airspace.' (Airspace which was approximately 50 miles southwest of Aircraft X).  I grew immediately concerned that the aircraft had not been radar identified; but when I asked the W01 controller; they said it had been.  I asked them to initiate a handoff to my sector (after a failed attempt to hand Aircraft X to sector 21; the sector south of mine; I eventually got track control and communication transfer of the aircraft).  A few moments passed and I noticed a second flight plan for an aircraft X1 in my EDST. Its plot was far to the west of Aircraft X.  I called Charleston approach and they told me they were blocking for the aircraft at W01's request.  I grew concerned that the W01 controller did not actually know where the aircraft was.  I felt compelled to radar identify the aircraft and did so. As most events involving ZDC and its controllers; I feel the need to recommend an increase in training.  It seems that the nonchalant culture of that facility leads to errors like this.  The egregious oversight of airspace knowledge is beyond shocking.  In a region of our airspace; where the radar coverage is sometimes intermittent; to allow an aircraft to progress so far into another facility's airspace and 1.)  Not know to whom that airspace belongs. 2.)  Not know for certain where the aircraft actually was is disconcerting to say the least.  It is fortunate that there were not any non-radar operations in that vicinity; as there sometimes tends to be.  If events such as these were isolated; the tone of this narrative would be less tense.  Alas; ZDC's numerous errors and continuous disregard for adjacent facilities is cause to motivate a change in culture which is long overdue.




Synopsis: ZID Controller reports of an aircraft popping up in his airspace. He tracks down who is suppose to be working the aircraft and then later finds another flight plan on the same aircraft. Controller reports of lack of concern from ZDC controllers who were working the aircraft.