Menu

Give Me Regulations or Give Me Guidance

“But different men often see the same subject in different lights….” — Patrick Henry

The above observation holds true in aviation regulation. Pilots regularly hear that something is “required by the FAA.” But where does that requirement actually come from, and how much legal weight does it carry? Federal statutes, the Federal Aviation Regulations (FARs), court decisions, legal interpretations, FAA orders, Advisory Circulars, and the Aeronautical Information Manual (AIM) each have a place in the regulatory framework, but they do not carry the same authority.

The foundation of this regulatory framework is federal law. Congress established the statutory framework governing civil aviation and delegated authority to the FAA to carry it out. Those statutes, primarily found in Title 49 of the United States Code, define the FAA’s regulatory authority.

Working within that framework, the FAA promulgates the FARs through the federal rulemaking process. The FARs are found primarily in Title 14 of the Code of Federal Regulations and include the familiar rules in Parts 43, 61, 67, 91, and elsewhere. The FARs establish legally enforceable requirements, but their application is not always clear.

Courts and administrative tribunals interpret and apply those laws and regulations in the cases before them. Federal court and NTSB decisions can therefore show how a regulation applies to particular facts.

Separate from those decisions, the FAA may express its position through Chief Counsel legal interpretations and formal policy statements or notices. These do not themselves create new regulatory requirements, but they do provide important insight into how the FAA interprets and applies its regulations.

Beyond these formal interpretations and policies, the FAA publishes non-regulatory guidance. Advisory Circulars, informal policy statements, handbooks, FAQs, the AIM, and similar publications may explain regulations, recommend practices, or identify acceptable means of compliance. Under 49 C.F.R. § 5.87, guidance cannot create binding requirements or be used as the basis for proving a violation. It may, however, articulate the FAA’s understanding of how an existing statute or regulation applies to particular circumstances. Guidance, therefore, should not be confused with law—but neither should it be ignored.

Not all FAA guidance is directed at pilots, either. FAA Order 8900.1, for example, contains internal policy and guidance for Flight Standards personnel. It may direct how an inspector handles an issue without necessarily creating a corresponding legal obligation for a pilot.

So, when someone says, “The FAA requires it,” ask: “Where does it say that, and what authority does it carry?” Whether regulation, interpretation, or guidance, the source matters.

AOPA Legal Services Plan Attorney Patrick Brooke poses for a portrait at the National Aviation Community Center on December 16, 2025. Photo by Rebecca Boone.
Patrick Brooke
Patrick Brooke is an in-house attorney with AOPA’s Legal Services Plan. Patrick is a Private Pilot and a former Panel Attorney with the Pilot Protection Services program.

Related Articles