37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 941188 |
Time | |
Date | 201104 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | PCT.TRACON |
State Reference | VA |
Aircraft 1 | |
Make Model Name | B737 Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | Descent |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | P180 Avanti |
Operating Under FAR Part | Part 91 |
Flight Phase | Cruise |
Flight Plan | IFR |
Person 1 | |
Function | Approach Departure |
Qualification | Air Traffic Control Fully Certified |
Events | |
Anomaly | ATC Issue All Types Airspace Violation All Types Deviation - Procedural Published Material / Policy |
Narrative:
This event happened while working the buffr sector at pct. I had just taken responsibility for the position when ZDC sector 15 called to apreq a P180 at 13;000 ft on the EMI5 arrival for bwi. Normally; props on this arrival hand off to mullr sector at 9;000. I approved the request; and subsequently got very busy with numerous departures off iad and dca; as well as arrivals to bwi. A B737 checked on at 15;000 ft over bubbi on the EMI5 arrival. I acknowledged the B737 and issued him a descent to 13;000. Soon after; mullr sector called on the override and asked if I was talking to the P180. I said I was not but he is supposed to be on my frequency. I then noticed a limited data block directly underneath the B737 and saw that it was the P180 level at 13;000 on mullr's tag. I immediately stopped the B737's descent at 14;000 and issued a turn to the left to diverge from the P180. The P180 then checked on and I immediately issued a turn to the right. Recommendation; this event happened during very busy traffic. I did not notice the limited data block of the P180 as it was covered up by the tag on the B737. Had it not been for mullr's intervention; the B737 would have descended into the P180. Also; it is not unusual that mullr would have taken the hand off on the P180; as they normally work the prop arrivals to bwi and would have no way of knowing that ZDC 15 had coordinated this arrival at 13;000 through my airspace. There are many occurrences of ZDC 15 flashing a hand off of a prop on the EMI5 arrival to buffr when it is supposed to flash to mullr and sometimes vice versa; although it is uncommon that buffr will accept a prop arrival through their airspace. This automation problem never happens with the jets; only props. I am not familiar with ZDC's setup; but on our ARTS at pct; it is possible to see what sector we are flashing to when handing off to an outside facility. This seems to be a systemic problem. This was a very unsafe situation that could have resulted in a very ugly operational error. This problem needs to be fixed as soon as possible!
Original NASA ASRS Text
Title: PCT Controller described a near loss of separation event when initially approving a non-standard routing/altitude entry from an adjacent facility and then failing to observe the wrong position automated hand off.
Narrative: This event happened while working the BUFFR Sector at PCT. I had just taken responsibility for the position when ZDC Sector 15 called to APREQ a P180 at 13;000 FT on the EMI5 arrival for BWI. Normally; props on this arrival hand off to MULLR Sector at 9;000. I approved the request; and subsequently got very busy with numerous departures off IAD and DCA; as well as arrivals to BWI. A B737 checked on at 15;000 FT over BUBBI on the EMI5 arrival. I acknowledged the B737 and issued him a descent to 13;000. Soon after; MULLR Sector called on the override and asked if I was talking to the P180. I said I was not but he is supposed to be on my frequency. I then noticed a limited data block directly underneath the B737 and saw that it was the P180 level at 13;000 on MULLR's tag. I immediately stopped the B737's descent at 14;000 and issued a turn to the left to diverge from the P180. The P180 then checked on and I immediately issued a turn to the right. Recommendation; this event happened during very busy traffic. I did not notice the limited data block of the P180 as it was covered up by the tag on the B737. Had it not been for MULLR's intervention; the B737 would have descended into the P180. Also; it is not unusual that MULLR would have taken the hand off on the P180; as they normally work the prop arrivals to BWI and would have no way of knowing that ZDC 15 had coordinated this arrival at 13;000 through my airspace. There are many occurrences of ZDC 15 flashing a hand off of a prop on the EMI5 arrival to BUFFR when it is supposed to flash to MULLR and sometimes vice versa; although it is uncommon that BUFFR will accept a prop arrival through their airspace. This automation problem never happens with the jets; only props. I am not familiar with ZDC's setup; but on our ARTS at PCT; it is possible to see what sector we are flashing to when handing off to an outside facility. This seems to be a systemic problem. This was a very unsafe situation that could have resulted in a very ugly operational error. This problem needs to be fixed ASAP!
Data retrieved from NASA's ASRS site as of April 2012 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.