A few years ago, flying a drone over a jobsite was something the survey crew did on a Friday afternoon with nobody's signature on anything. That era is over on federal work. The 2024 edition of EM 385-1-1 brought unmanned aircraft systems into the manual as a named activity, which means a UAS flight on a Corps site is a work activity like any other — and those require an accepted activity hazard analysis before they begin. Add FAA Part 107 and installation airspace rules, and the casual flight is now a documented operation. Activity hazard analysis software is how flight crews keep that documentation from becoming the reason nobody flies.
Why UAS AHAs are now mandatory on Corps sites
Two things changed. Drones stopped being a novelty and became production tools — progress photography, volumetric survey, bridge and dam inspection, levee reconnaissance after high water, penstock interior inspection, post-storm damage assessment. And the incident record caught up: flyaways into active airspace, aircraft striking crane booms and transmission lines, lithium-polymer battery fires, and prop injuries during hand launches.
The 2024 edition now treats UAS operations as an activity requiring hazard analysis, qualified personnel, and defined controls, and district safety offices increasingly reject a flight request that arrives without one. A generic photography JHA does not satisfy that. A credible OSHA 1926 activity hazard analysis covers both the aviation risk and the ground-level construction risk the crew is standing in — the visual observer walking backward while watching the aircraft is exposed to every hazard on that site.
Define the flight crew roles in the AHA
The single most useful thing a UAS AHA does is name people to roles:
- Remote Pilot in Command (RPIC): holds the Part 107 certificate and final authority over the flight, performs the preflight and airworthiness determination, makes the weather and airspace go/no-go call, and can terminate unilaterally.
- Visual Observer (VO): maintains visual line of sight and scans for intruding manned aircraft, other UAS, and ground personnel entering the area. The VO looks up and out — which means somebody else watches where the VO's feet are going.
- Ground crew: controls the launch and recovery zone, keeps non-participants clear, manages batteries and equipment, handles barricading.
- Site interface: the superintendent or SSHO contact who knows what else is happening during the flight window — the crane pick, the pour, the blast.
Record certificate numbers and currency, the aircraft registration, required waivers, and the RPIC-to-VO communication method. When two people cover a 40-acre site, write down what happens if they lose sight of each other.
Airspace coordination on military installations
Airspace is where federal UAS work differs most from commercial work. Beyond the Part 107 baseline — Class G by default, LAANC or a waiver for controlled airspace, altitude limits, anti-collision lighting, no operations over non-participants without a waiver — a military installation adds its own layer. Base operations, the airfield manager, range control, and installation security may all have standing rules, and some require prior approval or escort regardless of FAA authorization. Counter-UAS systems exist on some sites, and an unannounced flight can be treated as a security event rather than a paperwork oversight.
Good hazard analysis templates capture this as a coordination checklist inside the AHA: approval reference and date, point of contact, approved flight window, altitude ceiling, lateral boundaries, notifications before launch and after landing, and the abort instruction if an aircraft enters the area. Near a dam, lock, levee, or airfield, add the operational contact; near a range, the firing schedule. Most UAS near-misses trace back to a coordination step nobody owned.
Lost link, flyaway, and contingencies
Every UAS AHA should assume the link will fail, because eventually it does. Document the configured lost-link behavior — return to home, hover and land, or continue mission — and confirm the RPIC has verified the home point and a return-to-home altitude clearing every obstacle back to the launch point. A return-to-home altitude set below the crane boom is a collision waiting for a dropped signal.
The plan should also cover flyaway: who is notified, how the airspace authority and installation are contacted, the ground search protocol, and how the event is reported. Add recovery scenarios — a downed aircraft in water, on a roof, in an energized substation, or across a rail line is a hazard to be planned rather than improvised. Nobody climbs, enters, or swims for a drone without a separate AHA. Weather triggers deserve numbers, not adjectives: maximum wind and gust, minimum visibility and ceiling, temperature limits affecting battery performance, and lightning standdown criteria. A crew with a written limit aborts; a crew with a feeling keeps flying.
Battery and LiPo handling hazards
The most common UAS loss source is not the aircraft in the air — it is the batteries on the ground. Lithium-polymer packs fail thermally, and once a pack enters runaway it is a self-oxidizing fire a standard extinguisher will not stop. The AHA should cover inspection for puffing, dents, and damaged leads; removal-from-service criteria; attended charging on a non-combustible surface in a designated area; storage voltage and temperature limits; transport in fire-resistant containers rather than loose in a truck bed; the response to a hot or swollen pack; and disposal of damaged cells. Add the site controls: no charging in an occupied trailer overnight, a lithium-rated extinguisher or a bucket of sand within reach, and a named list of who may charge. This is the section most borrowed drone JHAs skip, and the one an inspector is most likely to test.
Crane, overhead line, and site deconfliction
A construction site is full of things a drone can hit and things that will hurt the flight crew. Require deconfliction with crane operations in the flight area — either the picks stop, or the flight boundary excludes the swing radius, and the decision is written and briefed to the operator and the RPIC. Overhead lines, guy wires, tower cranes, antennas, and lighting masts are strike hazards notoriously hard to see on a camera feed, so obstacles belong on the flight map before launch, not discovered from the controller. Ground-level hazards deserve equal attention: the VO walking into an excavation while tracking the aircraft, haul roads crossing the observation position, and barricading that keeps non-participants out from under a descending aircraft.
Score the risk, verify the controls, brief the crew
A built-in risk assessment and control matrix standardizes ratings before and after controls, so a flight over active work or near energized lines routes to the SSHO instead of passing on the strength of a certificate number. Controls then become field verification items: preflight checklist completed, airspace authorization attached, battery inspection logged, launch zone barricaded, crane deconfliction confirmed, post-flight inspection recorded — which is what turns OSHA compliance software into more than a place to store a PDF.
A preloaded job hazard analysis library shortens drafting to minutes, and a customizable job safety analysis form lets the project add contract numbers, installation approvals, aircraft serial numbers, and district signoff blocks. Because UAS work moves — three sites in a day is normal — a useful mobile AHA/JHA tool must hold the current AHA, the airspace approval, the flight map, and emergency contacts offline, and let the RPIC capture the briefing and preflight at the tailgate. Automation can gap-check the draft, flagging a flight with no lost-link behavior documented or no named visual observer, but it should never invent site facts; the RPIC still owns the go/no-go. That is the honest boundary for job hazard analysis software and job safety analysis software alike.
Compare platforms by workflow and cost
Survey and inspection firms weighing tooling generally look at Gadzoom, SafetyCulture, VelocityEHS, Intelex, and HCSS Safety alongside AHA Generator. Enterprise EHS platforms are strong at program-level management and may suit an organization already standardized on one. The narrower questions for a two-person flight crew: does the system produce a Corps-acceptable UAS AHA before the flight window closes, does it carry 2024-edition EM 385-1-1 AHA templates and Part 107 content rather than generic aerial-photography language, and does it work with no signal at a remote levee?
AHA Generator is built as affordable JHA software for exactly that pattern. Its pay-per-credit hazard analysis generator model matches cost to output: buy credits when the flight schedule fills, produce the analyses each site requires, and pay nothing between mobilizations — which fits a survey shop far better than per-seat licensing for occasional pilots.
UAS work is now a regulated construction activity on federal sites, and the crews that treat it that way keep their flight approvals. Corps-ready templates, mobile capture, and offline evidence give flight crews a document that satisfies the district and actually helps at the launch point.
Create your next UAS AHA now: ahagenerator.com
#ActivityHazardAnalysis #UAS #DroneSafety #Part107 #RPIC #EM385 #USACE #OSHA1926 #JobHazardAnalysis #AHAgenerator #SafetyCompliance