Narrative:

I filed IFR direct to avp at 9;000 ft and was cruising at that altitude. In contact with columbia approach I was advised by the columbia controller that I could stay at 9;000 and be routed around charlotte airspace or descend to 7;000 where 'they can handle you.' I descended to 7;000 and was handed off to the charlotte approach controller. This controller then issued me a radar vector almost 60 degrees off course to take me back the way I had come and around charlotte airspace to the west; and he made me hold off-course radar vectors for the better part of half an hour. When I asked when I could expect a more direct routing; another voice came on frequency and told me that I had to go around the charlotte airspace to accommodate arrivals and departures from clt. When I told him of the columbia controller's instructions to go to 7;000 for better handling by charlotte; this new voice (supervisor?) said something to the effect of 'yeah; we get that from those guys.'this circuitous routing added significant time to my flight; inconvenienced my passenger; and cut into my fuel reserves enough that; if it had persisted or had we not had decent weather at destination; it might well have compromised the safety of my flight.of additional note; this is not the only time I have been steered totally around charlotte airspace while IFR. It has happened repeatedly. I have also been denied transit when calling in VFR; on one occasion being made so late by the deviation that my destination field had closed for the air show I had planned to attend. I cannot fathom what charlotte's issue is with handling legitimate flights that don't happen to be landing at clt or within the charlotte class B veil; but if charlotte controllers intend to essentially close their airspace to transient GA aircraft; pilot education to that effect would be useful. Education to controllers in neighboring airspace sectors would also be very helpful.

Google
 

Original NASA ASRS Text

Title: An M20 pilot filed IFR to AVP expressed his displeasure when he was denied direct routing through the CLT Class B due to arrivals and departures.

Narrative: I filed IFR direct to AVP at 9;000 FT and was cruising at that altitude. In contact with Columbia Approach I was advised by the Columbia Controller that I could stay at 9;000 and be routed around Charlotte airspace or descend to 7;000 where 'they can handle you.' I descended to 7;000 and was handed off to the Charlotte Approach Controller. This Controller then issued me a radar vector almost 60 degrees off course to take me back the way I had come and around Charlotte airspace to the west; and he made me hold off-course radar vectors for the better part of half an hour. When I asked when I could expect a more direct routing; another voice came on frequency and told me that I had to go around the Charlotte airspace to accommodate arrivals and departures from CLT. When I told him of the Columbia Controller's instructions to go to 7;000 for better handling by Charlotte; this new voice (Supervisor?) said something to the effect of 'yeah; we get that from those guys.'This circuitous routing added significant time to my flight; inconvenienced my passenger; and cut into my fuel reserves enough that; if it had persisted or had we not had decent weather at destination; it might well have compromised the safety of my flight.Of additional note; this is not the only time I have been steered totally around Charlotte airspace while IFR. It has happened repeatedly. I have also been denied transit when calling in VFR; on one occasion being made so late by the deviation that my destination field had closed for the air show I had planned to attend. I cannot fathom what Charlotte's issue is with handling legitimate flights that don't happen to be landing at CLT or within the Charlotte Class B veil; but if Charlotte controllers intend to essentially close their airspace to transient GA aircraft; pilot education to that effect would be useful. Education to controllers in neighboring airspace sectors would also be very helpful.

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