B737-300 fails to meet clearance crossing restr arriving smf.

Attributes
ACN	448005
Time
Date	199909
Day	Mon
Local Time Of Day	1201 To 1800
Place
Locale Reference	intersection : turlo
State Reference	CA
Altitude	msl bound lower : 24000 msl bound upper : 31000
Environment
Flight Conditions	VMC VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zoa.artcc
Operator	common carrier : air carrier
Make Model Name	B737-300
Operating Under FAR Part	Part 121
Navigation In Use	other other vortac
Flight Phase	descent : intermediate altitude descent : approach
Route In Use	arrival : on vectors arrival star : wraps 5
Flight Plan	IFR
Aircraft 2
Controlling Facilities	artcc : zoa.artcc
Make Model Name	Commercial Fixed Wing
Flight Phase	cruise : level
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp
Experience	flight time last 90 days : 200 flight time total : 9800 flight time type : 2100
ASRS Report	448005
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 270 flight time total : 17000 flight time type : 10000
ASRS Report	448003
Events
Anomaly	conflict : airborne less severe non adherence : far non adherence : published procedure non adherence : clearance other spatial deviation
Independent Detector	other controllera other flight crewa other flight crewb
Resolutory Action	controller : provided flight assist controller : issued new clearance flight crew : returned to assigned altitude none taken : insufficient time
Supplementary
Problem Areas	Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

While cruising at FL310, fpr (J5), we received a clearance from center to proceed directly to clovis (czq) and the remainder of the 'wraps 5 arrival' (STAR). The clearance also included 'at pilot's discretion, cross the turlo intersection at FL240.' the crossing restr problem arose, or became evident, when center queried us by saying, 'didn't I give you turlo at FL240?' at the time, we were navigating solely by LNAV, and our FMC CDU indicated our top of descent point ws 11 mi. (As PF, this was the time I planned on to vacate FL310 in order to satisfy the crossing restr at FL240 over turlo.) the controller assured us we were actually 3 mi from turlo. At this moment, I left FL310 and began to expedite a descent to FL240. Clearly, it was too late to cross turlo at FL240. I recall the restr during my preflight planning on the FMC. At the time of the occurrence I was on the 'progress' page and it clearly indicated a 'to T/C' prompt. However, had I been on the 'descent' page, it would have shown the waypoint constraint for the altitude restr. I also failed to back up my FMC with raw data, and I did not have the PNF back me up. End result was overflying turlo about 6000 ft higher then our restr allowed. We violated crossing turlo at FL240.

Original NASA ASRS Text

Title: B737-300 FAILS TO MEET CLRNC XING RESTR ARRIVING SMF.

Narrative: WHILE CRUISING AT FL310, FPR (J5), WE RECEIVED A CLRNC FROM CTR TO PROCEED DIRECTLY TO CLOVIS (CZQ) AND THE REMAINDER OF THE 'WRAPS 5 ARR' (STAR). THE CLRNC ALSO INCLUDED 'AT PLT'S DISCRETION, CROSS THE TURLO INTXN AT FL240.' THE XING RESTR PROB AROSE, OR BECAME EVIDENT, WHEN CTR QUERIED US BY SAYING, 'DIDN'T I GIVE YOU TURLO AT FL240?' AT THE TIME, WE WERE NAVING SOLELY BY LNAV, AND OUR FMC CDU INDICATED OUR TOP OF DSCNT POINT WS 11 MI. (AS PF, THIS WAS THE TIME I PLANNED ON TO VACATE FL310 IN ORDER TO SATISFY THE XING RESTR AT FL240 OVER TURLO.) THE CTLR ASSURED US WE WERE ACTUALLY 3 MI FROM TURLO. AT THIS MOMENT, I LEFT FL310 AND BEGAN TO EXPEDITE A DSCNT TO FL240. CLRLY, IT WAS TOO LATE TO CROSS TURLO AT FL240. I RECALL THE RESTR DURING MY PREFLT PLANNING ON THE FMC. AT THE TIME OF THE OCCURRENCE I WAS ON THE 'PROGRESS' PAGE AND IT CLRLY INDICATED A 'TO T/C' PROMPT. HOWEVER, HAD I BEEN ON THE 'DSCNT' PAGE, IT WOULD HAVE SHOWN THE WAYPOINT CONSTRAINT FOR THE ALT RESTR. I ALSO FAILED TO BACK UP MY FMC WITH RAW DATA, AND I DID NOT HAVE THE PNF BACK ME UP. END RESULT WAS OVERFLYING TURLO ABOUT 6000 FT HIGHER THEN OUR RESTR ALLOWED. WE VIOLATED XING TURLO AT FL240.

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.