 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Chicago center controllers reported a problem associated with incorrect routing and being told of a fix they do not like to use for it.
| Attributes | |
| ACN | 1436387 |
| Time | |
| Date | 201704 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | ZAU.ARTCC |
| State Reference | IL |
| Aircraft 1 | |
| Make Model Name | Large Transport Low Wing 2 Turbojet Eng |
| Flight Phase | Taxi |
| Flight Plan | IFR |
| Person 1 | |
| Function | Enroute |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 4 |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy |
Narrative:
Aircraft X was filed on the KKILR3 arrival. Due to dispatch filing error the extra navigation information was filed incorrectly and en route automation modernization (eram) showed aircraft X unable to fly the KKILR3 RNAV STAR. So the route was shown..kamma..XXX.KKILR3.kmsp. The clearance delivery controller at [the departure airport] issued this. Only when the ZAU harly sector questioned the flights ability to fly the KKILR3 was the XXX questioned by the pilot. The aircraft was issued corrected routing and continued with no issue. Eram will not hand off aircraft with XXX in their route to adjacent facilities so the equipment must be changed in the flight plan menus in the edst. I am uncomfortable changing this information because I don't know this information. We are taught a work around to make this work. I would rather put in non-RNAV routing that eram shows he can fly and coordinating with the adjacent facility. If there is an incident I don't want to have to explain why I changed equipment information on a flight.training for the clearance delivery controller so they don't issue XXX routing. A way to override the XXX so it hands to adjacent facilities and I can coordinate with the receiving controller I verified with the pilot that they are able to fly the RNAV SID/STAR.
Original NASA ASRS Text
Title: Chicago Center Controllers reported a problem associated with incorrect routing and being told of a fix they do not like to use for it.
Narrative: Aircraft X was filed on the KKILR3 arrival. Due to dispatch filing error the extra NAV information was filed incorrectly and En Route Automation Modernization (ERAM) showed Aircraft X unable to fly the KKILR3 RNAV STAR. So the Route was shown..KAMMA..XXX.KKILR3.KMSP. The Clearance Delivery controller at [the departure airport] issued this. Only when the ZAU HARLY sector questioned the flights ability to fly the KKILR3 was the XXX questioned by the pilot. The aircraft was issued corrected routing and continued with no issue. ERAM will not hand off aircraft with XXX in their route to adjacent facilities so the equipment must be changed in the flight plan menus in the EDST. I am uncomfortable changing this information because I don't know this information. We are taught a work around to make this work. I would rather put in Non-RNAV routing that ERAM shows he can fly and coordinating with the adjacent facility. If there is an incident I don't want to have to explain why I changed equipment information on a flight.Training for the clearance delivery controller so they don't issue XXX routing. A way to override the XXX so it hands to adjacent facilities and I can coordinate with the receiving controller I verified with the pilot that they are able to fly the RNAV SID/STAR.
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.