37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 912587 |
Time | |
Date | 201010 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | ZZZ.ARTCC |
State Reference | US |
Aircraft 1 | |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 121 |
Flight Phase | Cruise |
Route In Use | None |
Flight Plan | IFR |
Person 1 | |
Function | Enroute |
Qualification | Air Traffic Control Fully Certified |
Person 2 | |
Function | Enroute |
Qualification | Air Traffic Control Fully Certified |
Events | |
Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy |
Narrative:
Aircraft X was northwest bound at FL360. Sector xw handed aircraft X to me on sector yu. I accepted the handoff because it appeared that the aircraft was headed into my sector on a normal route that we see all day. Sector xw then called to coordinate that aircraft Y; which had already been pointed out to me; was going to climb from FL350 to FL370. Both aircraft were in xw's airspace and it appeared the aircraft Y would pass behind the aircraft X. However; aircraft X was not on a normal route. A few minutes later aircraft X turned left about 30 degrees at KZ10W [a navigation reference system fix]. KZ10W; a fix in the middle of nowhere that is about a mile from actually getting into my airspace. The turn put the aircraft in conflict and although I turned the aircraft X and sector xw turned the aircraft Y; there was not enough time to keep separation. The 'K' fix that aircraft X filed; like all the 'K' fixes; is not depicted anywhere on our maps and none of the controllers in the area at the time had ever seen an aircraft turn at that particular fix. I; nor the xw controller; knew that there was even a fix there. So the assumption on both parties was that aircraft X was proceeding northwest bound into my airspace; when in fact; he turn just before and never entered my airspace. Several years ago when these fixes were put in the system; this exact scenario was brought up by controllers as an error waiting to happen. When thousands of aircraft fly through your airspace on the same route day after day; and then one turns 30 degrees nowhere near a depicted fix; it is going to catch controllers by surprise. Also; if you are going to clear an aircraft down line to one of these 'K' fixes; you do not know where it goes until you actually enter the fix and bring up a route line. You know that the fix is in kansas city center some where but it could be a 30 degree left turn or perhaps 30 degrees right.first depict the fixes on our radar so we know the fixes in our own airspace. Then scrap the 'K' fix grid and make a grid that makes since to people not just computer entries.
Original NASA ASRS Text
Title: Several ARTCC Controllers reported a loss of separation when an aircraft filed on NAVIGATION REFERENCE SYSTEM (NRS) waypoints makes an unanticipated turn.
Narrative: Aircraft X was northwest bound at FL360. Sector XW handed Aircraft X to me on Sector YU. I accepted the handoff because it appeared that the aircraft was headed into my sector on a normal route that we see all day. Sector XW then called to coordinate that Aircraft Y; which had already been pointed out to me; was going to climb from FL350 to FL370. Both aircraft were in XW's airspace and it appeared the Aircraft Y would pass behind the Aircraft X. However; Aircraft X was not on a normal route. A few minutes later Aircraft X turned left about 30 degrees at KZ10W [a Navigation Reference system Fix]. KZ10W; a fix in the middle of nowhere that is about a mile from actually getting into my airspace. The turn put the aircraft in conflict and although I turned the Aircraft X and Sector XW turned the Aircraft Y; there was not enough time to keep separation. The 'K' fix that Aircraft X filed; like all the 'K' fixes; is not depicted anywhere on our maps and none of the Controllers in the area at the time had ever seen an aircraft turn at that particular fix. I; nor the XW Controller; knew that there was even a fix there. So the assumption on both parties was that Aircraft X was proceeding northwest bound into my airspace; when in fact; he turn just before and never entered my airspace. Several years ago when these fixes were put in the system; this exact scenario was brought up by Controllers as an error waiting to happen. When thousands of aircraft fly through your airspace on the same route day after day; and then one turns 30 degrees nowhere near a depicted fix; it is going to catch controllers by surprise. Also; if you are going to clear an aircraft down line to one of these 'K' fixes; you do not know where it goes until you actually enter the fix and bring up a route line. You know that the fix is in Kansas City Center some where but it could be a 30 degree left turn or perhaps 30 degrees right.First depict the fixes on our radar so we know the fixes in our own airspace. Then scrap the 'K' fix grid and make a grid that makes since to people not just computer entries.
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.