Air Traffic Control Fully Certified
Air Traffic Control Time Certified In Pos 1 (yrs) 10
Situational Awareness
ATC Issue All Types; Conflict Ground Conflict; Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
Procedure; Manuals
I was working Local Control during a lull period in between pushes. The push was just about to start. With Runway 18R being closed; we were occasionally arriving to Runway 18L and we were also arriving to 13R which is a converging runway. Like I said; the push was about to start and the taxi status and our hat (position who controls departure gates) status had been set to the west side only having west departures and sending all other departures to the eastside. The Ground Controller accidently kept a northbound departure. He had the taxi status mistaken. Since he had mistaken the hat and taxi status the controller failed to underline the SID in red to remind me that I had to get a release. Then during this aircraft Y checked on to Runway 13R and I cleared him to land. Also I had an aircraft inbound to runway 18R. I put the BLECO in position and realized I had not obtained a release from Local East. I called Local East and got the release. I then launched aircraft X and the supervisor advised me I was in the Converging Runway Operation (CRO) box. I just barely missed getting through the extended centerline for 13R before aircraft Y landed 13R.First of all get rid of CRO procedure. In my opinion it is totally unnecessary. My guard was down being that I was in between pushes. I felt rushed to launch aircraft X because I had obtained the release; even though I did not need to rush. I did not perform my usual scan of the airport and I just simply forgot about the 13R arrival. I need to ensure that I go through all my mental checks before I issue a takeoff clearance.
DFW Local Controller reported clearing an aircraft for takeoff with an arrival landing on the converging non intersecting runway.