Appendix to Section 217.10 of 14 CFR part 217 - Instructions to Foreign Air Carriers for Reporting Traffic Data on Form 41 Schedule T-100(f)

(a) General instructions.

(1) Description. Form 41 Schedule T-100(f) provides flight stage data covering both passenger/cargo and all cargo operations in scheduled and nonscheduled services. The schedule is used to report all flights which serve points in the United States or its territories as defined in this part.

(2) Applicability. Each foreign air carrier holding a 402 permit, or exemption authority, and operating aircraft with seating configurations of more than sixty seats and/or available capacity (payload of passengers and cargo) of more than 18,000 pounds shall file Form 41 Schedule T-100(f). Reference to 402 is to section 402 of the Federal Aviation Act of 1958, as amended (FAAct).

(3) Address for filing reports: Office of Airline Information, K-25, Room 4125, U.S. Department of Transportation, 400 Seventh St., SW., Washington, DC 20590.

(4) Filing period. Form 41 Schedule T-100(f) shall be filed monthly and is due at the Department thirty (30) days following the end of the reporting month to which the data are applicable.

(5) Number of copies. A single set of legible Form 41 Schedule T-100(f) data and certification shall be submitted.

(6) Foreign air carrier certification. Each foreign air carrier shall submit a certification statement (illustrated at the end of this Appendix) as an integral part of each monthly Schedule T-100(f), as prescribed in § 217.5 of this part.

(7) Alternative filing on Automatic Data Processing (ADP) media. Foreign air carriers are encouraged to use ADP equipment to reduce the manual effort of preparing Schedule T-100(f). Foreign air carriers may use the floppy disk medium. ADP submission requirements for floppy discs are prescribed in paragraph (f).

(b) Preparation of Form 41 Schedule T-100(f):

(1) Explanation of nonstop segments and on-flight markets. There are two basic categories of data, one pertaining to nonstop segments and the other pertaining to on-flight markets. For example, the routing (A-B-C-D) consists of three nonstop segment records A-B, B-C, and C-D, and six on-flight market records A-B, A-C, A-D, B-C, B-D, and C-D.

(2) Guidelines for reporting a nonstop segment. A nonstop segment is reported when one or both points are in the United States or its territories. These data shall be merged with that for all of the other reportable nonstop operations over the same segment. Nonstop segment data must be summarized by aircraft type, under paragraph (h)(1), and class of service, paragraph (g)(1)(v).

(3) Rules for determining a reportable on-flight market. On-flight markets are reportable when one or both points are within the U.S., with the following exceptions: (i) Do not report third country to U.S. markets resulting from flight itineraries which serve a third country prior to a homeland point in flights passing through the homeland bound for the U.S.; and (ii) do not report U.S. to third country markets resulting from itineraries serving third country points subsequent to a homeland point in flights outbound from the U.S. and passing through the homeland. In reporting data pertaining to these two exceptions, the traffic moving to or from the U.S. relating to the applicable prior or subsequent third countries (referred to as “behind” or “beyond” traffic) is to be combined with the applicable foreign homeland gateway point, just as though the traffic were actually enplaned or deplaned at the homeland gateway, without disclosure of the actual prior or subsequent points. Applicable flights are illustrated in examples (6) and (7) under paragraph (c).

(c) Examples of flights. Following are some typical flight itineraries that show the reportable nonstop segment and on-flight market entries. The carrier's homeland is the key factor in determining which on-flight markets are reportable.

(1) SQ flight # 11 LAX—NRT—SIN. This is an example of a flight with an intermediate foreign country. It is not necessary to report anything on the NRT—SIN leg.

SQ—Singapore Airlines LAX—Los Angeles, USA NRT—Tokyo-Narita, Japan SIN—Singapore, Singapore A-3—Airport codeOriginA-4—Airport codeDestinationA-5—Service class (mark an X)FGLPQBy aircraft type—B-1—Aircraft type codeB-2—Revenue aircraft departuresB-3—Revenue passengers transportedB-4—Revenue freight transported (kg)Sum of all aircraft types—C-1-Total revenue passengers in marketC-2—Total revenue freight in market (kg)LAX NRT X 8161 12 2400 4800 400 500LAX SIN X 2000 4300

(2) SQ flight #15 LAX— HNL— TPE— SIN. This is an example of two U.S. points, an intermediate third country, and a homeland point. Information is reportable on only the on-flight markets and nonstop segments that consist of one or both U.S. points.

SQ—Singapore Airlines LAX—Los Angeles, USA HNL—Honolulu, USA TPE—Taipei, Taiwan SIN—Singapore, Singapore A-3—Airport codeOriginA-4—Airport codeDestin-ationA-5—Service class (Mark an x)FGLPQBy aircraft type—B-1—Acft. type codeB-2—Revenue aircraft departuresB-3—Revenue passengers transportedB-4—Revenue freight transported (kg)Sum of all aircraft types—C-1—Total revenue passengers in marketC-2—Total revenue freight in market (kg)LAXHNL X 8161 12 2700 5300 0 0LAXTPE X 700 1300LAXSIN X 2000 4000HNLTPE X 8161 12 2200 6800 1200 800HNLSIN X 1000 6000

(3) LB flight # 902 LPB-VVI-MAO-CCS-MIA. This flight serves two homeland points and two different foreign countries before terminating in the U.S. Nonstop segment information is required only for the nonstop segment involving a U.S. point. On-flight market information is required in 4 of the 10 markets, LPB-MIA and VVI-MIA, since these involve homeland and U.S. points; MAO-MIA is necessary to show traffic carried into the U.S., and CCS-MIA for the same reason, and also because in all cases where a nonstop segment entry is required, a corresponding on-flight market entry must also be reported.

LB—Lloyd Aero Boliviano LPB—La Paz, Bolivia VVI—Santa Cruz-Viru Viru, Bolivia MAO—Manaus, Brazil CCS—Caracas, Venezuela MIA—Miami, USA A-3—Airport codeOriginA-4—Airport codeDestinationA-5—Service class (mark an x)FGLPQBy aircraft type—B-1—Acft. type codeB-2—Revenue aircraft departuresB-3—Revenue passengers transportedB-4—Revenue freight transported (kg)Sum of all aircraft types—C-1—Total revenue passengers in marketC-2—Total revenue freight in market (kg)CCSMIAX81613169007100000LPBMIAX110020000VVIMIAX400030000MAOMIAX100012000

(4) LY flight #005 TLV-AMS-ORD-LAX. This flight serves a single foreign intermediate point and two U.S. points after its homeland origination. The information on the TLV-AMS leg is not reportable.

LY—El Al Israel Airlines TLV—Tel Aviv, Israel AMS—Amsterdam, Netherlands ORD—Chicago, USA LAX—Los Angeles, USA A-3—Airport codeOriginA-4—Airport codeDestinationA-5—Service class (mark an x)FGLPQBy aircraft type—B-1—Acft. type codeB-2—Revenue aircraft departuresB-3—Revenue passengers transportedB-4—Revenue freight transported (kg)Sum of all aircraft types—C-1—Total revenue passengers in marketC-2—Total revenue freight in market (kg)AMSORDX8161135010000501500TLVORDX1504000TLVLAXX1253000ORDLAXX81611150450000AMSLAXX251500

(5) QF flight #25 SYD—BNE—CNS—HNL—YVR. This flight serves three homeland points, a U.S. point, and a subsequent third country. Nonstop segment information is required on the respective legs into and out of the United States. All on-flight market entries involving the U.S. point HNL are also required. Data are not required on the homeland to homeland markets, or the homeland—third country markets.

QF—Qantas Airways (Australia) SYD—Sydney, Australia BNE—Brisbane, Australia CNS—Cairns, Australia HNL—Honolulu, USA YVR—Vancouver, Canada A-3—Airport codeOriginA-4—Airport codeDestinationA-5—Service class (mark an x)FGLPQBy aircraft typeB-1— Acft. type codeB-2—Revenue aircraft departuresB-3—Revenue freight transportedB-4—Revenue freight transported (kg)Sum of all aircraft typesC-1—Total revenue passengers in marketC-2—Total revenue freight in market (kg)CNS HNL X 8161 5 2200 41000 400 8000SYD HNL X 600 10000BNE HNL X 600 9000HNL YVR X 8161 5 750 15700 150 1700

(6) JL flight #002 HKG—NRT—SFO. This flight originates in a third country prior to the homeland. No data is required on the HKG-NRT leg, but the HKG-SFO passengers and cargo shall be shown as enplanements in the NRT-SFO on-flight market entry. These volumes are included by definition in the passenger and cargo transported volumes of the NRT-SFO nonstop segment entry.

JL—Japan Air Lines HKG—Hong Kong, Hong Kong NRT—Tokyo-Narita, Japan SFO—San Francisco, USA A-3—Airport codeOriginA-4—Airport codeDestinationA-5—Service class (mark an x)FGLPQBy aircraft typeB-1—Acft. type codeB-2—Revenue aircraft departuresB-3—Revenue passengers transportedB-4—Revenue freight transported (kg)Sum of all aircraft typesC-1—Total revenue passengers in marketC-2—Total revenue freight in market (kg)NRT SFO X 8161 3 1200 18000 1200 18000

(7) JL flight # 001 SFO-NRT-HKG. This flight is the reverse sequence of flight # 002 above; it requires a nonstop segment entry covering SFO-NRT, and a single on-flight market entry also for SFO-NRT. In this case, the on flight traffic enplaned at SFO and destined for HKG, a beyond homeland point, shall be included in the SFO-NRT entry; a separate SFO-HKG entry is not required.

JL—Japan Air Lines SFO—San Francisco, USA NRT—Tokyo-Narita, Japan HKG—Hong Kong, Hong Kong A-3—Airport codeOriginA-4—Airport codeDestinationA-5—Service class (mark an x)FGLPQBy aircraft typeB-1—Acft. type codeB-2—Revenue aircraft departuresB-3—Revenue passengers transportedB-4—Revenue freight transported (kg)Sum of all aircraft typesC-1—Total revenue passengers in marketC-2—Total revenue freight in market (kg)SFO NRT X 8161 1 400 20000 400 20000

(8) BA flight # 5 LHR-ANC-NRT-OSA. This example contains a single homeland point and a single U.S. point followed by two third country points. It is necessary to report the nonstop segments into and out of the U.S., and all three of the on-flight markets which have the U.S. point ANC as either an origin or destination.

BA—British Airways LHR—London, England ANC—Anchorage, USA NRT—Tokyo-Narita, Japan OSA—Osaka, Japan A-3—Airport codeOriginA-4—Airport codeDestinationA-5—Service class (mark an x)FGLPQBy aircraft typeB-1—Acft. type codeB-2—Revenue aircraft departuresB-3—Revenue passengers transportedSum of all aircraft typesB-4—Revenue freight transported (kg)C-1—Total revenue passengers in marketC-2—Total revenue freight in market (kg)LHRANCX8161103000500001001000ANCNRTX8161103150550001002500ANCOSAX1501500

(d) Provisions to reduce paperwork:

(1) Nonstop Segment Entries. The flight stage data applicable to nonstop segment entries must be summarized to create totals by aircraft equipment type, within service class, within pairs-of-points.

(2) On-flight Market Entries. The applicable on-flight market entries shall be summarized to create totals by service class within pair-of-points.

(e) Preparation of hard copy Schedule T-100(f):

(1) Section A—Indicative and flight pattern information. A copy of Schedule T-100(f) is shown at the end of this Appendix. Section A defines the origin and destination points and the service class code to which the nonstop segment data in Section B and the on-flight market data in Section C are applicable. Section A information, along with the carrier code and report date, must be included on each schedule.

(2) Section B—Nonstop segment information. Section B of the schedule is used for reporting nonstop segment information by aircraft type. To reduce the number of schedules reported, space is provided for including data on multiple different aircraft types. Similarly, the on-flight market section has been included on a single Schedule T-100(f), along with the nonstop segment data, rather than on a separate schedule.

(3) Section C—On-flight market information. Section C of the schedule is used for reporting on-flight market data. There will always be an on-flight market that corresponds to the nonstop segment. Because the on-flight market data are reported at the service class level rather than by aircraft type, a specific flight may produce more on-flight markets than nonstop segments, (see examples in paragraph (c) of this Appendix), resulting in data reported in sections A and C only.

(f) ADP media reports:

(1) ADP report format. A foreign air carrier may, in accordance with the following guidelines, use personal computers (and in some cases mainframe or minicomputers) to report Schedule T-100(f) data.

(i) Reporting medium. ADP data submission of T-100(f) information must be on IBM compatible floppy disk, including diskettes, floppy disks, or flexible disks. The particular type of acceptable minidisk is 51/4 inch, double-sided/double density, with a capacity of approximately 360,000 characters of data (360K). Carriers using mainframe or minicomputers shall download (transcribe) the data to the required floppy disk. Carriers wishing to use a different ADP procedure must obtain written approval to do so from the Director, OAI, under the waiver provisions in § 217.9 of this part. Requests for approval to use alternate methods must disclose the proposed data transmission methodology.

(ii) File characteristics. OAI files are reported in ASCII delimited format, sometimes called Data Interchange Format (DIF). This form of recording data provides for variable length fields (data elements) which, in the case of alphabetic data, are enclosed by quotation marks (“) and separated by a comma (,); numeric data elements are recorded without editing symbols and separated by a comma. The data is identified by its juxtaposition within a given record. Each record submitted by an air carrier shall contain the specified number of data elements all of which must be juxtapositionally correct.

(iii) Schedule T-100(f) record layout. Each minidisk record shall consist of data fields for recording a maximum of eleven (11) elements. The order and description of the data fields are as follows:

(1). Carrier code: Alphanumeric (2). Report date: Numeric (3). Origin airport: Alphabetic (4). Destination airport: Alphabetic (5). Service class code: Alphabetic (6). Aircraft type code: Numeric (7). Aircraft departures performed: Numeric (8). Revenue passengers transported: Numeric (9). Revenue freight transported: Numeric (10). Total revenue passengers in market: Numeric (11). Total revenue freight in market: Numeric

(A) Fields numbered 1 through 11 must always be provided. Therefore, enter a zero (0) or space when there is no reportable data for a given element. See paragraph (g)(1) through (g)(3) for a detailed definition of each data element.

(B) The following are sample disk records:

1234567891011Sample No. 1“CCC”8701“JFK”“LHR”“F”81612959697989Sample No. 2“CCC”8701“JFK”“LHR”“F”6901299599000Sample No. 3“CCC”8701“JFK”“LHR”“G”710229905990799Sample No. 4“CCC”8701“JFK”“LHR”“F”0000699799

Sample No. 1 represents a full record, using the applicable fields for reporting both the nonstop segment (6 through 9) and the on-flight market information (10 and 11). The service class is “F” indicating scheduled passenger/cargo service; the aircraft type code is 8161; the 816 indicates a Boeing 747-100, and the 1 in the units position indicates the standard “passengers-above and cargo-below” configuration.

Sample No. 2 contains nonstop segment information only. It is needed in this example to report the volumes transported on the same nonstop segment, but with a second aircraft type.

Sample No. 3 contains nonstop segment and on-flight market information for the same points, but for another service class (code letter “G” indicates all-cargo service). Also, the units position of aircraft type is a 2, indicating a cargo cabin. Field numbers 8 and 10 are for reporting passengers. In this case both contain a zero, indicating no passengers, while at the same time maintaining the required juxtaposition.

Sample No. 4 shows the reporting of only on-flight market information for a pair-of-points for which there is no corresponding nonstop segment information.

(2) External labeling requirements: Physical label. The following data must be clearly printed on a label affixed to the minidisk or its container.

Carrier Name Carrier code (as prescribed by DOT, BTS, OAI) File identification = “T-100(F) DATA” Report date (year, month to which data applies)

(3) Collating sequence, optional. If practical, the records should be sorted by origin and destination airport codes, service class, and aircraft type. However, the sequence is optional. Data may be submitted in any sequence including random.

(4) Summarization. See summarization rules as specified in paragraph (d)(1).

(g) Data element definitions:

(1) Service pattern information.

(i) Line A-1 Carrier code. Use the carrier code established by the Department. This code is provided to each carrier in the initial reporting letter from the Office of Airline Information (OAI). If there are any questions about these codes, contact the OAI Data Administration Division at the address in paragraph (a)(3) of this Appendix.

(ii) Line A-2 Report date. This is the year and month to which the data are applicable. For example, 8901 indicates the year 1989, month of January.

(iii) Line A-3 Origin airport code. This is the departure airport, where an aircraft begins a flight segment, and where the passengers originate in an on-flight market. Use the 3-letter code from the City/Airport Codes section of the Official Airline Guide Worldwide Edition. If no 3-letter code is available, OAI will assign one; the address is in paragraph (a)(3) of this Appendix.

(iv) Line A-4 Destination airport code. This is the arrival airport, where an aircraft stops on a flight segment, and where passengers deplane (get off the flight) after reaching their destination in a market. Use the 3-letter code from the source described in paragraph (g)(1)(iii) of this Appendix.

(v) Line A-5 Service class code. Select one of the following single letter codes which describes the type of service being reported on a given flight operation.

F = Scheduled Passenger/cargo Service G = Scheduled All-cargo Service L = Nonscheduled Civilian Passenger/Cargo Charter P = Nonscheduled Civilian All-Cargo Charter Q = Nonscheduled Services (Other than Charter)

(2) Nonstop segment information:

(i) Line B-1 Aircraft type code. Use the four digit numeric code prescribed in paragraph (h)(1) of this Appendix. If no aircraft type code is available, OAI will assign one. The address is in paragraph (a)(3) of this Appendix.

(ii) Line B-2 Aircraft departures performed. This is the total number of physical departures performed with a given aircraft type, within service class and pair-of-points.

(iii) Line B-3 Revenue passengers transported. This is the total number of revenue passengers transported on a given nonstop segment. It represents the total number of revenue passengers on board over the segment without regard to their actual point of enplanement.

(iv) Line B-4 Revenue freight transported. This item is the total weight in kilograms (kg) of the revenue freight transported on a given nonstop segment without regard to its actual point of enplanement.

(3) On-flight market information:

(i) Line C-1 Total revenue passengers in market. This item represents the total number of revenue passengers, within service class, that were enplaned at the origin airport and deplaned at the destination airport.

(ii) Line C-2 Total revenue freight in market. This item represents the total weight in kilograms (kg) of revenue freight enplaned at the origin and deplaned at the destination airport.

(h)[Reserved]

(i) Joint Service.

(1) The Department may authorize joint service operations between two direct air carriers. Examples of these joint service operations are:

Blocked-space agreements;

Part-charter agreements;

Code-sharing agreements;

Wet-lease agreements, and similar arrangements.

(2) Joint service operations shall be reported in Form 41 Schedules T-100 and T-100(f) within the following guidelines: (i) Blocked space, part-charters and code-sharing arrangements shall be reported by the carrier in operational control of the flight. The traffic moving under those agreements is reported the same as any other traffic on board the aircraft. (ii) Wet lease agreements shall be reported by the lessee as though the leased aircraft and crew were a part of the lessee's own fleet. (iii) If there are questions about reporting a joint service operation, contact the Director, Office of Aviation Information Management at the address in paragraph (a)(3) of this Appendix. (iv) The Department may require information pertaining to joint service operations in addition to that reported in Schedules T-100 and T-100(f) by U.S. and foreign air carriers. If additional information is needed, ad hoc reporting will be used by the Director, Office of Aviation Information Management (OAI), under authority delegated in § 385.27 (b) and (d) of this chapter. Ad hoc reporting requirements will be communicated to the applicable carriers by letter.

(j) Schedules.

EC30SE91.000 EC30SE91.001