FAA Part 107 Regulations

Lesson 1 — The 400-Foot Altitude Limit

Under 14 CFR 107.51, drone operations are limited to 400 feet above ground level (AGL). This is the standard altitude limit that keeps drones well below manned aircraft operating at minimum altitudes (typically 500 feet AGL in uncongested areas, 1,000 feet in congested areas). The 400-foot limit applies above the ground directly below the drone, not above the takeoff point — if you take off from a 300-foot hill and fly 400 feet up, you are 700 feet above the surrounding valley.

There is an important exception: when flying within 400 feet of a structure, you may fly up to 400 feet above the structure itself. If you're inspecting a 500-foot radio tower, you can legally fly up to 900 feet MSL to inspect the top. However, this exception requires you to stay within 400 feet of the structure horizontally — you can't use a tall building to justify high altitude operations a mile away. The structure exception is specifically designed for inspection and maintenance work on tall structures.

Altitude is measured AGL (above ground level), not MSL (mean sea level). This distinction matters in terrain with elevation changes. Your drone's barometric altimeter reads relative to the takeoff point — if you take off in a valley and the surrounding terrain is higher, your drone's displayed altitude may not reflect true AGL over that terrain. Use your judgment and knowledge of the terrain to stay within limits.

Lesson 2 — Visual Line of Sight (VLOS)

Under 14 CFR 107.31, the remote pilot in command (RPIC) must maintain visual line of sight with the drone throughout the flight — without the aid of any device other than corrective lenses. "Visual line of sight" means you must be able to see the drone with your unaided eyes (glasses and contacts are permitted) at all times to determine its position, altitude, attitude, and direction of travel.

FPV (first-person view) flying — using goggles to see through the drone's camera — does not satisfy the VLOS requirement by itself. If you fly FPV, a visual observer (VO) who can see the drone with unaided eyes must be present and in communication with you. The visual observer must also comply with VLOS requirements and is part of the operating crew.

There is no specific distance limit defined for VLOS — it depends on the drone's size, lighting, visibility conditions, and the pilot's eyesight. In practice, most drone pilots can maintain meaningful VLOS with common consumer drones to about 1,500 feet (roughly 400-500 meters). Beyond that, determining orientation and detecting other aircraft becomes difficult. You must be able to see the drone well enough to avoid collisions — if you can't determine which way it's pointed or whether it's climbing or descending, you've exceeded practical VLOS.

Practical VLOS Limits

While there is no legally defined distance limit for VLOS, practical experience and FAA guidance suggest that maintaining meaningful visual contact with most commercial drones — where you can determine orientation and detect conflicts — is typically possible to about 1,500-2,000 feet (roughly 400-600 meters) under good visibility conditions. Beyond this range, the drone appears as a small dot, and orientation is very difficult to determine without specific markings or lighting.

Factors that reduce practical VLOS distance: hazy or high-humidity air, sun angle (drone silhouetted against the sun, or sun in your eyes), small drone size, drone color that blends with sky or background, and pilot visual acuity limitations. Factors that extend VLOS: large drone size, high-contrast colors (orange drones against blue sky), clear dry air, overcast sky that provides neutral background, and pilot familiarity with the specific aircraft's visual signature.

Visual Observer Requirements

A visual observer (VO) is a person who assists the RPIC by maintaining visual contact with the drone. The RPIC and VO must be able to communicate at all times — typically face-to-face or via radio if separated. The VO cannot use aids other than corrective lenses to maintain VLOS. Multiple VOs can be used to extend the effective monitoring area, but each must maintain continuous visual contact with the drone throughout their monitoring responsibility.

Important limitation: a VO cannot be positioned ahead of the drone to effectively extend VLOS range. The VLOS requirement applies to the RPIC (or a VO working with the RPIC) maintaining visual contact from a fixed ground position — not a chain of observers each watching the drone as it passes through their visual range. True BVLOS operations always require a waiver, regardless of VO configuration.

Lesson 3 — Daylight and Civil Twilight Operations

Under 14 CFR 107.29, drone operations are limited to daylight and civil twilight — the 30-minute period before official sunrise and the 30-minute period after official sunset. Operations during civil twilight require the drone to be equipped with anti-collision lighting visible from at least 3 statute miles. The lighting must be active throughout civil twilight operations.

Night operations beyond civil twilight require a waiver (107.29 waiver). As of 2021, night operations are more broadly permitted under an updated rule — drone pilots may fly at night without a waiver, provided the drone has anti-collision lighting visible from 3 statute miles. However, some nuances remain — check the current 14 CFR 107.29 for the most up-to-date requirements, as night rules have evolved since Part 107 was first published.

Official sunrise and sunset times vary by location and date. Use the FAA's published sunrise/sunset tables, a reliable weather service, or an app that provides site-specific times. Civil twilight provides enough ambient light for reasonable visibility — after astronomical twilight (when the sun is more than 18 degrees below the horizon), visibility drops significantly and the risk of mid-air collision increases substantially.

Sunrise and Sunset Timing

Official sunrise and sunset times are published for specific locations and dates by the Naval Observatory at aa.usno.navy.mil and by many weather services. Civil twilight times — 30 minutes before official sunrise and 30 minutes after official sunset — are also published. The times vary with latitude, longitude, and date. At high latitudes (near the poles), civil twilight can extend for much longer than 30 minutes and "midnight sun" conditions create operational complexity.

The FAA's definition of sunrise and sunset for aviation purposes is the published standard sunrise/sunset times, not the first/last visible light. On overcast days, the sky may be dark before official sunset — this doesn't change when anti-collision lighting is required. Conversely, in clear high-altitude locations, usable light may extend well beyond official sunset — still doesn't change the legal timing. Use official published times, not judgment about visible light levels.

Anti-Collision Lighting Specifications

The Part 107 requirement for anti-collision lighting visible from 3 statute miles sounds straightforward but raises practical questions: how do you verify 3-mile visibility? The FAA hasn't published a specific test method, but aftermarket strobe lights marketed for drone use typically specify their visibility range in their product documentation. Choose lights with stated visibility of at least 3 statute miles and preferably more, from reputable manufacturers who have tested their products.

Built-in drone lights may or may not meet the 3-mile standard. DJI and other manufacturers have not universally certified their built-in lighting systems against the 3-mile standard. For commercial night operations, adding a dedicated aftermarket strobe — such as those from Lume Cube or similar aviation-grade manufacturers — is the safest compliance approach. The light should be oriented to be visible from all angles (360° horizontal coverage) and should have a flash rate that clearly indicates the aircraft is in motion, not stationary on the ground.

Lesson 4 — Speed, Visibility, and Cloud Clearance

Maximum groundspeed: 100 mph (87 knots) under 14 CFR 107.51. In practice, few drone operators approach this limit, but it matters for certain applications like FPV racing or high-speed survey work.

Minimum flight visibility: 3 statute miles from the control station under 14 CFR 107.51. Flight visibility is the visibility observed from the ground station position, not from the drone's perspective. If visibility drops below 3 SM due to fog, haze, smoke, or precipitation, Part 107 prohibits flight.

Cloud clearance requirements: Drones must maintain at least 500 feet below clouds and at least 2,000 feet horizontally from clouds. These requirements mirror the VFR cloud clearance requirements for Class G and Class E airspace. The reason: manned aircraft descending through clouds may emerge with limited time to spot and avoid traffic. Maintaining cloud clearance gives both you and manned aircraft time to see and avoid each other.

Groundspeed vs Airspeed

The 100 mph (87 knot) maximum in Part 107 specifies groundspeed — the actual speed of the drone over the ground, as opposed to airspeed (speed through the air). In a 20-knot headwind, a drone traveling at 87 knots groundspeed is actually moving through the air at 107 knots airspeed — but the legal limit applies to groundspeed. Conversely, a drone traveling at 87 knots groundspeed with a 20-knot tailwind is only moving through the air at 67 knots airspeed.

For most drone operations well below the 87-knot limit, this distinction is academic. It becomes relevant for high-speed racing drones or for drones flying in strong tailwinds. GPS-based airspeed displayed in drone apps represents groundspeed — the speed of the drone relative to the ground as calculated from GPS position changes. This is the correct measurement for Part 107 speed compliance.

Inflight Visibility Assessment

The Part 107 3-mile visibility requirement is assessed from the pilot's position on the ground — the pilot must have 3 miles of visibility from their control station. This is evaluated using the same criteria as surface aviation visibility: how far can you see objects clearly? On days with haze or smoke, visibility can degrade significantly from forecast values. If you can see mountains or identifiable landmarks at known distances, use those as reference points for visibility assessment.

During smoke events from wildfires — increasingly common in western US states — visibility can drop below 3 miles with little warning as smoke density changes with wind. Smoke also creates high-contrast lighting situations that make drones extremely difficult to see against the smoke-diffused sky. During smoke events, more conservative VLOS limits are prudent even if official visibility is technically above 3 miles.

Lesson 5 — Right-of-Way Rules

Under 14 CFR 107.37, drones must yield the right of way to ALL other aircraft — always. This is not a situational rule: a drone never has right of way over a manned aircraft, a glider, a hot air balloon, a parachutist, or any other airspace user. The drone must give way, full stop.

This rule is both a legal requirement and a practical necessity. Manned aircraft are significantly less maneuverable than most drones in the immediate term, and the consequences of a collision are catastrophic for the manned aircraft occupants. Drone pilots must continuously scan for air traffic and maneuver as necessary to avoid any aircraft — even if that aircraft appears to be on an unusual path, flying very low, or behaving unexpectedly.

Additionally, under 107.37, no person may operate a drone in a manner that creates a hazard to other aircraft, people on the ground, or property. This is the operational safety standard — not just yielding when in conflict, but actively operating in a way that doesn't create hazards in the first place. Pre-flight planning, continuous situational awareness, and conservative decision-making are all part of this obligation.

Practical Right-of-Way Implementation

In practice, implementing the right-of-way rule means constant vigilance for other aircraft in your operating area. Before flight, assess traffic patterns in your area: are you near a common flight path for helicopters (aerial tours, news, EMS)? Are you near a glider port or parachute drop zone? Are agricultural aircraft active in the area during your operation window? Cropdusters and agricultural helicopters fly at very low altitudes and may appear with little warning.

When manned aircraft are observed in your area, the most conservative action is to descend and land if the aircraft appears to be operating at or near your altitude, or to move laterally away from the aircraft's trajectory and reduce altitude. Communication with the pilot is generally not possible for drone operators without radio equipment, but large, slow maneuvers that take the drone away from the aircraft's path make your avoidance action visible to the pilot.

Emergency Aircraft Right-of-Way

Emergency aircraft — aircraft engaged in search and rescue, medical evacuation, firefighting, or other emergency operations — have absolute priority in the airspace. If you hear or see emergency aircraft, land immediately. Wildfire air tankers and helicopters operate in tactical patterns at very low altitudes, often with limited visibility due to smoke. News helicopters covering breaking events may arrive with minimal notice. EMS helicopters fly direct routes to hospitals at low altitudes. In any situation where emergency aircraft are operating, do not fly your drone regardless of current airspace authorization.

Lesson 6 — Careless and Reckless Operation

14 CFR 107.23 prohibits careless or reckless operation — flying in a manner that endangers the life or property of another. This is the FAA's catch-all rule that applies when no more specific regulation covers a dangerous situation. It mirrors the careless and reckless prohibition in 14 CFR 91.13 for manned aircraft.

Careless operation doesn't require intent — flying near a crowd without adequate margin, flying in deteriorating weather without adjusting plans, or ignoring equipment anomalies and continuing the flight can all constitute carelessness. Reckless operation involves a conscious disregard for the risk — flying directly over a crowded event after being told not to, continuing flight in zero-visibility conditions, or deliberately flying near manned aircraft approaches.

The careless/reckless rule is important because technology is always ahead of regulation. New drone capabilities, new operating environments, and new use cases appear faster than the FAA can write specific rules. If your operation would strike a reasonable person as dangerous even if no specific rule explicitly prohibits it, you are likely in careless/reckless territory. When in doubt, don't.

Case Studies in Careless Operation

The FAA has published several enforcement cases that illustrate what constitutes careless or reckless operation. A pilot who flew a drone over a crowded beach and lost control, striking a bystander, was found to have operated carelessly by not maintaining adequate distance from people. A pilot who continued flying after receiving multiple low battery warnings and then had a flyaway when the battery died was found to have operated recklessly by ignoring safety indicators. A pilot who flew over a moving highway with heavy traffic was found to have created an unacceptable hazard even though no accident occurred.

The common thread in careless/reckless findings: the pilot had information suggesting risk (people nearby, low battery, traffic below) and chose to continue the risky behavior rather than modify the operation. The careless/reckless standard is evaluated by what a reasonable, prudent pilot would have done under the same circumstances — not by whether an accident actually occurred. You can be cited for careless/reckless operation even if nothing bad happens.

The "Reasonable Pilot" Standard

FAA enforcement uses a "reasonable pilot" standard similar to the "reasonable person" standard in civil law. Would a reasonable, trained Part 107 pilot with equivalent knowledge and experience have made the same decision? This standard means that what other pilots do is relevant — if most Part 107 pilots would not fly in the conditions you chose to fly in, your decision may not meet the reasonable pilot standard. Consulting with experienced colleagues, reviewing incident reports, and developing judgment through training and experience all contribute to consistently meeting this standard.

Lesson 7 — Waivers: Flying Outside Standard Rules

Part 107 allows the FAA to waive specific operating rules for operators who can demonstrate they will maintain an equivalent level of safety. Waivable rules include: daylight operations (now largely moot for night), visual line of sight, operations over people, operations from moving vehicles, and others. You cannot waive the careless/reckless rule, the right-of-way rule, or the requirement to have a Remote Pilot Certificate.

Waiver applications are submitted through the FAA DroneZone at faadronezone.faa.gov. The application must include a detailed safety case: what operation you're conducting, what risks exist, and what specific mitigations you're implementing to address each risk. The FAA evaluates whether your risk mitigations are adequate to maintain safety equivalent to the standard rule.

Waiver processing times vary from days to months depending on complexity. Simple waivers with clear safety cases are approved more quickly. Operations involving novel risks (very large swarms, long-range BVLOS flights over populated areas) may require extensive documentation and take much longer. Start the waiver process well in advance of your intended operation date.

Building a Strong Waiver Safety Case

The FAA's waiver review process looks for three things in a safety case: hazard identification (what risks does this operation create?), risk analysis (how likely and severe are those risks?), and risk mitigation (what specific measures reduce those risks to an acceptable level?). Generic statements like "I will maintain situational awareness" are insufficient. Specific, measurable mitigations work: "A ground spotter will be positioned 100 feet north of the operating area to monitor for approaching aircraft and will use a dedicated radio channel to alert the RPIC immediately upon observing any manned aircraft within 1 mile."

Supporting documentation strengthens waiver applications: manufacturer performance data, test flight records, crew training certifications, standard operating procedures (SOPs), and emergency response plans. Operators who have previously received waivers and can demonstrate clean compliance history are more likely to receive approval on new applications. Build your waiver track record starting with simpler waiver types before attempting complex BVLOS or operations over people applications.

Waiver Conditions and Compliance

Approved waivers come with specific conditions — time of day limits, weather minimums, altitude restrictions, required equipment, crew training requirements, and often mandatory reporting of incidents or anomalies. Violating any waiver condition instantly voids the waiver, meaning you're operating without authorization. Waiver conditions are not suggestions — they are the specific terms under which the FAA determined your operation is safe. Compliance must be meticulous.

Keep waiver documentation accessible during operations. If an FAA inspector approaches during an authorized waiver operation, you need to present the waiver documentation and demonstrate compliance with each condition. Some waivers require you to carry printed copies; others allow digital presentation. Know your waiver's documentation requirements before every operation.

Lesson 8 — Accident Reporting

Under 14 CFR 107.9, the RPIC must report any drone accident to the FAA within 10 days if the accident results in: serious injury to any person, or loss of consciousness, or property damage (other than to the drone itself) in excess of $500. This is a mandatory reporting requirement — failure to report is itself a violation.

Reports are filed through the FAA DroneZone. The report should include the date, location, description of the incident, aircraft information, and the nature of the injury or damage. Accident reports may trigger an investigation, but the reporting requirement exists regardless of fault — it's about safety data collection, not automatic enforcement.

Best practice is to maintain detailed flight records for every operation. If an accident occurs, preserve all data: flight logs, video footage, maintenance records, and your preflight risk assessment. This documentation is invaluable for both insurance claims and any FAA investigation. Operators with thorough records and demonstrated safety practices consistently fare better in enforcement proceedings than those who cannot document their procedures.

What Constitutes a Reportable Accident

The $500 property damage threshold (excluding the drone itself) applies to damage caused by the drone to third-party property. Damage to your own drone doesn't trigger the reporting requirement. Damage to property you own (your car, your client's property) is subject to some interpretation — consult with an aviation attorney if the situation is ambiguous. The FAA's focus is on damage to third-party property and injury to people.

"Serious injury" in the Part 107 context follows the NTSB definition: any injury requiring hospitalization for more than 48 hours, resulting in a bone fracture, causing severe hemorrhage, nerve/muscle/tendon damage, internal organ damage, involving burns to more than 5% of body surface area, or resulting in loss of consciousness. Minor injuries — a scratch from a propeller, brief dizziness from a prop wash — do not trigger the reporting requirement, though documenting and reporting them voluntarily demonstrates good safety culture.

Voluntary Reporting Systems

Beyond mandatory accident reporting, the FAA encourages voluntary reporting of safety incidents through the Aviation Safety Hotline (1-800-255-1111) and the NASA Aviation Safety Reporting System (ASRS). The ASRS in particular provides a degree of confidentiality protection — reports submitted to ASRS in good faith are de-identified before analysis and submission is considered evidence of good-faith safety behavior in FAA enforcement proceedings.

Professional drone operators who experience near-misses, equipment anomalies that could have led to accidents, or operational situations where they discovered hazards should consider filing ASRS reports. These reports contribute to the FAA's understanding of drone operational risks and ultimately to better regulations. The aviation safety system depends on voluntary reporting to identify systemic issues before they cause serious accidents.