Controller failed to issue amended IFR routing to air carrier X. Operational deviation.

Attributes
ACN	131324
Time
Date	198912
Day	Thu
Local Time Of Day	0601 To 1200
Place
Locale Reference	atc facility : orf
State Reference	VA
Altitude	msl bound lower : 23000 msl bound upper : 23000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : orf tower : bos
Operator	common carrier : air carrier
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Flight Phase	cruise other
Route In Use	enroute : direct
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : departure
Qualification	controller : radar
Experience	controller radar : 8
ASRS Report	131324
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Events
Anomaly	non adherence : published procedure
Independent Detector	other other : unspecified atc
Resolutory Action	none taken : detected after the fact
Consequence	faa : investigated
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Deviation

Narrative:

Air carrier X checked in on frequency level FL230, and I acknowledged him. During air carrier X's 10 min flight through my airspace, I was working approximately 8-10 other aircraft, including 3-4 flts of military fgt's recovering from the warning area to lfi. Air carrier X was handed off to ZDC. They accepted the handoff and I switched the frequency. About an hour later ZDC called and reported the air carrier X didn't get the proper routing. I had inadvertently overlooked an amended routing on the flight progress strip. When I had assumed control of the position earlier, the previous controller had already accepted the handoff on air carrier X, and the strip was on the active board. As soon as I sat down, it got busy and I never noticed the routing change. Also, I believe a contributing factor may have been an improper position relief briefing.

Original NASA ASRS Text

Title: CTLR FAILED TO ISSUE AMENDED IFR ROUTING TO ACR X. OPERATIONAL DEVIATION.

Narrative: ACR X CHKED IN ON FREQ LEVEL FL230, AND I ACKNOWLEDGED HIM. DURING ACR X'S 10 MIN FLT THROUGH MY AIRSPACE, I WAS WORKING APPROX 8-10 OTHER ACFT, INCLUDING 3-4 FLTS OF MIL FGT'S RECOVERING FROM THE WARNING AREA TO LFI. ACR X WAS HANDED OFF TO ZDC. THEY ACCEPTED THE HDOF AND I SWITCHED THE FREQ. ABOUT AN HR LATER ZDC CALLED AND RPTED THE ACR X DIDN'T GET THE PROPER ROUTING. I HAD INADVERTENTLY OVERLOOKED AN AMENDED ROUTING ON THE FLT PROGRESS STRIP. WHEN I HAD ASSUMED CTL OF THE POS EARLIER, THE PREVIOUS CTLR HAD ALREADY ACCEPTED THE HDOF ON ACR X, AND THE STRIP WAS ON THE ACTIVE BOARD. AS SOON AS I SAT DOWN, IT GOT BUSY AND I NEVER NOTICED THE ROUTING CHANGE. ALSO, I BELIEVE A CONTRIBUTING FACTOR MAY HAVE BEEN AN IMPROPER POS RELIEF BRIEFING.

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.