Altitude deviation on descent. Flight crew ATC miscom. Crossing restr not met.

Attributes
ACN	321140
Time
Date	199511
Day	Sun
Local Time Of Day	0601 To 1200
Place
Locale Reference	atc facility : ogd
State Reference	UT
Altitude	msl bound lower : 12000 msl bound upper : 15000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	Commercial Fixed Wing
Operating Under FAR Part	Part 121
Navigation In Use	Other Other
Flight Phase	descent other
Route In Use	enroute airway : slc
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 230 flight time total : 14200 flight time type : 4390
ASRS Report	321140
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
Independent Detector	other controllera other flight crewa
Resolutory Action	none taken : detected after the fact
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

After vectors for spacing we were given a heading to intercept ogd 302 resume bearr 1 to kslc. We thought we were given 12000 ft but we were actually given 15000 ft at bearr intersection. We may even have read back 15000 ft but we put 12000 ft in the altitude alert. I was with a new first officer and while I was talking with ATC and looking at the chart, he put in 12000 ft and he started talking about how that was going to be a tough altitude to make at the 250 KT speed restr we had. Mistake #1 was overlooking his putting the altitude in the altitude selector. That is the PNF job. The altitude is then confirmed by the PNF. Mistake #2 was not questioning ATC about a restr that was almost impossible to make. That would also have clarified the altitude. They seldom give us an altitude that is that difficult to make without comment. The WX was VFR, we saw no traffic, had TCASII on 15 NM below and was showing no traffic. Mistake #3 was getting busy with making the incorrect crossing altitude and not checking.

Original NASA ASRS Text

Title: ALT DEV ON DSCNT. FLC ATC MISCOM. XING RESTR NOT MET.

Narrative: AFTER VECTORS FOR SPACING WE WERE GIVEN A HDG TO INTERCEPT OGD 302 RESUME BEARR 1 TO KSLC. WE THOUGHT WE WERE GIVEN 12000 FT BUT WE WERE ACTUALLY GIVEN 15000 FT AT BEARR INTXN. WE MAY EVEN HAVE READ BACK 15000 FT BUT WE PUT 12000 FT IN THE ALT ALERT. I WAS WITH A NEW FO AND WHILE I WAS TALKING WITH ATC AND LOOKING AT THE CHART, HE PUT IN 12000 FT AND HE STARTED TALKING ABOUT HOW THAT WAS GOING TO BE A TOUGH ALT TO MAKE AT THE 250 KT SPD RESTR WE HAD. MISTAKE #1 WAS OVERLOOKING HIS PUTTING THE ALT IN THE ALT SELECTOR. THAT IS THE PNF JOB. THE ALT IS THEN CONFIRMED BY THE PNF. MISTAKE #2 WAS NOT QUESTIONING ATC ABOUT A RESTR THAT WAS ALMOST IMPOSSIBLE TO MAKE. THAT WOULD ALSO HAVE CLARIFIED THE ALT. THEY SELDOM GIVE US AN ALT THAT IS THAT DIFFICULT TO MAKE WITHOUT COMMENT. THE WX WAS VFR, WE SAW NO TFC, HAD TCASII ON 15 NM BELOW AND WAS SHOWING NO TFC. MISTAKE #3 WAS GETTING BUSY WITH MAKING THE INCORRECT XING ALT AND NOT CHKING.

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.