37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1409571 |
Time | |
Date | 201612 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | ZDC.ARTCC |
State Reference | VA |
Aircraft 1 | |
Make Model Name | Small Transport Low Wing 2 Turboprop Eng |
Operating Under FAR Part | Part 91 |
Flight Phase | Cruise |
Flight Plan | IFR |
Person 1 | |
Function | Enroute |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 7.0 |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types |
Narrative:
Aircraft X ;was shown in the edst (enroute decision support tool) on route dqo.V29.mxe.V3.sbj going to ZZZ. However; the route display on the radar scope showed the dqo.DQO029.V3.sbj routing. There was no blue preferential routing shown in the edst to issue. I didn't realize the difference until the aircraft did not turn right at dqo; and instead continued on V3 to mxe. I attempted to turn the aircraft more to the right because I saw that modena sector had some westbound departures; however I could not reach the aircraft because the frequency was not working well in that vicinity. My assist accomplished the point-out. Buec (backup radios) are also currently out of service. I could not turn the aircraft or communicate with the aircraft when I needed to. Luckily; we were in the 3 mile radar portion; and aircraft X ended up staying on the route (V29.mxe.V3) at 13;000 feet and went behind the departure. North high sector at phl was concerned because the aircraft was not going into her airspace; and I reassured her that the aircraft was on the route (that I thought had passed because it was showing in the machine) and was going over mxe VOR then turning on V3; and that all the point-outs had been done. A little while later; I confirmed with north high sector what route they were shown that aircraft X was on; and they said they were showing dqo.V29.mxe.V3.sbj. Why was blue hert (host embedded route text) routing not displayed in the edst? If there was no blue hert routing displayed; why did the route display on the radar scope show the hert routing? The edst should have alerted me that a preferential route needed to be issued. I am still not clear why the route display shows the route as if the hert routing is applied (in all situations). What is the reason for this? Why would the route display not show the route the aircraft is actually on? I believe we should re-evaluate all hert routings for ZDC; and make appropriate changes. When was the last time it was all updated? Only when there is an issue with one route? Let's go through and check them all; area by area; gather information on known issues from the controllers and get it fixed. Can we change the route display to show the actual route and not the predictive route? If so; provide sufficient training for this change.
Original NASA ASRS Text
Title: A Center Controller reported of a radar display indicating an aircraft had the correct routing but the information on their EDST (Enroute Decision Support Tool) did not default to the proper routing display for the type aircraft. The controller was not made aware the aircraft was not on the correct routing.
Narrative: Aircraft X ;was shown in the EDST (Enroute Decision Support Tool) on route DQO.V29.MXE.V3.SBJ going to ZZZ. However; the route display on the radar scope showed the DQO.DQO029.V3.SBJ routing. There was no blue preferential routing shown in the EDST to issue. I didn't realize the difference until the aircraft did not turn right at DQO; and instead continued on V3 to MXE. I attempted to turn the aircraft more to the right because I saw that Modena sector had some westbound departures; however I could not reach the aircraft because the frequency was not working well in that vicinity. My Assist accomplished the point-out. BUEC (Backup radios) are also currently out of service. I could not turn the aircraft or communicate with the aircraft when I needed to. Luckily; we were in the 3 mile radar portion; and Aircraft X ended up staying on the route (V29.MXE.V3) at 13;000 feet and went behind the departure. North High sector at PHL was concerned because the aircraft was not going into her airspace; and I reassured her that the aircraft was on the route (that I thought had passed because it was showing in the machine) and was going over MXE VOR then turning on V3; and that all the point-outs had been done. A little while later; I confirmed with North High sector what route they were shown that Aircraft X was on; and they said they were showing DQO.V29.MXE.V3.SBJ. Why was blue HERT (Host Embedded Route Text) routing not displayed in the EDST? If there was no blue HERT routing displayed; why did the route display on the radar scope show the HERT routing? The EDST should have alerted me that a preferential route needed to be issued. I am still not clear why the route display shows the route as if the HERT routing is applied (in all situations). What is the reason for this? Why would the route display not show the route the aircraft is actually on? I believe we should re-evaluate all HERT routings for ZDC; and make appropriate changes. When was the last time it was ALL updated? Only when there is an issue with one route? Let's go through and check them all; area by area; gather information on known issues from the controllers and get it fixed. Can we change the route display to show the actual route and not the predictive route? If so; provide sufficient training for this change.
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.