Narrative:

Aircraft X was traveling northwest in a handoff status from ZTL unarm sector VFR at 11;500 ft. The route of flight had aircraft X on a flight path that would conflict with both the filpz and parqr arrival stream. When aircraft X checked on; I instructed aircraft X to maintain VFR at or below 5500 ft to avoid any conflict with clt traffic. I thought I heard 'roger'; but after 2-3 minutes realized that aircraft X was still at 11;500 ft.when I went back to question whether aircraft X was descending; they responded with 'unable'. I informed aircraft X the reason for the restriction was because of clt arrival traffic and again issued the 5;500 ft restriction; and they again said 'unable'. I told aircraft X 'turn left heading 330' to avoid filpz traffic; and they said unable. I said fly heading 270; they said unable again. I needed to coordinate with west arrival sector that aircraft X would be in their airspace in conflict with filpz traffic; and aircraft X began climbing. After I called traffic; aircraft X requested to cancel flight following. I said negative; remain this frequency due to the traffic in the area. I was concerned over what action aircraft X was taking to remain VFR - they were now turning on course.at this point aircraft X began asking for my 'name and badge number'. This took place at least 4 times. I kept focus on clt departure traffic and ignored the request. I gave aircraft X the phone number for the clt TRACON; and coordinated with ZTL moped that aircraft X was not complying with any traffic instructions. ZTL unarm should refrain from delivering VFR traffic at 11;500 ft when clt is landing south.

Related reports:

Google
 

Original NASA ASRS Text

Title: CLT TRACON Controller and a BE58 pilot reported a possible pilot deviation due to a communication breakdown near class Bravo airspace.

Narrative: Aircraft X was traveling Northwest in a handoff status from ZTL UNARM sector VFR at 11;500 ft. The route of flight had Aircraft X on a flight path that would conflict with both the FILPZ and PARQR arrival stream. When Aircraft X checked on; I instructed Aircraft X to maintain VFR at or below 5500 ft to avoid any conflict with CLT traffic. I thought I heard 'Roger'; but after 2-3 minutes realized that Aircraft X was still at 11;500 ft.When I went back to question whether Aircraft X was descending; they responded with 'unable'. I informed Aircraft X the reason for the restriction was because of CLT arrival traffic and again issued the 5;500 ft restriction; and they again said 'unable'. I told Aircraft X 'Turn left heading 330' to avoid FILPZ traffic; and they said unable. I said fly heading 270; they said unable again. I needed to coordinate with West Arrival sector that Aircraft X would be in their airspace in conflict with FILPZ traffic; and Aircraft X began climbing. After I called traffic; Aircraft X requested to cancel flight following. I said negative; remain this frequency due to the traffic in the area. I was concerned over what action Aircraft X was taking to remain VFR - they were now turning on course.At this point Aircraft X began asking for my 'name and badge number'. This took place at least 4 times. I kept focus on CLT departure traffic and ignored the request. I gave Aircraft X the phone number for the CLT TRACON; and coordinated with ZTL MOPED that Aircraft X was not complying with any traffic instructions. ZTL UNARM should refrain from delivering VFR traffic at 11;500 ft when CLT is landing south.

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.