Narrative:

On feb/xa/99 while descending into chino, ca, on a VFR flight from visalia, ca, I apparently violated brackett's airspace. I called chino approximately 10 mi out after listening to ATIS, received landing instructions, landed and then was told to call brackett ATC. I was informed by the ATC controller I had naved through their airspace. I was surprised to hear that, as my plan was to fly over cable under the outer ring of ont's class C airspace through the corridor between brackett and ontario. I told the ATC controller this was my first trip into this area, I had a current map in front of me, with an argus 7000 moving map, an additional handheld GPS and another pilot as an observer with me. We were doing everything we could to do what we thought was correct, and that I was sorry as I never saw them. I heard the ATC controller that I was talking with make a comment to someone else in the tower, explaining the situation as it happened and that I was new to this area. The person in the backgnd said 'just get his information and write him up' in a rather short fashion. I provided all the requested information to the ATC controller. I was also told that traffic had to be redirected. This, however, I don't understand, as both myself and my passenger (pilot) were scanning continually and never saw another aircraft anywhere near close. As I was approaching chino, I thought I was looking out my left side at ont (a double parallel runway) and I needed to stay west of a north/south road which is west of the runway. Obviously, now, it was not the correct road and not the correct parallel runway. In the haze and ground clutter, and since it was my first time into chino, my ground reference must have been incorrect. I have flown into 2 different countries, into the arctic circle, and I cross the united states coast-to-coast several times a yr and I have never violated anyone's airspace before. I was surprised to hear what had happened.

Related reports:

Google
 

Original NASA ASRS Text

Title: SMA ENTERS CLASS D AIRSPACE WITHOUT PROPER CLRNC AT POC.

Narrative: ON FEB/XA/99 WHILE DSNDING INTO CHINO, CA, ON A VFR FLT FROM VISALIA, CA, I APPARENTLY VIOLATED BRACKETT'S AIRSPACE. I CALLED CHINO APPROX 10 MI OUT AFTER LISTENING TO ATIS, RECEIVED LNDG INSTRUCTIONS, LANDED AND THEN WAS TOLD TO CALL BRACKETT ATC. I WAS INFORMED BY THE ATC CTLR I HAD NAVED THROUGH THEIR AIRSPACE. I WAS SURPRISED TO HEAR THAT, AS MY PLAN WAS TO FLY OVER CABLE UNDER THE OUTER RING OF ONT'S CLASS C AIRSPACE THROUGH THE CORRIDOR BTWN BRACKETT AND ONTARIO. I TOLD THE ATC CTLR THIS WAS MY FIRST TRIP INTO THIS AREA, I HAD A CURRENT MAP IN FRONT OF ME, WITH AN ARGUS 7000 MOVING MAP, AN ADDITIONAL HANDHELD GPS AND ANOTHER PLT AS AN OBSERVER WITH ME. WE WERE DOING EVERYTHING WE COULD TO DO WHAT WE THOUGHT WAS CORRECT, AND THAT I WAS SORRY AS I NEVER SAW THEM. I HEARD THE ATC CTLR THAT I WAS TALKING WITH MAKE A COMMENT TO SOMEONE ELSE IN THE TWR, EXPLAINING THE SIT AS IT HAPPENED AND THAT I WAS NEW TO THIS AREA. THE PERSON IN THE BACKGND SAID 'JUST GET HIS INFO AND WRITE HIM UP' IN A RATHER SHORT FASHION. I PROVIDED ALL THE REQUESTED INFO TO THE ATC CTLR. I WAS ALSO TOLD THAT TFC HAD TO BE REDIRECTED. THIS, HOWEVER, I DON'T UNDERSTAND, AS BOTH MYSELF AND MY PAX (PLT) WERE SCANNING CONTINUALLY AND NEVER SAW ANOTHER ACFT ANYWHERE NEAR CLOSE. AS I WAS APCHING CHINO, I THOUGHT I WAS LOOKING OUT MY L SIDE AT ONT (A DOUBLE PARALLEL RWY) AND I NEEDED TO STAY W OF A N/S ROAD WHICH IS W OF THE RWY. OBVIOUSLY, NOW, IT WAS NOT THE CORRECT ROAD AND NOT THE CORRECT PARALLEL RWY. IN THE HAZE AND GND CLUTTER, AND SINCE IT WAS MY FIRST TIME INTO CHINO, MY GND REF MUST HAVE BEEN INCORRECT. I HAVE FLOWN INTO 2 DIFFERENT COUNTRIES, INTO THE ARCTIC CIRCLE, AND I CROSS THE UNITED STATES COAST-TO-COAST SEVERAL TIMES A YR AND I HAVE NEVER VIOLATED ANYONE'S AIRSPACE BEFORE. I WAS SURPRISED TO HEAR WHAT HAD HAPPENED.

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.