
Airfield Pavement Condition Assessment by Drone
Drone condition assessment for runway, taxiway and apron pavement. Distress classified to ASTM D6433 categories, a PCI proxy per section, a ranked…
Drone and ground imagery over a window of one to two hours, turned into a map of every detected defect, a condition rating per section, a priority list and a 3D model of the surface. Report within two weeks.

A road department knows which streets are bad. What it usually cannot produce on demand is the evidence, in the same form, for the whole network, updated this year.
The survey exists to replace an opinion with a record. Three outcomes carry that, and each can be checked on the day it is delivered.
Cracks, potholes and areas of surface loss come back as objects with a position, a type and an extent, not as a description in a paragraph.
Each section carries a rating on a 0 to 100 scale together with the defects that produced it, and the network carries an overall figure.
Sections are ordered so that the ones needing attention first appear first, and each carries the reason it sits where it does.
The fourth deliverable, the 3D model of the surveyed surface, is what makes the second survey worth more than the first. It fixes the geometry the next capture is compared against, so change becomes measurable rather than remembered.
What the survey does not produce is a repair design, a bill of quantities or a cost estimate. Those belong to your designer. A condition survey that quietly becomes a works specification is one nobody can hold to account.
Each deliverable with what it contains and who owns it, including the parts that are deliberately outside the scope.
Every detected crack, pothole, patch and area of surface loss, with position, type and extent.
A rating on the 0 to 100 scale for each agreed section and for the network as a whole, with the defect densities behind it.
Sections ordered by the attention they need, each with the defects that place it there.
A model of the surveyed surface in a standard exchange format, usable without our software.
The defect inventory and section ratings as tabular data with coordinates, in the format your system reads.
One to two hours for the agreed area, drone and ground imagery, no closure booked beyond that window.
Arranged before the date where local rules require a permit for the drone flight.
The network split into sections, agreed before capture and reused on later surveys.
Not included. The survey reports condition, it does not specify works.
Not included. Bearing capacity needs coring or deflection testing.
Not included. Signs, markings and drainage assets are a separate inventory task.
You send the streets to survey and, if you have one, your centreline layer. We agree the section split, the export format and the capture windows. Output is a scope note with a price. Without an agreed section split the survey does not start, because a rating against boundaries nobody accepts cannot be defended.
Flight permissions are arranged where local rules need them, and the capture is planned from the road geometry and the camera optics so that coverage is computed rather than assumed. Output is a validated plan and confirmed dates.
Drone and ground imagery over one to two hours for the agreed area, with traffic moving through it. Larger networks are captured across several windows. If weather stops a window, that window is reflown rather than the plan rebuilt.
Imagery goes through the vision pipeline, which segments the surface and classifies each defect by type and severity. Detections below the confidence floor are held for human review rather than dropped.
Defect density is computed inside each agreed section, converted to a condition figure on the 0 to 100 scale, and the sections are ordered into the priority list. The 3D model is built from the same capture.
Map, ratings, priority list, 3D model and export land together within two weeks of capture, and we walk your engineer through the sections at the top of the list. Anything disputed is re-examined against the retained imagery.

The part of this service worth understanding before buying it is the detector, because everything downstream is arithmetic on what it finds.
Images are passed through a self-supervised vision transformer backbone. The model was trained without labels on a very large image corpus, and it turns every small patch of an image into a high-dimensional embedding that carries texture and structure rather than a category name. Lightweight heads sit on top of those embeddings and do the specific jobs: segmenting a crack from the surface around it, separating a pothole from a shadow, telling longitudinal cracking apart from a sealed joint, and grading alligator cracking by how far the pattern has developed. The method page for the backbone is DINOv3 for infrastructure surface analysis , and it goes into the architecture properly.
What matters operationally is not the architecture but the consequence. A frozen backbone with trained heads applies the same decision boundary to every metre of every survey. A crew driving a network applies a threshold that drifts with fatigue, weather and who is in the vehicle. The machine is not more perceptive than a good engineer standing on the road. It is more consistent than the same engineer on the twentieth kilometre, and consistency is what a time series needs.
The rating built on those detections is a proxy for a Pavement Condition Index , and it should be read as one. The idea is the same: distress of a given type, severity and density pulls a score down from 100. The derivation is not the same, because ASTM D6433 asks an inspector to walk sample units and read deduct curves by hand. Where a funding programme names the standard, the formal survey is what satisfies it. Where the question is which sections to treat first, this answers it across the whole network rather than across a sample.
The 3D model is the other half of the record. It fixes the geometry of the surveyed surface, which is what allows a survey next year to report change rather than a second opinion. Feeding both into a pavement management system is the point of the exercise, and the export format is agreed before capture for exactly that reason.
No rate is published, because the work scales with the network rather than with a line item.
Four things can stop a survey or weaken its result, and each has an owner.
Standing water, snow and heavy leaf cover hide the surface from a camera. The affected window is recaptured rather than rated through the obstruction, and this is the most common reason a date moves.
Parked cars, overhanging trees and narrow streets with tall buildings block a view from above. This is why ground imagery is in scope for some networks and not others, and it is decided at scoping rather than discovered on the day.
Urban drone flight is regulated, and a permit that does not arrive is a date that does not happen. That work sits with us, but it depends on the authority granting it.
A rating describes a defined stretch of road. If section boundaries move between surveys, the comparison breaks. Boundaries are frozen at scoping, and changing them later is a decision with a cost rather than an edit.

Drone condition assessment for runway, taxiway and apron pavement. Distress classified to ASTM D6433 categories, a PCI proxy per section, a ranked…

Drone-based runway and taxiway pavement scanning. Cracks, spalls, joint condition and FOD captured at a known ground resolution, every finding…

Automated drone inspection uses pre-programmed flight paths, computer vision, and AI analysis to survey infrastructure assets including runways,…
Send the streets you want surveyed and your centreline layer if you have one. That is enough to scope. A written scope note and a price come back within two working days, and the scope note is not binding until you accept it.