Date: 201312
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Aircraft: EMB ERJ 170/175 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Taxi
Aircraft component: Air Data Computer
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Troubleshooting; Human-Machine Interface; Confusion; Communication Breakdown
Second reporter function: First Officer; Pilot Not Flying
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural MEL / CDL; Deviation / Discrepancy - Procedural Maintenance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Aircraft In Service At Gate
Result: General Maintenance Action
Contributing factors: Aircraft; Human Factors
Primary problem: Human Factors

Narrative: After deicing and pushback we started the Number One Engine. After calling for the After Start Checklist; I noticed a cyan advisory message on the EICAS and called for the QRH. The First Officer took out the QRH and began looking up the advisory message on the EICAS. I was supervising him reading through the QRH and the action to be taken. We reverted the affected ADS system as per the QRH and continued on our way.The flight continued without event to the destination. After landing we shut down the engines and the message extinguished. I called Dispatch to let Maintenance know that we need them to come out to the aircraft. I wrote up that we had 'ADS system 2 fail' on the EICAS. Maintenance came out and said they had to do an engine run on the engine to see if they could duplicate the message. They said that they had multiple maintenance messages about ADS heater faults on the Central Maintenance Computer. I stayed on the airplane and talked with them really just because I had nothing better to do; and after starting the engine the cyan message came back up that said 'ADS probe 2 fail'. After thinking about it for a bit I asked the First Officer what message did he think we had on the EICAS. We both agreed it was definitely 'ADS system 2 fail'. After thinking about it after a while I grabbed the QRH and began looking through it. I realized it could not be 'ADS system 2 fail' because that was an amber caution message; and the only cyan message related to the ADS system was 'ADS probe 2 fail' which in the QRH said simply 'do not takeoff'. I began to realize after much discussion with the First Officer that I thought we ran the wrong QRH procedure before takeoff. We would never have known we did anything wrong if we didn't stick around to see that 'ADS probe 2 fail' message on the EICAS after Maintenance started the engine.I should've paid more attention to the QRH procedure that the First Officer was reading. We should've had better CRM between each other. I know that there are procedures associated with some cyan messages; but complacency definitely played a factor simply because the message was cyan. I think we both assumed that it wasn't a big deal. Also; I believe that we should've contacted Maintenance Control per the 'book'. That would've helped to catch the error.


Second narrative: The QRH should be in color [matching the color of the associated EICAS warning]. This would help identify if the correct message is being used on the checklist I should have visually shown the Captain the procedure in the QRH in addition to verbally stating it for his confirmation.


Synopsis: When the ERJ-170 flight crew inadvertently utilized the wrong checklist in response to an EICAS Air Data System message received just prior to takeoff they believed they had corrected the problem. After maintenance action taken at their destination they realized their error.