Direct Answer
Most Part 135 applications are not rejected on the merits of the operation — they are returned because the package is incomplete or not in the form and manner the FAA requires. Under FAA policy formalized in 2025, the FAA will no longer accept an application that is incomplete or non-conforming; it sends it back to be completed and resubmitted.
The recurring causes are documentation gaps, not bad operations: missing or non-conforming manuals (the General Operations Manual and General Maintenance Manual), a vague or incomplete compliance statement, missing or unqualified required management personnel and resumes, incomplete ownership or U.S.-citizenship documentation, an unrealistic schedule of events, and aircraft or operations documents that contradict the manuals.
The hard regulatory anchor is 14 CFR §119.35, which requires the application “in a form and manner prescribed by the Administrator” and at least 90 days before intended operation. The 2025 tightening (FAA Notice N 8900.735) is FAA policy and guidance, not new regulatory text. Bottom line: completeness, not just compliance, is what gets you past the gate — and it is the part you fully control.
The Mistake: Confusing “Rejected” with “Not Good Enough”
When a prospective operator hears that a Part 135 application was “rejected,” the natural assumption is that the FAA looked at the operation and decided it was not safe or not viable. In the large majority of cases, that is not what happened. What happened is far more mundane and far more preventable: the application package arrived incomplete, internally inconsistent, or not in the form and manner the FAA requires — and so it was returned before the substantive evaluation really got going.
This distinction is the whole point of this article. A returned package is a documentation failure, not an operational one. The aircraft can be sound, the people can be qualified, and the business plan can be excellent — and the application still bounces because a manual is non-conforming, a required management resume is missing, or two documents in the package contradict each other. The FAA’s certification process is built around demonstrating readiness with documents; if the documents are not complete and consistent, there is nothing for the agency to accept yet.
That is good news, because completeness is the part of certification you control most directly. You cannot control your Flight Standards office’s workload or how the agency staffs your project, but you can control whether every required document is present, current, conforming, and consistent on the day you submit. This guide walks through the 2025 FAA policy that raised the bar on intake, the specific documentation gaps that send packages back, the difference between a returned and a denied application, and a practical checklist to get accepted on the first pass. For the companion pieces, see how to get a Part 135 certificate and the Part 135 certification application checklist.
No invented statistics — and be wary of sources that have them
The FAA describes the causes of incomplete or insufficient applications qualitatively. There is no published “X% of Part 135 applications are rejected” figure, and we do not manufacture one. If you see a confident-looking rejection-rate statistic with no dated FAA source behind it, treat it as marketing, not fact. What is well documented is the policy and the categories of documentation gaps — and those are what you can actually act on.
The 2025 “Complete Application” Policy, Explained
In 2025 the FAA formalized a stricter posture on how it accepts certification applications. The policy document is FAA Notice N 8900.735, titled “Disposition of Incomplete or Insufficient Air Operator and Air Agency Certification Applications,” effective May 22, 2025. The agency also published a companion Federal Register notice, “Changes to Application for Certification Process,” on June 3, 2025, describing the same change. The core of it is simple to state: the FAA will no longer accept applications that are incomplete or not submitted in a form or manner acceptable to the Administrator. The policy spans multiple certificate types — including 14 CFR Part 135 — and applies to new applications submitted on or after its effective date.
This is FAA policy and guidance — not the CFR
Notice N 8900.735 and FAA Order 8900.1 are FAA guidance and policy: the agency’s own description of how it manages and accepts applications. They are not numbered sections of the Code of Federal Regulations, and the FAA updates and supersedes notices over time. The regulatory anchor underneath the policy is 14 CFR §119.35, which requires the application “in a form and manner prescribed by the Administrator” and at least 90 days before intended operation. Always confirm the current notice and its status with your Flight Standards office before relying on a specific number.
What changed, in practice, is the cost of submitting a half-finished package. Before, an applicant might submit early and incomplete and treat the FAA’s review as a way to find out what was still missing. Under the tightened policy, an incomplete or non-conforming package does not get worked on — it gets returned. That makes front-loaded completeness essential, because a returned package means you do not start the clock and you absorb the delay and the rework.
None of this is brand new in spirit. Longstanding FAA guidance in Order 8900.1 has provided that when items required for the formal application are missing or incomplete, the FAA notifies the applicant by letter, states the reasons for the rejection and the corrective action needed, and may either return the application or hold it until the applicant supplies what is missing. The 2025 notice sharpens and standardizes that posture across certificate types. Either way, the message to an applicant is identical: submit a complete, conforming package, or expect it back.
It helps to see where “acceptance” sits in the FAA’s overall certification flow. The agency describes a five-phase, three-gate process — and the completeness test bites hardest at the transition from Pre-application into Formal Application:
Phase 1 — Pre-application (Gate 1)
You request access to the FAA's Safety Assurance System (SAS) external portal, submit a Pre-application Statement of Intent (FAA Form 8400-6) to your Flight Standards office, the FAA evaluates resource availability, and you attend a pre-application meeting. Completing this phase clears Gate 1. Decisions here — the operations and aircraft you propose — define what your package must later document.
Phase 2 — Formal Application (Gate 2) — where completeness is tested
You submit the formal application letter and the required documents: the schedule of events, the compliance statement, your manuals (General Operations Manual and General Maintenance Manual), training curricula, management personnel qualifications, and supporting documents. This is the gate the complete-application policy guards. Under 14 CFR §119.35 the application is due at least 90 days before intended operation — and if the package is incomplete or non-conforming, it is returned rather than accepted.
Phase 3 — Design Assessment
Once accepted, the FAA reviews your manuals and documents in depth for compliance and conformity to safe operating practices. Gaps that survived intake surface here as revision cycles — another reason a clean, consistent package up front saves time later.
Phase 4 — Performance Assessment
The FAA validates that your procedures and programs work in practice — that crews are trained and directed effectively and operations match the manuals.
Phase 5 — Administrative Functions
The FAA issues the certificate and your operations specifications (OpSpecs). You arrive here only after a complete, conforming package cleared every prior gate.
The five-phase model is FAA guidance, not regulatory text, and the agency can revise it — confirm the current process with your Flight Standards office. For a fuller walk through the journey and the documents the FAA issues at the end, see how to get a Part 135 certificate, how long Part 135 certification takes, and operations specifications (OpSpecs) explained.
The Documentation Gaps That Get Packages Returned
The FAA describes the causes of incomplete or insufficient applications qualitatively, so what follows is a categorical map of the recurring documentation gaps — not a ranked statistic. Every one of these is a completeness or consistency problem, which is exactly why they are within your control to prevent before you submit.
Missing or non-conforming manuals
Most commonThe General Operations Manual and General Maintenance Manual are incomplete, internally inconsistent, or simply not written to be acceptable to the FAA. The General Operations Manual is required under 14 CFR §135.21 for operators using more than one pilot, and the formal application package depends on it. A manual that is thin, copied from a template without tailoring to your operation, or contradicted by your other documents is a classic reason a package comes back.
An incomplete or vague compliance statement
CommonThe compliance statement is where you map each applicable regulation to how, specifically, you comply with it. A compliance statement that is vague, skips applicable rules, or points to a manual section that does not actually contain the procedure is an incompleteness finding. Reviewers read this document as the index to your whole package — if it does not hold together, the package does not either.
Required management personnel problems
CommonThe Director of Operations, Chief Pilot, and (where applicable) Director of Maintenance must be named, qualified, and documented — with resumes and qualification records attached. 14 CFR §119.69 sets the management-personnel and qualification framework. A missing resume, an unfilled role, or a person who does not clearly meet the qualification requirements is a frequent cause of a returned package.
Incomplete ownership & U.S.-citizenship documentation
Eligibility14 CFR §119.36 requires a signed statement of ownership and management information for Part 135 applicants, and U.S.-citizen ownership and control requirements apply. Incomplete ownership disclosures, missing 5%-or-more stockholder information, or documentation that does not satisfy the citizenship and control tests is an intake problem before it is anything else.
An unrealistic or incomplete schedule of events
CommonThe schedule of events is your proposed timeline for completing the certification milestones. A schedule that is missing, internally inconsistent, or plainly unrealistic relative to the work remaining signals an incomplete package and invites it back. It also has to square with the 90-day-minimum lead time in 14 CFR §119.35.
Documents that contradict each other
ConsistencyEven when each document exists, the package is returned if the pieces disagree — aircraft documents that do not match the manuals, requested operations specifications that exceed what the manuals support, or a compliance statement that references procedures the manual does not contain. Internal consistency is part of completeness; a self-contradicting package is an incomplete one.
The pattern behind every gap
To go deeper on the two gaps that bite hardest, see the required management personnel qualifications and the General Operations / Maintenance Manual requirements — and note that a single-pilot operator has a different (and smaller) documentation footprint than a standard certificate holder.
Can you see, at a glance, whether your application package is actually complete?
FileFlo does not file your application or write your manuals — but it gives your manuals, compliance statement, management resumes, schedule of events, and aircraft documents one version-controlled, classified home, so you can see what is present, what is current, and what is still missing before you submit. That is exactly the completeness check a returned-for-incompleteness policy demands. Starter at $89/mo, Professional at $299/mo. 5-day free trial, no credit card required.
Returned vs. Denied vs. Withdrawn: Why the Words Matter
People use “rejected,” “returned,” and “denied” interchangeably, but they describe different things — and the everyday risk for an applicant is the most preventable one. Here is the plain-English difference. (The exact procedural consequences for your specific situation are a question for your aviation attorney and your Flight Standards office, not a blog post.)
Returned (incomplete / non-conforming)
The everyday riskThe FAA did not accept the package because it was incomplete or not in an acceptable form and manner. This is the situation the 2025 policy and longstanding 8900.1 guidance address: the agency notifies you, states the reasons and corrective action, and sends the package back (or holds it) to be completed and resubmitted. It is a documentation problem — and almost entirely within your control to prevent.
Denied (adverse action on the merits)
Formal adverse actionA denial is a more formal adverse action on an application the FAA did consider. It is a substantively different posture from a returned package, and it carries its own procedural rights and consequences. Most first-time applicants never reach a denial — they hit returned-for-incompleteness first. If denial is genuinely in play, that is squarely attorney territory.
Withdrawn / concluded (applicant-driven)
You stop, or stallFAA guidance contemplates that an applicant may withdraw an application at any point in the process, and that the FAA may conclude a certification project if the applicant does not proceed or does not meet the applicable 14 CFR requirements. This is less an adverse action than an acknowledgment that a project that has stalled or been abandoned will be closed out.
The takeaway for applicants
You will almost certainly meet the returned-for-incompleteness risk long before you ever meet a denial. So the single most valuable thing you can do is make your package impossible to return for a documentation reason: every required document present, current, conforming, and consistent — on the day you submit. That is a completeness discipline, and it is precisely what tools, checklists, and version control exist to enforce.
Related reading: Part 91 vs Part 135: compensation or hire · Illegal charter & the FAA grey-charter crackdown · Buying an existing Part 135 certificate · Part 135 certificate types
How to Get Accepted on the First Pass
You cannot control the FAA’s workload, but you can control whether your package gives the agency any reason to send it back. Under a complete-or-returned policy, that is the whole game. Here is the practical discipline that keeps a package from bouncing.
Build for completeness
- Assemble the package against the formal-application requirements and your own compliance statement — every required document present.
- Have required management personnel hired and qualified, with resumes and qualification records attached, before the formal application.
- Tailor manuals to your actual operation — never submit an untailored template.
- Confirm the current form-and-manner expectations with your Flight Standards office.
Build for consistency & control
- Make manuals, schedule of events, aircraft documents, and requested OpSpecs all tell the same story.
- Version-control the package so the submitted copy is unambiguously current — no stray superseded drafts.
- Cross-check the compliance statement against the manual sections it cites — every pointer must resolve.
- Do a completeness pass against a checklist before you submit, not after the FAA tells you what is missing.
The cheapest hour you will spend on certification
A returned package does not just cost you the resubmission — it costs you the delay, and every month of carrying management personnel and aircraft you absorb while you fix and resend. A disciplined completeness-and-consistency pass before you submit is the single cheapest, highest-leverage hour in the whole process. For the line-item view of what rework does to your budget, see how much a Part 135 certificate actually costs.
Where FileFlo fits — and where it does not
This is the right place to be precise about what FileFlo does. FileFlo is a compliance document intelligence platform: it classifies, indexes, version-controls, and tracks expirations on the documents you produce. For a Part 135 applicant, that maps directly onto the completeness problem this whole article is about. Your manuals, compliance statement, management resumes, schedule of events, ownership documents, and aircraft and OpSpecs records live in one organized, version-controlled place — so the question “is this package actually complete and current?” has a visible answer before you submit, instead of after the FAA returns it.
FileFlo is the completeness layer, not the certification consultant
To be unambiguous: FileFlo does not file your application, write your manuals, obtain your certificate, conform your aircraft, interact with the FAA, broker any deal, or provide legal, financial, or tax advice. Your certification team, your required management personnel, and your aviation attorney own that work. What FileFlo does is make it far harder to submit an incomplete or inconsistent package — and, after certification, it keeps the operating records you must maintain audit-ready for the life of the certificate. The FAA decides whether to accept and issue; keeping the record that proves your readiness complete, current, and consistent is the document problem FileFlo solves. (FileFlo does not claim SOC 2 certification.)
Once the certificate is issued, the same completeness discipline carries into operations. See what records a Part 135 operator must keep, the pilot records the FAA requires, and how to prepare for a Part 135 surveillance audit — because the audit is just the completeness test repeated, every year, for the life of the operation.
Frequently Asked Questions
Why are Part 135 applications rejected?
Most Part 135 applications are not rejected on the merits of the operation — they are returned because they are incomplete or not submitted in the form and manner the FAA requires. Under FAA policy issued in 2025 (Notice N 8900.735, "Disposition of Incomplete or Insufficient Air Operator and Air Agency Certification Applications"), the FAA will not accept an application package that is missing required documents or that does not meet the form-and-manner standard of 14 CFR §119.35. The most common documentation gaps are missing or non-conforming manuals (the General Operations Manual and General Maintenance Manual), an incomplete compliance statement, missing or unqualified required management personnel and their resumes, an unrealistic schedule of events, and supporting documents that contradict each other. The operation can be perfectly viable and still have its application package returned for being incomplete — which is why completeness, not just compliance, is what gets you past the gate.
Does the FAA return incomplete Part 135 applications?
Yes. In 2025 the FAA formalized a stricter intake posture. FAA Notice N 8900.735, effective May 22, 2025, states the agency will no longer accept applications that are incomplete or not submitted in a form or manner acceptable to the Administrator, and a companion Federal Register notice (June 3, 2025, "Changes to Application for Certification Process") describes the same change. The policy applies across multiple certificate types, including 14 CFR Part 135. Separately, FAA guidance in Order 8900.1 has long provided that if items required for the formal application are missing or incomplete, the FAA notifies the applicant by letter, states the reasons and the corrective action needed, and may return the application or hold it until the applicant supplies what is missing. The practical effect is the same: an incomplete package does not start the clock — it bounces.
What is the FAA complete-application policy?
The "complete application" policy is the FAA's 2025 tightening of how it accepts certification applications. It is FAA policy and guidance — not a new section of the Code of Federal Regulations. Under FAA Notice N 8900.735 (effective May 22, 2025) and the related Federal Register notice, the FAA will no longer accept an application that is incomplete or not submitted in a form or manner acceptable to the Administrator. The underlying regulatory hook is 14 CFR §119.35, which requires applications to be submitted "in a form and manner prescribed by the Administrator" and at least 90 days before the date of intended operation. In plain terms: the FAA expects a complete, conforming package up front, and an applicant who submits a partial or non-conforming package should expect it to be returned rather than worked on. Always confirm the current version of this policy with your Flight Standards office, because notices are updated and superseded over time.
What are the most common reasons a Part 135 application gets rejected or returned?
In practice, the recurring documentation gaps cluster into a handful of categories: (1) Missing or non-conforming manuals — the General Operations Manual and General Maintenance Manual are incomplete, internally inconsistent, or not written to be acceptable to the FAA; (2) An incomplete or vague compliance statement that does not map each applicable regulation to how you comply; (3) Required management personnel problems — the Director of Operations, Chief Pilot, or Director of Maintenance is missing, unqualified, or has no resume or qualification record attached, per 14 CFR §119.69; (4) Ownership and citizenship documentation that is incomplete or does not satisfy the U.S.-citizen ownership and control requirements tied to §119.36; (5) An unrealistic or incomplete schedule of events; and (6) Aircraft and operations documents that contradict the manuals or the requested operations specifications. Note that the FAA describes causes qualitatively; there is no published "top reasons" statistic to cite, and you should be skeptical of any source that invents one.
Is an incomplete application the same as a denied application?
Not exactly, and the distinction matters. Returning an incomplete or non-conforming application package — the situation the 2025 FAA policy and longstanding 8900.1 guidance address — generally means the FAA did not accept the package to begin with and is sending it back for you to complete and resubmit. A denial is a more formal adverse action on an application the FAA did consider. FAA guidance also contemplates that an applicant may withdraw an application at any point, and that the FAA may conclude a certification project if the applicant does not proceed or does not meet the applicable 14 CFR requirements. For your purposes as an applicant, the everyday risk is the first one — a package returned for being incomplete — and it is almost entirely within your control to prevent. The exact procedural consequences for your situation are a question for your aviation attorney and your Flight Standards office, not a blog post.
How do I avoid having my Part 135 application returned by the FAA?
Treat completeness as a discipline, not an afterthought. Build your application package against the formal-application requirements and your own compliance statement so that every required document is present, current, internally consistent, and conforming before you submit. Have your required management personnel hired and qualified — with resumes and qualification records attached — before the formal application, not after. Make sure your manuals, your schedule of events, your aircraft documents, and your requested operations specifications all tell the same story. Keep the package version-controlled so the copy you submit is unambiguously the current one and nothing references a superseded draft. And confirm the current form-and-manner expectations with your Flight Standards office, because the 2025 policy raised the bar on intake. The single highest-leverage move is eliminating the contradictions and gaps a reviewer can spot in the first pass — that is what gets a package accepted instead of returned.
Does FileFlo file my Part 135 application or get me certified?
No. FileFlo does not file your application, write your manuals, obtain your certificate, conform your aircraft, or interact with the FAA — and it does not give legal, financial, or tax advice. Those functions belong to your certification team, your required management personnel, and your aviation attorney. FileFlo is a compliance document intelligence platform: it classifies, indexes, version-controls, and tracks expirations on the documents you produce. For an applicant, that means your application package — manuals, compliance statement, management resumes, schedule of events, aircraft and OpSpecs documents — lives in one organized, version-controlled place where you can see at a glance what is present, what is current, and what is still missing before you submit. FileFlo is the completeness and document-readiness layer that helps you avoid a returned package; it is not the consultant that gets you certified. (FileFlo does not claim SOC 2 certification.)
Where can I read the actual FAA policy on incomplete applications?
The 2025 policy is FAA Notice N 8900.735, "Disposition of Incomplete or Insufficient Air Operator and Air Agency Certification Applications" (effective May 22, 2025), with a companion Federal Register notice titled "Changes to Application for Certification Process" published June 3, 2025. The longer-standing procedural guidance on accepting or rejecting a formal application — including notifying the applicant by letter with the reasons and required corrective action — lives in FAA Order 8900.1. The regulatory anchor for the form, manner, and 90-day timing of the application is 14 CFR §119.35, and the Part 135-specific application contents are in 14 CFR §119.36. Notices and orders are guidance that the FAA updates and supersedes over time, so treat any specific notice number as a starting point and confirm the current version with your Flight Standards office before you rely on it.
Don’t let an incomplete package cost you months
Under the FAA’s complete-or-returned policy, the surest way to lose time is to submit a package with a missing document, a non-conforming manual, or two records that contradict each other. FileFlo organizes and version-controls your Part 135 application documents so you can prove completeness before you submit — then keeps your pilot, maintenance, training, and authorization records audit-ready for the life of the certificate. AI document classification. 600+ document types. One-click FAA surveillance binder. Starter at $89/mo, Professional at $299/mo. No credit card required for the 5-day free trial. FileFlo does not get you certified or give legal advice — it organizes and proves your compliance documents.
5-day free trial · No credit card required · Cancel anytime
Continue your Part 135 certification reading
Reviewed by Chad Griffith, Founder, FileFlo — compliance document intelligence. Last reviewed June 15, 2026. The form-and-manner and 90-day formal-application requirements are verified against the Cornell Legal Information Institute eCFR (14 CFR §119.35); the Part 135 application contents against §119.36; the General Operations Manual requirement against §135.21; and the management-personnel framework against §119.69. The 2025 complete-application policy (FAA Notice N 8900.735, “Disposition of Incomplete or Insufficient Air Operator and Air Agency Certification Applications,” effective May 22, 2025, and the related Federal Register notice “Changes to Application for Certification Process,” June 3, 2025) and the formal-application rejection-letter procedure (FAA Order 8900.1) are FAA guidance and policy, not regulatory text, and the FAA updates and supersedes them over time — confirm the current version with your Flight Standards office. No rejection-rate statistic is asserted; the FAA describes causes qualitatively. Not legal, financial, or tax advice.