Narrative:

I was working ground control #1 during the arrival push and witnessed the following event take place involving local control #2 and ground control #2. Memphis was in a north confign; landing runway 36L and runway 36R; departing runway 36C. Ground control #2 taxied a hawker jet sbound on taxiway Y with the intention of crossing runway 36C at taxiway P and continuing south on taxiway south to the approach end of runway 36C. The purpose of this taxi route was to save the pilot some time. New amass was OTS and we did not have the staffing to open local control #3 so that runway 27 could be used; which would have ultimately saved the hawker jet even more taxi time. Ground control #2 had previously taxied an LJ35 to runway 36C via txwys Y; a; B; and south; to avoid traffic landing runway 36R that would taxi via taxiway Y. Local control #2 coordination with ground control #2 to have the traffic sbound on taxiway south 'give way' to a DC9 that had just landed on runway 36R and would exit the runway at S4 and then cross runway 36C at taxiway K. Ground control #2 provided 'give way' instructions to the wrong taxiing aircraft and the unaffected aircraft acknowledged the 'give way' instructions. The DC9 exiting runway 36R at S4 and the LJ35 at the intersection of taxiway south and S4 both came to a sudden halt; nose-to-nose; having proceeded with specific instructions from their respective controllers. At this point the ground control #2 controller (along with everyone else in the tower cabin attendant) realized what had happened. I believe that several factors contributed to his near collision: 1) the ground control #2 controller was working overtime today; and this was his 6TH consecutive day of work. 2) the ground control #2 controller had admitted to being very tired early in the day due to lack of sleep the night before. 4)the ground control #2 controller was reluctant to call in 'sick' due to the fact that 'lack of sleep is not an excuse for taking sick leave' (at least according to mem management). 5) at the time that local control #2 coordination with ground control #2 for the 'give way' instructions; ground control #2 had just started a position relief briefing and became distraction. 6) the ground control #2 controller's shift was due to end within the next 30 mins and he was ready to go home. I believe that the local control #2 controller could have helped the situation by not asking ground control #2 to 'give way' to his aircraft. The situation was so close; that the DC9 could have easily slowed his turn so as to pass behind the sbound traffic on taxiway south. The relieving controller had been watching the position for just a few moments; and it's possible that a more in depth review of the position might have allowed this controller to have assisted in stopping this error. The ground control #2 controller could have used a more traditional taxi route instead of trying to help the pilot to such a great degree.

Google
 

Original NASA ASRS Text

Title: MEM GND CTLR WITNESSED GND CONFLICT THAT REPORTEDLY OCCURRED BECAUSE CTL ISSUED INSTRUCTIONS TO THE WRONG ACFT.

Narrative: I WAS WORKING GND CTL #1 DURING THE ARR PUSH AND WITNESSED THE FOLLOWING EVENT TAKE PLACE INVOLVING LCL CTL #2 AND GND CTL #2. MEMPHIS WAS IN A N CONFIGN; LNDG RWY 36L AND RWY 36R; DEPARTING RWY 36C. GND CTL #2 TAXIED A HAWKER JET SBOUND ON TXWY Y WITH THE INTENTION OF XING RWY 36C AT TXWY P AND CONTINUING S ON TXWY S TO THE APCH END OF RWY 36C. THE PURPOSE OF THIS TAXI RTE WAS TO SAVE THE PLT SOME TIME. NEW AMASS WAS OTS AND WE DID NOT HAVE THE STAFFING TO OPEN LCL CTL #3 SO THAT RWY 27 COULD BE USED; WHICH WOULD HAVE ULTIMATELY SAVED THE HAWKER JET EVEN MORE TAXI TIME. GND CTL #2 HAD PREVIOUSLY TAXIED AN LJ35 TO RWY 36C VIA TXWYS Y; A; B; AND S; TO AVOID TFC LNDG RWY 36R THAT WOULD TAXI VIA TXWY Y. LCL CTL #2 COORD WITH GND CTL #2 TO HAVE THE TFC SBOUND ON TXWY S 'GIVE WAY' TO A DC9 THAT HAD JUST LANDED ON RWY 36R AND WOULD EXIT THE RWY AT S4 AND THEN CROSS RWY 36C AT TXWY K. GND CTL #2 PROVIDED 'GIVE WAY' INSTRUCTIONS TO THE WRONG TAXIING ACFT AND THE UNAFFECTED ACFT ACKNOWLEDGED THE 'GIVE WAY' INSTRUCTIONS. THE DC9 EXITING RWY 36R AT S4 AND THE LJ35 AT THE INTXN OF TXWY S AND S4 BOTH CAME TO A SUDDEN HALT; NOSE-TO-NOSE; HAVING PROCEEDED WITH SPECIFIC INSTRUCTIONS FROM THEIR RESPECTIVE CTLRS. AT THIS POINT THE GND CTL #2 CTLR (ALONG WITH EVERYONE ELSE IN THE TWR CAB) REALIZED WHAT HAD HAPPENED. I BELIEVE THAT SEVERAL FACTORS CONTRIBUTED TO HIS NEAR COLLISION: 1) THE GND CTL #2 CTLR WAS WORKING OVERTIME TODAY; AND THIS WAS HIS 6TH CONSECUTIVE DAY OF WORK. 2) THE GND CTL #2 CTLR HAD ADMITTED TO BEING VERY TIRED EARLY IN THE DAY DUE TO LACK OF SLEEP THE NIGHT BEFORE. 4)THE GND CTL #2 CTLR WAS RELUCTANT TO CALL IN 'SICK' DUE TO THE FACT THAT 'LACK OF SLEEP IS NOT AN EXCUSE FOR TAKING SICK LEAVE' (AT LEAST ACCORDING TO MEM MGMNT). 5) AT THE TIME THAT LCL CTL #2 COORD WITH GND CTL #2 FOR THE 'GIVE WAY' INSTRUCTIONS; GND CTL #2 HAD JUST STARTED A POS RELIEF BRIEFING AND BECAME DISTR. 6) THE GND CTL #2 CTLR'S SHIFT WAS DUE TO END WITHIN THE NEXT 30 MINS AND HE WAS READY TO GO HOME. I BELIEVE THAT THE LCL CTL #2 CTLR COULD HAVE HELPED THE SITUATION BY NOT ASKING GND CTL #2 TO 'GIVE WAY' TO HIS ACFT. THE SITUATION WAS SO CLOSE; THAT THE DC9 COULD HAVE EASILY SLOWED HIS TURN SO AS TO PASS BEHIND THE SBOUND TFC ON TXWY S. THE RELIEVING CTLR HAD BEEN WATCHING THE POS FOR JUST A FEW MOMENTS; AND IT'S POSSIBLE THAT A MORE IN DEPTH REVIEW OF THE POS MIGHT HAVE ALLOWED THIS CTLR TO HAVE ASSISTED IN STOPPING THIS ERROR. THE GND CTL #2 CTLR COULD HAVE USED A MORE TRADITIONAL TAXI RTE INSTEAD OF TRYING TO HELP THE PLT TO SUCH A GREAT DEGREE.

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