Narrative:

I was on a vector of 240 degrees with a clearance to climb to 4000 ft in class B airspace. Directly in front of me was a line of mountains with the lowest being 5700 ft. I became preoccupied by verifying that I would have sufficient clearance of the terrain, and I didn't notice that I had climbed through 4000 ft to 4100 ft. As soon as I realized my mistake, I began a descent back to 4000 ft. Moments later, ATC cleared me for 6500 ft, and I began a climb. About 5 seconds later, ATC canceled the altitude clearance and instructed me to maintain 4000 ft, which I proceeded to do. 10 seconds later, the controller asked me whether I had climbed above 4000 ft, and I replied that I had climbed to 4100 ft (the last altitude that I recalled being at). The controller then informed me that traffic was either crossing overhead or nearby at 4500 ft (I'm not sure which). I do not know whether a loss of separation occurred here, and if so, did it occur before or after the controller cleared me to 6500 ft? There are several contributing factors to this incident. The main factor involves lack of planning with regard to an unfamiliar clearance given by clearance delivery. For this trip, I had originally planned to depart north runway 19, but due to winds that day, the runways were reversed, and I found myself climbing out on a westerly heading instead of a southerly one. I should have considered this after clearance delivery issued my departure clearance, and should have consulted my charts with regard to the terrain around the departure route. I did not see the line of mountains that distraction me until I was airborne, so I became preoccupied with my charts. Because of this, I overshot my cleared altitude. The second factor involves assumptions that I made about my route of flight. On departure, I had expected to climb via a sbound course (from pilot guide) and proceeded by pilotage by following I-15 south to southern california. What the controller was doing was vectoring me to V-394. This would have eventually brought me back to my intended course, but the initial segment had me crossing high terrain that I would otherwise have avoided. Initially, I was not aware of this, and I should have asked the controller about his intentions and advised him of my intended route of flight. So in addition to being distraction by terrain avoidance, I was distraction from trying to figure out where ATC was vectoring me to, so I wasn't minding my altitude. From now on, I will consult my charts before departure if I am given an unfamiliar or unplanned clearance route. I will also be more pro-active in asking ATC about their intentions if I am being vectored in an unexpected direction. These steps would have avoided any distrs in busy airspace.

Google
 

Original NASA ASRS Text

Title: ALT AND NAV PROB IN LAS CLASS B AIRSPACE COUPLED WITH A TFC CONFLICT.

Narrative: I WAS ON A VECTOR OF 240 DEGS WITH A CLRNC TO CLB TO 4000 FT IN CLASS B AIRSPACE. DIRECTLY IN FRONT OF ME WAS A LINE OF MOUNTAINS WITH THE LOWEST BEING 5700 FT. I BECAME PREOCCUPIED BY VERIFYING THAT I WOULD HAVE SUFFICIENT CLRNC OF THE TERRAIN, AND I DIDN'T NOTICE THAT I HAD CLBED THROUGH 4000 FT TO 4100 FT. AS SOON AS I REALIZED MY MISTAKE, I BEGAN A DSCNT BACK TO 4000 FT. MOMENTS LATER, ATC CLRED ME FOR 6500 FT, AND I BEGAN A CLB. ABOUT 5 SECONDS LATER, ATC CANCELED THE ALT CLRNC AND INSTRUCTED ME TO MAINTAIN 4000 FT, WHICH I PROCEEDED TO DO. 10 SECONDS LATER, THE CTLR ASKED ME WHETHER I HAD CLBED ABOVE 4000 FT, AND I REPLIED THAT I HAD CLBED TO 4100 FT (THE LAST ALT THAT I RECALLED BEING AT). THE CTLR THEN INFORMED ME THAT TFC WAS EITHER XING OVERHEAD OR NEARBY AT 4500 FT (I'M NOT SURE WHICH). I DO NOT KNOW WHETHER A LOSS OF SEPARATION OCCURRED HERE, AND IF SO, DID IT OCCUR BEFORE OR AFTER THE CTLR CLRED ME TO 6500 FT? THERE ARE SEVERAL CONTRIBUTING FACTORS TO THIS INCIDENT. THE MAIN FACTOR INVOLVES LACK OF PLANNING WITH REGARD TO AN UNFAMILIAR CLRNC GIVEN BY CLRNC DELIVERY. FOR THIS TRIP, I HAD ORIGINALLY PLANNED TO DEPART N RWY 19, BUT DUE TO WINDS THAT DAY, THE RWYS WERE REVERSED, AND I FOUND MYSELF CLBING OUT ON A WESTERLY HDG INSTEAD OF A SOUTHERLY ONE. I SHOULD HAVE CONSIDERED THIS AFTER CLRNC DELIVERY ISSUED MY DEP CLRNC, AND SHOULD HAVE CONSULTED MY CHARTS WITH REGARD TO THE TERRAIN AROUND THE DEP RTE. I DID NOT SEE THE LINE OF MOUNTAINS THAT DISTR ME UNTIL I WAS AIRBORNE, SO I BECAME PREOCCUPIED WITH MY CHARTS. BECAUSE OF THIS, I OVERSHOT MY CLRED ALT. THE SECOND FACTOR INVOLVES ASSUMPTIONS THAT I MADE ABOUT MY RTE OF FLT. ON DEP, I HAD EXPECTED TO CLB VIA A SBOUND COURSE (FROM PLT GUIDE) AND PROCEEDED BY PILOTAGE BY FOLLOWING I-15 S TO SOUTHERN CALIFORNIA. WHAT THE CTLR WAS DOING WAS VECTORING ME TO V-394. THIS WOULD HAVE EVENTUALLY BROUGHT ME BACK TO MY INTENDED COURSE, BUT THE INITIAL SEGMENT HAD ME XING HIGH TERRAIN THAT I WOULD OTHERWISE HAVE AVOIDED. INITIALLY, I WAS NOT AWARE OF THIS, AND I SHOULD HAVE ASKED THE CTLR ABOUT HIS INTENTIONS AND ADVISED HIM OF MY INTENDED RTE OF FLT. SO IN ADDITION TO BEING DISTR BY TERRAIN AVOIDANCE, I WAS DISTR FROM TRYING TO FIGURE OUT WHERE ATC WAS VECTORING ME TO, SO I WASN'T MINDING MY ALT. FROM NOW ON, I WILL CONSULT MY CHARTS BEFORE DEP IF I AM GIVEN AN UNFAMILIAR OR UNPLANNED CLRNC RTE. I WILL ALSO BE MORE PRO-ACTIVE IN ASKING ATC ABOUT THEIR INTENTIONS IF I AM BEING VECTORED IN AN UNEXPECTED DIRECTION. THESE STEPS WOULD HAVE AVOIDED ANY DISTRS IN BUSY AIRSPACE.

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.