Poor handling by pvd may have led small aircraft to enter bos TCA without clearance.

Attributes
ACN	163132
Time
Date	199011
Day	Wed
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : pvd airport : bed
State Reference	RI
Altitude	msl bound lower : 5500 msl bound upper : 5500
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : bos tracon : pvd tower : bdr
Operator	general aviation : personal
Make Model Name	Small Aircraft, High Wing, 1 Eng, Retractable Gear
Flight Phase	cruise other
Route In Use	enroute : on vectors
Flight Plan	None
Person 1
Affiliation	Other
Function	flight crew : single pilot
Qualification	pilot : private
Experience	flight time last 90 days : 25 flight time total : 3000
ASRS Report	163132
Person 2
Affiliation	government : faa
Function	controller : approach
Qualification	controller : radar
Events
Anomaly	non adherence : far non adherence other other anomaly other
Independent Detector	other flight crewa
Resolutory Action	none taken : unable
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation other
Situations
ATC Facility	procedure or policy : unspecified

Narrative:

Routine flight to bedford from bi over providence arsa at 5500'. I always call ocean approach for VFR advisories above the pvd arsa. Planned ground track was bid direct pvd, pvd 025 degree right outbnd to the framingham, ma, area where a descent into bedford would put me well below the 4000' floor of the boston TCA. On this flight however, the ocean approach controller gave me a 045 degree heading request to 'avoid an impending departure from pvd', when I was about 10 mi north of pvd. Even though I pointed out that I was with ocean approach for VFR advisories above the arsa, the controller was adamant about the vector. I was never told to 'resume own navigation.' after a few mins passed and I began to approach the boston TCA near mansfield, I called ocean and asked for a handoff to boston approach for a TCA clearance. There was another delay and then ocean approach said 'squawk 1200, frequency changed approved.' this left me near, or in, the boston TCA west/O a clearance. Although I knew that ocean did not have the authority to vector me outside the arsa, my cooperation with them may have caused me to violate controled airspace. How can I avoid this in the future?

Original NASA ASRS Text

Title: POOR HANDLING BY PVD MAY HAVE LED SMA TO ENTER BOS TCA WITHOUT CLRNC.

Narrative: ROUTINE FLT TO BEDFORD FROM BI OVER PROVIDENCE ARSA AT 5500'. I ALWAYS CALL OCEAN APCH FOR VFR ADVISORIES ABOVE THE PVD ARSA. PLANNED GND TRACK WAS BID DIRECT PVD, PVD 025 DEG R OUTBND TO THE FRAMINGHAM, MA, AREA WHERE A DSNT INTO BEDFORD WOULD PUT ME WELL BELOW THE 4000' FLOOR OF THE BOSTON TCA. ON THIS FLT HOWEVER, THE OCEAN APCH CTLR GAVE ME A 045 DEG HDG REQUEST TO 'AVOID AN IMPENDING DEP FROM PVD', WHEN I WAS ABOUT 10 MI N OF PVD. EVEN THOUGH I POINTED OUT THAT I WAS WITH OCEAN APCH FOR VFR ADVISORIES ABOVE THE ARSA, THE CTLR WAS ADAMANT ABOUT THE VECTOR. I WAS NEVER TOLD TO 'RESUME OWN NAV.' AFTER A FEW MINS PASSED AND I BEGAN TO APCH THE BOSTON TCA NEAR MANSFIELD, I CALLED OCEAN AND ASKED FOR A HDOF TO BOSTON APCH FOR A TCA CLRNC. THERE WAS ANOTHER DELAY AND THEN OCEAN APCH SAID 'SQUAWK 1200, FREQ CHANGED APPROVED.' THIS LEFT ME NEAR, OR IN, THE BOSTON TCA W/O A CLRNC. ALTHOUGH I KNEW THAT OCEAN DID NOT HAVE THE AUTHORITY TO VECTOR ME OUTSIDE THE ARSA, MY COOPERATION WITH THEM MAY HAVE CAUSED ME TO VIOLATE CTLED AIRSPACE. HOW CAN I AVOID THIS IN THE FUTURE?

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.