Part 107 Weather: METARs, TAFs, and Safe Flight Decisions (2026)

Last Updated: October 6, 2026

Part 107 weather knowledge comes down to three jobs: understand what the weather is doing now, recognize what might change, and decide whether your drone can handle the conditions. A METAR reports observed airport weather. A TAF forecasts weather around an airport. Neither replaces checking conditions where you’ll actually fly.

Drone Launch Academy founder David Young is an FAA-certified Advanced Ground Instructor. This guide uses official weather references and practical examples to explain report codes, their limitations, and how they inform flight decisions.

TL;DR: Read the latest observation, check the forecast for your flight window, then verify conditions locally. Compare the result with Part 107 requirements and your aircraft’s limitations. If the information doesn’t support a confident decision, delay or cancel.

What weather knowledge do you need for Part 107?

You need to interpret aviation weather information, recognize hazardous conditions, and understand how weather affects a small unmanned aircraft. For exam preparation, focus on METARs, TAFs, clouds, visibility, wind, atmospheric stability, and density altitude. For actual flights, connect those concepts to the mission instead of stopping at code translation.

The FAA Remote Pilot Study Guide explains the underlying concepts. It’s an older instructional document, so use current regulations for operating requirements.

A sensible study order is:

1. Identify the report’s location and time.
2. Read wind, visibility, and clouds.
3. Recognize weather hazards and performance effects.
4. Follow forecast changes through your planned flight window.
5. Explain what the information means for a flight.

That last step matters. “G20” means gusts to 20 knots. The useful follow-up is whether your aircraft and mission can tolerate them. For the rest of your preparation, use our Part 107 study guide.

What are the Part 107 weather minimums?

Under the standard, unwaived Part 107 operating rules, flight visibility must be at least three statute miles from the control station. Your aircraft must remain at least 500 feet below clouds and 2,000 feet horizontally from clouds. Those requirements apply together; meeting one doesn’t excuse failing another.

14 CFR 107.51 sets these operating limitations. The distinction between reported visibility and flight visibility at your control station is important: an airport reporting 10 miles doesn’t establish visibility at your foggy launch site.

Three miles of visibility also doesn’t authorize a three-mile flight. Visual-line-of-sight and other operating requirements remain separate.

Part 107 doesn’t set one universal wind-speed limit for every drone. Follow the aircraft manual, applicable approvals, and a conservative mission assessment. Before flight, 14 CFR 107.49 requires the remote pilot to assess the operating environment, including local weather. A technically compliant flight can still be a poor decision.

What’s the difference between a METAR, a TAF, and a SPECI?

A METAR describes observed surface weather at a reporting station. A TAF forecasts conditions around an airport over a stated period. A SPECI is a special observation issued when significant changes warrant an update between routine reports. Together, they help you separate what’s been observed from what’s expected next.

The FAA study guide describes a TAF’s coverage as the area within five statute miles of the airport. Don’t stretch that into a promise about a hillside or shoreline farther away.

For current data, start with the National Weather Service Aviation Weather Center. Its raw and decoded views make a useful learning pair.

How do you read a METAR from left to right?

Read a METAR in a consistent sequence: report type, station, observation time, wind, visibility, weather, clouds, temperature and dew point, altimeter setting, then remarks. Keep the units straight: wind uses knots, U.S. visibility uses statute miles, temperatures use Celsius, and cloud heights are expressed in hundreds of feet.

Fictional practice example—not current flight weather:

METAR KJFK 061551Z 24012G20KT 10SM FEW020 BKN040 22/16 A2998 RMK AO2

The official NWS METAR/TAF key is a good decoding reference. A few additional patterns help:

• VRB means variable wind direction; 00000KT means calm.
• -RA means light rain; TSRA means thunderstorm with rain.
• BR means mist; FG means fog. BR does not mean drizzle.
• M05 means minus five degrees Celsius.
• AUTO identifies an automated observation; COR identifies a correction.

Don’t automatically ignore remarks. They can provide relevant context about conditions or changes. And don’t judge the sample by its generous visibility alone: gusts, local turbulence, equipment limitations, and conditions at the flight site still need checking.

Which cloud layers count as a ceiling?

A ceiling is the lowest broken or overcast cloud layer, or reported vertical visibility into an obscured sky. Few and scattered layers aren’t ceilings. However, cloud-clearance requirements still apply to individual clouds, including those below the ceiling. “No ceiling” therefore doesn’t mean “no clouds to consider.”

In the practice METAR, BKN040 establishes a 4,000-foot ceiling above the reporting station. That is not 4,000 feet MSL, and it doesn’t automatically establish the height above another site with different terrain.

For a simplified local example, assume a uniform cloud base at 800 feet above your operating site. Remaining 500 feet below it leaves a maximum altitude of 300 feet beneath that cloud. Horizontal clearance and all other requirements still apply. The usual 400-foot altitude limit doesn’t override cloud clearance.

How do you read a TAF for your planned flight time?

Start with the TAF’s issue time and validity period, then find the forecast segment covering your planned flight. An FM group starts new prevailing conditions; an overlapping TEMPO group identifies temporary variations you must consider. Read the entire relevant window, including possible deterioration before you’ve finished and landed.

Fictional practice example—not a current forecast:

TAF KJFK 061130Z 0612/0712 24008KT P6SM SCT030
FM061800 26014G22KT P6SM BKN025
TEMPO 0618/0621 2SM TSRA BKN008CB
FM062200 29008KT P6SM SCT035

Here’s the timeline:

• 061130Z: Issued on the sixth at 11:30 UTC.
• 0612/0712: Valid from 12:00 UTC on the sixth until 12:00 UTC on the seventh.
• Initial conditions: Wind from 240 degrees at eight knots, visibility greater than six statute miles, scattered clouds at 3,000 feet.
• FM061800: From 18:00 UTC on the sixth, wind from 260 degrees at 14 knots, gusting to 22; broken clouds at 2,500 feet.
• TEMPO 0618/0621: Between 18:00 and 21:00 UTC, temporary conditions include two-mile visibility, thunderstorms with rain, and broken cumulonimbus clouds at 800 feet.
• FM062200: From 22:00 UTC, the example forecasts lighter winds and scattered clouds.

A proposed 19:00 UTC mission falls within the temporary thunderstorm window. Don’t select the more comfortable prevailing line and discard the TEMPO warning. Postponing is the sensible planning response to this example; a later flight still requires fresh observations and a local assessment.

PROB30, when present, indicates a 30-percent probability of the listed conditions during its specified period. It isn’t permission to ignore them. Likewise, forecast improvement doesn’t mean conditions have already improved. All these times are UTC, not your local clock time; the date can change too.

Can you trust the nearest airport’s weather at your launch site?

Use the nearest relevant airport report as a starting point, not a site-specific guarantee. Distance, elevation, terrain, water, buildings, and changing weather can make conditions different where your drone operates. Check whether the station represents your location, compare other available information, and confirm what you can observe locally.

Imagine an airport reporting good visibility while your job site sits in a fog-filled valley. The airport report hasn’t become “wrong”; it’s describing another place.

The same problem applies to wind. A sheltered surface measurement may not reveal stronger wind above a tree line. Buildings and ridges can create turbulence that a regional forecast doesn’t resolve.

There’s no universal station-distance cutoff that makes a report suitable. Ask whether it captures the same weather pattern and terrain exposure. If nearby stations disagree, investigate rather than choosing the report you prefer.

Check timestamps, weather hazards, and local conditions. A handheld wind measurement helps, but it doesn’t describe your entire operating airspace.

Which weather hazards can make a legal flight unsafe?

Strong gusts, thunderstorms, fog, precipitation, icing, and reduced aircraft performance can make a flight unsafe even when standard visibility and cloud-clearance requirements are satisfied. Judge these hazards against your drone’s limitations and the actual mission. A forecast or app that labels conditions “good” can’t make that judgment for you.

Wind and turbulence: Compare gusts as well as sustained wind with the aircraft manual. A return leg into stronger wind can erode battery margin. Turbulence near obstacles and sudden wind shear add risks a simple wind-speed number misses.

Thunderstorms: Cumulonimbus clouds, building convection, lightning, hail, and outflow winds are warning signs. You don’t need to fly beneath the darkest cloud to encounter hazardous gusts or downdrafts.

Fog and low visibility: A narrowing temperature–dew-point spread can signal increasing saturation risk, but it isn’t a precise fog countdown. Radiation fog can develop after overnight cooling; advection fog forms when moist air moves over a colder surface.

Stable versus unstable air: Stable air commonly favors smoother conditions and layered clouds, sometimes with restricted visibility. Unstable air supports vertical development and turbulence. Neither label alone establishes safe drone weather.

Rain, cold, and icing: Check the aircraft’s environmental limitations. Clear visibility doesn’t make an unprotected drone rain-safe. Frost or ice can interfere with flight; see our cold-weather drone tips.

Density altitude: Higher elevation, heat, humidity, and lower pressure can reduce air density and aircraft performance. Don’t assume familiar flight time, payload capability, or climb performance carries over unchanged to a hot, high-elevation job.

How should you make a weather go/no-go decision?

Combine current observations, the forecast for your entire flight window, local conditions, Part 107 requirements, aircraft limitations, and contingency margin. Make the decision before launch, then keep reassessing. If weather deteriorates or the information is too uncertain, shorten, delay, or cancel the operation rather than forcing the original plan.

Use this repeatable checklist:

1. Define the mission. Note location, altitude, duration, return route, and landing options.
2. Retrieve relevant weather. In the Aviation Weather Center tool, select suitable stations and compare raw with decoded reports.
3. Check time and changes. Read the latest METAR or SPECI and the TAF segments overlapping the mission.
4. Assess visibility and clouds locally. Verify the standard weather requirements at the operating site.
5. Check aircraft limits and hazards. Include gusts, precipitation, temperature, terrain turbulence, and performance margin.
6. Plan a response. Decide what conditions would trigger an earlier landing and ensure sufficient power and workable landing options.
7. Recheck before launch and monitor during flight. Don’t let a favorable earlier forecast outweigh worsening conditions in front of you.

You can keep weather notes as part of your own operating process; this checklist doesn’t create a universal recordkeeping requirement.

Weather is one part of preflight. Airspace authorization, restrictions, people, and other obligations still need their own checks. Our Part 107 sectional-chart guide explains that separate airspace picture.

How can you practice Part 107 weather questions?

Practice by translating a report into plain English, then explaining its flight implications. Prioritize timestamps, wind and gusts, visibility, ceiling identification, and TAF change windows. Work through unfamiliar examples until you can explain your reasoning. These skills are more useful than memorizing one report or guessing how many weather questions you’ll receive.

Try these original practice questions—not actual FAA exam questions:

• What does 18010G18KT mean? Wind from 180 degrees true at 10 knots, gusting to 18. Evaluate the gusts, not just the steady wind.
• Which is the ceiling in SCT015 BKN030? The broken layer at 3,000 feet above the station. Scattered clouds at 1,500 feet still matter for separation.
• Which forecast matters at 19:00 UTC in the sample TAF? The 18:00 FM segment and the overlapping 18:00–21:00 TEMPO group—not the later 22:00 improvement.

Drone Launch Academy’s published instructor biographies include weather instructors Col. Don Berchoff and Maj. Nathan Green, both with aviation-meteorology backgrounds. The Part 107 prep course includes Weather and Flight Performance, alongside broader exam preparation.

What are the most common Part 107 weather questions?

Common weather questions focus on report codes, time, cloud-height references, visibility, and the gap between an airport summary and conditions at the launch site. Use the answers below as quick refreshers, then return to the worked examples and official references when you need to check the underlying reasoning.

Do I need to memorize every METAR and TAF abbreviation?

Build a working vocabulary and learn the report sequence rather than trying to memorize every uncommon code. Prioritize UTC time, wind and gusts, visibility, clouds, common weather, and forecast changes. Practice with current official study materials; don’t assume every examination question will reproduce an example you’ve already seen.

Is METAR wind direction true or magnetic?

METAR and TAF wind directions are reported relative to true north. For example, 27012KT means wind from 270 degrees true at 12 knots. That’s the direction the wind comes from, not where it’s going. Don’t confuse this reporting convention with magnetic directions used in other aviation contexts.

Are METAR cloud heights AGL or MSL?

METAR cloud-base heights are reported in hundreds of feet above the reporting station’s ground level, not mean sea level. BKN020 means a broken layer 2,000 feet above that station. Different terrain elevations and local conditions mean you shouldn’t automatically treat it as 2,000 feet above your launch site.

Does an MVFR label automatically prohibit a Part 107 flight?

No. MVFR is an aviation flight-category summary, not a complete Part 107 decision. Check actual flight visibility at the control station, separation from clouds, aircraft limitations, hazards, and every other applicable operating requirement. A color label also doesn’t establish conditions at your site or guarantee the operation is safe.

How often should I check the weather before flying?

Check while planning, again close to launch, and as conditions change during the operation. There’s no single report-age rule that makes every mission safe. Consider how quickly conditions are evolving, watch for special observations, and refresh the information when forecasts, reports, and local observations no longer tell a consistent story.

Can I fly a drone in rain if visibility meets Part 107 minimums?

Adequate visibility alone isn’t enough. You must also satisfy cloud clearance and other applicable requirements, follow your aircraft’s environmental limitations, and assess the operation’s risks. Rain can reduce visibility and damage equipment. If the aircraft isn’t suitable for the conditions, meeting a visibility minimum doesn’t make the flight appropriate.