RandyWaldron From United States of America, joined Mar 2006, 324 posts, RR: 3 Posted (8 years 2 weeks 6 days 21 hours ago) and read 4036 times:
This evening (6/20), Aer Lingus flight 132, had an engine fire during its takeoff roll on Boston's runway 22R.
As the pilots applied power to initiate the takeoff roll, a burst of smoke eminated from the No. 1 (left) engine. Seconds later, the engine erupted in flames. The aircraft aborted takeoff and after several minutes of inspection by the Massport Fire Department, taxied to a gate at Terminal E under its own power.
FYI, for interested BOS spotters. I watched the whole event unfold from a nearby beach and it was quite exciting.
Kaitak From Ireland, joined Aug 1999, 12395 posts, RR: 37
Reply 3, posted (8 years 2 weeks 6 days 21 hours ago) and read 3980 times:
Glad it all ended safely, but this will result in more schedule disruption. I guess North American will be getting a call soon.
I'm presuming it was a -300; I don't suppose you noticed which one?
No doubt the NTSB will be interested in this; while (thankfully!) it was nowhere near as dramatic as the AA 767 at LAX last week, I believe the NTSB is looking at failures of CF6 engines, to identify any possible common causes.
IKECVN69 From United States of America, joined Apr 2006, 32 posts, RR: 0
Reply 11, posted (8 years 2 weeks 4 days 3 hours ago) and read 3270 times:
I see that EI-JFK is airborne again after spending a couple of days in Boston being repaired. When an aircraft has a problem such as this away from its homeland, who actually troubleshoots & makes repairs? Just curious.