14 C.F.R. Section 25   Traffic and Capacity Elements


Title 14 - Aeronautics and Space


Title 14: Aeronautics and Space
PART 241—UNIFORM SYSTEM OF ACCOUNTS AND REPORTS FOR LARGE CERTIFICATED AIR CARRIERS
Traffic Reporting Requirements


Section 25   Traffic and Capacity Elements

General Instructions. (a) All prescribed reporting for traffic and capacity elements shall conform with the data compilation standards set forth in section 19—Uniform Classification of Operating Statistics.

(b) Carriers submitting Schedule T–100 shall use magnetic computer tape or IBM compatible disk for transmitting the prescribed data to the Department. Upon good cause shown, OAI may approve the request of a U.S. air carrier, under section 1–2 of this part, to use hardcopy data input forms or submit data via e-mail.

Schedule T–8—Report of all-cargo operations.

(a) This schedule shall be filed annually by all air carriers that conduct all-cargo operations under certificates issued under 49 U.S.C. 41103.

(b) Data reported on this schedule shall include only results of operations conducted in all-cargo aircraft. Data shall be segregated between domestic all-cargo operations conducted within the geographic limitations of section 418 certificates and all other all-cargo operations.

(c) Statement of operations. This statement shall include the following elements:

(1) Total operating revenue, categorized as follows:

(i) Transport revenues from the carriage of property in scheduled and nonscheduled service;

(ii) Transport revenues from the carriage of mail in scheduled and nonscheduled service; and

(iii) Transport-related revenues.

(2) Total operating expenses; and

(3) Operating profit or loss, computed by subtracting the total operating expenses from the total operating revenues.

(d) Summary of traffic and capacity statistics. This summary shall include the following elements:

(1) Total revenue ton-miles, which are the aircraft miles flown on each flight stage times the number of tons of revenue traffic carried on that stage. They shall be categorized as follows:

(i) Property; and

(ii) Mail.

(2) Revenue tons enplaned, reflecting the total revenue tons of cargo loaded on aircraft during the annual period;

(3) Available ton-miles, reflecting the total revenue ton-miles available for all-cargo service during the annual period, and computed by multiplying aircraft miles flown on each flight stage by the number of tons of aircraft capacity available for that stage;

(4) Aircraft miles flown, reflecting the total number of aircraft miles flown in cargo service during the annual period;

(5) Aircraft departures performed, reflecting the total number of take-offs performed in cargo service during the annual period; and

(6) Aircraft hours airborne, reflecting the aircraft hours of flight (from take-off to landing) performed in cargo service during the annual period.

Schedule T–100 U.S. Air Carrier Traffic and Capacity Data By Nonstop Segment and On-Flight Market

(a) Schedule T–100 collects detailed on-flight market and nonstop segment data on all revenue flights flown by U.S. certificated air carriers. This schedule is filed monthly. Separate data shall be reported for each operating entity (Latin America, Atlantic, Pacific; International, or Domestic) of the air carrier. Data for each operating entity shall be reported using the five digit entity code prescribed under section 19–5(c) of this part.

(b) Guidelines for reporting the automated monthly Schedule T–100 are included in the Appendix to this section.

(c) Reported data shall be compiled as aggregates of the basic data elements and service classes contained in sections 19–4 and 19–5 of this part.

(d) Joint-service operations. The air carrier in operational control of the aircraft (the carrier that uses its flight crews under its own FAA operating authority) must report joint-service operations.

Schedule T–100(f) Foreign Air Carrier Traffic Data by Nonstop Segment and On-Flight Market

(a) This Schedule T–100(f) collects detail on-flight market and nonstop segment data. This schedule shall be filed monthly by each foreign (non-U.S.) air carrier conducting operations to or from the United States with large aircraft pursuant to Section 41302 permits or exemption authority. Reported traffic data shall include all services affecting the United States, as prescribed in this part.

(b) Guidelines for reporting the monthly Schedule T–100(f) are included in the Appendix to §217.10 of this chapter. Copies of these instructions are provided to each foreign air carrier submitting the traffic data. Copies are also available from the Office of Airline Information, K–25, Room 4125, U.S. Department of Transportation, 400 Seventh St., SW., Washington, DC 20590.

(c) The reported data shall be compiled as aggregates of the basic data elements and service classes prescribed in sections 19–4 and 19–5 of this part.

Appendix to Section 241.25 of 14 CFR Part 241-Instructions to U.S. Air Carriers for Reporting Traffic and Capacity Data on Form 41 Schedule T–100

(a) Applicability. Each large U.S. air carrier that holds a 49 U.S.C. “41102 certificate must file the monthly Schedule T–100.

(b) Schedules, Frequency, and entity: (1) Schedule T–100 collects summarized flight stage data by reporting entity for scheduled and nonscheduled passenger, and cargo operations. The term entity refers to the geographic location designator prescribed by the Department in “241.19–5(c)(2). Thus, domestic entity operations are distinguished from international entity operations.

(2) [Reserved]

(c) Format of reports:

(1) Automatic Data Processing (ADP) magnetic tape. Refer to paragraph (f) of this appendix for instructions pertaining to mainframe and minicomputer reporting. The Department will issue “Accounting and Reporting Directives” to make necessary technical changes to these T–100 instructions. Technical changes which are minor in nature do not require public notice and comment.

(2) Microcomputer diskette—(i) Optional specification. If an air carrier desires to use its personal computers (PC's), rather than mainframe or minicomputers to prepare its data submissions, the following specifications for filing data on diskette media apply:

(ii) Reporting medium. Microcomputer ADP data submission of T–100 information must be on IBM compatible disks. Carriers wishing to use a different ADP procedure must obtain written approval to do so from the BTS Assistant Director—Airline Information. Requests for approval to use alternate methods must disclose and describe the proposed data transmission methodology. Refer to paragraph (k) of this appendix for microcomputer record layouts.

(iii) Microcomputer file characteristics. The files will be created 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 (,) or tab. Numeric data elements that are recorded without editing symbols are also separated by a comma (,) or tab. The data are identified by its juxtaposition within a given record. Therefore, each record must contain the exact number of data elements, all of which must be juxtapositionally correct. Personal computer software including most spreadsheets, data base management programs, and BASIC are capable of producing files in this format.

(d) Filing date for reports. The reports must be received at BTS within 30 days following the end of each reporting period.

(e) Address for filing: Data Administration Division, K–14, Room 4125, Office of Airline Information, Bureau of Transportation Statistics, U.S. Department of Transportation, 400 Seventh Street SW., Washington, DC 20590–0001.

(f) ADP format for magnetic tape—(1) Magnetic tape specifications. IBM compatible 9-track EBCDIC recording. Recording density of 6250 or 1600 bpi. The order of recorded information is:

Volume label

Header label

Data records

Trailer label

(2) [Reserved]

(g) External tape label information:

Carrier name

Report date

File identification

Carrier address for return of tape reel

(h) Standards. It is the policy of the Department to be consistent with the American National Standards Institute and the Federal Standards Activity in all data processing and telecommunications matters. It is our intention that all specifications in this application be in compliance with standards promulgated by these organizations.

(i) Volume, header, and trailer label formats:

(1) Use standard IBM label formats. The file identifier field of the header labels should be “T–100.SYSTEM”.

(2) [Reserved]

(j) Magnetic tape record layouts for T–100—(1) Nonstop segment record layout:

----------------------------------------------------------------------------------------------------------------        Field No.             Positions               Mode                            Description----------------------------------------------------------------------------------------------------------------1........................               1  1T.......................  Record type code (S = nonstop segment).2........................             2-6  5T.......................  Carrier entity code.3........................            7-12  6T.......................  Report date (YYYYMM).4........................           13-15  3T.......................  Origin airport code.5........................           16-18  3T.......................  Destination airport code.6........................              19  1T.......................  Service class code (F, G, L, N, P or R).7........................           20-23  4T.......................  Aircraft type code.8........................           24-28  5N.......................  Revenue departures performed (F, G, L, N,                                                                       P, R510).9........................           29-38  10N......................  Available capacity payload (lbs) (F, G, L,                                                                       N, P, R270).10.......................           39-45  7N.......................  Available seats (F, L, N310).11.......................           46-52  7N.......................  Passengers transported (F, L, N130).12.......................           53-62  10N......................  Rev freight transported (F, G, L, N, P,                                                                       R237)(in lbs).13.......................           63-72  10N......................  Revenue mail transported (F, G, L, N, P,                                                                       R239) (in lbs).14.......................           73-77  5N.......................  Revenue aircraft departures scheduled (F,                                                                       G520).15.......................           78-87  10N......................  Rev hrs, ramp-to-ramp (F, G, L, N, P,                                                                       R630) (in minutes).16.......................           88-97  10N......................  Rev hrs, airborne (F, G, L, N, P, R610)                                                                       (in minutes).----------------------------------------------------------------------------------------------------------------T= Text.N= Numeric.

(2) On-flight market record layout:

----------------------------------------------------------------------------------------------------------------        Field No.             Positions               Mode                            Description----------------------------------------------------------------------------------------------------------------1........................               1  1T.......................  Record type: M = on-flight market record.2........................             2-6  5T.......................  Carrier entity code.3........................            7-12  6T.......................  Report date (YYYYMM).4........................           13-15  3T.......................  Origin airport code.5........................           16-18  3T.......................  Destination airport code.6........................              19  1T.......................  Service class code (F, G, L, N, P or R).7........................           20-26  7N.......................  Total passengers in market (F, L, N110).8........................           27-36  10N......................  Rev freight in market (F, G, L, N, P,                                                                       R217) (in lbs).9........................           37-46  10N......................  Revenue mail in market (F, G, L, N, P,                                                                       R219) (in lbs).----------------------------------------------------------------------------------------------------------------T=Text.N-Numeric.

(k) Record layouts for microcomputer diskettes. The record layouts for diskettes are generally identical to those shown for magnetic tape, with the exception that delimiters (quotation marks, tabs and commas) are used to separate fields. It is necessary that the order of fields be maintained in all records.

(1) File characteristics. The files will be created 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 (,) or tab. Numeric data elements that are recorded without editing symbols are also separated by a comma (,) or tab. The data are identified by their juxtaposition within a given record. Therefore, it is critical that each record contain the exact number of data elements, all of which must be juxtapositionally correct. PC software including most spreadsheets, data base management programs, and BASIC produce minidisk files in this format.

(2) File naming conventions for diskettes. For microcomputer reports, each record type shall be contained in a separate DOS file on the same physical diskette. The following DOS naming conventions should be followed:

Record type S = SEGMENT.DAT

Record type M = MARKET.DAT

(l) Discussion of Reporting Concept. (1) Schedule T–100 collects summarized flight stage data and on-flight market data. All traffic statistics shall be compiled in terms of each revenue flight stage as actually performed. The detail T–100 data shall be maintained in such a manner as to permit monthly summarization and organization into two basic groupings. The first grouping, the nonstop segment information, is to be summarized by equipment type, within class of service, within pair-of-points, without regard to individual flight number. The second grouping requires that the enplanement/deplanement information be broken out into separate units called on-flight market records, which shall be summarized by class of service, within pair-of-points, without regard for equipment type or flight number.

(2) [Reserved]

(m) Joint Service—(1) Joint-service operations. 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 other similar arrangements.

(i) Joint-service operations are reported by the carrier in operational control of the flight, i.e., the carrier that uses its flight crews under its own FAA operating authority. The traffic moving under these agreements is reported on Schedule T–100 the same way as any other traffic on the aircraft.

(ii) If there are questions about reporting a joint-service operation, contact the BTS Assistant Director—Airline Information (fax no. 202 366–3383, telephone no. 202 366–4373).

(iii) Operational control. The air carrier in operational control of the aircraft (the carrier that uses its flight crew under its own FAA operating authority) must report joint-service operations.

(2) [Reserved]

(n) Glossary of data elements. §241.19–5 and §241.03.

(Approved by the Office of Management and Budget under control number 2138–0013)

[ER–755, 37 FR 19726, Sept. 21, 1972]

Editorial Note:  For Federal Register citations affecting part 241, section 25, see the List of CFR Sections Affected, which appears in the Finding Aids section of the printed volume and on GPO Access.


























































chanrobles.com