Narrative:

After reviewing the logbook for aircraft X. I proceeded with the rest of my preflight procedure; which was to include looking at all messages displayed on the EICAS. I came across an advisory message antiskid off on the EICAS; which had off displayed in amber in the antiskid button with the switch on and a discrete light antiskid displayed on the upper overhead panel. I have never seen this message or lights on any aircraft; including aircraft X in the past. Because I had never seen this before; I called maintenance control and asked about the message. Mx (maintenance) control had me release the parking brake; and the EICAS message and off and antiskid lights extinguished. The mx controller said this was normal and that the message would go out after pushback with the brakes released. We were almost 45 minutes late for a pushback due to late loading. We pushed; and after engine start; the ground crew advised me to set the parking brake; which I complied with. Upon setting the parking brake; the antiskid off EICAS; antiskid button off; and the antiskid discrete lights all illuminated. This left the airplane with two advisory level EICAS messages. I pulled out the crew deferral checklist and followed it; because we had pushed back; we were now onto the QRH (quick reference handbook) and the MEL/cdl (minimum equipment list/configuration deviation list). I quickly looked up antiskid in the aircraft X MEL (minimum equipment list); and it was not flight crew deferrable. I then told the ground person to stay with the airplane because we had a maintenance issue. I first called mx control again to notify them of the issue. After explaining the issue; mx control told me to release the parking brake; I did; and all EICAS messages and lights extinguished. Mx control told me this was normal and that I should depart. However; as I explained; I could not take the aircraft out without mx looking at it; because I had never seen these messages; nor do our MEL/cdl book; gom; or fcom (flight crew operations manual) allow us to depart with an issue; other than a status message. After about 25 minutes of discussing the issue; I told mx control we were going to go back into the gate. As the ground people were getting ready for us to power back into the gate; I decided to call the chief pilot. I explained the exact situation to the chief pilot; but was told the same thing; that messages were normal and that I should depart. I declined to depart and went into the gate. After safely parking at the gate; I called the chief pilot again. I explained I had opted to have mx look over the airplane. I also informed the chief pilot that; the first officer and I would be comfortable taking the airplane to ZZZ1; provided we had written documentation that the messages were normal. (Much like the ACARS messages on the EICAS screen on some airplanes a year or so ago. The message was part of the coi; indicating the message was a nuisance and should be disregarded.) the chief pilot told me that is what the mx representatives were doing. I took a picture of the log page after the mx representatives had signed it off. The first officer and I both agreed that the entry was sufficient to allow us to depart. We departed without further incident; except the same EICAS message; and two discrete lights were present with the parking brake set and would extinguish after the parking brake was released. Enroute to ZZZ1; I looked through both logbooks again; and was surprised to see that the antiskid off issue had been written up twice before in the days before this incident. The first write up had the antiskid system deferred. With a corrective action the following flight day of changing a control unit. Another day later; the same write up occurred with a return to the gate with a revision by the captain; of entered in error. Upon reviewing the logbooks; a second time and discovering I had missed the history of the same messages; I felt that I had departed in error from ZZZ. Welanded without incident in ZZZ1 and parked; I made another entry into the aircraft logbook about the antiskid off EICAS and associated discrete lights.first; make sure to more adequately review the aircraft write-ups to establish an aircraft history. Second; do not cave to pressure from management or mx control to depart with a discrepancy. Additionally; mx control informed us that according to the mx manual; the messages were considered normal; however; this condition was in no way normal; which makes the mx manuals and flight crew manuals in a probable disagreement.

Google
 

Original NASA ASRS Text

Title: B767 pilot encountered advisory message after pushback.

Narrative: After reviewing the logbook for Aircraft X. I proceeded with the rest of my preflight procedure; which was to include looking at all messages displayed on the EICAS. I came across an advisory message ANTISKID OFF on the EICAS; which had OFF displayed in amber in the Antiskid Button with the switch on and a discrete light ANTISKID displayed on the upper overhead panel. I have never seen this message or lights on any aircraft; including Aircraft X in the past. Because I had never seen this before; I called Maintenance Control and asked about the message. MX (Maintenance) Control had me release the parking brake; and the EICAS message and OFF and ANTISKID lights extinguished. The MX Controller said this was normal and that the message would go out after pushback with the brakes released. We were almost 45 minutes late for a pushback due to late loading. We pushed; and after engine start; the ground crew advised me to set the parking brake; which I complied with. Upon setting the parking brake; the ANTISKID OFF EICAS; Antiskid button OFF; and the ANTISKID discrete lights all illuminated. This left the airplane with two Advisory Level EICAS Messages. I pulled out the Crew Deferral Checklist and followed it; because we had pushed back; we were now onto the QRH (Quick Reference Handbook) and the MEL/CDL (Minimum Equipment List/Configuration Deviation List). I quickly looked up ANTISKID in the Aircraft X MEL (Minimum Equipment List); and it was not flight crew deferrable. I then told the ground person to stay with the airplane because we had a maintenance issue. I first called MX Control again to notify them of the issue. After explaining the issue; MX Control told me to release the Parking Brake; I did; and all EICAS Messages and lights extinguished. MX Control told me this was normal and that I should depart. However; as I explained; I could not take the aircraft out without MX looking at it; because I had never seen these messages; nor do our MEL/CDL Book; GOM; or FCOM (Flight Crew Operations Manual) allow us to depart with an issue; other than a Status Message. After about 25 minutes of discussing the issue; I told MX Control we were going to go back into the gate. As the ground people were getting ready for us to power back into the gate; I decided to call the Chief Pilot. I explained the exact situation to the Chief Pilot; but was told the same thing; that messages were normal and that I should depart. I declined to depart and went into the gate. After safely parking at the gate; I called the Chief Pilot again. I explained I had opted to have MX look over the airplane. I also informed the Chief Pilot that; the First Officer and I would be comfortable taking the airplane to ZZZ1; provided we had written documentation that the messages were normal. (Much like the ACARS messages on the EICAS Screen on some airplanes a year or so ago. The message was part of the COI; indicating the message was a nuisance and should be disregarded.) The Chief Pilot told me that is what the MX Representatives were doing. I took a picture of the log page after the MX Representatives had signed it off. The First Officer and I both agreed that the entry was sufficient to allow us to depart. We departed without further incident; except the same EICAS Message; and two Discrete lights were present with the Parking Brake set and would extinguish after the Parking Brake was released. Enroute to ZZZ1; I looked through both logbooks again; and was surprised to see that the ANTISKID OFF issue had been written up twice before in the days before this incident. The first write up had the ANTISKID System Deferred. With a Corrective Action the following flight day of changing a control unit. Another day later; the same write up occurred with a return to the gate with a revision by the Captain; of entered in error. Upon reviewing the logbooks; a second time and discovering I had missed the history of the same messages; I felt that I had departed in error from ZZZ. Welanded without incident in ZZZ1 and parked; I made another entry into the aircraft logbook about the ANTISKID OFF EICAS and associated Discrete Lights.First; make sure to more adequately review the aircraft write-ups to establish an aircraft history. Second; do not cave to pressure from Management or MX Control to depart with a discrepancy. Additionally; MX Control informed us that according to the MX Manual; the messages were considered normal; however; this condition was in no way normal; which makes the MX Manuals and Flight Crew Manuals in a probable disagreement.

Data retrieved from NASA's ASRS site and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.