 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZLA d-side controller described confusing routing event when unclear if in fact the r-side controller had changed the subject routing.
| Attributes | |
| ACN | 866418 |
| Time | |
| Date | 200912 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | ZLA.ARTCC |
| State Reference | CA |
| Aircraft 1 | |
| Make Model Name | B737 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Cruise |
| Route In Use | Direct |
| Flight Plan | IFR |
| Person 1 | |
| Function | Handoff / Assist |
| Qualification | Air Traffic Control Fully Certified |
| Person 2 | |
| Function | Enroute |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy |
Narrative:
It is customary for the r-side that issues the route to either put it in; or to ask the d-side to load the route. I have no specific recollection of this event. The r-side said he thought the route was in. Air carrier X was issued a direct route to vhp; but the route did not get in the machine. I remember the r-side signing in; and I had to ask him to make the data blocks bigger because I couldn't see them. It all happened about the same time. Recommendation; apparently the r-side put in vhp and got the message that vhp cannot merge. I believe that this message only appears on the r-side crud. Maybe there could be some other kind of warning; a bell; yellow route in the uret; some significant warning message that this route didn't take. Additionally; I believe the route line displays when entered; whether or not the route took; should be changed to display only when successfully entered.
Original NASA ASRS Text
Title: ZLA D-side Controller described confusing routing event when unclear if in fact the R-side Controller had changed the subject routing.
Narrative: It is customary for the R-side that issues the route to either put it in; or to ask the D-side to load the route. I have no specific recollection of this event. The R-side said he thought the route was in. Air Carrier X was issued a direct route to VHP; but the route did not get in the machine. I remember the R-side signing in; and I had to ask him to make the data blocks bigger because I couldn't see them. it all happened about the same time. Recommendation; apparently the R-side put in VHP and got the message that VHP cannot merge. I believe that this message only appears on the R-side crud. Maybe there could be some other kind of warning; a bell; yellow route in the URET; some significant warning message that this route didn't take. Additionally; I believe the route line displays when entered; whether or not the route took; should be changed to display only when successfully entered.
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.