Flight crew of an large transport undershot crossing altitude fix due to an FMS program problem.

Attributes
ACN	322670
Time
Date	199512
Day	Wed
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : ipl
State Reference	CA
Altitude	msl bound lower : 10000 msl bound upper : 16000
Environment
Flight Conditions	Mixed
Light	Dusk
Aircraft 1
Controlling Facilities	artcc : zla tracon : san
Operator	common carrier : air carrier
Make Model Name	MD-90 Series (DC-9-90) Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Navigation In Use	Other Other
Flight Phase	descent other
Route In Use	arrival other arrival star : star enroute airway : zla
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : flight engineer pilot : atp
Experience	flight time last 90 days : 120 flight time total : 9000 flight time type : 3400
ASRS Report	322670
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : commercial pilot : instrument pilot : atp
Events
Anomaly	altitude deviation : crossing restriction not met altitude deviation : undershoot non adherence : clearance
Independent Detector	other flight crewa
Resolutory Action	controller : issued new clearance
Consequence	Other
Supplementary
Primary Problem	Aircraft
Air Traffic Incident	Pilot Deviation

Narrative:

When loading the FMS on preflight, the FMS database revealed 2 baret. Baret 4 stars 'bar 09' and 'bar 27.' I selected 'bar 27' but my CDU display jumped from 'ipl' to 'swatt' intersection. I then manually typed in the intxns after 'ipl': 'kumba,' 'pillo' 'baret' 'PGY04305.' then I filled in the 'swatt' intersection to close the discontinuity. The flight plan was activated. En route, I typed in the crossing restr of 10000 ft at 'pillo.' on letdown I discover (too late) that although the 'pillo' 10000 ft restr is still on the 'legs' page and 'pillo' is the first check point on the page, the FMS has selected 'baret' as the active waypoint. The 'des' page showed the aircraft on profile, but I'm only 10 mi east of 'pillo' at 16000 ft. We informed la ARTCC we would not be able to cross 'pillo' at 10000 ft, and their reply was 'contact san diego approach control on frequency xxxxx.' checked in with san diego approach control and told them we would be high at 'pillo' and they put us on a vector for lindbergh. I do not understand why the FMS did what it did.

Original NASA ASRS Text

Title: FLC OF AN LGT UNDERSHOT XING ALT FIX DUE TO AN FMS PROGRAM PROB.

Narrative: WHEN LOADING THE FMS ON PREFLT, THE FMS DATABASE REVEALED 2 BARET. BARET 4 STARS 'BAR 09' AND 'BAR 27.' I SELECTED 'BAR 27' BUT MY CDU DISPLAY JUMPED FROM 'IPL' TO 'SWATT' INTXN. I THEN MANUALLY TYPED IN THE INTXNS AFTER 'IPL': 'KUMBA,' 'PILLO' 'BARET' 'PGY04305.' THEN I FILLED IN THE 'SWATT' INTXN TO CLOSE THE DISCONTINUITY. THE FLT PLAN WAS ACTIVATED. ENRTE, I TYPED IN THE XING RESTR OF 10000 FT AT 'PILLO.' ON LETDOWN I DISCOVER (TOO LATE) THAT ALTHOUGH THE 'PILLO' 10000 FT RESTR IS STILL ON THE 'LEGS' PAGE AND 'PILLO' IS THE FIRST CHK POINT ON THE PAGE, THE FMS HAS SELECTED 'BARET' AS THE ACTIVE WAYPOINT. THE 'DES' PAGE SHOWED THE ACFT ON PROFILE, BUT I'M ONLY 10 MI E OF 'PILLO' AT 16000 FT. WE INFORMED LA ARTCC WE WOULD NOT BE ABLE TO CROSS 'PILLO' AT 10000 FT, AND THEIR REPLY WAS 'CONTACT SAN DIEGO APCH CTL ON FREQ XXXXX.' CHKED IN WITH SAN DIEGO APCH CTL AND TOLD THEM WE WOULD BE HIGH AT 'PILLO' AND THEY PUT US ON A VECTOR FOR LINDBERGH. I DO NOT UNDERSTAND WHY THE FMS DID WHAT IT DID.

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.