793
Federal Aviation Administration, DOT
§ 91.1033
(3) The maximum allowable takeoff
weight for that flight;
(4) The center of gravity limits;
(5) The center of gravity of the load-
ed aircraft, except that the actual cen-
ter of gravity need not be computed if
the aircraft is loaded according to a
loading schedule or other approved
method that ensures that the center of
gravity of the loaded aircraft is within
approved limits. In those cases, an
entry must be made on the manifest in-
dicating that the center of gravity is
within limits according to a loading
schedule or other approved method;
(6) The registration number of the
aircraft or flight number;
(7) The origin and destination; and
(8) Identification of crewmembers
and their crew position assignments.
(d) The pilot in command of the air-
craft for which a load manifest must be
prepared must carry a copy of the com-
pleted load manifest in the aircraft to
its destination. The program manager
must keep copies of completed load
manifest for at least 30 days at its prin-
cipal operations base, or at another lo-
cation used by it and approved by the
Administrator.
(e) Each program manager is respon-
sible for providing a written document
that states the name of the entity hav-
ing operational control on that flight
and the part of this chapter under
which the flight is operated. The pilot
in command of the aircraft must carry
a copy of the document in the aircraft
to its destination. The program man-
ager must keep a copy of the document
for at least 30 days at its principal op-
erations base, or at another location
used by it and approved by the Admin-
istrator.
(f) Records may be kept either in
paper or other form acceptable to the
Administrator.
(g) Program managers that are also
certificated to operate under part 121
or 135 of this chapter may satisfy the
recordkeeping requirements of this sec-
tion and of § 91.1113 with records main-
tained to fulfill equivalent obligations
under part 121 or 135 of this chapter.
§ 91.1029
Flight scheduling and locat-
ing requirements.
(a) Each program manager must es-
tablish and use an adequate system to
schedule and release program aircraft.
(b) Except as provided in paragraph
(d) of this section, each program man-
ager must have adequate procedures es-
tablished for locating each flight, for
which a flight plan is not filed, that—
(1) Provide the program manager
with at least the information required
to be included in a VFR flight plan;
(2) Provide for timely notification of
an FAA facility or search and rescue
facility, if an aircraft is overdue or
missing; and
(3) Provide the program manager
with the location, date, and estimated
time for reestablishing radio or tele-
phone communications, if the flight
will operate in an area where commu-
nications cannot be maintained.
(c) Flight locating information must
be retained at the program manager’s
principal base of operations, or at
other places designated by the program
manager in the flight locating proce-
dures, until the completion of the
flight.
(d) The flight locating requirements
of paragraph (b) of this section do not
apply to a flight for which an FAA
flight plan has been filed and the flight
plan is canceled within 25 nautical
miles of the destination airport.
§ 91.1031
Pilot in command or second
in command: Designation required.
(a) Each program manager must des-
ignate a—
(1) Pilot in command for each pro-
gram flight; and
(2) Second in command for each pro-
gram flight requiring two pilots.
(b) The pilot in command, as des-
ignated by the program manager, must
remain the pilot in command at all
times during that flight.
§ 91.1033
Operating information re-
quired.
(a) Each program manager must, for
all program operations, provide the fol-
lowing materials, in current and appro-
priate form, accessible to the pilot at
the pilot station, and the pilot must
use them—
(1) A cockpit checklist;
VerDate Mar<15>2010
20:48 Jan 30, 2014
Jkt 232047
PO 00000
Frm 00803
Fmt 8010
Sfmt 8010
Q:\14\14V2.TXT
ofr150
PsN: PC150