NOTAM: KAA-mandated establishment of Viktor Airways

[Hotel26]

(Not a Challenge; not a Mission; more of a Game, and a co-operative one at that...)

"The KAA (Kerbin Aviation Authority) is instituting new Rules that all pilots are required, when operating flights at night or under IMC (Instrument Meteorological Conditions), to file a flight plan to adhere to Viktor Airways.  To this end, the KAA is seeking Airman co-operation in defining Kerbin 'Viktor' Airways."

                                                                                  

Here's an example of the 'Lakes' route between KSC and BKB:

KSC/288-109/HATTR/289-108/COBOL/253-070/FISHY/319-133/HOOKS/312-130/SAUCE/272-090/BKB

"Depart KSC on heading 288; fly inbound to intersection HATTR; then outbound on 289 until intercepting COBOL, etc etc etc..."

In reverse, 090 departing BKB until inbound SAUCE; thence outbound on 130...

The KAA will maintain an up-to-date spread-sheet here of all intersections (4 or 5 character pronounceable names) and 3-letter airport codes, as suggested by participating Airmen.  (and Airwomen).

No suggestion will be scrutinized/accepted by the KAA unless it has received at least one 'Like' from the community.

                                                                                  

Some further information will be furnished in the next response or two in the thread.

In the meantime, to get started, the KAA recommends down-loading it's Operations Certification Aircraft, the Viktor II,and deploying your own intersection nav-aids at the following locations (TBD in the following post) to test operations.

Naturally, you are quite welcome to design your own deployment aircraft and your own nav-aid!

Share your interesting destinations and how to get there!  Name intersections that will routinely be used by lost Kerbals, trying to find their way home -- for the sake of their passengers!!

(Please also consider the Victor III for fully-fledged ground-based relay station network.

 

Edited February 16, 2020 by Hotel26

[Hotel26]

Intersections (defined so far):

HATTR	3.588	-85.711
COBOL	8.834	-101.575
FISHY	4.647	-115.968
HOOKS	11.845	-123.542
SAUCE	20.363	-134.027

Routes:

'Lakes': KSC/288-109/HATTR/289-108/COBOL/253-070/FISHY/319-133/HOOKS/312-130/SAUCE/272-090/BKB

                                                               

Try it out!  Run a Victor II from intersection to intersection (according to coordinates given using e.g. Atmospheric Autopilot) and deploy the aids (descending/slowing to low altitude/speed each time).  I have Haystack open & ready at each drop to Rename the aid to its chosen intersection NAME and to set it from Debris type to Relay.

Then fly the route back, given the plan above.

My next proposed route is likely to be BKB - WMR (Woomerang)

 

 

Edited February 16, 2020 by Hotel26

[Hotel26]

Some background here (developing likely into 'guidelines').

The principal idea is to:

• fly to an intersection
• fly outbound on a charted heading
• before exiting the 100 km visible range of a nav-aid (marking the intersection), pick up reception of the next intersection on the route; and fly inbound to it
• you should never be in contact range of no intersection at all
• until finally arriving at the charted destination

Therefore, intersections should preferably not be closer than 100km (with exceptions) and no further apart than nearly 200km.

Once you fly a test run, you'll get the idea.

A route shouldn't zig-zag too much nor too often, but neither should it ignore existing intersections and over-crowd the Viktor map of intersections.  (This is where community oversight will become important and some occasional re-factoring may possibly occur.)

[Atmospheric Autopilot (or equivalent) is highly recommended!  Double-click an intersection when it becomes visible to select it as target; then select it as Tgt in the AA Cruise Flight Controller to fly inbound.  Select a heading to fly out on the charted course.]

 

 

Edited February 16, 2020 by Hotel26