 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZID radar associate controller describes failed coordination attempt that resulted in operational error between FL220 and FL230.
| Attributes | |
| ACN | 639184 |
| Time | |
| Date | 200411 |
| Day | Tue |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | navaid : ape.vortac |
| State Reference | OH |
| Altitude | msl bound lower : 22000 msl bound upper : 23000 |
| Environment | |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | artcc : zid.artcc |
| Operator | other |
| Make Model Name | Starlifter (C141) |
| Operating Under FAR Part | Part 91 |
| Flight Phase | climbout : intermediate altitude |
| Flight Plan | IFR |
| Aircraft 2 | |
| Controlling Facilities | artcc : zid.artcc |
| Operator | common carrier : air taxi |
| Make Model Name | Beechjet 400 |
| Operating Under FAR Part | Part 135 |
| Flight Phase | descent : intermediate altitude |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | government : faa |
| Function | controller : handoff position |
| Qualification | controller : radar |
| Experience | controller radar : 0.5 controller time certified in position1 : 1 controller time certified in position2 : 6 |
| ASRS Report | 639184 |
| Person 2 | |
| Affiliation | government : faa |
| Function | controller : radar |
| Events | |
| Anomaly | conflict : airborne less severe non adherence : required legal separation |
| Independent Detector | atc equipment : conflict alert other controllera |
| Resolutory Action | controller : issued alert |
| Consequence | faa : investigated |
| Miss Distance | horizontal : 16800 vertical : 600 |
| Supplementary | |
| Problem Areas | ATC Human Performance |
| Primary Problem | ATC Human Performance |
| Air Traffic Incident | Operational Error |
Narrative:
I called sector 31 to stop aircraft X at FL210. They said aircraft X had already been shipped and was our control. Sector was busy with much coordination, automation problems, r-side taking care of an overtake situation off cmh, and trying to get a dca departure spacing problem taken care of. I told the r-side that aircraft X did not get stopped and was his control to stop -- that the aircraft X had already been shipped to us. I didn't realize he didn't hear me. I was off the line when the aircraft X called and was busy thereafter with other tasks (eg, trying to get a track started, coordination with cmh approach) and didn't realize r-side controller didn't stop the aircraft X. Later, controller cleared aircraft Y from FL240 to FL220. Aircraft X and aircraft Y broke separation since aircraft X was climbing above FL210. They had passed each other by the time the error was noticed, and no further attempts to separate would have helped at that point.
Original NASA ASRS Text
Title: ZID RADAR ASSOCIATE CTLR DESCRIBES FAILED COORD ATTEMPT THAT RESULTED IN OPERROR BTWN FL220 AND FL230.
Narrative: I CALLED SECTOR 31 TO STOP ACFT X AT FL210. THEY SAID ACFT X HAD ALREADY BEEN SHIPPED AND WAS OUR CTL. SECTOR WAS BUSY WITH MUCH COORD, AUTOMATION PROBS, R-SIDE TAKING CARE OF AN OVERTAKE SIT OFF CMH, AND TRYING TO GET A DCA DEP SPACING PROB TAKEN CARE OF. I TOLD THE R-SIDE THAT ACFT X DID NOT GET STOPPED AND WAS HIS CTL TO STOP -- THAT THE ACFT X HAD ALREADY BEEN SHIPPED TO US. I DIDN'T REALIZE HE DIDN'T HEAR ME. I WAS OFF THE LINE WHEN THE ACFT X CALLED AND WAS BUSY THEREAFTER WITH OTHER TASKS (EG, TRYING TO GET A TRACK STARTED, COORD WITH CMH APCH) AND DIDN'T REALIZE R-SIDE CTLR DIDN'T STOP THE ACFT X. LATER, CTLR CLRED ACFT Y FROM FL240 TO FL220. ACFT X AND ACFT Y BROKE SEPARATION SINCE ACFT X WAS CLBING ABOVE FL210. THEY HAD PASSED EACH OTHER BY THE TIME THE ERROR WAS NOTICED, AND NO FURTHER ATTEMPTS TO SEPARATE WOULD HAVE HELPED AT THAT POINT.
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.