Narrative:

The occurrence/event was quite simply an 'altitude excursion' while on a descent clearance issued by ATC. As a united states customs citation ii, modified/operated in restr category, we began our flight with a short IFR proficiency flight conducted in VFR conditions. We filed and received our IFR clearance from owh to vct. From a cruise altitude of 14000 ft MSL, we were given a descent at pilot's discretion to descend and maintain 8000 ft. As PIC, I chose to allow the sic to fly from the left seat on this date, which is allowed in our operations. However, sic did not feel the need to perform an instrument approach to vct, so I advised that I did. I advised the sic that at 5000 ft MSL or approximately 20 NM out, I would take the controls and execute the VOR/DME runway 12L at vct. The problem of descending through 8000 ft MSL to approximately 7600 ft was discovered by both pilots nearly simultaneously. At this time ATC called noting our altitude, and verifying assigned altitude as 8000 ft MSL. Why did we miss our altitude? The mode select panel for flight director/autoplt is repositioned in front of left yoke, instead of the normal center pedestal area in normal cii's. Makes it difficult to double-check. The sic failed to activate altitude select on flight director/autoplt panel after we selected 8000 ft MSL in VNAV computer. Consequently, we did not get an altitude audio alert 1000 ft above preselected altitude. Moreover, autoplt obviously will not capture altitude if altitude select is not armed. As PIC, I was preoccupied briefing the approach into vct, setting up radios, etc. This kept me out of the loop so I did not issue altitude calls at 1000 ft above assigned altitude, and at 500 ft above, per our company policy. Although this event did not cause a traffic conflict, it had the potential to do so, all due to a breakdown in cockpit teamwork/crew coordination, sic's unfamiliarity with switchology from the left seat. I've never had this happen to me before, and once again, I realize we are all human and therefore are prone to error. Next time, we will aviate first, then navigation and do all the other lower priority tasks. Also, I'll take seriously a sic's lack of familiarity with left seat functions/switchology.

Google
 

Original NASA ASRS Text

Title: ALTDEV ALT OVERSHOT -- GOV FLC IS DISTRACTED DURING AN APCH BRIEFING AND DSNDS BELOW THEIR ASSIGNED ALT.

Narrative: THE OCCURRENCE/EVENT WAS QUITE SIMPLY AN 'ALT EXCURSION' WHILE ON A DSCNT CLRNC ISSUED BY ATC. AS A UNITED STATES CUSTOMS CITATION II, MODIFIED/OPERATED IN RESTR CATEGORY, WE BEGAN OUR FLT WITH A SHORT IFR PROFICIENCY FLT CONDUCTED IN VFR CONDITIONS. WE FILED AND RECEIVED OUR IFR CLRNC FROM OWH TO VCT. FROM A CRUISE ALT OF 14000 FT MSL, WE WERE GIVEN A DSCNT AT PLT'S DISCRETION TO DSND AND MAINTAIN 8000 FT. AS PIC, I CHOSE TO ALLOW THE SIC TO FLY FROM THE L SEAT ON THIS DATE, WHICH IS ALLOWED IN OUR OPS. HOWEVER, SIC DID NOT FEEL THE NEED TO PERFORM AN INST APCH TO VCT, SO I ADVISED THAT I DID. I ADVISED THE SIC THAT AT 5000 FT MSL OR APPROX 20 NM OUT, I WOULD TAKE THE CTLS AND EXECUTE THE VOR/DME RWY 12L AT VCT. THE PROB OF DSNDING THROUGH 8000 FT MSL TO APPROX 7600 FT WAS DISCOVERED BY BOTH PLTS NEARLY SIMULTANEOUSLY. AT THIS TIME ATC CALLED NOTING OUR ALT, AND VERIFYING ASSIGNED ALT AS 8000 FT MSL. WHY DID WE MISS OUR ALT? THE MODE SELECT PANEL FOR FLT DIRECTOR/AUTOPLT IS REPOSITIONED IN FRONT OF L YOKE, INSTEAD OF THE NORMAL CTR PEDESTAL AREA IN NORMAL CII'S. MAKES IT DIFFICULT TO DOUBLE-CHK. THE SIC FAILED TO ACTIVATE ALT SELECT ON FLT DIRECTOR/AUTOPLT PANEL AFTER WE SELECTED 8000 FT MSL IN VNAV COMPUTER. CONSEQUENTLY, WE DID NOT GET AN ALT AUDIO ALERT 1000 FT ABOVE PRESELECTED ALT. MOREOVER, AUTOPLT OBVIOUSLY WILL NOT CAPTURE ALT IF ALT SELECT IS NOT ARMED. AS PIC, I WAS PREOCCUPIED BRIEFING THE APCH INTO VCT, SETTING UP RADIOS, ETC. THIS KEPT ME OUT OF THE LOOP SO I DID NOT ISSUE ALT CALLS AT 1000 FT ABOVE ASSIGNED ALT, AND AT 500 FT ABOVE, PER OUR COMPANY POLICY. ALTHOUGH THIS EVENT DID NOT CAUSE A TFC CONFLICT, IT HAD THE POTENTIAL TO DO SO, ALL DUE TO A BREAKDOWN IN COCKPIT TEAMWORK/CREW COORD, SIC'S UNFAMILIARITY WITH SWITCHOLOGY FROM THE L SEAT. I'VE NEVER HAD THIS HAPPEN TO ME BEFORE, AND ONCE AGAIN, I REALIZE WE ARE ALL HUMAN AND THEREFORE ARE PRONE TO ERROR. NEXT TIME, WE WILL AVIATE FIRST, THEN NAV AND DO ALL THE OTHER LOWER PRIORITY TASKS. ALSO, I'LL TAKE SERIOUSLY A SIC'S LACK OF FAMILIARITY WITH L SEAT FUNCTIONS/SWITCHOLOGY.

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.