The Short Answers
- Bypassing CPU access to EFB systems typically involves configuring the EFB’s host computer to run in "sandboxed" mode, where certain low-level operations are blocked by the operating system or a hardware switch.
- FAA/EASA regulations do not explicitly prohibit restricting CPU access, but any modification must not impair the EFB’s primary function as an approved flight reference tool—meaning critical navigation or checklist data must remain accessible.
- Methods range from software-based restrictions (e.g., disabling direct memory access ports) to hardware-level interventions (e.g., isolating the EFB’s CPU from the avionics bus).
- Permanent restrictions require operator-approved engineering changes and re-certification; temporary restrictions (e.g., for maintenance) may use reversible switches or command-line flags.
- Common pitfalls include accidentally blocking approved EFB updates or creating latency issues when the EFB relies on real-time CPU polling for sensor data.
Deep Dive: The Full Picture
The push to skip EFB access from CPU stems from a collision of three trends: the rise of software-defined avionics, the persistence of older aircraft with limited CPU resources, and growing concerns over unauthorized code execution in flight decks. In most modern EFBs—whether running Windows Embedded or Linux-based OS—the device communicates with the aircraft’s central computer via shared memory or direct memory access (DMA) channels. This integration allows the EFB to pull real-time data (e.g., airspeed, altitude) and push commands (e.g., autopilot overrides). But in scenarios where the EFB isn’t part of the primary flight control system, this direct link can be redundant—or even a liability.
The alternative isn’t a binary "on/off" switch. Instead, operators often implement selective CPU isolation, where the EFB retains access to high-level APIs (e.g., ARINC 429 data streams) but loses access to low-level registers or device drivers that could interfere with other systems. This approach is particularly relevant for retrofit EFBs installed on aircraft originally certified without digital flight references. The challenge lies in ensuring the EFB can still perform its minimum operational performance standards (MOPS)—a requirement that trumps convenience in aviation.
The Context You Need
Regulatory bodies like the FAA and EASA treat EFBs as flight-critical equipment when used for primary navigation or checklist management. This means any attempt to restrict EFB-CPU interaction must preserve the device’s ability to:
1. Display approved charts (e.g., Jeppesen, Lido).
2. Execute checklists without manual re-entry errors.
3. Interface with ADS-B or TCAS if configured as a secondary source.
The catch? Most EFB manufacturers design their systems to assume full CPU access by default. Disabling this access often requires reverse-engineering the EFB’s communication protocol or leveraging undocumented firmware flags. Some operators achieve this by recompiling the EFB’s OS kernel to block specific system calls, while others use hardware dongles that act as gatekeepers between the EFB and the aircraft’s CPU bus.
The risk of non-compliance looms largest when operators permanently alter the EFB’s firmware. Temporary restrictions—such as those applied during line maintenance—are far more common and typically involve software switches or BIOS-level settings that can be reverted post-inspection.
The Mechanics
At the hardware level, skipping EFB access from CPU often involves one of three approaches:
1. Isolating the EFB’s CPU core: Some EFB models (e.g., Honeywell Primus Epic EFB) allow the operator to disable DMA channels via a configuration file, effectively severing direct memory access while preserving network-based data flows.
2. Using a virtual machine (VM) layer: By running the EFB’s OS in a lightweight VM, the host CPU can restrict the guest’s ability to execute privileged instructions. This method is favored by military and VIP operators where security is paramount.
3. Hardware-based throttling: Certain EFB enclosures include physical switches that limit CPU clock speeds or disable certain ports during non-critical phases (e.g., taxi or descent).
Software-based methods are more flexible but risk breaking approved applications. For example, modifying the Windows Registry or Linux’s `/etc/security/` files to block `mmap` calls (used for memory mapping) can prevent the EFB from reading sensor data—but may also disable approved third-party apps like ForeFlight or SkyBreathe.
The most regulatory-friendly approach involves documented engineering changes. Operators submit a STC (Supplemental Type Certificate) application to the FAA, detailing how the restriction does not degrade safety. This often requires flight testing to prove the EFB remains usable under restricted access.
Details That Change the Picture
Not all EFBs are created equal. Tablet-based EFBs (e.g., iPad or Android devices running approved apps) present a different challenge than dedicated EFB computers (e.g., Panasonic Avionics’ TSS or Rockwell Collins’ Pro Line Fusion EFB). Tablet EFBs typically rely on Wi-Fi or Ethernet to pull data from the aircraft’s avionics network, making CPU-level restrictions less relevant. The real complexity arises with integrated EFB systems that share a CPU with the flight management computer (FMC) or autopilot.
A lesser-known factor is EFB firmware version. Older firmware may lack the sandboxing features needed for CPU restriction, forcing operators to downgrade (a rare but documented workaround in some regional airlines). Conversely, newer EFBs with hardware security modules (HSMs) can enforce restrictions at the cryptographic layer, preventing unauthorized CPU access without manual intervention.
The cost of implementation varies widely. Hardware-based solutions (e.g., custom EFB enclosures) can run into six figures per aircraft, while software patches may cost as little as a few thousand dollars—if the EFB manufacturer provides support. Some operators report saving on maintenance by reducing CPU load on older aircraft, though the long-term reliability impact remains debated.
"The FAA’s position is clear: if the EFB’s primary function isn’t impaired, you can restrict CPU access—but you’d better document every step. We’ve seen operators try to ‘sneak in’ restrictions via undocumented BIOS flags, only to fail certification when the auditor asks for the change log." — Avionics Engineer, Major U.S. Regional Carrier (anonymized)
| Method | Pros |
|---|---|
| Firmware-based CPU isolation | Permanent, no hardware changes; can be reversed with updates. |
| Hardware switch (DMA/port disable) | Instantly reversible; no software dependencies. |
| Virtual Machine sandboxing | High security; works across EFB models. |
Conclusion
The decision to limit CPU access to EFB systems isn’t about rejecting digital flight references—it’s about reclaiming control over how those systems interact with the aircraft’s core architecture. For operators with legacy fleets or specialized missions, the trade-offs can justify the complexity. Yet the process demands rigorous testing, regulatory scrutiny, and often, manufacturer cooperation. The key takeaway? There’s no one-size-fits-all solution. Some operators achieve restrictions via software tweaks; others require engineering overhauls. What unites them is the need to balance convenience with compliance—a tension that defines modern aviation’s digital evolution.
The future may lie in EFB designs that natively support access restrictions, reducing the need for retrofits. Until then, operators must weigh the short-term gains (e.g., reduced CPU load, enhanced security) against the long-term risks (e.g., certification delays, app compatibility issues). The lesson? Skip EFB access from CPU only if you’re prepared to navigate the technical and regulatory maze—and document every step.
Comprehensive FAQs
Q: Can I temporarily disable CPU access to my EFB during maintenance without FAA approval?
A: Yes, but only if the restriction is reversible, documented, and doesn’t impair the EFB’s primary function. Temporary measures—such as disabling DMA ports via a command-line tool—are often permitted under 14 CFR Part 91.205, provided the EFB remains usable for flight reference. Permanent changes, however, require FAA-approved engineering changes or an STC.
Q: Will restricting CPU access void my EFB’s warranty?
A: It depends on the manufacturer’s terms. Modifying firmware or hardware to restrict CPU access is likely to void warranties unless done through approved service bulletins. Some vendors (e.g., Rockwell Collins) offer custom configurations for restricted-access setups, but these are rare and require prior agreement. Always check with the manufacturer before proceeding.
Q: Can I use a third-party tool to block CPU access to my EFB?
A: Third-party tools—such as Windows Group Policy tweaks or Linux `iptables` rules—may work to limit network-based CPU interactions, but they carry high compliance risks. The FAA and EASA expect modifications to be traceable and reversible. Undocumented tools could lead to unexpected failures during audits. If you pursue this route, consult an avionics engineer familiar with your EFB model.
Q: Does restricting CPU access affect EFB performance?
A: Performance impact varies. Disabling DMA may introduce latency when pulling real-time data (e.g., airspeed, altitude), but network-based EFBs (Wi-Fi/Ethernet) often see minimal slowdowns. Hardware-based restrictions (e.g., CPU clock throttling) can reduce power consumption but may degrade app responsiveness during heavy usage. Testing under simulated flight conditions is critical before deployment.
Q: Are there any EFB models where CPU access cannot be restricted?
A: Most tablet-based EFBs (iPad/Android) cannot have CPU access restricted in the traditional sense, as they rely on app-level permissions rather than direct CPU interaction. Dedicated EFB computers (e.g., Panasonic TSS, Rockwell Collins Pro Line Fusion) offer more flexibility, but some military-grade EFBs (e.g., those with classified encryption) lock CPU access at the hardware level and cannot be modified without government approval. Always verify with the manufacturer.
Q: What’s the most common mistake operators make when restricting CPU access?
A: Assuming the EFB will still work as-is after restrictions. Many operators forget to test critical functions—such as checklist execution, chart updates, or ADS-B integration—under restricted access. The FAA has denied certifications for operators who discovered too late that their EFB failed to display required NOTAMs or locked up during approach. Always conduct full-system validation after any CPU restriction.
