Airline Pilot Apps: Flight Deck EFB Software, PRD, and IACRA
Short answer: Airline pilot apps fall into two regulated categories: Electronic Flight Bag (EFB) software used in the flight deck and official federal portals used to get certified and hired. Under FAA Advisory Circular 120-76E (issued June 12, 2024), flight deck EFB apps are divided into Type A static reference tools and Type B interactive apps for weather, charts, and performance calculations. For licensing and hiring, pilots use the web-based IACRA portal for Airline Transport Pilot (ATP) certificates and the Pilot Records Database (PRD) under 14 CFR Part 111, where you must apply for electronic access at least 7 days before sharing your 5-year employment history with an air carrier.
How the FAA Regulates Flight Deck Apps vs Personal Devices
In commercial air carrier operations under 14 CFR Part 121, Part 125, Part 135, or Part 91 Subpart K (Part 91K), you cannot download a consumer app onto a personal tablet to replace required flight deck references. The Federal Aviation Administration (FAA) governs air carrier Electronic Flight Bag (EFB) programs through Advisory Circular (AC) 120-76E, issued on June 12, 2024, while general aviation Part 91 operations follow AC 91-78A, issued on February 23, 2024.
Under AC 120-76E, an EFB is any authorized device, or combination of devices, actively displaying Type A or Type B EFB applications as part of an aircraft operator's EFB program. Portable EFB hardware components are considered Portable Electronic Devices (PEDs). A portable tablet is only considered an EFB when actively displaying authorized Type A or Type B software. If that same tablet displays personal email or an unapproved app, it reverts to a personal PED. Under 14 CFR 121.542(d) (effective April 14, 2014), flightcrew members are prohibited from using a personal wireless communications device or laptop computer for personal use at their duty station on the flight deck while the aircraft is being operated, unless that use follows FAA-approved operational procedures.
Transport Canada Civil Aviation (TCCA) enforces a parallel structure under Advisory Circular 700-020 (Issue 03, effective March 28, 2018). Transport Canada defines an airline-managed tablet as a Controlled Portable Electronic Device (CPED), which is tracked to specific airframes or personnel by an appointed EFB Administrator who ensures no unauthorized changes are made to the hardware, software, or databases.
- Installed vs. portable hardware: Under AC 120-76E, EFB components are installed when incorporated into aircraft type design under 14 CFR Part 21 or as a proper alteration under 14 CFR 43.3. All other components are portable regardless of how often they are removed from the aircraft.
- Battery power rules: Each battery-powered EFB running Type B applications must have an established procedure to recharge from aircraft power during flight, a combined useful battery life covering taxi, flight operations, diversions, and reasonable delays, or an FAA-authorized mitigation strategy.
- Software updates and PIC duty: Operators must control and test application software and operating system changes prior to flight. Under AC 120-76E, the pilot in command (PIC) remains responsible for verifying that any EFB depiction of an en route, terminal area, approach, airport map, or sectional chart is current and up to date, including reviewing Notices to Air Missions (NOTAM) prior to departure and arrival.
- Paper removal: Operators can remove paper products from the flight deck using an equivalent level of safety only if their authorized EFB program includes mitigations preventing an EFB failure from causing the loss of required aeronautical information.
Type A vs Type B Airline Pilot Apps (FAA AC 120-76E) and Rules
Both the FAA (in AC 120-76E) and Transport Canada (in AC 700-020) classify flight deck software into Type A and Type B categories based on the safety severity of a software malfunction. Neither Type A nor Type B EFB applications can replace any installed equipment required by airworthiness or operating regulations.
AC 120-76E simplified how airlines manage Type B apps. While Type B applications must still be authorized as part of the operator's FAA-approved EFB program and listed in the operator's EFB program catalog, they are no longer individually identified or controlled in the airline's Operations Specifications (OpSpecs), Management Specifications (MSpecs), or Letters of Authorization (LOAs). Operators must retain records of changes to their EFB program for 3 months.
Comparison of Type A and Type B EFB Applications under FAA AC 120-76E
| Feature or Rule | Type A EFB Applications | Type B EFB Applications |
|---|---|---|
| Failure Condition Classification | Considered to have no safety effect | Considered a minor hazard |
| Paper Replacement Authority | Do not substitute for or replace any paper, system, or equipment required by regulations | May substitute for or replace paper products of information required for dispatch or carriage in the aircraft |
| Authorization and Tracking | Part of the operator's EFB program. Do not require specific authorization in OpSpecs, MSpecs, or LOAs | Authorized as part of the operator's FAA-authorized EFB program and listed in the operator's EFB program catalog |
| Schedule, Duty, and Logbook Tools | Pilot flight and duty-time logs, crewmember-required rest logs, trip scheduling and bid lists, flightcrew qualification and currency logs | Aircraft flight log and servicing records, Category II/III landing records, autopilot approach and autoland records |
| Manuals, Checklists, and Directives | Minimum Equipment Lists (MEL), Configuration Deviation Lists (CDL), Airline Policy and Procedures Manuals (PPM), 14 CFR, AIM, Chart Supplements | Airplane Flight Manuals (AFM), Flight Operations Manuals (FOM), Company Standard Operating Procedures (SOP), electronic checklists |
| Navigation, Weather, and Performance | Airport diversion policy guidance, noise abatement procedures, VOR check records | Takeoff, approach, and landing performance calculations, Weight and Balance (W&B) calculations, weather and aeronautical information, NOTAMs, icing holdover time tables |
Core Flight Deck and Schedule Apps by Category
Every software tool an airline pilot uses on duty fits into a functional category under AC 120-76E and TCCA AC 700-020. Under AC 120-76E, Type B weight and balance (W&B) applications must be produced for a specific aircraft and based on existing data in the FAA-approved Airplane Flight Manual (AFM), Pilot's Operating Handbook (POH), or W&B manual. Their algorithms may interpolate within approved data, but must never extrapolate beyond the approved aircraft-operating envelope.
Deicing and anti-icing holdover time apps follow strict limits. Transport Canada Advisory Circular 700-030 (Issue 02, effective November 18, 2014) governs Electronic Holdover Time (eHOT) applications. An eHOT app is Type A if it displays a fixed presentation of the Transport Canada Holdover Time Guidelines, and Type B if it dynamically calculates holdover times from crew inputs. Under AC 700-030, eHOT apps must update data annually, must not allow expired data to be used after October 1 of the following year, and must never interpolate holdover times between fluid dilutions (such as an 80/20 mixture) or between temperature brackets (such as between -3 and -14 degrees Celsius in snow).
- Aeronautical charts and moving maps (Type B): Under TCCA AC 700-020 Appendix B, interactive electronic aeronautical charts support panning, zooming, scrolling, and rotation for en route, area, approach, and airport surface maps. Displaying own-ship position is permitted only as an aid to situational awareness and is not intended for primary navigation.
- Weather, NOTAMs, and dispatch releases (Type B): Replaces paper weather reports with near-real-time weather and aeronautical information, graphical NOTAMs, master flight plan updating, and required dispatch or flight release documentation, often signed using approved Public Key Infrastructure (PKI) electronic signatures.
- Duty-time, rest, and bidding apps (Type A): Appendix A of AC 120-76E covers pilot flight and duty-time logs, crewmember-required rest logs, trip scheduling and bid lists, and flightcrew qualification recordkeeping (tracking CAT III qualifications, special airports, and landing currency).
- Safety reporting and reference apps (Type A): Covers lookup and completion of NASA Aviation Safety Reporting System (ASRS) forms, near midair collision (NMAC) reports, wildlife strike reports, hazardous materials (HAZMAT) lookup tables, and computer-based training modules.
The FAA Pilot Records Database (PRD) Application (14 CFR Part 111)
During a job search, pilots use federal web applications required to get hired. Under 14 CFR 111.5, the legacy Pilot Records Improvement Act (PRIA) ceased to be effective on September 9, 2024, and is no longer an alternative to the electronic Pilot Records Database (PRD). The FAA maintains a pilot's records in the PRD for the life of the pilot, removing them only upon official notification of death accompanied by a certified copy of the certificate of death or when an FAA audit indicates 99 years have passed since the pilot's date of birth.
To register in the Pilot User Portal in the FAA Pilot Records Database portal, you must hold a Commercial, Airline Transport Pilot (ATP), or Remote pilot certificate and a valid FAA medical certificate. Private pilots cannot access the PRD system. Starting mid-November 2026, the FAA automatically disables PRD user accounts after 365 days of inactivity, requiring you to log in at least once a year to keep your account active without contacting PRD Support.
Under 14 CFR 111.305, you must submit your application for electronic access to the PRD at least 7 days before seeking to access the database to review your record or grant consent to an air carrier. If you cannot meet electronic identity validation requirements, the FAA PRD Final Rule (86 FR 31006, published June 10, 2021) allows you to receive a paper copy of your records or release a PRD Airman Record (PAR) to an employer using paper FAA Form 8060-14.
- Required PRD application details (14 CFR 111.305(b)): Full name exactly as it appears on your pilot certificate, FAA-issued certificate number, current mailing address, telephone number, email address, and any identity verification items requested by the Administrator.
- Affirming your 5-year employment history (14 CFR 111.310(b)): Before any operator can view your PRD file, you must provide time-limited written consent affirming that your employment history in the PRD for the 5 years preceding the date of consent is accurate and complete.
- Separate NDR driving record consent (14 CFR 111.110 and 111.310(c)): Reviewing entities (except Part 91K fractional ownerships and 91.147 air tour operators) must run a National Driver Register (NDR) search for state motor vehicle driving records using separate written consent from the pilot. If you request a copy of state driving records obtained by the employer, the operator must provide them within 30 days.
What Airlines Evaluate in Your PRD Application Record
Under 14 CFR 111.100 and 111.105, reviewing entities (Part 119 certificate holders operating under Part 121, Part 125, or Part 135, Part 91K fractional ownership programs, and 14 CFR 91.147 air tour operators) cannot permit you to begin service as a pilot until evaluating all relevant FAA records, reporting entity records, NDR driving records, and your 5-year employment history.
As clarified in the FAA PRD Final Rule, an airline can hire you and begin your ground or simulator training (establishing your PRD Date of Hire under 14 CFR 111.10) before evaluating all PRD records. However, the operator cannot permit you to begin service as a pilot flight crewmember in flight until the full PRD evaluation is complete, unless qualifying for the good faith exception under 14 CFR 111.115 after receiving FAA notice of missing records from a previous employer.
Reporting entities (reviewing entities plus corporate flight departments operating two or more type-rated airplanes, turbine rotorcraft, or large powered-lift aircraft under 14 CFR 111.1(b)(4) and public aircraft operations) must upload records generated on or after June 10, 2022, plus historical PRIA records dating back to August 1, 2005 for Part 121 and Part 135 air carriers or August 1, 2010 for Part 125 and Part 91K operators. By our calculation from 14 CFR Part 111, your PRD timeline spans 6 distinct regulatory windows: a 7-day advance access application, a 10-day window for employers to correct reported errors, a 14-day window for on-request reporting entities to upload requested records, a 30-day window for standard contemporaneous record reporting and NDR record copies, a 45-day window from your PRD date of hire for the operator to document NDR compliance, and a 365-day login requirement.
Records Included vs Excluded in the FAA Pilot Records Database (14 CFR Part 111)
| Record Category | What Is Reported and Evaluated in the PRD | What Is Prohibited from PRD Reporting |
|---|---|---|
| FAA Records (14 CFR 111.135) | Current pilot and medical certificates, type ratings, limitations, failed attempts to pass a Part 61 practical test, un-overturned enforcement actions, and accidents or incidents as PIC or SIC | Records not pertaining to the individual pilot's certification, enforcement, or accident history |
| Drug and Alcohol Testing (14 CFR 111.135 & 111.220) | Verified positive drug tests, confirmed breath alcohol results of 0.04 or greater, on-duty or pre-duty alcohol use, refusals to submit to testing, and return-to-duty or follow-up test results | Negative routine drug or alcohol test results not categorized under return-to-duty or follow-up testing |
| Training, Qualification, and Proficiency (14 CFR 111.225) | Date of event, aircraft type, duty position, training curriculum, satisfactory or unsatisfactory result, check pilot or evaluator comments, and specific unsatisfactory tasks or maneuvers | Flight time, duty time, and rest time records. Physical examination or protected medical records. Recent flight experience logs. Voluntary Safety Reporting Program (ASAP) records (14 CFR 111.245) |
| Final Disciplinary Actions (14 CFR 111.230) | Written warnings, suspensions, or terminations pertaining to pilot performance that are not pending dispute, including whether the pilot was permanently or temporarily removed from aircraft operations | Disciplinary actions not pertaining to pilot performance, or actions subsequently overturned by employer-pilot agreement, dispute panel, or court of law |
| Final Separation from Employment (14 CFR 111.235) | Date and purpose of separation, stating whether it resulted from termination due to pilot performance/professional disqualification or another reason (medical disqualification, resignation, retirement) | Separations not yet final due to pending dispute, or separations subsequently overturned because the event did not occur or the pilot was not at fault |
| Motor Vehicle Driving History (14 CFR 111.110 & 111.240) | Verification documented within 45 days of the PRD date of hire that the operator completed the National Driver Register (NDR) search and evaluation | Any substantive information from State motor vehicle driving records (14 CFR 111.240(b)) |
IACRA and ATP Certification Applications (14 CFR Part 61 Subpart G)
The Integrated Airman Certification and Rating Application (IACRA) on the FAA IACRA website is the FAA's web-based system that guides you through airman certification, validates regulatory compliance, uses electronic signatures, and prints temporary airman certificates. Under IACRA Version 11.3, the digital system processes FAA Form 8710-1 (Airman Certification and/or Rating Application).
In Canada, Transport Canada sets a 40-working-day service standard for issuing an Airline Transport Pilot Licence or Commercial Pilot Licence, and a 10-working-day service standard for a temporary licence, permit, or medical certificate.
Pre-Interview Checklist for Your Pilot Applications
Because air carriers use the PRD to prompt interview conversations with pilot applicants, audit your electronic applications before your interview date using this checklist built from 14 CFR Part 111 and IACRA rules.
- Audit your FAA and employer records (14 CFR 111.315): Check every Part 61 practical test attempt, certificate limitation, and employer training record, including check pilot or evaluator comments reported under 14 CFR 111.225.
- Flag inaccuracies immediately (14 CFR 111.320 and 111.250): Report errors through the PRD to mark the record as in dispute. The reporting entity must correct the error within 10 days of identification or initiate a dispute investigation within 30 days.
- Update your 5-year employment history (14 CFR 111.310(b)): Ensure every pilot employer from the preceding 5 years is listed accurately so your PRD file matches your resume.
- Verify your IACRA profile and logbook totals: Confirm your full legal name and FAA certificate number match across IACRA, the PRD, and your logbook, and verify any simulator credits or R-ATP certifying statements under 14 CFR 61.159 or 61.160.
Practice example
When we review your Pilot Records Database file, will we see any practical test failures or unsatisfactory training events, and what did you change after that experience?
Example answer written by our team. The applicant is invented. Yes, when you review my PRD file under 14 CFR Part 111, you will see one Notice of Disapproval from my initial Commercial Pilot multiengine practical test in IACRA, and a clean record across all Part 135 training and proficiency checks since then. On that commercial checkride, I rushed the single-engine instrument approach setup and failed to brief the missed approach altitude changes thoroughly before crossing the final approach fix. I owned the mistake immediately, logged three hours of targeted retraining with my instructor focused on workload management and deliberate briefing pacing, and passed the recheck two days later. That failure changed how I treat every cockpit procedure. In Part 135 operations, I never let time pressure compress my setup or checklist discipline, and I ask for a delay vector if we are not stabilized and fully briefed.
This answer directly addresses what the hiring panel sees in the PRD under 14 CFR 111.135 and 111.225 without making excuses or blaming the examiner. It states the exact event, explains the root cause, and shows how the lesson improved the pilot's current multi-crew discipline.
Practice this on Fourstripe. Pick your airline and a captain runs the interview out loud: TMAAT, about-you, technical and scenario questions, with real follow-ups. You get a scored report on every answer. 7-day trial, then from $149 a week. Start a practice interview
Frequently asked questions
What is the IACRA application used for by airline pilots?
IACRA (Integrated Airman Certification and Rating Application) is the FAA's web-based portal that guides pilots through applying for airman certificates and ratings, such as an Airline Transport Pilot (ATP) certificate or aircraft type rating via digital FAA Form 8710-1. It validates regulatory compliance, uses electronic signatures, and prints temporary airman certificates.
How far in advance must a pilot apply for access to the Pilot Records Database (PRD)?
Under 14 CFR 111.305(c), a pilot must submit an application for electronic access to the PRD at least 7 days before seeking to access the database to review their own records or grant release consent to an operator. Additionally, starting mid-November 2026, you must log in at least once every 365 days to prevent automatic account deactivation.
Can an airline check a pilot's records in the PRD without permission?
No. Under 14 CFR 111.120 and 111.310, a reviewing entity cannot retrieve a pilot's records in the PRD before receiving the pilot's time-limited written consent.
How many years of employment history must a pilot verify in the PRD application?
Under 14 CFR 111.310(b), when providing written consent in the PRD, a pilot must affirm that their employment history for the 5 years preceding the date of consent is accurate and complete. If any past employers are missing, the pilot must update the employment history before releasing the record.
Can an airline hire a pilot and start training before reviewing their PRD records?
Yes. According to the FAA PRD Final Rule and 14 CFR 111.105, an operator can hire a pilot and begin required ground or simulator training (establishing the PRD Date of Hire) before evaluating all PRD records, but the operator cannot permit the individual to begin service as a pilot flight crewmember in flight until all relevant PRD and National Driver Register records are evaluated.
What is the difference between Type A and Type B EFB apps under FAA AC 120-76E?
Under FAA Advisory Circular 120-76E, Type A EFB applications have a failure classification of no safety effect and cannot replace required paper documents (such as duty-time logs or MEL lookups). Type B EFB applications have a minor failure classification, must be listed in the operator's FAA-authorized EFB program catalog, and can replace required paper flight deck references like aeronautical charts, weight and balance calculations, and Airplane Flight Manuals.
Sources
- FAA Advisory Circular 120-76E: Authorization for Use of Electronic Flight Bags
- 14 CFR Part 111: Pilot Records Database (eCFR)
- 14 CFR Part 61 Subpart G: Airline Transport Pilots (eCFR)
- FAA Pilot Records Database (PRD) Final Rule (Federal Register)
- FAA Pilot Records Database (PRD) Portal
- FAA Integrated Airman Certification and Rating Application (IACRA)
- FAA Pilot Training: Airline Transport Pilot (ATP)
- 14 CFR 111.255: Reporting Historical Records to PRD (GovInfo)
- Transport Canada Advisory Circular 700-020: Electronic Flight Bags
- Transport Canada Advisory Circular 700-030: Electronic Holdover Time (eHOT) Applications
- Transport Canada: Apply for a Pilot Permit, Licence or Rating
- FAA Advisory Circular 91-78A: Use of Electronic Flight Bags