AirNav Systems Forum
AirNav RadarBox and RadarBox24.com => AirNav RadarBox and RadarBox24.com Discussion => Topic started by: DeeJay on April 16, 2009, 04:23:55 PM
-
Deleted database record for G-MIDK, hoping that it would re-appear with the Monarch registration, but it re-appeared as G-MIDK. When I returned to database to find, details were blank. Seems I did something wrong somewhere. Would appreciate any advice.
-
Deejay,
How did you delete the record, did you do it in Database Explorer or in MyLog?
-
Allocator. Thanks your reply. Attempted in Database Explorer.
-
Deejay,
I might be missing what you are trying to do here. I've checked my database using Database Explorer and I get G-MIDK as a BMA aircraft - as is shown in the GAS database doing a manual lookup. Airframes.org is also showing this aircraft as a BMA registered aircraft, so I'm not sure what you mean by getting it to show with a Monarch registration.
When you checked the database using Database Explorer, dir you use the same search criteria as I have below - note that you need to select the "aircraft" table in the drop-down list at the top.
Airframes.org has the following list of Monarch Aircraft:
http://www.airframes.org/fleet/mon
-
Maybe you mean something along these lines?
See this clip from my Network tab. G-MIDK is owned by BMI, but is operating as a Monarch flight. The Company data is from the GAS database and the Airline Logo is generated by the Flight ID - at least by the MON part of it.
-
Allacator. Thanks your explanation. Clarified all.
-
Maybe you mean something along these lines?
See this clip from my Network tab. G-MIDK is owned by BMI, but is operating as a Monarch flight. The Company data is from the GAS database and the Airline Logo is generated by the Flight ID - at least by the MON part of it.
Allocator, I see you have two that need updating:-)
G-TTIB = G-OZBP & G-TTIH = G-OZBT
HTH Cheers John
-
According to Airframe.org and G-INFO
G-MIDK is reregistered as G-OZBN
G-MIDM is reregistered as G-OZBO
Stewart
-
According to Airframe.org and G-INFO
G-MIDK is reregistered as G-OZBN
G-MIDM is reregistered as G-OZBO
Stewart
OK, easy fix, Run Database Explorer and change the registrations and operator details. See below - Searched for G-MIDK, record found, changed Registration and Airline (AC) fields and deleted photo links in PT/LK/PT2/LK2 so hopefully the photo for the new registration will update next time the aircraft is detected. Same deal for G-MIDM
RB uses the information in the GAS database, so it will only ever update to what GAS shows. GAS is maintained by a group of unpaid volunteers, so it will take a little time to catch up.
-
CAn AirNav please look at how they update their master Database from GAS, as I have found some aircraft with updated details on the GAS server, where the AirNav server is still sending extracted data:-
From AirNav
3C656F - D-AIKO as per extract
from GAS -
D-AIKO Airbus A-330-343E A333 989 L2J 3C656F DLH [LH] Lufthansa 2009 D-WWKJ 2009-02-19
Thanks.
-
I can't see details for Hex code 3C656F on GAS.
Are you sure that you are not using airframes.org to show that detail for D-AKIO?
-
G-MIDK re-registered as G-OZBN on 2 April 2007
G-MIDM re-registered as G-OZBO on 14 May 2007
G-TTIB re-registered as G-OZBP on 6 February 2008
G-TTIH re-registered as G-OZBT on 25 February 2009
so database sources are very out of date....
-
Allocator - sory wrong source for Info.....
-
G-MIDK re-registered as G-OZBN on 2 April 2007
G-MIDM re-registered as G-OZBO on 14 May 2007
G-TTIB re-registered as G-OZBP on 6 February 2008
G-TTIH re-registered as G-OZBT on 25 February 2009
so database sources are very out of date....
Remember, the GAS team update their database as and when they can, on a purely voluntary and unpaid basis. Thank goodness they do this, otherwise our RB information would be very sparse. Airframes.org will not allow automated look-ups, as they state on their site - no bots
No bots, spiders, scrapers, scripted or otherwise automated queries, please.
As an exception, bots are tolerated only as long as they respect the robots.txt standard and if their purpose is to index this site to be included in a public search engine. And that is just a handfull like Google, MSN, Yahoo, etc.
Spidering this site violating this rule by sending private harvesting bots or otherwise sending automated queries is considered abuse. Violating bots will be blocked and/or publicly listed.
GAS are quite happy for individuals to send them updates, maybe you should do this and help them out?
If you wish to have updates from your own personal confirmed entries, please submit them for inclusion via the form below.
Alternatively you can EMail lists to ModeSdata.
-
We did try and contact airframes and come to an agreement but were unable to reach an agreement which would be beneficial to our customers.
Please remember there isn't a database anywhere which has handles these updates and GAS is doing a great job, as Allocator says they are unpaid volunteers.
GAS and us need the help of all the members to keep up to date with registration changes and get them sent in.
-
There, my Monarch Airlines re-registrations updated using Database Explorer - Two minute job :-)
Are there any more that I've missed?
If the sequence runs right through, maybe:
G-OZBA
G-OZBC
G-OZBD
G-OZBM
G-OZBQ
G-OZBS
-
Managed to find a few more in the sequence using GAS and airframes.org - some re-registered and some that I didn't have in my database.
Details added manually using Database Explorer.
-
G-OBZA re-registered in Jamaica
G-OBZC re-registered in Hong Kong
G-OBZD re-registered in Ireland
G-OBZJ re-registered in USA
G-OZBM 4007E5 AIRBUS A321-231 Monarch Airlines
G-OZBS 4008CB AIRBUS A321-231 Monarch Airlines
-
Allocator
You may want to check out my posts here
http://www.airnavsystems.com/forum/index.php?topic=2102.msg17339#msg17339
This gives a list of some common mode S re-registrations and miscodes seen in the UK .
-
Thanks for that, keeping any database up to date could be a full time job!
My posts were really just to show how the source information can be incorrect and how easy it is to manually update the NavData.db3 database. I quite enjoy tracking down these changes and updating manually, but some people want all to data to be provided automatically and 100% accurate - which is virtually impossible - lol
-
Hi all,
A few more out of date from the database.
400D10 G-ECIL now G-MRDC R44
4006B9 G-BXKB now G-OMYA A320
40132F G-CZNA now G-SPNA B763
40099A G-OOAW now G-OOPW A320
40075D G-BYZJ B733 now SE-RHT Viking de-reg'd 17-04-09 this may still be hangered at EGNX
400778 G-OGBE B733 to be OY-JTE for Jet Time hangered EGNX
HTH Cheers John