D10 controller described go around event when traffic on parallel approach to runway 35R did not res...

Narrative:

I was conducting OJT (on job training) on AR1/AR2 combined. OJT was also being conducted on AR3. Dfw was running simultaneous dependent ILS approaches to runways 36L/35R using procedures defined in our local wavier. AR3 had coordinated to turn their arrival in early and aircraft X was to be cleared for approach dependent to AR3's aircraft. The AR3 controller was late turning their traffic in. We turned aircraft X to final and maintained altitude separation until AR3's aircraft was established on final. We then cleared aircraft X for ILS runway 35R approach but that aircraft was above glide slope. They descended to glide slope but never slowed the aircraft. We transferred communications to dfw tower. Dfw tower advised us they were not talking to aircraft X. We attempted communications transfer again. Aircraft X advised on our frequency they were going around. We switched aircraft X to dfw tower again for instructions. We verified aircraft X was on tower frequency. Aircraft X called us again over the departure end of the runway again. I observed traffic to their left that had departed runway 35C. I issued traffic and a turn to aircraft X. I instructed developmental to hand off and switch aircraft X to the appropriate controller.

Original NASA ASRS Text

Title: D10 Controller described go around event when traffic on parallel approach to Runway 35R did not respond to repeated calls from ATC; elected to initiate a go around that resulted in considerable confusion between the tower and the approach controllers.

Narrative: I was conducting OJT (on job training) on AR1/AR2 combined. OJT was also being conducted on AR3. DFW was running simultaneous dependent ILS approaches to Runways 36L/35R using procedures defined in our local wavier. AR3 had coordinated to turn their arrival in early and Aircraft X was to be cleared for approach dependent to AR3's aircraft. The AR3 Controller was late turning their traffic in. We turned Aircraft X to final and maintained altitude separation until AR3's aircraft was established on final. We then cleared Aircraft X for ILS Runway 35R approach but that aircraft was above glide slope. They descended to glide slope but never slowed the aircraft. We transferred communications to DFW Tower. DFW Tower advised us they were not talking to Aircraft X. We attempted communications transfer again. Aircraft X advised on our frequency they were going around. We switched Aircraft X to DFW Tower again for instructions. We verified Aircraft X was on Tower frequency. Aircraft X called us again over the departure end of the runway again. I observed traffic to their left that had departed Runway 35C. I issued traffic and a turn to Aircraft X. I instructed developmental to hand off and switch Aircraft X to the appropriate controller.

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.

Attributes
ACN	874742
Time
Date	201002
Local Time Of Day	1801-2400
Place
Locale Reference	DFW.Airport
State Reference	TX
Aircraft 1
Make Model Name	A320
Operating Under FAR Part	Part 121
Flight Plan	IFR
Aircraft 2
Make Model Name	Commercial Fixed Wing
Operating Under FAR Part	Part 121
Flight Plan	IFR
Person 1
Function	Approach
Qualification	Air Traffic Control Fully Certified
Person 2
Function	Local
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy

D10 controller described go around event when traffic on parallel approach to runway 35R did not respond to repeated calls from ATC; elected to initiate a go around that resulted in considerable confusion between the tower and the approach controllers.