37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 184881 |
Time | |
Date | 199107 |
Day | Thu |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | atc facility : slt |
State Reference | PA |
Altitude | msl bound lower : 31000 msl bound upper : 31000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | artcc : zob |
Operator | common carrier : air carrier |
Make Model Name | Large Transport, Low Wing, 3 Turbojet Eng |
Flight Phase | climbout : intermediate altitude |
Route In Use | enroute : on vectors |
Flight Plan | IFR |
Aircraft 2 | |
Operator | common carrier : air carrier |
Make Model Name | Medium Large Transport, Low Wing, 2 Turbojet Eng |
Flight Phase | cruise other |
Route In Use | enroute : direct |
Flight Plan | IFR |
Person 1 | |
Affiliation | government : faa |
Function | controller : radar |
Qualification | controller : radar |
ASRS Report | 184881 |
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 | controller : issued new clearance other |
Consequence | faa : investigated |
Miss Distance | horizontal : 25800 vertical : 1100 |
Supplementary | |
Primary Problem | ATC Human Performance |
Air Traffic Incident | Intra Facility Coordination Failure Operational Error |
Narrative:
Air carrier X departed yyz-dkk direct psb climbing to interim altitude FL290 (required FL330). I had just finished an intrail spacing problem for traffic en route ewr with a couple of these at FL330. Air carrier X called and said they were approaching FL290 required FL330. I checked my traffic and looked at the bki sector (FL240-FL310) and fkl sector (FL330 and above). I observed no traffic and issued air carrier X climb to FL330 initiated handoff to fkl sector and made ovd point out to bki sector. I called the bki controller and made verbal point out. She said point out approved if air carrier X can cross 20 mi northeast psb at FL330. (No traffic was issued.) I knew the restriction was almost impossible but since the bki sector was and had been busy, I'd help. I asked air carrier X if he could meet the restriction, he replied that it might be tough, so I issued turn left heading 090, reaching FL330, cleared direct psb. I then called the fkl sector and relayed the clearance and gave him control. I then looked for the bki sector's traffic and observed a limited data block at FL310 on J146. I then issued a rerte to another aircraft to keep it out of the same bki sector. I then observed air carrier X and the FL310 traffic in such position I could clear air carrier X on course. At that time the fkl controller called and said 'there's some traffic to the east, no big deal, line do a left turn and go back to psb.' because the only traffic I was aware of was clear, I missed the 'do a left turn' and I cleared air carrier X direct psb and he went right. I called to make a point out to the new york center mip sector (N75). He told me he already approved it reference air carrier Y. I said I didn't know who air carrier Y was. About that time the fkl controller came on the override line and yelled which way is air carrier X turning, then, turn -- turn left. Because I still didn't know where the traffic was, I issued an immediate left turn heading 080 (just to get the turn started) and requested an expeditious climb. It was then I saw the traffic. Closest proximity was 4.3 mi and 1100 ft. Several different actions could have prevented this. When I was given what seemed to be an impossible restriction I should have descended air carrier X back to FL290 and left that sector work him. When I coordination with the fkl controller and gave him control, I should have switched communications.
Original NASA ASRS Text
Title: ACR X HAD LTSS FROM ACR Y. SYS ERROR. ARTCC INTRAFAC COORD.
Narrative: ACR X DEPARTED YYZ-DKK DIRECT PSB CLBING TO INTERIM ALT FL290 (REQUIRED FL330). I HAD JUST FINISHED AN INTRAIL SPACING PROB FOR TFC ENRTE EWR WITH A COUPLE OF THESE AT FL330. ACR X CALLED AND SAID THEY WERE APCHING FL290 REQUIRED FL330. I CHKED MY TFC AND LOOKED AT THE BKI SECTOR (FL240-FL310) AND FKL SECTOR (FL330 AND ABOVE). I OBSERVED NO TFC AND ISSUED ACR X CLB TO FL330 INITIATED HDOF TO FKL SECTOR AND MADE OVD POINT OUT TO BKI SECTOR. I CALLED THE BKI CTLR AND MADE VERBAL POINT OUT. SHE SAID POINT OUT APPROVED IF ACR X CAN CROSS 20 MI NE PSB AT FL330. (NO TFC WAS ISSUED.) I KNEW THE RESTRICTION WAS ALMOST IMPOSSIBLE BUT SINCE THE BKI SECTOR WAS AND HAD BEEN BUSY, I'D HELP. I ASKED ACR X IF HE COULD MEET THE RESTRICTION, HE REPLIED THAT IT MIGHT BE TOUGH, SO I ISSUED TURN L HDG 090, REACHING FL330, CLRED DIRECT PSB. I THEN CALLED THE FKL SECTOR AND RELAYED THE CLRNC AND GAVE HIM CTL. I THEN LOOKED FOR THE BKI SECTOR'S TFC AND OBSERVED A LIMITED DATA BLOCK AT FL310 ON J146. I THEN ISSUED A RERTE TO ANOTHER ACFT TO KEEP IT OUT OF THE SAME BKI SECTOR. I THEN OBSERVED ACR X AND THE FL310 TFC IN SUCH POS I COULD CLR ACR X ON COURSE. AT THAT TIME THE FKL CTLR CALLED AND SAID 'THERE'S SOME TFC TO THE E, NO BIG DEAL, LINE DO A L TURN AND GO BACK TO PSB.' BECAUSE THE ONLY TFC I WAS AWARE OF WAS CLR, I MISSED THE 'DO A L TURN' AND I CLRED ACR X DIRECT PSB AND HE WENT R. I CALLED TO MAKE A POINT OUT TO THE NEW YORK CENTER MIP SECTOR (N75). HE TOLD ME HE ALREADY APPROVED IT REF ACR Y. I SAID I DIDN'T KNOW WHO ACR Y WAS. ABOUT THAT TIME THE FKL CTLR CAME ON THE OVERRIDE LINE AND YELLED WHICH WAY IS ACR X TURNING, THEN, TURN -- TURN L. BECAUSE I STILL DIDN'T KNOW WHERE THE TFC WAS, I ISSUED AN IMMEDIATE L TURN HDG 080 (JUST TO GET THE TURN STARTED) AND REQUESTED AN EXPEDITIOUS CLB. IT WAS THEN I SAW THE TFC. CLOSEST PROX WAS 4.3 MI AND 1100 FT. SEVERAL DIFFERENT ACTIONS COULD HAVE PREVENTED THIS. WHEN I WAS GIVEN WHAT SEEMED TO BE AN IMPOSSIBLE RESTRICTION I SHOULD HAVE DSNDED ACR X BACK TO FL290 AND LEFT THAT SECTOR WORK HIM. WHEN I COORD WITH THE FKL CTLR AND GAVE HIM CTL, I SHOULD HAVE SWITCHED COMS.
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.