Operational Control in Part 135: Who Really Owns the Go/No-Go Decision?

It is 11 p.m. The charter client’s assistant is on the phone insisting the aircraft depart in 45 minutes despite a line of thunderstorms moving across the departure corridor. The broker has already told the client the flight is confirmed. The PIC is standing on the ramp looking at the sky. The Director of Operations’ phone is ringing. Who actually makes the call — and who is legally accountable if the wrong person does?

The answer is rooted in a concept that every Part 135 professional should be able to articulate under pressure: operational control in Part 135 belongs to the certificate holder. Not the customer. Not the broker. Not even the pilot in command acting alone. Understanding who owns the go/no-go decision in aviation — and training your team to exercise that authority under real-world pressure — is one of the most consequential safety and compliance challenges in charter operations today.

What Operational Control Actually Means Under Part 135

14 CFR Part 1 defines operational control Part 135 as the authority to initiate, conduct, or terminate a flight. That definition is deceptively compact. It means that the entity holding operational control bears legal and safety responsibility for every decision that affects whether a flight happens, how it proceeds, and when it ends.

Under 14 CFR Part 135, the FAA assigns that authority exclusively to the certificate holder. The certificate holder must identify — by name or position — the personnel authorized to exercise Part 135 operational control in the operations manual required by § 135.21. This is not a suggestion or best practice. It is a regulatory mandate that determines who has operational control in Part 135 charter operations.

ICAO offers a useful expansion of this concept by framing operational control across four phases: initiation, continuation, diversion, and termination. That framework reminds us that certificate holder authority is not limited to a pre-departure go/no-go moment. It spans the entire flight lifecycle — from the decision to release a flight, through en-route weather changes and diversion scenarios, to the decision to land or return.

This distinction matters because it repositions operational control Part 135 from a paperwork exercise to what it actually is: a legally binding safety framework. Every crew briefing, every weather evaluation, every maintenance deferral decision operates within this framework — whether the people making those decisions recognize it or not.

The Certificate Holder, the Director of Operations, and the PIC: Who Does What?

The operational control decision chain in Part 135 involves three distinct roles. Each carries specific responsibilities. None operates in isolation, and understanding how they interact is essential to sound aeronautical decision-making and charter operational control compliance.

Certificate Holder: The Legal Owner

The certificate holder is the regulatory owner of operational control. This entity — the company or individual holding the Part 135 certificate — is accountable for the legality and safety of every flight it conducts. That accountability covers crew assignment, flight release, weather evaluation, maintenance coordination, and airworthiness verification. The Part 135 certificate holder operational control responsibilities cannot be contracted away, outsourced to a broker, or transferred to an aircraft owner through a management agreement.

Director of Operations: The Delegated Decision Maker

The Director of Operations serves as the delegated responsible manager who administers operational control on behalf of the certificate holder day-to-day. The DO oversees flight release procedures, manages crew assignments and readiness, and ensures that each flight meets regulatory and company safety standards. The director of operations role in Part 135 operational control is critical — but delegation does not transfer legal accountability. The DO acts under the certificate holder’s authority, and authorized DO personnel must be identified by name or position in the operations manual per § 135.21.

Think of the DO as the operational decision maker within a framework the certificate holder owns. The DO’s authority is real and consequential, but it derives from the certificate, not from the individual.

PIC: Final Authority in the Air — and on the Ramp

The PIC holds final authority during the flight, and that authority includes a powerful and non-negotiable duty under § 135.109: when hazardous conditions are known, the certificate holder or PIC must restrict or suspend operations until those conditions are corrected. The PIC may not continue toward the intended landing airport under hazardous conditions unless conditions can reasonably be expected to improve by ETA, or no safer procedure exists.

If continuation becomes necessary despite those hazards, the situation invokes emergency authority under § 135.19. This is not routine decision-making — it is an emergency declaration with corresponding reporting obligations.

The pilot in command authority in the go/no-go decision aviation context is powerful, but it operates within the broader operational control framework. The PIC’s authority does not replace the certificate holder’s responsibility — it complements it. Both the certificate holder and the PIC share the duty to halt operations when conditions demand it.

Flight Release Procedures: The Operational Control Workflow in Practice

If operational control Part 135 is the legal framework, flight release procedures are its documented, auditable expression. A compliant Part 135 operator should follow a structured sequence before authorizing any flight departure:

• Risk review: Evaluate the overall risk profile of the flight — route, time of day, terrain, airspace complexity, and any known operational hazards.
• Weather evaluation: Assess current and forecast weather for departure, en route, destination, and alternate airports against company and regulatory minimums.
• Aircraft status and airworthiness: Confirm the aircraft is airworthy, including review of any MEL deferrals and their operational impact on the planned flight.
• Crew legality and fitness: Verify duty-time compliance, rest requirements, and crew readiness — including any late-breaking fatigue or fitness-for-duty concerns.
• Explicit release by an authorized person: The flight is released by a person identified in the Part 135 operations manual as authorized to exercise operational control.

Some operators adopt layered or joint release processes internally — requiring concurrence from both a dispatcher-type role and the PIC, for example. This is a sound safety design choice, but it does not alter the regulatory structure: the certificate holder retains Part 135 operational control, and release authority must flow through the documented chain.

The value of a risk-based go/no-go process is that it makes operational control visible and auditable. When every flight release follows a documented workflow, the operation can demonstrate compliance — and more importantly, it can identify where the decision chain broke down if something goes wrong. For operators building or auditing their flight release procedures Part 135 charter workflows, CTS’s Part 135 Training program includes structured modules on operational control documentation and compliance.

The Gray Zone: Brokers, Customers, and the Pressure to Go

Here is where operational control Part 135 moves from regulation to reality — and where the greatest compliance risk lives.

When a broker calls to say the client needs to depart in 30 minutes despite deteriorating weather, who makes the call? When an aircraft owner insists the plane should fly because “it’s my airplane,” who has authority? When a sales representative confirms a trip to a customer before the DO has reviewed the weather, who bears the liability?

The answer in every case: the certificate holder retains operational control. In practice, three persistent misconceptions erode that principle.

Misconception 1: The customer who pays can decide whether the flight goes. They cannot. A charter customer can request a flight, specify a destination, and choose a departure time — but the certificated operator makes the release decision. “Who pays” does not equal “who controls” — a distinction reinforced consistently in FAA enforcement actions and aviation legal commentary.

Misconception 2: A broker or sales representative can approve a trip if the operator is busy. Brokers do not hold operational control under Part 135. They facilitate transactions; they do not release flights. The moment a broker’s confirmation substitutes for an authorized operator’s release, the operation has a gray charter compliance problem — and potentially an illegal charter on its hands.

Misconception 3: An SMS or automated tool can replace the authorized human decision maker. AI tools, risk platforms, and automated weather analysis can support decisions. They do not replace the required human authorized decision maker. The operational control Part 135 structure demands accountability that software cannot provide.

The enforcement stakes are real. Operational control failures are most commonly surfaced in illegal charter and gray-charter enforcement actions, and the consequences include certificate suspension or revocation. Truth-in-leasing violations, improper management agreements, and undocumented broker influence on flight departure legality are among the most aggressively pursued enforcement areas in charter aviation.

The pressure to go will always exist. The question is whether your operation has built the training, documentation, and culture to withstand it.

Training the Decision: How to Build Operational Control Competency

Naming someone in the operations manual satisfies a regulatory requirement. It does not guarantee that person can exercise Part 135 operational control under pressure at 11 p.m. with a high-value client on the phone and a line of thunderstorms on the radar.

The gap between “having a manual” and “having a trained team” is where operational control fails in the real world. Closing that gap requires training that goes beyond regulatory awareness to build genuine aeronautical decision-making competency. Effective Part 135 operational control training should include scenario-based exercises across the decision types that matter most:

• Borderline weather and runway contamination: Conditions that are technically legal but operationally marginal — the decisions that test judgment, not just regulatory knowledge.
• Maintenance deferrals and MEL decision-making: Understanding when a deferral is acceptable and when accumulated deferrals create unacceptable risk.
• Customer and broker pressure to depart: Practicing the communication and authority required to decline a flight when external pressure is high.
• Late-breaking crew fatigue or duty-time issues: Recognizing that stop-work authority Part 135 crew members hold is not theoretical — it must be exercised when fatigue compromises safety.
• Diversion and continuation decisions en route: Applying § 135.109 in real time when conditions change after departure.

SMS integration with flight release procedures is essential to making this work. A well-designed safety management system program connects hazard reporting, risk matrices, and stop-work authority directly to the go/no-go decision, so every crew member and authorized manager understands that any safety gate can halt a flight — and that exercising that gate is expected, not penalized.

Compliance training should also address gray-charter avoidance and truth-in-leasing concepts, because misunderstanding the boundary between legitimate charter and unauthorized operations is one of the fastest paths to certificate action.

Closing the competency gap requires structured, scenario-based training that goes beyond regulatory awareness to build real decision-making muscle. Explore CTS’s Part 135 Training program for scenario-based e-learning that prepares your pilots, Directors of Operations, and safety personnel to own the go/no-go decision with confidence and regulatory compliance.

Key Takeaways: Operational Control Part 135 Is a Safety Behavior, Not Just a Regulation

Part 135 operational control is not a paperwork formality. It is a legally binding safety framework that determines who is accountable for every flight your operation conducts. The certificate holder owns it. The DO administers it. The PIC exercises final authority under hazardous conditions. No external party — customer, broker, or aircraft owner — can legally override that chain.

• Operational control Part 135 is defined as the authority to initiate, conduct, or terminate a flight — and it belongs to the certificate holder.
• The certificate holder must identify authorized personnel in the operations manual per § 135.21.
• The PIC has a duty to restrict or suspend operations under hazardous conditions per § 135.109 — a power that is critical but does not replace certificate holder accountability.
• Brokers, customers, and automated tools do not hold operational control and cannot replace the required authorized human decision maker.
• Operational control failures carry certificate-level enforcement risk, including suspension or revocation.

Operational control is a lived safety behavior that must be trained, documented, and defended — every flight, every day. Build that competency with CTS’s Part 135 Training program.

Frequently Asked Questions

Who has operational control in a Part 135 charter flight?
The certificate holder retains Part 135 operational control for every charter flight it conducts. The customer or broker may request the flight, but the certificated operator makes all release, continuation, and termination decisions. This responsibility cannot be transferred through a management agreement or brokerage arrangement.

What is the difference between operational control and PIC authority in Part 135?
Operational control is the certificate holder’s legal responsibility for initiating, conducting, and terminating flights. PIC authority under § 135.109 gives the pilot in command the duty to restrict or suspend operations when hazardous conditions exist. The PIC’s authority is powerful but operates within — not above — the certificate holder’s operational control framework.

Can a charter broker or customer authorize a Part 135 flight release?
No. Brokers do not hold operational control under 14 CFR Part 135. Only personnel identified in the certificate holder’s operations manual as authorized to exercise operational control may release a flight. A broker confirming a trip to a client does not constitute a valid flight release.

What does 14 CFR § 135.109 say about go/no-go decisions under hazardous conditions?
Section 135.109 requires the certificate holder or PIC to restrict or suspend operations when hazardous conditions are known. The PIC may not continue toward the intended landing airport unless conditions can reasonably be expected to improve by ETA or no safer procedure exists. If continuation is necessary despite the prohibition, the situation constitutes an emergency under § 135.19.

How should a Part 135 operator document operational control in their operations manual?
Under § 135.21, the operations manual must identify — by name or position — all personnel authorized to exercise operational control. The manual should also document flight release procedures, director of operations responsibilities, risk assessment workflows, and the authority chain for go/no-go decisions. For comprehensive Part 135 operational control training, visit CTS’s Part 135 Training program.