DISTRO_A_TO_HOVER_SF_ETHERNET_LINK
Viewing this guide for
graph TD
select-aircraft-variant{"<small><b>Step 1</b></small><br/>Question: Which aircraft variant are you troubl..."}
ev2-background["<small><b>Step 2</b></small><br/>Action: Use this maintenance guide to locate ..."]
ev3-background["<small><b>Step 3</b></small><br/>Action: Use this maintenance guide to locate ..."]
inspect-distro-a-hover-sf-flex{"<small><b>Step 4</b></small><br/>Question: Inspect the Distro to Hover-SF flex, ..."}
swap-distro-a-hover-sf-flex["<small><b>Step 5</b></small><br/>Action: Swap Distro to Hover-SF flex and proc..."]
inspect-hover-sf{"<small><b>Step 6</b></small><br/>Question: Inspect the Hover-SF motor especiall..."}
swap-hover-sf["<small><b>Step 7</b></small><br/>Action: Swap the Hover Stbd Fwd motor, procee..."]
inspect-distro-a{"<small><b>Step 8</b></small><br/>Question: Inspect the distro board especially ..."}
swap-distro["<small><b>Step 9</b></small><br/>Action: Swap the distro board, proceed to nex..."]
inspection-findings{"<small><b>Step 10</b></small><br/>Question: Was anything swapped due to damage?"}
swap-flex-anyway["<small><b>Step 11</b></small><br/>Action: Invisible damage is most likely in th..."]
is-the-issue-resolved{"<small><b>Step 12</b></small><br/>Question: Is the issue resolved?"}
the-aircraft-may-return-to-service("<small><b>Step 13</b></small><br/>Reference: The Aircraft may return to service.")
escalate-to-p2-avionics-hardware-on-call{{"<small><b>Step 14</b></small><br/>Escalation: Escalate to P2 Avionics Hardware On C..."}}
select-aircraft-variant -->|EV2| ev2-background
select-aircraft-variant -->|EV3| ev3-background
ev2-background --> inspect-distro-a-hover-sf-flex
ev3-background --> inspect-distro-a-hover-sf-flex
inspect-distro-a-hover-sf-flex -->|YES| swap-distro-a-hover-sf-flex
inspect-distro-a-hover-sf-flex -->|NO| inspect-hover-sf
swap-distro-a-hover-sf-flex --> inspect-hover-sf
inspect-hover-sf -->|YES| swap-hover-sf
inspect-hover-sf -->|NO| inspect-distro-a
swap-hover-sf --> inspect-distro-a
inspect-distro-a -->|YES| swap-distro
inspect-distro-a -->|NO| inspection-findings
swap-distro --> inspection-findings
inspection-findings -->|YES| is-the-issue-resolved
inspection-findings -->|NO| swap-flex-anyway
swap-flex-anyway --> is-the-issue-resolved
is-the-issue-resolved -->|Yes| the-aircraft-may-return-to-service
is-the-issue-resolved -->|No| escalate-to-p2-avionics-hardware-on-call
style select-aircraft-variant fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style ev2-background fill:#dcfce7,stroke:#22c55e,color:#14532d
style ev3-background fill:#dcfce7,stroke:#22c55e,color:#14532d
style inspect-distro-a-hover-sf-flex fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style swap-distro-a-hover-sf-flex fill:#dcfce7,stroke:#22c55e,color:#14532d
style inspect-hover-sf fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style swap-hover-sf fill:#dcfce7,stroke:#22c55e,color:#14532d
style inspect-distro-a fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style swap-distro fill:#dcfce7,stroke:#22c55e,color:#14532d
style inspection-findings fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style swap-flex-anyway fill:#dcfce7,stroke:#22c55e,color:#14532d
style is-the-issue-resolved fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style the-aircraft-may-return-to-service fill:#f3e8ff,stroke:#a855f7,color:#581c87
style escalate-to-p2-avionics-hardware-on-call fill:#fef3c7,stroke:#f59e0b,color:#78350f Hover or focus a block to preview it. Select the block to keep the preview open.
1 question
Which aircraft variant are you troubleshooting?
2 action
Use this maintenance guide to locate the Ethernet harness and connectors that should be inspected for this link fault.
Please read the checklist carefully, refer to the layout diagram and then proceed with the debugging steps below.
Make sure to check Zerp for any recently replaced HW. If any LRU was recently replaced, proceed with inspection or replacement of remaining LRUs in the list.
LRUs to check:
- Distro-A to Hover-SF flex harness.
- Hover-SF board and connector.
- Distro board and connector.
Please read the checklist carefully, refer to the layout diagram and then proceed with the debugging steps below.
Make sure to check Zerp for any recently replaced HW. If any LRU was recently replaced, proceed with inspection or replacement of remaining LRUs in the list.
LRUs to check:
- Distro-A to Hover-SF flex harness.
- Hover-SF board and connector.
- Distro board and connector.
3 action
Use this maintenance guide to locate the Ethernet harness and connectors that should be inspected for this link fault.
Please read the checklist carefully and then proceed with the debugging steps below.
Make sure to check Zerp for any recently replaced HW. If any LRU was recently replaced, proceed with inspection or replacement of remaining LRUs in the list.
LRUs to check:
- Distro-A to Hover-SF flex harness.
- Hover-SF motor and connector.
- Distro board and connector.
Please read the checklist carefully and then proceed with the debugging steps below.
Make sure to check Zerp for any recently replaced HW. If any LRU was recently replaced, proceed with inspection or replacement of remaining LRUs in the list.
LRUs to check:
- Distro-A to Hover-SF flex harness.
- Hover-SF motor and connector.
- Distro board and connector.
4 question
Inspect the Distro to Hover-SF flex, is there any visible damage?
5 action
Swap Distro to Hover-SF flex and proceed to the next inspection steps.
6 question
Inspect the Hover-SF motor (especially the connector), is there any visible damage?
7 action
Swap the Hover Stbd Fwd motor, proceed to next inspection steps.
8 question
Inspect the distro board (especially the relevant connector), is there any visible damage?
9 action
Swap the distro board, proceed to next steps.
10 question
Was anything swapped due to damage?
11 action
Invisible damage is most likely in the flex. Swap the flex (make sure the replacement has the foam covering). Notify and ship the removed flex to Avionics-HW-on-call POC (and include Joseph Katz). Try a redocking flight.
12 question
Is the issue resolved?
13 reference
The Aircraft may return to service.
14 escalation
Escalate to P2 Avionics Hardware 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.