Narrative:

Background: my home airport hef is within the tfr ADIZ now surrounding the national capital. This requires all VFR flts, even in the traffic pattern, to have an assigned transponder code. Flts beyond the traffic pattern require: a flight plan filed with FSS and en route control by pct departure/approach control. I filed with jyo FSS a VFR flight plan direct the 12 miles from hef north to jyo, 12 miles away, while skirting the western side of iad class B airspace innermost seven mile ring, which begins at the surface. How the problem arose: hef ground control assigned a transponder code and departure control frequency, and said to expect from pct departure after takeoff south of runway 16L, an initial vector west (wsw) toward casanova VORTAC. I took off with transponder and altitude encoder on and climbed out on runway heading to 1500 ft MSL with receivers tuned to pct departure as well as to hef tower. I wedged in an initial contact amongst pct's rapid communications with multiple traffic, but heard no reply. How it was discovered: suddenly, pct blared that I was approaching a restr area (R-6608B a six miles south) and to turn immediately north. Contributing factors: as hef tower gave no permission to turn west after takeoff, I kept runway heading. Being in an ADIZ under departure's control, I awaited the expected instruction to turn west. I had already been told by hef ground control that I would receive vectors, rather than conducting my own VFR navigation closer to yet beneath the dulles class B airspace en route to jyo. Corrective actions: I immediately turned north when so instructed by pct. In future, I will clarify with tower before south departures that I need to maneuver to avoid the restr area should I not receive timely vectors from pct. Rest of the brief flight: departure/approach control then vectored me west around dulles class B third ring (15 NM), until I was wnw of jyo, and thence vectored me until three miles nwn of jyo.

Related reports:

Google
 

Original NASA ASRS Text

Title: DUE TO FREQUENCY SATURATION, THE RPTR FOLLOWED ADIZ PROCS TO THE BEST OF HIS ABILITY, NEARLY ENTERED A RESTR AREA DUE TO HIS INABILITY TO ESTABLISH COMS WITH PCT TRACON.

Narrative: BACKGROUND: MY HOME ARPT HEF IS WITHIN THE TFR ADIZ NOW SURROUNDING THE NATIONAL CAPITAL. THIS REQUIRES ALL VFR FLTS, EVEN IN THE TFC PATTERN, TO HAVE AN ASSIGNED XPONDER CODE. FLTS BEYOND THE TFC PATTERN REQUIRE: A FLT PLAN FILED WITH FSS AND ENRTE CTL BY PCT DEP/APCH CTL. I FILED WITH JYO FSS A VFR FLT PLAN DIRECT THE 12 MILES FROM HEF N TO JYO, 12 MILES AWAY, WHILE SKIRTING THE WESTERN SIDE OF IAD CLASS B AIRSPACE INNERMOST SEVEN MILE RING, WHICH BEGINS AT THE SURFACE. HOW THE PROBLEM AROSE: HEF GND CTL ASSIGNED A XPONDER CODE AND DEP CTL FREQUENCY, AND SAID TO EXPECT FROM PCT DEP AFTER TKOF S OF RWY 16L, AN INITIAL VECTOR W (WSW) TOWARD CASANOVA VORTAC. I TOOK OFF WITH XPONDER AND ALT ENCODER ON AND CLIMBED OUT ON RWY HDG TO 1500 FT MSL WITH RECEIVERS TUNED TO PCT DEP AS WELL AS TO HEF TWR. I WEDGED IN AN INITIAL CONTACT AMONGST PCT'S RAPID COMS WITH MULTIPLE TFC, BUT HEARD NO REPLY. HOW IT WAS DISCOVERED: SUDDENLY, PCT BLARED THAT I WAS APCHING A RESTR AREA (R-6608B A SIX MILES S) AND TO TURN IMMEDIATELY N. CONTRIBUTING FACTORS: AS HEF TWR GAVE NO PERMISSION TO TURN W AFTER TKOF, I KEPT RWY HDG. BEING IN AN ADIZ UNDER DEP'S CTL, I AWAITED THE EXPECTED INSTRUCTION TO TURN W. I HAD ALREADY BEEN TOLD BY HEF GND CTL THAT I WOULD RECEIVE VECTORS, RATHER THAN CONDUCTING MY OWN VFR NAVIGATION CLOSER TO YET BENEATH THE DULLES CLASS B AIRSPACE ENRTE TO JYO. CORRECTIVE ACTIONS: I IMMEDIATELY TURNED N WHEN SO INSTRUCTED BY PCT. IN FUTURE, I WILL CLARIFY WITH TWR BEFORE S DEPS THAT I NEED TO MANEUVER TO AVOID THE RESTR AREA SHOULD I NOT RECEIVE TIMELY VECTORS FROM PCT. REST OF THE BRIEF FLT: DEP/APCH CTL THEN VECTORED ME W AROUND DULLES CLASS B THIRD RING (15 NM), UNTIL I WAS WNW OF JYO, AND THENCE VECTORED ME UNTIL THREE MILES NWN OF JYO.

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.