Frequently asked
questions.

Per acre is the wrong yardstick: what you are buying is the decision the data has to support, and the cost of making that decision late or making it wrong. One provider covers the whole range, the accuracy follows ASPRS methodology and is documented where it counts, and every project includes reprocessing for the life of the data. A low per-acre number has a way of coming back later as a second mobilization, a format you cannot open, or a result that does not hold up in an audit.

The answer arrives on paper instead of on faith. Your deliverable carries a formal ASPRS statement, set to what the project actually requires: produced to meet the standard, or tested to meet it with independent checkpoints that are withheld from the adjustment and measured against afterwards, shipping a documented root mean square error (RMSE). Because we process and validate on site, we confirm the data is sound while the crew is still on your property (which is the only point at which a problem is cheap to fix).

Twenty-four hours from flight to finished deliverable in your portal. That figure holds because the processing happens on site in our mobile lab, so the work is largely done and validated before the crew leaves your property. Turnaround is project dependent and is confirmed in your quote, so the date you are given is the one we have committed to.

Your capture is covered for the life of the data. Lifetime Data Support means we reprocess what we already flew into any format that was in scope, take a fresh look at specific areas, and rerun it through newer and more accurate engines as those arrive, at no additional cost. The only thing that carries a new charge is a new flight, and even that is discounted, because your site is already mapped, controlled, and proven.

You get one accountable provider who shows up, processes on site in a mobile lab that can reach the far corners of a property, and does not leave until the deliverable is validated against your scope. A national network hands you software and a contractor pool, which is a different product sold under a similar name. We hand you a finished and verified deliverable, a working relationship, and reprocessing for the life of the data behind it.

No, and we do not sell one. Stamped and recordable deliverables are not an Outlook UAS product: where a project needs one, the work is routed to a licensed Professional Land Surveyor who holds responsible charge, and where you already work with a surveyor we supply the capture and processing into their workflow. For engineering, planning, progress, and volume decisions, a deliverable tested to meet ASPRS standards with a documented RMSE is built for exactly that use. We will tell you in scoping which one your project calls for.

Travel is the real cost of bringing a crew and the mobile lab to your site, priced transparently and never as a markup. The project minimum is what lets us commit to the trip on a smaller job (it is the floor that makes a single-site visit viable, not a fee added on top). On larger or recurring work it folds into the scope and stops being visible at all.

Nine data products, and your project takes the ones it needs: orthomosaic, terrain (DTM), surface (DSM), contours, point cloud, 3D mesh, volumetrics, imagery and video, and a 3D flythrough. The full library sits on the service catalog with an example deliverable beside each one. Most projects take three or four, not nine, and the walkthrough on the aerial mapping page narrows it by industry and by the problem in front of you.

It names the standard, the edition, and the class, and it says which of two commitments applies. The wording comes from the ASPRS Positional Accuracy Standards for Digital Geospatial Data, Edition 2, Version 2 (2024), and the class is set by what your project requires instead of being picked off a shelf. Where the deliverable is tested, the statement also carries the measured root mean square error (RMSE) and the checkpoint count, so the number on the page can be traced to the survey that produced it.

Produced to meet says the dataset was built to a documented workflow: flight design, image overlap, post-processed kinematic (PPK) positioning, and processing discipline, with the ground sample distance stated on delivery. Tested to meet adds the measurement itself, and Edition 2 sets that floor at 30 independent checkpoints for a project area up to 1,000 square kilometres. Section 7.16 of the standard carries a reporting form for a site too small to reach 30, which is where most drone projects land, and a reduced count is stated plainly on the report instead of implied away.

Control is project dependent, and what decides it is what the number has to survive. Control may already exist on your site, or we establish it with an OPUS or GNSS session. Edition 2 asks that control and checkpoints be evenly distributed throughout the project area, with practical judgment where water, heavy vegetation, or access prevents it, so placement is a field decision and not a template stamped on every job.

Your data is never deleted. A retention tier governs how long the project stays open in your portal, not whether the capture survives, and reprocessing under Lifetime Data Support does not expire with the access window. Extended portal access past the included window is arranged with us and is not bought from a page: tell us the review cycle you work to and we will set it up.

Yes, and it is a product of its own: the Accuracy Verification Package tests aerial mapping data you already hold, whether it came from us, another vendor, or an internal program, with checkpoint locations planned independently of whoever produced the control. The report names the class the result actually supports, the checkpoint count, and the documented RMSE. A failing result is still useful, because it tells you which decisions that dataset can carry.

Fifteen minutes. That is a reply from the person who will do the work, not an autoresponder confirming receipt, and it does not wait for business hours, so scope a project and you will see it for yourself.

It is free, thirty minutes, by video or phone, and there is nothing to prepare. It is a first verbal pass across the things that decide whether a program holds up: standardization, pilot currency, records, and training cadence. You get a verbal recap and one recommended next step, and no written finding, score, or checklist is issued from the free call. If the answer is that nothing needs to change, that is a valid outcome.

Josh. M.S. in Uncrewed and Autonomous Systems from Embry-Riddle, former Instructor of Record for accredited undergraduate UAS coursework and university UAS program management, author of Safety Management System documentation with airmen and aircraft records oversight under FAA Parts 91, 107 and 135, FAA Part 107 and Part 61 rotorcraft, flying this work commercially since 2017. The person on the call is the person who does the work.

No. Outlook Universal Aerial Services, LLC provides regulatory readiness consulting: reviews, structured workbooks, and application preparation coaching. It is not a law firm and provides no legal advice, and it does not file, sign, or represent clients before the FAA, TSA, or FCC. You remain the applicant, you sign and submit every application, and the FAA alone decides.

No, and no one can, because the FAA decides waivers, permits, and certificates on its own timeline. What readiness work changes is the quality of what you put in front of them: the FAA's own waiver trend analysis reports that the vast majority of applications are two sentences or less, and its most common denial reason is failing to identify hazards and describe mitigations that reduce risk to an acceptable level. 14 CFR 107.200(b) asks for exactly two things, a complete description of the operation and justification that it can be conducted safely.

Part 108 is a proposed rule, and every mention of it here says so. The FAA's August 2025 notice of proposed rulemaking can change in its categories, thresholds, timing, and transition provisions before there is a final rule, and the proposal as published defines no automatic path for existing waiver holders. Readiness work consolidates your Part 107-era evidence into the proposal's vocabulary without assuming the final rule will preserve the proposal.

No. Passing a course creates a knowledge record, which is not permission to operate. Practical authorization rests with your employer authority or a designated evaluator who approves a person for defined aircraft, missions, payloads, and environments. Outcomes read demonstrated, not yet demonstrated, or demonstrated with conditions, never a grade. Part 107 recurrent training runs every 24 calendar months, and knowledge records stay separate from practical authorization.

It is the one-stop package. We build out the safety management system, the training program, the mapping and field checklists, and the aircraft and records structure, then hand the whole set over for you to put your own name on and edit as the operation changes. There is no licensing attached and nothing reverts to us: these are your documents, in your name, which is what the Build stage exists to produce.

There is no public price list and no application package to buy from a page. Paid work is fixed fee and scoped individually after the free call, because what it takes depends on what your program already has. How fast the rest moves is set by what the program needs, not by a clock we impose.

166 United States Part 107 accident and incident reports from NASA ASRS and the NTSB, 2016 through 2025, coded to HFACS in Embry-Riddle graduate research. Three unsafe-act patterns aim the curriculum: skill-based errors toward practical proficiency, decision-making errors toward scenario training, and known deviations toward compliance culture. The study is retrospective and associational, so it does not establish causation, evaluate any training program's effectiveness, rank operators, or promise an outcome, and it is not government endorsement.