Wrong routing loaded into the omega.

Attributes
ACN	302280
Time
Date	199504
Day	Tue
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : yql
State Reference	NS
Altitude	msl bound lower : 35000 msl bound upper : 35000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : czqm
Operator	common carrier : air carrier
Make Model Name	Commercial Fixed Wing
Operating Under FAR Part	Part 121
Navigation In Use	Other
Flight Phase	cruise other
Route In Use	enroute : other oceanic enroute : atlantic
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : commercial pilot : instrument pilot : flight engineer pilot : atp
Experience	flight time last 90 days : 198 flight time total : 6460 flight time type : 5000
ASRS Report	302280
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : instrument pilot : flight engineer pilot : commercial pilot : atp
Experience	flight time last 90 days : 200 flight time total : 7000 flight time type : 1800
ASRS Report	303001
Events
Anomaly	non adherence : clearance other anomaly other 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:

Leaving nat track C, gander cleared us na route 122. Flight plan had na 128. My copilot looked up na 122 and called off the new waypoints while I loaded them in our omega navigation units checking the position of the intersection on our navigation chart. When approximately 10 mi from tusky intersection, moncton asked 'are you proceeding to allex?' I said 'no, we were reclred na 122 and are now over tusky.' moncton then handed us off to ZBW who also asked if we were going to allex. After telling him we were over tusky, he gave us a squawk code, and after identify, cleared us direct to pvd, plymm 4 arrival jfk. Because I had failed to double-check the new routing when it was assigned, I told my first officer 'let's check the book again and verify na 122.' it was here we discovered our error. We had loaded na 120. Both rtes are the same out of cymon to brigg, then na 122 goes to allex and na 120 goes to tusky. Although my first officer had made the mistake of misreading the lines in the book, I feel the cause is my failure to verify the proper routing before loading into the navigation equipment.

Original NASA ASRS Text

Title: WRONG ROUTING LOADED INTO THE OMEGA.

Narrative: LEAVING NAT TRACK C, GANDER CLRED US NA RTE 122. FLT PLAN HAD NA 128. MY COPLT LOOKED UP NA 122 AND CALLED OFF THE NEW WAYPOINTS WHILE I LOADED THEM IN OUR OMEGA NAV UNITS CHKING THE POS OF THE INTXN ON OUR NAV CHART. WHEN APPROX 10 MI FROM TUSKY INTXN, MONCTON ASKED 'ARE YOU PROCEEDING TO ALLEX?' I SAID 'NO, WE WERE RECLRED NA 122 AND ARE NOW OVER TUSKY.' MONCTON THEN HANDED US OFF TO ZBW WHO ALSO ASKED IF WE WERE GOING TO ALLEX. AFTER TELLING HIM WE WERE OVER TUSKY, HE GAVE US A SQUAWK CODE, AND AFTER IDENT, CLRED US DIRECT TO PVD, PLYMM 4 ARR JFK. BECAUSE I HAD FAILED TO DOUBLE-CHK THE NEW ROUTING WHEN IT WAS ASSIGNED, I TOLD MY FO 'LET'S CHK THE BOOK AGAIN AND VERIFY NA 122.' IT WAS HERE WE DISCOVERED OUR ERROR. WE HAD LOADED NA 120. BOTH RTES ARE THE SAME OUT OF CYMON TO BRIGG, THEN NA 122 GOES TO ALLEX AND NA 120 GOES TO TUSKY. ALTHOUGH MY FO HAD MADE THE MISTAKE OF MISREADING THE LINES IN THE BOOK, I FEEL THE CAUSE IS MY FAILURE TO VERIFY THE PROPER ROUTING BEFORE LOADING INTO THE NAV EQUIP.

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.