Probable interfacility coordination breakdown between ZNY and ZDC ARTCC.

Attributes
ACN	493890
Time
Date	200011
Day	Thu
Place
Locale Reference	navaid : aml.vor
State Reference	VA
Altitude	msl bound lower : 33000 msl bound upper : 33500
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zny.artcc artcc : zdc.artcc tower : bed.tower
Operator	common carrier : air carrier
Make Model Name	Medium Large Transport, Low Wing, 2 Turbojet Eng
Operating Under FAR Part	Part 121
Flight Phase	cruise : enroute altitude change
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 60 flight time total : 10000 flight time type : 2500
ASRS Report	493890
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : multi engine pilot : commercial pilot : instrument
Events
Anomaly	non adherence : published procedure other anomaly other
Independent Detector	other controllerb
Resolutory Action	controller : issued new clearance
Supplementary
Problem Areas	ATC Human Performance
Primary Problem	ATC Human Performance
Air Traffic Incident	Inter Facility Coordination Failure

Narrative:

Level FL330 approximately 60 mi north of aml in ZNY airspace. ZNY gave clearance to FL350 with frequency change to contact ZDC. PF and PNF used double point method to confirm correct clearance and altitude set in altitude display window. After checking in with ZDC, the controller responded that he would have FL350 shortly. PNF responded that we were already climbing to FL350 with previous clearance. Controller initially said 'stand by...let me check.' approximately 10-15 seconds later, the controller asked us to stop climb and return to FL330. I asked controller if we had received a clearance in error. He responded that he had no way of knowing -- 'don't worry about it, no problem.' approximately 1-2 mins later, after level at FL330, we saw traffic on TCASII at FL350 opposite direction. No conflict ever occurred. Dca controller, just prior to handing us off, once again said 'I wouldn't worry about it.' we had an observer on the jump seat that was sure he heard FL350 also. I believe a lack of coordination or communication between 2 ARTCC's probably led to this situation.

Original NASA ASRS Text

Title: PROBABLE INTERFAC COORD BREAKDOWN BTWN ZNY AND ZDC ARTCC.

Narrative: LEVEL FL330 APPROX 60 MI N OF AML IN ZNY AIRSPACE. ZNY GAVE CLRNC TO FL350 WITH FREQ CHANGE TO CONTACT ZDC. PF AND PNF USED DOUBLE POINT METHOD TO CONFIRM CORRECT CLRNC AND ALT SET IN ALT DISPLAY WINDOW. AFTER CHKING IN WITH ZDC, THE CTLR RESPONDED THAT HE WOULD HAVE FL350 SHORTLY. PNF RESPONDED THAT WE WERE ALREADY CLBING TO FL350 WITH PREVIOUS CLRNC. CTLR INITIALLY SAID 'STAND BY...LET ME CHK.' APPROX 10-15 SECONDS LATER, THE CTLR ASKED US TO STOP CLB AND RETURN TO FL330. I ASKED CTLR IF WE HAD RECEIVED A CLRNC IN ERROR. HE RESPONDED THAT HE HAD NO WAY OF KNOWING -- 'DON'T WORRY ABOUT IT, NO PROB.' APPROX 1-2 MINS LATER, AFTER LEVEL AT FL330, WE SAW TFC ON TCASII AT FL350 OPPOSITE DIRECTION. NO CONFLICT EVER OCCURRED. DCA CTLR, JUST PRIOR TO HANDING US OFF, ONCE AGAIN SAID 'I WOULDN'T WORRY ABOUT IT.' WE HAD AN OBSERVER ON THE JUMP SEAT THAT WAS SURE HE HEARD FL350 ALSO. I BELIEVE A LACK OF COORD OR COM BTWN 2 ARTCC'S PROBABLY LED TO THIS SIT.

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.