Narrative:

While performing new-hire IOE on the last round trip of a 3-day; I turned over FMS/ACARS entry to the trainee because he had been progressing well and doing a good job. After he finished; I looked over all of the settings and we checked the route to the release; which was for a SUMMT4 departure (departing 08R). Trainee was pilot flying; and after an uneventful departure; we were somewhere near vocal and with atl departure. ATC issued direct hyk VOR; followed by a stern warning about adhering to the clearance. I didn't get the hint at that point. We headed toward hyk; but it wasn't until the handoff and second warning that I began to wonder what we had done wrong. I picked up the pre departure clearance that we had printed from ACARS and saw that we had been issued an altered clearance for the NUGGT4 departure; but the pilot flying had briefed the SUMMT4 during the preflight checks; and I had not cross-checked the pre departure clearance to ensure accuracy. The controller stated that it hadn't caused an issue and that he wouldn't file a report; but left no doubt that he was unhappy about it. I thanked him for the heads-up and we changed frequencies; continuing the flight without further complications. Early in the course of IOE with this trainee; we had discussed clearance changes and how they were noted on ACARS pdcs. However; with the abundance of information that he was taking in over the next three days; that detail didn't stick with him. By failing to check the pre departure clearance from ACARS; I placed too much responsibility for accuracy with the trainee when I should have been overseeing every detail of his work. As PIC; I am responsible for adhering to the clearance whether I'm performing IOE or any other type of flight. I should ensure that I cross-check of the pre departure clearance/clearance to the filed plan on all flights; regardless of whether it is IOE; operator error; or just a normal line flight. This deviation was easily avoidable!

Related reports:

Google
 

Original NASA ASRS Text

Title: An aircraft departed ATL after receiving a revised PDC SID which included the NUGGT FOUR. The IOE crew failed to remove the SUMMT FOUR from the FMC and so had track deviation on departure.

Narrative: While performing new-hire IOE on the last round trip of a 3-day; I turned over FMS/ACARS entry to the trainee because he had been progressing well and doing a good job. After he finished; I looked over all of the settings and we checked the route to the release; which was for a SUMMT4 departure (departing 08R). Trainee was pilot flying; and after an uneventful departure; we were somewhere near VOCAL and with ATL departure. ATC issued direct HYK VOR; followed by a stern warning about adhering to the clearance. I didn't get the hint at that point. We headed toward HYK; but it wasn't until the handoff and second warning that I began to wonder what we had done wrong. I picked up the PDC that we had printed from ACARS and saw that we had been issued an altered clearance for the NUGGT4 departure; but the pilot flying had briefed the SUMMT4 during the preflight checks; and I had not cross-checked the PDC to ensure accuracy. The Controller stated that it hadn't caused an issue and that he wouldn't file a report; but left no doubt that he was unhappy about it. I thanked him for the heads-up and we changed frequencies; continuing the flight without further complications. Early in the course of IOE with this trainee; we had discussed clearance changes and how they were noted on ACARS PDCs. However; with the abundance of information that he was taking in over the next three days; that detail didn't stick with him. By failing to check the PDC from ACARS; I placed too much responsibility for accuracy with the trainee when I should have been overseeing every detail of his work. As PIC; I am responsible for adhering to the clearance whether I'm performing IOE or any other type of flight. I should ensure that I cross-check of the PDC/clearance to the filed plan on ALL flights; regardless of whether it is IOE; Operator Error; or just a normal line flight. This deviation was easily avoidable!

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.