VFR PA32 with pct entered R-4001 while trying to avoid dc ADIZ.

Attributes
ACN	614965
Time
Date	200404
Day	Sat
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : bal.airport
State Reference	MD
Altitude	msl single value : 2400
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : pct.tracon
Operator	general aviation : personal
Make Model Name	PA-32 Cherokee Six/Lance/Saratoga
Operating Under FAR Part	Part 91
Navigation In Use	other
Flight Phase	cruise : level
Route In Use	enroute : on vectors
Flight Plan	VFR
Person 1
Affiliation	other
Function	flight crew : single pilot
Qualification	pilot : private
Experience	flight time last 90 days : 7 flight time total : 630 flight time type : 205
ASRS Report	614965
Person 2
Affiliation	government : faa
Function	controller : approach
Events
Anomaly	airspace violation : entry non adherence : published procedure non adherence : far
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance flight crew : exited penetrated airspace
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	Airspace Structure Flight Crew Human Performance ATC Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

ADIZ flight plans filed on 13.5 radial DME balance VOR, expecting southeast to esn as filed. Told by potomac approach to fly northeast, then told turn to north (360 degree heading), as I was in aberdeen space. I believed potomac approach was vectoring me around martin state and would send me southeast to easton as filed. Pct approach then sent me north around aberdeen and told me to call aberdeen when I landed (which I did). Upon return to leesburg (jyo), I went back to FSS and reported this matter to supervisor who said to file NASA report. Supervisor was disappointed that TRACON did not read the detailed comments in my ADIZ flight plan and said they should have vectored me to the southeast. I should have questioned the TRACON rather than think they were guiding me. My discussion with the supervisor of TRACON poses the question and need for clarification of, who is in control? Is it TRACON giving directives (general vectors such as fly northeast which is somewhere between 0-90 degrees) or the pilot with own navigation? Here the pilot, based on an extensive briefing from FSS, was thinking the TRACON was just vectoring me around martin state and back to southeast as my ADIZ flight plan specified. The question is whether the TRACON is aware of comments. The pilot thinks the TRACON is aware and trusts vectoring that contributes to a problem. Bottom line is pilot should question the TRACON and never assume.

Original NASA ASRS Text

Title: VFR PA32 WITH PCT ENTERED R-4001 WHILE TRYING TO AVOID DC ADIZ.

Narrative: ADIZ FLT PLANS FILED ON 13.5 RADIAL DME BAL VOR, EXPECTING SE TO ESN AS FILED. TOLD BY POTOMAC APCH TO FLY NE, THEN TOLD TURN TO N (360 DEG HDG), AS I WAS IN ABERDEEN SPACE. I BELIEVED POTOMAC APCH WAS VECTORING ME AROUND MARTIN STATE AND WOULD SEND ME SE TO EASTON AS FILED. PCT APCH THEN SENT ME N AROUND ABERDEEN AND TOLD ME TO CALL ABERDEEN WHEN I LANDED (WHICH I DID). UPON RETURN TO LEESBURG (JYO), I WENT BACK TO FSS AND RPTED THIS MATTER TO SUPVR WHO SAID TO FILE NASA RPT. SUPVR WAS DISAPPOINTED THAT TRACON DID NOT READ THE DETAILED COMMENTS IN MY ADIZ FLT PLAN AND SAID THEY SHOULD HAVE VECTORED ME TO THE SE. I SHOULD HAVE QUESTIONED THE TRACON RATHER THAN THINK THEY WERE GUIDING ME. MY DISCUSSION WITH THE SUPVR OF TRACON POSES THE QUESTION AND NEED FOR CLARIFICATION OF, WHO IS IN CTL? IS IT TRACON GIVING DIRECTIVES (GENERAL VECTORS SUCH AS FLY NE WHICH IS SOMEWHERE BTWN 0-90 DEGS) OR THE PLT WITH OWN NAV? HERE THE PLT, BASED ON AN EXTENSIVE BRIEFING FROM FSS, WAS THINKING THE TRACON WAS JUST VECTORING ME AROUND MARTIN STATE AND BACK TO SE AS MY ADIZ FLT PLAN SPECIFIED. THE QUESTION IS WHETHER THE TRACON IS AWARE OF COMMENTS. THE PLT THINKS THE TRACON IS AWARE AND TRUSTS VECTORING THAT CONTRIBUTES TO A PROB. BOTTOM LINE IS PLT SHOULD QUESTION THE TRACON AND NEVER ASSUME.

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.