BlueCap Australia

Drone LiDAR Survey & Mapping

LiDAR mapping built for mineral exploration and mining, mine planning, telecommunications and infrastructure — from broad terrain programmes to detailed corridor and site mapping.

BlueCap LiDAR terrain mapping data visualisation
Delivered terrain evidencePoint cloud → usable terrain modelsBare earth · canopy · obstacles · QA

LiDAR survey · LiDAR mapping · terrain models · point clouds · QA

BlueCap provides drone LiDAR survey and mapping services for mineral exploration, mining and infrastructure across Australia and worldwide. The BlueCapLidar® drone LiDAR system and long-endurance aircraft connect acquisition to classified point clouds, bare-earth terrain models and reviewable QA.

Production envelope

Aircraft-scale LiDAR coverage from a drone survey system

Four planning numbers connect field capacity, parallel deployment, point density and processing turnaround.

90–540km²/day
Productive area

9,000–54,000 ha across an eight-hour field day, depending on acquisition pattern and project conditions.

1–3systems
Parallel aircraft

One to three long-endurance BlueCapHeli® systems can acquire independent blocks in parallel.

100–250pts/m²
Planned point density

The project range runs from productive single-pass acquisition to a dual-orthogonal canopy survey.

Next-daydelivery
Processing turnaround

Field acquisition is visible in the browser; controlled terrain processing continues after each flight.

One connected LiDAR survey system, from project brief to terrain delivery

BlueCap Survey Portal

Define the survey area, plan routes, develop a quote-ready scope, follow field acquisition and keep processed results and deliverables in one connected project workspace.

BlueCapLidar® Payload

Dual-sensor point clouds, four-IMU data, RTK positioning and flight telemetry remain connected in the same synchronised field record.

BlueCapHeli® Carrier

The hybrid petrol-powered carrier provides 3 or 8 hours of endurance, field refuelling and a normal 100 km/h cruise speed for productive survey acquisition.

Cloud Post-Processing & Automated Workflow

The BlueCap-controlled cloud service filters and stitches point clouds, runs terrain processing, classification and QA, and packages consistent automated deliveries.

Five members of the BlueCap Australia survey team

BlueCap Survey Team

Geophysicists, remote pilots, engineers and post-processing specialists work as one accountable survey team from mission planning through acquisition, QC and delivery.

  • A typical deployment includes at least five core personnel plus approximately 5–10 local spotters.
  • AI-assisted tools accelerate repeatable processing and add a verification layer; experienced geophysicists remain responsible for final QC and every client deliverable.

LiDAR survey cost, schedule and market comparison

Estimate indicative LiDAR survey pricing, flight line-kilometres and field duration, then compare the commercial effect of productive area per flying day. This service view fixes the planning basis at 180 m parallel LiDAR line spacing; terrain, overlap, turns, required point density and a dual-orthogonal second pass are confirmed in the project quotation.

LiDAR survey indicative cost & schedule

Outside Australia? Open the full estimator →
Drones flying in parallelOne BlueCap field team operates the selected number of drones in parallel. Staffing scales to 5, 9 or 13 people and includes Chief Pilot, Operator Pilot, Junior Pilot, Spotters and Assistant roles.
Line spacing
Drone survey sizeChoose the approximate square drone survey footprint. Area and required flight line-km update with the selected grid spacing.
Indicative all-inclusive rateA$302 / line-kmSame rate across terrain and comms conditions
Planning estimate only. Actual duration may vary with approvals, weather, terrain access, logistics, equipment readiness and other practical operating conditions.
Estimated production flying days required by the selected flight line-km and number of parallel drones. Project flying operational days are calendar days when the field team is deployed in the survey area and conducting operational activities.
1
Estimated mobilisation period covering team travel to and from the project site together with non-flying and flying operational days.
1
Indicative totalA$190,000Mobilisation within Australia included

Open the complete calculator for international missions, currency display and downloadable estimates →

Like-for-like commercial comparison

Lower project cost. Centimetre-level terrain accuracy.

330 km² · approximately 50 delivered pts/m²

The public BlueCap reference combines an approximately A$160k project price with the single-pass acquisition basis shown below. Compare the required density, accuracy, ground returns and classification before comparing daily area. Three BlueCapHeli® systems are shown separately as a throughput option, not as the A$160k configuration.

BlueCap Survey Portal 2D map of an approximately 18 by 18 kilometre single-pass LiDAR mission divided into sorties for one BlueCapHeli
Portal mission-plan evidence

One block, verified in 2D and over 3D terrain.

Survey area
≈18 × 18 km · 324 km²
Line spacing
180 m · single pass
3D sensor AGL
100 m above terrain
2D density scenario
200 pts/m²
Deployment
1 × BlueCapHeli®
Portal verification
2D allocation · 3D drape

The 2D view documents coverage and sortie allocation at a 200 pts/m² planning target. The 3D view checks the same 18 × 18 km class of mission against terrain at 100 m sensor AGL and 180 m line spacing. These Portal views are planning evidence, not a substitute for the density, speed, overlap and deliverables confirmed in the quotation.

01 · BlueCap reference price≈A$160kproject≈A$485/km² at 330 km²

Indicative one-system planning reference before the project-specific review of terrain, mobilisation, classification and deliverables.

02 · Crewed-aircraft scenarioA$250–400kcrewed scenario≈A$760–1,210/km²

Indicative like-for-like planning scenario for a current crewed-aircraft quotation. It is not presented as a fixed market tariff.

03 · Scenario saving with BlueCapA$90–240klower≈36–60% below the scenario

Replace the scenario with a current aircraft quotation and compare the same density, accuracy, ground-return, classification and mobilisation scope.

Survey solutionRealistic productive areaFlying days at 330 km²
BlueCapHeli®Productivity165 km²/dayFlying days2
DJI M350 + L2Productivity2–6 km²/dayFlying days55–165
DJI M400 + L3Productivity12–25 km²/dayFlying days14–28
Large electric multirotor with high-end LiDARProductivity5–12 km²/dayFlying days28–66
Electric fixed-wing / VTOL LiDARProductivity15–40 km²/dayFlying days9–22
Petrol or heavy-lift fixed-wing droneProductivity30–70 km²/dayFlying days5–11
Comparable high-density performance

Compare density, accuracy and daily area together.

A crewed aircraft can map thousands of square kilometres per day when collecting low-density regional elevation data. That is not equivalent to a detailed survey targeting approximately 50 points/m² and centimetre-level acquisition accuracy. The useful comparison fixes the deliverable first, then compares daily coverage, mobilisation and project cost.

3 × BlueCapHeli® in parallelUp to 540 km²/day
Target delivered density
≈50 pts/m²
Acquisition accuracy basis
3–5 cm XY · 4–8 cm Z single pass
Effective survey swath
3 × ≈180 m effective

Three independently planned low-altitude blocks combine regional production with local deployment, terrain following and operation beneath higher cloud layers. Dual-orthogonal acquisition can tighten the stated accuracy further when the project requires it.

Crewed airborne LiDAR≈300–800 km²/day
Target delivered density
≈50 pts/m²
Acquisition accuracy basis
Must match the quoted BlueCap requirement
Effective survey swath
Sensor and altitude dependent

At comparable high density and accuracy, lower altitude, narrower swath, reduced speed or added overlap reduce the headline coverage available from low-density regional flying.

In the indicative scenario, BlueCap is A$90–240k lower while targeting approximately 50 delivered pts/m², 3–5 cm XY and 4–8 cm Z in the single-pass mode — a denser, more precisely defined terrain product than the 4–8 pts/m² aircraft examples.

Density and absolute accuracy are separate measures, so both are stated. The three-system row compares available daily throughput only; the ≈A$160k reference uses one BlueCapHeli® across two flying days. Replace the crewed scenario with a current quotation and require the same density, accuracy, ground-return, classification and mobilisation scope before procurement.

Why the BlueCap price holds

Productivity changes the commercial result.

Long missions

Long-endurance sorties keep useful acquisition time high.

Fewer base moves

Less repositioning and fewer return-to-base cycles across the block.

Two flying days

The 330 km² reference block is planned across two productive field days.

More area per mission

Approximately 165 km²/day on the comparison basis.

One workflow

BlueCap owns acquisition, processing, QA and delivery as one system.

Productive area and price remain project-planning figures, not universal guarantees. Line geometry, overlap, turns, point density, terrain, canopy, airspace, weather, mobilisation and deliverables are confirmed in the quotation. Alternative-system ranges describe realistic planning envelopes for a comparable 330 km² block.

Designing for area, density and accuracyTwo patterns. One project trade-off.

BlueCap LiDAR point-cloud terrain visualisation used for acquisition planning
AreaDensityAccuracy

Choose the acquisition pattern from the terrain product required, not from scanner footprint alone. A second pass at 90° exchanges daily area for higher point density and a clearer understanding of the surface beneath tree canopy.

Scanner footprint285 × 160 mInstantaneous window
Converted into field output by
  • Flight pattern
  • Turns and overlap
  • Terrain and canopy
  • Density and QA
Delivered field output90–540 km² / 8-hour dayUsable terrain products
01Productivity first

Parallel single-pass

One set of parallel flight lines, typically spaced about 180 m apart. This is the production-first pattern for broad areas and more open terrain.

Line design
~180 m spacing
Field output
~180–540 km²/day
Point density
~40–80 pts/m² ~100–120 pts/m² where geometry and speed support it

Best fit

Broad-area acquisition where field productivity is the priority. Particularly well suited to flat, lightly vegetated terrain such as deserts and open Western Australian bushland, where a single viewing axis meets the terrain-product requirement.

02Surface understanding first

Dual-orthogonal

The complete block is flown twice: one full parallel grid, then a second full grid at 90°. Crossed coverage adds a second observation axis across every part of the site and four viewing directions rather than two.

Line design
Two complete grids Project-equivalent north–south + east–west coverage
Field output
~90–270 km²/day
Point density
~100–250 pts/m²

Why the second full grid matters

Complementary pulse paths reduce direction-dependent occlusion behind tree crowns, scarps, rock faces, slopes and structures. They improve the opportunity for ground returns, make point geometry more uniform and support more stable classification and reconstruction of façades, outcrops and complex terrain.

Reference trade-off against single pass: field output is about half; density moves from ~40–80 to ~100–250 pts/m²; XY from 3–5 to 1.5–2.5 cm; Z from 4–8 to 2–4 cm; and canopy Z from ≤10–15 to ≤7 cm. These are project-design targets, not a universal probability of ground detection.
Delivered terrain quality

Absolute accuracy

The same measures stay aligned for direct comparison between both flight patterns.

Typical line spacing
~180 m
Sidelap
20% standard · 40% canopy
Flight speed
60–100 km/h
Flight designXYZZ under canopy
Parallel single-passXY3–5 cmZ4–8 cmZ under canopy≤10–15 cm
Dual-orthogonalXY1.5–2.5 cmZ2–4 cmZ under canopy≤7 cm
Common comparison basis
  • 100 m AGL reference
  • Eight-hour field day
  • Turns and return-to-base included
  • Complete refuelling or battery service included
Experience-based field planning · eight-hour field day

BlueCapHeli® vs Matrice L2

The same survey blocks are compared on complete acquisition cycles. BlueCap uses 2.5-hour fuelled flight legs; Matrice uses battery flights with return-to-base service. Turns and complete refuelling or battery-service cycles are included. These are planning values, not guaranteed production rates.

Experience-based BlueCapLidar® and DJI Zenmuse L2 field-time comparison
Survey blockSystemFlight timeField daysFlight cycles
and field service
10 × 10 km100 km²BlueCapLidar®carried by BlueCapHeli®4h 30m12flight legs · 1 refuel
Zenmuse L2carried by DJI Matrice 300 RTK77h13165battery cycles
20 × 20 km400 km²BlueCapLidar®carried by BlueCapHeli®18h38flight legs · 7 refuels
Zenmuse L2carried by DJI Matrice 300 RTK307h 30m51659battery cycles
30 × 30 km900 km²BlueCapLidar®carried by BlueCapHeli®40h516flight legs · 15 refuels
Zenmuse L2carried by DJI Matrice 300 RTK692h1151483battery cycles

Why LiDAR comes before a magnetic survey

BlueCapLidar® first measures terrain, canopy and obstacles. That surface becomes a calculated magnetic drape used by BlueCapHeli®, BlueCapWinch® and the suspended QuSpin QTFM Gen 2 as one acquisition-control system.

Control target1 mterrain-following accuracy relative to the LiDAR model
BlueCap LiDAR terrain surface used to calculate a magnetic survey drape
100 m AGLLiDAR surface model
Calculated drapeterrain · canopy · obstacles
>20 mcarrier–sensor separation
Measured terrain becomes the magnetic control surface
  1. 01

    Map the surface

    BlueCapLidar® records a 285 × 160 m instantaneous window at 100 m AGL and builds the terrain and obstacle model.

  2. 02

    Calculate the drape

    Terrain, canopy and obstacles become a flyable sensor-height profile; 35 m sensor AGL is a common reference in difficult tropical and subtropical relief.

  3. 03

    Control the sensor

    BlueCapWinch® actively manages the QuSpin QTFM Gen 2 while maintaining more than 20 m carrier-to-sensor separation.

  4. 04

    Fly and verify

    Speed control and sensor-AGL QA follow the calculated surface to target a 1 m terrain-following corridor before interpretation.

Geophysical purpose: hold sensor geometry stable enough that amplitude changes can be interpreted as geology rather than terrain-following error.

Controlled field evidence

Field experiment: terrain-following error can masquerade as geology

BlueCap repeated one controlled vertical profile at four separate field locations. BlueCapHeli® ascended above a QuSpin QTFM Gen 2 suspended on a pre-measured 20 m line while the stripped tubular bird rotated freely at each 25–50 m sensor-AGL level. Every height refers to the sensor above ground, not carrier altitude.

BlueCapBird® suspended magnetic sensor used for controlled sensor-height field testing
Only sensor height changed; horizontal position remained fixed
  1. 01
    RepeatabilityFour locations

    The response was repeated across separate sites rather than inferred from one location.

  2. 02
    Horizontal controlOne fixed point

    The carrier held horizontal position while only sensor-to-ground distance changed.

  3. 03
    Vertical control25–50 m AGL

    The helicopter increased height in one upward sequence; the 20 m suspension length remained fixed and sensor AGL was measured by range LiDAR.

  4. 04
    Airframe separationMore than 20 m

    The magnetic sensor never came closer than 20 m to the BlueCapHeli® airframe.

First-order interpretationAmplitude ∝ r−3for a compact shallow source at comparable observation geometry
Sensor too lowshort-wavelength anomaly appears stronger
Sensor too highanomaly is attenuated and spectrally shifted

Interpretation boundary: the chart below normalises the 35 m response and applies the first-order relationship across the tested 25–50 m range. It interprets the controlled experiment; it is not the unpublished raw time series.

BlueCap field experiment · normalised interpretation

Normalised height-response curve

The curve sets the 35 m sensor-AGL response to 100% and applies the first-order 1/r³ relationship across the field-tested 25–50 m range. It interprets the controlled experiment; it is not a plot of the unpublished raw series from the four locations.

25 m30 m35 m40 m45 m50 m0%50%100%150%200%250%300%~274%~159%100%~67%~47%~34%Normalised anomaly response (% of 35 m sensor-height reference)QuSpin sensor height above ground (m AGL)
Normalised 1/r³ reference across the field-tested height range 1 m terrain-following control band using a BlueCapLidar® surface model Reference at 35 m sensor AGL = 100%

Processing and deliverables

The engineers responsible for BlueCapLidar® also control its MCAP/MavROS 2 post-processing workflow. That connection keeps each LiDAR mapping requirement close to the payload, acquisition record and final terrain products.

A$290 / hourBlueCap client post-processing rate

In-house control avoids unnecessary third-party training, data adaptation and custom integration hours.

BlueCap cloud processing infrastructure used for automated survey workflows
BlueCap-controlled cloud workflow
  1. 01
    Field record

    Acquire and preview

    Flights record point clouds, telemetry and QA while the browser preview shows acquisition progress.

  2. 02
    Automated processing

    Filter, align and tile

    Flight strips are stitched with 20 m tile overlaps on a multi-node CPU cluster; about four hours is typical for one full flying day.

  3. 03
    Product generation

    Build terrain products

    DTM, DSM, CHM, intensity and obstacle layers are generated, classified and quality controlled.

  4. 04
    Controlled delivery

    Package the project

    Agreed formats, metadata, coordinate reference system and vertical datum are checked for GIS, engineering or geophysical use.

Delivery package

From raw record to usable terrain products

Formats, coordinate reference system, vertical datum and tile structure are agreed for the client workflow before processing is finalised.

01

Acquisition record

  • Real-time Foxglove browser preview
  • Raw MCAP logs — ~24 topics and up to 2 TB/day
  • ArduPilot .BIN files and mission metadata
02

Point cloud and web

  • Classified LAS/LAZ 1.4 point cloud
  • EPT web tiles for Entwine/Potree
  • Standard 1 × 1 km tiles or alternative sizes
03

Terrain surfaces

  • Bare-earth DTM GeoTIFF with vegetation removed
  • Surface DSM and canopy-height CHM GeoTIFF
  • Intensity rasters, tiles and QA layers
04

Planning and reference

  • Powerline, pole, tower, building and tree-crown obstacle vectors
  • ArduPilot terrain tiles at 0.5–1.0 m GSD
  • Project EPSG plus agreed ellipsoid or geoid vertical datum
BlueCap Survey Portal powerline clearance review showing measured obstacle heights along the flown trajectory
Obstacle layers in use: the Portal's powerline-clearance review checks measured obstacle heights against the flown trajectory — the same layers delivered to the client.

Evidence, project risk and commercial value

Technical review should start with measured data — the point cloud, terrain models, flight-path record and QA — rather than one headline scanner specification.

BlueCap LiDAR point-cloud evidence used for technical project review
Review the datanot one headline specification
Point cloud · terrain model · flight path · QA
Technical review pack

Five artefacts that make performance reviewable

Each item answers a different technical question before a client commits to a larger programme.

  1. 01

    Point-cloud screenshot and cross-section

    Canopy penetration, ground returns and surface structure.

    Pilot datasets · supplied on request
  2. 02

    Bare-earth DTM and canopy DSM sample

    Terrain-model quality for drape planning and magnetic correction.

    Prepared for the project area and datum
  3. 03

    Obstacle vector example

    Detection of powerlines, towers, buildings and tall vegetation.

    Format matched to mission-planning workflow
  4. 04

    Flight path and footprint overlay

    Actual trajectory, instantaneous footprint and accumulated coverage geometry.

    Used for internal planning and client review
  5. 05

    Sample LAS/LAZ or GeoTIFF tile

    Independent review by client geophysicists, GIS or engineering teams.

    Selected projects · data agreement required
Decision layer

Commercial impact for exploration projects

Remote-project cost is driven by flyable hours, deployed crew days and repeat visits — not only the sensor day rate.

Commercial riskHow the service respondsInvestor / client relevance
01Short weather and airspace windowsFlight-plan modelling combines footprint, speed, overlap, terrain and required density.More productive field days and lower standby cost.
02Incorrect magnetic target positioningBetter drape planning reduces sensor-AGL-driven anomaly distortion.Lower risk of drilling decisions based on flight-geometry artefacts.
03Repeat surveysIntegrated planning resolves terrain and acquisition constraints before magnetic flying.Fewer re-flights and cleaner handover to interpretation teams.
04Contractor handover gapsOne team owns the payload, terrain products, acquisition workflow and delivery QA.Stronger defensibility for professional exploration programmes.
Availability

Selected projects during continued field validation, prioritising dense canopy, steep relief and high line-density cases.

Pricing basis

Scoped by site area, relief, vegetation, acquisition pattern and deliverables; bundled LiDAR + Magnetics pricing is available.

Review the BlueCapLidar® payload architecture →

Project enquiry

BlueCap Starts with the Survey Decision

We use the Portal to turn your survey polygon into a quote-ready BlueCap project, review DEM-aware 2D and 3D mission design, follow field acquisition, and keep processing outputs and deliverables in one client workspace.

No software subscription fee for BlueCap service projects.

Inside the Portal01 / 07
BlueCap Portal map showing a large survey polygon divided into coordinated routes for four aircraft sorties
Multi-aircraft survey allocationDivide a large survey area into coordinated aircraft sorties and review the complete route geometry on the map.