EFB Compliance for Part 135: Getting OpSpec A061 Approval

Type A EFBs are portable devices (like iPads) not mounted to the aircraft. Type B EFBs are portable but mounted. Type C EFBs are installed avionics. Most Part 135 operators use Type A or B with apps like ForeFlight.

Any EFB used to replace required paper documents (charts, manuals, performance calculations) during flight operations requires OpSpec A061 authorization. Using an iPad for reference is one thing — using it as your primary navigation chart source requires formal approval.

Step 1: Define your EFB program in your GOM — devices, applications, intended use, backup procedures, and power management. Step 2: Develop EFB-specific crew training covering normal operations, failures, and reversion to backup procedures.

Step 3: Submit your EFB authorization package to your POI including the GOM amendment, training curriculum, and device/application inventory. Step 4: Your POI reviews, may request demonstration, and issues OpSpec A061 upon approval.

The approval process typically takes 60-120 days. Submit early and schedule a pre-application meeting with your POI.

Operating with EFBs as primary chart/manual source without OpSpec A061 — this is the most common finding and it is immediately actionable by inspectors.

Missing backup procedures for EFB failure during flight. Your GOM must address what happens when the iPad battery dies, the app crashes, or the device is damaged.

Inadequate crew training documentation. Every pilot must complete EFB training before using the device operationally, and recurrent training must address updates and changes.

Standardize on one device model and one app suite across your fleet. Mixed configurations increase training burden and failure modes.

Carry paper backup charts for all planned routes. Even with OpSpec A061, having paper charts available demonstrates operational maturity and provides genuine safety margin.

Document app update procedures — when ForeFlight or Jeppesen pushes an update, your EFB program should have a process for validating the update before operational use.