Missed crossing restr, possibly.

Attributes
ACN	298510
Time
Date	199503
Day	Fri
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : har
State Reference	PA
Altitude	msl bound lower : 18000 msl bound upper : 18000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zny
Operator	common carrier : air carrier
Make Model Name	B737-200
Operating Under FAR Part	Part 121
Flight Phase	cruise other descent other
Route In Use	arrival star : star enroute : direct
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 200 flight time total : 5000 flight time type : 2000
ASRS Report	298510
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp
Events
Anomaly	altitude deviation : crossing restriction not met non adherence : clearance other anomaly other
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance other
Consequence	faa : reviewed incident with flight crew
Supplementary
Primary Problem	Ambiguous
Air Traffic Incident	other

Narrative:

Original clearance was bfd direct psb, bucks 3 phl. Somewhere in the vicinity of bfd we were cleared directly to har on the bucks 3 arrival. While proceeding directly to har, and after changing to the next sector of ZNY, we received and read back a clearance to cross 30 southeast of har at FL180. Several mins later, ZNY asked if we were going to make the crossing of 30 southeast of psb at FL180. We said that psb was no longer on our route of flight and that we understood the clearance to be har. We were then given a vector for descent. Callback conversation with reporter revealed the following information: the reporter flies the B-737-200 for a major united states air carrier. The reporter thinks that the ARTCC controller goofed between psb and har. The reporter states that 'there is no doubt in my mind' that he read back the fix that was issued to him. The controller was upset initially, then calmed down and issued another vector. The reporter is not entirely in favor of cockpit resource management 'as it is being presented at his air carrier.'

Original NASA ASRS Text

Title: MISSED XING RESTR, POSSIBLY.

Narrative: ORIGINAL CLRNC WAS BFD DIRECT PSB, BUCKS 3 PHL. SOMEWHERE IN THE VICINITY OF BFD WE WERE CLRED DIRECTLY TO HAR ON THE BUCKS 3 ARR. WHILE PROCEEDING DIRECTLY TO HAR, AND AFTER CHANGING TO THE NEXT SECTOR OF ZNY, WE RECEIVED AND READ BACK A CLRNC TO CROSS 30 SE OF HAR AT FL180. SEVERAL MINS LATER, ZNY ASKED IF WE WERE GOING TO MAKE THE XING OF 30 SE OF PSB AT FL180. WE SAID THAT PSB WAS NO LONGER ON OUR RTE OF FLT AND THAT WE UNDERSTOOD THE CLRNC TO BE HAR. WE WERE THEN GIVEN A VECTOR FOR DSCNT. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: THE RPTR FLIES THE B-737-200 FOR A MAJOR UNITED STATES ACR. THE RPTR THINKS THAT THE ARTCC CTLR GOOFED BTWN PSB AND HAR. THE RPTR STATES THAT 'THERE IS NO DOUBT IN MY MIND' THAT HE READ BACK THE FIX THAT WAS ISSUED TO HIM. THE CTLR WAS UPSET INITIALLY, THEN CALMED DOWN AND ISSUED ANOTHER VECTOR. THE RPTR IS NOT ENTIRELY IN FAVOR OF COCKPIT RESOURCE MGMNT 'AS IT IS BEING PRESENTED AT HIS ACR.'

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.