A Reddit thread in r/flying raises a recurring point of confusion in commercial pilot training: the precise wording of 14 CFR 61.129's cross-country requirements for the day and night 2-hour training flights required for the Commercial Pilot Certificate (airplane, single-engine). The regulation specifies that these training flights must include "a total straight line distance of more than 100 nautical miles from the original point of departure." The poster's question—whether a round trip between Van Nuys (KVNY) and Santa Barbara (KSBA), each leg measuring 68nm, would satisfy the requirement—gets at a subtlety that trips up flight instructors and students alike: does the 100nm threshold apply to the straight-line distance to the single farthest point from departure, or can it be satisfied by summing multiple legs of a multi-stop flight?
The regulatory language is unambiguous on close reading, even though it's easy to misapply. "Straight line distance from the original point of departure" means the qualifying distance is measured as a single straight line from where the flight began to the point on the route that is farthest from that origin—not the cumulative distance flown across multiple legs. A KVNY-KSBA-KVNY round trip, even though it totals 136nm of flying, only ever gets the aircraft 68nm away from Van Nuys in a straight line, which falls well short of the 100nm minimum. This is functionally the same analysis pilots must apply to the more well-known 61.129(a)(4) cross-country requirement (250nm total distance with landings at three points, one leg of at least 100nm straight-line distance)—the straight-line leg requirement there causes identical confusion, and the FAA has issued guidance and legal interpretations over the years reinforcing that "straight line distance" is not synonymous with total distance flown or even the total distance of a multi-leg route.
This distinction matters significantly for working CFIs, DPEs, and commercial applicants because a training flight or cross-country that fails to meet the strict straight-line distance requirement does not count toward the certification requirement, even if it was logged as a cross-country flight under the broader definition in 61.1 (which only requires a landing more than 50nm from origin for most purposes). This creates a two-tiered trap: a flight can be a legitimate "cross-country" for logging purposes generally, yet still fail to satisfy the specific distance requirements baked into 61.129 for commercial training. Instructors who don't carefully map out straight-line distances before scheduling training routes risk having students fly qualifying-looking trips that don't actually satisfy the reg, forcing a repeat flight, additional cost, and schedule delays—an outcome nobody wants during an already expensive and time-compressed commercial training sequence.
For pilots and flight schools operating in geographically compact regions—Southern California being a prime example, with numerous towered airports clustered within 60-80nm of each other—this regulatory nuance has practical route-planning consequences. Instructors need to select destinations genuinely beyond the 100nm straight-line threshold (for example, KVNY to airports like Bishop, Fresno, or Las Vegas rather than closer-in fields like Santa Barbara) to ensure training flights count on the first attempt. This kind of granular regulatory literacy—knowing the difference between cumulative distance and straight-line distance, and between the general cross-country definition and certificate-specific cross-country requirements—reflects a broader theme in part 61 training: the regulations are precise and unforgiving, and misreading them costs real time and money. It's also a reminder that even experienced instructors benefit from periodically revisiting FAA legal interpretations and AC 61-65 guidance, since these details are exactly the kind of thing that get glossed over in ground school but scrutinized during a practical test or an insurance/logbook audit.