 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZID controller voiced concern regarding uret protocols used in various centers that resulted in unwanted/unknown routing changes.
| Attributes | |
| ACN | 789072 |
| Time | |
| Date | 200806 |
| Place | |
| Locale Reference | navaid : ape.vortac |
| State Reference | OH |
| Altitude | msl single value : 33000 |
| Environment | |
| Flight Conditions | IMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | artcc : zid.artcc |
| Operator | common carrier : air carrier |
| Make Model Name | CRJ 900 (all) Canadair Regional Jet 900 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | cruise : level ground : maintenance |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | government : faa |
| Function | controller : radar |
| Qualification | controller : radar |
| Experience | controller radar : 18 controller time certified in position1 : 19 |
| ASRS Report | 789072 |
| Events | |
| Anomaly | other anomaly other |
| Independent Detector | other controllera |
| Resolutory Action | none taken : anomaly accepted |
| Supplementary | |
| Problem Areas | FAA ATC Facility |
| Primary Problem | ATC Facility |
| Situations | |
| ATC Facility | computer equipment : zid.artcc procedure or policy : zid.artcc |
Narrative:
I was one staffing the ape sector. Aircraft X was filed ord..ape.J186.odf.WHINZ1.atl. I clicked on the routing portion of the flight plan in uret and tried to give direct hmv. The routing pops up as ape.J186.sot.FLCON3.atl. If I do a quick search while one staffing a sector and click on hmv and send the amendment it will change the arrival into atl. I would have thought that all I did was give direct hmv and the routing to stay the same. This is a known trap happening quite frequently and has to do with the automation between ZID and ZTL not wanting the same thing. ZID wants to be able to put in an amendment without having to do extra work and worry about the arrival changing inadvertently.
Original NASA ASRS Text
Title: ZID CTLR VOICED CONCERN REGARDING URET PROTOCOLS USED IN VARIOUS CENTERS THAT RESULTED IN UNWANTED/UNKNOWN ROUTING CHANGES.
Narrative: I WAS ONE STAFFING THE APE SECTOR. ACFT X WAS FILED ORD..APE.J186.ODF.WHINZ1.ATL. I CLICKED ON THE ROUTING PORTION OF THE FLT PLAN IN URET AND TRIED TO GIVE DIRECT HMV. THE ROUTING POPS UP AS APE.J186.SOT.FLCON3.ATL. IF I DO A QUICK SEARCH WHILE ONE STAFFING A SECTOR AND CLICK ON HMV AND SEND THE AMENDMENT IT WILL CHANGE THE ARR INTO ATL. I WOULD HAVE THOUGHT THAT ALL I DID WAS GIVE DIRECT HMV AND THE ROUTING TO STAY THE SAME. THIS IS A KNOWN TRAP HAPPENING QUITE FREQUENTLY AND HAS TO DO WITH THE AUTOMATION BTWN ZID AND ZTL NOT WANTING THE SAME THING. ZID WANTS TO BE ABLE TO PUT IN AN AMENDMENT WITHOUT HAVING TO DO EXTRA WORK AND WORRY ABOUT THE ARR CHANGING INADVERTENTLY.
Data retrieved from NASA's ASRS site as of May 2009 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.