I know this is a really old post and people don't like dragging up the dead, but after mulling about it I thought it would be appropriate to post this for proper internet records (i.e. people searching for answers from Google or this forums search function) it should be noted that this last post is not correct and is the opinion of the poster, albeit a well structured interpretation and one that I shared prior. The FAA has issued an advisory circular in 2016 (well prior to this thread) which is a bankable document you could take to court with you as evidence you were not in the wrong. This of course unless someone got hurt in which case the FAA says you are pretty much always responsible...essentially the PIC always must exercise due regard which is legalese for you are always the person responsible for the safe outcome of the flight (an example of due regard would be getting a citation for "too fast for conditions" after crashing your car even if you were not, or the officer cannot prove, you were speeding because the officer can in fact prove that you were going too fast to be able to properly control your vehicle).
To the point that it is about nit-picking the wording, I would agree it is highly debated as to whether or not (a) says all must maintain VLOS at all times or whether or not (a) is simply defining for each of those roles what VLOS means and (b) states that any of those mentioned in (a) and maintaining VLOS per (a) may be responsible for VLOS providing there is clear and concise communication as to who is currently maintaining VLOS. Though I would argue that in the former interpretation it would be silly that
optional people are
required to maintain VLOS for the duration of the flight.
Enter the FAA Advisory Circular which clears this up in a normal FAA way which says the PIC is still responsible for anything that happens to the drones when the drone is BVLOS by the PIC for "operational necessity" and does not specify how far or how long this could be (similar language in recent years has been used for manned aircraft as well - for instance icing conditions used to be defined, now there are parameters in which the PIC must calculate to determine if their skills and their aircraft are adequate to operate in the conditions required for safe flight through a certain area). Funny enough this AC was mentioned above but only about the radio comms thing and didn't mention this component.
It should be noted that this AC107-2 was cancelled on February 1, 2021 because there would be conflicting information in the rest of the AC with the new part 107 changes, that said, other than night flying (not applicable in the thread above) no longer requiring a waiver, I believe this interpretation would have nothing new conflicting. As the new rules are pretty new though I could have missed something and welcome that feedback.
See below for the FAA Advisory Circular on the subject:
AC 107-2 5.7
5.7 VLOS Aircraft Operation. The remote PIC and person manipulating the controls must be able to see the small UA at all times during flight. Therefore, the small UA must be operated closely enough to the
CS to ensure visibility requirements are met during small UA operations. This requirement also applies to the VO, if used during the aircraft operation. However,
the person maintaining VLOS may have brief moments in which he or she is not looking directly at
or cannot see the small UA,
but still
retains the capability to see the UA or
quickly maneuver it back to VLOS.
These moments can be for the safety of the operation (e.g., looking at the controller to see battery life remaining) or for
operational necessity. For operational necessity,
the remote PIC or person manipulating the controls
may intentionally maneuver the UA so that he or she loses sight of it for brief periods of time. Should the remote PIC or person manipulating the controls lose VLOS of the small UA, he or she must regain VLOS as soon as practicable. For example, a remote PIC stationed on the ground utilizing a small UA to inspect a rooftop may lose sight of the aircraft for brief periods while inspecting the farthest point of the roof. As another example, a remote PIC conducting a search operation around a fire scene with a small UA may briefly lose sight of the aircraft while it is temporarily behind a dense column of smoke. However, it must be emphasized that even though the remote PIC may briefly lose sight of the small UA, he or she always has the see-and-avoid responsibilities set out in part 107, §§ 107.31 and 107.37. The circumstances of what would prevent a remote PIC from fulfilling those responsibilities will vary, depending on factors such as the type of UAS, the operational environment, and distance between the remote PIC and the UA. For this reason,
there is no specific time interval that interruption of VLOS is permissible, as it would have the effect of potentially allowing a hazardous interruption or prohibiting a reasonable one. If VLOS cannot be regained, the remote PIC or person manipulating the controls should follow pre-determined procedures for a loss of VLOS. These procedures are determined by the capabilities of the sUAS and may include immediately landing the UA, entering hover mode, or returning to home sequence. Thus, the VLOS requirement would not prohibit actions such as scanning the airspace or briefly looking down at the small UA
CS.
Edit: Before someone says I am promoting illegal activity with drones (or someone interprets that the above means you can take the decision lightly), I would clarify that anyone in this scenario must keep in mind this same due regard I talked about earlier which, because due regard is ambiguous, also means your judgement based on the open-endedness still present in the AC and that means your judgement will be compared to that of your peers so if your gut tells you its not in the spirit of the law then it is consequently illegal to conduct the flight. If your gut says otherwise, consider alternative escape routes and proper language with your VO because the issue would be 100% your mistake if the VO says you have a GA plane approaching on the right....which right, his, yours? Consequently I'd assume this is why you have to learn certain aviation language - its why a pilot says "left downwind of 33" as everyone listening knows the pilot is heading 150 with runway 33 on his left and at pattern altitude and distance from the airport. What is your breakaway procedure, land, return to home? Return to home would not be my go-to because my UAV usually goes up first then home to avoid terrain. In a helicopter during high risk work, anyone could state break-away which meant for us to make an evasive maneuver back and to the right, if that would actually put us in more risk there were alternative procedures in place for language or actions. One such scenario where an obstacle "snuck up on us" was in fact a drone. If you think your drone is just going to smash up against a rotorcraft you could be right, but a measly small bird can take down a helicopter if they hit in the right spot. If you think a pilot should never be below 400ft AGL and your plan is based on that, think again, we were flying 50ft AGL sometimes, with usually 3 people on board in collaboration with a state EOC (so we were supposed to be doing what we were doing). Going back to my point about lingo, intentional or not, I think it makes sense that a hobbyist specifically has the restriction of a directly adjacent spotter vs. a commercial PIC who has a better understanding of his airspace and is given the latitude to identify safe operational needs (also fair to point out that a hobbyist never has an operational "need"). On that note if the brief loss of VLOS space was not one in which no manned aircraft could fly, no people could go, and no property could be damaged (I supposed other than an expensive UAV), I'd likely only consider a spotter who is also part 107 or possibly 61/141 who would be proficient at see and avoid as well as remote communications.