7
$\begingroup$

There are a few victor airways that cross without a named fix, just two solid lines drawn over each other on the IFR low charts. Can these be used as intersections for changing airways in IFR route planning? Assuming you are above MEA for both, prior to the crossing. They aren't very common but I happen to have one very near my usual airport that along with a poor DP makes planning for certain directions rather tedious.

Examples

  • the crossing of V55 and V170 just north of JMS VOR on chart enroute L-14 North Dakota;
  • V495 and V23 with V187 over Tacoma(this one may be due to SEA class B) ;
  • V183 NE of RZS near Santa Barbra, could you plan to turn north from V183 onto V485 or V107?
$\endgroup$
  • $\begingroup$ Interesting question. Bullet #2 is in my neck of the woods so I checked it out. (I don’t see V495 coming into play though...) I think it would be a problem, mainly with planning and filing because ForeFlight wouldn’t allow or show the transition when I tried just now. But, perhaps you could get around it creatively? E.i. File: “SEA, V23, (request radar vectors) V187, RADDY...” Or, pull up a lat/long for the point and insert into flight plan? $\endgroup$ – Michael Hall Sep 2 at 16:25
  • $\begingroup$ I may need to modify my question, my intent was focused on fully by the book flight plans, usable with lost comms or lost radar and using traditional nav. (excluding RNAV.) More of a pure theory question. $\endgroup$ – Max Power Sep 3 at 0:17
  • 1
    $\begingroup$ Given all those conditions I think the answer is probably no. But truly the only limiting factor is that the intersection doesn't have a name. Because it is an intersection... $\endgroup$ – Michael Hall Sep 3 at 1:01

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.