K90 TRACON controller reported an unidentified VFR aircraft was a near midair collision with a VFR a...

Attributes
ACN	1498021
Time
Date	201711
Local Time Of Day	1201-1800
Place
Locale Reference	K90.TRACON
State Reference	MA
Environment
Flight Conditions	VMC
Aircraft 1
Make Model Name	Small Transport Low Wing 2 Recip Eng
Operating Under FAR Part	Part 135
Flight Phase	Cruise
Route In Use	VFR Route
Flight Plan	VFR
Aircraft 2
Make Model Name	Small Transport Low Wing 2 Recip Eng
Flight Phase	Cruise
Route In Use	None
Flight Plan	VFR
Person 1
Function	Approach
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Time Certified In Pos 1 (yrs) 2
Events
Anomaly	ATC Issue All Types Conflict NMAC Deviation - Procedural Other / Unknown

Narrative:

Aircraft X requested VFR flight following for a short flight from at 1;000 feet. The pilot had opposite direction VFR traffic indicating 800 feet. I issued the traffic at 8 miles. Aircraft X did not have the traffic in sight. The VFR aircraft indicated level at 800 feet so at 5 miles I reissued the traffic and suggested a VFR climb if not in sight. Aircraft X did not have the traffic in sight and executed a climb to 1;500 feet. At 3 miles; I reissued the traffic and advised the pilot that the targets appeared likely to merge. The pilot did not request a vector for the traffic. Aircraft X then reported the traffic in sight at his same altitude of 1;500 feet; and not at the indicated 800 feet. During the time both before and after the conflict; the VFR traffic showed single sweep altitude changes to altitudes of 1;200; 1;600; and 1;700 feet; very infrequently.I should have issued proactive vectors to de-conflict the traffic situation since both altitudes were not verified.

Original NASA ASRS Text

Title: K90 TRACON Controller reported an unidentified VFR aircraft was a NMAC with a VFR aircraft the Controller was working.

Narrative: Aircraft X requested VFR flight following for a short flight from at 1;000 feet. The pilot had opposite direction VFR traffic indicating 800 feet. I issued the traffic at 8 miles. Aircraft X did not have the traffic in sight. The VFR aircraft indicated level at 800 feet so at 5 miles I reissued the traffic and suggested a VFR climb if not in sight. Aircraft X did not have the traffic in sight and executed a climb to 1;500 feet. At 3 miles; I reissued the traffic and advised the pilot that the targets appeared likely to merge. The pilot did not request a vector for the traffic. Aircraft X then reported the traffic in sight at his same altitude of 1;500 feet; and not at the indicated 800 feet. During the time both before and after the conflict; the VFR traffic showed single sweep altitude changes to altitudes of 1;200; 1;600; and 1;700 feet; very infrequently.I should have issued proactive vectors to de-conflict the traffic situation since both altitudes were not verified.

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

K90 TRACON controller reported an unidentified VFR aircraft was a near midair collision with a VFR aircraft the controller was working.