FAA Enforcement, Investigations, and Compliance Actions Attorney

FAA Enforcement, Investigations, and Compliance Actions




When the FAA contacts you, the clock starts.

A letter. A call from an inspector. A pilot questionnaire. A request for records. These are the moments where pilots and mechanics can accidentally turn a manageable situation into a bigger one—usually by talking too soon, guessing, or handing over information in a way that creates new questions.

We help you respond strategically, protect your certificate, and steer the matter toward the least disruptive outcome the facts will support—from early investigations through compliance actions, informal conferences, legal enforcement, and (when it makes sense) appeals.

If you’ve ever heard ATC say “possible pilot deviation” and read you a phone number, that phrase matters. It’s commonly called a Brasher warning or pilot deviation notification, and it can be the first breadcrumb in a chain that ends with a file in Flight Standards or counsel’s office if it’s not handled carefully.


Not every FAA “problem” is enforcement

The FAA has multiple ways to address safety issues. Some paths are designed to correct behavior and prevent recurrence. Others are designed to punish, deter, or remove a risk from the system.

The lane you’re in changes everything—what you should say, what you should produce, what leverage exists, and what “success” looks like:

  • Compliance Action is about fixing a root cause so it doesn’t happen again.
  • Administrative Action is formal documentation and warning without a legal charge.
  • Legal Enforcement Action is where the FAA is pursuing certificate action, civil penalties, or other legal remedies.

A well-handled case can often stay in the first two lanes. A poorly handled case tends to drift into the third.



The Paperwork Tells You What Lane You’re In

Aviation enthusiasts use shorthand because the process is repetitive. A few common examples:

  • Brasher warning / pilot deviation notification: what you may hear on the radio when ATC believes a possible deviation occurred.
  • MOR (mandatory occurrence report): what ATC may file internally after certain events.
  • LOI (letter of investigation) or questionnaires: the FAA’s way of collecting your narrative and documents.
  • EIR (enforcement investigative report): an internal case file that can support enforcement decisions.
  • NOPCA (notice of proposed certificate action) and civil penalty letters: signals that the matter is now on the legal enforcement track.
  • Emergency orders: immediately effective actions where timing and strategy become critical.

The goal isn’t to memorize acronyms. It’s to recognize when a request is gathering facts versus when the FAA is setting a record for a legal action—and to respond accordingly.



How the FAA Decides Which Direction To Go

The FAA’s published policies emphasize safety risk and whether the issue reflects an inability or unwillingness to comply.

Certain fact patterns push a case toward legal enforcement quickly:

  • Conduct viewed as reckless or showing deliberate indifference to safety
  • A pattern of repeated noncompliance (or a history that makes the FAA skeptical)
  • Failure to complete agreed corrective action
  • Situations where public safety is judged to be at risk
  • Allegations of intentional falsification or other intentional misconduct

In other words, the FAA is not only deciding what happened. It’s deciding what your conduct says about judgment, reliability, and future risk.

That’s why first communications matter. Early statements become “facts” that are hard to unwind later.



Compliance Tools We Push For (When the facts support it)

A lot of pilots assume the FAA has only two gears: “no action” or “take the certificate.” That’s not how the system is designed.

When the underlying event looks like a correctable mistake—not a willful disregard for safety—our job is to help present the case in a way that supports compliance or administrative outcomes.

Examples of compliance‑oriented tools and outcomes include:

  • Counseling / education with documented corrective steps
  • Targeted remedial training tied to the actual issue (not generic “more training”)
  • Administrative resolutions such as warning notices or letters that document correction without a legal charge
  • Deferred suspension concepts in the right case (a finding may still exist, but the disruptive loss of privileges can sometimes be avoided if corrective action is completed)
  • NASA ASRS / ASRP strategy when it’s eligible and timely, to preserve a sanctions‑waiver option while still addressing the safety issue
  • 709 reexamination when the FAA frames the issue as qualification—often paired with a plan to narrow scope, prepare intentionally, and keep the concern from expanding beyond what the FAA is actually worried about

These options aren’t automatic. The FAA’s decision is influenced by safety significance, whether the issue is isolated or repeated, the quality of your records, and whether your response shows ownership and prevention of recurrence.



Pilot’s Bill of Rights: Using the Tools it Actually Gives You

Pilot’s Bill of Rights changed the playing field in a few practical ways, especially around transparency and access to information.

Practically, we focus on things like:

  • Pinning down what the FAA is actually alleging and what evidence is driving the allegation
  • Requesting releasable information early (including ATC data when applicable)
  • Using the informal conference process to test the case, narrow the dispute, and pursue settlement on the strongest terms available

The goal isn’t to fight everything. The goal is to keep the FAA honest, avoid unforced errors, and push for the least‑severe outcome that the facts can support.



Letter of Investigation and Informal Conferences: What to Expect

Most FAA matters follow a recognizable rhythm:

  • Initial contact or written request for information
  • LOI questionnaire and a request for your narrative
  • Collection of records (logbooks, maintenance entries, dispatch/flight records, ATC data)
  • A decision point: compliance resolution, administrative action, or referral for legal enforcement
  • If legal enforcement: proposed action, informal conference, and settlement discussions

The earlier you engage, the more options you typically have—including the ability to position the matter for a compliance outcome where the facts support it, rather than letting it drift into legal enforcement by default.


Common Issues Cacciatore Legal Handles

  • Pilots:
    • Altitude deviations, airspace incursions, runway incursions
    • Pilot deviations involving ATC communications or clearances
    • Accident/incident response and early reporting strategy
    • “I thought it was allowed” interpretations that turn into enforcement
    • Medical‑related enforcement overlap and disclosure issues
  • Mechanics and maintenance:
    • Recordkeeping and logbook entry disputes
    • Accusations of improper return to service or inadequate inspection/repair
    • Certification issues involving forms, tags, or compliance records


What a Good Outcome Usually Looks Like

Every case is fact‑driven, but there are patterns:

  • When the issue is a correctable mistake and you present as cooperative, competent, and safety‑focused, the FAA is more likely to consider corrective resolutions.
  • When the FAA believes the issue reflects poor judgment, repeated behavior, or intentional misconduct, the case becomes harder and the upside narrows.

Our job is to maximize the best‑case outcome the facts can support—and to minimize damage when the facts are unfavorable.


What to do right now

If you’ve been contacted by the FAA:

  • Send the letter or email you received, including any deadlines.
  • Don’t guess. Don’t “explain it on the phone.”
  • Preserve records (texts, emails, flight logs, maintenance records).
  • Write down your timeline while it’s fresh.

Ready to talk?



Use the contact form to request a consult and attach the FAA correspondence. The sooner we see the actual language, the sooner we can pick the right path.