Narrative:

I was working the busy late morning arrival bank and it became busy enough to have an assistant local controller assigned to the position. I was working two converging landing only runways and each runway had added complexity due to the following conditions. Runway 19R had a disabled aircraft blocking the first high speed exit and runway 12 had multiple taxiway closures forcing all arrivals to roll out to the far end of this 10;500 ft runway to exit. Additional spacing had been requested from approach control to provide the necessary interval for arrivals to clear the runway at the far end. I believe 5 mi and 170 KTS was requested; but it was not being provided. This required intense monitoring on my part and occasional 'south' turns on final on my part to achieve the needed spacing. The incident in question concerned aircraft Y as the leading aircraft and an aircraft X as the trailing aircraft. I was closely watching as the lead aircraft was starting the turnoff at taxiway Y; 9;600 ft down runway 12; as the trailing aircraft X approached the landing threshold. At this point; the assistant local controller was already coordinating with the other local controller; LC1; for traffic and missed approach instructions. I was about to key the mike and issue the 'go-around' instructions to the aircraft X when the aircraft pitched up initiating a missed approach. I then immediately issued appropriate missed approach instructions. As the reason for initiating the missed approach; the pilot cited the aircraft Y at the far end of the runway. The pilot of the aircraft X was vectored for another approach and landing without any further comments. Our approach control routinely disregards the requests made of them to provide what the tower needs to facilitate safe and efficient service to the users. Approach should strictly apply and adhere to the needs of the tower when requested.

Related reports:

Google
 

Original NASA ASRS Text

Title: IAD Local Controllers described a pilot initiated a go-around when landing traffic failed to clear the runway; the reporter allege PCT failed to provide required arrival separation given the circumstances.

Narrative: I was working the busy late morning arrival bank and it became busy enough to have an Assistant Local Controller assigned to the position. I was working two converging landing only runways and each runway had added complexity due to the following conditions. Runway 19R had a disabled aircraft blocking the first high speed exit and Runway 12 had multiple taxiway closures forcing all arrivals to roll out to the far end of this 10;500 FT runway to exit. Additional spacing had been requested from Approach Control to provide the necessary interval for arrivals to clear the runway at the far end. I believe 5 MI and 170 KTS was requested; but it was not being provided. This required intense monitoring on my part and occasional 'S' turns on final on my part to achieve the needed spacing. The incident in question concerned Aircraft Y as the leading aircraft and an Aircraft X as the trailing aircraft. I was closely watching as the lead aircraft was starting the turnoff at Taxiway Y; 9;600 FT down Runway 12; as the trailing Aircraft X approached the landing threshold. At this point; the Assistant Local Controller was already coordinating with the other Local Controller; LC1; for traffic and missed approach instructions. I was about to key the mike and issue the 'go-around' instructions to the Aircraft X when the aircraft pitched up initiating a missed approach. I then immediately issued appropriate missed approach instructions. As the reason for initiating the missed approach; the pilot cited the Aircraft Y at the far end of the runway. The pilot of the Aircraft X was vectored for another approach and landing without any further comments. Our Approach Control routinely disregards the requests made of them to provide what the Tower needs to facilitate safe and efficient service to the users. Approach should strictly apply and adhere to the needs of the Tower when requested.

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.