 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Rerouting of traffic by ZOB and WX deviations may have caused a loss of separation by a radar controller.
| Attributes | |
| ACN | 556813 |
| Time | |
| Date | 200208 |
| Day | Thu |
| Local Time Of Day | 1801 To 2400 |
| Place | |
| Locale Reference | navaid : slt.vortac |
| State Reference | PA |
| Altitude | msl bound lower : 37600 msl bound upper : 37900 |
| Environment | |
| Flight Conditions | IMC |
| Light | Night |
| Aircraft 1 | |
| Controlling Facilities | artcc : zob.artcc |
| Operator | common carrier : air carrier |
| Make Model Name | B767 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | cruise : enroute altitude change cruise : holding |
| Route In Use | enroute : on vectors |
| Flight Plan | IFR |
| Aircraft 2 | |
| Controlling Facilities | artcc : zob.artcc |
| Operator | common carrier : air carrier |
| Make Model Name | B757 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | cruise : holding cruise : enroute altitude change |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | government : faa |
| Function | controller : radar |
| Qualification | controller : radar |
| Experience | controller time certified in position1 : 15 |
| ASRS Report | 556813 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : atp |
| Events | |
| Anomaly | conflict : airborne critical inflight encounter : weather non adherence : required legal separation non adherence : published procedure |
| Independent Detector | aircraft equipment : tcas other flight crewa other flight crewb |
| Resolutory Action | flight crew : took evasive action |
| Consequence | faa : investigated |
| Miss Distance | horizontal : 12000 vertical : 600 |
| Supplementary | |
| Problem Areas | Weather Environmental Factor ATC Human Performance |
| Primary Problem | ATC Human Performance |
| Air Traffic Incident | Inter Facility Coordination Failure Intra Facility Coordination Failure Operational Error |
Narrative:
We had been rerouting ewr arrs into the jfk and satellite arrival stream for approximately 20-30 mins when new york jfk sector shut us off. When this occurs, an already complex sector becomes far more complex. Discussions immediately start concerning who we have to hold, where will we hold, who we will have to shut off in addition to staying abreast of traffic sits. Air carrier X (B767) was at FL390 and requesting a west (left) deviation for WX. Knowing this would put him in conflict with an airplane at FL390 over jhw, I descended him. I had overlooked air carrier Y (B757) who was turning around because jfk would not take him. In sits such as this, the conflict alert is useless. By the time I realized the confliction, I tried to stop air carrier X's descent, but inadvertently called him air carrier Z. I descended air carrier Y and he acknowledged and started down. The 2 planes were on a potential collision course. Just as air carrier Y started down, air carrier X advised responding to TCASII and climbed from FL376 up to FL379. Air carrier Y said he too had a TCASII alert. If I had not had a lapse in awareness, the system error wouldn't have occurred. However, if air carrier Y hadn't been rerouted or spun out, this wouldn't have occurred.
Original NASA ASRS Text
Title: REROUTING OF TFC BY ZOB AND WX DEVS MAY HAVE CAUSED A LOSS OF SEPARATION BY A RADAR CTLR.
Narrative: WE HAD BEEN REROUTING EWR ARRS INTO THE JFK AND SATELLITE ARR STREAM FOR APPROX 20-30 MINS WHEN NEW YORK JFK SECTOR SHUT US OFF. WHEN THIS OCCURS, AN ALREADY COMPLEX SECTOR BECOMES FAR MORE COMPLEX. DISCUSSIONS IMMEDIATELY START CONCERNING WHO WE HAVE TO HOLD, WHERE WILL WE HOLD, WHO WE WILL HAVE TO SHUT OFF IN ADDITION TO STAYING ABREAST OF TFC SITS. ACR X (B767) WAS AT FL390 AND REQUESTING A W (L) DEV FOR WX. KNOWING THIS WOULD PUT HIM IN CONFLICT WITH AN AIRPLANE AT FL390 OVER JHW, I DSNDED HIM. I HAD OVERLOOKED ACR Y (B757) WHO WAS TURNING AROUND BECAUSE JFK WOULD NOT TAKE HIM. IN SITS SUCH AS THIS, THE CONFLICT ALERT IS USELESS. BY THE TIME I REALIZED THE CONFLICTION, I TRIED TO STOP ACR X'S DSCNT, BUT INADVERTENTLY CALLED HIM ACR Z. I DSNDED ACR Y AND HE ACKNOWLEDGED AND STARTED DOWN. THE 2 PLANES WERE ON A POTENTIAL COLLISION COURSE. JUST AS ACR Y STARTED DOWN, ACR X ADVISED RESPONDING TO TCASII AND CLBED FROM FL376 UP TO FL379. ACR Y SAID HE TOO HAD A TCASII ALERT. IF I HAD NOT HAD A LAPSE IN AWARENESS, THE SYS ERROR WOULDN'T HAVE OCCURRED. HOWEVER, IF ACR Y HADN'T BEEN REROUTED OR SPUN OUT, THIS WOULDN'T HAVE OCCURRED.
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.