An air carrier medium large transport failed to make its crossing restriction.

Attributes
ACN	272507
Time
Date	199405
Day	Mon
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : oak airport : sfo
State Reference	CA
Altitude	msl bound lower : 35000 msl bound upper : 35000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zoa tracon : hou
Operator	common carrier : air carrier
Make Model Name	B737-300
Operating Under FAR Part	Part 121
Navigation In Use	Other Other
Flight Phase	cruise other descent other
Route In Use	arrival other arrival star : star
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : cfi pilot : atp pilot : flight engineer
Experience	flight time last 90 days : 170 flight time total : 14500 flight time type : 5000
ASRS Report	272507
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : flight engineer pilot : atp
Experience	flight time last 90 days : 170 flight time total : 15000 flight time type : 5000
ASRS Report	272788
Events
Anomaly	aircraft equipment problem : less severe altitude deviation : undershoot altitude deviation : crossing restriction not met non adherence : published procedure non adherence : clearance other anomaly other
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance flight crew : returned to intended course or assigned course other
Consequence	faa : reviewed incident with flight crew
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

We were at at cruise FL350 on flight from lax-sfo. Just southeast of big sur we had received clearance to cross boldr intersection at 10000 ft, 200 KTS. In the vicinity of anjee intersection, ZOA frequency 125.45 MHZ queried our altitude and if we were going to make the crossing restriction. A quick check with the descent page on the FMC control panel/display showed us 17000 ft above profile -- obviously too high to meet the crossing restriction. My first officer and I both checked all inputs to the FMC and especially the descent crossing restriction. We also verified autopilot and flight director engagement with command engaged on the autoplt, VNAV and LNAV engaged on the flight director. However, neither of us had the descent page selected on our FMC display units. ZOA gave us a left 360 degree turn which put us back on descent profile. Our air carrier training indicates PF FMC display unit be on progress page and PNF's FMC display unit be on legs page, because the progress page 1 has a top of descent advisor display. We are personally going to use the PF FMC display in the descent page after this experience and recommend to the director of B737/300 that this confign will allow monitoring possible anomalies related to descent profiles. Supplemental information from acn 272788: I had been unusually tired all day -- a big convention at the hotel the night before made it impossible to sleep. Insufficient sleep was a major contributing factor.

Original NASA ASRS Text

Title: AN ACR MLG FAILED TO MAKE ITS XING RESTRICTION.

Narrative: WE WERE AT AT CRUISE FL350 ON FLT FROM LAX-SFO. JUST SE OF BIG SUR WE HAD RECEIVED CLRNC TO CROSS BOLDR INTXN AT 10000 FT, 200 KTS. IN THE VICINITY OF ANJEE INTXN, ZOA FREQ 125.45 MHZ QUERIED OUR ALT AND IF WE WERE GOING TO MAKE THE XING RESTRICTION. A QUICK CHK WITH THE DSCNT PAGE ON THE FMC CTL PANEL/DISPLAY SHOWED US 17000 FT ABOVE PROFILE -- OBVIOUSLY TOO HIGH TO MEET THE XING RESTRICTION. MY FO AND I BOTH CHKED ALL INPUTS TO THE FMC AND ESPECIALLY THE DSCNT XING RESTRICTION. WE ALSO VERIFIED AUTOPILOT AND FLT DIRECTOR ENGAGEMENT WITH COMMAND ENGAGED ON THE AUTOPLT, VNAV AND LNAV ENGAGED ON THE FLT DIRECTOR. HOWEVER, NEITHER OF US HAD THE DSCNT PAGE SELECTED ON OUR FMC DISPLAY UNITS. ZOA GAVE US A L 360 DEG TURN WHICH PUT US BACK ON DSCNT PROFILE. OUR ACR TRAINING INDICATES PF FMC DISPLAY UNIT BE ON PROGRESS PAGE AND PNF'S FMC DISPLAY UNIT BE ON LEGS PAGE, BECAUSE THE PROGRESS PAGE 1 HAS A TOP OF DSCNT ADVISOR DISPLAY. WE ARE PERSONALLY GOING TO USE THE PF FMC DISPLAY IN THE DSCNT PAGE AFTER THIS EXPERIENCE AND RECOMMEND TO THE DIRECTOR OF B737/300 THAT THIS CONFIGN WILL ALLOW MONITORING POSSIBLE ANOMALIES RELATED TO DSCNT PROFILES. SUPPLEMENTAL INFO FROM ACN 272788: I HAD BEEN UNUSUALLY TIRED ALL DAY -- A BIG CONVENTION AT THE HOTEL THE NIGHT BEFORE MADE IT IMPOSSIBLE TO SLEEP. INSUFFICIENT SLEEP WAS A MAJOR CONTRIBUTING FACTOR.

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.