Date: 201606
Local time of day: 1801-2400
Location: ZDC.ARTCC, VA
Aircraft: Large Transport
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZDC
ATC / advisory: Center ZDC
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Human-Machine Interface; Situational Awareness; Confusion
Second reporter function: Pilot Flying
Anomaly: Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance
Detector: Person Air Traffic Control
Result: Air Traffic Control Issued New Clearance; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: ATC Equipment / Nav Facility / Buildings; Procedure; Chart Or Publication
Primary problem: Procedure

Narrative: Charlotte International Airport started new procedures with a dual flow departure into ZDC ARTCC. Automation Adapted Departure Arrival Routes (ADARs) were put in; where if a dispatcher filed a wrong route; the automation piece would capture it and the tower (CLT) would issue the proper routing. Aircraft X had [Route X] in the computer; which is the proper routing. However; at the RDU VORTAC; the aircraft took a turn towards FKN VORTAC. I asked him what his FMS had; it was RDU [Route Y]; which is the old preferred routing [to destination].There was no loss of separation with any aircraft or airspace. However this could be a problem in the future. I'm filing to see where the lapse was. CLT tower should've issued the preferred routing. Or the pilots or dispatch put it wrong into the aircraft's FMS. This needs to be addressed. There are over 160 departures daily with these new SIDs and the new routing afterwards.


Second narrative: We entered our filed route in the FMC and confirmed the route via a careful read back per company policy; with emphasis on the new SID that was recently implemented and neither of us had flown. Unfortunately; during the course of cross checking our planned route; we missed the revised segment on the clearance that changed our route after the final fix on the SID (RDU). We proceeded via the filed jet route; which we have used for some time rather than direct to the new fix/route per the revised segment. We were corrected by the controller; who commented that we were not supposed to use the 'old' route anymore. No TCAS or traffic conflict occurred to the best of my knowledge.This was a simple human error - we both missed the revised segment on the PDC printout. Contributing to the error was our effort in diligently checking the new departure procedure therefore failing to notice the revised routing AFTER the SID.We frequently receive 'revised segments' that contain NO change to the filed route - sort of an electronic version of 'crying wolf.' Also; we have been inundated with changes in navigation procedures (some poorly designed) in and out of our hub; including significant lateral and vertical profile changes. Staying abreast of all the navigation procedure changed has been challenging.


Synopsis: ATC controller reported an aircraft flying the wrong departure route; and the pilot reported that they had not noticed the revised routing and failed to enter it into their FMC.