Narrative:

While in a two scope configuration; normal north and south split; I was monitoring the operation as well as working the radar data position. Traffic was steady moderate in all sectors. While working on a different issue; I became alert to a situation happening in the new bedford sector; which I began to monitor more closely. Aircraft X had just canceled their IFR flight plan into pym airport. The controller instructed the pilot that their IFR cancellation was received by ATC and to keep the beacon code for flight following into pym. At this time; aircraft X was approximately 20 miles southwest of the airport. After approximately two minutes; aircraft X informed the controller they were entering a left base at pym and wanted to cancel flight following. The controller then instructed aircraft X to squawk 1200 and remain above 025 to remain clear of the ewb class D airspace. Aircraft X complied and radar service was terminated.the controller terminated the tag of aircraft X and continued to work when ewb tower called questioning an aircraft that was in their airspace. Aircraft X then returned to the radar controller's frequency while the controller and I were coordinating with ewb about what was going on. Aircraft X was never again radar identified but reported coming close to [another] aircraft multiple times after their termination of flight following. Aircraft X continued on to pym airport.after the event; we used the falcon to replay the event and discovered that after squawking 1200; aircraft X's target appeared to descend into ewb's class D surface area without authorization. The target came within 100 feet of another 1200 target. The target of aircraft X then appeared to overfly runway 32 and ewb before climbing again and calling the radar controller. It appeared that aircraft X had mistaken ewb airport for pym airport. Aircraft X never established radio communication with ewb tower.approximately 15 minutes after the event; FSS called the TRACON requesting a phone number for aircraft X to report a near midair collision. This number was given; however; the pilot never called. The flm (flight line manager) in the building was notified. The presumed near midair collision was between aircraft X and the 1200 target at ewb.one recommendation to prevent this event from happening would be to continue to track VFR targets that were receiving flight following until we can assure they are at the correct airport.

Related reports:

Google
 

Original NASA ASRS Text

Title: PVD TRACON Controller reported terminating a VFR aircraft when pilot reported airport insight; but pilot was at wrong airport and had an NMAC with another VFR aircraft.

Narrative: While in a two scope configuration; normal north and south split; I was monitoring the operation as well as working the radar data position. Traffic was steady moderate in all sectors. While working on a different issue; I became alert to a situation happening in the New Bedford sector; which I began to monitor more closely. Aircraft X had just canceled their IFR flight plan into PYM airport. The controller instructed the pilot that their IFR cancellation was received by ATC and to keep the beacon code for flight following into PYM. At this time; Aircraft X was approximately 20 miles southwest of the airport. After approximately two minutes; Aircraft X informed the controller they were entering a left base at PYM and wanted to cancel flight following. The controller then instructed Aircraft X to squawk 1200 and remain above 025 to remain clear of the EWB Class D airspace. Aircraft X complied and radar service was terminated.The controller terminated the tag of Aircraft X and continued to work when EWB tower called questioning an aircraft that was in their airspace. Aircraft X then returned to the radar controller's frequency while the controller and I were coordinating with EWB about what was going on. Aircraft X was never again radar identified but reported coming close to [another] aircraft multiple times after their termination of flight following. Aircraft X continued on to PYM airport.After the event; we used the Falcon to replay the event and discovered that after squawking 1200; Aircraft X's target appeared to descend into EWB's class D surface area without authorization. The target came within 100 feet of another 1200 target. The target of Aircraft X then appeared to overfly Runway 32 and EWB before climbing again and calling the radar controller. It appeared that Aircraft X had mistaken EWB airport for PYM airport. Aircraft X never established radio communication with EWB tower.Approximately 15 minutes after the event; FSS called the TRACON requesting a phone number for Aircraft X to report a NMAC. This number was given; however; the pilot never called. The FLM (Flight Line Manager) in the building was notified. The presumed NMAC was between Aircraft X and the 1200 target at EWB.One recommendation to prevent this event from happening would be to continue to track VFR targets that were receiving flight following until we can assure they are at the correct airport.

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.