B737-700
Flight Crew Last 90 Days 159; Flight Crew Type 159
Human-Machine Interface; Training / Qualification
Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Air Traffic Control Issued Advisory / Alert; Air Traffic Control Issued New Clearance; Flight Crew Returned To Clearance
Human Factors; Manuals
I am in the EFB test program using the iPad instead of paper charts. When I selected a chart that expired that day; I got a red flag; warning me the chart had expired. Since we were after midnight Zulu; I thought I needed to use the next chart. I convinced my First Officer we should also changeover the FMC database. We had been cleared through PDC via ACARS to fly the COAST 5 Departure; but we failed to notice the numbering difference and loaded and briefed the COAST 6. Because both the charts and FMC were changed; we did not detect any errors during the route briefing. The COAST 6 Departure is significantly different from the COAST 5; so when we flew the COAST 6 with LNAV; we deviated from the COAST 5 routing. Center asked us about our routing and reassigned us the specific route points to fly.We made two errors: 1) we used charts and the FMC database too early (the changeover time is 0900Z; not 0000Z; as specified in the AOM); and 2) we failed to detect the numbering change of the assigned SID (COAST 5 versus COAST 6). Prevention: 1) All 'effective' and 'expired' dates should include the 0900Z time on both paper and electronic charts. 2) EFB training should include a lesson on the red flag warnings; and remind students of the 0900Z standard changeover time. 3) Crews must brief the name and NUMBER of the cleared departure or approach procedure.
B737 Captain reports changing to new charts in his EFB before the official change over time (0900Z); then changing the FMC database to match. A track deviation occurs when the Coast 6 departure is flown instead of the cleared Coast 5.