CAWIS needs to provide a VIEW to Business Intelligence (BII) - and/or any other requesting application(s), so that inquiries can be directed to a single source which allows for a reckoning of all known aircraft, all flight hours for all available years and the associated analysis codes required for any breakdowns.
Data notes : flight hours data has been collected historically since 1994 (though 1994 itself, is very incomplete)
Flight hours are collected for the previous year, during the current year, so data for Current-year - 1 should always be considered incomplete until current year end.
The Operating Rule data (found on Y02) is terribly incomplete/inaccurate. Unfortunately this is the data element most frequently requested for breakdowns. CAWIS only retains a PRIMARY-OPERATING-RULE (the numerically highest Op rule) so, any conclusions drawn from this data should be considered highly suspect.
An enhancement request for flight hours breakdowns by CARS , from TSB, is discussed here
AAIR CLIENT SUBMISSIONS
OPERATING RULE | DESCRIPTION |
|---|---|
406 | FLIGHT TRAINING UNIT |
604 | PRIVATE-OP PASSENGER |
701 | FOREIGN AIR OPS |
702 | AERIAL WORK |
703 | AIR TAXI OPS |
704 | COMMUTER OPS |
705 | AIRLINE OPS |
999 | UNDEFINED |
OPRULE (aka, Operating Rule/License Type/CAR) is acquired from NAPA. (V_CAW_IS_REG_AC_OP_RULE@NNPRODC.WORLD)
Unfortunately, the data is NOT completely reliable as is presented. It’s simply 2 columns - Tail_mark, and Operating_rule - reviewed & kept up to date, each night in the CCARCS/CAWIS synchronization routines.
However, only approximately 7800 of 39,000 registered aircraft are accounted for in this view on any given day.
For instances where NO OPRULE is provided for a specific tail-mark, the last known OPRULE remains in effect on that specific aircraft in CAWIS. For instances where an OPRULE was never provided, it stays at 999 – Unknown.
So, an aircraft may operate over a given year, under multiple Operating rules, for differing periods of time, but NAPA only provides to CAWIS, the numerically “highest” operating rule found for that aircraft.
So if an aircraft flew under 705 & 704 in a given year - CAWIS would only record it as having flown under 705.
There exists a long standing request (from AVSTATS) that flight hours be broken down by operating rule when the operators submit their AAIR, though no action has ever been taken. (requires a change to the regulation, the printed form, the AAIR code etc)
The Public AAIR data view should look something like this :
SEE ATTACHMENT : FLIGHT-HOURS-VIEW.TXT
DATA DESCRIPTIONS
AIRCRAFT_ID | UNIQUE NUMERIC IDENTIFIER FOR THIS AIRCRAFT ON THE CANADIAN REGISTER ALLOCATED BY CCARCS (Canadian Civil Aircraft Register) |
MARK | AIRCRAFT TAIL MARK DURING THIS REPORTING YEAR - BEGINS WITH 'F' OR 'G' ( 'I' is not included ultralights do not report flight hours ) An aircraft may change its tail mark many times over its lifetime |
REPORTING_YEAR | REPORTING YEAR - 2010 THRU CURRENT YEAR - 1. THIS REPORT ONLY INCLUDES AIRCRAFT FOR WHICH A REQUEST TO REPORT WAS ISSUED BY TC FOR REPORTING OF THAT CALENDAR YEAR - THE CURRENT "REPORTING YEAR" IS ALWAYS = CURRENT YEAR - 1 . DATA FOR THE CURRENT REPORTING YEAR IS NOT CONSIDERED COMPLETE UNTIL 31-DECEMBER OF THE FOLLOWING YEAR (aka THE COLLECTION YEAR) |
AIRCRAFT_ENTRY_DATE | ENTRY-DATE - INDICATES THE FIRST APPEARANCE OF THIS AIRCRAFT IN CAWIS (A DEFAULT DATE OF 1994 WAS USED FOR MUCH OF THE LEGACY DATA TAKEN FROM THE OLD MAINFRAME APP, CAIS) |
ACTIVE_IND | ACTIVE INDICATOR - IS THIS AIRCRAFT ON THE CURRENT REGISTER ? |
SR/IA | SALE REPORTED - OR - INVALID ADDRESS - THESE AIRCRAFT/OPERATORS ARE UNCONTACTABLE - THERE EXISTS AN INDICATION THAT AAIR WAS REQUESTED BUT NONE WAS RECEIVED. MANY SALE REPORTED AIRCRAFT HAVE BEEN DESTROYED, AND OWNERSHIP WAS TAKEN OVER BY INSURANCE COMPANIES, WHO DO NOT IDENTIFY THEMSELVES TO TC. MANY OTHER OF THESE AIRCRAFT APPEAR ON FOREIGN REGISTRIES. |
YEAR_MFG | YEAR OF MANUFACTURE - NOTE - AN AIRCRAFT LISTED HAVING BEEN CONSTRUCTED DURING THE CURRENT YEAR WILL NOT BE ISSUED A REQUEST FOR FLIGHT HOURS |
YEAR_IMPORT | YEAR OF IMPORT - NOTE - AN AIRCRAFT LISTED HAVING BEEN IMPORTED DURING THE CURRENT YEAR WILL NOT BE ISSUED A REQUEST FOR FLIGHT HOURS, DESPITE THE POSSIBLITY IT MAY HAVE BEEN ON THE REGISTER UNDER OTHER OWNERSHIP DURING THE PREVIOUS YEAR |
FLIGHT_AUTHORITY | FLIGHT_AUTHORITY |
PURPOSE | AIRCRAFT_PURPOSE DURING THE GIVEN REPORTING YEARCODE DESCR |
OPERATING_RULE | PRIMARY OPERATING RULE DURING THE REPORTING YEAR (ONLY THE NUMERICALLY HIGHEST OP RULE IS SAVED TO THE DATABASE)CODE DESCR |
MAX_TAKEOFF_LBS | MAXIMUM TAKE OFF WEIGHT POUNDS |
AIRCRAFT_MFG | AIRCRAFT MANUFACTURER |
AIRCRAFT_MODEL | AIRCRAFT MODEL - AN 'X' SUFFIX INDICATES AN OWNER-MAINTAINED VERSION OF THIS TYPE OF MODEL |
GROUP_ID | AIRCRAFT GROUP CODE FOR BII TOTALLING PURPOSES |
SERIAL_NUMBER | AIRCRAFT SERIAL NUMBER |
TATC_CD | TYPE_APPROVAL - OR - TYPE_CERTIFICATE NUMBER FOR THIS MANUFACTURER AND MODEL |
TCH_COUNTRY | TYPE_CERTIFICATE_HOLDER COUNTRY |
OWNER_TYPE | 1-INDIVIDUAL, 2-ORGANIZATION |
OWNER | LAST OWNER OF THAT AIRCRAFT DURING THE REPORTING YEAR |
CLIENT_ID | OWNER CLIENT_ID AS ASSIGNED BY CCARCS |
REGION | TC_REGIONCODE DESCR |
TC_CENTRE | TC_FILE_LOCATIONCODE DESCR REGN PROV |
COUNTRY | aircraft based country (99.99% Canada) However it can be based in any country |
PROVINCE | aircraft based province |
BASED | primary aircraft base |
MUNICIPALITY | aircraft based municipality |
OTHER | aircraft other based locale |
AIRPORT | aircraft based airport |
RECD_IND | WAS A REPORT RECEIVED FOR THIS REPORTING YEAR ? |
TIME_SINCE_NEW | TIME SINCE NEW FOR THAT REPORTING YEAR ( NOT NECESSARILY CUMULATIVE, ENTRY ERRORS WERE MADE FROM YEAR TO YEAR) |
YEARLY_HOURS_FLOWN | TOTAL HOURS FLOWN BY THIS AIRCRAFT DURING THIS REPORTING YEAR |
TRAINING_HOURS | TRAINING HOURS DURING THIS REPORTING YEAR |
OTHER_HOURS | OTHER TYPE HOURS DURING THIS REPORTING YEAR |
0 Comments