Narrative:

Prior to the event the dispatch paperwork was reviewed; clearance printed via pre departure clearance and entered into the FMC. The pre departure clearance clearance showed that we were assigned the PATSS2 RNAV departure. However; the dispatch paperwork was filed with our first point being direct to patss. Upon taxi; all checklists were completed and the runway verified on the legs page of the FMS display. After initial rotation; shortly after a positive rate was established; I noticed on the screen that the first point depicted was approximately 35 miles away; which seemed odd for an RNAV departure. I immediately asked the captain (who was the pilot not flying) what our first fix was. He asked me if I doubted the navigation; and then realized that the first point on our route of flight was not in accordance with the published RNAV departure (PATSS2). We should have been in a left turn direct to tjayy; but the route shown on the navigation screen showed direct patss.all this was realized prior to about 600 AGL. I was still hand flying at this point and began to turn the aircraft left toward tjayy in an attempt to recover the RNAV course; assuming the captain would quickly select the departure. If it was done quickly; the departure could have been selected and the tjayy or brrro waypoint brought up before the aircraft was out of the turn I had initiated. But; then there was some confusion between us on which way the RNAV departure turned off the runway; which severely delayed our course correction efforts.the tower handed us off to boston departure control; and we checked in with our problem; stating that we were on a heading toward patss. Departure gave us a heading back to the right (reversing the turn); and very soon after (less than 30 seconds) directed us to proceed direct to patss. At no time did we receive any conflicting traffic advisories or warnings (either from TCAS or from ATC) or terrain/obstruction warnings (either automated or from ATC). We assured that we were in no immediate danger due to course deviation and completed the normal takeoff profile.after programming the flight route in the FMC at the gate; we verified the waypoints and mileage against the flight plan. However; since the printed flight plan did not include the points on the PATSS2 RNAV departure; we overlooked the fact that the departure was not correctly selected. On the taxi; per the checklist; we verified the assigned runway (22R) had been correctly selected and was depicted at the top of the legs page. However; the last of the three items on that checklist item (runway/heading/first fix); while verbally stated; was incorrect. When the first fix; 'patss' was verbally stated in the checklist response; neither one of us noticed the problem nor verified it against the published chart. The new procedure in use at several other airports; where ATC and the flight crew state and read back the first point of the RNAV departure in the takeoff clearance; is excellent. There is no doubt we caused the error by not correctly verifying the points against the chart. But; as a final check; having the tower force you to read back the first fix in the takeoff clearance is a policy that should become standard nationwide.

Related reports:

Google
 

Original NASA ASRS Text

Title: A CRJ-900 flight crew failed to program the PATTS TWO RNAV SID off Runway 22R at BOS into their FMS. After takeoff Departure Control was able to clear them direct to PATTS; avoiding conflicts with other departures.

Narrative: Prior to the event the dispatch paperwork was reviewed; clearance printed via PDC and entered into the FMC. The PDC clearance showed that we were assigned the PATSS2 RNAV departure. However; the dispatch paperwork was filed with our first point being direct to PATSS. Upon taxi; all checklists were completed and the runway verified on the LEGS page of the FMS display. After initial rotation; shortly after a positive rate was established; I noticed on the screen that the first point depicted was approximately 35 miles away; which seemed odd for an RNAV departure. I immediately asked the Captain (who was the pilot not flying) what our first fix was. He asked me if I doubted the navigation; and then realized that the first point on our route of flight was not in accordance with the published RNAV departure (PATSS2). We should have been in a left turn direct to TJAYY; but the route shown on the NAV screen showed direct PATSS.All this was realized prior to about 600 AGL. I was still hand flying at this point and began to turn the aircraft left toward TJAYY in an attempt to recover the RNAV course; assuming the Captain would quickly select the departure. If it was done quickly; the departure could have been selected and the TJAYY or BRRRO waypoint brought up before the aircraft was out of the turn I had initiated. But; then there was some confusion between us on which way the RNAV departure turned off the runway; which severely delayed our course correction efforts.The Tower handed us off to Boston Departure Control; and we checked in with our problem; stating that we were on a heading toward PATSS. Departure gave us a heading back to the right (reversing the turn); and very soon after (less than 30 seconds) directed us to proceed direct to PATSS. At no time did we receive any conflicting traffic advisories or warnings (either from TCAS or from ATC) or terrain/obstruction warnings (either automated or from ATC). We assured that we were in no immediate danger due to course deviation and completed the normal takeoff profile.After programming the flight route in the FMC at the gate; we verified the waypoints and mileage against the flight plan. However; since the printed flight plan did not include the points on the PATSS2 RNAV departure; we overlooked the fact that the departure was not correctly selected. On the taxi; per the checklist; we verified the assigned Runway (22R) had been correctly selected and was depicted at the top of the LEGS page. However; the last of the three items on that checklist item (runway/heading/first fix); while verbally stated; was incorrect. When the first fix; 'PATSS' was verbally stated in the checklist response; neither one of us noticed the problem nor verified it against the published chart. The new procedure in use at several other airports; where ATC and the flight crew state and read back the first point of the RNAV departure in the takeoff clearance; is excellent. There is no doubt we caused the error by not correctly verifying the points against the chart. But; as a final check; having the Tower force you to read back the first fix in the takeoff clearance is a policy that should become standard nationwide.

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