The Vertx DA62 has a navigation database containing SIDs and STARs but I can’t find it. Looked in all the usual places but to no avail.

There has to be one because SIDs and STARs don’t ship with the default program. Or do they?

There are SIDs and STARs baked into the P3D scenery database.  If you open up an airfield with ADE and look at the raw data view, you'll see the approach data.

Only way to update that is using FSAeroData to replace the default base scenery with recompiled versions that bring in Navigraph data, AFAIK, which can bring side effects to other programs with it.

That's the primary reason I stayed away from the Vertx DA62--I'm uncomfortable with having to make a change that affects the entire system just for one add-on.

Thanks Bob. I'll load EGCC and check what ADE reports. I've used it many times but don't recall seeing that data.

But look at this site. I update the P3D files with this package each AIRAC cycle. Isn't this doing the same as FSAeroData?
https://aero.sors.fr/navaids3.html

When you say "the P3D database" is that a specific file generated by reading all the data in the BGLs? If so then if I update the default BGLs using the above site then surely my data would be up to date?

Do you know of a recent SID or STAR I can check to see if it's been updated?

1 hour ago, Ray Proudfoot said:

But look at this site. I update the P3D files with this package each AIRAC cycle. Isn't this doing the same as FSAeroData?
https://aero.sors.fr/navaids3.html

When you say "the P3D database" is that a specific file generated by reading all the data in the BGLs? If so then if I update the default BGLs using the above site then surely my data would be up to date?

Do you know of a recent SID or STAR I can check to see if it's been updated?

The Herve Sors update you linked to only updates the navaids.  It does not, AFAIK, change any of the fixes, legs, leg types etc, which are also coded into the base scenery bgls.  Most advanced add-ons use their own internal database for the approach/SID/STAR routes rather than what's coded into the base scenery.  A much better way of doing business, IMHO.

By "P3D database" I mean the collection of all the default bgl files in P3D root\scenery

You can look at the BENKY6 arrival into KORD--it changed from the BENKY5 this cycle, and waypoint/VOR BDF was replaced in the STAR track with waypoint BFORD

 

Thanks Bob. I've never used the Approach option in ADE before but here are two screenshots showing first the default and then the FSDT KORDv2 approaches. I can't see BENKY6 in either.

Is this the info you're referring to?

 

Of course the problem with keeping default approaches up to date is if you have a third party airport and that BGL takes priority anyway.

An updated AFD would be required and is that really going to be near the top of the developer's priority list? Doubt it. Bit of a nightmare really. You would have to use default airports only to keep all the data up to date and who's going to do that?

25 minutes ago, Ray Proudfoot said:

I can't see BENKY6 in either.

You are listing only approaches, not Arrivals?

Speaking strictly about approach fixes, they reflect real world (LAIKE is the G/S intercept fix for ILS 22L, for example)

1 hour ago, SAS443 said:

You are listing only approaches, not Arrivals?

Speaking strictly about approach fixes, they reflect real world (LAIKE is the G/S intercept fix for ILS 22L, for example)

I didn’t see Arrivals listed. Are they stored in a AFD file?

3 minutes ago, Ray Proudfoot said:

I didn’t see Arrivals listed. Are they stored in a AFD file?

Now I'm not so sure...I found some of the STAR waypoints listed in the raw data for the stock KORD (like BENKY) as "Route Waypoints"...in fact it's odd that now in ADE I don't have that "Approaches" page you showed above.

 

16 minutes ago, w6kd said:

Now I'm not so sure...I found some of the STAR waypoints listed in the raw data for the stock KORD (like BENKY) as "Route Waypoints"...in fact it's odd that now in ADE I don't have that "Approaches" page you showed above.

 

Did you select Approach in the top right? It defaults to Airport. That changes the options in the menu from where you can select Approach info.

I opened the UK2000 AFD for my local airport - EGCC - and listed Approaches. DAYNE is a STAR but doesn’t show. I don’t think it includes the name of the STAR. Bit of a mystery really.

Thinking more about this data in the AFD I don’t think it includes the STAR or SID info. Just the info for the type of approach for each runway. ILS, VOR etc. It probably extends no further than the FAF for each runway.

Looking at my own airport, Manchester, the runway designators haven’t changed for around 10 years when magnetic variation caused 06L/24R to change to 05L/23R. STAR names haven’t changed in years.

Even if Vertx is using core data several years old the vast majority of it will still be valid. I don’t think it’s a seriously enough problem to require a subscription to bring it up to date.

Does anyone know if SIDs and STARs are held in the default files? Something tells me they’re not since no default aircraft have a FMS capable of reading them. Only Navigraph generate them for 3rd party addons like PMDG737 etc.

If I remember correctly ,people were lamenting the fact that there was no way to access Navigraph in da62. I bought one cycle from fsaerodata so I had navaids ,artcc and approaches updated and used that until I went to v5. Ive never seen a sid / star in Da62, only approaches.

@rickgo, thanks for that. I’ll check the approaches for Manchester tomorrow.

I don’t know how difficult or expensive it is to get Navigraph to make specific data available. I use a freeware program for Concorde (CPS-X) and the author was able to get Navigraph to include his data. I can’t imagine he would have paid much for it and it’s still available now even though his program is now freeware and unsupported.

If Sean does return to his DA62 perhaps he could approach Navigraph about getting them to add his aircraft to their service.

@Ray Proudfoot when we begged Sean to support Navigraph FMS data he said it was unlikely since he basically would need to start from scratch with the G1000 code. Not happening...(but one can only hope)

@SAS443, that’s a real pity. It’s such a well written piece of code you wonder why he didn’t give the nav data more attention given its importance.