All insights

Field notes · Flybi Insights

What a week on a mine site changes.

Capture windows, haul-road activity and the people who use the output. A field note on making a measurement programme fit an operating mine.

FlybiOriginally published 22 April 20262 min read

Editorial revision · 11 October 2026

Orthomosaic showing an exploration block and its surrounding terrain
Original geospatial report outputA site in its operating context · Source orthomosaic from the technical report. The field note does not identify this as the mine described.

The blast window is not what you think it is.

Our proposal said "weekly overflight, Monday morning." The site's blast calendar said Monday at 11:00 is when the SW highwall comes down. Our flight window was 10:30–11:30. We learned this on day two, from a ground-crew foreman, not from the mine's own GIS team — because no one had ever written the blast schedule down in a form that crossed departments. We shifted to 06:10 Tuesday, before the first shift changeover. The lesson was to confirm the operating window across the relevant teams before each flight.

Haul-road condition is a mapping priority, not a nuisance.

We were there to map the pit. The mine manager wanted to know which haul road was killing his tyres. Point cloud ingestion was easy; the lesson was that the project buyer and the data user are often different people, and the scope should follow the user.

The dust doesn't stop because we booked a flight.

Airborne dust affected the first capture. The response was to coordinate the flight window with the water-tanker cycle and shift changeover. Field scheduling and image processing solve different problems: reliable information has to be captured before it can be processed.

Photos beat tickets.

A located photograph gives an engineering team something concrete to review: where the observation sits, what was visible and what needs a closer look. That is the value of connecting imagery to a site model. The finding still needs an owner, an assessment and a place in the team’s maintenance process.

The CFO wants the ledger, not the map.

We came in thinking the mine manager was the buyer. By week four, the CFO had joined our weekly review. She didn't want to see the 3D pit. She wanted the weighbridge-reconciled stockpile ledger. That became the new flagship deliverable — and the one that justified the monthly retainer.

The scope writes itself after week two.

The first delivery often reveals which information the site team will actually use. Build a review point into the programme, then agree any change in outputs, cost or responsibilities. The scope can become more useful without becoming ambiguous.

From understanding to action

Bring the question to your site.

Tell us what you need to measure, understand or review. We can help define the next step.

Explore V7

A useful first conversation

Let’s understand your site.

Share the question. We’ll help shape the scope.

Tell us what you need. Your details are used to handle this enquiry.

Explore Flybi

What can we help you find?

Start here

    Your browser. Your choice.

    Website preferences.

    This website uses no advertising cookies or analytics. Choose whether this browser remembers your motion preference.

    About browser storage

    Privacy details

    Flybi guide

    Website guide · Not live AI

    Hello. What would you like to understand about your site?

    Scripted guide. Your message stays in this page.