37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1220586 |
Time | |
Date | 201411 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | ZAB.ARTCC |
State Reference | NM |
Environment | |
Light | Night |
Aircraft 1 | |
Make Model Name | Light Transport Low Wing 2 Turbojet Eng |
Flight Phase | Descent |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Medium Transport Low Wing 2 Turbojet Eng |
Flight Phase | Descent |
Flight Plan | IFR |
Person 1 | |
Function | Enroute |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 20 |
Events | |
Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Clearance |
Narrative:
Aircraft X landing sdl. Aircraft Y landing iwa. I coordinated a stack (sdl lander at 11000 and the iwa lander at 12000). LOA calls for both aircraft to be at 12000 and issued descent to aircraft 1 to 14000. This aircraft had to level at 14000 due to the proximity of naa airspace (13000 and below). I issued the iwa inbound a descent to 15000. When sdl inbound was clear of naa; I issued 'descend and maintain 11000'. When I observed the bottom aircraft descending out of 12800; I issued a descent to the iwa inbound to 13000. I then went back and told the sdl inbound (the bottom aircraft) to cross shock at and maintain 11000 and 250knots. When I observed the bottom aircraft descending out of 11800; I issued 'cross shock at and maintain 12000 and 250knots;' to top aircraft. At shock intersection; I observed the top aircraft at 12800 descending to 12000 and the bottom aircraft at 11300. I asked the bottom aircraft to say altitude and he replied 11300. I told him to increase his descent and he replied 'traffic insight.' I used the rule of observing an aircraft leaving an altitude before issuing the altitude to another aircraft; but I am second-guessing my application of the rule because I went back and issued crossing restriction after I issued the descent.my recommendation would be to educate the workforce on when they can and cannot use the rule 'observed leaving an altitude.'
Original NASA ASRS Text
Title: ZAB Controller uses altitude leaving rule and has a loss of separation.
Narrative: Aircraft X landing SDL. Aircraft Y landing IWA. I coordinated a stack (SDL lander at 11000 and the IWA lander at 12000). LOA calls for both aircraft to be at 12000 and issued descent to aircraft 1 to 14000. This aircraft had to level at 14000 due to the proximity of NAA airspace (13000 and below). I issued the IWA inbound a descent to 15000. When SDL inbound was clear of NAA; I issued 'descend and maintain 11000'. When I observed the bottom aircraft descending out of 12800; I issued a descent to the IWA inbound to 13000. I then went back and told the SDL inbound (the bottom aircraft) to cross SHOCK at and maintain 11000 and 250knots. When I observed the bottom aircraft descending out of 11800; I issued 'Cross SHOCK at and maintain 12000 and 250knots;' to top aircraft. At SHOCK intersection; I observed the top aircraft at 12800 descending to 12000 and the bottom aircraft at 11300. I asked the bottom aircraft to say altitude and he replied 11300. I told him to increase his descent and he replied 'Traffic insight.' I used the rule of observing an aircraft leaving an altitude before issuing the altitude to another aircraft; but I am second-guessing my application of the rule because I went back and issued crossing restriction after I issued the descent.My recommendation would be to educate the workforce on when they can and cannot use the rule 'Observed leaving an altitude.'
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.