Narrative:

Aircraft X awaiting takeoff. TRACON calls and changes the heading turn left heading 270 to turn right heading 310; which was relayed to me by the ground controller; written on the strip and on my pad. Aircraft Y; an aircraft based at this airport (though quite probably not flown by a pilot from this airport) lands; and begins to turn left onto a taxiway which is notamed closed and has been for a couple of months. I issue a right turn onto the crossing runway into our 'bailout' area; and instead of turning right; as I am instructing; he starts a left turn onto the closed portion of a runway which is also notamed closed and has been for a couple of months. I have to insistently; and probably not as politely as I should have; tell him to turn right. All of this because I have traffic bearing down on final; but it is not yet imminent. He exits; finally; and we are good. I get aircraft X onto the runway; luaw (line up and wait); and clear him for takeoff. On departure; he makes a hard left turn (60 degrees of bank if not more) right into traffic on the downwind. Since I switched him early because I had no conflicts; I have to get on the line to find out what is going on while also issuing a traffic alert to the C172 who is in the way. He finally turns westbound; and I cannot remember if he got the 310 heading; which would have solved everything. Unfortunately; the controller in charge (controller in charge) was also engaged in the issues with aircraft Y who could not follow directions.due to the distraction by aircraft Y; I should have referred back to the strip before launching aircraft X. I failed to scan my pad and the strip to ensure I issued the heading. Furthermore; I showed a bad example as I am a flm (front line manager). It is my job to be better than my controllers; and yet I am human.

Google
 

Original NASA ASRS Text

Title: MYF Local Controller forgot to issue a revised departure heading to a departing aircraft.

Narrative: Aircraft X awaiting takeoff. TRACON calls and changes the heading turn left heading 270 to turn right heading 310; which was relayed to me by the Ground Controller; written on the strip and on my pad. Aircraft Y; an aircraft based at this airport (though quite probably not flown by a pilot from this airport) lands; and begins to turn left onto a taxiway which is NOTAMed closed and has been for a couple of months. I issue a right turn onto the crossing runway into our 'bailout' area; and instead of turning right; as I am instructing; he starts a left turn onto the closed portion of a runway which is also NOTAMed closed and has been for a couple of months. I have to insistently; and probably not as politely as I should have; tell him to turn right. All of this because I have traffic bearing down on final; but it is not yet imminent. He exits; finally; and we are good. I get Aircraft X onto the runway; LUAW (Line Up And Wait); and clear him for takeoff. On departure; he makes a hard left turn (60 degrees of bank if not more) right into traffic on the downwind. Since I switched him early because I had no conflicts; I have to get on the line to find out what is going on while also issuing a traffic alert to the C172 who is in the way. He finally turns westbound; and I cannot remember if he got the 310 heading; which would have solved everything. Unfortunately; the CIC (Controller In Charge) was also engaged in the issues with Aircraft Y who could not follow directions.Due to the distraction by Aircraft Y; I should have referred back to the strip before launching Aircraft X. I failed to scan my pad and the strip to ensure I issued the heading. Furthermore; I showed a bad example as I am a FLM (Front Line Manager). It is my job to be better than my controllers; and yet I am human.

Data retrieved from NASA's ASRS site 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.