 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZAU controller experienced operational deviation during clearance readback error as aircraft entered adjacent ZID sector.
| Attributes | |
| ACN | 639009 |
| Time | |
| Date | 200410 |
| Day | Tue |
| Local Time Of Day | 0601 To 1200 |
| Place | |
| Locale Reference | navaid : fwa.vortac |
| State Reference | IN |
| Altitude | msl single value : 24000 |
| Environment | |
| Flight Conditions | VMC |
| Weather Elements | Turbulence |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | artcc : zau.artcc artcc : zid.artcc |
| Operator | common carrier : air carrier |
| Make Model Name | DC-9 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | descent : intermediate altitude |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | government : faa |
| Function | controller : radar |
| Qualification | controller : radar |
| Experience | controller time certified in position1 : 18 controller time certified in position2 : 7 |
| ASRS Report | 639009 |
| Person 2 | |
| Affiliation | government : faa |
| Function | controller : radar |
| Qualification | controller : radar |
| Experience | controller radar : 19 flight time total : 365 |
| ASRS Report | 635239 |
| Events | |
| Anomaly | airspace violation : entry non adherence : published procedure |
| Independent Detector | other controllera other controllerb |
| Resolutory Action | none taken : detected after the fact |
| Supplementary | |
| Problem Areas | ATC Human Performance |
| Primary Problem | ATC Human Performance |
| Air Traffic Incident | Operational Deviation |
Narrative:
Air carrier X was on 124.82 10 NM northwest of fwa VORTAC at FL290. Aircraft was issued 'air carrier X contact ZAU on 119.85.' the aircraft read back '118.95.' 124.82 is slightly garbled near fwa VORTAC and I missed that pilot readback, wrong frequency. Aircraft stayed at FL240, LOA states aircraft should be at FL230. I did not know aircraft went to wrong frequency. The low side controller that I tried to ship aircraft to did not inform me that air carrier X never showed up. I assumed they would descend aircraft or point out to day sector if they didn't, since I shipped aircraft with plenty of time to descend. Sector had data block overlap and I dropped data block. Air carrier X violated day sector at FL240 without a pointout.
Original NASA ASRS Text
Title: ZAU CTLR EXPERIENCED OPDEV DURING CLRNC READBACK ERROR AS ACFT ENTERED ADJACENT ZID SECTOR.
Narrative: ACR X WAS ON 124.82 10 NM NW OF FWA VORTAC AT FL290. ACFT WAS ISSUED 'ACR X CONTACT ZAU ON 119.85.' THE ACFT READ BACK '118.95.' 124.82 IS SLIGHTLY GARBLED NEAR FWA VORTAC AND I MISSED THAT PLT READBACK, WRONG FREQ. ACFT STAYED AT FL240, LOA STATES ACFT SHOULD BE AT FL230. I DID NOT KNOW ACFT WENT TO WRONG FREQ. THE LOW SIDE CTLR THAT I TRIED TO SHIP ACFT TO DID NOT INFORM ME THAT ACR X NEVER SHOWED UP. I ASSUMED THEY WOULD DSND ACFT OR POINT OUT TO DAY SECTOR IF THEY DIDN'T, SINCE I SHIPPED ACFT WITH PLENTY OF TIME TO DSND. SECTOR HAD DATA BLOCK OVERLAP AND I DROPPED DATA BLOCK. ACR X VIOLATED DAY SECTOR AT FL240 WITHOUT A POINTOUT.
Data retrieved from NASA's ASRS site as of July 2007 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.