Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Communication Breakdown; Distraction; Training / Qualification; Time Pressure; Situational Awareness; Troubleshooting; Workload
Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Maintenance; Ground Event / Encounter FOD
Aircraft Aircraft Damaged; General Flight Cancelled / Delayed; General Maintenance Action
Aircraft; Human Factors; Procedure
At XA:10 we arrived at the aircraft in ZZZ for Flight X parked at gate X. In the logbook of Aircraft X was an open write up for Air Pack 2 REG fault. I spoke with the gate agent about it and then called dispatch.  Dispatch conferenced me in with maintenance.  It was known about the open write up since  the night before. Maintenance advised me maintenance was on the way. We completed all the preflight duties and walk around items at about XA:35. Maintenance had come out to ascertain the problem at about XA:50; 10 minutes prior to our scheduled push time. Maintenance informed me that we would be delayed about one hour at the gate for a solution. Eventually maintenance informed me the pack would be selected off and the valve had to be visually scanned closed. To do that he would have to open a panel. Upon completion of the procedure by maintenance; I walked outside to see all the panels were closed on the right side of the aircraft. They were. Once back on the flight deck I received the signed off logbook with the deferred MEL item and proceeded with our checklists. As we were being pushed back; the maintenance member drove up to the guide man. We were asked to look on the flight deck and 1st class galley for an iPad. We found none and relayed the message back. We continued our start of both engines normally with no issues. We taxied out via Taxiway 1 to Taxiway 2 and took off from ZZZ on runway XX at about XC:48 local. After takeoff rotation there was just a slight rumble that sounded like an out of round tire usually does as the gear is raised. It abated quickly and no engine anomalies noted. Upon cruise to ZZZ1 we received an ACARS message from dispatch at XI:03; regarding FOD on the runway after our takeoff.  Dispatch noted the possibility it was the maintenance member's iPad he was looking for. I told dispatch all engine parameters are normal and we proceeded to ZZZ1 with a normal landing on runway XXR. After the shutdown; I met the ZZZ1 Maintenance manager outside by the number 2 engine. It had signs of ingesting FOD. It is apparent that contract maintenance at ZZZ left the iPad inside the nacelle after our initial preflight and caused damage to the engine.Maintenance having laid an item in an engine nacelle and leaving it there after our preflight was complete.Not laying any tool or item in the nacelle of an engine.
At XA:10 we arrived at the aircraft in ZZZ for Aircraft X parked at gate XX. In the logbook of Aircraft X was an open write up for Air Pack 2 REG fault. I spoke with the gate agent about it and then called dispatch.  Dispatch conferenced me in with maintenance. It was known about the open write up since  the night before. Maintenance advised me maintenance was on the way. We completed all the preflight duties and walk around items at about XA:35 maintenance had come out to ascertain the problem at about XA:50; 10 minutes prior to our scheduled push time. Maintenance informed me that we would be delayed about one hour at the gate for a solution. Eventually maintenance informed me the pack would be selected off and the valve had to be visually scanned closed. To do that he would have to open a panel. Upon completion of the procedure by maintenance; I walked outside to see all the panels were closed on the right side of the aircraft. They were. Once back on the flight deck I received the signed off logbook with the deferred MEL item and proceeded with our checklists. As we were being pushed back; the maintenance member drove up to the guide man. We were asked to look on the flight deck and 1st class galley for an iPad. We found none and relayed the message back. We continued our start of both engines normally with no issues. We taxied out via Taxiway 1 to Taxiway 2 and took off from ZZZ on runway XX at about XC:48 local. After takeoff rotation there was just a slight rumble that sounded like an out of round tire usually does as the gear is raised. It abated quickly and no engine anomalies noted. Upon cruise to ZZZ1 we received an ACARS message from dispatch at XI:03; regarding FOD on the runway after our takeoff.  Dispatch noted the possibility it was the maintenance member's iPad he was looking for. I told dispatch all engine parameters are normal and we proceeded to ZZZ1 with a normal landing on runway XXR. After the shutdown; I met the ZZZ1 Maintenance manager outside by the number 2 engine. It had signs of ingesting FOD. It is apparent that contract maintenance at ZZZ left the iPad inside the nacelle AFTER our initial preflight and caused damage to the engine.Maintenance having laid an item in an engine nacelle and leaving it there after our preflight was complete.Not laying any tool or item in the nacelle of an engine.
Flight Crew reported minor engine rumbles on takeoff and continuing the flight. After arrival at destination airport; it was discovered that the #2 engine had FOD damage. Reporters surmised it was probably caused by a technician leaving their Company iPad in the engine inlet.