CL65 flight crew fails to make crossing restr during descent.

Attributes
ACN	576675
Time
Date	200303
Day	Tue
Local Time Of Day	1201 To 1800
Place
Locale Reference	intersection : harty
State Reference	PA
Altitude	msl bound lower : 23000 msl bound upper : 27000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zny.artcc tower : bfi.tower
Operator	common carrier : air carrier
Make Model Name	Regional Jet CL65, Undifferentiated or Other Model
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
Experience	flight time last 90 days : 180 flight time total : 15000 flight time type : 2000
ASRS Report	576675
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : commercial pilot : multi engine pilot : instrument
Experience	flight time last 90 days : 190 flight time total : 6000 flight time type : 1700
ASRS Report	576866
Events
Anomaly	altitude deviation : crossing restriction not met non adherence : clearance
Independent Detector	other controllera other flight crewa
Resolutory Action	controller : issued new clearance
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance

Narrative:

We were at cruise at FL270. We were given instructions to cross harty intersection at FL230. FL230 was entered into the FMS for vertical navigation, but entered for stw VOR, which was the next fix. ATC asked if we were going to make restr, and I responded yes and we were descending at 2700 FPM. It was then we realized we had just passed harty intersection. Controller came back to say that we had just passed harty. I then explained briefly the error. I asked if we had created a problem. Controller replied 'no problem' and then handed us off. Looking back, I had entered information on wrong line on FMS, first officer 'verified' it. Buttons on FMS don't always line up well with text, but still we should have 'read' it. No excuse -- just an explanation!

Original NASA ASRS Text

Title: CL65 FLT CREW FAILS TO MAKE XING RESTR DURING DSCNT.

Narrative: WE WERE AT CRUISE AT FL270. WE WERE GIVEN INSTRUCTIONS TO CROSS HARTY INTXN AT FL230. FL230 WAS ENTERED INTO THE FMS FOR VERT NAV, BUT ENTERED FOR STW VOR, WHICH WAS THE NEXT FIX. ATC ASKED IF WE WERE GOING TO MAKE RESTR, AND I RESPONDED YES AND WE WERE DSNDING AT 2700 FPM. IT WAS THEN WE REALIZED WE HAD JUST PASSED HARTY INTXN. CTLR CAME BACK TO SAY THAT WE HAD JUST PASSED HARTY. I THEN EXPLAINED BRIEFLY THE ERROR. I ASKED IF WE HAD CREATED A PROB. CTLR REPLIED 'NO PROB' AND THEN HANDED US OFF. LOOKING BACK, I HAD ENTERED INFO ON WRONG LINE ON FMS, FO 'VERIFIED' IT. BUTTONS ON FMS DON'T ALWAYS LINE UP WELL WITH TEXT, BUT STILL WE SHOULD HAVE 'READ' IT. NO EXCUSE -- JUST AN EXPLANATION!

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.