 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZAU controller described a flawed automated hand off attempt to C90; the reporter noting several similar recent events
| Attributes | |
| ACN | 967501 |
| Time | |
| Date | 201108 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | ZAU.ARTCC |
| State Reference | IL |
| Aircraft 1 | |
| Make Model Name | EMB ERJ 145 ER&LR |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Descent |
| Flight Plan | IFR |
| Person 1 | |
| Function | Enroute |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | ATC Issue All Types |
Narrative:
I was working the bearz sector on an east flow for ord. On east flow; all aircraft get re-routed over the fix esspo then direct ord. Aircraft X had the correct routing into the uret. He was squawking a code which our NAS system identified. The aircraft was in hand off status when chicago TRACON calls me to say that he see's the hand off on the aircraft but does not see the aircraft. I asked the controller what he meant. He said he only saw a primary target on the aircraft and that no code was being squawked. I confirmed to the controller that the aircraft was squawking. As the aircraft was about 3 miles from the boundary; C90 said they finally saw the target and called radar contact. I then shipped the aircraft without further incident. I have seen this situation more than once as of late and some type of issue is in automation or radar whichever is causing this issue and needs to be investigated and fixed. I've had a few aircraft go into C90 where they couldn't see them and I've been told that its because some other aircraft in the TRACON is already squawking the same code and causes issues. If this is the case; we need to figure out how to avoid this.
Original NASA ASRS Text
Title: ZAU Controller described a flawed automated hand off attempt to C90; the reporter noting several similar recent events
Narrative: I was working the Bearz Sector on an East Flow for ORD. On East flow; all aircraft get re-routed over the FIX Esspo then direct ORD. Aircraft X had the correct routing into the URET. He was squawking a code which our NAS system identified. The aircraft was in hand off status when Chicago TRACON calls me to say that he see's the hand off on the aircraft but does not see the aircraft. I asked the controller what he meant. He said he only saw a primary target on the aircraft and that no code was being squawked. I confirmed to the controller that the aircraft was squawking. As the aircraft was about 3 miles from the boundary; C90 said they finally saw the target and called RADAR contact. I then shipped the aircraft without further incident. I have seen this situation more than once as of late and some type of issue is in automation or RADAR whichever is causing this issue and needs to be investigated and fixed. I've had a few aircraft go into C90 where they couldn't see them and I've been told that its because some other aircraft in the TRACON is already squawking the same code and causes issues. If this is the case; we need to figure out how to avoid this.
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.