Flight crew fails to check the non common route associated with their arrival into jfk.

Attributes
ACN	315520
Time
Date	199509
Day	Thu
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : ene
State Reference	ME
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zbu
Operator	common carrier : air carrier
Make Model Name	Commercial Fixed Wing
Operating Under FAR Part	Part 121
Navigation In Use	Other Other
Flight Phase	cruise other
Route In Use	enroute : other oceanic
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 150 flight time total : 20000 flight time type : 2000
ASRS Report	315520
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : instrument pilot : commercial
Events
Anomaly	non adherence : clearance other spatial deviation
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance other
Consequence	faa : reviewed incident with flight crew
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

Flight had been rerted over ocean. Gander ATC thus gave us an expected codified route assignment onward to a fix at the united states border appropriate to the coast-in fix off the atlantic into canada. The experienced copilot affirmed, with book in hand, that the route was correct, thus we both neglected to check the non common portion to jfk -- a kennebunk arrival instead of a plymm 4 arrival. Our route was very subtly different en route to a common descent point - - providence. ZBW queried us on our flight path when we appeared to be slightly off track. He corrected our mistake apparently without penalizing the crew. The situation was potentially hazardous should these have been other traffic as there often is. We broke a rule of thorough confirmation and the lapse quickly made itself evident. It further underscores the need to confirm routing each time one changes frequency, altitude, and routings!

Original NASA ASRS Text

Title: FLC FAILS TO CHK THE NON COMMON RTE ASSOCIATED WITH THEIR ARR INTO JFK.

Narrative: FLT HAD BEEN RERTED OVER OCEAN. GANDER ATC THUS GAVE US AN EXPECTED CODIFIED RTE ASSIGNMENT ONWARD TO A FIX AT THE UNITED STATES BORDER APPROPRIATE TO THE COAST-IN FIX OFF THE ATLANTIC INTO CANADA. THE EXPERIENCED COPLT AFFIRMED, WITH BOOK IN HAND, THAT THE RTE WAS CORRECT, THUS WE BOTH NEGLECTED TO CHK THE NON COMMON PORTION TO JFK -- A KENNEBUNK ARR INSTEAD OF A PLYMM 4 ARR. OUR RTE WAS VERY SUBTLY DIFFERENT ENRTE TO A COMMON DSCNT POINT - - PROVIDENCE. ZBW QUERIED US ON OUR FLT PATH WHEN WE APPEARED TO BE SLIGHTLY OFF TRACK. HE CORRECTED OUR MISTAKE APPARENTLY WITHOUT PENALIZING THE CREW. THE SIT WAS POTENTIALLY HAZARDOUS SHOULD THESE HAVE BEEN OTHER TFC AS THERE OFTEN IS. WE BROKE A RULE OF THOROUGH CONFIRMATION AND THE LAPSE QUICKLY MADE ITSELF EVIDENT. IT FURTHER UNDERSCORES THE NEED TO CONFIRM ROUTING EACH TIME ONE CHANGES FREQ, ALT, AND ROUTINGS!

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.