The Standard

A written standard, not a hobby.

Every flight we conduct is run against a Standard Operating Procedures manual modeled on FAA Part 91 commercial conventions — the same manual we'd hand to an insurance underwriter, a public safety client, or a TOP-program auditor.

Process discipline is what separates a $30,000 mapping contract from a $300 real estate gig. We built the operation for the former.

Before the flight.

By the time we arrive on site, the mission is largely already complete. Hours of planning have happened in advance.

Scope and deliverables are defined in writing before any flight is scheduled. Airspace is reviewed and any required authorizations — LAANC for controlled airspace, waivers, exemptions — are filed days in advance through Aloft, not on arrival. Weather is briefed using aviation-grade tools: METARs and TAFs from aviationweather.gov, winds aloft, NOTAMs reviewed in ForeFlight. Wind at four hundred feet, where the aircraft will actually fly, is what matters. Temporary flight restrictions — presidential movements, sporting events, wildfires — are screened before any equipment leaves the case.

A formal risk assessment is completed for every mission. Higher-risk missions trigger additional planning, second-pilot review, or scope reduction. Some missions are declined.

On site.

Arrival is choreographed. There is a sequence, and we follow it every time. Buyers who have hired drone operators before recognize the difference within the first five minutes.

The vehicle parks outside the takeoff and landing zone, not in it. Equipment is staged from a foam-cut Pelican hard case, kept clean and organized — the case itself is a signal. A walking site survey confirms hazards identified in pre-mission planning and flags anything new. A defined operations area is established with a landing pad and traffic cones marking the perimeter, so bystanders see immediately that this is an operations area, not a hobbyist setup. Crew arrives in branded ANSI Class 2 high-visibility safety vests and hard hats. There is no ambiguity about who is operating the aircraft.

Real-time air traffic awareness comes through a portable Stratux dual-band ADS-B receiver, displayed on a 13-inch iPad running ForeFlight. We see manned aircraft within fifty miles before we see them with our eyes. A handheld aviation-band transceiver monitors local CTAF, UNICOM, and approach frequencies during the entire operation. Wind aloft is verified with a Kestrel handheld weather meter, not estimated from ground conditions.

A pre-flight checklist is run on every flight, off a printed and laminated reference. Not from memory. The day a pilot flies from memory is the day the pilot misses something. A crew briefing is conducted before takeoff — even on solo flights, with the client representative if no other crew is present.

In the air.

The flight itself is the visible part of the iceberg. By this point, the work is mostly executing the plan.

The aircraft is in continuous direct sight throughout the flight, by the pilot or by a designated visual observer whose only job is that. ADS-B air traffic awareness is monitored continuously on a separate iPad display, independent of the drone controller. Radio traffic on local aviation frequencies is monitored throughout.

Battery state is monitored against conservative thresholds — return-to-home triggers at twenty-five percent remaining, well above the manufacturer's defaults. Manufacturer minimums assume ideal conditions; conditions are never ideal. The aircraft yields to all manned aircraft, every time, without exception. If a Cessna enters the area, we descend and land before they're a factor.

For mapping work flown on the Freefly Astro with an RTK ground base, flight paths are flown at consistent altitude, ground speed, and overlap to manufacturer specification through Auterion Mission Control. Survey-grade outputs require survey-grade flying. For cinematography, distance to subjects, structures, and people is held to internal standards stricter than the regulations require.

After the flight.

The aircraft is on the ground. The client may consider the work done; we consider it half-complete. The next phase is internal.

A post-flight inspection of the airframe happens before it is repacked into the case. Anomalies are caught now, not on the next mission. Every flight is logged in Airdata UAV — date, duration, conditions, pilot, aircraft, battery cycles, anomalies. Logs are maintained for years and are available to clients and insurance carriers on request.

Flight data and source media are downloaded to encrypted storage with redundant backup before the equipment leaves the site. A debrief is conducted with the crew on what worked and what to change. Any incident — a hard landing, a near-miss with another aircraft, an unexpected behavior — is documented internally and used to improve the operation. We report what worried us, not only what broke something. A near-miss reported is more valuable than damage that wasn't.

The deliverable.

Most drone operators treat the deliverable as an afterthought — the email at the end with a Dropbox link. We treat it as the product. The flight is the means; the deliverable is what the client actually bought, and it has its own design discipline.

There are two failure modes for drone deliverables, and the buyer who has worked with operators before has probably encountered both. The first is the Dropbox dump: a folder of unedited files and a "let me know what you think" email, leaving the client to figure out what they have. The second is deliverable theater: a flashy PDF that obscures thin underlying work. We aim for neither.

Two categories, two workflows.

Imagery deliverables are aesthetic products. Data deliverables are technical products. They ship through different platforms because the audiences inside the client's organization are different — marketing opens one, engineering opens the other.

Accuracy is reported, not promised.

For mapping work, every deliverable includes ground sample distance, absolute and relative accuracy verified against ground control points, RTK fix percentage, and processing software metadata. Without these numbers, an orthomosaic is a pretty picture. With them, it is a survey-grade dataset that a civil engineer can build on. We provide the numbers on every project.

One persistent client portal per engagement.

Everything we deliver — imagery, video, maps, models, documentation — lives at a single branded URL: sightlinegeospatial.com/clients/[client]/[project]. Past projects do not get buried in old email threads. The client comes back to the same place a year later and finds everything as they left it.

Service tiers map to deliverables, not flight hours.

Clients self-select the scope they need. Tiers are stackable — a recurring engagement can include any combination of imagery, mapping, and modeling deliverables.

Lifecycle sequencing for complex engagements.

For land development, master planning, and hospitality siting, deliverables sequence across the project lifecycle. The same airframe, the same operator, multiple touchpoints over multiple years — building a single coherent record of the property from acquisition through operations.

Why this matters.

Process is interesting only insofar as it produces outcomes. Here is what the discipline buys our clients.

Reliability.

Missions get flown when they are scheduled, or they are rescheduled before the client is on site. Operators who are casual about weather are casual about your timeline.

Insurance and liability.

We carry commercial liability and aircraft hull coverage in line with industry-standard limits through SkyWatch.AI. Certificates of insurance naming the client as additional insured are issued before the engagement begins, not after.

Defensibility.

If something goes wrong — and over enough flights, something eventually does — the documentation exists to demonstrate that the operation was conducted to standard. That defensibility is the client's protection, not just the operator's.

Regulatory credibility.

A documented operation can support waivers, exemptions, and complex airspace authorizations that an undocumented operation cannot. As the work scales, the documentation is what enables the scaling.

Deliverables that drop into existing workflows.

Civil engineers can use the orthomosaic in their CAD environment because we deliver it in their coordinate system with their accuracy requirements documented. Marketing teams can use the imagery because it is color-graded, sized, and licensed properly. The deliverable design saves the client's internal team hours of rework on every project.

A persistent record.

Every project remains accessible to the client indefinitely, in one place. When a contractor disputes a billable volume eighteen months later, the data is still there. When a real estate listing needs to be refreshed for a re-sale, the master files are still there. The engagement does not end when the invoice clears.

Standards & currency.

The credentials behind the operation. Listed as facts, not as marketing. Updated as currencies are renewed and new programs are pursued.