Establish a usable observation
Separate a witness report, received identifier, physical radar track and optical observation. Each contributes different evidence to the assessment.
Airport drone detection that connects current observations, source-aware assessment and coordinated response. Design the sensing and the operational handoff together.

A report of a drone near an airport raises immediate questions: where was it observed, is the track current, which sensor supports it and who needs the information? The airport must also account for authorized UAS operations and other low-altitude activity. Detection is useful when it gives the response team enough context to assess the event through the airport’s established process.
AirSentinel combines supported RF observations with Atlas intelligence and optional radar, optical and ADS-B inputs. The objective is a clearer, shared picture for airport operations and authorized partners—not an automatic operational decision based on an unidentified map symbol.
Separate a witness report, received identifier, physical radar track and optical observation. Each contributes different evidence to the assessment.
Connect the operations desk and authorized responders to the same event. Keep data timing and available location information visible in the handoff.
Optional dual-band ADS-B reception adds equipped aircraft for situational awareness. Aircraft without receivable ADS-B transmissions remain outside that input.
Airport siting involves more than reception range. Evaluate approaches, buildings, terrain, sensor views and the installation’s relationship to airport communications and navigation systems. RF reception, radar and optical coverage each require their own assessment; no one layer identifies intent.
Coordinate a proposed airport deployment with the relevant airport stakeholders and aviation authority. FAA guidance addresses electromagnetic compatibility, installation review and operational effects, and describes a coordinated UAS response plan for Part 139 airports. AirSentinel data should support that plan and its designated decision makers. Read the FAA airport guidance.
Explore RF, radar and optical integrationDefine who monitors, validates, communicates and makes operational decisions before a detection occurs.
Review source, current location, movement and available identification; seek complementary observations where appropriate.
Provide the designated airport and authorized public-safety teams with a consistent event picture.
Retain available history to understand the event, evaluate coverage and inform the airport’s return-to-normal process.
Atlas can ingest compatible third-party sensors and export configured AMS and fused data into the airport’s preferred C2 or intelligence platform. Specify track identifiers, timestamps, coordinate conventions and data-age handling at each interface. Optional ADS-B is an additional awareness source; the system should not be presented as a replacement for air traffic control or as certified separation assurance.
Explore Atlas interoperabilityAgree the acceptance criteria before the deployment, then exercise the full workflow.
Read the evaluation guideNo. Sensors provide observations. Airport teams assess their relevance and act through established procedures and responsibilities.
No. It receives compatible transmissions from equipped aircraft within reception coverage. It complements the airspace picture and does not provide a complete surveillance or separation service.
Discuss the sensing, coordination and validation your airport needs.