Date: 201601
Local time of day: 0001-0600
Location: SLC.Airport, UT
Flight conditions: VMC
Light: Night
Aircraft: Medium Large Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ground SLC
Aircraft component: Aero Charts
Component problem: Design
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown; Time Pressure; Confusion; Distraction; Situational Awareness
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Incursion Taxiway
Detector: Person Air Traffic Control
When detected: Taxi
Result: Air Traffic Control Issued Advisory / Alert; Flight Crew Became Reoriented; Flight Crew FLC complied w / Automation / Advisory
Contributing factors: Chart Or Publication; Procedure; Airport
Primary problem: Chart Or Publication

Narrative: Pushed back from the B Concourse onto Taxiway H for de-ice. Ground Control cleared us to 34R de-ice pad via Taxiway H then Y. Just south of Taxiway H4; Ground Control told us to increase our taxi speed to allow for an aircraft exiting the 34R de-ice pad to taxi northbound on Taxiway H for takeoff on a south runway. Between H4 and H3; ground control told us we had missed Taxiway Y. We were issued an amended clearance to the 34R de-ice pad via H then H3 then Y. There were no conflicts with any aircraft on this route.The SLC 10-9 Jeppesen chart (dated 4 DEC 15; Effective 10 Dec) and the Company Airport Info does not show Taxiway H3 between Taxiway H and Y. They also do not show a large; lighted physical island between Taxiway H3 and spot 6Y in the 34R de-ice pad that separates Taxiways H and Y. There are also no NOTAMs issued for this discrepancy or advisories on the ATIS. Since there is no H3 depicted between Taxiway H and Y; my FO and I incorrectly interpreted the initial taxi clearance to join Taxiway Y from H at the point just south of Taxiway H3 primarily referencing the 34R De-ice Pad Inset on the 10-9 chart. If H3 and the island were depicted on the 10-9 chart; we would have reason to question that taxi route since H3 wasn't in the initial clearance. I was also distracted by Ground Control's request to taxi faster at the very point were Taxiway Y starts just south of H4 and had missed any lighted signs or surface markings while looking for the aircraft ATC was referencing down at the 34R de-ice pad. It was night and both the FO and I had never used the new 34R de-ice pad before.The 10-9 chart need to be updated to accurately reflect the current surface feature of the airfield. A NOTAM; ATIS advisory; 10-7; or FOIB/FOAB might also be helpful in the meantime. While it wasn't applicable to us; the Low-Vis Taxi Routes (10-9D; 10-9E) also do not show Taxiway H3 between Taxiway H and Y. They also do not show the large; lighted physical island between Taxiway H3 and spot 6Y in the 34R de-ice pad that separates Taxiways H and Y. This is a safety issue.




Synopsis: Flight crew was cleared to taxi on SLC Taxiways H; Y to de-ice pad 6Y but did not identify the H to Y Taxiway transition. After missing Taxiway Y; the crew was cleared H3 to Y but they could not identify the Taxiway H3 transition to Y off Runway 34R. The large physical island in the deice pad south of H3 and north of 6Y is not depicted on any airport or taxi diagram.