Ok that make sense. The protected area is four miles on a DME ARC? Haha thankfully I have never had to fly that approach. We use HOT ILS 5 since our airport is M89. It gets fun when your doing VOR 5 outbound and some one is HOT ILS 5 inbound.
The VOR is located on the field and basically you are back tracking the extended centerline.
You got it! Being 0.1 off the arc because of slant range error (I didn't do the math on the error at that altitude/distance but it's small), isn't gonna put you in any danger, therefore the substitution is allowed.
It's too late at night for Trigonometry.
There's a lot of those "we're outbound climbing, you're inbound descending" setups happen regularly in the training environment VFR, doing practice approaches, I've noticed. Real IFR, they wouldn't do it without a solid altitude separation until the targets had passed each other.
Jesse wisely broke off one of those once on one of our approaches in Nebraska when we ended up head to head with someone. "Turn left 30 degrees for traffic."
It's also a great way to set up the question, "What's your minimum safe altitude here and where are you exactly? How far can you fly this direction?" Etc. Ahh distractions.
Which will make you fumble around and look at the MSA ring on the chart if you forgot to brief it. And twiddle with one of the Nav heads. And realize you didn't start a timer. And then thank the evil Instructor angels that this particular approach has DME and it's on the field, so at least you know how far out you are on your mystery vector.
(Yep. Ask me how I know this! Grin!)
And then the next part, "Okay, we're clear of traffic, Skylane 79M you're cleared via own navigation to the [insert approach here] and cleared for the approach."
And you figure out how to get back...
We also had one where we were northwest of KLNK VFR and KLNK approach cleared someone else for the VOR 18 underneath us while we were given "make straight in for 17".
We were both eyeballs-locked on the aircraft only a few hundred feet below us, converging, roughly the same speed once Jesse spotted him first.
We even had enough time to talk about what we'd do if he went missed early and climbed into us for some reason.
Even once we'd swapped sides, his published missed would turn him back into us if he'd have done it early.
We thought that was a bit of a strange situation to put us both in. Us for the left runway, him for the right, crossing, us without an altitude restriction to stay higher at first.
We made up our own restriction since we had been flying that approach and knew what altitude he was *supposed* to be at.
It was night and he was fairly visible after Jesse picked him out of the lights of Lincoln.
With nearly matching speeds there wasn't much "movement" for the eye to pick out. It was more like seeing him because his lights weren't moving and the background lights were. Eerie.
Converging targets at night. Not the smartest thing I've ever seen. If I hadn't been flying that approach and the VOR 17 all week and was just tooling along VFR, I might have sauntered down to his altitude or a lot closer to it by thinking I should be something near pattern altitude a couple miles out.
I'm sure the controller would have straightened it out, but one missed radio call... and enough airtime blocked with "Say again?" would've made that into a close call.