Database Update Requests

[Runway 31]

Thanks Ingo, wish our weather was so nice

Alan

[EK01]

A3C68C - Boeing Test reg?

Chris,

It's N342UP  c/n 37865 a B767-34AER of United Parcel Service on it's first flight today.

Ian

Guys and especially updater team,

I forget to give you the details of this website which is very useful for Boeing updates regarding first flights, etc. Registrations, c/n's, dates, hex codes, photographs. They are all there. It's where I got the details of the UPS first flight. It's updated daily. Apologies if you already have it :

http://boeing-test-flights.blogspot.com/

Ian

[Runway 31]

Thanks Ian, I use it every night to get the new Boeings.  Its very good and usually updated around a couple of hours after the flights.  Wish we had the same thing for Airbuses.

Alan

[YXUphoto]

A9AB62 / N722ED popped up on my box.  FAA doesn't have it registered, so not sure if it is new Reg or wrong code.

(flew between FL170 and FL300)...also have a record of it from Feb. 2010.

[Runway 31]

Cant find anything on it YXU, possibly a miscode. I tried a few searches and got nothing, did it have a flight ID?

Alan

[mike L]

Hi Alan can you add this  4062F0    G-DECR

Mike

[RodBearden]

Hi - I see that ANZ are flying their new 777-300ER's on ANZ1 now. ZK-OKO is populating as a B773 - should be a B77W.

Rod

[ACW367]

Hi - I see that ANZ are flying their new 777-300ER's on ANZ1 now. ZK-OKO is populating as a B773 - should be a B77W.

Rod

Rod that is the ICAO bug corruption still at work.  All new B77W are converted by the system guessing. Despite us entering B77W, that is not what reaches users due to the bug, and instead the system guesses and resolves resolves it to B773.  

[Runway 31]

Hi Mike

4062F0 G-DECR, Pegasus QuikR c/n 8521

Thanks

Alan

[RodBearden]

ACW - I'm quite prepared to accept that it is the bug, but it's a shifty little blighter - ZK-OKN populated OK as a B77W.

Rod

[ACW367]

OKN was in the last navdata release.  The aircraft in the navdata release have the ICAO codes we have given them, the bug only affects aircraft downloaded by a user subsequent to the navdata change. 

Currently when you get OKO it will corrupt to B773.  But when Airnav distribute the next navdata OKO will be included in that release with the B77W code and it will appear on your box as such after that point.

[ACW367]

When you do a 'show all' on the navdata aircraft table, DR10 OO-UAR (44D432) was the last aircraft included in the last navdata update file.  All aircraft above OO-UAR will have the ICAO code that we have entered into the updater. 

Every aircraft that appears below that airframe in the table will have been downloaded from the server subsequent to the navdata release, and every one of the records below OO-UAR is subject to the bug corruption as it passes through the airnav server and before it reaches the user.  Any wrong codes that appear on records below OO-UAR, we have no control of.

[RodBearden]

Many thanks for that explanation, ACW. Much appreciated - and sorry if you've explained that before - I admit I don't pay full attention to this thread.

Rod

[superspotter]

Hi Guys;
A compendium of errors going on here! Just had N118DC a Be35 climb out of Luxembourg. However I suspect the Hexcode is wrong as it was showing A04A9D, this is on a Lear 60 N118HC. Checking on the web found N118DC to be A04A39. Incidentally, to murky the waters further, my Db has N118HC as a Be90!! regards clive.

[EK01]

Hi Guys;
A compendium of errors going on here! Just had N118DC a Be35 climb out of Luxembourg. However I suspect the Hexcode is wrong as it was showing A04A9D, this is on a Lear 60 N118HC. Checking on the web found N118DC to be A04A39. Incidentally, to murky the waters further, my Db has N118HC as a Be90!! regards clive.

Superspotter,

According to the FAA website, N118HC is indeed a Beech C90 c/n LJ-648 operated by Grimaud Inc.  N118DC is a  Beech M35, c/n  D-6548 but showing 'registration pending'

Ian