FAA PRD: Pilot Records Database Complete Guide for Airlines & Pilots

The FAA Pilot Records Database (PRD) changed how airlines hire pilots. Before PRD launched, hiring carriers chased paper records from previous employers, sometimes waiting weeks for files that could be incomplete, lost, or scrubbed of unflattering details. The Pilot Records Improvement Act of 1996 (PRIA) tried to fix that, but the process stayed slow and uneven.

Then came Colgan Air Flight 3407 in 2009 — a crash that killed 50 people and exposed how badly the system was working. Congress responded with the Airline Safety and FAA Extension Act of 2010, and after a decade of rulemaking, PRD went live as the mandatory replacement for PRIA.

If you are a pilot, the database holds your career history. If you are an airline, you cannot legally hire a flight crewmember without checking it first. The shift is bigger than a software upgrade. The Federal Aviation Administration now controls the canonical record set, every reporting employer must upload data on a regular cadence, and pilots have a consent-driven right to see what is inside their own file. This guide walks through what PRD actually stores, who has to use it, how to access your own records, and what to do when something in your file is wrong.

The stakes are higher than most pilots realize. A wrong drug test entry, a misclassified training failure, or a lingering employment record from a company that no longer exists can sink a job application before the interview. Knowing how PRD works — and knowing how to fix errors — is now part of basic career hygiene for anyone holding an airman certificate.

The pilots who treat their PRD file as something they check once every few years, only when prompted by an HR department, are the ones who get blindsided. The ones who log in every six months, scroll through the access log, and verify their training entries are the ones who never face a delayed offer letter.

This guide reflects the rules as they stood after the most recent FAA guidance updates and assumes you are a pilot operating under FAA jurisdiction. The same general principles apply to pilots flying under foreign certificates who later transition to FAA carriers, but the data flow is slightly different and the consent mechanics involve a few extra steps that are outside the scope of this overview.

PRD is run by the FAA's Aviation Data Systems Branch under 14 CFR Part 111, the regulation that codifies what records get stored, who reports them, and how access is controlled. The database went into full operational use in June 2022, replacing the patchwork PRIA process that had governed pilot record sharing for 26 years. Every Part 121 air carrier, Part 135 operator, Part 91 Subpart K fractional, public aircraft operator, and certain corporate flight departments must report into PRD.

The system is split into two flows. The reporting flow requires employers to upload pilot records on hire, on separation, and periodically during employment. The evaluation flow lets a prospective employer pull a candidate's full PRD report after the pilot consents in writing. The pilot can see the same report, free of charge, by logging into the FAA portal.

Both flows run on the same backend infrastructure, which is built on FAA-managed servers with controlled access logs for every read and write. The technical architecture matters because it explains why errors are now harder to bury — every change to your file is timestamped and attributed to a specific reporting user at a specific employer.

What ends up in your PRD file is broader than most pilots expect. The database is not just a logbook of jobs held — it is a structured record of qualifications, disciplinary events, and safety-critical data points pulled from multiple federal sources. FAA regulations require reporting employers to submit data within set timeframes, and the FAA itself feeds in enforcement and certification information directly from its own systems.

The categories below are the ones that matter most when an airline reviews your file. Understanding what is in each bucket helps you spot errors and understand what hiring carriers will see.

Pilot consent is the legal hinge of the entire system. Under 49 USC 44703(h), no air carrier may request your PRD report without your signed written authorization, and that consent is specific — it names the requesting employer, covers a single application, and expires after the carrier completes its evaluation. You sign the consent through the FAA PRD portal using your airman certificate number and a verified identity. The consent is digital, time-stamped, and stored alongside the access log so you can later see exactly which employers viewed your file.

Consent is not a one-way door. You can revoke it at any point before the carrier completes the pull, although in practice that usually ends the application. You also have the right to see your own report at no cost, as often as you want, without any third party being notified. Airlines, on the other hand, can only request a report when they have a documented intent to hire, and every request is logged.

The consent mechanism replaced the old PRIA written release that pilots signed on paper for every previous employer individually. Under PRIA, a pilot applying to a major might sign 8 or 10 separate releases, one per employer in their history, and the hiring airline had to chase each one. PRD collapses that into a single consent because the FAA already holds the data.

For hiring airlines, the PRD check is not optional and not a background step you can defer. 14 CFR 111.225 requires the carrier to evaluate the PRD report before allowing a pilot to act as a flight crewmember. That means the report must be pulled, reviewed, and documented before the pilot flies a single revenue leg. Carriers that fail to comply face FAA enforcement, and the rule applies whether the pilot is a new hire, a returning furloughee, or a contract crewmember.

The review is more than a checkbox. Carriers must evaluate the substance of what is in the report and retain documentation of that evaluation for 5 years. If the report shows a disqualifying event — a failed checkride hidden in training records, a positive drug test, a revoked medical — the carrier must address it before the pilot is cleared to fly. Internal hiring committees typically maintain a written rubric for evaluating PRD content, and the FAA can audit those rubrics during a Part 121 inspection.

Carriers also have to handle disclosed issues consistently across candidates. The FAA pays attention during audits to whether the same PRD finding produced the same outcome for two different applicants. Inconsistent treatment, especially when it correlates with protected class status, is the kind of pattern that triggers a deeper compliance review and can lead to discrimination complaints filed in parallel with FAA enforcement.

Accessing your own PRD records is straightforward once you have the right credentials lined up. The portal lives at prd.faa.gov and requires a Login.gov account linked to your airman certificate. The first-time setup takes about 20 minutes, mostly because Login.gov verifies your identity using a government ID and a phone number. After that, future logins take a couple of clicks.

Once inside, you can view your full record, download a PDF, see the access log showing which employers have pulled your report, and flag any entry you believe is wrong. The portal also lets you see pending data submissions from your current employer if any are queued.

The transition from PRIA to PRD was not a name change — it was a structural rebuild. Under PRIA, the hiring airline shouldered the burden of chasing records. The carrier sent written requests to every previous employer, every FAA office, and every drug testing consortium, then waited for responses that could take 30 days or more. Records arrived on paper or fax, were often incomplete, and varied wildly in format. Pilots with histories at defunct carriers sometimes had records that simply could not be retrieved.

PRD flipped the model. The FAA now holds the authoritative dataset, employers feed in on a schedule, and the hiring carrier pulls a single standardized report. Most queries return results within minutes rather than weeks. The data is structured, searchable, and consistent across all reporting entities. Defunct carriers no longer create black holes because the FAA retained the historical records during the migration.

There are tradeoffs. The reporting burden on employers is higher because they must submit data continuously, not just on request. Smaller Part 135 operators initially struggled with the technical onboarding to the PRD system, although the FAA published guidance and templates to help. And because the FAA now controls the canonical record, errors are harder to correct informally — the formal dispute process described later is the only legitimate path.

For pilots, the practical impact of the PRIA-to-PRD transition is that hiring timelines have compressed dramatically. A regional airline that used to wait three or four weeks for previous-employer records can now complete the PRD evaluation in a single afternoon. That speed cuts both ways. A clean record means a faster offer. A contested record means a hiring committee sees the dispute flag immediately and may pause your file pending the FAA review window.

Errors in PRD files are more common than the FAA likes to admit. Reporting employers sometimes mis-key dates, attach training records to the wrong pilot, or fail to clear a record after a checkride retest. The FAA's own enforcement data can lag, occasionally showing actions that were later withdrawn. And legacy data migrated from PRIA included some records that were already wrong on paper before they entered the new system.

The good news is that the dispute process is codified in 14 CFR 111.255 and works. Pilots who find an error can file a written correction request through the PRD portal, and the FAA forwards it to the reporting entity for verification. The reporting entity has 30 days to respond. If the entity confirms the error, the record is corrected. If they dispute the correction, the FAA reviews the underlying evidence and rules. While the dispute is pending, the contested record is flagged in the report so prospective employers see that it is under review.

Some common errors crop up often enough that it is worth knowing how to handle them in advance. The list below covers the ones the FAA has flagged most often in its annual PRD compliance reports. Each one has a known cause and a known fix, and pilots who recognize the pattern can usually clear a problem record within the standard 30-day dispute window.

The single most common error category is training data attached to the wrong pilot. This typically happens at large regionals where two pilots have similar names and the records clerk transposes airman certificate numbers during data entry. The fix is straightforward — flag the entry, attach proof that you were not the pilot in the training event, and the reporting carrier corrects the record. The harder cases involve unsatisfactory checkride entries that were later remediated but never updated in the system. If your retest succeeded, the file should show both events with the successful outcome on top.

One area that still generates confusion is which training events trigger a PRD report. The rule is simpler than most pilots think. Any event documented in the operator's training records — checkrides, line checks, recurrent ground school, qualification training, and unsatisfactory events — gets reported. Informal coaching sessions and peer mentoring do not. If the training generates a checking airman signature in your file, it goes to PRD.

The future of PRD is one of incremental expansion. The FAA has signaled that helicopter operators and certain Part 91 corporate operators may eventually be folded into mandatory reporting. For now, the system is stable, data quality is improving each quarter, and pilots who review their files regularly avoid most of the hiring-process headaches that catch others off guard.

Your FAA Registry entry, your medical, and your PRD record now form a triangle of federal data that defines your professional standing. The 10 minutes a year it takes to log in and check your PRD report is one of the highest-leverage habits a working pilot can build.

Whether you are a 1,500-hour CFI applying to a regional or a senior captain bidding to a new fractional operator, the PRD report is part of how you will be evaluated. Treat it like a credit report — check it before someone else does, fix what is wrong, and keep moving. That habit alone separates pilots who get hired quickly from those who get tangled in delays they never saw coming. The pilots who succeed in the modern hiring environment are not the ones with perfect records — almost no one has those after a 20-year career.

They are the ones who know what is in their file, understand how to explain anything that looks unusual, and can walk into an interview ready to answer questions about specific entries without being surprised by what the hiring committee sees on their screen. A pilot who can speak confidently about an old training event already in the file projects competence and self-awareness, and that is exactly what hiring committees are listening for during the technical interview.