Navigation error results in uncoordinated penetration of airspace.

Attributes
ACN	122884
Time
Date	198909
Day	Tue
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : sfo airport : sql
State Reference	CA
Altitude	msl bound lower : 3000 msl bound upper : 3000
Environment
Flight Conditions	Mixed
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : oak
Operator	general aviation : personal
Make Model Name	Small Aircraft, High Wing, 1 Eng, Fixed Gear
Flight Phase	cruise other cruise other
Route In Use	enroute other
Flight Plan	None
Person 1
Affiliation	Other
Function	flight crew : single pilot
Qualification	pilot : cfi pilot : instrument pilot : commercial
Experience	flight time last 90 days : 18 flight time total : 700 flight time type : 150
ASRS Report	122884
Person 2
Affiliation	government : faa
Function	controller : approach
Qualification	controller : radar
Events
Anomaly	inflight encounter : weather non adherence : far other anomaly other
Independent Detector	other flight crewa
Resolutory Action	flight crew : returned to intended course or assigned course flight crew : exited penetrated airspace
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

Routine flight: returning small aircraft to its home base at haf. Departed clear (VFR) sql on a bay meadow departure. I could see clouds peeking over the coastal hills--not a good sign for VFR arrival at haf. Over the pass in the coastal hills, I got the WX from haf unicom: 'ceiling 1800 and dropping, runway 30 recommended.' I flew RNAV to the airport at 3000' looking for a hole--nothing. I then called bay approach to air file for RNAV-a to haf. Nearing haf, I called up bay, who informed me that the RNAV-a approach had been notamed as unusable. I then turned around and headed for sql. In a few seconds I saw the san mateo bridge (no point in tuning in sfo VOR). My heading was fine, but I seemed to be farther north(west) than I would have liked. I don't know that I busted the sfo TCA, but it is possible. Correcting actions: leave the area expeditiously. Contributing factors: 1) lack of recent flying: a) I haven't kept up my accustomed frequent flying for several weeks; B) had I thought, I would have had sfo VOR set as a waypoint. 3) wanting to get down. 4) stratus layer. I know the bay area very well--when I can see the ground (or when I use my INS).

Original NASA ASRS Text

Title: NAVIGATION ERROR RESULTS IN UNCOORDINATED PENETRATION OF AIRSPACE.

Narrative: ROUTINE FLT: RETURNING SMA TO ITS HOME BASE AT HAF. DEPARTED CLR (VFR) SQL ON A BAY MEADOW DEP. I COULD SEE CLOUDS PEEKING OVER THE COASTAL HILLS--NOT A GOOD SIGN FOR VFR ARR AT HAF. OVER THE PASS IN THE COASTAL HILLS, I GOT THE WX FROM HAF UNICOM: 'CEILING 1800 AND DROPPING, RWY 30 RECOMMENDED.' I FLEW RNAV TO THE ARPT AT 3000' LOOKING FOR A HOLE--NOTHING. I THEN CALLED BAY APCH TO AIR FILE FOR RNAV-A TO HAF. NEARING HAF, I CALLED UP BAY, WHO INFORMED ME THAT THE RNAV-A APCH HAD BEEN NOTAMED AS UNUSABLE. I THEN TURNED AROUND AND HEADED FOR SQL. IN A FEW SECS I SAW THE SAN MATEO BRIDGE (NO POINT IN TUNING IN SFO VOR). MY HDG WAS FINE, BUT I SEEMED TO BE FARTHER N(W) THAN I WOULD HAVE LIKED. I DON'T KNOW THAT I BUSTED THE SFO TCA, BUT IT IS POSSIBLE. CORRECTING ACTIONS: LEAVE THE AREA EXPEDITIOUSLY. CONTRIBUTING FACTORS: 1) LACK OF RECENT FLYING: A) I HAVEN'T KEPT UP MY ACCUSTOMED FREQUENT FLYING FOR SEVERAL WKS; B) HAD I THOUGHT, I WOULD HAVE HAD SFO VOR SET AS A WAYPOINT. 3) WANTING TO GET DOWN. 4) STRATUS LAYER. I KNOW THE BAY AREA VERY WELL--WHEN I CAN SEE THE GND (OR WHEN I USE MY INS).

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