ZDC ARTCC controllers reported concerns with the frequent track deviations on the KILNS SID out of CLT; citing numerous critical conflicts in the past few months.
Synopsis
ZDC ARTCC controllers reported concerns with the frequent track deviations on the KILNS SID out of CLT; citing numerous critical conflicts in the past few months.
Narrative
Aircraft X was climbing out of CLT on the KILNS SID; AUDII transition. After the KILNS waypoint they turned north to QUART; skipping both DURST and AUDII on the arrival. The aircraft was between FL200 and FL210 at this time and climbing to FL270. Conflict alert started between Aircraft X and Aircraft Y; a SHPRD departure out of RDU leaving 170 for FL230. I stopped Aircraft Y's climb at FL210 to ensure separation but did not have time to properly point the aircraft out to T33 before violating their airspace.This early turn puts them in immediate conflict with T33's airspace AND any SHPRD departures out of RDU. This is not a new problem; it has been happening for many years; and I was told it was the 4th occurrence this month.Once the situation was sorted; I explained to the pilot that this is an ongoing problem. He confirmed that he was flying the KILNS Departure but also acknowledged that he wasn't flying over DURST or AUDII. He told me that there was a runway change at CLT.The departure should be NOTAM'd out until it's fixed. There's no reason this should still be happening after all this time and it's inherently unsafe. Of all of the occurrences of aircraft flying routes other than their flight plan; this situation makes up 99% of them. Furthermore; it's completely unpredictable and the result is a nearly 90-degree left turn into an adjacent facility's airspace and our own opposite direction traffic.
Second reporter narrative
KILNS5 SID pilot error. Aircraft X filed CLT.KILNS5.AUDII.QUART.PHLBO4.EWR dropped out DURST and AUDII from their SID and went KILNS direct to QUART.The controller noticed the turn because the data block started flashing with Aircraft Y; RDU.SHRPD STAR westbound.These two aircraft were head-on and the targets crossed out. There was potential for a mid-air collision had Aircraft X not climbed as well. There was a violation of ZTL airspace in the shelf FL240 - FL270 above LIB. Controller working the sector was also asked to file a report.I was sitting in the area as this error occurred and coached the working controller on what to do. As the airspace Subject Matter Expert (SME); I have seen this type of error and have documents spanning from many years ago until today that show a repeated imminent safety risk to the KILNS SID. This is the fourth instance of this known pilot error this month and the second incident in the past three days alone.I asked the Area 2 Front Line Manager (FLM) and the OMIC (Operations Manager in Charge) to call CLT and ZTL to ask for KILNS-BARMY departures as one because there is weather in the sector and the repeated nature of this known safety risk. The OMIC stated that they would not be making the call. They stated that they were monitoring the situation" and for me to "do what you have to do in your report." This is not the first time that this specific OMIC has refused to make this call.Recommendation: Turn off the KILNS SID until the DURST SID is published. Management call CLT and ZTL to shut off KILNS SID indefinitely or; at a minimum; whenever there is a safety risk after an error has occurred. Put the safety of aircraft first."
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.