Narrative:

Aircraft X; a solo student pilot of a C172; landed on runway xxl without incident. At this time I was working local 1 and 2 combined as well as ground 1 and 2; which is common at this hour; but can be difficult and complex due to a sometimes unpredictable flight training schedule. For this incident; the traffic and complexity was moderate to fairly difficult. Due to staffing issues no other controllers were on break at this time or available to open other positions. Aircraft X was instructed to turn off [runway] xxl at N3 and taxi to the ramp via november. Aircraft X then requested pattern work which is normally done on [runway] xxr. The aircraft was instructed to make a 180 and short of runway xxl. Aircraft Y; by now; had checked in and cleared to land on xxl. Aircraft X requested takeoff clearance. With aircraft Y on about a 2 mile file; I cleared aircraft X for a takeoff without delay from xxl [at an intersection] and told the aircraft to expect transition to xxr in the upwind. I watched as I saw the lights from the cessna make a turn onto the runway. My next movement was to the right and sequences the 2 aircraft on the right downwind for xxr. About 10 seconds later I turned my head back to the left to make sure that aircraft X was airborne. I saw what appeared to be cessna lights climbing. The intersection is about 1 mile from the tower and at night is very difficult to see; especially a little cessna 172. Anyways; after I saw the airborne lights; I knew my runway separation would be approved with the other cessna now on about a 1 mile final. The attention was then back to the pattern on xxr to make sure the aircraft were following each other properly. It was at this time that aircraft Y said; 'we have traffic that just departed opposite direction right toward us.' it was at this time that aircraft X's data block appeared on my radar just off the departure end of [runway] yyr. I quickly turned to look and immediately asked aircraft X their heading. The aircraft replied; '245.' the instructed heading was runway heading; or in this instance; 070. I immediately turned aircraft X to the right to avoid the oncoming opposite direction traffic landing xxl. Aircraft Y said he had traffic in sight and passed under aircraft X about 400 ft below. I then turned aircraft X to a 070 heading to clear the xxl final. When the aircraft was back on the upwind; I made a judgment call that pattern work for this aircraft might not be a good idea; the pilot sounding flustered. I told the aircraft to make 180 and join the left downwind for xxl and cleared the aircraft to land. On base; the aircraft overshot the final. I then instructed the aircraft to land xxr. On final for xxr; aircraft X requested a go-around. I then sequenced the aircraft in the pattern for xxr. The aircraft landed xxr without incident and taxied back to the ramp. As aircraft Y was taxiing back to the ramp he informed he had the opposite direction cessna in sight the entire time and was about 400 ft below when he crossed the threshold. At night; the tower sits about 1 mile from the intersection of N3. After dark when the incident occurred; it is extremely difficult to visualize the little aircraft; all you have to find them are the tiny lights on the aircraft. When aircraft X made the turn on the runway it appeared everything at that point was normal. As I took a second look later; I again saw cessna looking lights climbing though the air. Even at this point with the aircraft maybe just 100 ft off the ground; it is still nearly impossible to notice the aircraft departing in the opposite direction. I did notice the data tag pop up early; which again brought my attention back to the aircraft. It was at this point that I and aircraft Y noticed the aircraft departed in the opposite direction. This airport is a very tough facility to work at night. There are at many times numerous aircraft; mostly single engine aircraft on frequency. On a [runway] xx operation; most of these aircraft land and depart from over a mile away from the tower. These aircraft are only required lights that still make it very difficult to position their location and direction. It wasn't until aircraft X's data blocked popped up off the departure end of [runway] yyr that you could tell he was departing the wrong direction. There is not a whole lot that I think can be done in this situation. I will spend more time concentrating on departing aircraft at night and maybe not try and depart an aircraft with another on a 2 mile final. However; aircraft X has to be more aware of her surroundings; especially after just landing xxl then departing the opposite direction. With this being said aircraft Y had aircraft X in his sight and was beneath him as he landed. However; I will make a better effort to ensure that this doesn't happen again.

Related reports:

Google
 

Original NASA ASRS Text

Title: Tower Controller and pilot described a conflict event when an aircraft cleared for takeoff from a runway intersection departed in the opposite direction; conflicting with traffic on final.

Narrative: Aircraft X; a solo student pilot of a C172; landed on Runway XXL without incident. At this time I was working Local 1 and 2 combined as well as Ground 1 and 2; which is common at this hour; but can be difficult and complex due to a sometimes unpredictable flight training schedule. For this incident; the traffic and complexity was moderate to fairly difficult. Due to staffing issues no other controllers were on break at this time or available to open other positions. Aircraft X was instructed to turn off [Runway] XXL at N3 and taxi to the ramp via November. Aircraft X then requested pattern work which is normally done on [Runway] XXR. The aircraft was instructed to make a 180 and short of Runway XXL. Aircraft Y; by now; had checked in and cleared to land on XXL. Aircraft X requested takeoff clearance. With aircraft Y on about a 2 mile file; I cleared aircraft X for a takeoff without delay from XXL [at an intersection] and told the aircraft to expect transition to XXR in the upwind. I watched as I saw the lights from the Cessna make a turn onto the runway. My next movement was to the right and sequences the 2 aircraft on the right downwind for XXR. About 10 seconds later I turned my head back to the left to make sure that aircraft X was airborne. I saw what appeared to be Cessna lights climbing. The intersection is about 1 mile from the Tower and at night is very difficult to see; especially a little Cessna 172. Anyways; after I saw the airborne lights; I knew my runway separation would be approved with the other Cessna now on about a 1 mile final. The attention was then back to the pattern on XXR to make sure the aircraft were following each other properly. It was at this time that aircraft Y said; 'We have traffic that just departed opposite direction right toward us.' It was at this time that aircraft X's data block appeared on my RADAR just off the departure end of [Runway] YYR. I quickly turned to look and immediately asked aircraft X their heading. The aircraft replied; '245.' The instructed heading was runway heading; or in this instance; 070. I immediately turned aircraft X to the right to avoid the oncoming opposite direction traffic landing XXL. Aircraft Y said he had traffic in sight and passed under aircraft X about 400 FT below. I then turned aircraft X to a 070 heading to clear the XXL final. When the aircraft was back on the upwind; I made a judgment call that pattern work for this aircraft might not be a good idea; the pilot sounding flustered. I told the aircraft to make 180 and join the left downwind for XXL and cleared the aircraft to land. On base; the aircraft overshot the final. I then instructed the aircraft to land XXR. On final for XXR; aircraft X requested a go-around. I then sequenced the aircraft in the pattern for XXR. The aircraft landed XXR without incident and taxied back to the ramp. As aircraft Y was taxiing back to the ramp he informed he had the opposite direction Cessna in sight the entire time and was about 400 FT below when he crossed the threshold. At night; the Tower sits about 1 mile from the intersection of N3. After dark when the incident occurred; it is extremely difficult to visualize the little aircraft; all you have to find them are the tiny lights on the aircraft. When aircraft X made the turn on the runway it appeared everything at that point was normal. As I took a second look later; I again saw Cessna looking lights climbing though the air. Even at this point with the aircraft maybe just 100 FT off the ground; it is still nearly impossible to notice the aircraft departing in the opposite direction. I did notice the data tag pop up early; which again brought my attention back to the aircraft. It was at this point that I and aircraft Y noticed the aircraft departed in the opposite direction. This airport is a very tough facility to work at night. There are at many times numerous aircraft; mostly single engine aircraft on frequency. On a [Runway] XX operation; most of these aircraft land and depart from over a mile away from the Tower. These aircraft are only required lights that still make it very difficult to position their location and direction. It wasn't until aircraft X's data blocked popped up off the departure end of [Runway] YYR that you could tell he was departing the wrong direction. There is not a whole lot that I think can be done in this situation. I will spend more time concentrating on departing aircraft at night and maybe not try and depart an aircraft with another on a 2 mile final. However; aircraft X has to be more aware of her surroundings; especially after just landing XXL then departing the opposite direction. With this being said aircraft Y had aircraft X in his sight and was beneath him as he landed. However; I will make a better effort to ensure that this doesn't happen again.

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.