Date: 201706
Local time of day: 0601-1200
Location: IAH.Airport, TX
Flight conditions: IMC
Weather elements / visibility: Rain
Light: Daylight
Aircraft: EMB ERJ 170/175 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Climb
Airspace: Class B IAH
ATC / advisory: Tower IAH
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness; Workload
Second reporter function: Pilot Flying; First Officer
Anomaly: Deviation - Altitude Overshoot; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Became Reoriented; Flight Crew Executed Go Around / Missed Approach; Flight Crew Returned To Clearance
Contributing factors: Human Factors; Weather
Primary problem: Human Factors

Narrative: During a missed approach from Runway 8L ILS in IAH we incurred a 300 ft deviation. While on the ILS 8L the First Officer initiated a missed approach as a result [of] heavy rain causing him to lose sight of the runway. To the best of my recollections runway visibility as indicated by the ATIS was 3000 RVR. However; as [a] result of the heavy rain and the fact that the wipers were stopping half way and then continuing to full movement; caused the visibility to be reduced even more. While on short final the FO disconnected the auto pilot in preparation for landing after having the runway in sight. Following the missed approach; the autothrottle was disconnected; so the missed approach was done without autopilot and autothrottles. In addition; proper missed approach procedures were not followed resulting in many distractions during the missed approach. Immediately after the missed [approach] ATC instructed us to turn to a heading of 360. While we were turning ATC once again indicated a turn to a 360 heading; to which we replied that we were in the turn for 360 heading. Following the altitude deviation I took over the control from the FO [and] corrected the altitude. We continued on the assigned heading and returned to Runway 8L.  It's obvious that the first thing that we must correct is the missed approach procedure call out and a missed approach checklist. As a result of this event we all should incorporate refreshing the missed approach call out during the approach briefing. In addition; I feel I could have taken control much earlier from the FO to minimize or even prevent going above assigned altitude. I probably failed to recognize that the FO was a bit overwhelmed during the missed approach.


Second narrative: One mile from the airport the [moderate] rain became heavy rain and the visibility dropped. The Captain changed my windshield wipers from low to high when the wipers stopped in front of my line of sight for a few seconds; making me lose visual of the runway. Combined with the heavy rain and poor visibility about 100-80 ft off the runway I called go-around.Since the autothrottle came off when I pushed too [far] forward into max thrust; I got distracted looking at my airspeed trying not to overspeed the flaps; [and] by the time I looked at my altitude I had already busted my assigned altitude of 3000 ft [by] about 300 ft.


Synopsis: EMB-175 flight crew reported an altitude deviation occurred during a missed approach in heavy rain.