Caesar,
The best course of action in cases like this is to email
ops@pilotedge.net as shown on the Contact page of the web site. It's not that we don't want people discussing it, but this isn't really something the wider PE community can specifically help with. If you have a real world procedural question, or a technical sim question, or a story to share, the forum is fantastic. But, specific questions about incidences on the network are best handled through an email to
ops@pilotedge.net. Peter and I are the only people who can actually resolve this specific question for you.
That said, since it's being discussed, we can handle it here. It turns out there is some confusion here. When the V3 was written (long, long ago), there was no intention to REQUIRE a pilot to do the flight without landing elsewhere. However, from an operational standpoint, any kind of a stop along the way would need to be relatively short, otherwise it would place a unique burden on the testing process (ie, the notion of a test taking 5 hours and having to survive several controller shift changes). However, this was never addressed either way with controllers when the training program was brought to PilotEdge. I've personally let pilots do a full stop taxi back at VNY upon request, but I've just learned that other pilots have been failed for attempting the same thing, so we have not been consistent in this regard. Unfortunately, I wasn't aware of this until now.
Peter and I discussed it and the decision is to EXPLICITLY prohibit any landings prior to the full stop landing at Torrance, purely to avoid the possibility of the test being drawn out. Certainly, there's nothing easier or harder from a pilot's perspective whether you stop or not, that's not the issue. It's purely related to the operational implications of resuming a test some unknown number of minutes/hours after the first half is flown. So, to avoid any type of slippery slope, the V3 text will be updated to show that landings are prohibited prior to TOA.
Since there was nothing prohibiting a temporary stop in the V3 material as it stood at the time of your test, I have made arrangements for you to be able to resume the test from SMO, receiving credit for the portion that was already flown. You can start from SMO, complete a south-bound transition (other than the one you have already flown, I believe it was the Mini Route) and then land at TOA. Advise the controller that you are resuming a V-3 with the Mini Route already completed, and that the controller should mark it as a pass with a note saying, "2nd half of V-3," and then Peter will take care of it from there. Of course, this assumes you have no issues during the second transition.
Sorry for the confusion. We try to eradicate any inconsistencies when we see them. Hopefully you can continue to enjoy the network from this point on. Try not to get too rattled by what happens, have faith that we can resolve it after the fact. For instance, rather than being upset about this fail, you could reasonably expect to escalate this to support/ops and receive some type of resolution....in this case, full credit for the portion flown. It's not something the controllers can resolve in real time, but we can generally get things cleared up offline.