Airframe classification
Class and confidence, on-device, offline.
Defense · Awareness · Whitepaper
Detect. Classify. Advise.
NavTrax is a defensive-posture system. It detects and classifies unmanned aircraft, estimates intent, and recommends legal countermeasures with an assessed probability of success. It does not jam, spoof or engage anything. That boundary is architectural, not a policy statement.
01 / Problem statement
What we are designing against.
Counter-UAS capability presents a genuine dilemma for a software vendor.
Detection without classification is noise. An RF signature is not a threat. A hobby airframe, a survey contractor and a hostile ISR platform generate similar returns, and an alert that cannot distinguish them will be ignored inside a week.
Effect is legally constrained. Jamming, spoofing and kinetic engagement are restricted to specific authorities in specific circumstances in every jurisdiction we operate in. Software that quietly offers them creates liability for the operator, not for us.
Automation invites escalation. An automated engagement chain removes the human judgment that is the only thing distinguishing a defensive action from an unlawful one.
02 / Mechanism
The design, stated so it can be evaluated.
- RF and BLE signature classification
- On-device classification against a signature set, producing an airframe class and a confidence rather than a binary alert.
- Intent estimation
- Track behavior — loiter, transit, orbit, approach — assessed against the protected area to produce an intent estimate with its own confidence.
- Legal countermeasure advisory
- The system recommends measures that are lawful for the operator in their jurisdiction: exclusion radius, evacuation of an exposed position, concealment, or referral to an authority that holds the relevant powers.
- Assessed probability
- Each recommendation carries an estimated probability of success, because a recommendation without one is a guess in a uniform.
- Human authorization gate
- Any action with a physical effect requires a signed human authorization token with a time-to-live and an audit entry. There is no automation path around it.
- Architectural boundary
- NavTrax has no effector interface. It cannot jam, spoof or engage, because there is nothing in the system to do so with. This is a deliberate absence.
03 / Capabilities
What is actually delivered.
Intent estimation
From track behavior against the protected area.
Exclusion radius recommendation
Drawn on the operating picture.
Concealment and evacuation advice
Terrain-derived, from the offline DEM.
Referral to authority
With the packet that authority will need.
Signed human authorization
TTL and audit entry on every gated action.
No effector interface
Stated as a capability boundary, not a roadmap item.
04 / Reference
| Function | NavTrax | Note |
|---|---|---|
| Detect and classify | Yes | On-device, RF and BLE signatures |
| Estimate intent | Yes | From track behavior, with confidence |
| Recommend exclusion radius | Yes | Advisory, drawn on the picture |
| Recommend concealment | Yes | Terrain-derived |
| Refer to authority | Yes | With a prepared packet |
| Jam or spoof | No | No effector interface exists |
| Kinetic engagement | No | No effector interface exists |
| Automated engagement | No | Human authorization is mandatory |
05 / Process
Traced, node by node.
Advisory by architecture.
Counter-UAS awareness is Enterprise, and the capability boundary above is contractual.