CRJ200 crew does not comply with the kennedy 1 SID departing jfk.

Attributes
ACN	735906
Time
Date	200704
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : jfk.airport
State Reference	NY
Altitude	msl single value : 5000
Environment
Flight Conditions	Mixed
Weather Elements	Ice
Light	Night
Aircraft 1
Controlling Facilities	tracon : n90.tracon
Operator	common carrier : air carrier
Make Model Name	Regional Jet 200 ER&LR
Operating Under FAR Part	Part 121
Navigation In Use	other vortac
Flight Phase	climbout : intermediate altitude
Route In Use	departure sid : kennedy.1
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Experience	flight time last 90 days : 30 flight time total : 5000 flight time type : 2500
ASRS Report	735906
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Events
Anomaly	non adherence : published procedure non adherence : clearance other spatial deviation
Independent Detector	other controllera other flight crewa
Resolutory Action	controller : issued new clearance none taken : detected after the fact
Consequence	faa : reviewed incident with flight crew faa : assigned or threatened penalties
Supplementary
Problem Areas	Aircraft Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance

Narrative:

We were assigned the kennedy one departure utilizing the canarsie climb off runway 31L. The first officer and I checked the flight plan in the FMS and I briefed the departure. I utilized white data and backed it up with the VOR 2 bearing pointer while the first officer utilized green data (first mistake). As we departed I noticed the white data did not display the turn towards cri. I reverted to the VOR 2 pointer and proceeded towards cri. I then noticed the VOR 2 was not pointing to cri and I was about to cross the 039 degree radial. I disregarded the reliability of the pointer and made a turn towards cri based on the FMS plan map (second mistake). At this point ATC queried us about our deviation and gave us a heading. He discussed violating us but later said he would not send the report in. After reaching cruise altitude; I once again checked the FMS to see what went wrong and noticed that the incorrect runway; runway 13L was selected instead of 31L (third mistake). I have flown this procedure many times in the past without any issues. My decision to fly it differently than I have in the past; using green data; caused this deviation. This departure has been and still is a serious issue for my air carrier as ATC reminded me; and I thought I was ready for it. I failed this time. However; I will not make this mistake twice.supplemental information from acn 735997: we departed jfk on the kennedy 1 cri climb. Captain was the PF. He was using the FMS while I was in green data. We made turn to cri; but we soon got off course. We later discovered that the wrong runway was entered in the FMS by captain. At the gate I mentioned that I fly this departure in green data. The captain responded; I could put green data on my side while he put white data on his side; mistake (1). We discussed the information and he said it was only a recommendation; which I discovered later was a mistake (2). We reviewed the FMS routing but we did not catch the wrong runway was entered. Earlier the captain asked me which runway and I said runway 31L and assumed it was put in correctly; mistake (3). I now make sure to pay particular attention to the runway when reviewing the routing. I also make sure green data is used on this departure.

Original NASA ASRS Text

Title: CRJ200 CREW DOES NOT COMPLY WITH THE KENNEDY 1 SID DEPARTING JFK.

Narrative: WE WERE ASSIGNED THE KENNEDY ONE DEP UTILIZING THE CANARSIE CLB OFF RWY 31L. THE FO AND I CHKED THE FLT PLAN IN THE FMS AND I BRIEFED THE DEP. I UTILIZED WHITE DATA AND BACKED IT UP WITH THE VOR 2 BEARING POINTER WHILE THE FO UTILIZED GREEN DATA (FIRST MISTAKE). AS WE DEPARTED I NOTICED THE WHITE DATA DID NOT DISPLAY THE TURN TOWARDS CRI. I REVERTED TO THE VOR 2 POINTER AND PROCEEDED TOWARDS CRI. I THEN NOTICED THE VOR 2 WAS NOT POINTING TO CRI AND I WAS ABOUT TO CROSS THE 039 DEG RADIAL. I DISREGARDED THE RELIABILITY OF THE POINTER AND MADE A TURN TOWARDS CRI BASED ON THE FMS PLAN MAP (SECOND MISTAKE). AT THIS POINT ATC QUERIED US ABOUT OUR DEV AND GAVE US A HDG. HE DISCUSSED VIOLATING US BUT LATER SAID HE WOULD NOT SEND THE RPT IN. AFTER REACHING CRUISE ALT; I ONCE AGAIN CHKED THE FMS TO SEE WHAT WENT WRONG AND NOTICED THAT THE INCORRECT RWY; RWY 13L WAS SELECTED INSTEAD OF 31L (THIRD MISTAKE). I HAVE FLOWN THIS PROC MANY TIMES IN THE PAST WITHOUT ANY ISSUES. MY DECISION TO FLY IT DIFFERENTLY THAN I HAVE IN THE PAST; USING GREEN DATA; CAUSED THIS DEVIATION. THIS DEP HAS BEEN AND STILL IS A SERIOUS ISSUE FOR MY ACR AS ATC REMINDED ME; AND I THOUGHT I WAS READY FOR IT. I FAILED THIS TIME. HOWEVER; I WILL NOT MAKE THIS MISTAKE TWICE.SUPPLEMENTAL INFO FROM ACN 735997: WE DEPARTED JFK ON THE KENNEDY 1 CRI CLB. CAPT WAS THE PF. HE WAS USING THE FMS WHILE I WAS IN GREEN DATA. WE MADE TURN TO CRI; BUT WE SOON GOT OFF COURSE. WE LATER DISCOVERED THAT THE WRONG RWY WAS ENTERED IN THE FMS BY CAPT. AT THE GATE I MENTIONED THAT I FLY THIS DEP IN GREEN DATA. THE CAPT RESPONDED; I COULD PUT GREEN DATA ON MY SIDE WHILE HE PUT WHITE DATA ON HIS SIDE; MISTAKE (1). WE DISCUSSED THE INFO AND HE SAID IT WAS ONLY A RECOMMENDATION; WHICH I DISCOVERED LATER WAS A MISTAKE (2). WE REVIEWED THE FMS ROUTING BUT WE DID NOT CATCH THE WRONG RWY WAS ENTERED. EARLIER THE CAPT ASKED ME WHICH RWY AND I SAID RWY 31L AND ASSUMED IT WAS PUT IN CORRECTLY; MISTAKE (3). I NOW MAKE SURE TO PAY PARTICULAR ATTENTION TO THE RWY WHEN REVIEWING THE ROUTING. I ALSO MAKE SURE GREEN DATA IS USED ON THIS DEP.

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