Narrative:

Washington tower/TRACON is preparing to move into an entire new facility. Consequently, many equipment problems are not being rectified in a timely, efficient manner. Basically, controllers feel that management/maintenance has the attitude of 'screw it we're moving soon anyway.' the FAA is way behind here in just trying to keep up with what they have now. Lack of maintenance personnel and motivation seems to be the focus of the problem. For a long time (in excess of 2 yrs) we have had particular problems with 2 frequencys on the departure side of the room. They are 126.55 and 125.65. On mar/fri/97, FAA form 1800-1 (ucr) was filed with headquarters FAA regarding known and documented interference problems with frequency 125.65. This reporter filed that report. The end result was the frequency was taken OTS awaiting flight check. For the time being the status remains the same. As an alternative 126.55 was being utilized. This frequency has been problematic over the past few yrs as well. It's assigned to a high sector yet seldom got utilized. The problem is one of reception. In the northeast quadrant of the airspace controllers cannot hear readbacks to control instructions. Normally, after a few retries to the pilot we got the readback. Pilots aren't too happy because they have to repeat themselves or run through a series of wasted motions trying to see if the aircraft had a transmit problem. Valid arguments all. This is a busy sector in the washington metropolitan area so one can imagine the frustration and possible safety consequences it can cause. On mar/mon/97, at approximately XA50 pm EST a situation arose that I attribute directly to problems with the frequencys. The scenario involved a B727 IFR to lga and a VFR B737 being worked by an adjacent facility (baltimore approach). The incident happened 5-10 NM southwest of the balance VOR. My workload was moderate. The B727 was eastbound from dca headed to eno via its 271 degree radial. I started having reception problems on frequency 126.55 and reported it to the supervisors on duty. One of them set me up on a spare frequency. I had to change each aircraft to the new frequency, and the only way I felt was safe to assure they heard me was to have each individual aircraft acknowledge the change by identing. It took a lot of time to do so. I had a supervisor sitting right beside me as an extra set of eyes and to assist me as needed. I'm sure glad he was there. The supervisor was sitting 2 ft from me and very calmly pointed to my scope. He pointed out an aircraft whose mode C reflected 14500 ft headed north to south across the path of the eastbound B727. As is usually the case, the B727 was climbing through 14000 ft when I issued a turn and traffic. The B727 reported it was responding to a TCASII resolution and I didn't bother him for a moment. The traffic was called as type unknown and altitude unverified. The jet told me it was a B737 and 14500 ft was right. At the time of this incident I had maybe 2 other airplanes, having 'dumped off' all I could. There are lots of causal factors here. I have 20 yrs air traffic experience in radar, 16 of them are right here in dca. The B737 was above class B airspace operating VFR. Maybe the adjacent facility was trying to point out the B737 to me, I'd had too much else to do at the time anyway so probably didn't hear them if they were. I was in my own airspace at the time. I damn near switched the air carrier to the center but hadn't made the handoff yet. If it weren't for that supervisor's 'extra set of eyes' I'd never have seen the other airplane. We asked the pilot to call us when he got to lga. He did. He wasn't angry. He said he was surprised and startled by the event but understood the situation. The only thing he said that sets me aback is that he wanted the traffic call to have been made sooner.

Google
 

Original NASA ASRS Text

Title: RPTR SIT OF A PROB WITH 2 DC FREQS. RPTR CLAIMS A UCR HAS BEEN FILED ON 1 FREQ. FREQ WAS TAKEN OTS FOR FLT CHK. ON A SUBSEQUENT OCCASION, RECEPTION PROBS WERE ENCOUNTERED ON THE OTHER FREQ, TFC WAS SWITCHED TO AN ADJOINING SECTOR BY HAVING THE PLTS IDENT AS ACKNOWLEDGEMENT. RPTR ALLEGES EQUIP PROBS ARE NOT BEING RECTIFIED IN A TIMELY AND EFFICIENT MANNER DUE PLANNED FACILITY MOVE TO A NEW LOCATION.

Narrative: WASHINGTON TWR/TRACON IS PREPARING TO MOVE INTO AN ENTIRE NEW FACILITY. CONSEQUENTLY, MANY EQUIP PROBS ARE NOT BEING RECTIFIED IN A TIMELY, EFFICIENT MANNER. BASICALLY, CTLRS FEEL THAT MGMNT/MAINT HAS THE ATTITUDE OF 'SCREW IT WE'RE MOVING SOON ANYWAY.' THE FAA IS WAY BEHIND HERE IN JUST TRYING TO KEEP UP WITH WHAT THEY HAVE NOW. LACK OF MAINT PERSONNEL AND MOTIVATION SEEMS TO BE THE FOCUS OF THE PROB. FOR A LONG TIME (IN EXCESS OF 2 YRS) WE HAVE HAD PARTICULAR PROBS WITH 2 FREQS ON THE DEP SIDE OF THE ROOM. THEY ARE 126.55 AND 125.65. ON MAR/FRI/97, FAA FORM 1800-1 (UCR) WAS FILED WITH HEADQUARTERS FAA REGARDING KNOWN AND DOCUMENTED INTERFERENCE PROBS WITH FREQ 125.65. THIS RPTR FILED THAT RPT. THE END RESULT WAS THE FREQ WAS TAKEN OTS AWAITING FLT CHK. FOR THE TIME BEING THE STATUS REMAINS THE SAME. AS AN ALTERNATIVE 126.55 WAS BEING UTILIZED. THIS FREQ HAS BEEN PROBLEMATIC OVER THE PAST FEW YRS AS WELL. IT'S ASSIGNED TO A HIGH SECTOR YET SELDOM GOT UTILIZED. THE PROB IS ONE OF RECEPTION. IN THE NE QUADRANT OF THE AIRSPACE CTLRS CANNOT HEAR READBACKS TO CTL INSTRUCTIONS. NORMALLY, AFTER A FEW RETRIES TO THE PLT WE GOT THE READBACK. PLTS AREN'T TOO HAPPY BECAUSE THEY HAVE TO REPEAT THEMSELVES OR RUN THROUGH A SERIES OF WASTED MOTIONS TRYING TO SEE IF THE ACFT HAD A XMIT PROB. VALID ARGUMENTS ALL. THIS IS A BUSY SECTOR IN THE WASHINGTON METROPOLITAN AREA SO ONE CAN IMAGINE THE FRUSTRATION AND POSSIBLE SAFETY CONSEQUENCES IT CAN CAUSE. ON MAR/MON/97, AT APPROX XA50 PM EST A SIT AROSE THAT I ATTRIBUTE DIRECTLY TO PROBS WITH THE FREQS. THE SCENARIO INVOLVED A B727 IFR TO LGA AND A VFR B737 BEING WORKED BY AN ADJACENT FACILITY (BALTIMORE APCH). THE INCIDENT HAPPENED 5-10 NM SW OF THE BAL VOR. MY WORKLOAD WAS MODERATE. THE B727 WAS EBOUND FROM DCA HEADED TO ENO VIA ITS 271 DEG RADIAL. I STARTED HAVING RECEPTION PROBS ON FREQ 126.55 AND RPTED IT TO THE SUPVRS ON DUTY. ONE OF THEM SET ME UP ON A SPARE FREQ. I HAD TO CHANGE EACH ACFT TO THE NEW FREQ, AND THE ONLY WAY I FELT WAS SAFE TO ASSURE THEY HEARD ME WAS TO HAVE EACH INDIVIDUAL ACFT ACKNOWLEDGE THE CHANGE BY IDENTING. IT TOOK A LOT OF TIME TO DO SO. I HAD A SUPVR SITTING RIGHT BESIDE ME AS AN EXTRA SET OF EYES AND TO ASSIST ME AS NEEDED. I'M SURE GLAD HE WAS THERE. THE SUPVR WAS SITTING 2 FT FROM ME AND VERY CALMLY POINTED TO MY SCOPE. HE POINTED OUT AN ACFT WHOSE MODE C REFLECTED 14500 FT HEADED N TO S ACROSS THE PATH OF THE EBOUND B727. AS IS USUALLY THE CASE, THE B727 WAS CLBING THROUGH 14000 FT WHEN I ISSUED A TURN AND TFC. THE B727 RPTED IT WAS RESPONDING TO A TCASII RESOLUTION AND I DIDN'T BOTHER HIM FOR A MOMENT. THE TFC WAS CALLED AS TYPE UNKNOWN AND ALT UNVERIFIED. THE JET TOLD ME IT WAS A B737 AND 14500 FT WAS RIGHT. AT THE TIME OF THIS INCIDENT I HAD MAYBE 2 OTHER AIRPLANES, HAVING 'DUMPED OFF' ALL I COULD. THERE ARE LOTS OF CAUSAL FACTORS HERE. I HAVE 20 YRS AIR TFC EXPERIENCE IN RADAR, 16 OF THEM ARE RIGHT HERE IN DCA. THE B737 WAS ABOVE CLASS B AIRSPACE OPERATING VFR. MAYBE THE ADJACENT FACILITY WAS TRYING TO POINT OUT THE B737 TO ME, I'D HAD TOO MUCH ELSE TO DO AT THE TIME ANYWAY SO PROBABLY DIDN'T HEAR THEM IF THEY WERE. I WAS IN MY OWN AIRSPACE AT THE TIME. I DAMN NEAR SWITCHED THE ACR TO THE CTR BUT HADN'T MADE THE HDOF YET. IF IT WEREN'T FOR THAT SUPVR'S 'EXTRA SET OF EYES' I'D NEVER HAVE SEEN THE OTHER AIRPLANE. WE ASKED THE PLT TO CALL US WHEN HE GOT TO LGA. HE DID. HE WASN'T ANGRY. HE SAID HE WAS SURPRISED AND STARTLED BY THE EVENT BUT UNDERSTOOD THE SIT. THE ONLY THING HE SAID THAT SETS ME ABACK IS THAT HE WANTED THE TFC CALL TO HAVE BEEN MADE SOONER.

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