Pct controller experienced loss of separation during military fly-by operation.

Attributes
ACN	597440
Time
Date	200310
Day	Sat
Local Time Of Day	1201 To 1800
Place
Locale Reference	navaid : bal.vortac
State Reference	MD
Altitude	msl single value : 6000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : pct.tracon
Operator	general aviation : personal
Make Model Name	PA-44 Seminole Turbo Seminole
Flight Phase	cruise : level
Route In Use	enroute airway : v93.airway
Flight Plan	IFR
Aircraft 2
Controlling Facilities	tracon : pct.tracon
Make Model Name	Skyhawk 172/Cutlass 172
Flight Phase	cruise : level
Route In Use	enroute airway : v93.airway
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : approach
Qualification	controller : radar
Experience	controller radar : 22 controller time certified in position1 : 17 flight time total : 1000
ASRS Report	597440
Events
Anomaly	non adherence : required legal separation
Independent Detector	atc equipment : conflict alert other controllera
Resolutory Action	controller : issued new clearance flight crew : took evasive action
Consequence	faa : investigated
Supplementary
Problem Areas	Airspace Structure Aircraft ATC Human Performance
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Error

Narrative:

Aircraft #1 was established on V93 sebound. Aircraft #2 was established on LOA radials nwbound. Both aircraft were at 6000 ft. Local procedures put both aircraft opposite direction at the same altitude, and on intersecting paths. Heavy traffic in the sector, combined with a flight of F18's preparing to 'fly-by' the military took up too much of my attention. The F18's were IFR waiting for the 'fly-by' and I had difficulty finding somewhere to hold them. While attending to this, aircraft #1 and aircraft #2 came within close proximity of each other. Altitude for direction of flight is one of the most basic tools for separating aircraft. A procedure mandated by SOP that puts aircraft opposite direction at the same altitude is a major contributing factor. Additionally, the washington area ADIZ has caused more and more aircraft to file IFR, even though the WX is extremely VFR, out of pilot's fears of a violation. This has significantly increased the workload in this sector. I've been a pilot for 28 yrs and a controller for 22 yrs, and the havoc this ADIZ has brought to both flying, and ATC is unlike anything I've ever seen.

Original NASA ASRS Text

Title: PCT CTLR EXPERIENCED LOSS OF SEPARATION DURING MIL FLY-BY OP.

Narrative: ACFT #1 WAS ESTABLISHED ON V93 SEBOUND. ACFT #2 WAS ESTABLISHED ON LOA RADIALS NWBOUND. BOTH ACFT WERE AT 6000 FT. LCL PROCS PUT BOTH ACFT OPPOSITE DIRECTION AT THE SAME ALT, AND ON INTERSECTING PATHS. HVY TFC IN THE SECTOR, COMBINED WITH A FLT OF F18'S PREPARING TO 'FLY-BY' THE MIL TOOK UP TOO MUCH OF MY ATTN. THE F18'S WERE IFR WAITING FOR THE 'FLY-BY' AND I HAD DIFFICULTY FINDING SOMEWHERE TO HOLD THEM. WHILE ATTENDING TO THIS, ACFT #1 AND ACFT #2 CAME WITHIN CLOSE PROX OF EACH OTHER. ALT FOR DIRECTION OF FLT IS ONE OF THE MOST BASIC TOOLS FOR SEPARATING ACFT. A PROC MANDATED BY SOP THAT PUTS ACFT OPPOSITE DIRECTION AT THE SAME ALT IS A MAJOR CONTRIBUTING FACTOR. ADDITIONALLY, THE WASHINGTON AREA ADIZ HAS CAUSED MORE AND MORE ACFT TO FILE IFR, EVEN THOUGH THE WX IS EXTREMELY VFR, OUT OF PLT'S FEARS OF A VIOLATION. THIS HAS SIGNIFICANTLY INCREASED THE WORKLOAD IN THIS SECTOR. I'VE BEEN A PLT FOR 28 YRS AND A CTLR FOR 22 YRS, AND THE HAVOC THIS ADIZ HAS BROUGHT TO BOTH FLYING, AND ATC IS UNLIKE ANYTHING I'VE EVER SEEN.

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.