WIRELESS_REGDOMAIN_INCORRECT
Viewing this guide for
Applicable alarms (1)
WIRELESS_REGDOMAIN_INCORRECT
Likely outcomes — click to expand
Based on 4,609 missions where this alarm fired in the last 90 days as of 2026-10-13
Grounding vs discrepancy (of 134 ZERP issues filed on these missions)
Frequently replaced parts
| Part | P/N | Removals |
|---|---|---|
| ASSM, FLIGHT COMPUTER, FORE, ZIP, P2 | 48408 | 12 |
| ASSM, FLIGHT COMPUTER, AFT, ZIP, P2 | 48409 | 11 |
| DOCKING FIN WINCH ASSY, ZIP, P2 | 24084 | 11 |
| COATED PCBA, TAIL NODE, ZIP, P2 | 29407 | 3 |
| HOVER AND SERVO FWD PORT(LH) FLEX HARNESS, ZIP, P2 | 0121833 | 1 |
Frequently co-occurring alarms (% of the 4,609 missions above)
Aggregated from fleet operations and refreshed daily. Individual outcomes may vary by site and configuration.
Background
Section titled “Background”WIRELESS_REGDOMAIN_INCORRECT means the Aircraft has not confirmed the WiFi regulatory domain as US.
This guide first rules out higher-priority V2V receive and broadcast reception alarms.
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
power-cycle-the-aircraft["<small><b>Step 1</b></small><br/>Action: Power cycle the Aircraft. For steps, ..."]
run-mission-preflight-again["<small><b>Step 2</b></small><br/>Action: Run mission preflight once more."]
what-happened-after-preflight-retry{"<small><b>Step 3</b></small><br/>Question: After the power cycle and preflight r..."}
use-rx-v2v-absent-guide["<small><b>Step 4</b></small><br/>Action: Use the RX_V2V_ABSENT guide/topics..."]
use-broadcast-reception-guide["<small><b>Step 5</b></small><br/>Action: Use the missing or insufficient broa..."]
troubleshoot-actual-preflight-failure["<small><b>Step 6</b></small><br/>Action: Troubleshoot the alarm that actually ..."]
escalate-regdomain-after-ruleouts{{"<small><b>Step 7</b></small><br/>Escalation: Escalate to P2 Embedded Linux On Call..."}}
return-to-service["<small><b>Step 8</b></small><br/>Action: The alarm did not reproduce after the..."]
power-cycle-the-aircraft --> run-mission-preflight-again
run-mission-preflight-again --> what-happened-after-preflight-retry
what-happened-after-preflight-retry -->|Preflight Failure: WIRELESS...| escalate-regdomain-after-ruleouts
what-happened-after-preflight-retry -->|Preflight Failure: RX_V2V_A...| use-rx-v2v-absent-guide
what-happened-after-preflight-retry -->|Preflight Failure: V2V_SELF...| use-broadcast-reception-guide
what-happened-after-preflight-retry -->|Preflight Failure: V2V_SELF...| use-broadcast-reception-guide
what-happened-after-preflight-retry -->|Preflight Failure: None of ...| troubleshoot-actual-preflight-failure
what-happened-after-preflight-retry -->|No Preflight Failure| return-to-service
style power-cycle-the-aircraft fill:#dcfce7,stroke:#22c55e,color:#14532d
style run-mission-preflight-again fill:#dcfce7,stroke:#22c55e,color:#14532d
style what-happened-after-preflight-retry fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style use-rx-v2v-absent-guide fill:#dcfce7,stroke:#22c55e,color:#14532d
style use-broadcast-reception-guide fill:#dcfce7,stroke:#22c55e,color:#14532d
style troubleshoot-actual-preflight-failure fill:#dcfce7,stroke:#22c55e,color:#14532d
style escalate-regdomain-after-ruleouts fill:#fef3c7,stroke:#f59e0b,color:#78350f
style return-to-service fill:#dcfce7,stroke:#22c55e,color:#14532d Hover or focus a block to preview it. Select the block to keep the preview open.
1 action
Power cycle the Aircraft. For steps, see Power Cycle Aircraft.
2 action
Run mission preflight once more.
3 question
After the power cycle and preflight retry, what happened? Pick the first option that applies.
4 action
5 action
Use the missing or insufficient broadcast receptions guide before continuing with
WIRELESS_REGDOMAIN_INCORRECT. 6 action
Troubleshoot the alarm that actually caused the preflight failure before returning the Aircraft to service.
7 escalation
Escalate to P2 Embedded Linux On Call. Include the mission ID and use WiFi 802.11 V2V Troubleshooting: WIRELESS_REGDOMAIN_INCORRECT as the starting point for troubleshooting. If a compute board consistently cannot scan WiFi or does not have WiFi firmware come up, the repair may be to replace the compute board and/or escalate to P2 Avionics Hardware On Call.
8 action
The alarm did not reproduce after the power cycle and preflight retry. The Aircraft may return to service.
Resolution note
This plaintext block is ready to paste into the Resolution Note field on the ZERP issue you're working. The permalink below gives engineering review access to the full step-by-step timeline including any back-navigation; share it if the case needs a deeper look.
Permalink:
Session is too large to fit in a URL. Use Download session JSON to share the timeline out-of-band.
Did this guide help you get unblocked?
Open suggestions
There are no open suggestions.
Open pull requests
There are no open pull requests.