 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZAU controller described a long standing automation anomaly that alters flight plans depending upon the data entering position.
| Attributes | |
| ACN | 888745 |
| Time | |
| Date | 201005 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | PTK.Airport |
| State Reference | MI |
| Aircraft 1 | |
| Make Model Name | A320 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Descent |
| Route In Use | STAR CRUXX 4 |
| Flight Plan | IFR |
| Person 1 | |
| Function | Enroute |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types |
Narrative:
This aircraft evidently did not have the cruxx 4 arrival after lfd. When I talked to the aircraft; his route showed he had been issued the cruxx 4 arrival. I had no reason to doubt or believe he was not going to fly arrival so I descended the aircraft to FL350 and shipped to joliet sector. The real issue here is the automation over the lfd fix. Aircraft going to dtw and ptk over lfd; if you give aircraft direct lfd and enter it on the r-side it will remove the arrival from the route of flight. This is a known issue that has been around as long as I have been at ZAU. I would like to know why automation has not updated/fixed this known problem. If you enter direct lfd from d-side it leaves the arrival in place but many times you are working without a d-side and do all entries from the r-side. This is an issue that needs to be fixed in a 'safety first' culture. Recommend automation fix adaptation over lfd fix for dtw and ptk arrivals. This issue has been known for years.
Original NASA ASRS Text
Title: ZAU controller described a long standing automation anomaly that alters flight plans depending upon the data entering position.
Narrative: This aircraft evidently did not have the CRUXX 4 arrival after LFD. When I talked to the aircraft; his route showed he had been issued the CRUXX 4 arrival. I had no reason to doubt or believe he was not going to fly arrival so I descended the aircraft to FL350 and shipped to Joliet Sector. The real issue here is the automation over the LFD fix. Aircraft going to DTW and PTK over LFD; if you give aircraft direct LFD and enter it on the R-Side it will remove the arrival from the route of flight. This is a known issue that has been around as long as I have been at ZAU. I would like to know why automation has not updated/fixed this known problem. If you enter direct LFD from D-Side it leaves the arrival in place but many times you are working without a D-Side and do all entries from the R-Side. This is an issue that needs to be fixed in a 'safety first' culture. Recommend automation FIX adaptation over LFD fix for DTW and PTK arrivals. This issue has been known for years.
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.