Narrative:

Two parts to this event - filed IFR flt plan from ZZZ to clt via Majic1 arrival. Closest STAR available. A/C is GPS waas /G and ads-B equipped. ZZZ tower insisted on describing majic [intersection] in radial and bearing instead of using [intersection] name. After looking it up; I made no change in flt plan and after to was turned over to gso app. VFR and bumpy with light to occasional moderate. As soon as I checked on gso had a reroute: direct gants V409 locas. This really spiked the workload as I had to look everything up and load into GPS. Bright sun made it hard to see ipad where charts were displayed and turbulence made it difficult to program. Was heads down for several minutes with occasional glimpses outside and trying to fly; communicate and program. Single pilot ops deserve some consideration. Rest of the arrival was uneventful.later in the week; I had opportunity to speak with atl ATC rep who said it was likely due to LOA between gso and clt. There are several aspects to this that need systemic change. 1. ATC need to move from VHF descriptors to RNAV descriptors if the aircraft files /G. Don't describe intersections in [terms] of VOR and bearing/radials. Much more complex to translate for GPS units.2. If there's a preferred route then let's publicize them and that's what we'll file. It's easier for both ATC and pilots. I've been after the FAA for years to publicize all the loas and secret routes - most of them are not shown in the AFD - which very few people have anyway. The efb flight planners can give you an idea but why not go to the source.3. I understand that there will be changes but there was no runway change or convective weather involved.

Google
 

Original NASA ASRS Text

Title: BE36 pilot reported increased workload resulted when he was cleared on a different route than filed to CLT perhaps due to an LOA between GSO and CLT TRACONS.

Narrative: Two parts to this event - Filed IFR flt plan from ZZZ to CLT via Majic1 arrival. Closest STAR available. A/C is GPS WAAS /G and ADS-B equipped. ZZZ tower insisted on describing MAJIC [Intersection] in radial and bearing instead of using [intersection] name. After looking it up; I made no change in flt plan and after TO was turned over to GSO app. VFR and bumpy with light to occasional moderate. As soon as I checked on GSO had a reroute: Direct GANTS V409 LOCAS. This really spiked the workload as I had to look everything up and load into GPS. Bright sun made it hard to see iPad where charts were displayed and turbulence made it difficult to program. Was heads down for several minutes with occasional glimpses outside and trying to fly; communicate and program. Single pilot ops deserve some consideration. Rest of the arrival was uneventful.Later in the week; I had opportunity to speak with ATL ATC rep who said it was likely due to LOA between GSO and CLT. There are several aspects to this that need systemic change. 1. ATC need to move from VHF descriptors to RNAV descriptors if the aircraft files /G. Don't describe intersections in [terms] of VOR and bearing/radials. Much more complex to translate for GPS units.2. If there's a preferred route then let's publicize them and that's what we'll file. It's easier for both ATC and pilots. I've been after the FAA for years to publicize all the LOAs and secret routes - most of them are NOT shown in the AFD - which very few people have anyway. The EFB flight planners can give you an idea but why not go to the source.3. I understand that there will be changes but there was no runway change or convective weather involved.

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.