EMB ERJ Flight Crew reported a return to gate event was caused by communications problems and maintenance paperwork issues.
Synopsis
EMB ERJ Flight Crew reported a return to gate event was caused by communications problems and maintenance paperwork issues.
Narrative
We brought the aircraft into ZZZ that morning. After landing; we received a message saying 'LG NO DISPATCH'. (I noted the previous day there was a voided out write up of the same message.) Once we parked at the gate and shut down the engine and hydraulics; the message disappeared. However; the left main inboard brake was showing about 42 degrees while the outboard was showing 242 degrees. I decided to call it in and explain everything that happened. Maintenance Control said they will call contract maintenance because they think this is a break temperature sensor issue. I hold off on boarding until the issue is resolved in case it's something worse. Contract maintenance shows up; swaps out the sensor; which fixes the issue; grabs the maintenance logbook and goes to fill it out saying we are good to board. We board up; get the can back and it was showing what they did with it sign and dated. We close up; get permission to push back and we do. Halfway through pushing we pull up the take off data to load it into the MCDU; and it's showing 'aircraft out of service'. We set the brake and I call maintenance to ask what is going on. It is then they advice me there is an issue with the paperwork and we are not legal and to return to the gate until they get it corrected. We hang up; tell the FAs; passengers; ramp; Dispatch; and operations what is going on and we needing to return to gate. It takes about 15-20 minutes but we finally get parked back at our gate. I call maintenance again to get a better idea of the issue. They explain how contract Maintenance took the brake sensor off of another one of our aircraft; but messed up how they wrote it up in that aircraft's maintenance logbook; which is causing us to be illegal. We had no idea we were not legal until I called about the out of service message. Contract Maintenance came out; took our maintenance logbook. Once all the paperwork was in line; they brought back the logbook. There were no changes to our log book. We closed up and departed without further problems. When on a maintenance delay; we want to leave as soon as possible; but to prevent something like this happening again; we should check the takeoff data to verify no 'aircraft out of service' messages appear and that we receive numbers. Scenario like this; past departure time; we usually have the passenger count and the bag count before we are ready for it; (as long as it's auto close out) we can check to see if we are good or not.
Second reporter narrative
Upon landing at ZZZ; we got a 'LG NO DISPATCH' EICAS Message. Maintenance came out and fixed the issue. The logbook looked correct and we thought the plane had been returned to service. As we pushed off the gate; I sent for the takeoff numbers and it came back saying that the plane was out of service. The Captain called Maintenance again to find out that the paperwork was not completed correctly unbeknownst to us. To correct this; we had to return to the gate where Maintenance again came out and corrected the paperwork. At no time were we told that the paperwork was incorrect until we had already pushed off the gate and had called Maintenance again ourselves. In the case that a plane is out of service for a reason the crew would be unaware of; such as paperwork; the Dispatcher or Maintenance should contact the crew view ACARS or phone to let us know. When the can was signed and the Maintenance personnel there told us we were good to go; we had no way of knowing that the paperwork on the other end was messed up.
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.