Date: 201408
Local time of day: 1201-1800
Location: ALB.Airport, NY
Light: Daylight
Aircraft: Small Transport; Low Wing; 2 Recip Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Takeoff / Launch
ATC / advisory: Tower ALB
Reporter organization: Government
Reporter function: Supervisor / CIC; Ground; Local
Reporter qualification: Air Traffic Control Developmental
Human factors: Situational Awareness; Fatigue; Training / Qualification; Workload; Communication Breakdown
Second reporter function: Local; Ground
Anomaly: Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Incursion Runway
Detector: Person Other Person
Contributing factors: Airport; Human Factors; Procedure
Primary problem: Procedure

Narrative: I arrived at work to find only one CPC was assigned on the shift and I was the only Tower Rated Controller scheduled on the shift until our Supervisor was scheduled at XX00.  After working on position (LOCAL/GROUND/TCIC) for 2 hours and 15 minutes I was relieved by the one CPC on the shift.  He had been relieved by the Supervisor about 5-10 minutes prior.  Airport operations had closed our secondary runway (10/28) for maintenance work on the REIL's.  When this happened I coordinated the closure with the one CPC/CPCIC/RADAR Controller that was here (the same one that relieved me).  During my briefing; knowing he had just come from working the RADAR/CIC position; I gave him a truncated briefing which was essentially the traffic I was working.  I had left out the runway closure in my briefing; but had a memory aid out and visible where I prefer it (between the two departure drop tubes).  I did my overlap and assumed he had full awareness of the position operations.  A while later; it is my understanding that the controller cleared an aircraft for takeoff from the closed runway.  This was approximately 2.5 hours into our shift and roughly the same amount of time on position for him.  On top of all this; though the runway was called closed; there were no X's placed on either end of the runway. The pilot had; to my knowledge; stated the ATIS reflecting the closure and said nothing as well.I recommend better staffing and a better scheduling practice.  There should be better awareness from Supervisors of situations like this.  For months; we have been working 6 day work weeks with 2 hours OT regularly scheduled on the front or back of our shifts.  Typical staffing used to have about 5-6 FPLs and 2-3 Developmentals/CPCIT's.  This morning was 1 FPL and 4 developmentals/CPCIT's.


Second narrative: Working Local and Ground Combined; Runway 1 in use and Runway 28 is closed.  I had been on Radar for 2 hours and 5 minutes; got out of position and instantly relieved another controller working Local who had also been working 2 hours and 10 minutes.  I had known RWY 28 was closed; and the butter bar indicated in front of me that it was as well.  Aircraft X called for taxi and requested Runway 10; I am unsure if she checked in with the ATIS; but it was on the ATIS.  I told her Runway 10 taxi via Charlie.  She read back the instructions and called ready. I threw the strip downstairs to RADAR for a release; they said Runway 10 released.  I cleared Aircraft X for takeoff on Runway 10.  Shortly after airport Ops had called and said the runway was closed; questioning what just happened.  We here have been working 6 day work weeks; with minimal staffing; minimal breaks; and constantly close to or over 2 hours on position.  My question is why Airport Ops never put X's on the runway to show it was closed.  This could have stopped the problem right away. Hire more staffing.Put X's on the runway.


Synopsis: ALB Controller reports an aircraft was cleared for takeoff on a closed runway.