PA28 pilot challenges K90 controller's response to multiple call-ups after frequency change from pvd...

Attributes
ACN	518317
Time
Date	200107
Day	Thu
Local Time Of Day	1201 To 1800
Place
Locale Reference	navaid : mvy.vor
State Reference	MA
Altitude	msl single value : 5000
Environment
Flight Conditions	IMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : k90.tracon tracon : pvd.tracon tracon : azo.tracon
Operator	general aviation : personal
Make Model Name	PA-28 Cherokee/Archer II/Dakota/Pillan/Warrior
Operating Under FAR Part	Part 91
Flight Phase	cruise : level
Person 1
Affiliation	other
Function	flight crew : single pilot
Qualification	pilot : atp pilot : commercial pilot : instrument pilot : multi engine pilot : cfi
Experience	flight time last 90 days : 25 flight time total : 2600 flight time type : 1200
ASRS Report	518317
Person 2
Affiliation	government : faa
Function	controller : approach
Events
Anomaly	non adherence : published procedure
Independent Detector	other flight crewa
Resolutory Action	none taken : anomaly accepted
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	ATC Human Performance
Primary Problem	ATC Human Performance

Narrative:

IFR to mvy. Pvd approach handed me off to cape approach at 5000 ft. I checked in 'cape n-number 5000 ft, with ATIS information.' no reply. Waited 30-40 seconds. Checked in again. Controller 'barked at me' about stepping on someone. I replied that I did not, and if he is working 2 frequencys, then there is no way for me to know that. He said to listen up, to which I replied I was just handed off, so obviously whatever he broadcast wasn't available on a different sector's frequency. After descending me to the approach, he apologized and I said no problem. After I made my remarks to his false accusations, he then began to key the military on this frequency, while talking on another (which I suspect was the military frequency). Solution: when controllers work more than 1 frequency, they should key the military on all so that aircraft have a clue about it. How else would one otherwise know? It seems lately that every other time I fly, I must fill out one of these reports, because someone gets 'mouthing' when they are wrong!

Original NASA ASRS Text

Title: PA28 PLT CHALLENGES K90 CTLR'S RESPONSE TO MULTIPLE CALL-UPS AFTER FREQ CHANGE FROM PVD TRACON.

Narrative: IFR TO MVY. PVD APCH HANDED ME OFF TO CAPE APCH AT 5000 FT. I CHKED IN 'CAPE N-NUMBER 5000 FT, WITH ATIS INFO.' NO REPLY. WAITED 30-40 SECONDS. CHKED IN AGAIN. CTLR 'BARKED AT ME' ABOUT STEPPING ON SOMEONE. I REPLIED THAT I DID NOT, AND IF HE IS WORKING 2 FREQS, THEN THERE IS NO WAY FOR ME TO KNOW THAT. HE SAID TO LISTEN UP, TO WHICH I REPLIED I WAS JUST HANDED OFF, SO OBVIOUSLY WHATEVER HE BROADCAST WASN'T AVAILABLE ON A DIFFERENT SECTOR'S FREQ. AFTER DSNDING ME TO THE APCH, HE APOLOGIZED AND I SAID NO PROB. AFTER I MADE MY REMARKS TO HIS FALSE ACCUSATIONS, HE THEN BEGAN TO KEY THE MIL ON THIS FREQ, WHILE TALKING ON ANOTHER (WHICH I SUSPECT WAS THE MIL FREQ). SOLUTION: WHEN CTLRS WORK MORE THAN 1 FREQ, THEY SHOULD KEY THE MIL ON ALL SO THAT ACFT HAVE A CLUE ABOUT IT. HOW ELSE WOULD ONE OTHERWISE KNOW? IT SEEMS LATELY THAT EVERY OTHER TIME I FLY, I MUST FILL OUT ONE OF THESE RPTS, BECAUSE SOMEONE GETS 'MOUTHING' WHEN THEY ARE WRONG!

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

PA28 pilot challenges K90 controller's response to multiple call-ups after frequency change from pvd TRACON.