TTG572 - why did it return?
 

Hi all

I live in Boronia and about 7.30PM 28/12 heard a plane pass overhead. I quickly went on to Flightradar24 and found that it was Tigerair TGG572 MEL-OOL. What was peculiar was that the flight had taken off a little earlier but was now circling Melbourne.

I tracked the plane and it now appears to have safely landed back at MEL.

Has anyone any idea why the plane returned to MEL rather than continued on to OOL? Bird strike maybe?

cheers Peter

https://uk.flightaware.com/live/flight/TGG572

I don't know about the return but you have the makings of a brilliant journalistic area by including "circling Melbourne" and "landed safely" in a short post.

Captain forgot his pressies.

****s and giggles. Thought they'd see what attention they could get on pprune

Can't be too much wrong with A320 TGG572 / TT572:

Departed Melbourne Tullamarine - MEL Wednesday 28-Dec-2016 20:47 AEDT (47 minutes late)

Landed at Gold Coast - OOL Wednesday 28-Dec-2016 21:28 AEST (59 minutes late)

I half expected to see a headline in today's Herald-Sun

"TIGER AIRLINES FLIGHT IN TULLA RETURN DRAMA
Tiger Airlines flight forced to return to Tullamarine Airport after mid-air event."

I accept that there can be quite innocuous explanations for why this can happen but there can also be other more concerning ones too. I am still curious to know why they incurred the extra cost in landing back at Tulla.

Because the Captain chose to return. That's a pretty accurate explanation. Because aircraft don't just return themselves.

Either way, it may not be any of your business.

Compared to the cost of going U/S in OOL? :rolleyes:

Could be a number of reasons from medical to a mechanical issue.

If it was a serious medical issue circling is unlikely so most likely would be a mechanical issue. As posted above would have possibly been a grounding issue in an unfavourable place. The circling could have been for trouble shooting or planning (can guys fix a broken Fritz in OOL?)

Given the short time back on the ground it was a quick fix.

It was not a "plane", it was a boomerang.

Returning boomerangs have a special curved shape and two or more wings that will spin to create unbalanced aerodynamic forces. These forces — sometimes called “lift" — cause the boomerang's path to curve in an elliptical shape, so that it will return to the thrower when thrown correctly.

Peter - Band a Lot has probably given you the most accurate answer....

....But this is really not the most apppropriate place to seek answers to your curiosity, scornful and sarcastic replies are rude, uncalled for and really rather unprofesional....apologies on behalf of...

I agree, I thought the original post was very polite and deserved some respect for its honesty.

They departed 47 minutes later.....That's a pretty damn quick turn around if you ask me. Hat's off to Tiger and ML ATC. Must have been an important chrissy present for the captain.....:E

Ever heard of a Maintenance Procedure for some inane issue that couldn't be deferred by the crew at OOL?

Or maybe they had the wrong "books"?

This time of year I expect a certain licence was required for a defer, and OOL LAME was on vacation.

What ever it was (assuming a maintenance issue) it was more of a paperwork issue than a test and repair issue.

Having stated the aeroplane was circling Melbourne, your Flightradar24 link does not show that!

Here is the link to FR24:

http://www.flightradar24.com/data/fl...tt572/#c030cac

Indeed FR24 it does not seem to show any airborne activity prior to departure of the flight to OOL. On FR24 (and Flight Aware) such an event at a major airport with lots of data feeders nearby would generally show up just like a rejected takeoff or aborted landing - as a continuous trail incorporating all air and ground movements by the aircraft. In fact if an aircraft returns to the gate, the previous excursion will often still be appended when the flight does eventually take off, sometimes hours later.

I found out that both the wife and girlfriend were onboard, can't have them comparing notes. :ouch::E