Missing Aircraft Types in My Flights

[jgrloit]

It seems as though it is not just the aircraft table that needs more update capability.
The routes table is also being talked about, and that will not be updated by the mylogs, autopopulate routine!!!

[tarbat]

The routes table is also being talked about, and that will not be updated by the mylogs, autopopulate routine!!!

Routes in the route table have a date against them, and they auto-expire after a month (I think).

[AirNav Support]

The aircraft type has been discussed at length recently as well. Please have a search of the forum.

Routes are updated as they have timestamp, and once a specfic time has passed they are rechecked with our servers.

[jgrloit]

That did NOT happen during the last changeover in March.
I was still seeing routes, without the intermediate routing, as the aircraft regularly landed at EGNT.
Most were to or from AGPF and heading to the med!!!

[tarbat]

That did NOT happen during the last changeover in March.
I was still seeing routes, without the intermediate routing, as the aircraft regularly landed at EGNT.
Most were to or from AGPF and heading to the med!!!

Remember it can take uo to a month before the current route in the database reaches its expiry date.  So the routes can be wrong for up to a month.

[EGNXR]

Yes, it should.  But sometimes when you FIRST see an aircraft, the GAS details aren't complete.  So it populates with "...".  What's needed is a way to force an update at a later date, and that's what Airnav need to develop, in my opinion.

I agree, and when the dust settles on V3.0 beta it will be very high on my wish list for V3.1

So I'll keep manually updating while I get my head around SQL. (Every days a school day)

The aircraft type has been discussed at length recently as well. Please have a search of the forum.

Airnav, the link to this thread is in an earlier reply. The outcome of the thread is open ended as there seems no definate answer to where the wrong short types are coming from or what is going to be done about it from your end?

Its one for the wish list for after V3.0 beta is all sorted. But we will cross that bridge later, I appreciate you have enough on with snagging the Beta.

Cheers John

[DaveReid]

But sometimes when you FIRST see an aircraft, the GAS details aren't complete.  So it populates with "..."

I'm confused - are we saying that GAS has "..." in the type field, which RadarBox reproduces, or that RadarBox itself populates the type with "..." when GAS doesn't have any details?

Although the end result would be the same, we're talking about a different fix in each case.

[EGNXR]

I'm confused - are we saying that GAS has "..." in the type field, which RadarBox reproduces, or that RadarBox itself populates the type with "..." when GAS doesn't have any details?

Although the end result would be the same, we're talking about a different fix in each case.

Dave, A quick scroll through network traffic produced this in Database Explorer.

OO-TAE was the last new aircraft my box picked up localy, the rest are from Network traffic. Note the BMD0 which on network shows DC10 N373FE and the differance with the screen shot of what shows in myflights. VERY STRANGE!

John

[mighty3507]

I'm confused - are we saying that GAS has "..." in the type field, which RadarBox reproduces, or that RadarBox itself populates the type with "..." when GAS doesn't have any details?

Although the end result would be the same, we're talking about a different fix in each case.

This is the issue I am seeing. I see the correct ICAO aircraft type for an aircraft in GAS. However, that value never gets populated into the AT column of my Aircraft database. I get '...' instead.  This appears to be occurring for all aircraft that are not Boeing or Airbus.

For example,  AC9AAE. This is an Delta Airlines MD 90. GAS shows an ICAO Type of 'MD90'.  I saw this aircraft in my flights  with the '...' for AT. I used the DB explorer  to delete the aircraft. I then closed RB and reopened.  The '...' value for AT was brought back in.

I know there have been issues with incorrect values getting into GAS and then brought in to RB. I am just wondering why values I see in GAS do not come into my DB.

--Steve

[tarbat]

I'm confused - are we saying that GAS has "..." in the type field, which RadarBox reproduces, or that RadarBox itself populates the type with "..." when GAS doesn't have any details?

Don't know - only Airnav can answer that.  My guess is that, when first seen, the ICAO type is probably empty in GAS, and the Airnav server inserts the "..." in ICAO Type.  At some later date someone updates GAS with the ICAO Type, but that never gets to the Airnav servers.

But that is all guesswork.

[malc41]

Which I assume goes back to what tarbat said before about once the ... is in the short column it is not updated?

[tarbat]

Which I assume goes back to what tarbat said before about once the ... is in the short column it is not updated?

Correct - unless you correct it manually.

[DaveReid]

Don't know - only Airnav can answer that.  My guess is that, when first seen, the ICAO type is probably empty in GAS, and the Airnav server inserts the "..." in ICAO Type.  At some later date someone updates GAS with the ICAO Type, but that never gets to the Airnav servers.

But that is all guesswork.

Fair enough.

Anyway, the good news is that, once V3.0 has settled down, I've been told that evaluating various options for getting the aircraft and photo details right is a priority from AirNav's point of view.

So expect to see a distinct improvement in the not-too-distant future.

[malc41]

And so say all of us