Narrative:

This is a serious problem that management is not willing to fix properly. Here at cvg we have 3 RNAV departures that turn into the path of the other runway departures. Not only do they turn into the path of other runway departures but the turn into the wrong controller's airspace. Our management has put a band aid fix on this they call it a 'work around' which increases controller work load and there is an opportunity for human error to happen. If the human error factor does happen it could be anything from separation error to a midair. The 'work around' they are having us do is put a red circle around the departure gate when the clearance is read and turning them off the SID into the right controllers airspace. There have been times when an airplane has gotten out to the runway before somebody noticed that it was one of these bad sids. We have a lot of new and inexperienced controllers missing things. This is one of them. KENLN2 departures off of runway 36R require controllers to take aircraft off of a filed routing to prevent conflicting with runway 36C/36L departures. Instead of having pilots fly the RNAV off of the ground as they prefer to do; controllers have to turn aircraft to avoid entering the wrong departure controller's airspace and to avoid conflicting traffic. BNGLE2 and HAGOL2 departures suffer the same issues as listed above except they involve aircraft departing 18L conflicting with runway 18C/18R departures. Controllers currently have to issue headings off of the runway with the pilot having no expectation to join the RNAV departure or controllers have to issue noise track headings to aircraft to comply with local orders. We recommended that these 3 RNAV departures be NOTAM unusable or not available until they are fixed but management will not do it. Take the human error factor out of it.

Google
 

Original NASA ASRS Text

Title: CVG controller voiced concern regarding locally implemented departure procedures requiring controllers to issue initial heading to aircraft on the RNAV SIDs because of aircraft and airspace conflicts; the reporter suggesting the RNAV procedures be put on hold until revised.

Narrative: This is a serious problem that Management is not willing to fix properly. Here at CVG we have 3 RNAV departures that turn into the path of the other runway departures. Not only do they turn into the path of other runway departures but the turn into the wrong controller's airspace. Our Management has put a band aid fix on this they call it a 'work around' which increases controller work load and there is an opportunity for human error to happen. If the human error factor does happen it could be anything from separation error to a midair. The 'work around' they are having us do is put a red circle around the departure gate when the clearance is read and turning them off the SID into the right controllers airspace. There have been times when an airplane has gotten out to the runway before somebody noticed that it was one of these bad SIDS. We have a lot of new and inexperienced controllers missing things. This is one of them. KENLN2 departures off of Runway 36R require controllers to take aircraft off of a filed routing to prevent conflicting with Runway 36C/36L departures. Instead of having pilots fly the RNAV off of the ground as they prefer to do; controllers have to turn aircraft to avoid entering the wrong Departure Controller's airspace and to avoid conflicting traffic. BNGLE2 and HAGOL2 departures suffer the same issues as listed above except they involve aircraft departing 18L conflicting with Runway 18C/18R departures. Controllers currently have to issue headings off of the runway with the pilot having no expectation to join the RNAV departure or controllers have to issue noise track headings to aircraft to comply with local orders. We recommended that these 3 RNAV departures be NOTAM unusable or Not Available until they are fixed but Management will not do it. Take the human error factor out of it.

Data retrieved from NASA's ASRS site as of April 2012 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.