Narrative:

We were filed fll BEECH3 bahma...rajay A555. The pre departure clearance cleared us - BEECH3 bahma zqa -. During the preflight I checked the pre departure clearance against the filed route and against the FMC. Noticing the change; I searched the enroute charts to verify the difference. Somehow I went into the chart looking for rajay instead of zqa; and I believe what happened was that I noticed rajay was on A555; so I assumed it was one of those pre departure clearance changes that does not change the route at all; just highlights a point along the already filed route. Even when I determine that such a pre departure clearance change is the case; I always enter it that way (as listed in the pre departure clearance) in the FMC and note the change (whether it is an actual change in the route or not) during my clearance briefing. For some reason; I broke my routine this time; did not enter the pre departure clearance change (as I had mistakenly concluded there was no actual change to the route) and the pre departure clearance change to fly over zqa was not caught prior to takeoff. Enroute to rajay; ATC queried us regarding our clearance and informed us we should have been going to zqa. I see two ways to mitigate these types of pre departure clearance errors:1) first officers should always enter the pre departure clearance exactly as shown in the FMC; even if a change is clearly no change at all; just breaking out a waypoint on an already filed airway.2) the pre departure clearance change notation could be cleaned up and made clearer. Also; pre departure clearance changes that do not actually change the route at all should be eliminated. Certainly no excuse; but I think two factors led me to make this error. One; of course; was going into the enroute chart looking for the wrong waypoint (rajay vice zqa). The other was having had quite a few pre departure clearance changes recently that did not change the actual filed route at all. That and perhaps being slightly rushed led me to be satisfied that there was no actual route change this time and to not change the FMC routing - first time I ever did that; I believe. Completely my fault and lesson learned. Proper procedures would have caught my mistake if followed.

Related reports:

Google
 

Original NASA ASRS Text

Title: B737 flight crew reports a track deviation departing FLL due to missing a revised segment in their PDC.

Narrative: We were filed FLL BEECH3 BAHMA...RAJAY A555. The PDC cleared us - BEECH3 BAHMA ZQA -. During the preflight I checked the PDC against the filed route and against the FMC. Noticing the change; I searched the enroute charts to verify the difference. Somehow I went into the chart looking for RAJAY instead of ZQA; and I believe what happened was that I noticed RAJAY was on A555; so I assumed it was one of those PDC changes that does not change the route at all; just highlights a point along the already filed route. Even when I determine that such a PDC change is the case; I always enter it that way (as listed in the PDC) in the FMC and note the change (whether it is an actual change in the route or not) during my clearance briefing. For some reason; I broke my routine this time; did not enter the PDC change (as I had mistakenly concluded there was no actual change to the route) and the PDC change to fly over ZQA was not caught prior to takeoff. Enroute to RAJAY; ATC queried us regarding our clearance and informed us we should have been going to ZQA. I see two ways to mitigate these types of PDC errors:1) First officers should always enter the PDC exactly as shown in the FMC; even if a change is clearly no change at all; just breaking out a waypoint on an already filed airway.2) The PDC change notation could be cleaned up and made clearer. Also; PDC changes that do not actually change the route at all should be eliminated. Certainly no excuse; but I think two factors led me to make this error. One; of course; was going into the enroute chart looking for the wrong waypoint (RAJAY vice ZQA). The other was having had quite a few PDC changes recently that did not change the actual filed route at all. That and perhaps being slightly rushed led me to be satisfied that there was no actual route change this time and to not change the FMC routing - first time I ever did that; I believe. Completely my fault and lesson learned. Proper procedures would have caught my mistake if followed.

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