 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZDC controller described a conflict event noting problematic radio coverage as a contributing factor.
| Attributes | |
| ACN | 1148210 |
| Time | |
| Date | 201402 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | ZDC.ARTCC |
| State Reference | VA |
| Aircraft 1 | |
| Make Model Name | PA-46 Malibu Meridian |
| Flight Phase | Cruise |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | Regional Jet 200 ER/LR (CRJ200) |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Climb |
| Route In Use | Vectors |
| Flight Plan | IFR |
| Person 1 | |
| Function | Enroute |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy |
Narrative:
While working the r-side at sector 38 during a busy and complex session; I placed a crj westbound on J209 on a vector H220 initially to avoid multiple FL270 traffic (including a meridian; eastbound on J209); so I could climb the aircraft. While making several other moves to get the traffic flow in order; I slant zeroed an aircraft on top of the meridian and could no longer see the data block; and missed him as I went back to re-evaluate the crj. As I adjusted the heading to H235 and issued the climb to the crj to FL280 the conflict alert went off and I had realized my mistake; however; I measured and seen that I had 5.1 miles between these two and increasing. This was a busy session; with multiple aircraft on vectors; and also a lot of readbacks due to the documented fact that tyi's main frequency in and around tyi VORTAC has been unreadable to pilots; which causes a lot of confusion and causes more workload for controllers; which was a problem during this session as I finally had to switch to buec's to obtain a manageable frequency. Fix tar river's 132.22 frequency to help reduce controller workload and missed readbacks.
Original NASA ASRS Text
Title: ZDC Controller described a conflict event noting problematic radio coverage as a contributing factor.
Narrative: While working the R-Side at Sector 38 during a busy and complex session; I placed a CRJ westbound on J209 on a vector H220 initially to avoid multiple FL270 traffic (including a Meridian; eastbound on J209); so I could climb the aircraft. While making several other moves to get the traffic flow in order; I slant zeroed an aircraft on top of the Meridian and could no longer see the data block; and missed him as I went back to re-evaluate the CRJ. As I adjusted the heading to H235 and issued the climb to the CRJ to FL280 the conflict alert went off and I had realized my mistake; however; I measured and seen that I had 5.1 miles between these two and increasing. This was a busy session; with multiple aircraft on vectors; and also a lot of readbacks due to the documented fact that TYI's Main frequency in and around TYI VORTAC has been unreadable to pilots; which causes a lot of confusion and causes more workload for controllers; which was a problem during this session as I finally had to switch to BUEC's to obtain a manageable frequency. Fix Tar River's 132.22 frequency to help reduce controller workload and missed readbacks.
Data retrieved from NASA's ASRS site 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.