FOM Captain Statements 12 APR 24 Flashcards
Learn about Captain FOM statements at United
The Captain must verify via FMC/FMGC that the FAR fuel requirements
are met prior to accepting revision.
QRG.10.11
All crewmembers must certify their individual Fitness for Duty (FFD) by stating
to the Captain they are fit, and the Captain must concur. The Captain will then
accept or decline the extension request. Acceptance of the extension is a reaffirmation
of FFD. The flight’s takeoff roll must be initiated by the CCO time, or
the flight must not take off. Contact Dispatch or return to the gate.
1.50.10
ENGINE FAILURE OR SHUTDOWN
If an engine failure or shutdown occurs on a two-engine aircraft, diversion is
required to the nearest suitable airport, in point of time, where a safe landing
can be made (FAR 121.565). The Captain must notify ATC and Dispatch as
soon as possible, provide reason for the engine
2.10.9
ENGINE ANOMALIES
When an engine anomaly occurs that does not require shutdown (e.g, vibration,
temperature exceedance, overheat, loss of oil quantity), a diversion to the
nearest suitable airport is not required but the Captain must notify Dispatch and
TOMC as soon as possible to discuss the appropriate course of action.
2.10.9
DEPLANING OF AN ILL OR INJURED PERSON
When it is necessary to deplane a person who is ill or otherwise unable to care
for oneself, the Captain must ensure care is provided until the custody of the
person is transferred to other qualified persons or agencies.
2.20.8
Emergencies/Non-Normals
If diversion to an undesignated or emergency airport is required, the Captain
must exercise emergency authority. Additionally, airports designated as
emergency airports are typically only issued a single approach chart which may
cause problems depending on the current wind or navaid status.
None of the guidance provided above precludes the definition of Adequate
Airport in the Glossary as they apply to ETOPS.
2.30.2
Emergencies/Non-Normals
DISPATCH NOTIFICATION
When it becomes necessary to consider a diversion, including if going to a
designated alternate, the Captain must make every effort to confer with the
dispatcher. This coordination allows the two jointly responsible individuals to
assure themselves that the best course of action under the circumstances is
used.
2.30.3
Emergencies/Non-Normals
While the Captain must determine the safest course of action to best safeguard
the flight, consider maintaining a position midway between known oceanic
tracks at an altitude between normally assigned flight levels until a revised
clearance is received.
Following a gross navigation error, the Captain must:
Submit an IOR.
Provide the Master Flight Plan or Master Flight Log and a copy of the EFB
orientation chart to the Chief Pilot.
Email a screenshot of the EFB plotting chart or a picture of the paper
orientation chart to GNE@united.com.
2.50.7
Emergencies/Non-Normals
CAPTAIN AND DISPATCHER JOINT RESPONSIBILITIES
The Captain and the dispatcher are jointly responsible for the preflight planning,
delay, Dispatch Release, and if appropriate, the redispatch of a flight (FARs
121.533, 121.535).
The Captain must not allow a flight to continue toward any airport to which it has
been released if, in the opinion of the Captain or the dispatcher, the flight cannot
be operated safely; unless, in the opinion of the Captain, there is no safer
procedure. In that event, continuation toward that airport is an emergency
situation and requires the use of emergency authority as defined in this section
(FAR 121.627).
3.10.1
Operating Information
CAPTAIN EMERGENCY AUTHORITY
In an emergency situation that requires an immediate decision and action, the
Captain may take any action considered necessary under the circumstances. In
such cases, the Captain may deviate from prescribed operations, procedures
and methods, weather minimums, and other regulations governing the operation
to the extent required in the interest of safety (FAR 121.557[a]).
The FAR requires the FAA to be notified of the exercise of Captain emergency
authority and any deviation that results from it; therefore, the Captain must
complete the appropriate Company reports as outlined in the Communications
chapter.
3.10.4
Operating Information
Authority & Responsibility
When CDR operations are initiated, the code for the new route is assigned by
Ground or Tower prior to takeoff. Read back the code with the flight number. If
the CDR route is not found on the Flight Plan or FMC/FMGC, request a full
route clearance from ATC. A desire to rejoin the original route must be pilotinitiated
and include the details of the route desired. (ATC understands that a
return to the original route is generally desirable, once the flight is clear of
conflicting weather or traffic.) The Captain must verify via FMC/FMGC that the
new route meets FAR fuel requirements, prior to accepting the revision. See the
following CDR Dispatch Reporting Requirements section.
CPDLC-DCL Reroutes The Captain must verify via FMC/FMGC that the FAR
fuel requirements are met prior to accepting the reroute. See the following CDR
Dispatch Reporting Requirements section.
3.40.8
Operating Information
Flight Planning
CLOSING THE CABIN DOOR FOR DEPARTURE
The Captain must consider all factors before allowing the cabin door to be
closed for departure. For example, the cabin door should remain open until
movement of the aircraft is imminent to prevent an inaccurate tarmac delay start time. Moreover, if a lengthy delay on the gate is anticipated, the tarmac delay
start time is delayed as long as the passengers are allowed the option to
deplane, which requires an open cabin door and egress announcements.
If a significant delay is encountered after the main cabin door is closed, and the
aircraft is still at the gate (e.g., deice delays, maintenance issue), coordinate
with Customer Service to reopen the door to offer egress to the passengers.
3.50.2
Operating Information
Departure Procedures
AIRCRAFT MOVEMENT
Note: The boarding door should not be closed until fueling is complete.
The CSR will use the “Ready to go” phrase to indicate to the Captain that they
are ready to close the boarding door. The Captain must not allow aircraft
movement until:
The Purser has advised verbally that the cabin is ready.
The Purser closes the flight deck door and confirms it’s secure closed.
The Before Push Checklist has been completed.
In the event that a passenger is reported to be standing or moving in the cabin
during ground movement, it may be safer, in the Captain’s judgment, to continue
to taxi depending on the circumstances. It may not be desirable to stop an
aircraft in a manner that is not anticipated by Tower and Ground ATC personnel
or other aircraft operators in the immediate vicinity. Unanticipated aircraft
movements or stops may introduce additional safety threats.
3.50.18
Operating Information
Departure Procedures
Once the Captain relays pushback clearance to the ground crew, the Captain
must deselect ATC and Ramp.
3.50.21
Operating Information
Departure Procedures
“Breakaway” Procedures
If an aircraft inadvertently detaches from the tug, the tug driver will immediately
say, “Breakaway, breakaway” over the headset interphone. Upon hearing such
a command, the Captain must immediately apply the brakes. If the aircraft is
rolling backwards, use gentle braking effort to avoid tipping the aircraft on to its
tail. Once stopped, set the parking brake and await further instructions from the
ground crew prior to releasing the brake.
If using hand signals during pushback, Ramp personnel will give the “Stop”
hand signal to convey the “Breakaway, breakaway” message.
3.50.23
Operating Information
Departure Procedures
Reposition of an Aircraft (“Brake-Riding”)
Pilots may be required to reposition an aircraft from remote parking to the gate.
See the United Pilot Agreement (UPA) for additional information. The following
guidance applies to towing of an aircraft from remote parking to the gate with
pilots in the control seats:
The Captain must discuss the tow-in with the tug driver and ground crew.
Pilots must accomplish all normal applicable checklists, per the FM. (e.g.,
Preflight, Before Push, Tow-In).
Communication with ground personnel is established and exterior clearance
is confirmed before tow-in.
Both pilots are seated in the primary flight deck control seats.
3.70.5
Operating Information
Parking
DEPARTURE BRIEFING
The Captain must ensure the departure briefing topics below are briefed prior to
brake release. Items previously briefed during the same duty period or not
applicable to the flight need not be mentioned unless there is a pilot change.
Items covered and verified as a part of normal SOP flow (e.g., loading the FMC)
may be omitted. Any changes prior to takeoff should be rebriefed. The briefing
should be concise, tailored to the relevant threats, and focused on the big
picture.
Discuss Threats First: Personal? Environmental? Technical?
3.90.3
Operating Information
Crew Information
If the takeoff weight increase provisions above cannot be complied with, the
Captain must contact Dispatch for a review of the Flight Plan to ensure FAR
reserve fuel and Method I/II Dispatch provisions (if required) are maintained.
Dispatch must respond with either a revised Flight Plan or a message (e.g.,
OKAY TO PROCEED). The Captain may always request a revised Flight Plan
based on a new takeoff weight.
Note: If the takeoff weight decreases by 2000 pounds or greater, consider
contacting Dispatch to update the Flight Plan and ensure flight is
optimized.
4.10.5
Dispatch
Flight Planning Policy
Captain-Initiated Changes
Captains must contact Dispatch for any changes to the Flight Plan or fuel
changes greater than 2000 pounds. Changes to the planned fuel load within 45
minutes of departure (1 hour for flag flights) must be coordinated with Station
Operations, who alerts the fuelers. If the Captain coordinates with the
dispatcher to receive additional fuel (CAPT), it will not automatically be
annotated on the Flight Plan unless the request exceeded 2000 pounds, or the
Captain requests such action from the dispatcher (which will take several
minutes). If the new fuel value is not automatically updated, the Captain must
amend the copy of the Release with a write-in change to the PLAN GATE fuel
value. The final weights and HOWGOZIT will automatically reflect these fuel
adds.
4.50.3
Dispatch
Dispatch Release
Consider accepting the Release before printing or downloading the Flight Plan
package to ensure that the included Release is signed. If the Release is
subsequently signed, selecting only the Release for print or download will
provide a single copy of the first page of the Flight Plan (showing the Captain’s
acceptance). Given that dispatch planning is based on a fully qualified Captain
(C3 minimum code), the Captain is required to alert the dispatcher if they are on
high minimums via the use of the HM code when accepting the Release. The
following options, in order of preference, are available to the Captain to accept a
Release:
Electronically Using CCS>Flight Planning>Sabre FPM, Pilot Mobile, or
ACARS.
Note: “Note to Dispatcher” is non-functional.
Verbally
Provide the Captain’s name, file number, approach minimum code (i.e., C3
or HM), pilot base, and authorization to the dispatcher to accept the
Release on the Captain’s behalf. The Captain must then carry a signed
copy to the destination (e.g., either manually sign the copy, print or
download to the Pilot EFB a copy showing the Captain’s electronic
signature).
If communication with Dispatch is not possible, as occasionally occurs at
remote stations, the Captain must:
1. Have the local station representative relay the information above to
Dispatch with a request for Dispatch to electronically sign the Release
for the Captain.
2. Confirm with the dispatcher that the Release was electronically
accepted on the Captain’s behalf once communication is
reestablished, which may occur after airborne.
4.50.6
Dispatch
Dispatch Release
Flight Plan Considerations
Fuel should be planned conservatively to account for possible delays.
Inform Dispatch of any maintenance irregularity as early as possible to assist
in planning.
The Captain must monitor crew legality problems and keep Crew Scheduling
informed of any issues as early as possible for planning purposes.
Flight following is difficult and the pilots should alert the dispatcher of any
deviations or delays through any communications service available.
4.50.8
Dispatch
Dispatch Release
NO REDISPATCH
If for any reason redispatch is not possible, the terms of the original dispatch
apply, and except in an emergency, the flight must continue to the intermediate
destination and land (OpSpec B044). If the flight continues to the intermediate
destination, the pilot must obtain an amended ATC clearance to do so.
Continuing to the planned destination beyond the redispatch point without a
Redispatch Message requires the use of Captain’s emergency authority.
If all available means to obtain the Redispatch Message from Dispatch have
been exhausted and the message has not been received by the redispatch
point, the Captain must consider all factors (weather, NOTAMS, fuel,
approaches, handling, etc.) and determine whether the safest course of action
is to continue to the planned destination or divert to the intermediate destination.
In either case, continue efforts to contact and coordinate with Dispatch.
4.60.3
Dispatch
Redispatch
MRD CURRENCY
FAR 121.709 requires that after maintenance is performed on an aircraft, an
Airworthiness Release must be provided. This Airworthiness Release signifies
that maintenance was performed in accordance with the approved certificate
holder’s Maintenance Manual procedures, and further indicates the aircraft is in
condition for safe flight. Therefore, the Captain must ensure the current MRD is
on board and reviewed per the procedures in this chapter.
5.20.3
Maintenance
Maintenance Regulatory Guidance
RECORDING AND REPORTING DEFECTS
FAR 121.563 requires the Captain to ensure that all mechanical irregularities
occurring during flight time are entered in the maintenance computer system
(the electronic logbook) at the end of that flight time. Therefore, prior to leaving
the aircraft, the Captain must ensure any known defects are reported and
recorded per the defect reporting procedures in this chapter.
5.20.3
Maintenance
Maintenance Regulatory Guidance
If after review of the route, weather, MRD, DIL, and Log History, the Captain
believes the result of these combinations has rendered the aircraft inoperable
for the assigned routing, the Captain must address concerns with Dispatch and
TOMC. The dispatcher will initiate a conference call with the Captain, TOMC,
and any other personnel necessary to answer specific questions (e.g., the
FODM, operations manager, aircraft router, and the station).
5.40.3
Maintenance
Maintenance Release Procedures
If the decision to reclassify the aircraft as Unable to Operate is ultimately made,
the dispatcher and Captain will arrive at a mutual understanding regarding the
specific operational or safety reasons. After this discussion, the dispatcher will
send an Unable to Operate meter. The Captain must submit an IOR detailing
the specific operational or safety reasons for the Unable to Operate decision.
5.40.4
Maintenance
Maintenance Release Procedures
AFTER BLOCK-OUT AND PRIOR TO TAKEOFF
1. Send appropriate maintenance code or notify TOMC/HMC and confirm
receipt.
2. Verbally notify and coordinate action with the controlling Maintenance
authority (i.e., HMC or TOMC).
3. A new MRD is required prior to takeoff.
Note: If the flight deck printer is inoperative, the original paper copy of
the MRD, if available, may be amended by the pilots. TOMC will
make the required SCEPTRE entries and will give verbal
instructions for updating MRD to include:
Flight number
System to be deferred
MEL number
Dispatcher’s desk
Time stamp
TOMC Controller’s name
4. If the defect is a deferrable dispatch item, prior to takeoff:
A. TOMC is responsible for ensuring the Captain is notified of such.
B. The Captain must coordinate with Dispatch for an amended Release
(verbal, electronic, or printed).
5.50.5
Maintenance
Maintenance Reporting
AFTER BLOCK-OUT AND PRIOR TO TAKEOFF
1. Report defect details to TOMC/HMC who then advises how to proceed.
2. If a return to gate is required, use the Prior To Block-Out procedures above.
3. If the defect is deferrable without the need for a technician, then prior to
takeoff:
A. Record the defect and deferral on a NRM Fallback Log coupon and
place it in the MRD pouch. See the Sceptre ELB ACARS Unavailable
Procedures.
B. If the deferral is an MEL item, TOMC/HMC provides a verbal MEL OPS
PLACARD briefing, unless the MEL is contained in the EFB.
Note: If the MEL procedure is overly complicated such that basic
note-taking is unreasonable, return to the gate and obtain a
printed MRD which includes OPS PLACARD information.
C. If a dispatch item, the Captain must coordinate with Dispatch for a
verbal or electronic amended release (TOMC/HMC conferences in
Dispatch).
Note: The combination of the existing MRD with the Maintenance-reviewed
NRM Fallback Log coupon is the new Maintenance Release.
5.90.3
Maintenance
Sceptre ELB ACARS Unavailable
Procedures
AFTER BLOCK-OUT AND PRIOR TO TAKEOFF
1. Report defect to TOMC or GUM Maintenance.
2. If a return to gate is required, use the Prior To Block-Out procedures above.
3. If the defect is deferrable without the need for a technician, then prior to
takeoff:
A. Record the defect and deferral on a NRM coupon and place it in the
MRD pouch. See Sceptre ELB ACARS Unavailable Procedures for the
proper clearing format.
B. If the deferral is an MEL item, the Captain must review the Ops
Placard section of the applicable MEL card and comply with all
procedures.
C. If a dispatch item, the Captain must coordinate with Dispatch for a
verbal or electronic amended release (TOMC or GUM Maintenance
conferences in Dispatch).
5.95.2
Maintenance
Guam/Micronesia ACARS SATCOM
Unavailable Procedures
UNITED TAKEOFF SAFETY POLICY
In the high speed regime, especially at speeds near V1, a decision to reject
should not be based on the perceived ability that the aircraft can be stopped.
The decision to reject should be made only if the failure involved would impair
the ability of the aircraft to be safely flown. Each FM provides guidance for what
may be an appropriate reason to reject a takeoff in either the low or high speed
environments. The “100 knots” callout is the alert that the aircraft is entering the
high speed phase of takeoff, and as such, the acceptable reasons to reject a
takeoff shrink dramatically to significant safety issues (e.g., fire, engine failures
and other FM critical issues). This Takeoff Safety Policy does not advocate that
a go decision be made at or just after the “100 knots” callout. When the aircraft
has entered the high speed regime, the Captain must make the decision to stop
or go, based on the nature and severity of the malfunction and the proximity to
V1. At or beyond V1, takeoff should be continued due to the possibility of
insufficient runway available to stop the aircraft if a stop decision is made.
6.40.1
Navigation
Takeoff
ALLOWABLE TAKEOFF WEIGHTS
Note: After receipt of Final Weights, if a request for takeoff data is made that
is 2000 pounds or greater below the TOG on the Final Weight
Manifest, an ACARS Takeoff Data Warning message will be
generated. The Captain must review the takeoff data.
Before takeoff, the Captain must ensure the aircraft gross weight does not
exceed the maximum gross weight allowed by the performance calculations
used for the specific runway, flap, and bleed configuration used. Unless noted
otherwise, the runway length used for the takeoff calculation is based on the full
runway length published on the Jeppesen airport diagram pages (10-9, 20-9,
etc.). If an intersection takeoff is offered or desired, that data must be available
and verified before accepting the intersection takeoff.
6.40.2
Navigation
Takeoff
Circle-To-Land Obstacle Clearance
WARNING: Comply with all circling restrictions on the applicable
approach chart and the airport information page (10-7).
The Captain must brief terrain and obstacles in the vicinity
of the airport in the arrival briefing.
6.100.11
Navigation
General Approach Procedures
IFR CLEARANCE
The Captain must obtain a proper ATC clearance for departure from the
controlling authority (e.g., FSS, TRACON, ARTCC).
6.120.6
Navigation
No Tower Procedures
TERMINAL AREA STORM AVOIDANCE
If storm activity in the terminal area is such that recommended cell clearance
cannot be maintained, the Captain must consider the following:
Circumnavigating around the area or landing at an alternate airport.
Holding at the gate, or delaying takeoff until the Captain determines that a
safe departure can be conducted.
Takeoffs, approaches, and landings should not be attempted when
thunderstorms are near the airport, unless the runway and flight path,
including any Engine Failure Procedures, are clear of the thunderstorm
effects and its associated gust front.
7.10.8
Adverse Weather
Adverse Weather