I just noted a small "bug" probably present in all versions of SD. When planning a border crossing flight and adding a published border crossing reporting point, SD will still add its own border crossing point in the flightplan in lat/lon notation. To wit, a flight from Graz (LOWG) to Maribor (LJMB) with a border crossing point of OLMOT will still insert another border crossing point.

I suggest to omit the calculated crossing point in case there already is a waypoint in the flightplan which is within 5 miles (measured along the planned route) of the physical border crossing.

Also, what were thise superfluous DCT's in the route portion? In Austria this drives the controller crazy. Have got an admonishing call twice because of them.

-- Chris.

Well, just to prove I'm not making this up it is all spelled out in this document:
http://www.austrocontrol.at/jart/prj3/austro_control/data/dokumente/bbABB_227_tcm586-72348.pdf

Specifically, according to ICAO, you are supposed to use DCT if the departure point is not on an ATS route, followed by the first point on the ATS route and then the route designator. Or, if you are leaving an ATS route, use DCT before the first off-route point, except if both of these points are specified by geographical coordinates. For flights off ATS routes, use DCT between successive points unless both of them are given by geographical coordinates or radial and distance from a radio navigation aid.

So, it seems you are doing it correctly if, indeed, you abstain from using DCT between points given in lat/lon format (I haven't checked this yet.

Austrocontrol do, however, specify that for flights inside the FIR Vienna, DCT must only be used by flights of the Austrian military if their mission so demands and flights for geographic surveying.

Oh well, -- Chris.