 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Air carrier Y climb to occupied altitude had less than standard separation from air carrier X. System error.
| Attributes | |
| ACN | 243161 |
| Time | |
| Date | 199306 |
| Day | Wed |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | atc facility : bvt |
| State Reference | IN |
| Altitude | msl bound lower : 33000 msl bound upper : 33000 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | artcc : zau |
| Operator | common carrier : air carrier |
| Make Model Name | Medium Large Transport, Low Wing, 2 Turbojet Eng |
| Navigation In Use | Other Other |
| Flight Phase | cruise other |
| Route In Use | enroute : direct |
| Flight Plan | IFR |
| Aircraft 2 | |
| Operator | common carrier : air carrier |
| Make Model Name | Medium Large Transport, Low Wing, 2 Turbojet Eng |
| Navigation In Use | Other Other |
| Flight Phase | climbout : intermediate altitude |
| Route In Use | enroute : direct |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | government : faa |
| Function | oversight : supervisor |
| Qualification | controller : radar |
| ASRS Report | 243161 |
| Person 2 | |
| Affiliation | government : faa |
| Function | controller : radar |
| Qualification | controller : radar |
| Events | |
| Anomaly | conflict : airborne less severe non adherence : published procedure non adherence : required legal separation |
| Independent Detector | other controllera |
| Resolutory Action | none taken : anomaly accepted |
| Consequence | faa : investigated |
| Miss Distance | horizontal : 24000 vertical : 1500 |
| Supplementary | |
| Primary Problem | ATC Human Performance |
| Air Traffic Incident | Operational Error |
Narrative:
I was supervising in the south area of operation, ZAU. Having just completed a scan of the area's sectors to determine if any assistance was required, I was informed by the bvt controller that an aircraft on his frequency, air carrier X, was responding to an RA (TCASII). I looked over and saw air carrier X and air carrier Y within 5 mi and less than 2000 ft of one another within the confines of the rbs sector. I went to the rbs sector and the controller stated 'I just had a deal.' I observed that the aircraft were in no danger of colliding. I immediately had the radar and manual controller relieved from duty, and notified the area manager in charge. The r-ctlr said he simply gave a clearance to air carrier Y that put him in confliction with air carrier X. There's a possibility that he issued the clearance with data blocks overlapping causing the controller(south) to be unable to recognize the confliction. Suggestion to prevent a recurrence: don't issue a clearance to aircraft with overlapping data blocks.
Original NASA ASRS Text
Title: ACR Y CLB TO OCCUPIED ALT HAD LTSS FROM ACR X. SYS ERROR.
Narrative: I WAS SUPERVISING IN THE S AREA OF OP, ZAU. HAVING JUST COMPLETED A SCAN OF THE AREA'S SECTORS TO DETERMINE IF ANY ASSISTANCE WAS REQUIRED, I WAS INFORMED BY THE BVT CTLR THAT AN ACFT ON HIS FREQ, ACR X, WAS RESPONDING TO AN RA (TCASII). I LOOKED OVER AND SAW ACR X AND ACR Y WITHIN 5 MI AND LESS THAN 2000 FT OF ONE ANOTHER WITHIN THE CONFINES OF THE RBS SECTOR. I WENT TO THE RBS SECTOR AND THE CTLR STATED 'I JUST HAD A DEAL.' I OBSERVED THAT THE ACFT WERE IN NO DANGER OF COLLIDING. I IMMEDIATELY HAD THE RADAR AND MANUAL CTLR RELIEVED FROM DUTY, AND NOTIFIED THE AREA MGR IN CHARGE. THE R-CTLR SAID HE SIMPLY GAVE A CLRNC TO ACR Y THAT PUT HIM IN CONFLICTION WITH ACR X. THERE'S A POSSIBILITY THAT HE ISSUED THE CLRNC WITH DATA BLOCKS OVERLAPPING CAUSING THE CTLR(S) TO BE UNABLE TO RECOGNIZE THE CONFLICTION. SUGGESTION TO PREVENT A RECURRENCE: DON'T ISSUE A CLRNC TO ACFT WITH OVERLAPPING DATA BLOCKS.
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.