Narrative:

I was on an IFR flight near sfo for palo alto (pao). Approach control agreed to vectors for sjc ILS 12 and when VMC cancel IFR and proceed VFR to pao. Upon reaching VMC 20 west of pao, I cancelled IFR and proceeded VFR with advisories from bay approach to pao. During VFR to pao and with advisories I inadvertently penetrated sql airspace. Within sql airspace approach handed me off to pao tower. I contacted pao tower and advised of my location and the flight proceeded normally without incident. Poor pilot navigation (primarily a descent to 2000 ft to maintain VFR) was the cause of my penetrating sql airspace. However, at the time of the handoff from approach, I was already in sql airspace. I do not know if approach coordinated with sql tower.

Google
 

Original NASA ASRS Text

Title: AFTER CANCELING IFR FLT PLAN, PRIVATE PLT INADVERTENTLY PENETRATED A NEARBY ATA ENRTE TO DEST ARPT VFR.

Narrative: I WAS ON AN IFR FLT NEAR SFO FOR PALO ALTO (PAO). APCH CTL AGREED TO VECTORS FOR SJC ILS 12 AND WHEN VMC CANCEL IFR AND PROCEED VFR TO PAO. UPON REACHING VMC 20 W OF PAO, I CANCELLED IFR AND PROCEEDED VFR WITH ADVISORIES FROM BAY APCH TO PAO. DURING VFR TO PAO AND WITH ADVISORIES I INADVERTENTLY PENETRATED SQL AIRSPACE. WITHIN SQL AIRSPACE APCH HANDED ME OFF TO PAO TWR. I CONTACTED PAO TWR AND ADVISED OF MY LOCATION AND THE FLT PROCEEDED NORMALLY WITHOUT INCIDENT. POOR PLT NAV (PRIMARILY A DSCNT TO 2000 FT TO MAINTAIN VFR) WAS THE CAUSE OF MY PENETRATING SQL AIRSPACE. HOWEVER, AT THE TIME OF THE HANDOFF FROM APCH, I WAS ALREADY IN SQL AIRSPACE. I DO NOT KNOW IF APCH COORDINATED WITH SQL TWR.

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.