 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Approach controller voiced concern regarding an observed likely loss of separation event with two controllers each working one of the involved aircraft. Reporter noted neither controller involved issued traffic; and one was involved in another separation event a short time later.
| Attributes | |
| ACN | 955523 |
| Time | |
| Date | 201106 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | ZZZ.TRACON |
| State Reference | US |
| Aircraft 1 | |
| Make Model Name | Regional Jet 200 ER/LR (CRJ200) |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Descent |
| Route In Use | Vectors |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | Skyhawk 172/Cutlass 172 |
| Flight Phase | Descent |
| Route In Use | Vectors |
| Flight Plan | IFR |
| Person 1 | |
| Function | Approach |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy |
Narrative:
An IFR C172 landing a satellite airport was being worked by radar east on a northbound track for the airport descending from 60 with an automated point out to [the main airport's] final radar; who was working an IFR CRJ2 from the northeast landing on runway xx. The CRJ2 had been handed off and shipped from the radar east controller. Upon checking in with the final controller; the CRJ2 was given direct to the next fix and descended to 2;500; which put the aircraft in conflict with the C172. I believe loss of separation occurred and neither aircraft received a traffic call from their respective controllers. Recommendation; if finals are going to take point outs on aircraft landing at the satellite airport which is just inside the eastern boundary of their airspace; there is no excuse to get any and all the main airport's arrival traffic established on the final approach course for runway's xxl/right. Both final approach courses are clear of the satellite airport. The concept of pointing two aircraft at each other and descending them to similar altitudes is beyond my comprehension when you are not talking to both aircraft and there are so many other safe options. I am also told that the same final radar controller almost ran an IFR arrival aircraft into a VFR aircraft just 10 minutes later. Will somebody please do something.
Original NASA ASRS Text
Title: Approach Controller voiced concern regarding an observed likely loss of separation event with two controllers each working one of the involved aircraft. Reporter noted neither controller involved issued traffic; and one was involved in another separation event a short time later.
Narrative: An IFR C172 landing a satellite airport was being worked by Radar East on a northbound track for the airport descending from 60 with an automated point out to [the main airport's] Final RADAR; who was working an IFR CRJ2 from the northeast landing on Runway XX. The CRJ2 had been handed off and shipped from the RADAR East Controller. Upon checking in with the Final Controller; the CRJ2 was given direct to the next fix and descended to 2;500; which put the aircraft in conflict with the C172. I believe loss of separation occurred and neither aircraft received a traffic call from their respective controllers. Recommendation; if Finals are going to take point outs on aircraft landing at the satellite airport which is just inside the eastern boundary of their airspace; there is no excuse to get any and all the main airport's arrival traffic established on the final approach course for Runway's XXL/R. Both final approach courses are clear of the satellite airport. The concept of pointing two aircraft at each other and descending them to similar altitudes is beyond my comprehension when you are not talking to both aircraft and there are so many other safe options. I am also told that the same Final RADAR Controller almost ran an IFR arrival aircraft into a VFR aircraft just 10 minutes later. Will somebody please do something.
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.