Narrative:

[I was] working local control; departing runway 28R; also landing runway 28R; 28L; and runway 32. Traffic [was] light; no stand-alone supervision in the cab; so I was unable to use luaw for my 28R departures. I had 3 aircraft to depart; all filed over ewc VOR; and needed to meet release times for tbm/apreq airports. Arrival traffic was on about a 12 mile final when I switched the first aircraft to departure. Since I was unable to luaw; I had to clear the next 2 aircraft from the parallel taxiway; facing the downwind direction. Basically; as soon as I switch aircraft #1 to departure; I was able to clear aircraft #2; and then do the same with aircraft #3. A g-iv had taxied out from a hangar located north of the departure end of runway 28R. I was not in a position to allow him to cross runway 28R until my arrival had landed. Total wait time about 4 or 5 minutes. The g-iv asked ground control for the phone number for the supervisor; and this was given to the crew. When the g-iv got to the approach end of the runway; I called them and asked if they were ready for departure. The reply was they would be ready in 'a minute'. When I got on break; I stopped in the TRACON to inform the supervisor what had happened. The supervisor informed me that they had already spoken to someone in the g-iv. This might explain why they were not ready when they got to the runway. Please re-visit the no luaw criteria. It does not enhance safety; it degrades safety by forcing controllers to clear traffic for departure from a non-standard location. It forces a controller to guess as to how fast an aircraft can make the turn to the runway; will he start take off roll immediately; and will he even start to move as soon as I expect him to. In this case; it delayed an aircraft from crossing a runway in order to adhere to a regulation that; I say again; does not enhance safety.

Related reports:

Google
 

Original NASA ASRS Text

Title: PIT Controller voiced concern regarding the LUAW requirements that reference the presence of a supervisor/CIC; describing unnecessary departure delays resulting from this policy.

Narrative: [I was] working Local Control; departing Runway 28R; also landing Runway 28R; 28L; and Runway 32. Traffic [was] light; no stand-alone supervision in the cab; so I was unable to use LUAW for my 28R departures. I had 3 aircraft to depart; all filed over EWC VOR; and needed to meet release times for TBM/APREQ airports. Arrival traffic was on about a 12 mile final when I switched the first aircraft to departure. Since I was unable to LUAW; I had to clear the next 2 aircraft from the parallel taxiway; facing the downwind direction. Basically; as soon as I switch aircraft #1 to departure; I was able to clear aircraft #2; and then do the same with aircraft #3. A G-IV had taxied out from a hangar located north of the departure end of Runway 28R. I was not in a position to allow him to cross Runway 28R until my arrival had landed. Total wait time about 4 or 5 minutes. The G-IV asked Ground Control for the phone number for the supervisor; and this was given to the crew. When the G-IV got to the approach end of the runway; I called them and asked if they were ready for departure. The reply was they would be ready in 'a minute'. When I got on break; I stopped in the TRACON to inform the Supervisor what had happened. The supervisor informed me that they had already spoken to someone in the G-IV. This might explain why they were not ready when they got to the runway. Please re-visit the no LUAW criteria. It does not enhance safety; it degrades safety by forcing controllers to clear traffic for departure from a non-standard location. It forces a controller to guess as to how fast an aircraft can make the turn to the runway; will he start take off roll immediately; and will he even start to move as soon as I expect him to. In this case; it delayed an aircraft from crossing a runway in order to adhere to a regulation that; I say again; does not enhance safety.

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