Flightradar24

[Tomliner]

Been trying to access this site just now but it seems to be down.Not permanently I hope EricT

[DaveB]

Wonder if it's due to the foul weather Eric. My broadband has dropped a couple of times this morning.. hardly surprising with the very high winds and rain we're having

Still.. it keeps me out of the garden
EDIT:.. it's up at the moment Eric
ATB
DaveB

[Tomliner]

Just have to wait and see Dave.Wx not too bad up here today so far! EricT

[Garry Russell]

Hi Eric

Not had a problem

I have it on right now

[Tomliner]

Hi Garry.Just tried again,same result.the'Planes tab count also shows zero.At the mo I am using an IPad on 3G but that should make no difference.I'll try later on wifi or on the old steam powered PC when I get home.
Scratch that.Just remembered that I turned off JavaScript in Safari All ok now.EricT

[Garry Russell]

OK mate

Useful info

I mucked up the other day...nothing, no 'planes ...just a map and sitting watching continentall drift didn't really appeal to me

When I turned on the PC they were there on that one

Then the penny dropped...I had left a filter running on the laptop

[FlyTexas]

One of our brand new 800's misbehaving. I hope we kept the sales receipt.

[Garry Russell]

It's probably something serious...like a scratched winglet

[FlyTexas]

God forbid!

Brian

[Chris Trott]

Flightaware's got a much more clear picture.

Looks like the flight diverted into Indianapolis and they replaced the aircraft as the flight is enroute to Florida now.

http://flightaware.com/live/flight/SWA1717

Also, FlightAware and the FAA make the situation clearer that the aircraft in question that had the radio failure was a 737-300, not N8303. Flightradar24 has confused the replacement aircraft (N8303) with the original aircraft. Flightradar24 shows the aircraft dropping off track when it was still circling south of Midway. FlightAware shows its full track into Indy before being replaced by N8303.