EMB170 flight crew reported amber EICAS message appeared and silenced the alert. The Message did not reappear until the next crew operated the aircraft on the following outbound flight.

Date: 2022-08 · Aircraft: EMB ERJ 170/175 ER/LR · Phase: cruise

Anomalies: aircraft-equipment-problem-critical|deviation-discrepancy-procedural-clearance|deviation-discrepancy-procedural-published-material-policy

Synopsis

EMB170 flight crew reported amber EICAS message appeared and silenced the alert. The Message did not reappear until the next crew operated the aircraft on the following outbound flight.

Narrative

The flight preparation was uneventful and as expected. The preflight walk-around and pre-flight checks were normal. The flight was uneventful before the EICAS message. Once the Amber EICAS message appeared we silenced the alert and the Pilot Flying (PF); Captain (CA) called for the Quick Reference Handbook (QRH). We both pulled out the QRH and I Pilot Monitoring (PM) read the QRH. The two-step checklist called for a cycle of the parking brake lever and to ensure it was correctly stowed after the cycle process. Once this was accomplished the alert did not immediately go away. The note below step one warns of a possible tire bursting on landing if the EICAS message does not go away. We proceeded to step two; which calls for a full flap landing. We prepared the numbers for a full flap landing and completed the checklist. Then the PM/First Officer (FO) looked through AOM 1 (Aircraft Operating Manual) and AOM 2 for any additional information on our braking and tires that could affect our landing or cause the situation. Nothing of note was found and within ten minutes the EICAS message went away. We proceeded with the full flap landing and did inform the Flight Attendants of the situation. However; both PF/Captain and the FO/PM agreed that since the message did go away; and that we had no other indication of the brakes being set we did not anticipate any issue and the EICAS message was an erroneous message. We landed in ZZZ1 with no issue. We did inform the next crew of what happened and me and the other Captain agreed since the message went away the next crew would take the plane to ZZZ2. Maintenance was not called. Before leaving ZZZ1 after a two-hour sit I received a call from maintenance control that the next crew had the same issue in flight that we did and [requested priority handling] into ZZZ2. From my experiences in the past; when maintenance control is called for a situation that happened in flight that went away; even with the running of a QRH checklist I've told not to write it up as the issue was no longer occurring. It is each Pilot in Command's (PIC's) responsibility to take all the information they are given and decide about the airworthiness and safety of their airplane. I decided it was not a maintenance issue since safety was never compromised and the message went away and the airplane landed normally; and everything was normal with the brakes. We did inform the next crew so they could make their own decision on their aircraft. They chose to go with the information given. The suggestion is more for me as PIC; I learned from this situation and next time I will call maintenance control and let them decide and not rely on previous experiences so from now on I will call.

Second reporter narrative

[Narrative contained no additional information.]

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.