Database Update Requests

[Runway 31]

Yes ffa, there are a number of aircraft with defective transponders

Alan

[ffa1978]

FFA,
maybe you could be so kind to give us the source of your screenshots.
Is it data you received or is it a russian flight tracking website?

ABW is usually not using flight numbers with 4 digits after ABW.

Many thanks.

Ingo

Not true! ABW periodically using 4 digits after ABW !!Screenshot attached From My VRS

[ffa1978]

Another aircraft with miscode hex Vq-BJX Rossiya Airlines -periodically using two hex (424964-true,4249164-wrong)

[neroon79]

ABW usually uses ABW plus 3 digits flight ids for regular routes. Counting the total number of operations I'd like to say, that they are occasionally but repeatingly using ABW plus 4 digits flight ids. Especially for delivery flights and single point A to point C (via point B) operations.

In addition to defective transponders I noticed an increase of bogus flight id / aircraft combinations in times of high traffic. Especially if you have a hugh coverage area the posibilty of interference of several data packets sent by several aircraft at same time can cause problems. In some cases I saw two aircraft with same flight id for several minutes moving on screen. Further I got cases in which I was the only one who received a flight id with a particular aircraft. The big flight tracking sites had the flight id connected to another aircraft. In that cases I consider my data to be corrupted in some way.

In many cases we are able to track down the reason for an error or we are able to figure out the aircraft which was causing it and in other cases can't or it takes days to track it down. In case of ABW5180 / VP-BKK no other flight tracking netwok has received flight id ABW5180 or activity of VP-BKK, which makes it highly impossible to figure out the origin of the entry in your friends flight history database. I personally ignore this entries until they are appear in a regular bases.

Ingo

[ffa1978]

I dont see never wrong Hex/id for me only.I don't see ghost hex.My range 250 miles stability with 10 Dbi Radial A10-1090 antenn and LNA 30 db 0.6db Nf.In days i see 500-550 aircaft and more.

[Runway 31]

The problems are in the busy areas which see that number of aircraft in an hour or so!

Alan

[neroon79]

Just to be sure is it 500-550 simultanously or per day?

[neroon79]

My problems are really starting in times I've 200+ airframes in my list simultanously,

Another aircraft with miscode hex Vq-BJX Rossiya Airlines -periodically using two hex (424964-true,424164-wrong).

For me it looks like a fault in the database or the software accesing the database. 424164 is assigned to VP-CFF. If VQ-BJX is shown during reception of hex 424164 there must be something wrong with the database itself or the software accessing the database.

With correct working software and database, during the reception of a particular flight id, from two different hex codes at the same time, the flight id should occur with aircraft data of both hex numbers in the flight history list. With many hours between the two receptions I would say VQ-BJX is in the database with two different hex adresses against it. The different Boing types are supporting this presumption. Hex 424964 is the correct one and 424164 is a false entry which should be exchanged with the data of VP-CFF. Unfortunately VQ-BJX seems indeed repeatingly using false hex of 424164 (either a dodgy or deliberately/unknowingly miscoded box). Nevertheless the type data of the Boeing aircraft(s) is still inconsistent and needs to be checked if both entries VQ-BJX shall be kept.

A one digit variation in HEX address can easily be caused by reception of corrupted data packets. I've about 10 cases per day. Ususally placed in or around the peak times of air traffic. 

Ingo

[ffa1978]

550-660 per day.In one moment max 50-60

[ffa1978]

My problems are really starting in times I've 200+ airframes in my list simultanously,

Another aircraft with miscode hex Vq-BJX Rossiya Airlines -periodically using two hex (424964-true,424164-wrong).

For me it looks like a fault in the database or the software accesing the database. 424164 is assigned to VP-CFF. If VQ-BJX is shown during reception of hex 424164 there must be something wrong with the database itself or the software accessing the database.

With correct working software and database, during the reception of a particular flight id, from two different hex codes at the same time, the flight id should occur with aircraft data of both hex numbers in the flight history list. With many hours between the two receptions I would say VQ-BJX is in the database with two different hex adresses against it. The different Boing types are supporting this presumption. Hex 424964 is the correct one and 424164 is a false entry which should be exchanged with the data of VP-CFF. Unfortunately VQ-BJX seems indeed repeatingly using false hex of 424164 (either a dodgy or deliberately/unknowingly miscoded box). Nevertheless the type data of the Boeing aircraft(s) is still inconsistent and needs to be checked if both entries VQ-BJX shall be kept.

A one digit variation in HEX address can easily be caused by reception of corrupted data packets. I've about 10 cases per day. Ususally placed in or around the peak times of air traffic. 

Ingo

I dont have crashed packet .Example for Vq-BJX from my VRS -repeat miscode stable.It's not error recieve packets.In one moment recieve aircraft more station with this miscode hex.. During one flight HEX not changed.PS And -i not use AIrnav or another database/I used only local handmade basestation.sqb with Virtual radar

[Runway 31]

ffa,

What happens when you have the miscode user of the hex and the correct user of the hex in your reception area at the same time?

Alan

[X]

Hi Alan / ffa1978

   424261  AFL7611                          CP-2923    B737  Boliviana De Avia... 2017/11/30 14:23:40
   424261  AFL1102  UUEE-URKK       CP-2923    B737  Boliviana De Avia... 2017/12/01 11:15:02 
   424261  AFL1103  URKK-UUEE       CP-2923    B737  Boliviana De Avia... 2017/12/01 16:12:07 
   424261  AFL1204  UUEE-USPP       CP-2923    B737  Boliviana De Avia... 2017/12/01 20:51:51 
   424261  AFL1205  USPP-UUEE       CP-2923    B737  Boliviana De Avia... 2017/12/02 13:24:55 
   424261  AFL1510  UUEE-USRR       CP-2923    B737  Boliviana De Avia... 2017/12/02 22:17:50 

I like you picked up "424261" on AFL1205 with reg CP-2923 in fact I have picked it up 5 times today and first appeared 30/11/17 on a delivery flight number AFL7611 ex Toulouse. VP-BKK B738 was delivered last night as AFL7649 but that is 42437E! So we currently have an unidentified machine, however it is unusual for an aircraft to go into Aeroflot service so quickly after delivery!

424261 is currently in the air as AFL1510 (normally an A320) en route Surgut again showing as CP-2923! Whatever it is, we have a miscoding/ double coding issue!

X

[Runway 31]

Hi X

Look back other replies and you will see that it is 424261 VP-BTO A320-214 c/n 7932 ex TLS 30 Nov as AFL7611.  The Bolivian is also using the same hex code unfortunately.

I am at Gleneagles for the weekend and my laptop doesnt have a working d/b updater so it wont get added to the d/b till I get home tomorrow afternoon

Alan

[X]

Alan

Was too busy trying to sort 424261 I missed some posts out but thanks for the update...enjoy Gleneagles, I hope it is not as snowy as MOW.....can see sod all at the moment

X

[ffa1978]

Alan:I never seen misscode hex and true hex from one aircraft at the same time/Transpoder transmitted in one moment only one hex.In one aircraft  (sorry -I dont remember registration) Hex changed every few minutes.One symbol on hex changed.on the track it made no difference.Wrong and true hex contained on Basestation.sqb with one regs and in VRS table only changed row with hex periodically on this flight.On maps track was smooth.
And another situation -two identical hex at same time from AFL and Vim (VP-BAC Aeroflot HEX 424317(true) and VP-BLI Vim Airlines with same HEX 424317 but wrong(424357-true hex).VRS crazy ! Broken track and the aircraft appearance in a random location on the map.
VQ-BQK S7 AIRLINES also have true and miscode hex (424571-true) and (424171-misscode).During flight hex not change.it confirmed