Mci tower controller described conflict event involving traffic landing runway 1L and a departure fr...

Attributes
ACN	826757
Time
Date	200903
Place
Locale Reference	MCI.Airport
State Reference	MO
Environment
Flight Conditions	Marginal
Light	Daylight
Aircraft 1
Make Model Name	Regional Jet 700 ER/LR (CRJ700)
Operating Under FAR Part	Part 121
Flight Phase	Initial Climb
Flight Plan	IFR
Aircraft 2
Make Model Name	MD-80 Series (DC-9-80) Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	Landing
Flight Plan	IFR
Person 1
Function	Departure Approach Local
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Radar 24 Air Traffic Control Time Certified In Pos 1 (yrs) 26
Events
Anomaly	Conflict Airborne Conflict

Narrative:

Aircraft X was cleared for takeoff on runway 27; with aircraft Y on 8-9 mile final for runway 1L at mci. Local controller was trying to coordinate alternate heading for aircraft X to northwest with the departure controller. Several attempts were made to get heading. I noted that I had not seen aircraft X depart yet. Turned and saw aircraft X was on the roll; but only 1/2 way down runway; with aircraft Y on 3 miles final. Both aircraft were visually observed; advised local to send aircraft Y around on an immediate 270 degree heading. Local sent aircraft Y around; but I had to tell them immediate again. Aircraft Y did go around on about a 1-2 mile final and aircraft X was turned to a northwest heading. Both aircraft were kept in sight and switched to departure; once on diverging headings. Closest distance was probably 1-1/2 miles; with aircraft turning away from each other.

Original NASA ASRS Text

Title: MCI Tower Controller described conflict event involving traffic landing Runway 1L and a departure from Runway 27; claiming the late go-around issued by the Local Controller caused the event.

Narrative: Aircraft X was cleared for takeoff on Runway 27; with Aircraft Y on 8-9 mile final for Runway 1L at MCI. Local Controller was trying to coordinate alternate heading for Aircraft X to northwest with the Departure Controller. Several attempts were made to get heading. I noted that I had not seen Aircraft X depart yet. Turned and saw Aircraft X was on the roll; but only 1/2 way down runway; with Aircraft Y on 3 miles final. Both aircraft were visually observed; advised Local to send Aircraft Y around on an immediate 270 degree heading. Local sent Aircraft Y around; but I had to tell them immediate again. Aircraft Y did go around on about a 1-2 mile final and Aircraft X was turned to a northwest heading. Both aircraft were kept in sight and switched to Departure; once on diverging headings. Closest distance was probably 1-1/2 miles; with aircraft turning away from each other.

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.

Mci tower controller described conflict event involving traffic landing runway 1L and a departure from runway 27; claiming the late go-around issued by the local controller caused the event.