Heading track altitude deviation altitude overshot in descent.

Attributes
ACN	316200
Time
Date	199509
Day	Sat
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : sbp
State Reference	CA
Altitude	msl bound lower : 4300 msl bound upper : 5000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zla tower : las
Operator	common carrier : air carrier
Make Model Name	Commercial Fixed Wing
Operating Under FAR Part	Part 135
Flight Phase	descent other
Route In Use	enroute : on vectors enroute other
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 250 flight time total : 10000 flight time type : 5000
ASRS Report	316200
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : instrument pilot : commercial
Events
Anomaly	altitude deviation : overshoot non adherence : clearance other anomaly other other spatial deviation
Independent Detector	other controllera other flight crewa
Resolutory Action	controller : issued new clearance flight crew : returned to intended course or assigned course
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation
Situations
ATC Facility	procedure or policy : unspecified

Narrative:

We were direct to the mqo VOR from the northwest. We were advised by ZOA that we would be holding for an aircraft ahead of us into sbp, therefore I was maintaining a higher than normal altitude of 15000 ft. Upon handoff to ZLA, we were immediately requested to maintain maximum airspeed and maximum descent rate to 5000 ft and given a heading to intercept the localizer. Due to this sudden change in plans, my first officer had to go off to call company operations and brief the passenger. Without an altitude alerter and due to our high speed and rate of descent, I descended below assigned altitude by 700 ft and went through the localizer. I was VMC on top of an undercast, therefore I knew I had terrain clearance. I got back up to altitude, re-intercepted the localizer and continued the approach without incident. I believe better communication and planning between ZOA and ZLA would have given me a much better idea of what to expect. The ZLA controller was very busy and very rude. An altitude alerter would also have been very helpful.

Original NASA ASRS Text

Title: HDG TRACK ALTDEV ALT OVERSHOT IN DSCNT.

Narrative: WE WERE DIRECT TO THE MQO VOR FROM THE NW. WE WERE ADVISED BY ZOA THAT WE WOULD BE HOLDING FOR AN ACFT AHEAD OF US INTO SBP, THEREFORE I WAS MAINTAINING A HIGHER THAN NORMAL ALT OF 15000 FT. UPON HDOF TO ZLA, WE WERE IMMEDIATELY REQUESTED TO MAINTAIN MAX AIRSPD AND MAX DSCNT RATE TO 5000 FT AND GIVEN A HDG TO INTERCEPT THE LOC. DUE TO THIS SUDDEN CHANGE IN PLANS, MY FO HAD TO GO OFF TO CALL COMPANY OPS AND BRIEF THE PAX. WITHOUT AN ALT ALERTER AND DUE TO OUR HIGH SPD AND RATE OF DSCNT, I DSNDED BELOW ASSIGNED ALT BY 700 FT AND WENT THROUGH THE LOC. I WAS VMC ON TOP OF AN UNDERCAST, THEREFORE I KNEW I HAD TERRAIN CLRNC. I GOT BACK UP TO ALT, RE-INTERCEPTED THE LOC AND CONTINUED THE APCH WITHOUT INCIDENT. I BELIEVE BETTER COM AND PLANNING BTWN ZOA AND ZLA WOULD HAVE GIVEN ME A MUCH BETTER IDEA OF WHAT TO EXPECT. THE ZLA CTLR WAS VERY BUSY AND VERY RUDE. AN ALT ALERTER WOULD ALSO HAVE BEEN VERY HELPFUL.

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.