Narrative:

I was working local control 1 and 2 (LC1/LC2) combined. Memphis was landing runways 36L/36C/36R and runway 27. I was responsible for all runway 36 arrs. Another controller was staffed at local control 3 for all runway 27 arrs. Ground control 1 and 2 were combined as usual; and this single ground controller is responsible for all aircraft that have landed on runways 36L/36C/36R. Each aircraft that lands on runways 36L/36C/36R in this confign; must then cross runway 27; which is an active arrival and departure runway. There are 6 intersecting txwys that cross runway 27; and our asde/amass equipment does not provide adequate coverage for these areas. The asde/amass display is located between local control 1 and ground control 1. As each runway 36L arrival landed and then taxied northbound on txwys M and north; each associated asde/amass data tag would drop off of the asde/amass display as the aircraft passed the ramp just south of taxiway a; and south of the departure end of runway 27. During one 15 min period; I observed several aircraft land on runway 36L; taxi north on txwys M and north; and each associated asde/amass data tag dropped off of the display. Using runway 27 during this type of operation is difficult enough as it is. Not having the ability to use asde/amass on runway 27 makes for a less safe operation. This equipment is not certified for use on runway 27; but it should be. This is where the vast majority of our runway xings take place; and it happens each and every night on the inbound and outbound operation. The FAA needs to install adequate equipment to ensure the safe operation of all runway xings during all times of the day/night; and under all WX conditions.

Google
 

Original NASA ASRS Text

Title: MEM TWR CTLR DESCRIBED SEVERAL INSTANCES OF ASDE AND AMASS DATA BLOCK LOSSES; SUGGESTING ASDE AND AMASS SHOULD BE AVAILABLE FOR RWY 27 OPS.

Narrative: I WAS WORKING LCL CTL 1 AND 2 (LC1/LC2) COMBINED. MEMPHIS WAS LNDG RWYS 36L/36C/36R AND RWY 27. I WAS RESPONSIBLE FOR ALL RWY 36 ARRS. ANOTHER CTLR WAS STAFFED AT LCL CTL 3 FOR ALL RWY 27 ARRS. GND CTL 1 AND 2 WERE COMBINED AS USUAL; AND THIS SINGLE GND CTLR IS RESPONSIBLE FOR ALL ACFT THAT HAVE LANDED ON RWYS 36L/36C/36R. EACH ACFT THAT LANDS ON RWYS 36L/36C/36R IN THIS CONFIGN; MUST THEN CROSS RWY 27; WHICH IS AN ACTIVE ARR AND DEP RWY. THERE ARE 6 INTERSECTING TXWYS THAT CROSS RWY 27; AND OUR ASDE/AMASS EQUIP DOES NOT PROVIDE ADEQUATE COVERAGE FOR THESE AREAS. THE ASDE/AMASS DISPLAY IS LOCATED BTWN LCL CTL 1 AND GND CTL 1. AS EACH RWY 36L ARR LANDED AND THEN TAXIED NBOUND ON TXWYS M AND N; EACH ASSOCIATED ASDE/AMASS DATA TAG WOULD DROP OFF OF THE ASDE/AMASS DISPLAY AS THE ACFT PASSED THE RAMP JUST S OF TXWY A; AND S OF THE DEP END OF RWY 27. DURING ONE 15 MIN PERIOD; I OBSERVED SEVERAL ACFT LAND ON RWY 36L; TAXI N ON TXWYS M AND N; AND EACH ASSOCIATED ASDE/AMASS DATA TAG DROPPED OFF OF THE DISPLAY. USING RWY 27 DURING THIS TYPE OF OP IS DIFFICULT ENOUGH AS IT IS. NOT HAVING THE ABILITY TO USE ASDE/AMASS ON RWY 27 MAKES FOR A LESS SAFE OP. THIS EQUIP IS NOT CERTIFIED FOR USE ON RWY 27; BUT IT SHOULD BE. THIS IS WHERE THE VAST MAJORITY OF OUR RWY XINGS TAKE PLACE; AND IT HAPPENS EACH AND EVERY NIGHT ON THE INBOUND AND OUTBOUND OP. THE FAA NEEDS TO INSTALL ADEQUATE EQUIP TO ENSURE THE SAFE OP OF ALL RWY XINGS DURING ALL TIMES OF THE DAY/NIGHT; AND UNDER ALL WX CONDITIONS.

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.