A380 any one seen these yet?

[flymee1939]

Has anyone seen this fellow on the system and does it come up as A380 in aircraft column.

Flymee

[Runway 31]

They come up as A388

Alan

[neroon79]

I get usually 8 to 12 different A388 per day serving up to 20 different connections.

A388 is the correct ICAO Type designator for A380-8** airframes.

[Budgie]

Yep, I've had 5 today.
2 x Air France
2 x Lufthansa
1 x Emirates

[Team Spirit]

Yes, I've picked up 10 today :)
4 x AIRFRANCE
2 x EMIRATES
4 x LUFTHANSA
And I had the pleasure in flying in one last year LHR to CDG and return " most excellent it was too " :)

Here's a pic of the actual aircraft and below a model in 1/200 scale which I bought at CDG prior to boarding for the flight back to Heathrow.

[dxman]

today :

4 Emirates
2 Quantas
2 Singapore airlines
5 Lufthansa

overall in total 44 different ones

[ACW367]

Has anyone seen this fellow on the system and does it come up as A380 in aircraft column.

Flymee

As Alan explained the correct code is A388 and that is the code with the silhouette. If you pick newly delivered ones up on the network, the incredibly annoying Airnav bug will populate them to your existing navdata with incorrect short code A380, even though they are in our DB as A388. This will only be corrected on your system if you upload a subsequent new Navdata containing our DB work, issued roughly monthly.  Even then if it is in your Mylog, uploading the new Navdata alone will not correct the Mylog entry. It will only correct when you pick up the aircraft physically on your box again following the upload. 

Newly delivered Boeing 777 Freighters will also incorrectly display B77F instead of the correct ICAO of B77L you should be getting from our DB.

If you search back through the forum you will find many threads explaining this.  Hope that helps explain a longstanding issue.

[neroon79]

Additional to the mentioned A388/A380 and B77L/B77F there is the same bug-problem with the K35R which will populate as KC35(as far as I remember) and the C17, which will populate as BC3. This will especially an issue, if you are using an old database delivered on the ANRB Software CD. If you are not living an in area with a huge amount of airframes using false ICAO Hex addresses it's highly recommended to download the latest Database release available in this forum. Even if you do so, you have to go through your database and manually correct the designators of all newly populated airframes of the mentioned Type. Furthermore almost al smaller AC are populating without the designator at all.

My A388 List from yesterday:

1.    VH-OQH   Airbus        A380-842  QFA9      7C4927  Australia    au   23/08/2011  03:08
2.    9V-SKJ   Airbus        A380-841  SIA322    76CD6A  Singapore    sg   23/08/2011  03:18
3.    VH-OQF   Airbus        A380-841  QFA31     7C4925  Australia    au   23/08/2011  04:10
4.    D-AIMA   Airbus        A380-841  DLH401    3C65A1  Germany      de   23/08/2011  04:24
5.    F-WWSF   Airbus        A380      AIB031C   383F1A  France       fr   23/08/2011  08:05
4b.   D-AIMA   Airbus        A380-841  DLH454    3C65A1  Germany      de   23/08/2011  08:38
6.    D-AIMF   Airbus        A380-841  DLH400    3C65A6  Germany      de   23/08/2011  09:27
7.    A6-EDC   Airbus        A380-861  UAE202    8960E4  United Arab  ae   23/08/2011  09:58
8.    D-AIMC   Airbus        A380-841  DLH455    3C65A3  Germany      de   23/08/2011  10:12
9.    A6-EDA   Airbus        A380-861  UAE17     8960E2  United Arab  ae   23/08/2011  10:29
10.   A6-EDG   Airbus        A380-861  UAE1      8960E8  United Arab  ae   23/08/2011  10:32
11.   9V-SKB   Airbus        A380-841  SIA333    76CD62  Singapore    sg   23/08/2011  11:03
12.   D-AIMD   Airbus        A380-841  DLH721    3C65A4  Germany      de   23/08/2011  11:40
2b.   9V-SKJ   Airbus        A380-841  SIA317    76CD6A  Singapore    sg   23/08/2011  11:56
1b.   VH-OQH   Airbus        A380-842  QFA32     7C4927  Australia    au   23/08/2011  12:24
13.   D-AIMB   Airbus        A380-841  DLH711    3C65A2  Germany      de   23/08/2011  13:25
14.   D-AIME   Airbus        A380-841  --------  3C65A5  Germany      de   23/08/2011  13:59
14.   D-AIME   Airbus        A380-841  DLH710    3C65A5  Germany      de   23/08/2011  14:00
9b.   A6-EDA   Airbus        A380-861  UAE18     8960E2  United Arab  ae   23/08/2011  14:28
10b.  A6-EDG   Airbus        A380-861  UAE2      8960E8  United Arab  ae   23/08/2011  14:50
15.   9V-SKK   Airbus        A380-841  SIA318    76CD6B  Singapore    sg   23/08/2011  16:52
16.   A6-EDE   Airbus        A380-861  UAE3      8960E6  United Arab  ae   23/08/2011  16:57
12b.  D-AIMD   Airbus        A380-841  DLH720    3C65A4  Germany      de   23/08/2011  17:10
3b.   VH-OQF   Airbus        A380-841  QFA10     7C4925  Australia    au   23/08/2011  21:31
15b.  9V-SKK   Airbus        A380-841  SIA321    76CD6B  Singapore    sg   23/08/2011  22:01

[flymee1939]

Thanks for your reply folks will be keeping my eyes on the lookout and will report my first sighting.

Hi Alan good to see your reply too.

Flymee

[EK01]

Has anyone seen this fellow on the system and does it come up as A380 in aircraft column.

Flymee

As Alan explained the correct code is A388 and that is the code with the silhouette. If you pick newly delivered ones up on the network, the incredibly annoying Airnav bug will populate them to your existing navdata with incorrect short code A380, even though they are in our DB as A388. This will only be corrected on your system if you upload a subsequent new Navdata containing our DB work, issued roughly monthly.  Even then if it is in your Mylog, uploading the new Navdata alone will not correct the Mylog entry. It will only correct when you pick up the aircraft physically on your box again following the upload. 

Newly delivered Boeing 777 Freighters will also incorrectly display B77F instead of the correct ICAO of B77L you should be getting from our DB.

If you search back through the forum you will find many threads explaining this.  Hope that helps explain a longstanding issue.

Not a serious issue but I think I know which anti AN site will pick up this one and, no doubt, one very bitter banned AN forum member in particular.

[eyeinthesky]

Your right not a serious issue, but you know who will be raving about it on another site, "he is a little child who has lost his rattle on here".LOL

[EK01]

Eye in the sky,

You are right. It didn't take them long. Once again they seem to recognise not only their anti AN site but even themselves from a description only. Interesting to note however a number of posts now coming through on their forum from their own contributors who are beginning to find the continual anti AN comments from two of their members in particular just a little tiresome.

Methinks they need to get out more !

Edit:  picked up 2 hours after their post first appeared apparently. just goes to show some of us have better things to do than spending our time continually checking a site we are banned from for little snippets to be critical about. Dear oh dear.

[flymee1939]

Cracked it!

Seen levelled at EGLL A388 QFA32 VH-OQE  Quantas. My first. (A few minutes ago)

My data shows this as A388 does that mean my data is up to date?
When I say data I mean network table.

flymee

[orkney]

Hello

Congratulations :-). It should indeed say A388.

Andrew

[neroon79]

Was it really necessary to mention this "other" site?

Do not touch any chains end without seeing the other end, because you don't know which kind of animal is on the other end. ;-)