Making sense of a reported sighting
A station, training ground or fixed operational site can contribute a local receiver. The resulting map and recorded activity can support a briefing or a later review, with responsibility for operational decisions remaining in the service’s established systems.
A team receives a report of a drone near a fixed site. The reviewer checks the time and place on Layer400, opens the received trail and looks at nearby reported aircraft where relevant.
If a supported Remote ID emergency status is received, the map highlights that report for inspection. Following the event, eligible playback can help the team review the received sequence alongside its own operational log.
Questions worth answering
- What was received near the reported location and time?
- Is there a reported emergency status or relevant aircraft context?
- Which recorded observations can support the later review?
The features that fit this setting.
Notice a reported drone emergency
Supported received Remote ID emergency statuses are highlighted on the map, with optional notices for activity outside the current view. The status is broadcast information, not an independently verified incident.
Depends on received broadcasts · reports are not independently verifiedExplore this feature →Inspect aircraft and drone context together
Review suitable reported positions and projected separation, keeping estimates distinct from observations.
When suitable reports are availableExplore this feature →Support a structured debrief
Replay retained activity with eligible access and compare the recorded sequence with your own incident timeline.
Sign-in and history entitlement applyExplore this feature →Explore an approved data workflow
Request the specific live or history scopes needed for an agreed organisational integration.
Approval and scope limits applyExplore this feature →Set an area. Choose what brings you back.
Begin with a fixed station, training area or other agreed location. Choose a named area and a designated reviewer rather than assuming a receiver installation creates a mobile incident network.
Available area notifications can draw a reviewer’s attention to received activity around a fixed site. Match channels and quiet-hour settings to the agreed review workflow and test them before use.
- Choose the place. Use the map’s area-alert entry to select your centre and radius, then name the saved area in your account.
- Choose the activity. Review the rules available to your account and enable the ones relevant to this place.
- Choose the channel. Configure an available email, browser push or webhook channel, check quiet hours and send a test.
- Open the observation. Use the event timeline’s Live or Playback link as available to inspect what triggered your attention.
Area alerts · limited rollout. Account and channel availability apply. Email, opt-in browser push and signed webhooks have separate delivery states; notification timing depends on the rule, quiet hours and delivery channel. Check your account’s options and send a test before building a routine around notifications.
Explore your account’s area-alert options →
An area selects relevant received activity. It does not change the receiver’s listening range or create a flight restriction.
Give the receiver a useful home.
- Define the information requirement with the team that will assess the observations, including how it records timestamps and track references.
- Plan a fixed-site receiver installation with dependable power, networking and an identified equipment owner.
- Agree a practical acceptance review covering the map, receiver reporting and any enabled notifications or separately approved integration.
Questions for this setting.
Is reported emergency status the same as a confirmed emergency?
No. Layer400 highlights supported emergency status received in a drone broadcast. The responsible team must assess that report alongside its other information.
Can this support a vehicle-mounted deployment?
The public receiver release is for fixed sites. Moving platforms require a separately scoped deployment discussion; they are not assumed by this guide.