A320 flight crew reported an engine fire and engine cowling burn-through while troubleshooting an engine reverser fault on the ground with Maintenance Control.
Synopsis
A320 flight crew reported an engine fire and engine cowling burn-through while troubleshooting an engine reverser fault on the ground with Maintenance Control.
Narrative
Taxied out to Runway XX at ZZZ as planned and briefed. Nearing departure end we got an Eng 2 Reverser fault. Stopped and reviewed QRC. Nothing for on ground event noted. Called Maintenance Control. Decided to taxi back to ramp to clear taxiway and work issue. Taxied via Runway XX and exited at Taxiway XX. Parked on south side of Deice Ramp. Maintenance Control directed to start APU. Captain set brakes and we started APU. Upon direction from Maintenance Control; we shut down both motors. Captain stood up to check circuit breaker panel. CB at N41 on 121 VU panel was popped; labeled Engine 2 Oil Quantity Sensor Channel B.Upon Maintenance Control direction; we reset circuit breaker. We were directed to restart engines and report back. Started Engine 1. At 50% N2 the FO (First Officer) started Engine 2. Normal indications; when radio call reported engine fire on right side. FO looked right and saw some smoke blowing past the right window. Then the fire alarm and ECAM illuminated. FO looked up to verify indication and pointed to ECAM screen. Started to read the first step and alarm stopped and ECAM went away. Radio call reported sparks from bottom of Engine 2. There was a momentary alarm bell again and then it went away. Fire loop fault appeared and FO shut down motor with Master Engine switch. No other indications of fire noted. Airport CTAF called fire department. Crew stayed on phone with Maintenance and fire department reported a burn-through on the cowling and scorching on the cowling. Crew elected to taxi to Parking with fire department concurrence. Shutdown went normal. Passengers deplaned via air stairs. Normal checklists completed.
Second reporter narrative
[Report narrative contained no additional information.]
More incidents for this aircraft family →
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.