Narrative:

I as controller in charge had called the departure controller to request we scan our non-standard heading strip/s prior to any runway 24 departures due to the wind favoring 24 so drastically. T75 had already given us the headings of 270 and 240 to use for all turbo-prop departures. The departure controller said not to coordinate every departure off of runway 24. I went over and told the local control this. Local control had traffic landing runway 24 with training in progress on ground control. Ground control was using taxiway C to taxi to runway 29. Local control just discussed with the ground control trainer and trainee about using taxiway D to taxi to runway 29 to avoid the problems of the 24 arrivals not being able to turn off at taxiway C. Local control landed a traffic on 24 and had him turn off at C to head straight to the pad due to traffic opposite direction traffic. During this course of events; local control had put another air carrier on runway 29 to line up and wait. Local control had put aircraft X on runway 24 with traffic about 2 out and gave ground control the crossing while coordinating the 24 departure with the departure controller. I assumed that the 24 departure would be after traffic on a 2 mile final for runway 24. I was watching the aircraft Y approaching to cross runway 24 and listening to ground control prompt him to hurry; also watching the air carrier not move on runway 29. Then the ground control trainer said; 'you're rolling'! Ground control trainer then tried to stop the aircraft Y from crossing the hold short lines for runway 24. The phone rang and I answered just when the asde-X went off. The ground control trainer told local control to send that guy around and he did. I told the supervisor. Contributing factors to me was the excessive requirement to coordinate every jet departure off a runway that the TRACON had already given us headings to use. This created one extra step. On all the asdx displays the runway configuration is on the approach end of runway 24. When a 24 departure approaches and turns onto runway 24 there is a blob of letters on the approach end of the runway that is unreadable; aircraft X just happened to be a beautiful white aircraft that blended in nicely to the runway markings until he rolled. Training was also a factor in this situation. Recommendation; establish standard procedures for runway 24 turbo jet departures. The requirement to verbally coordinate is redundant and ridiculous.

Related reports:

Google
 

Original NASA ASRS Text

Title: STL Controller described a go around event when taxiing traffic crossed a hold line; the reporter indicating that excessive coordination requirements with the TRACON and training both were contributing factors in this event.

Narrative: I as CIC had called the Departure Controller to request we scan our non-standard heading strip/s prior to any Runway 24 departures due to the wind favoring 24 so drastically. T75 had already given us the headings of 270 and 240 to use for all turbo-prop departures. The Departure Controller said not to coordinate every departure off of Runway 24. I went over and told the Local Control this. Local Control had traffic landing Runway 24 with training in progress on Ground Control. Ground Control was using Taxiway C to taxi to Runway 29. Local Control just discussed with the Ground Control trainer and trainee about using Taxiway D to taxi to Runway 29 to avoid the problems of the 24 arrivals not being able to turn off at Taxiway C. Local Control landed a traffic on 24 and had him turn off at C to head straight to the pad due to traffic opposite direction traffic. During this course of events; Local Control had put another air carrier on Runway 29 to line up and wait. Local Control had put Aircraft X on Runway 24 with traffic about 2 out and gave Ground Control the crossing while coordinating the 24 departure with the Departure Controller. I assumed that the 24 departure would be after traffic on a 2 mile final for Runway 24. I was watching the Aircraft Y approaching to cross Runway 24 and listening to Ground Control prompt him to hurry; also watching the air carrier not move on Runway 29. Then the Ground Control trainer said; 'You're rolling'! Ground Control trainer then tried to stop the Aircraft Y from crossing the hold short lines for Runway 24. The phone rang and I answered just when the ASDE-X went off. The Ground Control trainer told Local Control to send that guy around and he did. I told the supervisor. Contributing factors to me was the excessive requirement to coordinate every jet departure off a runway that the TRACON had already given us headings to use. This created one extra step. On all the ASDX displays the runway configuration is on the approach end of Runway 24. When a 24 departure approaches and turns onto Runway 24 there is a blob of letters on the approach end of the runway that is unreadable; Aircraft X just happened to be a beautiful white aircraft that blended in nicely to the runway markings until he rolled. Training was also a factor in this situation. Recommendation; establish standard procedures for Runway 24 Turbo Jet departures. The requirement to verbally coordinate is redundant and ridiculous.

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.