37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1075880 |
Time | |
Date | 201303 |
Local Time Of Day | 0001-0600 |
Place | |
Locale Reference | ZOB.ARTCC |
State Reference | OH |
Aircraft 1 | |
Make Model Name | Dash 8-400 |
Operating Under FAR Part | Part 121 |
Flight Phase | Cruise |
Flight Plan | IFR |
Person 1 | |
Function | Enroute |
Qualification | Air Traffic Control Developmental |
Events | |
Anomaly | ATC Issue All Types Deviation - Track / Heading All Types |
Narrative:
D-side controller issued a clearance direct to the extol intersection just on the east side of our airspace. I route keyed the aircraft in direct extol it appeared to process correctly; however there have been known issues with the processing using this particular intersection. When I routed in direct using the route key I had not noticed the computer dropped out the Shaff7 arrival to ewr; last I saw on my acl the aircraft had the arrival. ZBW reported the deviation; they showed the aircraft direct extol direct ewr which was not in fact what the aircraft was doing. I believe the software should at least show us a processing error or some kind of notification if it is going to drop any portion of routing. I also see several times a day where ZBW routes props inbound to cyyz direct to the linng intersection and the computer drops out the Verko2 arrival; but if I look in the previous route it shows the had the proper arrival.
Original NASA ASRS Text
Title: ZOB Controller described an incorrect routing event when software indicated the correct routing was processing correctly but in fact was dropping out a key route segment.
Narrative: D-Side Controller issued a clearance direct to the EXTOL Intersection just on the east side of our airspace. I route keyed the aircraft in direct EXTOL it appeared to process correctly; however there have been known issues with the processing using this particular intersection. When I routed in direct using the route key I had not noticed the computer dropped out the Shaff7 arrival to EWR; last I saw on my ACL the aircraft had the arrival. ZBW reported the deviation; they showed the aircraft direct EXTOL direct EWR which was not in fact what the aircraft was doing. I believe the software should at least show us a processing error or some kind of notification if it is going to drop any portion of routing. I also see several times a day where ZBW routes props inbound to CYYZ direct to the LINNG Intersection and the computer drops out the Verko2 arrival; but if I look in the previous route it shows the had the proper arrival.
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.