Skip to content
View in the app

A better way to browse. Learn more.

The Drone Talk Hub - The Ultimate Drone Community Hub

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Clouds, Ceilings and Visibility Minimums

FAA ACS — Task III.A: Sources of Weather Information

This closing Module 5 lesson ties everything you've learned about reading weather reports directly to the regulation that governs every Part 107 flight: 14 CFR 107.51. You'll learn how sky condition layers and ceilings are reported, what "ceiling" technically means versus a partial cloud layer, and exactly how the flight visibility and cloud clearance minimums apply to real-world sUAS operations.

3 SMMinimum flight visibility, 107.51
500 ftMin. distance below clouds, 107.51
2,000 ftMin. distance horizontally from clouds
BKN / OVCSky condition codes that create a ceiling

Sky condition layers

A METAR reports sky condition as up to several layers, each with a coverage code and a height in hundreds of feet AGL. The coverage codes describe how much of the sky that layer covers, from clear to fully overcast, and a report can list more than one layer stacked at different altitudes (for example a scattered layer at 5,000 ft with a broken layer above it at 10,000 ft).

SKC / CLR — 0/8 sky coverage (clear; CLR is used by automated stations) FEW — 1/8 to 2/8 sky coverage SCT — Scattered, 3/8 to 4/8 sky coverage BKN — Broken, 5/8 to 7/8 sky coverage OVC — Overcast, 8/8 sky coverage

What officially counts as a "ceiling"

Not every cloud layer is a ceiling. By definition, a ceiling is the height of the lowest layer reported as broken (BKN) or overcast (OVC), or the vertical visibility into an indefinite obscuration (VV). A FEW or SCT layer, no matter how low, is not a ceiling — it describes scattered clouds a pilot can operate around, not a layer that meaningfully caps the sky.

Why the distinction matters operationally

A "BKN020" report means broken clouds at 2,000 ft AGL — a real ceiling that limits how high you can legally and practically climb while maintaining the required distance below clouds. A "SCT020" report at the same altitude is a very different operating picture: scattered clouds you can generally operate beneath or around without the same hard ceiling effect.

Vertical visibility (VV) — the "no ceiling" ceiling

When the sky is obscured (typically by fog, heavy precipitation, blowing snow, or similar) rather than covered by a distinct cloud layer, automated stations report vertical visibility (e.g. "VV004") instead of a normal sky condition group. This is functionally treated as a ceiling for planning purposes, even though there is no discrete cloud base — it represents how far up you could see before the obscuration blocks the view entirely.

Cross-section diagram showing three stacked cloud layers at different altitudes labeled SCT at 5000 feet, BKN at 8000 feet, and OVC at 12000 feet, with an arrow pointing to the BKN layer labeled as the reported ceiling

Only the lowest broken or overcast layer counts as the reported ceiling — scattered layers below or between it do not, even though they still appear in the sky condition group.

View Larger

The flight visibility requirement

107.51 requires a minimum flight visibility, as observed from the location of the control station, of no less than 3 statute miles. This is the same visibility concept you learned to read from METARs and TAFs in earlier lessons — but under Part 107 it must be assessed from the control station's own vantage point, not just pulled from the nearest airport's report.

The cloud clearance requirement

The aircraft must remain at least 500 feet below any cloud and at least 2,000 feet horizontally from any cloud. These distances exist to keep sUAS operations well clear of the airspace where manned aircraft operating under instrument or special VFR procedures might be transitioning through a cloud layer.

14 CFR 107.51(c) — Minimum flight visibility: 3 statute miles 14 CFR 107.51(c) — Minimum distance from clouds: 500 ft below, 2,000 ft horizontal

Applying it to a specific ceiling

If a nearby BKN or OVC layer is reported at a given AGL height, the maximum altitude at which you can legally operate while maintaining the 500 ft vertical clearance is that ceiling height minus 500 ft — always in addition to staying within the 400 ft AGL general operating limit that applies to most Part 107 operations, whichever is more restrictive.

A worked example

METAR reports "BKN018" (broken ceiling at 1,800 ft AGL) and visibility "6SM." Flight visibility (6 SM) clearly exceeds the 3 SM minimum. For cloud clearance, you must stay at least 500 ft below the 1,800 ft ceiling — a maximum of 1,300 ft AGL from that requirement alone. Since most Part 107 operations are already capped at 400 ft AGL, the 400 ft limit is the binding constraint here, not the cloud clearance calculation — but on a lower ceiling (for example BKN005, 500 ft AGL) the cloud clearance requirement could become the binding limit instead.

Code Coverage Counts as a ceiling? Notes
SKC / CLR0/8 (clear)NoCLR is used by automated stations reporting no clouds detected below 12,000 ft.
FEW1/8 – 2/8NoSparse enough that it does not constitute a ceiling regardless of height.
SCT3/8 – 4/8NoStill below the ceiling threshold, though the sky is noticeably more covered than FEW.
BKN5/8 – 7/8YesThe lowest BKN or OVC layer is the reported ceiling height.
OVC8/8 (overcast)YesFull cloud coverage — also counts as the ceiling if it's the lowest BKN/OVC layer.
VV///Obscured sky, no distinct layerYes (functionally)Reported instead of a layer when the sky is obscured; treated as a ceiling for planning purposes.

Checking Visibility and Cloud Clearance Before Launch

Run through this sequence any time a ceiling is reported at or below a few thousand feet AGL.

1

Confirm flight visibility meets the 3 SM minimum

Check the reported visibility from the nearest source, then confirm it against what you can actually observe from your own control station location — the regulation is based on what you can see, not just what a distant station reports.

2

Identify the lowest BKN, OVC, or VV layer

Scan the sky condition group for the lowest layer coded BKN or OVC, or a VV group — that height is your reported ceiling. Ignore FEW and SCT layers for this step.

3

Subtract 500 ft for your vertical clearance ceiling

Ceiling height minus 500 ft gives the maximum altitude at which you can operate while meeting the vertical cloud clearance requirement.

4

Compare against your other altitude limits

Apply whichever limit is lower: the 400 ft AGL general operating cap, any applicable airspace authorization ceiling, or the cloud-clearance-derived altitude from step 3.

Tip: on most low-ceiling days, 400 ft AGL is still well below the cloud-clearance-derived limit, but always run the numbers rather than assuming.
5

Check horizontal clearance from nearby cloud edges

Maintain at least 2,000 ft horizontally from any cloud, not just the layer directly overhead — this matters most near isolated building cumulus or an approaching cell rather than a uniform overcast deck.

Caution: a low, dropping ceiling with deteriorating visibility can turn a legal launch into a non-compliant flight within minutes — monitor conditions throughout the flight, not just at launch.
Mistake Why it happens Correct understanding Regulation / source
Treating any reported cloud layer as a ceilingAll cloud codes look similar in the METAR stringOnly BKN, OVC, or VV layers count as a ceiling — FEW and SCT layers do not, regardless of height.FAA/NWS METAR coding standards
Assuming 400 ft AGL is always the binding altitude limit400 ft AGL is the most commonly cited Part 107 altitude figureA low ceiling can push the cloud-clearance-derived limit below 400 ft AGL — always compare both.14 CFR 107.51
Using a distant airport's reported visibility without checking locallyMETAR visibility is the most readily available number107.51 is based on visibility observed from the control station, which can differ from a report several miles away.14 CFR 107.51(c)
Ignoring horizontal cloud clearance in favor of only checking vertical clearanceVertical distance below clouds feels like the more intuitive numberThe 2,000 ft horizontal clearance also applies and matters especially near isolated cumulus buildups.14 CFR 107.51(c)

Do the 107.51 visibility and cloud clearance rules apply even under a waiver?

A specific waiver or authorization can modify certain 107.51 provisions for that operation, but absent a waiver addressing visibility/cloud clearance specifically, the standard minimums apply. Always check the exact terms of any waiver rather than assuming it covers weather minimums.

What if FEW or SCT clouds are directly overhead but no BKN/OVC layer exists?

Without a reported BKN, OVC, or VV layer, there is technically no ceiling, but the underlying cloud clearance distances (500 ft below, 2,000 ft horizontal) still apply to any cloud you're operating near, scattered or not.

How often should visibility and ceiling be reassessed during a flight?

Continuously. Both can change meaningfully within a single flight, especially near developing convective activity or fog — treat your pre-flight check as a starting point, not a one-time clearance for the whole mission.

Is a "special VFR" clearance relevant to Part 107 operations?

Special VFR is a manned-aircraft ATC clearance concept for operating in controlled airspace below normal VFR weather minimums; it isn't something a Part 107 remote pilot requests. The reason 107.51's cloud clearance distances exist is precisely to keep sUAS well clear of the altitudes where manned traffic, including special VFR traffic, might be operating.

Test Your Knowledge

Answer the questions below to check your understanding. Every answer can be found in the lesson above.

Loading questions...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.