Title 14

PART 291 APPENDIX A

Appendix A to Subpart E of Part 291 - Instructions to U.S. Air Carriers for Reporting Traffic and Capacity Data on Schedule T-100

14:4.0.1.1.39.5.8.7.4 : Appendix A

Appendix A to Subpart E of Part 291 - Instructions to U.S. Air Carriers for Reporting Traffic and Capacity Data on Schedule T-100

(a) Format of reports - (1) Automatic Data Processing (ADP) magnetic tape. Refer to paragraph (d) 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 (i) 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 their 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.

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

(c) Address for filing. Data Administration Division, RTS-42, Office of Airline Information, Bureau of Transportation Statistics, U.S. Department of Transportation, 1200 New Jersey Avenue SE, Washington, DC 20590-0001.

(d) 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:

(i) Volume label.

(ii) Header label.

(iii) Data records.

(iv) Trailer label.

(2) [Reserved]

(e) External tape label information. (1) Carrier name.

(2) Report date.

(3) File identification.

(4) Carrier address for return of tape reel.

(f) 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 are in compliance with standards promulgated by these organizations.

(g) 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”.

(h) 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).

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	4T	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).

(i) Record layouts for microcomputer diskettes. The record layouts for diskette 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 should be contained in a separate DOS file on the same physical diskette. The following DOS naming conventions should be followed: