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.

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.
Aircraft-scale LiDAR coverage from a drone survey system
Four planning numbers connect field capacity, parallel deployment, point density and processing turnaround.
9,000–54,000 ha across an eight-hour field day, depending on acquisition pattern and project conditions.
One to three long-endurance BlueCapHeli® systems can acquire independent blocks in parallel.
The project range runs from productive single-pass acquisition to a dual-orthogonal canopy survey.
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.

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
- 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
Lower project cost. Centimetre-level terrain accuracy.
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.

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.
Indicative one-system planning reference before the project-specific review of terrain, mobilisation, classification and deliverables.
Indicative like-for-like planning scenario for a current crewed-aircraft quotation. It is not presented as a fixed market tariff.
Replace the scenario with a current aircraft quotation and compare the same density, accuracy, ground-return, classification and mobilisation scope.
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.
- 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.
- 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.
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.
Productivity changes the commercial result.
Long-endurance sorties keep useful acquisition time high.
Less repositioning and fewer return-to-base cycles across the block.
The 330 km² reference block is planned across two productive field days.
Approximately 165 km²/day on the comparison basis.
BlueCap owns acquisition, processing, QA and delivery as one system.
Designing for area, density and accuracyTwo patterns. One project trade-off.

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.
- Flight pattern
- Turns and overlap
- Terrain and canopy
- Density and QA
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.
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.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
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.
| Survey block | System | Flight time | Field days | Flight cycles and field service |
|---|---|---|---|---|
| 10 × 10 km100 km² | BlueCapLidar®carried by BlueCapHeli® | 4h 30m | 1 | 2flight legs · 1 refuel |
| Zenmuse L2carried by DJI Matrice 300 RTK | 77h | 13 | 165battery cycles | |
| 20 × 20 km400 km² | BlueCapLidar®carried by BlueCapHeli® | 18h | 3 | 8flight legs · 7 refuels |
| Zenmuse L2carried by DJI Matrice 300 RTK | 307h 30m | 51 | 659battery cycles | |
| 30 × 30 km900 km² | BlueCapLidar®carried by BlueCapHeli® | 40h | 5 | 16flight legs · 15 refuels |
| Zenmuse L2carried by DJI Matrice 300 RTK | 692h | 115 | 1483battery 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.

- 01
Map the surface
BlueCapLidar® records a 285 × 160 m instantaneous window at 100 m AGL and builds the terrain and obstacle model.
- 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.
- 03
Control the sensor
BlueCapWinch® actively manages the QuSpin QTFM Gen 2 while maintaining more than 20 m carrier-to-sensor separation.
- 04
Fly and verify
Speed control and sensor-AGL QA follow the calculated surface to target a 1 m terrain-following corridor before interpretation.
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.

- 01RepeatabilityFour locations
The response was repeated across separate sites rather than inferred from one location.
- 02Horizontal controlOne fixed point
The carrier held horizontal position while only sensor-to-ground distance changed.
- 03Vertical 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.
- 04Airframe separationMore than 20 m
The magnetic sensor never came closer than 20 m to the BlueCapHeli® airframe.
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.
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.
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.
In-house control avoids unnecessary third-party training, data adaptation and custom integration hours.

- Field record
Acquire and preview
Flights record point clouds, telemetry and QA while the browser preview shows acquisition progress.
- 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.
- Product generation
Build terrain products
DTM, DSM, CHM, intensity and obstacle layers are generated, classified and quality controlled.
- Controlled delivery
Package the project
Agreed formats, metadata, coordinate reference system and vertical datum are checked for GIS, engineering or geophysical use.
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.
Acquisition record
- Real-time Foxglove browser preview
- Raw MCAP logs — ~24 topics and up to 2 TB/day
- ArduPilot .BIN files and mission metadata
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
Terrain surfaces
- Bare-earth DTM GeoTIFF with vegetation removed
- Surface DSM and canopy-height CHM GeoTIFF
- Intensity rasters, tiles and QA layers
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

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.

Five artefacts that make performance reviewable
Each item answers a different technical question before a client commits to a larger programme.
Point-cloud screenshot and cross-section
Canopy penetration, ground returns and surface structure.
Pilot datasets · supplied on requestBare-earth DTM and canopy DSM sample
Terrain-model quality for drape planning and magnetic correction.
Prepared for the project area and datumObstacle vector example
Detection of powerlines, towers, buildings and tall vegetation.
Format matched to mission-planning workflowFlight path and footprint overlay
Actual trajectory, instantaneous footprint and accumulated coverage geometry.
Used for internal planning and client reviewSample LAS/LAZ or GeoTIFF tile
Independent review by client geophysicists, GIS or engineering teams.
Selected projects · data agreement required
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.
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.





