2024-11 · NASA ASRS report 2187129
Air Carrier flight crew flying ERJ-170 aircraft reported loss of flap control during descent.
While on descent into ZZZ from ZZZ1; we were cleared to cross ZZZZZ at 13;000. At this point; we were at 19;000 and we had already gotten the ATIS and loaded; bugged; and briefed the ILS for Runway XXL. We started descending for ZZZZZ and as we were about to run the descent checklist; we noticed a 'flap low rate' awareness message appear. This message lasted for about 10 seconds. The Captain then deployed the speed brakes to begin slowing down; and about 5 seconds later; we had a 'flap fail' message appear on the EICAS. We identified and canceled and began running the QRH. We thoroughly went through the QRH and once we gathered and analyzed all available and pertinent information; we decided to [request priority handling] due to the fact our Vapp was close to max tire speed; and the weather conditions in ZZZ; which was reported wind around 300 @ 19 gusting 24 range as well as wet runways. As a result; we decided it would be best as well to change to Runway XXR for the added runway length. At this point; we established and communicated a plan; notified ATC we were [requesting priority handling] and requested the trucks to be rolled; notified the flight attendants; Dispatch; and passengers; and requested a long straight in final. As we were on the downwind; we ran the flap fail descent checklist and at around a 15 mile final we got configured and completed the flap fail landing checklist. We then continued to the runway; landed in the touchdown zone; and came to a stop on the runway. We got on the discrete frequency to talk to the trucks and advise them we would like them to check us out to make sure there was no issues; and after they thoroughly checked us out and advised us everything looked normal; we elected to taxi to the gate as the brake temps stayed in the green and there were no anomalies seen by rescue. The trucks followed us to the gate and we pulled into the gate without any further issues. Once we got to the gate; MX (Maintenance) was waiting for us and advised us the plane had been having flap issues. The Captain wrote the issue up; and the event ended there.
During the descent into ZZZ from ZZZ1 we had built bugged briefed the approach to Runway XXL. We were reaching the top of descent at 19000 to cross ZZZZZ at 13000; about to complete the descent checklist; and as we started to pitch down; we noticed 'Flap low rate' pop up momentarily and went away as we noticed it. I then pulled out about 1/4 speed brake to begin slowing down. About 4 seconds later the EICAS message 'FLAP FAIL' came up. We identified and canceled then began running the QRH. We had made no adjustments to the flaps so we had nowhere to 'return to previous position' so continued with the QRH. In the process of deciding whether to [request priority handling] we began retrieving landing data and coefficient for Flaps failed indicating 0; at 68xxx lbs we used 70;000 lbs numbers to get a VAPP of 182 with slats 3; flaps 0 and 6564 factored landing distance (1.83). We decided to [request priority handling] because of our proximity to Max tire speed and current weather in ZZZ 300@19 (ish) combined with a wet runway. We decided to make the change to Runway XXR for the added runway length for extra safety in slowing down with the wet conditions and high approach speed. We returned to establish and communicate a plan; [requested priority handling] with ATC and gave all pertinent information and requested trucks to be rolled for us and inspection after landing and stopping on the runway. Messaged Dispatch and notified them of flap failure and [request of priority handling]. Called flight attendants and notified them of the [priority handling]; flap failure and increased approach speed; I did not order a brace command; and told them we would be landing and stopping on the runway for inspection in case we got hot brakes from the faster approach speed. We returned to the QRH; requested a long straight in final. I discussed whether we should make an announcement with the FO; we decided to make one to brief them on the presence of the trucks and plan to stop on the runway after landing because of a technical issue with the plane and just using this as an added safety precaution. In the downwind I decided to extend the flaps to position 1 wait 10 seconds and return them to 0 in order to verify that they would extend slats which verified we were using the correct QRH and landing numbers as well as verify that the flaps were indeed failed because they had failed when we had made no adjustments to them. They operated as expected; flaps stayed at 0 but slats came to 3 which confirmed our numbers and plan. We finished the flap fail descent and then on a 12 mile final got configured and completed the Flap fail Landing checklist. We landed in the touchdown zone; rolled out and stopped on the runway. I pulled up the EICAS status page and checked our brake temps which were about 90ish and 120ish degrees Celsius a side; but still requested the fire trucks inspect the aircraft to make sure there wasn't anything going on we didn't have an indication of. There was not and we elected to taxi to our gate. Upon arriving to the gate; I wrote up the Flap fail and details of the event in the MX (Maintenance) report and called Dispatch then MX to inform them of the write up. Suggestions: The training we have received set us up wonderfully to be prepared and to handle this situation.
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.
Loading the flight search…
Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.
We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.
Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.
Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.