B737-400 fails to make altitude crossing restr of FL240 40 mi south of raalf.

Attributes
ACN	353857
Time
Date	199611
Day	Tue
Local Time Of Day	0601 To 1200
Place
Locale Reference	atc facility : orw
State Reference	CT
Altitude	msl bound lower : 24000 msl bound upper : 28000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zbw
Operator	common carrier : air carrier
Make Model Name	B737-400
Operating Under FAR Part	Part 121
Navigation In Use	Other Other
Flight Phase	descent other
Route In Use	arrival star : star
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp pilot : flight engineer pilot : cfi
Experience	flight time last 90 days : 100 flight time total : 9000 flight time type : 1000
ASRS Report	353857
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Events
Anomaly	altitude deviation : crossing restriction not met non adherence : clearance
Independent Detector	other flight crewa
Resolutory Action	none taken : anomaly accepted
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

At FL330 south of the norwich arrival to bos, we were 'cleared direct to raalf intersection with pilot's discretion to maintain FL280 and expect 40 NM south of raalf at FL240.' altitude window was reset to FL280, then the fmcs was programmed to the new crossing restr. Shortly after this, the clearance was given to 'cross 40 NM south of raalf and maintain FL240.' the fmcs would not program. I tried to program the fmcs, but with the 100 KTS of tailwind I passed the crossing point before making the crossing altitude. This was due to several factors: 1) not starting descent to FL280 as soon as the new altitude was received. 2) excessive tailwinds during descent. 3) failure of the fmcs to accept programming (the leg from bos-clt the fmcs failed to properly program for the captain during descent). 4) failure to maintain orientation to the crossing fixes. 5) captain had left the cockpit a few mins earlier to go to the restroom. Had there been 2 crew members observing the situation it probably would not have occurred.

Original NASA ASRS Text

Title: B737-400 FAILS TO MAKE ALT XING RESTR OF FL240 40 MI S OF RAALF.

Narrative: AT FL330 S OF THE NORWICH ARR TO BOS, WE WERE 'CLRED DIRECT TO RAALF INTXN WITH PLT'S DISCRETION TO MAINTAIN FL280 AND EXPECT 40 NM S OF RAALF AT FL240.' ALT WINDOW WAS RESET TO FL280, THEN THE FMCS WAS PROGRAMMED TO THE NEW XING RESTR. SHORTLY AFTER THIS, THE CLRNC WAS GIVEN TO 'CROSS 40 NM S OF RAALF AND MAINTAIN FL240.' THE FMCS WOULD NOT PROGRAM. I TRIED TO PROGRAM THE FMCS, BUT WITH THE 100 KTS OF TAILWIND I PASSED THE XING POINT BEFORE MAKING THE XING ALT. THIS WAS DUE TO SEVERAL FACTORS: 1) NOT STARTING DSCNT TO FL280 AS SOON AS THE NEW ALT WAS RECEIVED. 2) EXCESSIVE TAILWINDS DURING DSCNT. 3) FAILURE OF THE FMCS TO ACCEPT PROGRAMMING (THE LEG FROM BOS-CLT THE FMCS FAILED TO PROPERLY PROGRAM FOR THE CAPT DURING DSCNT). 4) FAILURE TO MAINTAIN ORIENTATION TO THE XING FIXES. 5) CAPT HAD LEFT THE COCKPIT A FEW MINS EARLIER TO GO TO THE RESTROOM. HAD THERE BEEN 2 CREW MEMBERS OBSERVING THE SIT IT PROBABLY WOULD NOT HAVE OCCURRED.

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.