Page Comparison

DATA ELEMENT OR BUTTON 

DESCRIPTION

MARK

Current aircraft tail mark (Y02,Y93) - Not updatable by CLIENT.
Note : An aircraft tail mark can change at any time by request of the owner/operator.

(A “swap” record is placed on CARS_DAILY_CAIS_MASTER and a notation of the MARK update is made on the Y01 TC_notes during the sync job)

Occasionally a tail mark change occurs between AAIR notification and receipt. (EDM email or Hard copy mailing) In these instances, an AAIR is required for “this specific aircraft” identified by by model and serial number, regardless of the tail mark noted in the email or on the form.

AAIR DUE

March-30 - or - May-30

LAST AAIR FORM RECEIVED BY TC

Date last AAIR was received/recorded on the M01 table

LAST NOTIFICATION SENT BY TC

Date M01 record for the current reporting year was created (date current date)

OWNER NAME

Owner name from Y53 table

ADDRESS LINE-1

owner address line-1 (A90)

ADDRESS LINE-2

owner address line-2 (A90)

CITY/TOWN

owner city (A90)

PROVINCE/STATE

owner province_cd (A90)

COUNTRY

owner country_cd (A90)

POSTAL CODE

owner postal cd (A90)

FAX

owner fax number (A92)

PHONE

owner phone number (A92)

AAIR PREFERRED LANGUAGE

values - currently not actioned in any way - all transmissions are currently bilingual

OWNER EMAIL

owner email address (A92)

FLIGHT AUTHORITY

potential values - unchangeable by the submitter (ultralights H,I are not included)

TYPE OF REGISTRATION

potential values - unchangeable by the submitter. Data provided by CCARCS

BASED COUNTRY

Anything from TR21_country table - though 99.9% are listed as Canada

PROVINCE/STATE

Anything from the TR01_province table - includes Canadian provinces and US States

MUNICIPALITY

Freeform text - Note : as a security measure, ALL TEXT fields are inspected for HTML characters

AIRPORT

Acquired from CCARCS by can be changed by the submitter - freeform text

OTHER

Freeform text

TC REGION

Denotes the physical location of the aircraft’s 5008 file. Region is provided by CCARCS. Not updateable by the Client

LAST 100 HOUR INSPECTION

The Client/User provides the Date of their most recent 100 hour inspection for this aircraft. If the user inadvertently provides a date LOWER than the most recent date already on file (C07 table) and submits the AAIR, they would need to contact TC and/or describe the “error” in the owner notes.

Data cleanups of this nature are to be handled by the Publications Unit (see also PBI: #115120 - revisions to inspection dates on the 5008 page )

Re-entering the completed AAIR in edit mode will only display the most recent date of inspection found on C07 for this aircraft-id

NOTE: the client can only enter Annual/100 Hour inspections. (Inspection type = 2) TC inspections are entered by TC users only on the 5008 page (Inspection type = 1)

INSPECTED BY

AME/AMO or Owner/Other

MODIFY

1. SELECT AME -OR- AME by a Name search

or

2. SELECT AME -OR- AMO by a document number search

or

3. CLIENT selects Owner/Other. Owners name is auto filled into INSPECTED-BY field, but can be altered (freeform text)

example: instances where the AMO/AME could NOT be located under options 1 or 2

AMO/AME NAME

Will contain AMO / AME or an Owner-Other name

LICENSE NUMBER

License number of AMO/AME - this field does not appear when OWNER/OTHER is selected.
NOTE: Inactive/Expired AMO & AME numbers always need to appear in both lists (AMO_INFO, AME_INFO) since the inspection date being entered can potentially be several years old

Aircraft operated pursuant to CAR IV or CAR VII

Not a database element. Simply a radio button that overrides the requirement to put in an Annual inspection date.

Details on the Canadian Aviation regulations are here :

Canadian Aviation Regulations (CARS)  

Has Aircraft been damaged since last report

The Client provides Date damage occurred (Y02). This cannot be earlier than year of manufacture or greater than current date.

If a Damaged date was provided in a previous reporting year, but NO repair date was ever provided, that Damaged date will continue to appear on that AAIR page each year, until such time as the operator provides a Repaired-date.

When a Y02 record is found to have both a DAMAGED date and a REPAIRED date, the overnight job (beginning 3rd week of December of any given year) will insert a NEW Y02 record having NULLS in both the damaged and repaired date fields (thus burying the Damaged/repaired dates in History), so the damaged date will come up null for the next reporting year.

NOTES:

1. the CLIENT can also NULL out a damaged date without providing a repaired date. This occurrence gets recorded to the Y05 log file

2. A newly registered aircraft that has previously been on the register can possibly display a damaged-date if no repair-date was supplied before last de-registry

Date of Repair certification

Cannot be earlier than year of manufacture or greater than current date.

Must be greater than or equal to Damaged date.
[ER] Historical Damaged and Repaired dates need to appear in a grid format on the 5008 page so TC users/inspectors might review and/or make corrections

The Last reported Total Time Since New is :

Non updatable by client. Total Time Since New (TSN) for this aircraft (Q02 table where flying hours type code = 1) from the most recently received AAIR is provided here for reference. Client issues with this figure should be placed in the owner notes for any data repair required by the Publications unit.
There have been many flight hours discrepancies caused by decimal points, and french keyboards substituting commas for periods

Total Hours flown from January 1st to December 31st YYYY

Total hours flown by this aircraft in the reporting year (Current year - 1)

Cannot exceed 8760 hours (24 hours * 365 days in a year)

Total Hours flown since new up to December 31st YYYY

Total time since new (TSN) for this Aircraft up to 31-December of the reporting year. This value must be equal to or greater than the TSN provided above

TRAINING

Any training related hours (Operating rule 406) performed during this reporting period. Must be less then or equal to Hours flown in that year

OTHER AERIAL WORK

Any “other” related hours performed during this reporting period. Must be less then or equal to Hours flown in that year (Note: this data element and Training hours were added by management request in the late 90’s but are very rarely filled in )

[ER] There exists an ongoing request from the AVSTATS group to breakdown flight hours collection, for all aircraft by operating rule. Background notes included for reference only.

SEE ATTACHMENT - CAWIS-AAIR_FLIGHT HOURS TSB REPORT.msg

This would entail

1) adding these codes to TR34_flying_hours_type,

2) recoding the AAIR and the 5008 page with these 7 extra columns (below)

3) redesigning the paper form

4) reconciling the Historical data from Y02, which does provide a PRIMARY-OPERATING-RULE for any given year and breaking down the existing Annual hours flown on Q02 by some agreed upon percentile

REPORTING PERIOD

Show the client the data for the previous years for which this aircraft has submitted a report (non-updatable)

“Missing” flight hours for any previous reporting periods can also be entered

Discrepancies should be reported in the owner notes field. (There are frequently disagreements in the logbooks, when ownership changes for an aircraft)

This data element will display Reporting-period/hours-flown for ALL years in which this aircraft reported an AAIR.

Notes: AAIR data was only saved historically beginning in 1994

AAIR data cannot exist prior to the aircraft year of manufacture (Y01)

HOURS FLOWN DURING REPORTING PERIOD

ANNUAL HOURS FLOWN (from Q02 table where flying hours type code = 2) for the reporting period

MANUFACTURER COMMON NAME

Aircraft manufacturer (Y04) - acquired from CCARCS

Not updateable by client

All mfg/model discrepancies should be reported in the owner notes field.

CCARCS DESIGNATION

CCARCS legal name for this manufacturer (Y01 -or- Y93)

Not updateable by client

MODEL

Aircraft model - Y04 table - acquired from CCARCS

Not updateable by client

SERIAL NUMBER

Aircraft serial number - Y04 table - acquired from CCARCS

Not updateable by client

TYPE CERTIFICATE

NAPA TATC code from Y62 table matching this aircraft manufacturer/model

Not updateable by client

EMPTY WEIGHT LAST ACTUAL

optional - must be less than or equal to MAX take-off - pounds only

ON L/G

optional - values

DATE

Date required if a new EMPTY LAST ACTUAL provided

EMPTY WEIGHT LAST AMENDED

optional - must be less than or equal to MAX take-off - pounds only

ON L/G

optional

DATE

date required if a new EMPTY WEIGHT LAST AMENDED provided

MAX TAKE OFF WEIGHT

acquired from CCARCS, updatable by CLIENT

ON L/G

optional

MODIFY (ENGINE)

Modify - The CLIENT can select any engine from the Y62 mfg/model table to replace the one currently appearing on this aircraft. (Y04 TABLE)

The CLIENT may also create a new model (and manufacturer, if necessary) which gets moved to the NOT report for possible AD review by a CAW Technical inspector

Not reporting is described in detail here : NOT REPORTING

REMOVE (ENGINE)

remove existing ENGINE mfg/model from this aircraft

ADD (ENGINE)

ADD a new ENGINE to this aircraft (Ordinal number 2,3 etc)
NOTE : there is no limit to the number of engines that an aircraft file can have.
The Number of engines on Y01 is adjusted accordingly
Engine manufacturer and model rows do NOT necessarily have to match (but 99% of the time, they do)

MANUFACTURER 

Engine manufacturer (Y04 table)

MODEL

Engine model (Y04 table)

SERIAL NUMBER

freeform text - fully updatable by client

TATC CODE

NAPA TATC code from Y62 table matching this engine manufacturer/model

Not updateable by client

MODIFY (PROPELLER)

Modify - The CLIENT can select any propeller from the Y62 mfg/model table to replace the one currently appearing on this aircraft. (Y04 TABLE)

The CLIENT may also create a new model (and manufacturer, if necessary) which gets moved to the NOT report for possible AD review by a CAW Technical inspector

REMOVE (PROPELLER)

remove existing PROPELLER mfg/model from this aircraft

ADD (PROPELLER)

ADD a new PROPELLER to this aircraft (Ordinal number 2,3 etc)
The number of Propeller manufacturer/model rows must match the number or ENGINE rows

MANUFACTURER 

Propeller manufacturer (Y04 table)

MODEL

Propeller model (Y04 table)

SERIAL NUMBER

freeform text - fully updatable by client

TATC CODE

NAPA TATC code from Y62 table matching this propeller manufacturer/model

Not updateable by client

SKI MANUFACTURER

SKI manufacturer (Y04 table)

SKI MODEL

Ski model (Y04 table)

MODIFY

Modify - The CLIENT can select any SKI from the Y62 mfg/model table to replace the one currently appearing on this aircraft. (Y04 TABLE)

The CLIENT may also create a new model (and manufacturer, if necessary) which gets auto assigned a TATC code of “NOT CERTIFICATED” ( Ski & Float models are not monitored by CAW Inspectors )

FLOAT MANUFACTURER

FLOAT manufacturer (Y04 table)

FLOAT MODEL

Float model (Y04 table)

MODIFY

Modify - The CLIENT can select any FLOAT from the Y62 mfg/model table to replace the one currently appearing on this aircraft. (Y04 TABLE)

The CLIENT may also create a new model (and manufacturer, if necessary) which gets auto assigned a TATC code of “NOT CERTIFICATED” ( Ski & Float models are not monitored by CAW Inspectors )

THE AIRCRAFT IS CURRENTLY OUT OF SERVICE

Activating this radio button reveals the following input fields to the Client.

a) Out of Service Start,

b) Expected return to service

c) Expected return to service unknown

d) Out of service reason

1. The user provides an Out of Service Start Date (y02 table) (OOS) . Limit is 5 years in the past

2. The user provides an Expected return to service date (y02 table) (ERTS) - 5 year limit from the Out of Service Start date. It should fall within Current-year + 2 or later.

3. Estimated return to service date UNKNOWN - the system applies an ERTS date of OOS-start + 5 years

4. The complete Out of service period must EXCEED a full calendar year (ie: at least ALL of the next calendar year ) to be considered out of service. If they fly 1 hour this year and 1 hour next year, the aircraft is not considered OOS

5. OOS conditions are “buried” by newer Y02 history records by the overnight batch job, with NULLs in the OOS fields, once an Expected-Return-to-Service (ERTS) date has been passed.

6. An OOS aircraft where the OOS-start-date is less than the Current year, WILL NOT be contacted for AAIR reporting until the calendar year AFTER the ERTS date has been reached. However if the OOS start date is within the current year, they will be contacted via EDM and they are obliged to report any hours flown during the active portion of this current year.

7. An OOS aircraft where the OOS-start-date is less than the Current year, will have an AAIR auto recorded by overnight batch job for each year of the OOS period (an M01 record inserted with issue-date and received-date = Current date and ZERO hours recorded on the Q02 table) These aircraft will then be exempted from the next EDM run because the system will have already recorded “closed” AAIRs for the current reporting year.

8. An operator indicating a "permanent" out of service status should be encouraged to contact registry ( CCARCS ) to de-register that  aircraft

OUT OF SERVICE START DATE

Beginning of the out of service (OOS) period. If this date falls within the current year, the operator will receive AAIR notification next year for hours flown this year.

EXPECTED RETURN TO SERVICE DATE

(ERTS_DATE) The End (or expected end) of the out of service period. Must fall somewhere within Current-year + 2 to be considered a legitimate out of service period.
The Operator may return to service early by contacting the Publications unit. The TC user then enters a new ERTS date of today (or somewhere near today) .

When the overnight job encounters an ERTS date <= Sysdate, a new Y02 record is inserted where OOS-start-date, ERTS-date, and OOS-reason-code are all NULLs

[ER] Expired out of service periods need to appear in a grid format on the 5008 page for AAIR debugging purposes

OUT OF SERVICE REASON

values

OWNERS NOTES

Freeform text - The CLIENT should enter any submission difficulties or data anomalies here. They are ALL displayed on the 5008 edit page for the TC user to review (ordered newest to oldest) Due to security concerns, the system will raise an error if any statements are found resembling HTML code

SUBMIT

Submit the AAIR

BACK

Go back to AAIR aircraft list without submitting this AAIR

INSTRUCTIONS

Link to instructions for AAIR submission

AAIR INSTRUCTIONS - PDF