A90 TRACON Controller reported possible automation issues and training deficiencies affecting communication with Providence Approach.

Date: 2022-10 · Aircraft: Medium Transport; High Wing; 2 Turboprop Eng · Phase: cruise

Anomalies: atc-issue-all-types|deviation-discrepancy-procedural-published-material-policy

Synopsis

A90 TRACON Controller reported possible automation issues and training deficiencies affecting communication with Providence Approach.

Narrative

I took the handoff on Aircraft X from PVD Approach. The tag appeared VFR; Aircraft X was level at 3;000 feet and the destination in the scratchpad was advertising VMC conditions. A few minutes after the initial check-in; the pilot of Aircraft X inquired as to whether PVD gave them an IFR clearance or not. I told the pilot that the info I had on the aircraft was that they were VFR; and I would work out an IFR clearance; since the aircraft was not in my airspace yet. When I called PVD Approach to coordinate an IFR clearance on Aircraft X; the controller who answered the line indicated that Aircraft X was already IFR. I informed the controller that the aircraft appeared IFR on my side. I proceeded to (re) issue an IFR clearance for clarification sake to the pilot. A full route printout from the FDIO on the beacon code yielded a VFR altitude on Aircraft X.I am probably biased in saying this; but I feel this has happened multiple times with aircraft from PVD approach in recent months. It is possible there is some automation issue between our two facilities. However; more likely is there is a knowledge/expectation gap that the PVD controllers have with the capabilities of STARS and data transfer between the two systems. Some training on their side may be helpful.

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.