Narrative:

I was working finals; light traffic as I recall. I had B717 on a right base for 33L into bwi at 030. He was approximately ten miles southeast of the airport and reported the field in sight. I cleared him for the visual to 33L and switched him to the tower. Meantime; a VFR; sfra only aircraft on a Z tag was flying underneath the class B; as they always are; inbound to fme from the east. He was flying under the 1;500 ft shelf; but at one point indicated 1;500. He's 'supposed to be 1;499 or less'; which is ridiculous in itself. The sfra aircraft then entered the bwi surface area. I also believe while inbound on the visual the B717 pilot descended beneath the class B. They both end up getting in a close proximity inside the surface area. As they got close; I called the sfra controller who said he was issuing traffic. The B717 had a TCAS and climbed. Recommendation; for one; the sfra position is set up for a controller to take a lot of heat should something go wrong. The rules are incredibly vague. The aircraft are not receiving flight following. However; if there was a collision; you can bet the first person to be blamed for the pilots not 'seeing and avoiding' like they're supposed to; would be the guy sitting at the scope. For this incident; the SR22 pilot violated the class B and in a big way. The B717 pilot descended below to the bravo; putting himself at risk. I was not talking to either aircraft; but had I been working the sfra position. Not much I would have done differently. The VFR aircraft run the boundaries as close as they can every single day. For them to be permitted to run the very edge of the bravo airspace by one foot vertically and horizontally is asking for trouble. To then criticize the controller for not predicting he would bust into the class B is even more ridiculous. Two pilots did something they weren't supposed to do; thus causing this problem. We can't fly the planes too.

Related reports:

Google
 

Original NASA ASRS Text

Title: PCT Controller working arrivals into BWI described a conflict event between an air carrier on a visual approach and a VFR aircraft that entered Class B.

Narrative: I was working finals; light traffic as I recall. I had B717 on a right base for 33L into BWI at 030. He was approximately ten miles southeast of the airport and reported the field in sight. I cleared him for the visual to 33L and switched him to the Tower. Meantime; a VFR; SFRA only aircraft on a Z tag was flying underneath the Class B; as they always are; inbound to FME from the east. He was flying under the 1;500 FT shelf; but at one point indicated 1;500. He's 'supposed to be 1;499 or less'; which is ridiculous in itself. The SFRA aircraft then entered the BWI surface area. I also believe while inbound on the visual the B717 pilot descended beneath the Class B. They both end up getting in a close proximity inside the surface area. As they got close; I called the SFRA Controller who said he was issuing traffic. The B717 had a TCAS and climbed. Recommendation; for one; the SFRA position is set up for a Controller to take a lot of heat should something go wrong. The rules are incredibly vague. The aircraft are not receiving flight following. However; if there was a collision; you can bet the first person to be blamed for the pilots not 'seeing and avoiding' like they're supposed to; would be the guy sitting at the scope. For this incident; the SR22 pilot violated the Class B and in a big way. The B717 pilot descended below to the Bravo; putting himself at risk. I was not talking to either aircraft; but had I been working the SFRA position. Not much I would have done differently. The VFR aircraft run the boundaries as close as they can every single day. For them to be permitted to run the very edge of the Bravo airspace by one foot vertically and horizontally is asking for trouble. To then criticize the Controller for not predicting he would bust into the Class B is even more ridiculous. Two pilots did something they weren't supposed to do; thus causing this problem. We can't fly the planes too.

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