The PAVE Checklist for Risk Assessment
Recognizing a hazard is the first and most important step in ADM — and the easiest step to skip when you're rushed. PAVE is a memory aid that forces a systematic scan across every category of risk before a flight, so nothing gets missed simply because it wasn't the category you happened to be thinking about that day. This lesson explains all four PAVE categories — Pilot, Aircraft, enVironment, and External pressures — and walks through how to actually run the checklist against a real mission.
P is for Pilot
The Pilot category asks the remote PIC to honestly assess their own fitness to fly — not the aircraft's condition, their own. This includes physical fatigue, illness, stress from something unrelated to the flight, recency of experience with this specific aircraft or this specific type of mission, and proficiency with any new equipment or software involved. A common self-check tool from manned aviation, IMSAFE (Illness, Medication, Stress, Alcohol, Fatigue, Eating/emotion), applies just as directly to a remote pilot as to a pilot in the cockpit — the human factors covered in Module 8 build directly on this category.
A is for Aircraft
The Aircraft category covers the airworthiness and readiness of the sUAS itself: whether the preflight inspection revealed any damage or anomaly, whether the battery is properly charged and healthy, whether firmware and any critical software updates are current, whether the payload is correctly mounted (see Module 6's weight and balance lesson), and whether the aircraft is appropriate for the mission at hand — a lightweight consumer quadcopter is not the right aircraft choice for a mission requiring sustained wind tolerance it isn't rated for, even if it's the only aircraft available that day.
V is for enVironment
The enVironment category covers everything about the physical and regulatory space the flight will happen in: current and forecast weather (Module 5), airspace classification and any required authorization (Module 3), terrain and obstacles, ground hazards near the launch and recovery point, and the presence of people, moving vehicles, or structures relevant to Part 107's operating rules. This category is deliberately broad because environmental hazards are the ones most likely to change between when a mission is scheduled and when it actually launches.
E is for External pressures
The External pressures category is the one most pilots underweight, because it isn't a physical hazard the way weather or a damaged propeller is — it's a psychological one. Client deadlines, the cost of a canceled trip to the job site, a schedule with no slack built in, or a desire to avoid disappointing someone are all external pressures capable of pushing a pilot toward launching despite a hazard identified in one of the other three categories. This category is explored in depth in this module's lesson on managing external pressures.
The four PAVE categories, each with representative hazards a remote pilot should scan for before launch.
View LargerPAVE and the regulatory preflight requirement
14 CFR 107.49 requires the remote PIC to complete a preflight familiarization, inspection, and briefing before every flight, covering local weather, airspace, notices to air missions, terrain and obstacles, and the condition of the aircraft and any control station or support equipment. PAVE is not itself a regulation, but it is a practical, memorable structure for actually satisfying what 107.49 requires — instead of trying to remember an unordered list, a pilot who has internalized PAVE has an automatic four-part scan to run through.
Worked scenario: running PAVE on a real mission
You're scheduled to fly a construction-progress mapping mission at 7 a.m. Pilot: you slept poorly and feel noticeably groggy — a flag, but not automatically a no-go by itself. Aircraft: preflight inspection is clean, battery is fully charged, firmware is current. enVironment: forecast shows gusts building to near the aircraft's rated limit by mid-morning, and the site is inside the lateral boundary of a Class D surface area requiring a LAANC authorization you haven't yet requested. External pressures: the general contractor has requested this exact time slot because concrete pour documentation needs to happen before 9 a.m. Running all four categories surfaces two real hazards (fatigue, missing authorization) and one time-sensitive risk (wind window closing) that a rushed pilot focused only on "is the drone charged" would have missed entirely.
PAVE is a scan, not a pass/fail test
A common misunderstanding is treating PAVE as a checklist where any flagged item automatically means "no-go." In practice, PAVE identifies hazards; it doesn't by itself tell you what to do about them. A hazard identified in one category (mild fatigue, a marginal wind forecast) might be acceptable with a mitigation (extra rest before launch, a firm decision to land before wind exceeds a set threshold) rather than an automatic cancellation. The risk assessment matrix lesson later in this module builds the next step: scoring an identified hazard's severity and likelihood to decide whether a mitigation is enough or the flight should be scrubbed.
PAVE for recurring, familiar missions
Experienced pilots flying a familiar route sometimes skip PAVE specifically because the mission feels routine — but routine missions are exactly where complacency creates risk. A site you've flown fifty times can still have new construction equipment, a newly erected tower crane, or today's specific weather that differs from every prior visit. Running PAVE, even briefly, on a familiar mission takes only a minute and catches exactly the kind of change a pilot on autopilot is most likely to miss.
| Category | What it covers | Example hazards | Related course module |
|---|---|---|---|
| Pilot | Remote PIC fitness to fly | Fatigue, illness, stress, unfamiliarity with the aircraft or mission type | Module 8: Physiological and Human Factors |
| Aircraft | Airworthiness and readiness of the sUAS | Damage found on preflight, weak battery, outdated firmware, wrong aircraft for the mission | Module 6: Loading and Performance / Module 10: Maintenance and Inspection |
| enVironment | Weather, airspace, terrain, obstacles, people and vehicles nearby | Wind approaching aircraft limits, missing airspace authorization, new obstacle near the site | Module 3: Airspace / Module 5: Weather |
| External pressures | Non-physical pressures pushing toward launch | Client deadline, cost of rescheduling, desire to avoid disappointing someone | This module's lesson on managing external pressures |
Running PAVE Before a Mission
Work through all four categories in order, every time, even on a familiar route.
Assess Pilot fitness first
Honestly evaluate fatigue, illness, stress, and recency of experience before considering anything about the aircraft or environment.
Complete the Aircraft preflight inspection
Check airframe condition, propellers, battery charge and health, firmware currency, and payload mounting against the manufacturer's checklist.
Scan the enVironment
Check current and forecast weather, confirm airspace classification and any required authorization, and identify terrain, obstacles, and people or vehicles near the operating area.
Identify External pressures honestly
Name any deadline, cost, or interpersonal pressure influencing the decision to fly, separately from the actual physical hazards identified above.
Decide with all four categories visible at once
Make the go/no-go call after weighing every category together, not by reacting to whichever hazard happened to be noticed first.
| Mistake | Why it happens | Correct understanding | Regulation / source |
|---|---|---|---|
| Only checking the Aircraft category and skipping the other three | Aircraft condition feels like the most concrete, checklist-friendly category | All four categories exist because hazards commonly come from the pilot, environment, or external pressures, not only the aircraft. | FAA Remote Pilot Study Guide, ACS Task V.D |
| Treating any flagged PAVE item as an automatic no-go | PAVE is mistaken for a strict pass/fail test | PAVE identifies hazards; deciding whether a mitigation is sufficient is a separate risk-assessment step. | FAA Remote Pilot Study Guide |
| Skipping PAVE on familiar, routine missions | A frequently flown site feels low-risk by default | Site conditions change; complacency on routine missions is a common source of missed hazards. | 14 CFR 107.49 |
| Treating External pressures as irrelevant to safety | Deadlines and client relationships don't feel like a "flight hazard" | External pressures are a recognized hazard category precisely because they push pilots to override hazards found elsewhere. | FAA Remote Pilot Study Guide, ACS Task V.D |
Is PAVE a required legal checklist under Part 107?
No specific regulation names "PAVE." It is a memory aid taught to satisfy the preflight familiarization requirement in 14 CFR 107.49, which does require covering weather, airspace, and aircraft condition among other items, but does not mandate any particular checklist format.
What order should I check the PAVE categories in?
The order P-A-V-E is the standard sequence, and checking Pilot first is intentional — a pilot who is unfit to fly should recognize that before investing time evaluating the aircraft or environment. In practice, many pilots run all four quickly and then revisit any flagged category in more depth.
Does PAVE replace the need for a written preflight inspection checklist?
No. PAVE is a broader risk-scan across four hazard categories; a written aircraft preflight inspection checklist (covered in Module 10) is a detailed, aircraft-specific procedure that sits inside the Aircraft category of PAVE.
How is PAVE different from the DECIDE model taught in the next lesson?
PAVE is for identifying hazards; DECIDE is the process for deciding what to do once a hazard has been identified. Think of PAVE as the "what to look for" step and DECIDE as the "what to do about it" step.
Test Your Knowledge
Answer the questions below to check your understanding. Every answer can be found in the lesson above.