Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

  1. The owner of two or more aircraft can request approval from the Aircraft Certification Publications unit to submit a single consolidated fleet report for their aircraft in lieu of submitting individual reports for each of those aircraft.

  2. Consolidated fleet reports are to be submitted in an approved form and manner to the Publications Unit (the client is to fill out a prepopulated XLS sheet) not later than on the approved due date, and shall contain information for each individual aircraft in the fleet. The approved due date for the consolidated report is 30-March.

Information Note:
The owner will not be sent an automated reminder that a consolidated fleet report is coming due. The reminders are handled through system generated emails manually sent to each operator (currently around 60+ fleets on file)

A FLEET is defined by a record on Y59, with 4 digit “fleet numbers” (1st digit represents TC region) These fleet numbers are applied to Y02 records (fleet_id) to tie aircraft together under a single fleet reporting unit.

The effects of an aircraft having a fleet_number on y02 are to

  1. exempt that specific aircraft from processing during an EDM broadcast

  2. prevent that owner from submitting individual aircraft via the website

  3. include ALL of that owners aircraft in a spreadsheet when a Consolidated fleet report is launched.

Launching the Fleet AAIR Report at the Beginning of a new AAIR cycle

During the first week of each January, the Publications Unit (AARDA) requests the “Consolidated Fleet Report” from the AAIR side menu

The Fleet report “Launch” button performs the following tasks

  1. Create email documents, 1 for each FLEET, containing a spreadsheet of the tombstone data for each aircraft within each fleet, with blank columns for the owner to fill in

  2. It publishes these “unsent” emails in the inbox of TC.AAIR-RAINA.TC@TC.GC.CA

  3. A Publications user forwards these emails manually to each client, after ensuring that the email addresses and spreadsheet contents are correct

Special note : this function is NOT security protected to Admin role code (AU) though it likely should be. Any CAWIS user with a role code of HU or above can “launch” this report in the mistaken belief that they will receive an online list of all FLEETS and their associated aircraft. While the emails generated do not go further than the Publications unit, it does cause them frequent confusion (3 or 4 times per year) There is also no record kept of what user launched the report. This issue has been raised with AARDA management previously.

  • No labels

0 Comments

You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account.