Date: 201508
Local time of day: 1201-1800
Location: ZKC.ARTCC, KS
Aircraft: EMB ERJ 145 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class C TUL
ATC / advisory: Center ZKC
Second aircraft: Commercial Fixed Wing
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness; Training / Qualification; Communication Breakdown; Confusion; Human-Machine Interface
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance
Detector: Person Air Traffic Control
Result: Air Traffic Control Provided Assistance
Contributing factors: Human Factors; Procedure; ATC Equipment / Nav Facility / Buildings
Primary problem: Procedure

Narrative: TRACON called ZKC ARTCC to verify if ZKC ARTCC had radar on Aircraft X. I responded in the negative and TRACON proceeded to relay the flight information for Aircraft X i.e. he was a departure climbing to 15;000 feet squawking XXXX and routed direct [fix fix]etc. The TRACON then explained he was unable to flash the aircraft for unknown reasons. I took down the information and full routed Aircraft X and saw there were two flight plans. I called Aircraft X radar contact and gave my initials to the TRACON controller. I then attempted to departure message the Aircraft X flight plan that was proposed out and was unsuccessful. One minute later TRACON called again and explained the reason for not being able to hand off the aircraft with automation was because the Aircraft X call sign still had two flight plans in the system. The TRACON controller then went into further detail saying the other flight plan was an arrival and that Aircraft X had already landed. However; the TRACON controller for some unknown reason was unable to remove that specific flight plan. I then said I would remove the flight plan for him. The TRACON controller responded with a thank you and the call was terminated. The problem with this situation is that the TRACON controller was mistaken. Aircraft X had not yet landed and was actually in ARTCCs' airspace at the same time as the other Aircraft X departure. When I removed the flight plan from the system it then caused a disruption in the ARTCC and took several minutes to sort out. I would recommend the airline dispatcher refrain from permitting such close proximity in time lapse between same call sign flight plans. The dispatcher should monitor more closely identical call signs flight plans and consider delays i.e. weather and maintenance when permitting the usage of same call sign flight plans so as to prevent this incidents in the future. I further recommend instead of assuming an arrival has landed because the same call sign departs; TRACON Controllers do more investigating before requesting the removal of a flight plan.




Synopsis: TRACON could not perform an automated handoff of a departing aircraft to the ARTCC. The reason was a flight plan with the same call sign as the departure was an active flight already in the ARTCC system. Unbeknownst to the ARTCC Controller the ARTCC active flight plan was an arrival to the same airport as the departure which would not handoff. The TRACON Controller mistakenly told the ARTCC Controller the ARTCC active flight plan had already landed. The ARTCC Controller then removed the flight plan from the ARTCC system. This caused the ARTCC sector working the active arrival to lose data on this aircraft.