37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1028508 |
Time | |
Date | 201208 |
Local Time Of Day | 0001-0600 |
Place | |
Locale Reference | ZZZ.ARTCC |
State Reference | US |
Aircraft 1 | |
Make Model Name | EMB ERJ 190/195 ER/LR |
Operating Under FAR Part | Part 121 |
Flight Phase | Cruise |
Route In Use | Vectors |
Flight Plan | IFR |
Person 1 | |
Function | Enroute |
Qualification | Air Traffic Control Fully Certified |
Events | |
Anomaly | ATC Issue All Types Airspace Violation All Types Conflict Airborne Conflict Inflight Event / Encounter Weather / Turbulence |
Narrative:
I was working combined sectors with numerous aircraft and severe impact of weather and airspace constrictions. The warning area was active and 'not' accepting point outs. I had aircraft that needed to go around weather so I had to have these aircraft squawk 7700 in order to fly through the warning area. During all of this; I accepted a point out on air carrier Y climbing to FL360. Literally moments later; I took a hand off on air carrier X who was on a large deviation around weather at FL340 and headed towards the warning area. I was working other aircraft that were already on 7700 codes and was in the process of having air carrier X do so as well when both the adjacent sector cpc and I noticed the confliction. The adjacent sector cpc could not enter the warning area airspace with their air carrier Y and my air carrier X would not turn so the adjacent sector tried to get a report from their aircraft that they were out of FL350. I thought that they had received that report and that they didn't know how to report it in the data tag so I /ok'd the function from my position. I reported the aircraft at FL350 only to have the data tag reset to FL347. Sometime later; the supervisor came over to ask what happened between our aircraft. I thought that we had both vertical and horizontal but the supervisor said that we did not. Have my aircraft squawk 7700 sooner when ever they are near military airspace and/or other aircraft because of weather.
Original NASA ASRS Text
Title: Enroute Controller described a loss of separation event during weather deviations and vectors to clear restricted airspace.
Narrative: I was working combined sectors with numerous aircraft and severe impact of weather and airspace constrictions. The Warning Area was active and 'not' accepting point outs. I had aircraft that needed to go around weather so I had to have these aircraft squawk 7700 in order to fly through the Warning Area. During all of this; I accepted a point out on Air Carrier Y climbing to FL360. Literally moments later; I took a hand off on Air Carrier X who was on a large deviation around weather at FL340 and headed towards the Warning Area. I was working other aircraft that were already on 7700 Codes and was in the process of having Air Carrier X do so as well when both the adjacent sector CPC and I noticed the confliction. The adjacent sector CPC could not enter the Warning Area airspace with their Air Carrier Y and my Air Carrier X would not turn so the adjacent sector tried to get a report from their aircraft that they were out of FL350. I thought that they had received that report and that they didn't know how to report it in the data tag so I /ok'd the function from my position. I reported the aircraft at FL350 only to have the Data tag reset to FL347. Sometime later; the supervisor came over to ask what happened between our aircraft. I thought that we had both vertical and horizontal but the supervisor said that we did not. Have my aircraft squawk 7700 sooner when ever they are near military airspace and/or other aircraft because of weather.
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.