Sydney Airport Message Board Sydney Airport Message Board  

Go Back   Sydney Airport Message Board > Spotting and Movements > Radar Spotting


Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 27th July 2012, 01:02 PM
Kurt A Kurt A is offline
YSSY Forum Administrator
 
Join Date: Mar 2008
Location: YSSY
Posts: 956
Default ADS-B Aircraft Blacklist

Stemming from another conversation around spurious ADS-B spikes; for those interested, I have been manning a blacklist of aircraft who are notorious for transmitting incorrect position reports.
These are only aircraft that have been operating in, out, or around YSSY.

Here is the unfortunate list of repeat offenders I have personally recorded over the past year:

7C4366 //Nauru Air Corporation 737-33A VH-NLK
7C1473 //Qantas Airways A-330-202 VH-EBP
7C6C6F //V Australia Boeing 777-3GZER VH-VPD
C81C17 //Pacific Blue Airlines 737-8FE ZK-PBK
E8023F //LAN Chile A-340-313X CC-CQF
7C6C71 //V Australia Boeing 777-3GZER VH-VPF
C817CC //Pacific Blue Airlines 737-8FE/W ZK-PBD
E8023E //LAN Chile A-340-313X CC-CQE

You might have your own list, or may have an update to mine. If you've noticed an improvement on any of the above aircraft, please let me know and I'll remove them.
I guess the only real way of knowing if any of these aircraft above still offend is for me to clear my plot's blacklist and compare the plot over time once again.

DaveReid puts it nicely:
Quote:
The only conclusion that can definitely be drawn from a spike is that something has produced an ADS-B transmission that SBS or RadarBox has been able to decode and interpret as an aircraft at a significantly longer ranger than normal.

This could be due to either atmospheric conditions causing reception range to be greater than usual (i.e. the position reports are being correctly decoded), a garbled transmission (one or more bits corrupted) which results in a spurious position report or, in a few cases, an aircraft which is incorrectly encoding its position.

The best way to determine which is the most likely explanation is to look at successive position reports from the same aircraft.
Hope this is of some use for other radar spotters around Australia.
__________________
YSSY Forum Administrator
Reply With Quote
  #2  
Old 27th July 2012, 05:22 PM
Nigel C Nigel C is offline
Prolific Member
 
Join Date: Mar 2008
Location: The farm
Posts: 4,022
Default

Naughty aircraft!
__________________
I am always hungry for a DoG Steak! :-)
Reply With Quote
  #3  
Old 20th August 2012, 08:25 PM
Bob Peake Bob Peake is offline
Member
 
Join Date: Aug 2012
Posts: 2
Default ADS-B "Blacklist"

Karl,

As you would expect, Airservices monitors ADS-B performance and carries out various checks before it uses ADS-B for air traffic control. With respect to the aircraft on your "Blacklist", they fall into several groups

7C6C6F //V Australia Boeing 777-3GZER VH-VPD
7C6C71 //V Australia Boeing 777-3GZER VH-VPF
C81C17 //Pacific Blue Airlines 737-8FE ZK-PBK
C817CC //Pacific Blue Airlines 737-8FE/W ZK-PBD
This group were all equipped with a version of a Mode S / ADS-B transponder that had a fault. This fault has now been fixed, so you can remove them from your blacklist.

E8023F //LAN Chile A-340-313X CC-CQF
E8023E //LAN Chile A-340-313X CC-CQE
These two aircraft are fitted with an old GPS transponder that does not meet CASA's requirements for an ADS-B data source. They should be upgraded before the flight level 290 and above ADS-b mandate comes into force in December 2012.

7C4366 //Nauru Air Corporation 737-33A VH-NLK
The standard ADS-B message from an aircraft includes information about the accuracy and integrity of the data source. This information is ignored by boxes like the SBS-1, but is critical for determining if the data is suitable for air traffic control. Transmissions from this aircraft indicate low accuracy / integrity, so it never gets through to the ATC system. The data source is probably an inertial nav system rather than GPS. Again, it needs to be upgraded before Dec 2013.

7C1473 //Qantas Airways A-330-202 VH-EBP
No problems have been observed with this aircraft. The only suggestion I can think of is that the observed anomaly might have been attributable to the position decoding method used. To unambigously determine an ADS-B position it is necessary to use "global CPR decoding", which requires processing of two separate ADS-B messages, referred to as "odd" and "even" message types. Some processing software uses "local decoding" with only one message, which sometimes produces anomalous results. Suggest you remove this one from your blacklist.

Regards

Bob.
Reply With Quote
  #4  
Old 20th August 2012, 09:59 PM
Bernie P's Avatar
Bernie P Bernie P is offline
Member
 
Join Date: Mar 2008
Location: Western Sydney
Posts: 852
Default

Quote:
Originally Posted by Bob Peake View Post

Karl,

...
I didn't know we had a Karl!?!?
__________________
----------

My Flight Diary

My Photos Flickr Images
Reply With Quote
  #5  
Old 21st August 2012, 01:11 AM
Kurt A Kurt A is offline
YSSY Forum Administrator
 
Join Date: Mar 2008
Location: YSSY
Posts: 956
Default

We can go with Karl, lol.


Hi Bob,

Thanks for updating us with the latest information regarding the "blacklist". This is great news and your update is very much appreciated.

So currently the maintained list looks like this:

Quote:
7C4366 //Nauru Air Corporation 737-33A VH-NLK
E8023F //LAN Chile A-340-313X CC-CQF
E8023E //LAN Chile A-340-313X CC-CQE

Are there others we might need to be aware of presently? Also, might you have any intel on the latest one that Grahame recorded as incorrectly reporting it's position?

Quote:
71BF52 //Korean Air Boeing 777-2B5 HL7752
P.S: I received your PM and am very much in favour of your suggestions. I just hadn't yet had a chance to reply properly with my thoughts. But I very much look forward to working with you to put something together that will be of value.
__________________
YSSY Forum Administrator
Reply With Quote
  #6  
Old 21st August 2012, 02:27 AM
Philip Argy's Avatar
Philip Argy Philip Argy is offline
Senior Member
 
Join Date: May 2008
Location: North Strathfield
Posts: 1,402
Smile Bob's maiden post is very helpful!

Quote:
Originally Posted by Bernie P View Post
I didn't know we had a Karl!?!?
Be nice, Bernard!
__________________
Philip
Reply With Quote
  #7  
Old 21st August 2012, 08:51 AM
Bernie P's Avatar
Bernie P Bernie P is offline
Member
 
Join Date: Mar 2008
Location: Western Sydney
Posts: 852
Default

Haha, Philip, i was thus the at the end

On a similar, but slight different issue, 5/8/12 I was on the following flight

Quote:
VH-TJX TN0494 05/08/2012 21:54 Qantas B737-476 Melbourne-Sydney
(http://16right.com/)

Now this was a QF flight, yet it had the TN details, puzzeled much!!
__________________
----------

My Flight Diary

My Photos Flickr Images
Reply With Quote
  #8  
Old 21st August 2012, 11:40 AM
Grahame Hutchison's Avatar
Grahame Hutchison Grahame Hutchison is offline
Prolific Member
 
Join Date: Mar 2008
Location: Sydney's Eastern Suburbs - View From Bondi To Jibbon Point And Bravo 10 South
Posts: 8,533
Default

Bernie, The old TJ series B737s all transmit the TN flight ID. Don't think they bothered changing it changed when Australian was merged into Qantas way back.
__________________
Joined 1999 @www16Right FlightDiary Airliners Web QR Retired PPL C150/172 PA28-161/181 Pitts S-2B SIM: 12Hr QF B767 B744 CX B742 Nikon D100-D200-D300-D500
Reply With Quote
  #9  
Old 21st August 2012, 08:50 PM
Bob Peake Bob Peake is offline
Member
 
Join Date: Aug 2012
Posts: 2
Default Black list - KAL 777s

Kurt,

Apologies for converting Kurt to Karl in yesterday's post - at least I got two of the four letters right.

Regarding the question about Korean Air Boeing 777-2B5 reg HL7752777, address 71BF52, at present we have all the KAL 777s marked as suspect because they have the same faulty transponder as the Virgin aircraft had. The list includes KAL aircraft with the following addresses
71BD31
71BD32
71BD33
71BD34
71BD73
71BD74
71BD75
71BD98
71BF14
71BF15
71BF33
71BF34
71BF50
71BF51
71BF52
71BF64
71BF65
71BF66
71BF82
71BF83
71BF84
71C208
71C209
71C210
71C222

Sorry to add so many new entries to your blacklist.

Regards

Bob.
Reply With Quote
  #10  
Old 27th August 2012, 09:58 AM
Kurt A Kurt A is offline
YSSY Forum Administrator
 
Join Date: Mar 2008
Location: YSSY
Posts: 956
Default

Thanks Bob,

Thanks for the information. I have updated my list with the KAL entries.
The latest offender was this morning's LAN aircraft, who was seen well over the drink between Perth and South Africa:

Quote:
E8023C //LAN Chile A-340-313X CC-CQA
__________________
YSSY Forum Administrator
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT +10. The time now is 12:59 AM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.
Copyright © Sydney Airport Message Board 1997-2022
Use of this web site constitutes acceptance of the Conditions of Use and Privacy Statement