Handbook

UA.V.D.K5

OperationsAeronautical Decision-MakingUA.V.D.K5
Exam Weight: 35-45%
Refs: AC 107-2; FAA-H-8083-2, FAA-H-8083-25; FAA-G-8082-22

UA.V.D.K5: Hazard identification and risk assessment.

ACS Area V — Operations Task D: Aeronautical Decision-Making References: AC 107-2; FAA-H-8083-2, FAA-H-8083-25; FAA-G-8082-22


Key Concepts

Build the Hazard Picture: "What If?" Analysis

Treat the small UA, crew, and environment as a system. Identify and control hazards by asking "what if?" and documenting significant foreseeable hazards before flight. Use a structured process to capture hazards related to the aircraft, crew, and operating area.[1]

Use examples to sharpen analysis. For instance, "loss of control link over people" could result from control-station power loss, out-of-range operation, or signal interference (Wi-Fi/Bluetooth), leading to ground impact, injury, and aircraft damage. This tabled analysis makes risks visible and actionable.[2]

Thoroughly describe the operational environment before assessing risks. Include current/forecast weather, equipment condition and limitations, crew fatigue/awareness, terrain/obstacles, hazards from flying over people, and "human factor" pressures like schedule or unfamiliar equipment. For night or mixed operations, consider night vision adaptation, unlit towers/buildings, and visibility of your anti-collision light for at least 3 statute miles.[3]

Assess Risk, Set Limits, and Plan Contingencies

For each identified hazard, list causes and effects, then estimate likelihood and severity to define risk. Record mitigations that reduce likelihood and/or severity. Always add an emergency/contingency plan for when the event occurs (e.g., controlled landing area, lost-link procedure, crew callouts).[3]

Set explicit operational limits (minimum weather, altitude bands, speed ranges, etc.), define and brief discontinue ("knock-it-off") criteria and who executes the decision, and review Weight and Balance. These controls reduce ambiguity and help break error chains early.[4]

Use root cause analysis to justify your selected likelihood/severity levels, then develop targeted controls. A focused crew brainstorm can expose simple, high-value mitigations. Prioritize the few hazards that drive the greatest risk and document successful practices for future missions.[4]

Embed ADM in Required Preflight Actions

§ 107.49 requires preflight familiarization, inspection, and actions. Your assessment must address local weather, airspace and flight restrictions, location of persons and moving vehicles not directly participating, surface property, eligibility of the aircraft for operations over people/moving vehicles, and whether the operation is over an open-air assembly. Consider the chance that nonparticipants enter the area during the operation and any other ground hazards. Use current aeronautical charts or tools like B4UFLY to understand the type of airspace.[5]

These items map directly to hazard ID and risk control: they reveal where bystanders and vehicles could be exposed, when airspace or TFRs constrain your options, and whether your aircraft’s limitations make a plan unacceptable.

Remote ID as a Risk Control

After September 16, 2023, most registered or required-to-be-registered small UAs must comply with Remote ID. The serial number of either the Standard Remote ID UA or the broadcast module must be on the Certificate of Aircraft Registration. If you move a module between aircraft, update the serial number on the registration before flight. Even aircraft 0.55 pounds or less must comply when operated under any part that requires registration. Remote ID enhances airspace awareness for the FAA and law enforcement, helping distinguish compliant users from potential risks.[6]

A broadcast module must transmit key message elements (identity via module serial number; UA latitude/longitude; geometric altitude; UA velocity; take-off latitude/longitude; take-off geometric altitude; UTC time mark) and meet performance requirements, including a synchronized time mark, an automatic pre-takeoff self-test with notification of results, and continuous monitoring with malfunction notification from takeoff to shutdown. Treat these as both compliance checks and preflight risk controls.[7]

If operating in an FAA-Recognized Identification Area (FRIA), manage compliance risk by tracking its status. Changes to application information must be submitted within 10 calendar days; FRIAs are effective for 48 calendar months unless renewed, and renewal requests should be submitted at least 120 days prior to expiration. FRIAs are subject to ongoing FAA review and may be modified or terminated—verify boundaries and validity during preflight ADM.[8]

Test Yourself

UA.V.D.K5

No practice questions are currently available for this specific knowledge element.