Who can ask to see your Part 107 certificate?

Four authorities can ask to see your Part 107 certificate and require you to present it: the FAA Administrator, an authorized representative of the National Transportation Safety Board, any federal, state, or local law enforcement officer, and an authorized representative of the Transportation Security Administration. That list comes straight from 14 CFR 107.7, and the third entry is the one that surprises pilots, because it means the city police officer walking up to your launch point has the same certificate inspection right as an FAA inspector.

This article walks through what the rule requires you to have and to hand over, what each of the four authorities tends to be doing when they ask, where the rule stops and voluntary cooperation begins, and why the encounter should end with an entry in the program's records. The whole regulation is a few paragraphs long, and knowing it cold is the difference between a two minute check and a bad afternoon.

What the rule requires you to carry and present

The obligation has two halves. First, a remote pilot in command, and anyone manipulating the controls, must have the remote pilot certificate in physical possession and readily accessible while exercising its privileges, together with identification. Readily accessible means on your person or within reach at the operation, not in a truck across the site and not at home in a drawer. The identification must carry the details the certification rules specify, in practice a government photo ID whose name matches the certificate.

Second, on request from any of the four listed authorities, you must present both for inspection. The text of 14 CFR 107.7 also reaches past the card: the rule requires making available to the Administrator, on request, any document, record, or report the regulations require you to keep, and a companion provision lets the FAA inspect the aircraft and require a demonstration of compliance. The certificate check is the visible tip of a broader inspection authority, which is worth understanding before anyone official is standing next to you.

The four authorities and what each is usually doing

FAA personnel are the expected case, most often an aviation safety inspector from the local Flight Standards office conducting a field check or following up on a complaint or authorization. NTSB representatives appear around accidents and incidents, where their interest in the certificate is part of establishing who was operating what. TSA representatives connect to the security side of the airspace system. All three are aviation agencies whose requests arrive with obvious context.

The law enforcement entry is deliberately broad: any federal, state, or local officer. The FAA wrote the rule that way because officers on the ground are usually the first authority to reach a drone operation drawing attention, and verifying the operator's identity and certification is the first step in sorting a legal operation from a problem. The officer does not need aviation expertise, a specialized assignment, or FAA coordination to ask. For the pilot, the professional response is identical across all four: produce the certificate and ID promptly, answer identity questions directly, and keep the interaction factual.

Where the rule stops, and everyone else

The 107.7 list is short on purpose, and it does not include clients, property managers, security guards, or curious bystanders. None of them holds a regulatory right to inspect your certificate. Refusing a private demand is legal, and often still unwise, because clients and site owners control access and contracts even where they cannot cite regulations. The practical split is to treat the four authorities as obligations and everyone else as relationship management, decided by professionalism rather than compelled by rule.

The other boundary worth knowing is what the rule does not compel even from authorities. Presenting the certificate and ID for inspection is required. Surrendering the certificate, consenting to searches beyond the rule's scope, or speculating about fault at an incident scene are not part of 107.7, and records requests beyond the card formally run to the Administrator. A pilot can be completely cooperative on the required items while staying disciplined about everything else, and crews should agree on that posture before the first field contact rather than improvising it mid encounter.

Being ready to answer is a program property

Individual pilots pass certificate checks. Programs pass them repeatedly, across crews and job sites, because readiness is built into how the operation runs rather than into one person's glovebox. That starts with the obvious layer, every pilot carrying certificate and ID as a standing equipment item, and extends to the layer inspectors reach next: the registration certificate for the aircraft on site, any waiver or authorization covering the operation, and the records the regulations require, reachable from the field rather than from someone's desk on Monday.

The encounter itself belongs in the record. A field contact with any authority is an operational event, and the program should capture it the same day: who asked, which agency, when and where, what was presented, and how it resolved. Those entries turn scattered anecdotes into a pattern the program can see, protect the pilot if the story is ever retold differently, and give the operation something better than memory if the same inspector, or the same client, ever asks again.

Common mistakes in certificate inspection requests

Assuming police cannot ask. Any federal, state, or local law enforcement officer is on the 107.7 list with the same inspection right as the FAA. Arguing jurisdiction with an officer over a settled rule turns a routine check into an incident.

Leaving the certificate somewhere else. Physical possession and ready accessibility are required while flying, and a card at home or in a distant vehicle fails the rule even though the certification is valid. Make carrying it a preflight equipment item.

Presenting a phone photo. The rule contemplates the certificate itself, presented with identification. A picture of a card is a conversation starter, and what it starts is a longer inspection.

Overcorrecting into oversharing. The required items are the certificate and ID, with broader records requests running to the Administrator. Volunteering speculation, extra documents, or site access beyond the request helps no one, including you.

Letting the encounter vanish. An undocumented field contact leaves the program with rumors instead of records. Log who asked, what was shown, and the outcome the same day, while the details are still exact.

FAQ

Can a local police officer really demand my drone license?

Yes. The rule lists any federal, state, or local law enforcement officer among the four authorities entitled to inspect your remote pilot certificate and identification, alongside the FAA, the NTSB, and the TSA. Present both promptly and keep it factual.

Do I have to show my certificate to a client or security guard?

No regulation compels it, since private parties are not on the 107.7 list. Showing it anyway is often the professional move, because clients and property owners control access and contracts even without inspection rights.

What exactly must I have with me while flying commercially?

Your remote pilot certificate, in physical possession and readily accessible, plus identification containing the details the certification rules specify. Practically that means the card and a matching government photo ID on your person at the operation.

Can an inspector go beyond the certificate check?

Yes. The rule requires making required documents, records, and reports available to the Administrator on request, and it authorizes the FAA to inspect the aircraft and require demonstrations of compliance. Field readiness means more than the card.

Closing thought

The answer to the title question is a list of four, and every commercial pilot should be able to recite it: FAA, NTSB, TSA, and any law enforcement officer. The deeper preparation is structural, carrying the card as a matter of habit, keeping the operation's documents reachable from the field, and writing down every official contact. Checks go quickly for pilots who expected them, and expecting them is a choice a program makes in advance.

If you are preparing pilots for authority requests in the field, FlybyOps was built for the operational record problem at the center of regulated drone work. A pilot registry confirming who holds current certificates, a document vault that puts authorizations and registrations within reach on site, role-based access control over program records, and an append-only audit log are all part of how the platform keeps the proof an officer can ask for one screen away from the pilot who needs it.