 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Atlanta center controller reported a loss of separation due to the automation not allowing 3 mile separation between the two aircraft.
| Attributes | |
| ACN | 1597659 |
| Time | |
| Date | 201811 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | ZTL.ARTCC |
| State Reference | GA |
| Aircraft 1 | |
| Make Model Name | Super King Air 300 |
| Flight Phase | Cruise |
| Route In Use | Vectors |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Cruise |
| Route In Use | Vectors |
| Flight Plan | IFR |
| Person 1 | |
| Function | Enroute |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 11 |
| Events | |
| Anomaly | ATC Issue All Types Airspace Violation All Types Conflict Airborne Conflict Deviation - Procedural Clearance |
Narrative:
Training was in progress on R29/R30. The clt 3 mile airspace was unavailable. An arrival and departure push was in progress at the sectors and aircraft Y aircraft at 140 was vectored to parallel the inbounds on the descent via clearance into clt. Aircraft X was an overflight at 140 northwest bound. Aircraft X was vectored to a 360 heading to miss aircraft Y within what should have been a usable 3 mile airspace 30 miles from the gso radar. The 2 aircraft went into conflict alert with approximately 4.8 miles aircraft X was then descended to 130. I'm not sure why the equipment decided that the these 2 aircraft were not within the gso designated 3 mile airspace when they were within 40 miles of the antenna; and that was a deciding factor on the vector used and the 'loss' of separation. At the same time this was going on; aircraft Y was flashing at clt approach; but at in incorrect sector as decided by the automation. We attempted to call clt with a handoff; and they eventually called radar; but the aircraft had already penetrated the airspace.1. Fix the automation so that aircraft flash at the appropriate sector within approach control airspace.2. Have the correct radar site in use for the 3 mile airspace when an adjacent 3 mile airspace is unusable.
Original NASA ASRS Text
Title: Atlanta Center Controller reported a loss of separation due to the automation not allowing 3 mile separation between the two aircraft.
Narrative: Training was in progress on R29/R30. The CLT 3 mile airspace was unavailable. An arrival and departure push was in progress at the sectors and Aircraft Y aircraft at 140 was vectored to parallel the inbounds on the descent via clearance into CLT. Aircraft X was an overflight at 140 northwest bound. Aircraft X was vectored to a 360 heading to miss Aircraft Y within what should have been a usable 3 mile airspace 30 miles from the GSO radar. The 2 aircraft went into conflict alert with approximately 4.8 miles Aircraft X was then descended to 130. I'm not sure why the equipment decided that the these 2 aircraft were not within the GSO designated 3 mile airspace when they were within 40 miles of the antenna; and that was a deciding factor on the vector used and the 'loss' of separation. At the same time this was going on; Aircraft Y was flashing at CLT Approach; but at in incorrect sector as decided by the automation. We attempted to call CLT with a handoff; and they eventually called Radar; but the aircraft had already penetrated the airspace.1. Fix the automation so that aircraft flash at the appropriate sector within approach control airspace.2. Have the correct radar site in use for the 3 mile airspace when an adjacent 3 mile airspace is unusable.
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.