Air carrier large transport altitude deviation undershot altitude crossing restriction because fix w...

Attributes
ACN	128735
Time
Date	198911
Day	Fri
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : dxo
State Reference	MI
Altitude	msl bound lower : 23000 msl bound upper : 23900
Environment
Flight Conditions	IMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zob
Operator	common carrier : air carrier
Make Model Name	Large Transport, Low Wing, 2 Turbojet Eng
Navigation In Use	Other Other
Flight Phase	cruise other descent other
Route In Use	enroute : direct
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 225 flight time total : 7500 flight time type : 1000
ASRS Report	128735
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp
Events
Anomaly	altitude deviation : crossing restriction not met altitude deviation : undershoot 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:

Told to cross 60 mi west of fnt at FL230. Fnt was not on our route, nor had it been programmed into the FMC. By the time we had properly programmed the FMC, we were only able to descend to 23900' at 60 me west of fnt. Flight plan had us filed to a point formed by V450 and the dxo 342 degree right, then direct polar. The point formed by V450 and the dxo 342 degree right was not programmed in the FMC data base. When in inserted the original route, I skipped the point, intending to figure the proper programming while en route, and then forgot about it. To correct both these situations, I would recommend that on automated cockpits, the necessary chkpoints be in the FMC data base, or ATC not use points not programmed into the data base. Also, both these situations could have been prevented if we had not depended so much on the automation and gone back to basic flying.

Original NASA ASRS Text

Title: ACR LGT ALT DEVIATION UNDERSHOT ALT CROSSING RESTRICTION BECAUSE FIX WAS NOT IN THE FMC.

Narrative: TOLD TO CROSS 60 MI W OF FNT AT FL230. FNT WAS NOT ON OUR ROUTE, NOR HAD IT BEEN PROGRAMMED INTO THE FMC. BY THE TIME WE HAD PROPERLY PROGRAMMED THE FMC, WE WERE ONLY ABLE TO DSND TO 23900' AT 60 ME W OF FNT. FLT PLAN HAD US FILED TO A POINT FORMED BY V450 AND THE DXO 342 DEG R, THEN DIRECT POLAR. THE POINT FORMED BY V450 AND THE DXO 342 DEG R WAS NOT PROGRAMMED IN THE FMC DATA BASE. WHEN IN INSERTED THE ORIGINAL ROUTE, I SKIPPED THE POINT, INTENDING TO FIGURE THE PROPER PROGRAMMING WHILE ENRTE, AND THEN FORGOT ABOUT IT. TO CORRECT BOTH THESE SITUATIONS, I WOULD RECOMMEND THAT ON AUTOMATED COCKPITS, THE NECESSARY CHKPOINTS BE IN THE FMC DATA BASE, OR ATC NOT USE POINTS NOT PROGRAMMED INTO THE DATA BASE. ALSO, BOTH THESE SITUATIONS COULD HAVE BEEN PREVENTED IF WE HAD NOT DEPENDED SO MUCH ON THE AUTOMATION AND GONE BACK TO BASIC FLYING.

Data retrieved from NASA's ASRS site as of August 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.

Air carrier large transport altitude deviation undershot altitude crossing restriction because fix was not in the FMC.