Pilot flies into restr airspace possibly.

Attributes
ACN	309980
Time
Date	199507
Day	Wed
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : boi
State Reference	ID
Altitude	msl bound lower : 7000 msl bound upper : 9500
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : boi
Operator	general aviation : personal
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Operating Under FAR Part	Part 91
Flight Phase	climbout : intermediate altitude
Flight Plan	None
Person 1
Affiliation	Other
Function	flight crew : single pilot
ASRS Report	309080
Person 2
Affiliation	government : faa
Function	controller : departure
Qualification	controller : radar
Events
Anomaly	non adherence : far other anomaly other
Independent Detector	other other : unspecified cockpit
Resolutory Action	flight crew : exited adverse environment flight crew : exited penetrated airspace
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

Departed caldwell (U35) at XA30 mdt intending to fly through boi class C and proceed on the boi 093 degree radial for an initial leg to destination (den-bjc). Could not contact boi radar, and proceeded south to stay clear of class C, while climbing to 9500 ft and using the slc sectional chart landmarks for navigation. When well clear, assumed a heading of 75 degrees to gradually intercept boi 093 degree. At 9500 ft, noticed mountain home AFB ahead about 10 mi, and then noticed R-3203. First check of my IFR chart led me to see information for R-3203C which tops out at 6000 ft. Unable to determine what part of R-3203 is a or B, but assume a underlies B. I was unable to contact boi, or ZLC, and altered heading to 60 degrees to expedite departure from R-3203 boundaries. With no DME, exact position was not known. It is possible I was still west of the boundary. I knew before departure that my radios were intermittent, could receive ok but not transmit. Hence, my decision to proceed with no filed plan, and certainly no dependence on IFR assistance. Avoiding boi was my primary concern, and I failed to notice R-3203 until the class C problem was solved. I do not know if R-3203 was active.

Original NASA ASRS Text

Title: PLT FLIES INTO RESTR AIRSPACE POSSIBLY.

Narrative: DEPARTED CALDWELL (U35) AT XA30 MDT INTENDING TO FLY THROUGH BOI CLASS C AND PROCEED ON THE BOI 093 DEG RADIAL FOR AN INITIAL LEG TO DEST (DEN-BJC). COULD NOT CONTACT BOI RADAR, AND PROCEEDED S TO STAY CLR OF CLASS C, WHILE CLBING TO 9500 FT AND USING THE SLC SECTIONAL CHART LANDMARKS FOR NAV. WHEN WELL CLR, ASSUMED A HDG OF 75 DEGS TO GRADUALLY INTERCEPT BOI 093 DEG. AT 9500 FT, NOTICED MOUNTAIN HOME AFB AHEAD ABOUT 10 MI, AND THEN NOTICED R-3203. FIRST CHK OF MY IFR CHART LED ME TO SEE INFO FOR R-3203C WHICH TOPS OUT AT 6000 FT. UNABLE TO DETERMINE WHAT PART OF R-3203 IS A OR B, BUT ASSUME A UNDERLIES B. I WAS UNABLE TO CONTACT BOI, OR ZLC, AND ALTERED HDG TO 60 DEGS TO EXPEDITE DEP FROM R-3203 BOUNDARIES. WITH NO DME, EXACT POS WAS NOT KNOWN. IT IS POSSIBLE I WAS STILL W OF THE BOUNDARY. I KNEW BEFORE DEP THAT MY RADIOS WERE INTERMITTENT, COULD RECEIVE OK BUT NOT XMIT. HENCE, MY DECISION TO PROCEED WITH NO FILED PLAN, AND CERTAINLY NO DEPENDENCE ON IFR ASSISTANCE. AVOIDING BOI WAS MY PRIMARY CONCERN, AND I FAILED TO NOTICE R-3203 UNTIL THE CLASS C PROB WAS SOLVED. I DO NOT KNOW IF R-3203 WAS ACTIVE.

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.