Pct controller experienced a loss of separation event when failing to note the incorrect runway assi...

Narrative:

I was working iadfc combined with iadfe and iadfw. Arrival aircraft crj-900 from barin in the scratchpad said runway 19L so I planned for crj-900 to be number 1 for 19L. GLF2 was on a right base for runway 19C. When I cleared crj-900 for the visual approach to runway 19L; the pilot advised me that he was assigned runway 19C which was conflicting with the scratch pad information. Since he was already on a base turn only about 6 miles out I did not want to change his runway to the runway that was indicated on his scratchpad and that I was vectoring for; so I amended his heading to pass behind GLF2 and turned the aircraft to a 170 degree heading to join the final for runway 19C. He then saw the airfield and I proceeded to clear him for the approach. Crj-900 saw GLF2 but I did not say 'maintain visual separation' because I thought I had enough divergence and I was gonna bring him through the localizer and bring crj-900 back around to give him plenty of room to follow GLF2. Since I did not say 'maintain visual separation'; I lost separation because I did not quite have 45 degrees opposite course divergence separation. Ensure scratch pad information matches with the runway you assign. Possibly even restate the runway assignment when the aircraft checks in with the final approach controller.

Original NASA ASRS Text

Title: PCT Controller experienced a loss of separation event when failing to note the incorrect runway assignment scratchpad information in the data block.

Narrative: I was working IADFC combined with IADFE and IADFW. Arrival aircraft CRJ-900 from BARIN in the scratchpad said Runway 19L so I planned for CRJ-900 to be number 1 for 19L. GLF2 was on a right base for Runway 19C. When I cleared CRJ-900 for the visual approach to Runway 19L; the pilot advised me that he was assigned Runway 19C which was conflicting with the scratch pad information. Since he was already on a base turn only about 6 miles out I did not want to change his runway to the runway that was indicated on his scratchpad and that I was vectoring for; so I amended his heading to pass behind GLF2 and turned the aircraft to a 170 degree heading to join the final for Runway 19C. He then saw the airfield and I proceeded to clear him for the approach. CRJ-900 saw GLF2 but I did not say 'maintain visual separation' because I thought I had enough divergence and I was gonna bring him through the localizer and bring CRJ-900 back around to give him plenty of room to follow GLF2. Since I did not say 'maintain visual separation'; I lost separation because I did not quite have 45 degrees opposite course divergence separation. Ensure scratch pad information matches with the runway you assign. Possibly even restate the runway assignment when the aircraft checks in with the Final Approach Controller.

Data retrieved from NASA's ASRS site as of July 2013 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.

Attributes
ACN	1049813
Time
Date	201211
Local Time Of Day	0001-0600
Place
Locale Reference	PCT.TRACON
State Reference	VA
Aircraft 1
Make Model Name	Regional Jet 900 (CRJ900)
Operating Under FAR Part	Part 121
Flight Phase	Final Approach
Route In Use	Vectors
Flight Plan	IFR
Aircraft 2
Make Model Name	Gulfstream II (G1159)
Flight Phase	Final Approach
Route In Use	Visual Approach
Flight Plan	IFR
Person 1
Function	Approach Departure
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types Deviation - Procedural Published Material / Policy

Pct controller experienced a loss of separation event when failing to note the incorrect runway assignment scratchpad information in the data block.