Over the weekend, it has emerged that an Emirates Airbus A380 bound for Dubai rejected it’s takeoff in Sao Paulo, with flames seen coming from the engine.
Information has been released pertinent to this incident, which we will get into in this article.
Without further ado, let’s get into it…
Emirates Flight EK262 – Sao Paulo to Dubai…
Emirates flight EK262 is a routine scheduled flight between Sao Paulo and Dubai.
The aircraft involved in this incident is understood to be A6-EUL.
As per data from Planespotters.net, A6-EUL is a 7.9 year old Airbus A380 that was delivered to the airline in December 2016.
Furthermore, of the A380 variant, Emirates has 116 in their fleet.
Of that 116, 91 are in active service, with 25 still parked, with an average fleet age of 9.4 years.
As well as the A380, the aircraft has the following aircraft in it’s commercial fleet:
- 1 Airbus A319.
- 143 Boeing 777s.
Emirates flight EK262 pushed back from Sao Paulo at 0400 local time on June 15, around two hours and 55 minutes late initially.
From there, the aircraft taxied out to the runway for it’s departure to Dubai.
As per The Aviation Herald, it is understood that this incident took place during the takeoff roll.
The crew rejected takeoff following a bang being heard, which then followed by a streak of flames.
Following that rejected takeoff, the aircraft exited the runway at Sao Paulo, with the flight to Dubai cancelled.
Aircraft Still Grounded Two Days On…
Data from RadarBox highlights that A6-EUL, the Emirates A380, is still stuck in Sao Paulo two days after the incident.
At this stage, it is unclear when the aircraft will return to commercial service.
With it’s left hand GP7270 engine out of action, the aircraft cannot return to service until the fixes are made.
It is believed that the streak of flame would be as a result of an engine surge on the aircraft.
What Next?
In terms of what comes next for this Emirates Airbus A380 in Sao Paulo is the work is well underway to get the aircraft fixed.
Furthermore, it is currently unclear how long it will take to fix, as this could be a range of factors.
One factor could be the fact that parts for the aircraft type need to be sent to the Brazilian airport.
Maintenance facilities may not be equipped to deal with the superjumbo, so engineers may need to be sent there.
As soon as the relevant resources are around the aircraft, then the needed fixes can be made.
Data from RadarBox also has tracked the aircraft briefly under the callsign ENG001, where it has taxied on a taxiway presumably.
This could indicate that the resources are there to fix the aircraft, and that the affected engine has been tested.
If the tests were successful, then this would indicate that the aircraft can return to commercial service soon.
But for now, all eyes will be on when the aircraft eventually departs Sao Paulo back to Dubai.
Click the banner to subscribe to our weekly Emergencies and Incidents newsletter.
Click the photo to join our WhatsApp channel so then you can stay up to date with everything going on in the aviation industry!
