Droid Paraland System Terminal or Failed
Viewing this guide for
Applicable alarms (5)
0x00100196ZIP_EXECUTIVE_V4_DROID_PARALAND_SYSTEM_TERMINAL0x001001A8ZIP_EXECUTIVE_V4_DROID_PARALAND_SYSTEM_FAILEDZIP_EXECUTIVE_CODE_DROID_PARALAND_SYSTEM_TERMINAL
Likely outcomes — click to expand
Based on 0 missions where this alarm fired in the last
90 days
(for 0x00100196) as of 2026-10-13
Aggregated from fleet operations and refreshed daily. Individual outcomes may vary by site and configuration.
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
did-the-alarm-occur-during-a-dlb{"<small><b>Step 1</b></small><br/>Question: Did the alarm occur during a Droid Le..."}
complete-the-dlb-work-orders["<small><b>Step 2</b></small><br/>Action: Complete the work orders listed below..."]
use-the-droid-safety-status-vs-droid-exe{"<small><b>Step 3</b></small><br/>Question: Use the “Droid Safety Status vs. Droi..."}
this-is-not-a-problem-and-the-zip-can-b["<small><b>Step 4</b></small><br/>Action: This is not a problem and the zip can..."]
use-the-droid-safety-status-alarms-bara{"<small><b>Step 5</b></small><br/>Question: Use the “Droid Safety Status Alarms” ..."}
follow-the-relevant-troubleshooting-gui("<small><b>Step 6</b></small><br/>Reference: Follow the relevant troubleshooting g...")
use-the-droid-squib-control-status-alar{"<small><b>Step 7</b></small><br/>Question: Use the “Droid Squib Control Status A..."}
follow-the-relevant-troubleshooting-g-2("<small><b>Step 8</b></small><br/>Reference: Follow the relevant troubleshooting g...")
use-the-droid-mission-planner-mission-s{"<small><b>Step 9</b></small><br/>Question: Use the Droid Mission Planner State ..."}
this-is-not-a-problem-and-the-zip-can-2["<small><b>Step 10</b></small><br/>Action: This is not a problem and the zip can..."]
escalate-to-p2-droid{{"<small><b>Step 11</b></small><br/>Escalation: Escalate to P2 Droid On Call"}}
did-the-alarm-occur-during-a-dlb -->|Yes| complete-the-dlb-work-orders
did-the-alarm-occur-during-a-dlb -->|No| use-the-droid-safety-status-vs-droid-exe
use-the-droid-safety-status-vs-droid-exe -->|Yes| this-is-not-a-problem-and-the-zip-can-b
use-the-droid-safety-status-vs-droid-exe -->|No| use-the-droid-safety-status-alarms-bara
use-the-droid-safety-status-alarms-bara -->|Yes| follow-the-relevant-troubleshooting-gui
use-the-droid-safety-status-alarms-bara -->|No| use-the-droid-squib-control-status-alar
use-the-droid-squib-control-status-alar -->|Yes| follow-the-relevant-troubleshooting-g-2
use-the-droid-squib-control-status-alar -->|No| use-the-droid-mission-planner-mission-s
use-the-droid-mission-planner-mission-s -->|Yes| this-is-not-a-problem-and-the-zip-can-2
use-the-droid-mission-planner-mission-s -->|No| escalate-to-p2-droid
style did-the-alarm-occur-during-a-dlb fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style complete-the-dlb-work-orders fill:#dcfce7,stroke:#22c55e,color:#14532d
style use-the-droid-safety-status-vs-droid-exe fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style this-is-not-a-problem-and-the-zip-can-b fill:#dcfce7,stroke:#22c55e,color:#14532d
style use-the-droid-safety-status-alarms-bara fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style follow-the-relevant-troubleshooting-gui fill:#f3e8ff,stroke:#a855f7,color:#581c87
style use-the-droid-squib-control-status-alar fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style follow-the-relevant-troubleshooting-g-2 fill:#f3e8ff,stroke:#a855f7,color:#581c87
style use-the-droid-mission-planner-mission-s fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style this-is-not-a-problem-and-the-zip-can-2 fill:#dcfce7,stroke:#22c55e,color:#14532d
style escalate-to-p2-droid fill:#fef3c7,stroke:#f59e0b,color:#78350f Hover or focus a block to preview it. Select the block to keep the preview open.
1 question
Did the alarm occur during a Droid Left Behind (DLB) event?
2 action
Complete the work orders listed below:
- Aircraft: Complete the work order for the relevant aircraft version:
- EV2: #195: Inspect Aircraft after Droid Left Behind (DLB)
- EV3: #662: Inspect Aircraft after Droid Left Behind (DLB)
- Droid: Complete the following work orders in order:
1. #1169: Reset Droid after DLB
2. #1196: Offload Droid Logs after DLB
3. #1302: Perform Droid GNSS Status Test after DLB
- Aircraft: Complete the work order for the relevant aircraft version:
- EV2: #195: Inspect Aircraft after Droid Left Behind (DLB)
- EV3: #662: Inspect Aircraft after Droid Left Behind (DLB)
- Droid: Complete the following work orders in order:
1. #1169: Reset Droid after DLB
2. #1196: Offload Droid Logs after DLB
3. #1302: Perform Droid GNSS Status Test after DLB
3 question
Use the “Droid Safety Status vs. Droid executive vertical safety status” baraza template to determine if the droid executive vertical comms safety_status momentarily flickers to FAILURE but the droid safety_status parachute_state stays armed. See image below for an example. Do you observe this behavior?
NOTE: Add some padding if the plot is empty.
An example of the droid executive vertical safety_status momentairly going to failure but the droid safety status parachute state staying in ARMED with no failure
NOTE: Add some padding if the plot is empty.
An example of the droid executive vertical safety_status momentairly going to failure but the droid safety status parachute state staying in ARMED with no failure
4 action
This is not a problem and the zip can be returned to service.
5 question
Use the “Droid Safety Status Alarms” baraza template to determine if any safety status alarms were set. Were any safety status alarms set?
NOTE: Add some padding if the plot is empty.
NOTE: Add some padding if the plot is empty.
6 reference
Follow the relevant troubleshooting guide for the safety status alarm.
7 question
Use the “Droid Squib Control Status Alarms” baraza template to determine if any alarms were set. Were any alarms set? Please add some padding if the plot is empty
8 reference
Follow the relevant troubleshooting guide for the alarm.
9 question
Use the Droid Mission Planner State baraza template mission state to determine if the safety status failure occurred during stowing, indicating it was likely spurious due to electrostatic discharge (ESD)
10 action
This is not a problem and the zip can be returned to service.
11 escalation
Escalate to P2 Droid On Call
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.