EV2_TAIL_NODE_TO_HOVER_PF_ETHERNET_LINK
Viewing this guide for
graph TD
ev2-background["<small><b>Step 1</b></small><br/>Action: Use this maintenance guide to locate ..."]
inspect-distro-tail-flex{"<small><b>Step 2</b></small><br/>Question: Inspect the distro tail flex, is ther..."}
swap-distro-tail-flex["<small><b>Step 3</b></small><br/>Action: Swap the distro tail flex and proceed..."]
inspect-tail-node{"<small><b>Step 4</b></small><br/>Question: Inspect the tail node especially the..."}
swap-tail-node["<small><b>Step 5</b></small><br/>Action: Swap the tail node, proceed to next i..."]
inspect-hover-pf-flex{"<small><b>Step 6</b></small><br/>Question: Inspect the hover PF flex, is there a..."}
swap-hover-pf-flex["<small><b>Step 7</b></small><br/>Action: Swap the hover PF flex and proceed to..."]
inspect-hover-pf{"<small><b>Step 8</b></small><br/>Question: Inspect the hover PF motor especiall..."}
swap-hover-pf["<small><b>Step 9</b></small><br/>Action: Swap the Hover Port Fwd motor, procee..."]
inspect-distro{"<small><b>Step 10</b></small><br/>Question: Inspect the distro board especially ..."}
swap-distro["<small><b>Step 11</b></small><br/>Action: Swap the distro board, proceed to nex..."]
inspection-findings{"<small><b>Step 12</b></small><br/>Question: Was anything swapped due to damage?"}
swap-flexes-anyway["<small><b>Step 13</b></small><br/>Action: Invisible damage is most likely in on..."]
is-the-issue-resolved{"<small><b>Step 14</b></small><br/>Question: Is the issue resolved?"}
the-aircraft-may-return-to-service("<small><b>Step 15</b></small><br/>Reference: The Aircraft may return to service.")
escalate-to-p2-avionics-hardware-on-call{{"<small><b>Step 16</b></small><br/>Escalation: Escalate to P2 Avionics Hardware On C..."}}
ev2-background --> inspect-distro-tail-flex
inspect-distro-tail-flex -->|YES| swap-distro-tail-flex
inspect-distro-tail-flex -->|NO| inspect-tail-node
swap-distro-tail-flex --> inspect-tail-node
inspect-tail-node -->|YES| swap-tail-node
inspect-tail-node -->|NO| inspect-hover-pf-flex
swap-tail-node --> inspect-hover-pf-flex
inspect-hover-pf-flex -->|YES| swap-hover-pf-flex
inspect-hover-pf-flex -->|NO| inspect-hover-pf
swap-hover-pf-flex --> inspect-hover-pf
inspect-hover-pf -->|YES| swap-hover-pf
inspect-hover-pf -->|NO| inspect-distro
swap-hover-pf --> inspect-distro
inspect-distro -->|YES| swap-distro
inspect-distro -->|NO| inspection-findings
swap-distro --> inspection-findings
inspection-findings -->|YES| is-the-issue-resolved
inspection-findings -->|NO| swap-flexes-anyway
swap-flexes-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 ev2-background fill:#dcfce7,stroke:#22c55e,color:#14532d
style inspect-distro-tail-flex fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style swap-distro-tail-flex fill:#dcfce7,stroke:#22c55e,color:#14532d
style inspect-tail-node fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style swap-tail-node fill:#dcfce7,stroke:#22c55e,color:#14532d
style inspect-hover-pf-flex fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style swap-hover-pf-flex fill:#dcfce7,stroke:#22c55e,color:#14532d
style inspect-hover-pf fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style swap-hover-pf fill:#dcfce7,stroke:#22c55e,color:#14532d
style inspect-distro 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-flexes-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 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 to Tail Node flex harness.
- Tail Node board and connector.
- Hover-PF to Distro flex harness.
- Hover-PF board and connector.
- Distro board and connectors.
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 to Tail Node flex harness.
- Tail Node board and connector.
- Hover-PF to Distro flex harness.
- Hover-PF board and connector.
- Distro board and connectors.
2 question
Inspect the distro tail flex, is there any visible damage?
3 action
Swap the distro tail flex and proceed to the next inspection steps.
4 question
Inspect the tail node (especially the connector), is there any visible damage?
5 action
Swap the tail node, proceed to next inspection steps.
6 question
Inspect the hover PF flex, is there any visible damage?
7 action
Swap the hover PF flex and proceed to the next inspection steps.
8 question
Inspect the hover PF motor (especially the connector), is there any visible damage?
9 action
Swap the Hover Port Fwd motor, proceed to next inspection steps.
10 question
Inspect the distro board (especially the relevant connectors), is there any visible damage?
11 action
Swap the distro board, proceed to next steps.
12 question
Was anything swapped due to damage?
13 action
Invisible damage is most likely in one of the flexes. Swap both relevant flexes (make sure the replacements have the foam covering). Notify and ship the removed flexes to Avionics-HW-on-call POC (and include Joseph Katz). Try a redocking flight.
14 question
Is the issue resolved?
15 reference
The Aircraft may return to service.
16 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.