Narrative:

I was on an IFR flight plan under control of baltimore approach. ATC was waiting for an IFR departure off frederick before allowing me to descend further. I was at 4000 ft about 15 NM northeast of the airport when ATC issued a TA to me '...traffic 12 O'clock 1 mi opposite direction indicating 4000 ft...' several seconds later a passenger in the copilot seat saw a piper cherokee or similar headed right toward us head on. I dived to the left which upset several passenger. Apparently the other plane was VFR. The hazy condition and it's not using landing lights made it almost impossible to see. Mixed IFR and VFR traffic can be hazardous and this was an awfully close call. I even had on recognition lights but apparently the other traffic never saw me.

Google
 

Original NASA ASRS Text

Title: NMAC.

Narrative: I WAS ON AN IFR FLT PLAN UNDER CTL OF BALTIMORE APCH. ATC WAS WAITING FOR AN IFR DEP OFF FREDERICK BEFORE ALLOWING ME TO DSND FURTHER. I WAS AT 4000 FT ABOUT 15 NM NE OF THE ARPT WHEN ATC ISSUED A TA TO ME '...TFC 12 O'CLOCK 1 MI OPPOSITE DIRECTION INDICATING 4000 FT...' SEVERAL SECONDS LATER A PAX IN THE COPLT SEAT SAW A PIPER CHEROKEE OR SIMILAR HEADED RIGHT TOWARD US HEAD ON. I DIVED TO THE L WHICH UPSET SEVERAL PAX. APPARENTLY THE OTHER PLANE WAS VFR. THE HAZY CONDITION AND IT'S NOT USING LNDG LIGHTS MADE IT ALMOST IMPOSSIBLE TO SEE. MIXED IFR AND VFR TFC CAN BE HAZARDOUS AND THIS WAS AN AWFULLY CLOSE CALL. I EVEN HAD ON RECOGNITION LIGHTS BUT APPARENTLY THE OTHER TFC NEVER SAW ME.

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.