Crossing restriction not met.

Attributes
ACN	315245
Time
Date	199509
Day	Fri
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : bpr
State Reference	TX
Altitude	msl bound lower : 11000 msl bound upper : 11000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zfw
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 : zfw enroute other
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp pilot : cfi
Experience	flight time last 90 days : 88 flight time total : 11000 flight time type : 88
ASRS Report	315245
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 200 flight time total : 17500 flight time type : 200
ASRS Report	314830
Events
Anomaly	altitude deviation : undershoot altitude deviation : crossing restriction not met non adherence : clearance other anomaly other
Independent Detector	other controllera other flight crewa
Resolutory Action	controller : issued new clearance other
Consequence	faa : reviewed incident with flight crew
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

We were cleared direct to bpr with a crossing restriction of 40 mi northwest of bpr. Due to an input error on the CDU, I inadvertently placed the 40 mi waypoint sequenced after bpr rather than before it. Shortly thereafter, the crossing restriction was removed and a new one issued to cross didly intersection at 11000 ft. Due to the fact that the FMC was planning the descent with an additional 40 mi leg (back in the opposite direction), we were unable to make the crossing restriction at didly. When we discovered the error, we had to request (and received) relief on the altitude. No traffic conflict occurred. Added diligence in proper input and cross checking of data in the FMC would have prevented this occurrence.

Original NASA ASRS Text

Title: XING RESTRICTION NOT MET.

Narrative: WE WERE CLRED DIRECT TO BPR WITH A XING RESTRICTION OF 40 MI NW OF BPR. DUE TO AN INPUT ERROR ON THE CDU, I INADVERTENTLY PLACED THE 40 MI WAYPOINT SEQUENCED AFTER BPR RATHER THAN BEFORE IT. SHORTLY THEREAFTER, THE XING RESTRICTION WAS REMOVED AND A NEW ONE ISSUED TO CROSS DIDLY INTXN AT 11000 FT. DUE TO THE FACT THAT THE FMC WAS PLANNING THE DSCNT WITH AN ADDITIONAL 40 MI LEG (BACK IN THE OPPOSITE DIRECTION), WE WERE UNABLE TO MAKE THE XING RESTRICTION AT DIDLY. WHEN WE DISCOVERED THE ERROR, WE HAD TO REQUEST (AND RECEIVED) RELIEF ON THE ALT. NO TFC CONFLICT OCCURRED. ADDED DILIGENCE IN PROPER INPUT AND CROSS CHKING OF DATA IN THE FMC WOULD HAVE PREVENTED THIS OCCURRENCE.

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.