Narrative:

Just retook local position after my break from working the same position. Briefing included all necessary information; runway 9R in use. Aircraft taxing to runway 27L for departure on taxiway B. Strip had 340 heading marked by previous controller with an estimated release of 33 to 35 past the hour. Automatic releases available on runway 9R headings 060-120 inclusive; any other headings need to be coordinated. Previous controller stated that I could coordinate the 340 if I wanted too when the aircraft was at the release time. I waited until the release time; then marked and issued a 300 heading. Thinking that I was on runway 27L; because that is where the aircraft was and runway 27L was the active when I left to go on break; and that 27L has an automatic departure gate of 240-300 inclusive; I thought...'now I don't have to coordinate the heading because I am staying in the departure gate'. Aircraft departed opposite direction on 27L heading 300 without the proper coordination with the departure controller for the opposite direction runway. Recommendation; just because something looks normal (27L departure after just working 27L departures prior to the session) does not mean you can relax. Follow through with thought process. Use memory joggers for unusual ops (i.e. Opposite direction departure...write the runway on the strip to show as different from the active runway...this is SOP here...not followed.)

Google
 

Original NASA ASRS Text

Title: SBN controller described a failure to comply with local procedures that involved a lack of coordination after a runway change had occurred.

Narrative: Just retook Local position after my break from working the same position. Briefing included all necessary information; Runway 9R in use. Aircraft taxing to Runway 27L for departure on Taxiway B. Strip had 340 heading marked by previous Controller with an estimated release of 33 to 35 past the hour. Automatic releases available on Runway 9R headings 060-120 inclusive; any other headings need to be coordinated. Previous Controller stated that I could coordinate the 340 if I wanted too when the aircraft was at the release time. I waited until the release time; then marked and issued a 300 heading. Thinking that I was on Runway 27L; because that is where the aircraft was and Runway 27L was the active when I left to go on break; and that 27L has an automatic departure gate of 240-300 inclusive; I thought...'Now I don't have to coordinate the heading because I am staying in the departure gate'. Aircraft departed opposite direction on 27L heading 300 without the proper coordination with the Departure Controller for the opposite direction runway. Recommendation; just because something looks normal (27L departure after just working 27L departures prior to the session) does not mean you can relax. Follow through with thought process. Use memory joggers for unusual ops (i.e. opposite direction departure...write the runway on the strip to show as different from the active runway...this is SOP here...not followed.)

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.