Narrative:

After pushback; started engines 1 & 3 in normal sequence without incident. When starting eng #2; parameters indicated a delay in engine light-off. There was an abrupt change in RPM when we briefly discussed aborting the start attempt. Crew in aircraft behind us advised ramp tower that our aircraft had a tailpipe fire on number 2. We complied with the QRH; coordinated a [return to the ramp] (straight ahead due to our gw (gross weight) and only 2 engines available for taxi. Made aml (aircraft maintenance logbook) entry; maintenance inspected; did an engine run and signed off discrepancy. Compounding the issue was an MEL for #2 fuel flow indication and weak APU. Subsequent start was normal.weak APU and lack of fuel flow information to crew during start sequence. Recommend maintain APU's to peak performance.

Google
 

Original NASA ASRS Text

Title: Cargo aircraft Captain reported an engine tailpipe fire during the engine start sequence.

Narrative: After pushback; started Engines 1 & 3 in normal sequence without incident. When starting Eng #2; parameters indicated a delay in engine light-off. There was an abrupt change in RPM when we briefly discussed aborting the start attempt. Crew in aircraft behind us advised ramp tower that our aircraft had a tailpipe fire on number 2. We complied with the QRH; coordinated a [return to the ramp] (straight ahead due to our GW (Gross Weight) and only 2 engines available for taxi. Made AML (Aircraft Maintenance Logbook) entry; Maintenance inspected; did an engine run and signed off discrepancy. Compounding the issue was an MEL for #2 Fuel Flow indication and weak APU. Subsequent start was normal.Weak APU and lack of fuel flow information to crew during start sequence. Recommend maintain APU's to peak performance.

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.