37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1040958 |
Time | |
Date | 201210 |
Local Time Of Day | 0001-0600 |
Place | |
Locale Reference | PCT.TRACON |
State Reference | VA |
Aircraft 1 | |
Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
Flight Phase | Descent |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Saab 340 Undifferentiated |
Operating Under FAR Part | Part 121 |
Flight Phase | Cruise |
Route In Use | Vectors |
Flight Plan | IFR |
Person 1 | |
Function | Approach Departure |
Qualification | Air Traffic Control Fully Certified |
Events | |
Anomaly | ATC Issue All Types |
Narrative:
The operations manager (OM) came over with a list of outages and told the controller in charge (controller in charge) that this stuff was out on the hour. The controller in charge replied you mean now; the OM said yes and walked off. That list of outages included 1 frequency that we were using in the area; all guard frequencies for the area; all standby frequencies and multiple landlines. Minutes later the luray controller feeding me aircraft on the frdmm and trupps descending via lost communications with all aircraft; this was the frequency that was listed on the outages. As the word started getting around that luray lost frequency's it was also discovered that the shd area also lost 3 frequency's with no notice. The whole TRACON turned into chaos and people scrambled to get in contact with aircraft. Aircraft #1 was descending via to 060 while aircraft #2 was lost in the shd area eastbound at 060. Aircraft #2 was pointed out to me but I told them that all my aircraft from the west were descending to 060 and we had lost communications with them. I made multiple calls on guard but I don't think they were heard due to guard being released to maintenance. Aircraft #1 finally checked in with me saying he was at 080 and staying there until he figured out what was going on. I think he saw aircraft #2 on TCAS at 060 and took it on himself to stay separated because the 'descend via' would have put him at 060 and a near midair with aircraft #2. This is just one of many events that need to be looked at between the shd and mtv areas at pct. It was sheer luck that we didn't have many errors and I believe that aircraft used TCAS while descending via on multiple arrivals to separate themselves. First; the breakdown started with the OM that released 2 pages of things including busy frequencies; guard; and landlines with no thought or advanced notice on the operation. This should have been done on a late night shift. Secondly; the 'descend via' to 060 on the trupps/frdmm into dca on runway 19 needs to stop. The mtv area as a whole had complained since it was being developed last year that this was unsafe and would result in an error. Our concerns were ignored; the procedures were published and we have problems everyday on these 2 stars. These stars need to stay at 080 of we are going to have a major deal just northwest of dca. This entire operation at pct needs to be looked at. It was ugly; I've been doing ATC for a long time and this made me very unsettled.
Original NASA ASRS Text
Title: PCT Controller described an unsafe chaotic situation when multiple frequencies were released by a supervisor to Maintenance with very little warning and/or planning with regard to impact.
Narrative: The Operations Manager (OM) came over with a list of outages and told the Controller In Charge (CIC) that this stuff was out on the hour. The CIC replied you mean now; the OM said yes and walked off. That list of outages included 1 frequency that we were using in the area; all guard frequencies for the area; all standby frequencies and multiple landlines. Minutes later the Luray Controller feeding me aircraft on the FRDMM and TRUPPS descending via lost communications with all aircraft; this was the frequency that was listed on the outages. As the word started getting around that Luray lost frequency's it was also discovered that the SHD area also lost 3 frequency's with no notice. The whole TRACON turned into chaos and people scrambled to get in contact with aircraft. Aircraft #1 was descending via to 060 while Aircraft #2 was lost in the SHD area eastbound at 060. Aircraft #2 was pointed out to me but I told them that all my aircraft from the west were descending to 060 and we had lost communications with them. I made multiple calls on Guard but I don't think they were heard due to Guard being released to maintenance. Aircraft #1 finally checked in with me saying he was at 080 and staying there until he figured out what was going on. I think he saw Aircraft #2 on TCAS at 060 and took it on himself to stay separated because the 'descend via' would have put him at 060 and a near midair with Aircraft #2. This is just one of many events that need to be looked at between the SHD and MTV areas at PCT. It was sheer luck that we didn't have many errors and I believe that aircraft used TCAS while descending via on multiple arrivals to separate themselves. First; the breakdown started with the OM that released 2 pages of things including busy frequencies; guard; and landlines with no thought or advanced notice on the operation. This should have been done on a late night shift. Secondly; the 'descend via' to 060 on the TRUPPS/FRDMM into DCA on Runway 19 needs to stop. The MTV area as a whole had complained since it was being developed last year that this was unsafe and would result in an error. Our concerns were ignored; the procedures were published and we have problems everyday on these 2 STARS. These STARS need to stay at 080 of we are going to have a major deal just northwest of DCA. This entire operation at PCT needs to be looked at. It was ugly; I've been doing ATC for a long time and this made me very unsettled.
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.