Air carrier deviating around WX came in close proximity to another air carrier over the ocean.

Attributes
ACN	119190
Time
Date	198908
Day	Tue
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : ack
State Reference	MA
Altitude	msl bound lower : 39000 msl bound upper : 43000
Environment
Flight Conditions	Mixed
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zbw
Operator	common carrier : air carrier
Make Model Name	Widebody, Low Wing, 4 Turbojet Eng
Navigation In Use	Other
Flight Phase	climbout : intermediate altitude
Route In Use	enroute : other oceanic enroute : atlantic
Flight Plan	IFR
Aircraft 2
Operator	common carrier : air carrier
Make Model Name	Widebody, Low Wing, 4 Turbojet Eng
Navigation In Use	Other
Flight Phase	cruise other
Route In Use	enroute : atlantic enroute : other oceanic
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : radar
Qualification	controller : radar
ASRS Report	119190
Person 2
Affiliation	government : faa
Function	controller : radar
Qualification	controller : radar
ASRS Report	119517
Events
Anomaly	conflict : airborne less severe inflight encounter : weather non adherence : required legal separation other spatial deviation
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance
Consequence	Other
Miss Distance	horizontal : 60000 vertical : 0
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

When I relieved sector 17 (nantucket sector), air carrier X was relaying through an air carrier that he was deviating 20 degree right of course for WX. Air carrier X was at FL390 flight planned over slatn and requesting climb to FL410 or FL430. My RA17 controller coordinated a climb to FL430 with the ny oceanic controller and I gave the clearance to the aircraft. Air carrier X was close enough for me to hear his response. Air carrier Y called on frequency at FL390 and he was going over joboc. Air carrier Y also was radar identified about 40 mi east of joboc. 4 or 5 mins later I asked air carrier X to squawk a code and he was identified at FL430 right on top of air carrier Y (air carrier X had reported reaching FL430 4 or 5 mins prior to being identified). Previous to identing air carrier X, 2 primary targets were observed within 2-3 mi of each other, 50 mi east of joboc. I don't know how close the aircraft got before air carrier X was out of FL410 as boston ARTCC does not have radar or communications very far east of 6700 west log.

Original NASA ASRS Text

Title: ACR DEVIATING AROUND WX CAME IN CLOSE PROX TO ANOTHER ACR OVER THE OCEAN.

Narrative: WHEN I RELIEVED SECTOR 17 (NANTUCKET SECTOR), ACR X WAS RELAYING THROUGH AN AIR CARRIER THAT HE WAS DEVIATING 20 DEG RIGHT OF COURSE FOR WX. ACR X WAS AT FL390 FLT PLANNED OVER SLATN AND REQUESTING CLIMB TO FL410 OR FL430. MY RA17 CTLR COORDINATED A CLIMB TO FL430 WITH THE NY OCEANIC CTLR AND I GAVE THE CLRNC TO THE ACFT. ACR X WAS CLOSE ENOUGH FOR ME TO HEAR HIS RESPONSE. ACR Y CALLED ON FREQ AT FL390 AND HE WAS GOING OVER JOBOC. ACR Y ALSO WAS RADAR IDENTIFIED ABOUT 40 MI E OF JOBOC. 4 OR 5 MINS LATER I ASKED ACR X TO SQUAWK A CODE AND HE WAS IDENTIFIED AT FL430 RIGHT ON TOP OF ACR Y (ACR X HAD REPORTED REACHING FL430 4 OR 5 MINS PRIOR TO BEING IDENTIFIED). PREVIOUS TO IDENTING ACR X, 2 PRIMARY TARGETS WERE OBSERVED WITHIN 2-3 MI OF EACH OTHER, 50 MI E OF JOBOC. I DON'T KNOW HOW CLOSE THE ACFT GOT BEFORE ACR X WAS OUT OF FL410 AS BOSTON ARTCC DOES NOT HAVE RADAR OR COMS VERY FAR E OF 6700 W LOG.

Data retrieved from NASA's ASRS site as of August 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.