Narrative:

I was working local control. Air carrier X checked in on visual approach runway 22. Shortly after; air carrier Y reported ready for takeoff at the approach end of runway 22. Air carrier X was between 3-4 mile final; and I cleared air carrier Y for takeoff with no delay. After a short delay; air carrier Y read back the takeoff clearance and stated no delay. I then advised air carrier X of the departing traffic. Air carrier Y proceeded slowly onto the approach end of runway 22. After another delay; I reiterated 'no delay please' to air carrier Y. He read back 'roger' and began rolling down the runway at taxi speed. About one minute after I issued the takeoff clearance; air carrier Y was still very slowly taxiing down the runway. I saw there would be no way to maintain the required 6000 ft runway separation between the two jets. I canceled air carrier Y's takeoff clearance; then immediately sent air carrier X around. At this point; air carrier X was approximately one half mile final. Air carrier X began the climb and overflew air carrier Y on the runway. While there was no loss of separation; an unnecessary go-around was caused. I believe causing factors were me trying to unnecessarily get one aircraft in front of the other to expedite traffic flow and air carrier Y's delayed takeoff. Recommendation; I'm not sure how the pilot could be further encouraged to take off sooner. Building a larger gap ahead of landing aircraft would be beneficial. Also; implementation of tiph procedures would greatly help similar scenarios at our airport. Tiph would not have affected this incident; but there are often times where controllers have to get airplanes closer than necessary because tiph is not available to us.

Google
 

Original NASA ASRS Text

Title: EVV controller described simultaneous cancellation of take off clearance/go around event when a departure failed to expedite takeoff as requested.

Narrative: I was working Local Control. Air Carrier X checked in on visual approach Runway 22. Shortly after; Air Carrier Y reported ready for takeoff at the approach end of Runway 22. Air Carrier X was between 3-4 mile final; and I cleared Air Carrier Y for takeoff with no delay. After a short delay; Air Carrier Y read back the takeoff clearance and stated no delay. I then advised Air Carrier X of the departing traffic. Air Carrier Y proceeded slowly onto the approach end of Runway 22. After another delay; I reiterated 'no delay please' to Air Carrier Y. He read back 'roger' and began rolling down the runway at taxi speed. About one minute after I issued the takeoff clearance; Air Carrier Y was still very slowly taxiing down the runway. I saw there would be no way to maintain the required 6000 ft runway separation between the two jets. I canceled Air Carrier Y's takeoff clearance; then immediately sent Air Carrier X around. At this point; Air Carrier X was approximately one half mile final. Air Carrier X began the climb and overflew Air Carrier Y on the runway. While there was no loss of separation; an unnecessary go-around was caused. I believe causing factors were me trying to unnecessarily get one aircraft in front of the other to expedite traffic flow and Air Carrier Y's delayed takeoff. Recommendation; I'm not sure how the pilot could be further encouraged to take off sooner. Building a larger gap ahead of landing aircraft would be beneficial. Also; implementation of TIPH procedures would greatly help similar scenarios at our airport. TIPH would not have affected this incident; but there are often times where controllers have to get airplanes closer than necessary because TIPH is not available to us.

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.