EMB 170/175 flight crew reported a FLAP FAIL EICAS Message on approach. After configuring the aircraft; the flight crew continued to landing.
Synopsis
EMB 170/175 flight crew reported a FLAP FAIL EICAS Message on approach. After configuring the aircraft; the flight crew continued to landing.
Narrative
We were flying the RNAV GPS XXR approach to ZZZ. I was the Pilot Flying and when calling for flaps 1 we got the FLAP FAIL EICAS and noticed that we had Slats 3 and Flaps 0. We went around and advised ATC of the situation/[requested priority handling] and got delayed vectors. We ran the appropriate QRH and The Captain notified the Flight Attendants of the situation I continued to fly the airplane while The Captain set us up for an approach to XXL. We shot the approach and landed on XXL with Slats 3 and Flaps 0. I conducted the landing and The Captain took control at around 60 kts. and stopped the airplane on the runway. Due to the high brake temperatures we elected to remain on the runway and have the airport fire trucks inspect the brakes. After they inspected them we taxied off the runway and remained on the taxiway to allow the brakes to cool down to a safe temperature before returning to the gate. Once they cooled to a safe temperature we taxied to the gate with the fire trucks following to continuously monitor the airplane.
Second reporter narrative
Configuring for landing from Flaps UP to Flaps 1; we received a FLAP FAIL EICAS Message. Following the QRH procedure; we attempted a reset by selecting the prior flaps setting (UP). The FLAP FAIL EICAS Message cleared until Flaps 1 was re selected as directed by the QRH for FLAP FAIL. Further following the QRH procedure; priority handling was requested due to the excessive speed that a Flaps 0/Slats 3 would require. Given the increased potential for a brake overheat event; Crash Fire Rescue (CFR) was requested to be close to assist the crew in handling any potential complications that might have arisen. The Cabin Crew was briefed via the all call button and told that no brace command would be issued. Since we were very close to landing before the event occurred; they stated that the cabin was already secured and that they needed no further time to prepare. The FLAP FAIL DESCENT checklist was completed and the ILS to ZZZ XXL was requested for additional stopping length. The aircraft was configured early and the FLAP FAIL landing checklist was completed the approach and landing went forward without issue. Touchdown was smooth and maximum effort braking was accomplished along with max reverse thrust. The aircraft was brought to a stop on the runway adjacent to the taxiway to allow CFR to approach and assist in an obstacle free area. CFR reported no notable damage to the aircraft was observed.At about this time; we received an expected BRAKE OVERHEAT EICAS message. We remained on the runway until the brake temperatures indicated on our MFDs stopped climbing from their peak and started to decrease. In the heading that the aircraft was facing after landing (runway heading); the winds to help cool the brakes were being blocked by the number 1 engine. As Pilot in Command (PIC); I elected to vacate the runway to an adjacent taxiway to get the aircraft turned into a direction that facilitated better exposure to the prevailing wind to help cool the brakes until the BRAKE OVERHEAT EICAS message extinguished. Once the BRAKE OVERHEAT message extinguished; we contacted ZZZ Ground Control for an uneventful taxi to the assigned gate. Passengers were deplaned without delay and dispatch/maintenance were contacted immediately following the final passenger deplaning.
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.