A300 flight crew fails to comply with crossing restr on descent for jfk.

Attributes
ACN	602323
Time
Date	200312
Day	Wed
Local Time Of Day	1801 To 2400
Place
Locale Reference	intersection : hoggs
State Reference	NY
Altitude	msl bound lower : 19000 msl bound upper : 19500
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Controlling Facilities	artcc : zny.artcc
Operator	common carrier : air carrier
Make Model Name	A300
Operating Under FAR Part	Part 121
Navigation In Use	other
Flight Phase	descent : approach
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : flight engineer pilot : atp
Experience	flight time last 90 days : 45 flight time total : 6000 flight time type : 300
ASRS Report	602323
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Events
Anomaly	altitude deviation : crossing restriction not met non adherence : clearance
Independent Detector	other flight crewa
Resolutory Action	none taken : anomaly accepted
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	Aircraft Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

While descending on the camrm four arrival into jfk I was working on a problem with the airplane. I am the first officer and was the PNF. My side FMS (#2) was x-talking to #1 FMS, but the FMC (flight management computer) was not computing any data. Earlier I answered a radio call to cross hoggs intersection at FL190. The captain set this altitude and I confirmed it. I watched him type this restr into his FMS as he was flying in profile mode. I went back to working on my FMS problems. The next thing I knew was ATC asked if we would meet our restr. He told me to answer yes. I looked at my navigation display to see we were at 23000 ft with 6 mi to go. He dove the airplane but still did not get to 19000 ft till a mi or two past hoggs. For some reason his FMC did not compute the crossing correctly. We wrote the FMS up on the ground and after re-racking they tested ok. Problem 1) captain not backing up FMS with raw data, also watching what I was doing and not flying the airplane. Problem 2) I should have not worried about my FMS as he was flying and his was working, better than mine anyway.

Original NASA ASRS Text

Title: A300 FLT CREW FAILS TO COMPLY WITH XING RESTR ON DSCNT FOR JFK.

Narrative: WHILE DSNDING ON THE CAMRM FOUR ARR INTO JFK I WAS WORKING ON A PROB WITH THE AIRPLANE. I AM THE FO AND WAS THE PNF. MY SIDE FMS (#2) WAS X-TALKING TO #1 FMS, BUT THE FMC (FLT MGMNT COMPUTER) WAS NOT COMPUTING ANY DATA. EARLIER I ANSWERED A RADIO CALL TO CROSS HOGGS INTXN AT FL190. THE CAPT SET THIS ALT AND I CONFIRMED IT. I WATCHED HIM TYPE THIS RESTR INTO HIS FMS AS HE WAS FLYING IN PROFILE MODE. I WENT BACK TO WORKING ON MY FMS PROBS. THE NEXT THING I KNEW WAS ATC ASKED IF WE WOULD MEET OUR RESTR. HE TOLD ME TO ANSWER YES. I LOOKED AT MY NAV DISPLAY TO SEE WE WERE AT 23000 FT WITH 6 MI TO GO. HE DOVE THE AIRPLANE BUT STILL DID NOT GET TO 19000 FT TILL A MI OR TWO PAST HOGGS. FOR SOME REASON HIS FMC DID NOT COMPUTE THE XING CORRECTLY. WE WROTE THE FMS UP ON THE GND AND AFTER RE-RACKING THEY TESTED OK. PROB 1) CAPT NOT BACKING UP FMS WITH RAW DATA, ALSO WATCHING WHAT I WAS DOING AND NOT FLYING THE AIRPLANE. PROB 2) I SHOULD HAVE NOT WORRIED ABOUT MY FMS AS HE WAS FLYING AND HIS WAS WORKING, BETTER THAN MINE ANYWAY.

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.