B767 flight crew reported unreliable air speed indications on the First Officer's side with EEC 1 and EEC 2 EICAS messages after take off. The messages cleared on their own along with an Aileron Lockout EICAS Message. The flight continued to the destination airport.

Date: 2022-08 · Aircraft: B767-300 and 300 ER

Anomalies: aircraft-equipment-problem-less-severe|deviation-discrepancy-procedural-published-material-policy

Synopsis

B767 flight crew reported unreliable air speed indications on the First Officer's side with EEC 1 and EEC 2 EICAS messages after take off. The messages cleared on their own along with an Aileron Lockout EICAS Message. The flight continued to the destination airport.

Narrative

Aircraft was 354;000 pounds takeoff weight; high altitude airport with wet runway and thunderstorms in area. Performance had us taking off with Max Power. I was pilot monitoring and First Officer (FO) had the takeoff. At the 80 KIAS call out FO said he was showing 54 KIAS. I crossed referenced the standby airspeed and mine and both were showing the same around 88 KIAS. I had been watching my speed closely with the max power takeoff and it accelerated normally throughout the takeoff roll. I decided since we were in the high speed regime and both my airspeeds indicated normally that I'd continue the takeoff; after taking control of the aircraft; and continue vice risk the high speed reject under our conditions. Takeoff was normal until around 400 ft. when we received the IAS DISAGREE Engine Indicating and Crew Alerting System (EICAS). Shortly afterwards we received both L and R EEC EICAS messages. We were performing a Noise Abatement Departure Procedure takeoff and around cleanup those EICAS messages cleared on their own and we received an AILERON LOCKOUT EICAS. I took the radios and had control of the airplane and asked for vectors to clear the thunderstorms on our SID. FO started running the QRH and before he could finish the EICAS cleared itself too on its own. Airspeed and all systems went back to normal and remained that way the remainder of the flight. I put this in the aircraft release for Aircraft X upon return to ZZZ1. Maybe an anomaly with the Air Data Computer; or something with FO Pitot System.

Second reporter narrative

Normal and standard push; start; and taxi. Crew discussed high altitude; wet runway; Noise Abatement Departure Procedure and SID considerations. Performance called for flaps 5; as I recall V1 140; VR150. Captain was pilot monitoring (PM); I was pilot flying (PF). During takeoff roll; thrust felt normal/correct for conditions. PM made '80 knots' call; I looked at right Primary Flight Display (PFD) and saw 54 and said 'I have 54'. After about 1-2 seconds; Captain took the controls and rotated at VR based on speeds on left PFD and ISFD (Integrated Standby Flight Display). After positive rate; we raised the gear. At 400 ft.; the Captain called 'LNAV'; I verified the Flight Mode Annunciator (FMA) and replied 'Armed'. Shortly afterwards; we received IAS DISAGREE Engine Indicating and Crew Alerting System (EICAS); the Auto-Throttles disengaged; and the roll mode went to HDG SEL. I re-selected LNAV; and THR to re-engage Auto-Throttles. Somewhere above 1;500 ft. AGL we engaged VNAV; cleaned up; completed the after takeoff checklist; and maneuvered to avoid a thunderstorm. L and R ENGINE EEC EICAS appeared as well. The Captain took the radios and directed me to run the QRH. By the time I finished IAS DISAGREE and pulled up UNRELIABLE AIRSPEED; the three EICAS messages cleared; airspeeds matched ISFD and L and R PFD. Soon after; we received an AILERON LOCKOUT EICAS; which cleared approximately 30-60 seconds later. All instruments and indications remained normal for the duration of the flight. Event record was selected. Post-flight; we coordinated a debrief with maintenance on the aircraft; and the Captain entered the discrepancy in the aircraft release. We checked the [reporting program requirements] and determined that a report was not required. After further deliberation; we agreed that a report was appropriate.Suspect right pitot static source or Air Data Computer anomaly. Defer to Maintenance avionics expertise.

More incidents for this aircraft family →

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