Compendium of Survey Data Record Layouts

TP-14930

April 1, 2015

Introduction

This document contains record layouts for various surveys which must be completed by transportation undertakings in accordance to the Transportation Information Regulations.

Air

Airlines

The Enplaned / Deplaned Flight Centric Survey

Data Record Layout
Record Type
Carrier Security Key
Carrier IATA Code
Flight Number
Departure or Origin Airport IATA Code
Departure Date
Departure Time
Arrival or Destination Airport IATA Code
Arrival Date
Arrival Time
Schedule or Charter flag
Passenger or Freighter flight flag
Unit of Weight
Aircraft Type
Aircraft seating capacity
Payload Capacity
CTA Charter permits
Departure Airport Enplaned PAX Count Revenue
Departure Airport Enplaned PAX Count Non-Revenue
Departure Airport Transiting PAX Count Revenue
Departure Airport Transiting PAX Count Non-Revenue
Arrival Airport Deplaned PAX Count Revenue
Arrival Airport Deplaned PAX Count Non-Revenue
Arrival Airport Transiting PAX Count Revenue
Arrival Airport Transiting PAX Count Non-Revenue
Departure Airport Enplaned Freight
Departure Airport Transiting Freight
Arrival Airport Deplaned Freight
Arrival Airport Transiting Freight
Departure Airport Enplaned Luggage Count
Departure Airport Enplaned Luggage Weight
Departure Airport Enplaned Mail
Arrival Airport Deplaned Mail
Aircraft Registration Mark
GMT Or Local Time Flag
Next Leg Stop Airport IATA Code For This Flight
The Enplaned / Deplaned Flight Centric Survey

The Enplaned / Deplaned Flight Centric Survey table lists the data elements that air carriers are required to submit as per the Transportation Information Regulations. Some of the key fields include departure or origin airport International Air Transport Association (IATA) Code, arrival or destination airport IATA Code and payload capacity, passengers enplaned and deplaned, mail enplaned and deplaned and freight enplaned and deplaned.

On-Board Coupon Origin and Destination Survey

Data Record Layout
Record type
Carrier security key
Carrier IATA code
Year
Quarter/Month
Reporting frequency
Origin airport IATA Code
Destination airport IATA Code
Number of revenue passengers
Weight of cargo (Kg)
Weight of mail (Kg)
Number of non-stop flights
On-Board Coupon Origin and Destination Survey

The On-Board Coupon Origin and Destination Survey table lists the data elements that air carriers are required to submit as per the Transportation Information Regulations. Some of the key fields include reporting frequency, number of revenue passengers and the number of non-stop flights. The survey enables regional air carriers to report their passenger and cargo loads.

Aircraft Fleet and Fuel Consumption Report

Data Record Layout
Year
Carrier
Aircraft Registration
Aircraft Manufacturer
Aircraft Model
Aircraft Year of construction
Engine #1 Manufacturer
Engine #1 Model
Engine #1 Year of construction
Engine #2 Manufacturer
Engine #2 Model
Engine #2 Year of construction
Engine #3 Manufacturer
Engine #3 Model
Engine #3 Year of construction
Engine #4 Manufacturer
Engine #4 Model
Engine #4 Year of construction
Domestic flights fuel consumption
International flights fuel consumption
Aircraft Fleet and Fuel Consumption Report

The Aircraft Fleet and Fuel Consumption Report table lists the data elements that air carriers are required to submit as per the Transportation Information Regulations. Some of the key fields include engine manufacturer, model and year of construction. The report enables air carriers to report their fuel consumption by aircraft type.

Statement of Air Cargo Fluidity Indicators

Data Record Layout
For carriers using IATA Cargo 2000
Booking Entity IATA Code
Booking Entity Air Waybill Number
Air Waybill Origin IATA Code
Air Waybill Destination IATA Code
Actual Shipment Weight
Chargeable Shipment Weight
Piece Count
Product Type Designation
Date Route Map Created
Time Route Map Created
Date the electronic Airway Bill was created
Time Electronic Airway Bill was created
Date freight was checked-in at the origin airport
Time freight was checked-in at the origin airport
Date goods were confirmed onboard
Time goods were confirmed onboard
Date and time of arrival and IATA airport code at each connection airport
Date and time of departure and IATA airport code at each connection airport
Date freight was accepted at the destination airport
Time freight was accepted at the destination airport
Date freight and documents were available for pickup at the destination airport
Time freight and documents were available for pickup at the destination airport
Date Freight and documents delivered
Time Freight and documents delivered
Commodity Type
Flight Number (First Leg)
Carrier IATA Code (First Leg)
Departure Airport IATA Code (First Leg)
Departure Date (First Leg)
Departure Time (First Leg)
Arrival Airport IATA Code (First Leg)
Arrival Date (First Leg)
Arrival Time (First Leg)
Any additional reservation legs as required
For carriers not using IATA Cargo 2000
Origin airport
Date freight was checked-in at the origin airport
Time freight was checked-in at the origin airport
Destination airport
Date freight and documents were available for pickup
Time freight and documents were available for pickup
Statement of Air Cargo Fluidity Indicators

The Statement of Air Cargo Fluidity Indicators table lists the data elements that air carriers are required to submit as per the Transportation Information Regulations. Some of the key fields include piece count, product type designation and destination airport. The statement helps air carriers report the speed and direction of their supply chains.

General Aviation Operational Survey (Detailed)

Data Record Layout
Carrier Code
Flight Number
Departure Airport IATA Code
Departure Date
Departure Time
Arrival Airport IATA Code
Arrival Date
Arrival Time
Activity Type
Aircraft Type
Aircraft Mark
Passenger Count
Amount of freight (Kg)
General Aviation Operational Survey (Detailed)

The General Aviation Operational Survey (Detailed) table lists the data elements that air carriers are required to submit as per the Transportation Information Regulations. Some of the key fields include carrier code, departure and arriving airport IATA code and amount of freight (Kg).  The survey permits general aviation operators to report their operations in detail.

General Aviation Operational Survey (Summary)

Data Record Layout
Year and Quarter
Carrier Code
Activity Type
Aircraft Type
Aircraft Mark
Passenger Count
Amount of freight (Kg)
Local segments flown
Cross-country segments flown
International segments flown
Airport most flown to
2nd airport most flown to
3rd airport most flown to
4th airport most flown to
5th airport most flown to
6th airport most flown to
7th airport most flown to
8th airport most flown to
9th airport most flown to
10th airport most flown to
General Aviation Operational Survey (Summary)

The General Aviation Operational Survey (Summary) table lists the data elements that air carriers are required to submit as per the Transportation Information Regulations. Some of the key fields include year and quarter, airport most flown to and passenger count. The survey allows general aviation operators to report a summary of their operations.

General Aviation Financial Survey

Data Record Layout
Year
Percentage of fleet used for private use
Amount of fuel consumed
Fuel expenditure
Maintenance expenditure
NAV Canada services expenditures
Airport fees
Other expenses
General Aviation Financial Survey

The General Aviation Financial Survey table lists the data elements that air carriers are required to submit as per the Transportation Information Regulations. Some of the key fields include percentage of fleet used for private use, fuel expenditure and airport fees.  The survey enables general aviation operators to report their financial statements.

Airports

Balance Sheet, Airport

Data Record Layout
Airport ICAO Code(s)
Period reported
Is a balance sheet produced (Y/N)
If reporting for multiple airports, is a balance sheet produced for each airport (Y/N)
Cash And Cash Equivalents
Marketable Securities/investments
Accounts Receivable
Other Current Assets
Capital Assets
Work-in-progress
Other Assets
Accounts Payable and Accrued Liabilities
Current Portion Of Long-term Debt
Other Current Liabilities
Long-term Debt
Other Long-term Liabilities
Net Assets (Equity)
Airport Balance Sheet

The Airport Balance Sheet table lists the data elements that airports are required to submit as per the Transportation Information Regulations. Some of the key fields include period reported, capital assets, and accounts payable and accrued liabilities.

Income Statement, Airport

Data Record Layout
Airport ICAO Code(s)
Period reported
Is an income statement produced (Y/N)
If reporting for multiple airports, is an income statement produced for each airport (Y/N)
Year
Landing Fees
Terminal Fees
Aviation Fuel Sales
Aircraft parking fees
Other Aviation Fees
Car Parking Revenues
Concessions Revenues
Rental Revenues
Other Commercial Revenues
Airport Improvement Fees
Other Revenue/gains
Salaries, Wages, Benefits
Amortization
Goods And Services Purchases
Property Taxes
Other Operating Cost
Interest Expense
Other Expenses/losses
Net Earnings (Loss)
Airport Income Statement

The Airport Income Statement table lists the data elements that airports are required to submit as per the Transportation Information Regulations. Some of the key fields include landing fees, airport improvement fees and interest expense.

Air Navigation Services

Flight Plan Report

Data Record Layout
Departure date and time (UTC)
Carrier Code
Flight number
Aircraft registration
Aircraft type
Origin airport code
Destination airport code
NAV Canada Flight Plan Identifier
Flight Plan Report

The Flight Plan Report table lists the data elements that air navigation service providers are required to submit as per the Transportation Information Regulations. Some of the key fields include carrier code, aircraft registration and destination airport code.  The report helps air navigation service providers report the flight plans filed with them.

Flight Tracking Report

Data Record Layout
Departure date
Carrier Code
Flight number
Aircraft registration
Aircraft type
Origin airport code
Destination airport code
Controlled airspace Entry/Exit flag
Point of controlled airspace entry or exit
Flight Tracking Report

The Flight Tracking Report table lists the data elements that air navigation service providers are required to submit as per the Transportation Information Regulations. Some of the key fields include departure date, aircraft type and point of controlled airspace entry or exit. The report allows air navigation service providers to report on the entry and exit of aircraft in Canadian airspace.

Marine

Marine Carriers

Annual marine fleet inventory and fuel consumption survey

Data Record Layout
Reporting Year
Vessel Name
Country Of Registration
Gross Tonnage
Net Tonnage
Length
Beam
Draft
Class
Engine Type
Engine Model Number
Engine Size
Engine Cylinder Size
Specific Fuel Consumption (Underway)
Specific Fuel Consumption (In Maneuvers)
Specific Fuel Consumption (In Hotelling)
Specific Fuel Consumption (At Anchor)
Specific Fuel Consumption (In Dry Dock)
Year of Construction
Year of Last Rebuilt
Technologies That Enhance Fuel Efficiency
Number of Strokes of the Engine’s Pistons
Type of Hull
Ice Class and Name of the Classification Society Which Assigned Said Class
Vessel’s Classification and Name of the Classification Society Which Assigned Said Class
Vessel’s Environmental Notation and Name of the Classification Society Which Assigned Said Class
Hours Operated During The Year
Tonnes Carried During The Year
Tonnes-Kilometres Carried During The Year
Passengers-Kilometres Carried During The Year
Vessel-Kilometres Performed During The Year
Fuel Consumption
Type of Fuel
Quality of Fuel
Annual Marine Fleet Inventory and Fuel Consumption Survey

The Annual Marine Fleet Inventory and Fuel Consumption Survey table lists the data elements that marine carriers are required to submit as per the Transportation Information Regulations. Some of the key fields include country of registration, engine model number and fuel consumption.  The survey enables marine operators to report their fleet inventory and fuel consumption.

Domestic Shipping Survey

Data Record Layout
Vessel Name
Voyage No.
Report No.
Port of arrival/departure
Stop Type
Country of registry
Gross Tonnage
Net Tonnage
Type of vessel
MMSI Number
IMO Number
Transport Canada Registration Number (TCRN)
Departures
  • Date
  • Port departed from
  • Port(s) where cargoes were loaded
  • Description of Cargo
  • Net weight (Containerized vs. Non-containerized)
  • Unit of measure
  • United Nations Code for Dangerous Goods
Arrivals
  • Date
  • Last port departed from
Domestic Shipping Survey

The Domestic Shipping Survey table lists the data elements that marine carriers are required to submit as per the Transportation Information Regulations. Some of the key fields include the vessel type, the port of departure and of arrival, the description and the weight of the cargo.  The survey enables marine carriers to report their vessel and cargo movements between Canadian ports.

Tugboat Survey

Data Record Layout
Barge or Vessel Name
Gross Tonnage
Net Tonnage
Country of Registry
Reporting Period (MM-YYYY)
Departures
  • Port or Designated Area of Departure
  • Number of Trips
  • Description of Cargo
  • Total Weight
  • Unit of Measure
  • United Nations Code for Dangerous Goods
Port of Arrival
Tugboat Survey

The Tugboat Survey table lists the data elements that tugboat operators are required to submit as per the Transportation Information Regulations. Some of the key fields include the port or designated area of departure and of arrival, the description and the weight of the cargo loaded. The survey enables tugboat operators to report their cargo and vessel movements between Canadian areas and ports.

Ferry Survey

Data Record Layout
Vessel Name
Gross Tonnage
Net Tonnage
Country of Registry
Reporting Period (MM -YYYY)
Departures
  • Port or Designated Area of Departure
  • Number of Trips
  • Number of Passengers
  • Number of Vehicles
  • Description of Cargo
  • Total Weight
  • Unit of Measure
  • United Nations Code for Dangerous Goods
Port of Arrival
Ferry Survey

The Ferry Survey table lists the data elements that ferry operators are required to submit as per the Transportation Information Regulations. Some of the key fields include the port or designated area of departure and of arrival, the number of passengers and vehicles carried.  The survey enables ferry operators to report the origin and destination of their trips and the number of passengers and vehicles carried.

Canadian Port Authorities

Port Infrastructure Survey

Data Record Layout
Port Information
Port name
Year
Railroad track length
Wharf Information (for each wharf)
Operator
Wharf number
Wharf length
Water depth
Name of terminal served (if any)
Cargo handling and loading equipment (for each terminal)
Terminal name (if any)
Latitude:
Longitude:
Terminal capacity (tonnes)
Number and capacity of container cranes
Number and capacity of bulk conveyers
Other (specify)
Warehousing area (containers) [ha]
Warehousing area (solid bulk – ambient temperature) [ha]
Warehousing area (solid bulk - refrigerated) [ha]
Warehousing volume (liquid bulk)
Specific bulk commodity handled (if any)
Port Infrastructure Survey

The Port Infrastructure Survey table lists the data elements that Canadian Port Authorities are required to submit as per the Transportation Information Regulations. Some of the key fields to be collected include port name, terminal capacity and operator. The survey assists Canadian Port Authorities when reporting on their infrastructure.

Rail

Locomotive Fleet Survey

Data Record Layout
Rail carrier name
Year
Locomotive number
Locomotive manufacturer
Locomotive model
Locomotive year of construction
Year of last engine retrofit
Locomotive horsepower
Locomotive classification
Locomotive Fleet Survey

The Locomotive Fleet Survey table lists the data elements that rail carriers are required to submit as per the Transportation Information Regulations. Some of the key fields include rail carrier name, locomotive model and year of last engine retrofit.  The survey allows rail carriers to report on the characteristics of their locomotive fleet.

Passenger Rail Origin and Destination Survey

Data Record Layout
Rail carrier name
New Reservation /Cancellation Flag
Ticket number
Ticket Origin Station
Ticket Destination Station
Passenger Type
Fare
Train #1 Origin
Train #1 Destination
Train #1 Date
Train #1 Train Number
Train #1 Class
Train #2 Origin
Train #2 Destination
Train #2 Date
Train #2 Train Number
Train #2 Class
Train #3 Origin
Train #3 Destination
Train #3 Date
Train #3 Train Number
Train #3 Class
Passenger Rail Origin and Destination Survey

The Passenger Rail Origin and Destination Survey table lists the data elements that rail carriers are required to submit as per the Transportation Information Regulations. Some of the key fields include rail carrier name, passenger type and fare.  The survey enables rail carriers to report the origin, destination, and itinerary of their passengers.

Passenger Rail Line Traffic Report

Data Record Layout
Rail carrier name
Year
Month
Rail line end points
Number of passengers carried
Passenger Rail Line Traffic Report

The Passenger Rail Line Traffic Report table lists the data elements that rail carriers are required to submit as per the Transportation Information Regulations. Some of the key fields to be collected include rail carrier name, rail line end points and number of passengers carried.

Railway Grain Traffic Survey

Data Record Layout
Rail carrier name
Week beginning date
Corridor used
Hopper car / Container flag
Loaded railway cars
Tonnes carried
Railway Grain Traffic Survey

The Railway Grain Traffic Survey table lists the data elements that Class I rail carriers that transport grain are required to submit as per the Transportation Information Regulations. Some of the key fields include the rail carrier name, the corridor used, the number of loaded railway cars and the tonnage of grain transported. The survey allows rail carriers to report on railway grain traffic.  

Railway Car Order Fulfilment Survey

Data Record Layout
Rail carrier name
Week beginning date
Total railway cars ordered
Total railway cars committed
Total railway cars placed
Total railway cars ordered and cancelled
Railway Car Order Fulfilment Survey

The Railway Car Order Fulfilment Survey table lists the data elements that Class I rail carriers that transport grain are required to submit as per the Transportation Information Regulations. Some of the key fields include the rail carrier name, the number of railway cars ordered, committed, placed, and ordered and cancelled. This survey allows rail carriers to report on their order fulfilment for grain shipments.

Railway Car Fleet Survey

Data Record Layout
Rail carrier name
Week beginning date
Total railway cars loaded
Total railway cars empty
Total railway cars stored
Total railway cars bad order
Railway Car Fleet Survey

The Railway Car Fleet Survey table lists the data elements that Class I rail carriers that transport grain are required to submit as per the Transportation Information Regulations. Some of the key fields include the rail carrier name, the number of railway cars that are loaded, empty, stored and in bad order. The survey allows rail carriers to report on the situation of their fleet of covered hopper cars.

Railway Car Event Survey

Data Record Layout
Rail carrier name
Week beginning date
Railway car letters
Railway car number
Loaded/empty indicator
Event type
Date and Time of the movement event begins
Date and Time the movement event ends
Standard point location code or Freight Station Accounting Code of the point where the movement begins
Standard point location code or Freight Station Accounting Code of the point where the movement ends
7-digit STCC (standard transportation commodity code)
Railway Car Event Survey

The Railway Car Event Survey table lists the data elements that Class I rail carriers that transport grain are required to submit as per the Transportation Information Regulations. Some of the key fields include the railway car event type, the date and the time the movement event begins and ends, and the code that identifies the geographic location where the movement event begins and ends. This survey allows rail carriers to report on railway car event for grain shipments.

Survey of Railway Safety-Related Data Elements

Summary of proficiency tests

Data Elements Description
Railway ID Railway name/identification
Reporting Period 12 month period which the data represents from November 1 to October 31 (e.g. 2014/15 would represent the data from November 1, 2014 to October 31, 2015)
Rule The CROR rule number that is being tested (112, 115, 104 or 105)
# of Passes Number of passes means compliant to the rule
# of Fails Number of fails means not compliant to the rule
Survey of Railway Safety-Related Data Elements

Summary of proficiency tests

The Summary of proficiency tests table lists and describes the data elements that Class I and Class II rail carriers would be required to collect. The data elements include the railway name and identification; the reporting period, which is the 12 month period from November 1 to October 31; the rule number from the Canadian Rail Operating Rules that is being tested; the number of passes that are compliant and the number of fails that were not compliant to each rule number that was tested.

Number of locomotives set off en route for mechanical reasons

Data Elements Description
Railway ID Railway name/identification
Reporting Period 12 month period which the data represents from November 1 to October 31 (e.g. 2014/15 would represent the data from November 1, 2014 to October 31, 2015)
Month Month the locomotive set off occurred in
Set off Type Categories for set offs are: Wheel defects; Wheel bearing defects; Suspension bearings – plain; Suspension bearings – roller; Axle failures; Dragging equipment; Air brake malfunction
Counts Number of locomotive set offs found
Number of locomotives set off en route for mechanical reasons

The Number of locomotives set off en route for mechanical reasons table lists and describes the data elements that Class I and Class II rail carriers would be required to collect. The data elements include the railway name and identification; the reporting period, which is the 12 month period from November 1 to October 31; the month in which the locomotive set off occurred; the set off type, which is the cause of the set off and includes wheel defects, wheel bearing defects, suspension bearings – plain, suspension bearings – roller, axle failures, dragging equipment, and air brake malfunction; and the number of locomotive set offs found.

Number of cars set off en route for mechanical reasons

Data Elements Description
Railway ID Railway name/identification
Reporting Period 12 month period which the data represents from November 1 to October 31 (e.g. 2014/15 would represent the data from November 1, 2014 to October 31, 2015)
Month Month the car set off occurred in
Set off Type Categories for set offs are: Wheel defects; Wheel bearing defects – Burnt-off journals; Wheel bearing defects – Overheated bearings; Axle failures; Dragging equipment; Air brake malfunction
Counts Number of car set offs found
Number of cars set off en route for mechanical reasons

The Number of cars set off en route for mechanical reasons table lists and describes the data elements that Class I and Class II rail carriers would be required to collect. The data elements include the railway name and identification number; the reporting period, which is the 12 month period from November 1 to October 31; the month in which the car set off occurred; the set off type, which is the cause of the set off and includes wheel defects, wheel bearing defects – burnt-off journals, wheel bearing defects – overheated bearings, axle failures, dragging equipment, and air brake malfunction; and the number of car set offs found.

Number of train pull aparts caused by a broken knuckle and/or a broken drawbar

Data Elements Description
Railway ID Railway name/identification
Reporting Period 12 month period which the data represents from November 1 to October 31 (e.g. 2014/15 would represent the data from November 1, 2014 to October 31, 2015)
Month Month the pull apart occurred in
Subdivision Name of the subdivision
Counts Number of train pull aparts found
Number of train pull aparts caused by a broken knuckle and/or a broken drawbar

The Number of train pull aparts caused by a broken knuckle and/or a broken drawbar table lists and describes the data elements that Class I and Class II rail carriers would be required to collect. The data elements include the railway name and identification; the reporting period, which is the 12 month period from November 1 to October 31; the month in which the pull apart occurred; the name of the subdivision and the number of train pull aparts found.

Number of broken and/or cracked wheels found on a train in a yard or in a repair facility

Data Elements Description
Railway ID Railway name/identification
Reporting Period 12 month period which the data represents from November 1 to October 31 (e.g. 2014/15 would represent the data from November 1, 2014 to October 31, 2015)
Month Month the broken /cracked wheel was found
Type of Broken and/or Cracked Wheel Types are: Flange cracked/broken; Rim cracked/broken; Rim shattered; Plate cracked/broken
Counts Number of broken/cracked wheels
Number of broken and/or cracked wheels found on a train in a yard or in a repair facility

The Number of broken and/or cracked wheels found on a train in a yard or in a repair facility table lists and describes the data elements that Class I and Class II rail carriers would be required to collect.  The data elements include the railway name and identification; the reporting period, which is the 12 month period from November 1 to October 31; the month in which the broken or cracked wheel was found; the type of broken and/or cracked wheel, which includes cracked or broken flange, cracked or broken rim, shattered rim, and cracked or broken plate; and the number of broken and/or cracked wheels found.

Deviations from the track geometry standards in the Rules Respecting Track Safety

Data Elements Description
Railway ID Railway name/identification
Reporting Period 12 month period which the data represents from November 1 to October 31 (e.g. 2014/15 would represent the data from November 1, 2014 to October 31, 2015)
Subdivision Name of the subdivision
Counts Number of urgent defects found (those which are indications of deviations to the Rules Respecting Track Safety)
Deviations from the track geometry standards in the Rules Respecting Track Safety

The Deviations from the track geometry standards in the Rules Respecting Track Safety table lists and describes the data elements that Class I and Class II rail carriers would be required to collect. The data elements include the railway name and identification; the reporting period, which is the 12 month period from November 1 to October 31; the name of the subdivision; and the number of deviations found.

Deviations from the defective rail standards in the Rules Respecting Track Safety using rail flaw testing activities

Data Elements Description
Railway ID Railway name/identification
Reporting Period 12 month period which the data represents from November 1 to October 31 (e.g. 2014/15 would represent the data from November 1, 2014 to October 31, 2015)
Subdivision Name of the subdivision
Counts Number of defects found
Deviations from the defective rail standards in the Rules Respecting Track Safety using rail flaw testing activities

The Deviations from the defective rail standards in the Rules Respecting Track Safety using rail flaw testing activities table lists and describes the data elements that Class I and Class II rail carriers would be required to collect. The data elements include the railway name and identification; the reporting period, which is the 12 month period from November 1 to October 31; the name of the subdivision; and the number of defects found.

In-service rail failures

Data Elements Description
Railway ID Railway name/identification
Reporting Period 12 month period which the data represents from November 1 to October 31 (e.g. 2014/15 would represent the data from November 1, 2014 to October 31, 2015)
Subdivision Name of the subdivision
Counts Number of in-service rail failures found
In-service rail failures

The In-service rail failures table lists and describes the data elements that Class I and Class II rail carriers would be required to collect. The data elements include the railway name and identification; the reporting period, which is the 12 month period from November 1 to October 31; the name of the subdivision; and the number of in-service rail failures found.

In-service joint pull aparts

Data Elements Description
Railway ID Railway name/identification
Reporting Period 12 month period which the data represents from November 1 to October 31 (e.g. 2014/15 would represent the data from November 1, 2014 to October 31, 2015)
Subdivision Name of the subdivision
Counts Number of in-service joint pull aparts found
In-service joint pull aparts

The In-service joint pull aparts table lists and describes the data elements that Class I and Class II rail carriers would be required to collect. The data elements include the railway name and identification; the reporting period, which is the 12 month period from November 1 to October 31; the name of the subdivision; and the number of in-service joint pull aparts found.

Total tonnage per year per segment of track

Data Elements Description
Railway ID Railway name/identification
Reporting Period 12 month period which the data represents from November 1 to October 31 (e.g. 2014/15 would represent the data from November 1, 2014 to October 31, 2015)
Subdivision Name of the subdivision
Tonnage mile from Beginning of zone associated with a tonnage value in million gross tons (MGT)
Tonnage mile to End of zone associated with a tonnage value in million gross tons (MGT)
Tonnage (total) Total Tonnage in million gross tons (MGT) between “Tonnage mile from” and “Tonnage mile to”
Total tonnage per year per segment of track

The Total tonnage per year per segment of track table lists and describes the data elements that Class I and Class II rail carriers would be required to collect. The data elements include the railway name and identification; the reporting period, which is the 12 month period from November 1 to October 31; the name of the subdivision; the tonnage mile of the beginning of the zone associated with a tonnage value in million gross tons; the tonnage mile of the end of the zone associated with a tonnage value in million gross tons; and the total tonnage in million gross tons between the beginning and end of the zone.

Information related to any malfunction of an Automated Warning System for which a trouble ticket was issued

Data Elements Description
Railway ID Railway name/identification
Reporting Period 12 month period which the data represents from November 1 to October 31 (e.g. 2014/15 would represent the data from November 1, 2014 to October 31, 2015)
Subdivision Name of the subdivision
Mileage of Automated Warning System Mileage point of the Automated Warning System affected
Ticket number The number assigned by the railway for the trouble ticket
Date reported Date the malfunction was reported
Time reported Time the malfunction was reported
Reported problem Description of the malfunction reported in the field
Failed Sub-system Name Name of the sub-system and/or component that malfunctioned (e.g. track circuit, track bond, etc.)
Resolution The remedy that was applied to resolve the malfunction
Restoration Date Date the malfunction was repaired
Restoration time Time the malfunction was repaired
Information related to any malfunction of an Automated Warning System for which a trouble ticket was issued

The Information related to any malfunction of an Automated Warning System for which a trouble ticket was issued table lists and describes the data elements that Class I and Class II rail carriers would be required to collect. The data elements include the railway name and identification; the reporting period, which is the 12 month period from November 1 to October 31; the name of the subdivision ; the mileage point of the Automated Warning System affected; the number assigned by the railway for the trouble ticket; the date that the malfunction was reported; the time that the malfunction was reported; a description of the malfunction reported in the field; the name of the failed sub-system and/or component that malfunctioned, for example a track circuit or a track bond, etc.; the remedy that was applied to resolve the malfunction; the date that the malfunction was repaired; and the time that the malfunction was repaired.

Information related to any malfunction of a Wayside Inspection System for which a trouble ticket was issued

Data Elements Description
Railway ID Railway name/identification
Reporting Period 12 month period which the data represents from November 1 to October 31 (e.g. 2014/15 would represent the data from November 1, 2014 to October 31, 2015)
Subdivision Name of the subdivision
Mileage of Wayside Inspection System Mileage point of the Wayside Inspection System affected
Ticket number The number assigned by the railway for the trouble ticket
Date reported Date the malfunction was reported
Time reported Time the malfunction was reported
Reported problem Description of the malfunction reported in the field
Failed Sub-system Name Name of the sub-system and/or component that malfunctioned (e.g. Hot Box Detector, bearing detector, mirror, etc.)
 Resolution The remedy that was applied to resolve the malfunction
Restoration Date Date the malfunction was repaired
Restoration Time Time the malfunction was repaired
Information related to any malfunction of a Wayside Inspection System for which a trouble ticket was issued

The Information related to any malfunction of a Wayside Inspection System for which a trouble ticket was issued table lists and describes the data elements that Class I and Class II rail carriers would be required to collect. The data elements include the railway name and identification ID; the reporting period, which is the 12 month period from November 1 to October 31; the name of the subdivision; the mileage point of the Wayside Inspection System affected; the number assigned by the railway for the trouble ticket; the date that the malfunction was reported; the time that the malfunction was reported; a description of the malfunction reported in the field; the name of the failed sub-system and/or component that malfunctioned, for example the Hot Box Detector, a bearing detector, or a mirror, etc.; the remedy that was applied to resolve the malfunction; the date that the malfunction was repaired; and the time that the malfunction was repaired.

Information related to any malfunction of a Wayside Signal System for which a trouble ticket was issued

Data Elements Description
Railway ID Railway name/identification
Reporting Period 12 month period which the data represents from November 1 to October 31 (e.g. 2014/15 would represent the data from November 1, 2014 to October 31, 2015)
Subdivision Name of the subdivision
Mileage of Wayside Signal System Mileage point of the Wayside Signal System affected
Ticket number The number assigned by the railway for the trouble ticket
Date reported Date the malfunction was reported
Time reported Time the malfunction was reported
Reported problem Description of the malfunction reported in the field
Failed Sub-system Name Name of the sub-system and/or component that malfunctioned (e.g. signal control point, power switch, indication rod, etc.)
 Resolution The remedy that was applied to resolve the malfunction
Restoration Date Date the malfunction was repaired
Restoration Time Time the malfunction was repaired
Information related to any malfunction of a Wayside Signal System for which a trouble ticket was issued

The Information related to any malfunction of a Wayside Signal System for which a trouble ticket was issued table lists and describes the data elements that Class I and Class II rail carriers would be required to collect. The data elements include the railway name and identification; the reporting period, which is the 12 month period from November 1 to October 31; the name of the subdivision; the mileage point of the Wayside Signal System affected; the number assigned by the railway for the trouble ticket; the date that the malfunction was reported; the time that the malfunction was reported; a description of the malfunction reported in the field; the name of the failed sub-system and/or component that malfunctioned, for example the signal control point, a power switch, or an indication rod, etc.; the remedy that was applied to resolve the malfunction; the date that the malfunction was repaired; and the time that the malfunction was repaired.

Number of culverts requiring continued monitoring per subdivision at the end of the reporting period

Data Elements Description
Railway ID Railway name/identification
Reporting Period 12 month period which the data represents from November 1 to October 31 (e.g. 2014/15 would represent the data from November 1, 2014 to October 31, 2015).
Note: The data represents the status of the culverts at the end of the reporting period
Subdivision Name of the subdivision
Number of culverts Total number of culverts on the subdivision
Culverts with continuous monitoring Number of culverts on the subdivision requiring continued monitoring
Number of culverts requiring continued monitoring per subdivision at the end of the reporting period

The Number of culverts requiring continued monitoring per subdivision at the end of the reporting period table lists and describes the data elements that Class I and Class II rail carriers would be required to collect. The data elements include the railway name and identification; the reporting period, which is the 12 month period from November 1 to October 31, noting that the data represents the status of the culverts at the end of the reporting period; the name of the subdivision; the total number of culverts on the subdivision; and the number of culverts on the subdivision requiring continued monitoring.

Number of bridges with Temporary Slow Orders per subdivision at the end of the reporting period

Data Elements Description
Railway ID Railway name/identification
Reporting Period 12 month period which the data represents from November 1 to October 31 (e.g. 2014/15 would represent the data from November 1, 2014 to October 31, 2015). Note: The data represents the status of the bridges at the end of the reporting period
Subdivision Name of the subdivision
Number of Bridges Total number of bridges on the subdivision
Bridges with Temporary Slow Orders Number of bridges with Temporary Slow Orders on the subdivision
Number of bridges with Temporary Slow Orders per subdivision at the end of the reporting period

The Number of bridges with Temporary Slow Orders per subdivision at the end of the reporting period table lists and describes the data elements that Class I and Class II rail carriers would be required to collect. The data elements include the railway name and identification; the reporting period, which is the 12 month period from November 1 to October 31 that the data represents, noting that the data represents the status of the culverts at the end of the reporting period; the name of the subdivision; the total number of bridges on the subdivision; and the number of bridges with Temporary Slow Orders on the subdivision.

Road

Intercity Buses

Scheduled Intercity Bus Passenger Origin and Destination Survey

Data Record Layout
Motor Carrier Name
Date
Passenger Origin
Passenger Destination
Connection 1 City
Connection 1 Motor Carrier
Connection 2 City
Connection 2 Motor Carrier
Connection 3 City
Connection 3 Motor Carrier
Discount type
Fare paid
Number of passengers
Scheduled Intercity Bus Passenger Origin and Destination Survey

The Scheduled Intercity Bus Passenger Origin and Destination Survey table lists the data elements that intercity buses are required to submit as per the Transportation Information Regulations. Some of the key fields include motor carrier name, discount type and number of passengers. The survey assists intercity bus companies when reporting the origin, destination, and itinerary of their passengers.

Passenger Motor Carrier Schedules Survey

Data Record Layout
Motor Carrier Name
Year
Quarter
Origin
Destination
Express or Local
Number of departures
Number of seats available
Passenger Motor Carrier Schedules Survey

The Passenger Motor Carrier Schedules Survey table lists the data elements that intercity buses are required to submit as per the Transportation Information Regulations. Some of the key fields include express or local, number of departures, and number of seats available.

Scheduled Intercity Bus Freight and Parcel Survey

Data Record Layout
Motor Carrier Name
Date
Origin City
Destination City
Total weight of freight carried
Total weight of parcels carried
Number of bus bills
Number of parcels/items
Revenues
Scheduled Intercity Bus Freight and Parcel Survey

The Scheduled Intercity Bus Freight and Parcel Survey table lists the data elements that intercity bus companies are required to submit as per the Transportation Information Regulations. Some of the key fields include total weight of freight carried, number of parcels/items and revenues.  The survey enables intercity bus companies to report on their freight operations.

Annual Bus Fleet Inventory and Fuel Consumption Survey

Data Record Layout
Motor Carrier Name
Reporting Year
Registration
Vehicle make
Vehicle model
Vehicle Vintage (Model-Year)
Vehicle type of tire
Vehicle tare weight
Vehicle seating capacity
Accessibility for passengers with reduced mobility
Bus engine type
Bus engine output
Bus engine year of construction
Bus transmission type
Distance travelled by the bus (KM)
Location city
Location province
Fuel type
Fuel consumption (British Columbia)
Fuel consumption (Alberta)
Fuel consumption (Saskatchewan)
Fuel consumption (Manitoba)
Fuel consumption (Ontario)
Fuel consumption (Quebec)
Fuel consumption (New Brunswick)
Fuel consumption (Prince Edward Isl.)
Fuel consumption (Nova Scotia)
Fuel consumption (Newfoundland & Labrador)
Fuel consumption (Nunavut)
Fuel consumption (Northwest Territories)
Fuel consumption (Yukon)
Fuel consumption (United States)
Fuel consumption (Mexico)
Annual Bus Fleet Inventory and Fuel Consumption Survey

The Annual Bus Fleet Inventory and Fuel Consumption Survey table lists the data elements that intercity bus companies are required to submit as per the Transportation Information Regulations. Some of the key fields include registration, fuel type and distance travelled by the bus. 

Trucking

Annual Truck Fleet Inventory and Fuel Consumption Survey

Data Record Layout
Motor Carrier Name
Reporting Year
Registration
Truck/ Trailer flag
Vehicle make
Vehicle model
Vehicle Vintage (Model-Year)
Vehicle type of tire
Vehicle tare weight
Truck engine type
Truck engine output
Truck engine year of construction
Truck transmission type
Distance travelled by the truck (KM)
Location city
Location province
Fuel type
Fuel consumption (British Columbia)
Fuel consumption (Alberta)
Fuel consumption (Saskatchewan)
Fuel consumption (Manitoba)
Fuel consumption (Ontario)
Fuel consumption (Quebec)
Fuel consumption (New Brunswick)
Fuel consumption (Prince Edward Island)
Fuel consumption (Nova Scotia)
Fuel consumption (Newfoundland & Labrador)
Fuel consumption (Nunavut)
Fuel consumption (Northwest Territories)
Fuel consumption (Yukon)
Fuel consumption (United States)
Fuel consumption (Mexico)
Annual Truck Fleet Inventory and Fuel Consumption Survey

The Annual Truck Fleet Inventory and Fuel Consumption Survey table lists the data elements that trucking companies are required to submit as per the Transportation Information Regulations. Some of the key fields include registration, fuel type and truck engine type.

Date modified: