37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1007672 |
Time | |
Date | 201204 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | ZME.ARTCC |
State Reference | TN |
Aircraft 1 | |
Make Model Name | Regional Jet 700 ER/LR (CRJ700) |
Operating Under FAR Part | Part 121 |
Flight Phase | Cruise |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | DC-10 Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | Cruise |
Flight Plan | IFR |
Person 1 | |
Function | Enroute |
Qualification | Air Traffic Control Developmental |
Events | |
Anomaly | ATC Issue All Types Conflict Airborne Conflict |
Narrative:
A DC10 and a CRJ7 conflicted with one another. Both were at interim altitudes of FL350. The DC10 made a hard turn at a new fix that was implemented recently as part of new sids at mem. There was moderate to heavy traffic with numerous aircraft in conflictions and a lot going on. I was working the radar associate position and I was trying to keep up and take care of coordination and other duties as well as trying to listen to the r-side. The r-side had a few aircraft on vectors. I was unaware of the sharp turn the DC10 was going to make and was paying attention to other things. Sector 35 called our sector and the calls were forwarded to me. I answered and the controller asked if we were doing anything to separate those two aircraft. I told him I thought the r-side had the DC10 turned out but it was a different aircraft. I got off the line and double checked with the r-side who took immediate action to turn the two aircraft. It was a moment too late and a loss of separation occurred. The new sids was a large factor to this loss of separation. The aircraft go westbound for several miles and then make really large abrupt turns; depending on their route of flight after the SID. It has been a problem since its introduction a couple of months ago. I understand that those in charge of airspace are aware of this and are moving these fixes closer to mem to cut down on this problem.
Original NASA ASRS Text
Title: ZME Controller described a conflict event involving traffic departing MEM both utilizing the new SIDS recently implemented; the reporter claiming the new SIDS were a large contributing factor in this instance.
Narrative: A DC10 and a CRJ7 conflicted with one another. Both were at interim altitudes of FL350. The DC10 made a hard turn at a new fix that was implemented recently as part of new SIDS at MEM. There was moderate to heavy traffic with numerous aircraft in conflictions and a lot going on. I was working the RADAR Associate position and I was trying to keep up and take care of coordination and other duties as well as trying to listen to the R-Side. The R-Side had a few aircraft on vectors. I was unaware of the sharp turn the DC10 was going to make and was paying attention to other things. Sector 35 called our sector and the calls were forwarded to me. I answered and the controller asked if we were doing anything to separate those two aircraft. I told him I thought the R-Side had the DC10 turned out but it was a different aircraft. I got off the line and double checked with the R-Side who took immediate action to turn the two aircraft. It was a moment too late and a loss of separation occurred. The new SIDS was a large factor to this loss of separation. The aircraft go westbound for several miles and then make really large abrupt turns; depending on their route of flight after the SID. It has been a problem since its introduction a couple of months ago. I understand that those in charge of airspace are aware of this and are moving these fixes closer to MEM to cut down on this problem.
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.