B737-300 misses crossing restr due to improper FMC programming.

Attributes
ACN	442570
Time
Date	199907
Day	Mon
Local Time Of Day	1801 To 2400
Place
Locale Reference	intersection : ridgy
State Reference	MD
Altitude	msl single value : 24000
Environment
Flight Conditions	VMC
Light	Dusk
Aircraft 1
Controlling Facilities	artcc : zdc.artcc
Operator	common carrier : air carrier
Make Model Name	B737-300
Operating Under FAR Part	Part 121
Navigation In Use	other
Flight Phase	descent : intermediate altitude
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp pilot : commercial pilot : instrument
Experience	flight time last 90 days : 180 flight time total : 12000 flight time type : 3100
ASRS Report	442570
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : commercial pilot : instrument pilot : multi engine
Events
Anomaly	altitude deviation : crossing restriction not met non adherence : clearance
Independent Detector	atc equipment other atc equipment : radar other controllera
Resolutory Action	none taken : insufficient time
Supplementary
Problem Areas	Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

First officer was in control of airplane. The descent was programmed into FMC and LNAV was selected. We were given a descent to cross ridgy at FL240. I confirmed everything was set up properly. I then busied myself with copying ATIS and contacting company for a gate assignment. I notice the airplane start its descent, and I felt that everything was ok. When I switched back to ATC frequency, ZDC asked us if we were given ridgy at FL240. We confirmed that we had. We were approaching the fix but were way high. I stated we would be high but get down as soon as possible. We were at FL240 within 10 mi. First officer is relatively new with the company and the airplane. Sometime after given the clearance, he changed the FMC to cross skiay at FL240 and was flying the plane so as to cross that fix. The lesson I learned was I need to monitor 'new guys' more closely.

Original NASA ASRS Text

Title: B737-300 MISSES XING RESTR DUE TO IMPROPER FMC PROGRAMMING.

Narrative: FO WAS IN CTL OF AIRPLANE. THE DSCNT WAS PROGRAMMED INTO FMC AND LNAV WAS SELECTED. WE WERE GIVEN A DSCNT TO CROSS RIDGY AT FL240. I CONFIRMED EVERYTHING WAS SET UP PROPERLY. I THEN BUSIED MYSELF WITH COPYING ATIS AND CONTACTING COMPANY FOR A GATE ASSIGNMENT. I NOTICE THE AIRPLANE START ITS DSCNT, AND I FELT THAT EVERYTHING WAS OK. WHEN I SWITCHED BACK TO ATC FREQ, ZDC ASKED US IF WE WERE GIVEN RIDGY AT FL240. WE CONFIRMED THAT WE HAD. WE WERE APCHING THE FIX BUT WERE WAY HIGH. I STATED WE WOULD BE HIGH BUT GET DOWN ASAP. WE WERE AT FL240 WITHIN 10 MI. FO IS RELATIVELY NEW WITH THE COMPANY AND THE AIRPLANE. SOMETIME AFTER GIVEN THE CLRNC, HE CHANGED THE FMC TO CROSS SKIAY AT FL240 AND WAS FLYING THE PLANE SO AS TO CROSS THAT FIX. THE LESSON I LEARNED WAS I NEED TO MONITOR 'NEW GUYS' MORE CLOSELY.

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.