Mci controller described class B incursion event that required intervention to maintain separation; ...

Narrative:

While working arrival radar; I noticed a VFR target from the mkc airport area climbing northwest bound into the class B airspace out of 3;000 ft. Tagged target with aircraft Y and observed it climbing up to 3;500 ft; still northwest bound. I had aircraft X on vector to final runway 1L at 3;000 ft; mkc called and advised they were talking to aircraft and descending. I advised them that aircraft needed to descend fast; I had aircraft X on vector to join final. I observed aircraft Y to turn southwest bound toward my aircraft X; I called traffic alert and vectored aircraft X away from target and then back to final north of aircraft Y. Aircraft Y continued southwest bound and descended below the class B airspace toward lwc. Advised flm (front line manager); who called and talked to mkc and got the aircraft call sign and possible destination. Recommendation; it appeared mkc gave aircraft a discrete code; if this is true; then mkc should always add in with code to remain outside of class B (which they might do). If aircraft was not on discrete code then they should try to advise VFR aircraft to remain outside of class B.

Original NASA ASRS Text

Title: MCI Controller described Class B incursion event that required intervention to maintain separation; reporter indicated that preceeding MCI Controller may have issued Class B clearance.

Narrative: While working Arrival RADAR; I noticed a VFR target from the MKC airport area climbing northwest bound into the Class B airspace out of 3;000 FT. Tagged target with Aircraft Y and observed it climbing up to 3;500 FT; still northwest bound. I had Aircraft X on vector to final Runway 1L at 3;000 FT; MKC called and advised they were talking to aircraft and descending. I advised them that aircraft needed to descend fast; I had Aircraft X on vector to join final. I observed Aircraft Y to turn southwest bound toward my Aircraft X; I called traffic alert and vectored Aircraft X away from target and then back to final north of Aircraft Y. Aircraft Y continued southwest bound and descended below the Class B airspace toward LWC. Advised FLM (Front Line Manager); who called and talked to MKC and got the aircraft call sign and possible destination. Recommendation; it appeared MKC gave aircraft a discrete code; if this is true; then MKC should always add in with code to remain outside of Class B (which they might do). If aircraft was not on discrete code then they should try to advise VFR aircraft to remain outside of Class B.

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.

Attributes
ACN	873167
Time
Date	201002
Local Time Of Day	1201-1800
Place
Locale Reference	MCI.TRACON
State Reference	MO
Aircraft 1
Make Model Name	Beech 1900
Flight Phase	Descent
Route In Use	Vectors
Flight Plan	IFR
Aircraft 2
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Flight Phase	Descent
Flight Plan	VFR
Person 1
Function	Approach
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types Airspace Violation All Types Deviation - Procedural FAR

Mci controller described class B incursion event that required intervention to maintain separation; reporter indicated that preceeding mci controller may have issued class B clearance.