 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
TRACON developmental described a loss of separation event when communications between the reporter and another developmental in the tower cab fail to address the impending situation.
| Attributes | |
| ACN | 1108449 |
| Time | |
| Date | 201308 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | ZZZ.TRACON |
| State Reference | US |
| Aircraft 1 | |
| Make Model Name | Hawker Horizon (Raytheon) |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Descent |
| Route In Use | Vectors |
| Flight Plan | IFR |
| Person 1 | |
| Function | Approach Departure |
| Qualification | Air Traffic Control Developmental |
| Person 2 | |
| Function | Local |
| Qualification | Air Traffic Control Developmental |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy |
Narrative:
A B350 called me on a 090 heading. He hadn't tagged up yet but I had a primary target; so I radar identification'd him and asked his altitude. He responded he was out of 026. I didn't hear final descend a hawker (apparently tower approved a point-out) out of 050 on the downwind. When the tag on the B350 came up (the mode C altitude had not displayed yet) final came over to me and asked if he was stopped at 030. I said no. He said he stopped the hawker at 040. I told the B350 to maintain 030 for traffic. At that moment his mode C displayed and he was already at 036 (maybe even 038; I do not readily recall). I told him to turn to heading 360 immediately. At the same time; final turned the hawker to a 180 heading. The B350 had already started descending and complied with the turn de-conflicting the two aircraft. Tower should have advised final of the traffic that was still in their departure release area prior to approving a lower altitude for the hawker.
Original NASA ASRS Text
Title: TRACON developmental described a loss of separation event when communications between the reporter and another developmental in the tower cab fail to address the impending situation.
Narrative: A B350 called me on a 090 heading. He hadn't tagged up yet but I had a primary target; so I RADAR ID'd him and asked his altitude. He responded he was out of 026. I didn't hear final descend a Hawker (apparently Tower approved a point-out) out of 050 on the downwind. When the tag on the B350 came up (the Mode C altitude had not displayed yet) final came over to me and asked if he was stopped at 030. I said no. He said he stopped the Hawker at 040. I told the B350 to maintain 030 for traffic. At that moment his Mode C displayed and he was already at 036 (maybe even 038; I do not readily recall). I told him to turn to heading 360 immediately. At the same time; final turned the Hawker to a 180 heading. The B350 had already started descending and complied with the turn de-conflicting the two aircraft. Tower should have advised final of the traffic that was still in their departure release area prior to approving a lower altitude for the Hawker.
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.