Role playbook · PILOT
Pilot
Captains and First Officers operating CyViation-protected aircraft.
Audience: Cockpit crewTime to first value: end of week 1
Why CyViation matters in your role
You already manage weather, NOTAMs and traffic. CyViation adds cyber and GNSS-integrity risk to that picture, in language you already use:
- A pre-flight cyber briefing tied to your specific route and tail.
- In-flight alerts when entering a zone with known GNSS jamming or spoofing — before the symptoms reach your displays.
- A post-flight debrief so anomalies on your sector feed the next crew's briefing.
The goal is fewer surprises and more confidence in your nav picture — not more paperwork.
Daily playbook
- Pull your pre-flight cyber briefing for today's route on your EFB, alongside weather and NOTAMs.
[SkyRay → Pre-Flight Briefing] - Note any active jamming / spoofing zones on your planned RNP corridor and brief the FO. Plan the "what if GNSS is lost here" call before pushback.
- Check tail-specific advisories — was a cyber-maintenance bulletin (CMB) applied since your last flight on this tail?
[SkyRay → Aircraft Asset View] - Acknowledge SkyRay app permissions on the EFB before pushback. If the integration is red, write it up like any EFB defect.
- After engine shutdown, file a 30-second post-flight note for any cyber / GNSS event you saw.
[SkyRay → Post-Flight Debrief]
Weekly playbook
- Calibrate trust: review last week's alerts vs. what you actually observed; flag false positives so the SOC can tune.
- Read the pilot bulletin / SOC digest (5 minutes) — curated for flight crew, not analysts.
- Refresh on the jamming-vs-spoofing decision tree — what changes on your displays, what to call ATC, what to log.
- Submit anomalous-event reports, even nuisance ones. Pattern detection needs the low-grade events too.
First 30 days
- Completed the SkyRay pilot training module
- EFB integration tested on two real flights
- Acknowledged alerts on at least 5 flights with post-flight feedback on each
- Read the aircraft-type-specific cyber risk profile for the type you fly most
- Met your SOC liaison (a name + channel, not a generic inbox)
- Walked through the jamming-vs-spoofing decision tree with another crew member
- Filed at least one "false positive" so SOC can tune for your sectors
Key screens
| Use case | Screen |
|---|---|
| Cyber briefing before flight | Pilot EFB · [SkyRay → Pre-Flight Briefing] |
| Live in-flight alert view | [SkyRay → Live Flight Alert View] |
| Aircraft cyber-maintenance status | [SkyRay → Aircraft Asset View] |
| Post-flight feedback | [SkyRay → Post-Flight Debrief] |
| GNSS threat overview | [Overwatch → GNSS Threat Map] |
When to escalate
| Situation | Who | How |
|---|---|---|
| Suspected in-flight spoofing affecting nav | ATC first, then dispatcher | Standard ops call; SkyRay note after landing |
| EFB SkyRay integration not loading pre-flight | Dispatcher + MRO on-call | Treat as any EFB defect |
| Recurring false positive on a sector | SOC liaison | Weekly digest reply is fine |
| Tail blocked by a CMB you didn't know about | MRO duty manager | Don't accept the aircraft until cleared |
Glossary
Full list on the Glossary page. The five you need here: GNSS, jamming (denies signal), spoofing (deceives position), RNP corridor, CMB.