Part 107 training & competency→
Live Part 107 preparation and competency-based recurrent training, aimed by a remote-pilot competency taxonomy derived from Part 107 accident and incident data. The certificate is where it begins, not where it ends.
Ground control target set
Build a UAS program that holds together.
Outlook UAS helps teams decide what to own, standardize current operations, prepare for expanded authority, and train pilots through scenario-based work tied to the missions they perform.
Free either way. If nothing needs fixing, that is worth knowing too.
Current state before recommendations
Missions, authority, people, aircraft, records, and data workflow are examined before a build plan is proposed.
See the review approach→
Scenario-based training
Control, workload, judgment, and recovery are tied to the missions pilots actually perform.
Review the training→
An operating record your team owns
Authority, currency, aircraft, maintenance, mission, and data records remain reconstructable.
See the field toolkit→
Accuracy & ASPRS prep
Accuracy tested and disclosed to a stated ASPRS class, independently, not offered as an adjective.
See accuracy verification→
A program is a chain, not a certificate.
An in-house program is a chain. Each link below has to hold for the decision at the end to hold. A certificate licenses a pilot; it does not demonstrate competence for this aircraft, payload, and mission.
Governance & authority
Who owns mission approval, safety, competency, and final acceptance, and whether the documented practice matches what actually happens.
Mission planning, airspace & weather
The planning standard, airspace, site hazards, and weather limits tied to the deliverable, and who holds go/no-go authority.
Pilot competency & human factors
Mission competence beyond the certificate, recurrent proficiency, and the three human-factors patterns behind real UAS accidents: skill-based errors, decision-making, and known deviations.
Aircraft, maintenance & records
Configuration, Remote ID, firmware, batteries, and maintenance, captured in records you could reconstruct months later.
Acquisition design
Turning the intended use into a collection specification: altitude, ground sample distance, overlap, geometry, control, checkpoints, and acceptance criteria.
Positional quality & data integrity
Independent verification, coordinate systems and datums, a measured RMSE with limitations, and reproducibility: produced-to versus tested-to.
Data lifecycle & economics
Storage, retention, and access; the complete cost per accepted, decision-ready output; procurement discipline; and the path to scale.
Open any stop on the chain to read the operating domain behind it. The free call above touches the areas most relevant to your program today; a fuller Review examines all seven domains and connects findings to evidence you already have.
Where is the program stuck?
Find the closest condition, then follow its branches. Each path names the most useful place to begin, without grading the program or forcing it into a package.
Practice varies between pilots.
Standardization, currency, records, and training cadence read differently depending on who flies that day.
If no one has read the whole program recently
Book the Readiness Call→Free · 30 min
A free conversation reads standardization, pilot currency, records, and training cadence as they operate today. Verbal recap, one next step, no score.
If the gaps are already known
Scope a Program Review→If warranted
A fixed-scope look across the program's operating domains, tied to evidence you already have. Findings and a prioritized plan you own.
If only the training has drifted
Scenario-based training→Live · scoped
Control, workload, go/no-go judgment, and recovery rehearsed against the missions pilots actually perform.
Deciding what to own.
Mission frequency, geography, workflow fit, internal people, and control of the record decide the model before any equipment does.
If the mission is occasional or specialized
Hire the capture→Free quote
Payloads used once or twice a year cost far more to own than to hire from a specialist who flies them.
If the mission is recurring and core
Test the internal case→Decision guide
Six signals that favor an internal capability, tested before equipment is bought. Ownership has to earn its place.
If both are true
Run a deliberate hybrid→Decision guide
Build the recurring core in-house, hire the exceptions, and keep one operating record across both.
A rule limits the mission.
Operating authority is prepared on paper before it is flown. The useful first move depends on which relief the mission actually needs.
If the relief is waivable under Part 107
Waiver readiness→Scoped
A readiness review against the target waiver, a prioritized roadmap, and coaching for your CONOPS, risk analysis, and safety case.
If the target is BVLOS at scale
Part 108 preparation→Proposed rule
Consolidate Part 107-era evidence into the shape the proposed rule would expect, without assuming the final rule preserves it.
If the blocker itself is unclear
Book the Readiness Call→Free · 30 min
Thirty minutes to separate what is actually waivable from what is an authorization, and to name the next step.
Training misses the work.
Part 107 knowledge preparation and recurrent program training are different jobs. The right entry depends on where the pilots stand.
If pilots are not certificated yet
Part 107 preparation→Live course
Live preparation for the certificate, taught from a working aerial-data operation. The certificate is where it begins.
If certificated pilots miss mission skills
Scenario-based recurrent training→Live · scoped
The three patterns behind real UAS accidents, rehearsed against your own missions instead of generic drills.
If practical ability is unproven
Proficiency flight work→Practical
Flight work observed and documented to a stated standard. Knowledge is trained; practical ability is demonstrated.
Field collection varies by crew.
The accepted deliverable defines the field work: control, checkpoints, resolution, overlap, and completeness before the crew leaves the site.
If the spec lives in someone's head
License the Operator Toolkit→Licensed
Plan the field work from the required deliverable, backward, on a repeatable accuracy standard rather than an operator's memory.
If data exists but no one has tested it
Independent accuracy verification→Independent
Surveyed checkpoints, a documented RMSE, and an honest checkpoint count against what the program believes it has.
If the program would rather hire the capture
Aerial data, flown for you→Free quote
Field-checked collection with a qualified 24-hour handoff, while your team keeps the decision.
Want to inspect the evidence first? Review the research basis→
Where it starts, and where it can go.
One free call is the whole commitment today. Everything past it is scoped only if it earns its place. This is the shape of the work, not a schedule.
Free · first signal
Readiness Call
A 30-minute read of where the program stands, out loud.
You leave with the first thing to fix: no writeup, no score.
If warranted
Review
A fixed-scope look across all seven domains of the program.
Findings, a maturity picture, and a prioritized plan you own.
If you choose it
Build
The findings turned into competency, SOPs, training, and records.
A working system your team runs, not a binder on a shelf.
Ongoing
Sustain
Currency, records, and renewals kept current on a cadence.
A living system that stays decision-ready and gets sharper each cycle, not a binder that ages on a shelf.
The first signal comes in the call itself. How fast the rest moves is set by what the program needs, not by a clock we impose.
Insurance readiness
Records an underwriter or counsel could follow.
Uptime
Aircraft that keep flying, on schedule.
Documentation
A record that holds up after an incident.
The four levels of the practice.
Each has its own page: what it covers, how it is delivered, and what a program walks away with. Every one of them begins with the same free call.
Field & data-collection discipline→
The intended use turned into a collection specification (control, ground sample distance, overlap, and checkpoints designed before the flight) with field completeness checks before the site is left. Fewer reflights, data accepted the first time.
Accuracy & ASPRS prep→
Accuracy stated the only way that defends itself: intended use, coordinate system and datum, control, independent checkpoints, a measured RMSE, and honest limitations, to a stated ASPRS class, tested independently.
The research underneath→
Graduate research (Embry-Riddle) applying HFACS to FAA Part 107 accident and incident data, standards work, and the operational aviation history the practice stands on. Credentials and documentation on request.
Already producing data?
An independent accuracy verification against a program's own data is often the most useful first hour: surveyed checkpoints, a documented RMSE, and an honest checkpoint count against what the program believes it has.
How an Accuracy Verification works→
Everything on this page is either educational or the free call. A fuller Program Review, competency Build, and ongoing Sustain support are scoped in conversation, never sold from a page.
The practice has a documented research basis.
Research helps aim program questions and scenario-based training. It does not substitute for a review of the organization's own operation.
Reports coded
166 U.S. Part 107 accident & incident reports
Sources
NASA ASRS + NTSB
Window
2016 through 2025
Framework
HFACS human-factors coding
The retrospective graduate study (Embry-Riddle) identifies patterns in practical proficiency, decision-making, and known deviations. It does not establish causation, evaluate a training program's effectiveness, rank operators, or promise outcomes. Credentials and documentation on request.
Start with the program as it runs today.
No polished binder is required. Bring the mission types, current practices, and the point where useful or repeatable work is getting stuck. If nothing needs fixing, that is worth knowing too.