A pilot on a VFR right-traffic pattern encountered a small patch of cloud at 1,100 feet AGL roughly a mile from the runway on final approach. Rather than fly through the cloud or accept a lateral offset that would have still allowed alignment with the centerline before touchdown, the pilot chose to maneuver around the cloud, drift off the extended runway centerline, and then request a left turn back to tower to re-sequence for landing. Tower approved the request without issue. The pilot later brought the scenario to a Reddit flying forum, where fellow pilots debated whether flying through such a small cloud fragment would have been acceptable given the brief duration of instrument conditions it would have created, and whether repositioning from an offset final was a viable alternative to the go-around-style maneuver actually flown.
The core issue at hand is cloud clearance compliance under 14 CFR 91.155 for VFR flight. In Class D, C, or B airspace typically found around towered airports below 10,000 feet MSL, VFR pilots must remain 500 feet below, 1,000 feet above, and 2,000 feet horizontally from clouds, with reduced clearance (clear of clouds) permitted only in Class G airspace at certain altitudes. A wisp of cloud at 1,100 feet AGL a mile from the runway is a scenario many pilots have faced, and the temptation to simply "punch through" a small patch is common, especially when the alternative involves added workload, radio calls, and pattern disruption. However, intentionally penetrating cloud in VFR flight, even briefly, is a regulatory violation regardless of duration, and it also strips away the pilot's outside visual references at low altitude in the traffic pattern, a phase of flight where terrain, other aircraft, and obstacles demand full attention. The pilot in this scenario made the conservative and technically correct choice by maintaining cloud clearance and communicating early with tower, which is precisely the kind of decision-making that keeps a minor deviation from becoming a bigger problem.
For working pilots, particularly those flying under Part 91, 135, or instructing under Part 61/141, this scenario is a useful reminder that regulatory compliance and safety margins should never be sacrificed for the sake of pattern efficiency or avoiding a slightly awkward radio call. Tower controllers deal with go-arounds, extended patterns, and re-sequencing requests routinely, and a clear, early call requesting a turn back for realignment is far preferable to arriving high, fast, or misaligned on short final, or to entering cloud without a clearance to do so. This also touches on the broader question of side-loading onto final: while lining up with the centerline before touchdown is technically achievable from an offset position, doing so at low altitude close to the runway compresses the pilot's decision-making window and can mask a destabilized approach. Established stabilized approach criteria, widely taught in both GA and professional training environments, generally call for the aircraft to be established on the extended centerline and in landing configuration by a defined point above the runway, not scrambling to intercept it in the final seconds before touchdown.
More broadly, this incident reflects a recurring theme in general aviation risk management: small, isolated hazards, whether a wisp of cloud, a bird, or a brief traffic conflict, often prompt pilots to weigh regulatory technicalities against practical judgment. The pilots who tend to have the best safety records are those who default to the conservative option and treat air traffic control as a resource for resolving ambiguity rather than an obstacle to efficient pattern work. As training pipelines increasingly emphasize scenario-based decision-making over rote procedure, situations like this one serve as valuable case studies for CFIs and check airmen alike, reinforcing that "go around and try again" is rarely the wrong answer when cloud clearance, stabilized approach criteria, or basic VFR minimums are in question.