Narrative:

The facility began using crda (converging runway display aid) tool to depart runway 32L while landing 27R and 27L per ord standard operating procedure. Myself and the controller in charge (controller in charge) observed the operation and believed that the runway 32L controller may not be properly applying the crda procedures. The controller in charge called to the center tower supervisor to inform him of this observation. We were told that the crda procedures were being applied correctly. As we continued to observe the operation; it became more and more apparent that the crda procedures were not being applied in accordance with the ord SOP. Aircraft X was on approach to runway 27R inside the adw (arrival departure window). On runway 32L; aircraft Y was in position and holding. I then looked back at aircraft Y and saw the aircraft on departure roll with aircraft X on about a 3/4 mile final. I issued aircraft X a go around and miss approach instructions since it was obvious that we would not be in compliance with the crda order or the 7110.65 in relation to converging runway operations. Aircraft X was issued an altitude of 4000 feet and a heading of 040 since I was unable to get in contact with the runway 32L controller due to an improper landline configuration. A traffic call was made to aircraft X in relation to aircraft Y in which aircraft X reported aircraft Y in sight. Aircraft X was then told to contact departure. After an additional call [to] the center tower supervisor; it was revealed that the runway 32L controller had not been using the correct boxes for the crda operation. Recommend the runway 32L controller apply the crda procedures correctly and the supervisor observing the operation and correct the deficiencies. Better training on a procedure that is rarely used.

Related reports:

Google
 

Original NASA ASRS Text

Title: ORD Tower Controller observed that a different runway Tower Controller was not correctly following rules for intersecting runway arrival/departure separation.

Narrative: The facility began using CRDA (Converging Runway Display Aid) tool to depart runway 32L while landing 27R and 27L per ORD Standard Operating Procedure. Myself and the Controller In Charge (CIC) observed the operation and believed that the Runway 32L controller may not be properly applying the CRDA procedures. The CIC called to the center tower supervisor to inform him of this observation. We were told that the CRDA procedures were being applied correctly. As we continued to observe the operation; it became more and more apparent that the CRDA procedures were not being applied in accordance with the ORD SOP. Aircraft X was on approach to Runway 27R inside the ADW (Arrival Departure Window). On Runway 32L; Aircraft Y was in position and holding. I then looked back at Aircraft Y and saw the aircraft on departure roll with Aircraft X on about a 3/4 mile final. I issued Aircraft X a go around and miss approach instructions since it was obvious that we would not be in compliance with the CRDA order or the 7110.65 in relation to Converging Runway Operations. Aircraft X was issued an altitude of 4000 feet and a heading of 040 since I was unable to get in contact with the Runway 32L controller due to an improper landline configuration. A traffic call was made to Aircraft X in relation to Aircraft Y in which Aircraft X reported Aircraft Y in sight. Aircraft X was then told to contact departure. After an additional call [to] the center tower supervisor; it was revealed that the Runway 32L controller had not been using the correct boxes for the CRDA operation. Recommend the Runway 32L controller apply the CRDA procedures correctly and the supervisor observing the operation and correct the deficiencies. Better training on a procedure that is rarely used.

Data retrieved from NASA's ASRS site 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.