 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZME controller voiced concern regarding recent automation changes that have added additional controller workload and confusion.
| Attributes | |
| ACN | 997931 |
| Time | |
| Date | 201203 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | ZME.ARTCC |
| State Reference | TN |
| Aircraft 1 | |
| Make Model Name | B777 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Cruise |
| Flight Plan | IFR |
| Person 1 | |
| Function | Enroute |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | ATC Issue All Types |
Narrative:
Changes to host programming have caused filed flight plans with the routing bna.RMG4.katl to require a manual update via a route amendment message or a uret entry to correct the actual flight plan for this flight. The host deficiency indicates to the controller a 'red or blue' routing; a PAR; is required for the flight. The flight is currently flying the RMG4 arrival; no need to reroute other than the fact that the computer system is broken! This problem is exacerbated by two other existing anomalies currently plaguing the ZME area 5 host software without resolve. 1. The failure of the automatic hand-off for sector 63 to sector 62; atl landing traffic over bwg. Previously reported. 2. The loss of the reroute key function direct rmg. Previously reported. 3. Today's latest and greatest. Since the last tape hang-up; aircraft routed bna.RMG4.katl indicate a 'blue-routing' bna.ERLIN9. In other words; area 5 must manually intervene to correct the computer deficiencies once again. In the interest of safety; one would expect solutions to these problems beyond our manual interventions. Quite frankly; I find it repugnant that the eram excuse will be the savior of all.
Original NASA ASRS Text
Title: ZME Controller voiced concern regarding recent automation changes that have added additional controller workload and confusion.
Narrative: Changes to HOST programming have caused filed flight plans with the routing BNA.RMG4.KATL to require a manual update via a route amendment message or a URET entry to correct the actual flight plan for this flight. The HOST deficiency indicates to the controller a 'red or blue' routing; a PAR; is required for the flight. The flight is currently flying the RMG4 arrival; no need to reroute other than the fact that the computer system is BROKEN! This problem is exacerbated by two other existing anomalies currently plaguing the ZME AREA 5 HOST software without resolve. 1. The failure of the AUTO HAND-OFF for Sector 63 to Sector 62; ATL landing traffic over BWG. Previously reported. 2. The loss of the reroute key function DIRECT RMG. Previously reported. 3. Today's latest and greatest. Since the last tape hang-up; aircraft routed BNA.RMG4.KATL indicate a 'blue-routing' BNA.ERLIN9. In other words; Area 5 must manually intervene to correct the computer deficiencies once again. In the interest of safety; one would expect solutions to these problems beyond our manual interventions. Quite frankly; I find it repugnant that the ERAM excuse will be the savior of all.
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.