MU2 first officer believes that an ongoing feud between controllers and certain pilots is leading to...

Narrative:

Upon being cleared for a visual approach to the active runway we were vectored to intercept the final south of the FAF for noise abatement. We were then vectored to the south to make room for a B737 approaching from the southwest. At this point the captain (pilot not flying) became concerned; as it seemed that the airliner (B737) was receiving priority handling and we were being vectored unnecessarily. He asked the approach controller if it would be easier for them if we canceled IFR so we could proceed direct. We were promptly told that it would not make a difference and that he would have to sequence us the same no matter what. The captain then requested a phone number in order to ask the approach supervisor to discuss the arrival once on the ground. The flight then made an uneventful approach and landing. Upon speaking with the supervisor on the phone; he accused us of not using our proper call sign; not using proper phraseology; interrupting other aircraft communications; and hogging the frequency. The captain requested that the supervisor pull the tapes in order to prove that we had not done any of what was accused. The only extra communications we made with the approach controller was to offer up canceling IFR and to ask for the telephone number in order to speak with a supervisor after the flight. The frequency was not busy; with no more than three aircraft on at the time.we share a similar sounding tail number with a neighboring flight department that has been known; in the past; to query controllers. I believe that due to this; the supervisor handled an innocent question gruffly. This is not the first time we have been vectored like this during our approach into this airport and have been told by other pilots who are based there that they have encountered the same situation. I feel that we were unjustly accused of improper radio usage and that tension between controllers and pilots on the ground will cause tension in the terminal area adding stress to an already high workload/stressful phase of flight. I think that pilots and controllers need to put themselves in each other shoes to understand both sides of the operation. As a relative 'new guy'; I also believe that old grudges between certain pilots and controllers need to be left on the ground.

Original NASA ASRS Text

Title: MU2 First Officer believes that an ongoing feud between Controllers and certain pilots is leading to arrival delays and an unsafe working environment.

Narrative: Upon being cleared for a visual approach to the active runway we were vectored to intercept the final south of the FAF for noise abatement. We were then vectored to the south to make room for a B737 approaching from the southwest. At this point the Captain (pilot not flying) became concerned; as it seemed that the airliner (B737) was receiving priority handling and we were being vectored unnecessarily. He asked the Approach Controller if it would be easier for them if we canceled IFR so we could proceed direct. We were promptly told that it would not make a difference and that he would have to sequence us the same no matter what. The Captain then requested a phone number in order to ask the Approach Supervisor to discuss the arrival once on the ground. The flight then made an uneventful approach and landing. Upon speaking with the supervisor on the phone; he accused us of not using our proper call sign; not using proper phraseology; interrupting other aircraft communications; and hogging the frequency. The Captain requested that the supervisor pull the tapes in order to prove that we had NOT done any of what was accused. The only extra communications we made with the Approach Controller was to offer up canceling IFR and to ask for the telephone number in order to speak with a supervisor after the flight. The frequency was not busy; with no more than three aircraft on at the time.We share a similar sounding tail number with a neighboring flight department that has been known; in the past; to query controllers. I believe that due to this; the supervisor handled an innocent question gruffly. This is not the first time we have been vectored like this during our approach into this airport and have been told by other pilots who are based there that they have encountered the same situation. I feel that we were unjustly accused of improper radio usage and that tension between controllers and pilots on the ground will cause tension in the terminal area adding stress to an already high workload/stressful phase of flight. I think that pilots and controllers need to put themselves in each other shoes to understand both sides of the operation. As a relative 'New Guy'; I also believe that old grudges between certain pilots and controllers need to be left on the ground.

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.

Attributes
ACN	1019602
Time
Date	201206
Local Time Of Day	1201-1800
Place
Locale Reference	A90.TRACON
State Reference	NH
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	MU-2
Operating Under FAR Part	Part 91
Flight Phase	Final Approach
Route In Use	Visual Approach
Flight Plan	IFR
Person 1
Function	First Officer Pilot Flying
Qualification	Flight Crew Commercial Flight Crew Instrument Flight Crew Multiengine
Experience	Flight Crew Last 90 Days 75 Flight Crew Total 610 Flight Crew Type 290
Events
Anomaly	ATC Issue All Types Deviation - Procedural Other / Unknown

MU2 first officer believes that an ongoing feud between controllers and certain pilots is leading to arrival delays and an unsafe working environment.