# Something very broken

**URL:** <https://discussions.flightaware.com/t/something-very-broken/9642>\
**Category:** General\
**Created:** [March 19, 2010, 10:23pm UTC](https://discussions.flightaware.com/t/something-very-broken/9642 "2010-03-19T22:23:07Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![RobK](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/robk/32/128611_2.png) [@RobK](https://discussions.flightaware.com/u/RobK)\
**Post date:** [March 19, 2010, 10:23pm UTC](https://discussions.flightaware.com/t/something-very-broken/9642/1 "2010-03-19T22:23:07Z")

</div>

Weird things afoot…

Wanted to look up DAL656 so keyed it in and hit enter. Brings up the flight details for COM5344. 😮 Similarly, DAL657 brings up the flight details for COM5343 😮😮 . I can click on the links from the TXKF airport page and the flights load ok but not when directly keyed.

Edit: When entering DAL656 from the forum index it loads ok first time, but if you key it in a second time it gives you COM5344 again. 😮😮

Opera 10.50

---

<div class="post-metadata">

**Author:** ![RobK](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/robk/32/128611_2.png) [@RobK](https://discussions.flightaware.com/u/RobK)\
**Post date:** [March 19, 2010, 10:26pm UTC](https://discussions.flightaware.com/t/something-very-broken/9642/2 "2010-03-19T22:26:57Z")

</div>

More issues… 😕

DAL494 works ok if you click the link from the MDSD departures but when entering it directly it morphs into ASQ494. 😮

Edit: and same thing as above - if you key it in from the forums it works ok first time but try keying it in again and you’ll get ASQ494. 😮

---

<div class="post-metadata">

**Author:** ![mduell](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/mduell/32/115680_2.png) [@mduell](https://discussions.flightaware.com/u/mduell)\
**Post date:** [March 19, 2010, 11:10pm UTC](https://discussions.flightaware.com/t/something-very-broken/9642/3 "2010-03-19T23:10:09Z")

</div>

Are you sure you’re not adding another digit?

I’m unable to reproduce your findings, and none of our Delta codeshare ranges change the numbers except some Comair flights that drop the 6.

---

<div class="post-metadata">

**Author:** ![RobK](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/robk/32/128611_2.png) [@RobK](https://discussions.flightaware.com/u/RobK)\
**Post date:** [March 20, 2010, 9:01am UTC](https://discussions.flightaware.com/t/something-very-broken/9642/4 "2010-03-20T09:01:10Z")

</div>

> [@mduell](#):
>
> **Are you sure you’re not adding another digit?**
> 
> I’m unable to reproduce your findings, and none of our Delta codeshare ranges change the numbers except some Comair flights that drop the 6.

❗ No Mark… I am not adding additional digits… 😐

Still broken. Just tried DAL493 which gives me SKW493 instead. WTF 😮

---

<div class="post-metadata">

**Author:** ![deef1999](https://avatars.discourse-cdn.com/v4/letter/d/a4c791/32.png) [@deef1999](https://discussions.flightaware.com/u/deef1999)\
**Post date:** [March 20, 2010, 11:28am UTC](https://discussions.flightaware.com/t/something-very-broken/9642/5 "2010-03-20T11:28:48Z")

</div>

Works fine for me on IE8

---

<div class="post-metadata">

**Author:** ![davysims](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/davysims/32/52887_2.png) [@davysims](https://discussions.flightaware.com/u/davysims)\
**Post date:** [March 20, 2010, 12:54pm UTC](https://discussions.flightaware.com/t/something-very-broken/9642/6 "2010-03-20T12:54:08Z")

</div>

Works for me.

---

<div class="post-metadata">

**Author:** ![pika1000](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/pika1000/32/124076_2.png) [@pika1000](https://discussions.flightaware.com/u/pika1000)\
**Post date:** [March 20, 2010, 11:10pm UTC](https://discussions.flightaware.com/t/something-very-broken/9642/7 "2010-03-20T23:10:15Z")

</div>

No problemo on Firefox.

Rob, have you been drinking again? 😆

---

<div class="post-metadata">

**Author:** ![AirmanElmo](https://avatars.discourse-cdn.com/v4/letter/a/7feea3/32.png) [@AirmanElmo](https://discussions.flightaware.com/u/AirmanElmo)\
**Post date:** [March 21, 2010, 1:55am UTC](https://discussions.flightaware.com/t/something-very-broken/9642/8 "2010-03-21T01:55:35Z")

</div>

No squawks here on Opera10. However, an extra numerical digit in the flight number for either of the DAL flights brings up COM flights. But again, using 6656, 6556, or 6566 instead of DAL 656 didn’t yield any of the reported COM flight numbers.

---

<div class="post-metadata">

**Author:** ![RobK](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/robk/32/128611_2.png) [@RobK](https://discussions.flightaware.com/u/RobK)\
**Post date:** [March 21, 2010, 12:46pm UTC](https://discussions.flightaware.com/t/something-very-broken/9642/9 "2010-03-21T12:46:06Z")

</div>

I don’t use FF but I tried it on Chrome and IE6 which are the only other browsers I have on this machine (I don’t use IE6 but I tried it as it’s there). The same issue is apparent using those browsers as well. First time you key in DAL656 with Chrome it pulls up the correct details but type in DAL656 a second time from there and it returns COM5344.

With IE6 the first time you type in DAL656 it gives you COM5344.

The main PC is shared with others and uses Adblock in both Opera and Chrome (don’t blame me, I didn’t put them on there!) but there’s no Adblock on IE6. I tried my laptop which doesn’t use any Adblockers and the problem is still there, so it’s definitely nothing to do with those just in case someone was about to ask if I was using any.

I also tried it logged out and logged in and it doesn’t make any difference there either.

I can’t believe that NO-ONE else is getting this issue. This is across 3 different browsers and 2 completely different systems (ancient Compaq desktop pre-Pent 1 and top end HP laptop with all the bells and whistles). Both do run XP though so are all you guys running Vista or 7 ? Perhaps OS related?

I’ve even recorded some avi files of the processes for you to see what happens

Chrome - [sendspace.com/file/6iqgk2](http://www.sendspace.com/file/6iqgk2) (12 MEG)  
Opera - [sendspace.com/file/bb7gpi](http://www.sendspace.com/file/bb7gpi) (12 MEG)  
IE6 - [sendspace.com/file/1dp0dc](http://www.sendspace.com/file/1dp0dc) (14 MEG)

The processes are laggy due to CamStudio running. The browsers (with exception of IE) normally run very fast.

---

<div class="post-metadata">

**Author:** ![deef1999](https://avatars.discourse-cdn.com/v4/letter/d/a4c791/32.png) [@deef1999](https://discussions.flightaware.com/u/deef1999)\
**Post date:** [March 21, 2010, 1:06pm UTC](https://discussions.flightaware.com/t/something-very-broken/9642/10 "2010-03-21T13:06:36Z")

</div>

I also was able to reproduce this. Typed in DAL656 hit enter, flight came up normally. Typed in dal656 again, hit enter and came up with COM 5344 (copied from top of page: FlightAware couldn’t find flight tracking data for COM5344 just yet.)

ROBK IS CORRECT!!!

---

<div class="post-metadata">

**Author:** ![RobK](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/robk/32/128611_2.png) [@RobK](https://discussions.flightaware.com/u/RobK)\
**Post date:** [March 21, 2010, 1:16pm UTC](https://discussions.flightaware.com/t/something-very-broken/9642/11 "2010-03-21T13:16:49Z")

</div>

> [@deef1999](#):
>
> I also was able to reproduce this. Typed in DAL656 hit enter, flight came up normally. Typed in dal656 again, hit enter and came up with COM 5344 (copied from top of page: FlightAware couldn’t find flight tracking data for COM5344 just yet.)
> 
> ROBK IS CORRECT!!!

🙂🙂

I now await the onslaught of FF-fanboys with the usual “every other browser in the world is shit except FF… Works fine on FF… You should change to FF… FF is open source and therefore automatically better than anything else ever made in entire world… FF FTW!” etc etc etc etc yawn etc yawn. 😆

---

<div class="post-metadata">

**Author:** ![damiross](https://avatars.discourse-cdn.com/v4/letter/d/b9bd4f/32.png) [@damiross](https://discussions.flightaware.com/u/damiross)\
**Post date:** [March 21, 2010, 2:29pm UTC](https://discussions.flightaware.com/t/something-very-broken/9642/12 "2010-03-21T14:29:21Z")

</div>

> [@RobK](#):
>
> I now await the onslaught of FF-fanboys with the usual “every other browser in the world is shit except FF… Works fine on FF… You should change to FF… FF is open source and therefore automatically better than anything else ever made in entire world… FF FTW!” etc etc etc etc yawn etc yawn. 😆

My! My! Did we get up on the wrong side of the browser this morning?

---

<div class="post-metadata">

**Author:** ![olseric](https://avatars.discourse-cdn.com/v4/letter/o/a9a28c/32.png) [@olseric](https://discussions.flightaware.com/u/olseric)\
**Post date:** [March 21, 2010, 2:38pm UTC](https://discussions.flightaware.com/t/something-very-broken/9642/13 "2010-03-21T14:38:23Z")

</div>

Confirmed here. Both FF and IE8.

---

<div class="post-metadata">

**Author:** ![JHEM](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/jhem/32/9683_2.png) [@JHEM](https://discussions.flightaware.com/u/JHEM)\
**Post date:** [March 21, 2010, 2:50pm UTC](https://discussions.flightaware.com/t/something-very-broken/9642/14 "2010-03-21T14:50:35Z")

</div>

“Every other browser in the world is shit except FF… Works fine on FF… You should change to FF… FF is open source and therefore automatically better than anything else ever made in entire world… FF FTW!”

😉

---

<div class="post-metadata">

**Author:** ![damiross](https://avatars.discourse-cdn.com/v4/letter/d/b9bd4f/32.png) [@damiross](https://discussions.flightaware.com/u/damiross)\
**Post date:** [March 21, 2010, 2:53pm UTC](https://discussions.flightaware.com/t/something-very-broken/9642/15 "2010-03-21T14:53:34Z")

</div>

I entered DAL656 into the “track any flight” field while in the forum DAL656 came up. Then when I entered DAL656 again, COM5344 came up with a protest that the flight doesn’t exist.

When I entered DAL656 directly into the “track any flight” field from within the main site (i.e. not when I was in the forum". The COM5344 protest came up.  
Tried: DAL657, got COM5343 (flight doesn’t exist)  
DAL659 - got COM5341 (flight doesn’t exist)  
DAL658, got COM5342 with the following data:

> Aircraft (XXXX/ - track or photos)  
> Origin Montreal-Trudeau (CYUL / YUL - track or info)  
> Destination John F Kennedy Intl (KJFK - track or info)
> 
> Route n/a  
> Date Wednesday, Jul 09, 2008  
> Duration Unknown  
> Status result unknown  
> Scheduled Actual/Estimated  
> Departure 06:28 EDT 06:28 EDT  
> Arrival 07:07 EDT result unknown  
> Speed   
> Altitude Unspecified

This doesn’t occur when I use the “track commercial flight” field.

---

<div class="post-metadata">

**Author:** ![TimCoble](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/timcoble/32/31860_2.png) [@TimCoble](https://discussions.flightaware.com/u/TimCoble)\
**Post date:** [March 21, 2010, 2:58pm UTC](https://discussions.flightaware.com/t/something-very-broken/9642/16 "2010-03-21T14:58:02Z")

</div>

Nobody asked, but yes, I’ve been drinking again.  
You know, St Paddy’s Month.

---

<div class="post-metadata">

**Author:** ![deef1999](https://avatars.discourse-cdn.com/v4/letter/d/a4c791/32.png) [@deef1999](https://discussions.flightaware.com/u/deef1999)\
**Post date:** [March 21, 2010, 3:48pm UTC](https://discussions.flightaware.com/t/something-very-broken/9642/17 "2010-03-21T15:48:11Z")

</div>

> [@TimCoble](#):
>
> Nobody asked, but yes, I’ve been drinking again.  
> You know, St Paddy’s Month.

You have been drinking, isn’t it St. Patty’s?

---

<div class="post-metadata">

**Author:** ![RobK](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/robk/32/128611_2.png) [@RobK](https://discussions.flightaware.com/u/RobK)\
**Post date:** [March 21, 2010, 6:23pm UTC](https://discussions.flightaware.com/t/something-very-broken/9642/18 "2010-03-21T18:23:01Z")

</div>

> [@damiross](#):
>
> > [@RobK](#):
> >
> > I now await the onslaught of FF-fanboys with the usual “every other browser in the world is shit except FF… Works fine on FF… You should change to FF… FF is open source and therefore automatically better than anything else ever made in entire world… FF FTW!” etc etc etc etc yawn etc yawn. 😆
> 
> My! My! Did we get up on the wrong side of the browser this morning?

Nope! I was just giving the Fire of the Fox fan-boys a good dowsing of water before they got chance to get started! 😛

---

<div class="post-metadata">

**Author:** ![AirmanElmo](https://avatars.discourse-cdn.com/v4/letter/a/7feea3/32.png) [@AirmanElmo](https://discussions.flightaware.com/u/AirmanElmo)\
**Post date:** [March 21, 2010, 7:20pm UTC](https://discussions.flightaware.com/t/something-very-broken/9642/19 "2010-03-21T19:20:32Z")

</div>

I don’t think it’s anything firefox can fix anyway. ❓  
Anyway, I have the described result when I enter DAL656 in the “Flight/Tail” box, hit enter, re-enter DAL656, and hit enter again.  
Using the “Type part of airline name…” box doesn’t come up with that error.

---

<div class="post-metadata">

**Author:** ![JHEM](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/jhem/32/9683_2.png) [@JHEM](https://discussions.flightaware.com/u/JHEM)\
**Post date:** [March 21, 2010, 7:26pm UTC](https://discussions.flightaware.com/t/something-very-broken/9642/20 "2010-03-21T19:26:32Z")

</div>

> [@deef1999](#):
>
> > [@TimCoble](#):
> >
> > Nobody asked, but yes, I’ve been drinking again.  
> > You know, St Paddy’s Month.
> 
> You have been drinking, isn’t it St. Patty’s?

Only to the accursed English invaders!

[Next page](https://discussions.flightaware.com/t/something-very-broken/9642.md?page=2)
