Far local controller described operational error event when clearing a departure for takeoff with tr...

Narrative:

I had a learjet in the local pattern with numerous inbounds and departures. Aircraft X who was following my learjet was cleared to land. After my learjet did a touch and go on runway 36; I decided there was a gap before the landing aircraft X to depart a small aircraft that was full length on runway 36 westbound; because there was not a wake turbulence delay. After I cleared him for takeoff; a call from an aircraft from a nearby airport came over the frequency which I told to contact approach on a different frequency. After that transmission; I knew that I wanted to get aircraft Y who was at intersection B3 and runway 36 out before the learjet came around again. I observed the cessna that I had cleared for takeoff just off the departure end and then proceeded to clear aircraft Y for takeoff at the intersection. After the takeoff clearance I keyed up to my radar controller to point out the learjet who was going to be slightly outside my airspace with his wide pattern during which the aircraft X said that he was going around due to aircraft Y approaching the runway at the B3 intersection. Aircraft Y was past the hold short line but did not appear to be on the runway when aircraft X passed by him. I told aircraft X to enter right traffic for runway 36 and he came around again and landed. Recommendation; I believe the call from the aircraft from a different airport; the point out with radar briefly distracted me along with not scanning effectively before clearing aircraft Y for takeoff contributed to this event. My recommendation would be to advise my ground controller no intersection departures when there are jets in the pattern and wake turbulence delays are possible. This adds a complexity of extending the jet traffic which you might not have room to do when busy; to allow the wake turbulence delay to expire. Also; [the development of] a better scan technique when clearing aircraft for takeoff.

Original NASA ASRS Text

Title: FAR local controller described operational error event when clearing a departure for takeoff with traffic on final; reporter noting the need to improve airport scanning before take off clearances are issued.

Narrative: I had a Learjet in the local pattern with numerous inbounds and departures. Aircraft X who was following my Learjet was cleared to land. After my Learjet did a touch and go on Runway 36; I decided there was a gap before the landing Aircraft X to depart a small aircraft that was full length on Runway 36 westbound; because there was not a wake turbulence delay. After I cleared him for takeoff; a call from an aircraft from a nearby airport came over the frequency which I told to contact approach on a different frequency. After that transmission; I knew that I wanted to get Aircraft Y who was at Intersection B3 and Runway 36 out before the Learjet came around again. I observed the Cessna that I had cleared for takeoff just off the departure end and then proceeded to clear Aircraft Y for takeoff at the intersection. After the takeoff clearance I keyed up to my RADAR controller to point out the Learjet who was going to be slightly outside my airspace with his wide pattern during which the Aircraft X said that he was going around due to Aircraft Y approaching the runway at the B3 Intersection. Aircraft Y was past the hold short line but did not appear to be on the runway when Aircraft X passed by him. I told Aircraft X to enter right traffic for Runway 36 and he came around again and landed. Recommendation; I believe the call from the aircraft from a different airport; the point out with RADAR briefly distracted me along with not scanning effectively before clearing Aircraft Y for takeoff contributed to this event. My recommendation would be to advise my Ground Controller no intersection departures when there are jets in the pattern and wake turbulence delays are possible. This adds a complexity of extending the jet traffic which you might not have room to do when busy; to allow the wake turbulence delay to expire. Also; [the development of] a better scan technique when clearing aircraft for takeoff.

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	880214
Time
Date	201003
Local Time Of Day	0601-1200
Place
Locale Reference	FAR.Tower
State Reference	ND
Aircraft 1
Make Model Name	Beechcraft King Air Undifferentiated or Other Model
Flight Phase	Landing
Route In Use	Visual Approach
Flight Plan	IFR
Aircraft 2
Make Model Name	Small Aircraft Low Wing 1 Eng Retractable Gear
Flight Phase	Takeoff
Route In Use	None
Flight Plan	VFR
Person 1
Function	Local
Qualification	Air Traffic Control Fully Certified
Person 2
Function	Supervisor / CIC
Events
Anomaly	ATC Issue All Types Conflict Ground Conflict Critical Deviation - Procedural Published Material / Policy

Far local controller described operational error event when clearing a departure for takeoff with traffic on final; reporter noting the need to improve airport scanning before take off clearances are issued.