[Alan Black AS122]

I seem to have a knack for finding the quirks in the system ;-) I just went to enter JST415 in the FlightKiosk and got the results below. Although it look like it detected the flight correctly initially, it ended up entering a flight from OOL-KAST?

Here's the text from the kiosk so you can see the progress.

Alan


Flight Data Found
You entered following data for flight search: Airline: JST Flight Number: 415
(JQ) Jetstar 415

OOL Coolangatta Gold Coast, QLD, AU to SYD Sydney, NSW, AU
Departs: 9:45 AM Arrives: 12:15 PM
Duration: 1h 30m
Equipment: Airbus Industrie A320
Flight Distance: 6,311 Nautical Miles

Airline IATA found in database: Jetstar Airways Pty Ltd [JST / JST] NOT CORRECT?
Departure airport IATA found in database: Coolangatta [OOL / YBCG] NOT CORRECT?
Arrival airport IATA found in database: Astoria Regl [AST / KAST] NOT CORRECT?

NO MATCHING FLIGHT FOUND: (JQ) Jetstar 415 - added flight to database.

[Buckeye Roy]

Alan,

Looks like what is happening is instead of the FK entering the flight data from FliightStats its showing the flight data for Flt#415 which was entered in July 2013 and is already in the Jetstar Flight Schedules. This flight has the wrong arrival airport (AST/KAST) showing. Unfortunately I could not remove the erroneous flight without removing all the flights departing OOL airport to fix it.

[Tom - We need to have a single flight removal function in the Admin Section. Or, add a batch removal function done by arrival airports as well as departing airports.]

[AS 2 Tom Little]

Roy,

No doubt I need to get that function in there soon. But I do not think that (bad flight in the database) is what is causing the issue. In fact I tried to delete that flight and then entered FK data, but the flight is still drawing up KAST as arrival. I need to look further into the code to see what is going on.

[AS 2 Tom Little]

Found the bug! There was an internal code problem that was causing some airport data to get corrupted in translation.